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

[Mentaluproar]

This might be a stupid question to ask, but why use the 4.4 kernel when mainline is compatible with this board? Wouldn’t it make more sense to apply some patches to a newer kernel than to backport fixes to an older one?

[lmza]

I tried the 22.02.2019 release and this is the first Rockpro64 image that actually detects my DVB pcie x1 card. Well done!

I still unfortunately still need the kernel source in order to build and install the V4L DVB Device drivers. So looking forward to this.

I express the same view as many other Rockpro64 users whereby I felt a bit tricked in buying the Rockpro64 without the knowledge that only a few PCIe cards are actually supported by default. 

Thank you for the effort and getting this far!

[Mrfixit2001]

mentaluproar - not a stupid question at all
The 4.4 kernel is rockchip's board-specific breed, and has a lot of special tweaks which make it optimized for their platform. Mainline's compatibility isn't quite there yet, but continues to get better every day. It's important to differentiate the difference between "compatible" and "bootable". There's many features that just haven't made it to mainline yet. But again, that will improve in time. For now, I've chosen to take mainline improvements and backport them to the 4.4 kernel in order to provide the most optimized experience I'm able to. This is especially important with features like hardware acceleration. The kernel in this build is optimized for media and emulation, altho obviously can be utilized for many other things such as desktops.

[tblindba]

I just tried the newest version, and I think its a great improvement. I'm using the NAS box with the Pine64 PCI card, and the first version would pick up the PCI card every 4th or 5th reboot. It kept on saying there was a PCI timeout error in the dmesg.

Now I've booted several times after trying the new version and the disks came right up every time.

This is fantastic work!

Thanks again!

I haven't tried a desktop environment yet, has anyone tried to get firefox or chromium working?

[Luke]

I just tried the newest version, and I think its a great improvement. I'm using the NAS box with the Pine64 PCI card, and the first version would pick up the PCI card every 4th or 5th reboot. It kept on saying there was a PCI timeout error in the dmesg.

Now I've booted several times after trying the new version  and the disks came right up every time.

This is fantastic work!

Thanks again!

I haven't tried a desktop environment yet, has anyone tried to get firefox or chromium working?

As for your question regarding desktop ... unless something goes wrong a desktop testing image should be uploaded in a week or so.

[MisterA]

I'm sorry to report this build is still not playing well with my PCIe x4 Sata card.

I can boot into the OS most of the time, but a warm reboot is hit & mis. My monitor becomes active but nothing is shown on it.
When I can boot into the os, lspci shows:
00:00.0 PCI bridge: Device 1d87:0100
01:00.0 PCI bridge: Pericom Semiconductor Device 2608
02:01.0 PCI bridge: Pericom Semiconductor Device 2608
02:02.0 PCI bridge: Pericom Semiconductor Device 2608
02:03.0 PCI bridge: Pericom Semiconductor Device 2608
02:04.0 PCI bridge: Pericom Semiconductor Device 2608
03:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
06:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)

I can see the one harddrive I attached to the board, and can mount the partition and do read/write operations.
However the sata card stil gets extremely hot, after two minutes the four chipset chips got over 80 degrees celsius. I switched the board off because I was afraid I was going to damage the card. The card has 4 marvel 9215 chips on it, each able of controlling 4 sata disks (https://www.amazon.com/IO-Crest-Controll...B00XI4OL82)

In dmesg I can see entries like below, perhaps this has something to do with it?
[    0.230078] vcc12v_pcie: supplied by dc_12v
[    0.230086] dc_12v: could not add device link regulator.8 err -2
[    0.230122] vcc12v_pcie: 12000 mV 
[    0.230280] reg-fixed-voltage vcc1v8-sdio: Looking up vin-supply from device tree
[    0.230296] vcc1v8_sdio: unable to resolve supply
[    0.230303] reg-fixed-voltage vcc1v8-wifi: Looking up vin-supply from device tree
[    0.230317] vcc1v8_wifi: unable to resolve supply
[    0.230326] reg-fixed-voltage vcc12v-pcie-regulator: vcc12v_pcie supplying 12000000uV
[    0.230380] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc3v3-pcie-regulator[0]'
[    0.230395] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    0.230429] vcc3v3_pcie: supplied by vcc3v3_sys
[    0.230437] vcc3v3_sys: could not add device link regulator.9 err -2
[    0.230462] vcc3v3_pcie: 3300 mV 

Attached is my dmesg.

[NoDiskNoFun]

Hello MrFixIt, 
i've seen you uploaded the kernel source to github, thanks 
Could u provide your config or a defconf file since i am not able to build it (crashed early at vdso.h)

CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
make[1]: 'include/generated/vdso-offsets.h' is up to date.
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/compile.h
CC arch/arm64/kernel/vdso.o
arch/arm64/kernel/vdso.c: In function 'vdso_init':
arch/arm64/kernel/vdso.c:119:6: warning: 'memcmp' reading 4 bytes from a region of size 1 [-Wstringop-overflow=]
error, forbidden warning:vdso.c:119
if (memcmp(&vdso_start, "\177ELF", 4)) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[1]: *** [scripts/Makefile.build:278: arch/arm64/kernel/vdso.o] Error 1
make: *** [Makefile:1031: arch/arm64/kernel] Error 2

[NoDiskNoFun]

I worked around this bug by reverting to gcc-7 but now it stops at

make[1]: *** No rule to make target 'fs/readdir.o', needed by 'fs/built-in.o'. S
make: *** [Makefile:1031: fs] Error 2

[Mrfixit2001]

NoDiskNoFun: Sorry for the confusion - the fork you saw was not my kernel source, it was just there for a pull request I made on nuumio's repo.

That being said, now that I've got my releases updated, I have taken the time to create a new repo for my patched kernel source and pushed it for everyone:
https://github.com/mrfixit2001/rockchip-kernel

Please note that when I compile my kernel I use a config overlay, so the defconfig in the source isn't representative of the configs in my releases. I expect if you're compiling your own kernel, you'll likely have your own config needs anyways! But other than that, now you have all my updates!

Enjoy!

[pineadmin]

Added Minimal Debian by mrfixit2001 - 190222 on Wiki and Pine64 Installer