Update 22.02.2019 Feature-complete Debian build - SDIO WiFi/BT / PCIe / 3D / 2D

[laserguru]

dkryder: I found the installing wicd in LXDE makes WiFi configuration quite easy.

[caillou]

Given that I have no HDMI screen for my board, is there a way to start the ssh daemon by default on this build?

[dkryder]

dkryder:  I found the installing wicd in LXDE makes WiFi configuration quite easy.

thanks i will keep that in mind. right now i have no wifi though and no desktop so no way to d/l anything. i'm looking for a way to setup wifi in this minimum build. but, i've given up. i moved on to a build that has a desktop. the debian build that comes with desktop works fine.

[Mrfixit2001]

Here is the current kernel config in the build, will be enabling more in future releases.
https://pastebin.com/FKzRTrWX

caillou: SSH is enabled by default and should start up automatically

[MisterA]

I'm referring to my previous post about my PCIe Sata controller not working as it should: is there any news on better PCIe support?
Or should I presume that PCIe support can't get better for this board and that it's more of a hardware issue?

Best regards,
Jan

[Mrfixit2001]

MisterA - Jan - thanks for reaching out. I see you actually have this error in your dmesg: "bad mode: 0 [#1] SMP". So far I've only had one other user with this issue, others are having good success with pcie. My research in this error suggests a power issue. Can you confirm your power supply, and that you're powering your pcie disks externally? If you gather more logs from boots where pcie does not work for you, please provide them.

[MisterA]

MisterA - Jan - thanks for reaching out. I see you actually have this error in your dmesg: "bad mode: 0 [#1] SMP". So far I've only had one other user with this issue, others are having good success with pcie. My research in this error suggests a power issue. Can you confirm your power supply, and that you're powering your pcie disks externally? If you gather more logs from boots where pcie does not work for you, please provide them.

Hello, thank you for your reply.

I'm powering the rockpro64 board and the harddrive from a PC ATX 450W psu, but from a different power rail. So personally I doubt that insufficient power could be the culprit.
I will test powering the rockpro64 from a dedicated 5A 12V psu and the harddrive from the ATX psu but I'm pretty sure it will not make a difference.

Thank you for your help!

[NoDiskNoFun]

build error is:

  DTC     arch/arm64/boot/dts/rockchip/rk3399-box-808-android-6.0.dtb
arch/arm64/boot/dts/rockchip/rk3399-box-808-android-6.0.dtb: ERROR (phandle_references): Reference to non-existent node or label "cpu_id"

ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: *** [scripts/Makefile.lib:320: arch/arm64/boot/dts/rockchip/rk3399-box-808-android-6.0.dtb] Error 2
make[1]: *** [scripts/Makefile.build:484: arch/arm64/boot/dts/rockchip] Error 2
make: *** [arch/arm64/Makefile:131: dtbs] Error 2

i comment-out almost every dts from arch/arm63/boot/dts/rockchip/Makefile except of rk3399-rockpro64.dts

then it compiles just fine but panics on boot

[mknawabi]

Here is the current kernel config in the build, will be enabling more in future releases.
https://pastebin.com/FKzRTrWX

caillou: SSH is enabled by default and should start up automatically

Thank you for this. I mean to test a 4K framebuffer with your kernel, and the .config will help save me a bit of time going through menuconfig.

Also--have you been keeping a list of the patches that you've been applying to your kernel?

Cheers,

-Yama

[p1x3l3d]

MisterA - Jan - thanks for reaching out. I see you actually have this error in your dmesg: "bad mode: 0 [#1] SMP". So far I've only had one other user with this issue, others are having good success with pcie. My research in this error suggests a power issue. Can you confirm your power supply, and that you're powering your pcie disks externally? If you gather more logs from boots where pcie does not work for you, please provide them.

Hi Mrfixit, MisterA,

First off: thanks for all your hard work MrFixit Really happy to see that a stable build for the RockPro64 is being worked on!
Just tried your latest build (22.02.2019) and it runs smooth from eMMC here. I can SSH into it and it has internet access, so I can install packages and play around with it.

I have two issue though:
- The white indicator LED keeps blinking instead of burning steadily. I don't know if this indicates a problem as the system seems to be running fine, and I couldn't find anything about this in the documentation.
- My RAID controller (a HighPoint Rocket 640L, which I believe uses the Marvell 88SE9230 chipset), connected through PCI-e, is also not recognized:

Code:

root@localhost:/home# lspci
00:00.0 PCI bridge: Device 1d87:0100

The RAID controller chipset gets extremely hot (as in: can't touch it) after a short while though, and I see the same error showing up in my dmesg log as MisterA:

Code:

[ 1.743287] Internal error: Oops - bad mode: 0 [#1] SMP

Attached you can find my dmesg output. The error can be found on line 1035.

My RockPro64 is powered by the 'official' (EU) 12v 5A PSU and the two hard drives I have connected receive power from the RockPro itself through the 'official' power cable for SATA drives.

An interesting fact may be that I had Arch-ARM running on the RockPro64 before, and it seemed to be able to at least recognize the RAID controller; it showed up when I typed lscpi.

Do you have any idea what might be going wrong? If there's anything I can do to help/test any furter, please let me know

Thanks in advance!