Search the Community

Hi! On the Rockpro64, with the latest Amrbian dev kernel (5.4.0-rc1-rockchip64 updated on 19th of January), the sata hard drive connected to PCIe through the pine store adapter does not go to sleep anymore. It is properly set with hdparm and a udev rule, it used to work fine with the dev kernel before the 19th of January update. Now, if I issue a sleep commd (hdpram -y /dev/sda) it goes to sleep properly but not by itself after the 5 minutes inactivity I have set up. Mathias

In order to enumerate the major issues that are *still* valid now, I'm creating a 'crash dump' thread. The idea is simple, if your RK3399 board crashed recently, you just : Write what happened during the crash; Provide the link you got from sudo armbianmonitor -u , after the crash happened; Provide the content of /var/log/kern.log (if this file is present on your system) (attach it or copy the content on pastebin and link it here). No discussion here. Feel free to create a new dedicated thread afterwards to talk about the problem you encountered. Minor issues are welcome too, if they trigger a BUG message in your logs. Just state that it's a minor issue.

On several RockPro64 boards I experience infrequent freezes, mostly directly on boot, but also after some longer (hours, days) uptime. I use the official power adapter and no additional hardware except a PCIe adapter for an SSD, which works flawlessly when operational. When looking at the kern.log, there are quite a few errors and warnings, but comparing to a successful boot these are all also present. So I don't think they cause the freeze directly. Currently, I recorded the freeze on the latest Armbian Bionic as release just recently. FWIW, I think the same issue also occurs on the previous Debian Stretch image (had various freezes, but have not recorded any details yet). On a unsuccessful boot, the error occurs after about 8 seconds. A reboot (or two) usually fixes the issue, until the next time... Jul 8 15:18:23 carol kernel: [ 8.528275] Unable to handle kernel NULL pointer dereference at virtual address 00000000 Jul 8 15:18:23 carol kernel: [ 8.530625] pgd = ffffffc0ead3f000 Jul 8 15:18:23 carol kernel: [ 8.532515] [00000000] *pgd=0000000000000000, *pud=0000000000000000 Jul 8 15:18:23 carol kernel: [ 8.534710] Internal error: Oops: 96000005 [#1] SMP Jul 8 15:18:24 carol kernel: [ 8.536753] Modules linked in: af_packet iptable_nat nf_nat_ipv4 nf_nat nf_log_ipv4 nf_log_common xt_LOG xt_limit nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_conntrack nf_conntrack iptable_filter snd_soc_rockchip_hdmi_dp rk_vcodec ip_tables x_tables autofs4 phy_rockchip_pcie Jul 8 15:18:24 carol kernel: [ 8.542598] CPU: 5 PID: 1044 Comm: find Not tainted 4.4.182-rockchip64 #1 Jul 8 15:18:24 carol kernel: [ 8.544959] Hardware name: Pine64 RockPro64 (DT) Jul 8 15:18:24 carol kernel: [ 8.547155] task: ffffffc0eb247000 task.stack: ffffffc0e1c78000 Jul 8 15:18:24 carol kernel: [ 8.549491] PC is at do_dentry_open+0x234/0x2e4 Jul 8 15:18:24 carol kernel: [ 8.551687] LR is at do_dentry_open+0x288/0x2e4 Jul 8 15:18:24 carol kernel: [ 8.553852] pc : [<ffffff80081f2738>] lr : [<ffffff80081f278c>] pstate: a0000145 Jul 8 15:18:24 carol kernel: [ 8.556284] sp : ffffffc0e1c7bbc0 Jul 8 15:18:24 carol kernel: [ 8.558403] x29: ffffffc0e1c7bbc0 x28: ffffffc0eb247000 Jul 8 15:18:24 carol kernel: [ 8.560742] x27: 0000000000000000 x26: ffffffc0f26eb000 Jul 8 15:18:24 carol kernel: [ 8.563064] x25: 000000000000011d x24: ffffffc0e1cff690 Jul 8 15:18:24 carol kernel: [ 8.565376] x23: ffffff8008219cb8 x22: 0000000000000000 Jul 8 15:18:24 carol kernel: [ 8.567670] x21: 0000000000000000 x20: ffffffc0f27882b0 Jul 8 15:18:24 carol kernel: [ 8.569954] x19: ffffffc0e1cff680 x18: 0000007fb4979a70 Jul 8 15:18:24 carol kernel: [ 8.572191] x17: 0000007fb48e8848 x16: ffffff80081f3ea4 Jul 8 15:18:24 carol kernel: [ 8.574416] x15: 0000000000000000 x14: ffffffffffffffff Jul 8 15:18:24 carol kernel: [ 8.576663] x13: 0000000000000000 x12: 0101010101010101 Jul 8 15:18:24 carol kernel: [ 8.578896] x11: 7f7f7f7f7f7f7f7f x10: 0000007fb4a8a140 Jul 8 15:18:24 carol kernel: [ 8.581115] x9 : 0000000000000000 x8 : ffffffc0e1cff7b8 Jul 8 15:18:24 carol kernel: [ 8.583390] x7 : 0000000000000000 x6 : ffffffc0f061d1e9 Jul 8 15:18:24 carol kernel: [ 8.585641] x5 : 0000000000000000 x4 : 00000000000055b1 Jul 8 15:18:24 carol kernel: [ 8.587874] x3 : 00000040eee4a000 x2 : ffffff8008219a20 Jul 8 15:18:24 carol kernel: [ 8.590114] x1 : ffffff8008c02140 x0 : 0000000000000000 Jul 8 15:18:24 carol kernel: [ 8.592341] Jul 8 15:18:24 carol kernel: [ 8.592341] PC: 0xffffff80081f26b8: Jul 8 15:18:24 carol kernel: [ 8.596219] 26b8 54fffd60 f940c680 f9001660 b4fffd20 aa1603e1 aa1303e0 940c0a2c 2a0003f6 Jul 8 15:18:24 carol kernel: [ 8.598764] 26d8 35000700 b9405261 d5033bbf f940ca80 b5000320 b50004b7 f9401660 f9402c17 Jul 8 15:18:24 carol kernel: [ 8.601305] 26f8 b5000457 b9405660 370004c0 b9405660 36080100 f9401661 f9400c22 b5000062 Jul 8 15:18:24 carol kernel: [ 8.603883] 2718 f9401421 b4000061 320e0000 b9005660 b9405260 12166c00 b9005260 f9409a60 ... Full kern.log boot log: https://pastebin.com/zcpxB1HQ Please find attached the full armbianmonitor output here: https://pastebin.com/NkVAejC6 Any help is greatly appreciated!

There's an issue with Panfrost and Mesa 19.3 that causes X11 to crash in "OsLookupColor" which you may run into on Armbian on RK3399 devices; it can be solved by enabling the experimental branch in your /etc/apt/sources.list by adding the following line: deb http://deb.debian.org/debian experimental main contrib non-free You can then run 'apt update' and install experimental branch packages with 'apt -t experimental install <package>'. To fix the crash in X11, update the following from experimental: libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0 mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers This should allow X11 to run properly. Thanks to zackw at the Pine64 forums (Original post: https://forum.pine64.org/showthread.php?tid=8915&pid=61701#pid61701 )

Where can I find a link to the source git for What source code are the 5.4.23-rockchip64 kernels from?

We talk about test of different parts. It was orginal one topic but split. The other is https://forum.armbian.com/topic/12936-how-to-control-fan-on-rockpro64 @deathisunknown Which kernel are you using? 5.3.xxx? Until this week end, I was using Ayufan's kernel in order to have ats working (I have the nas box with a harddrive so I want to have some ventilation). I've switched to Armbian's current kernel (5.3.xxx, I don't remember the exact subversion) and noticed that the fan would not spin. Then I tried Armbian's dev kernel (5.4.0-rc1) and my fan works fine. I stumbled upon this thread in the mean time, but since as I remember the latest current kernel got compiled in November, it would not have this change included. On the other hand, I did not call "modprobe" while (quickly) testing the "current" kernel so It could have been there but I missed it...

See https://forum.pine64.org/showthread.php?tid=8685 Using his SPI flash image, and then using armbian-config flash from SPi/system on NVME option worked. I had commented out the set the uboot partition section to what is started booting from lines in boot cmd to do the initial testing. I have been booting mainline for a while on this device. It boots much faster, and two or three weeks agoTobias Schramms atf patch made into mainline atf so the device no longer hangs on a soft reboot. I have booted from sd, emmc and the NVME with this u-boot. I haven't tried usb3 or usb2.

Hello, is booting SPI + NVME supported on RockPro64? If I use armbian-config and installing system SPI + NVME will not boot the system. When using SD (mmc) + NVME is OK. SPI + USB also OK. Thank you for your help.

Hi! I'm using Armbian with Ayufan's 5.3.0rc4 kernel (until ~1 month ago when I decided to freeze the dev kernels, they were not able to expose the pwmon for the fan that I need to keep running to cool my nas case). But I've seen lots of updates flying around about uboot. So I am wondering: are there significant improvements to uboot? I am currently using an old version of uboot on the SPI flash (so it is a little painful to test new version) and I am wondering if I should disable my SPI in order to have uboot on my emmc (to boot off the emmc) or if there is even a newer option to reflash my spi with a newer uboot... Thanks, Mathias PS: so far, every time I've reflashed my SPI with Ayufan's sd-card image, it was very, very slow and I never got any visual feedback so I had to leave it for several hours to be sure it would work

Hello, I'm using a RockPro64 boards inside one of my projects and I just noticed an issue related to the reset process. When pushing the reset button, the boards hangs in a reset loop. Using the oscilloscope, I found that the reset signal (OTP_OUT_H) is toggled every 330ms by the CPU and the only way to get it back to work is to power off the board, wait a few seconds, and power it back. The same issue is found if, after a working boot, a quick power cycle is performed. I tried disconnecting everything from the board but still, when pushing the reset button, the boards hangs in a loop condition (as if it’s constantly crashing at boot). The console doesn’t print anything. I have already written to Pine support but they told me it's an OS related issue. The OS in use is: 1) Linux distribution Armbian 5.90 downloaded from this link: https://dl.armbian.com/rockpro64/archive/Armbian_5.91_Rockpro64_Debian_buster_default_4.4.184_desktop.7z 2) Kernel based on Linux 4.4.182 Thank you

Hi, Greatings for the team. Currently i am using Armbian Bionic Desktop image with my rockpro64. I went through this link for GPU supported libs installation- I can see there are libMali.so files in /usr/lib/aarch... folder. I also installed armnn from this link- https://developer.arm.com/solutions/machine-learning-on-arm/developer-material/how-to-guides/configuring-the-arm-nn-sdk-build-environment-for-tensorflow-lite/build-arm-nn And successfully done and tested. But when i am running on of my tenseflowlite based project, it is throughing error- Loaded model mobilenet_ssd.tflite resolved reporter nn version: 1.0.0 findAvailableDevices filename:libarmnn-driver.so d_info:256608 d_reclen:40s ERROR: The DDK is not compatible with any of the Mali GPUs on the system. The DDK was built for 0x860 r2p0 status range [0..15], but none of the GPUs matched: ##Exception: Could not initialize the CL runtime. Error description: clGetDeviceIDs. CL error code: -6 [E][ArmnnDriver]: ArmnnDriver: Failed to setup CL runtime: Could not initialize the CL runtime. Error description: clGetDeviceIDs. CL error code: -6. Device will be unavailable. [D][ArmnnDriver]: Register Service: armnn (version: 1.0.0)! [ERROR]: IDevice::getCapabilities returned the error DEVICE_UNAVAILABLE first invoked time: 488.432 ms Please suggest any solution related to this Mali GPUs issue. Will appreciate your help. Thanks.

Hi all experts, This is a serious issue for me as for one of the project i am using more than 20 numbers of rockpro64. I have installed them in my different locations of office. I have used two types of OS- *) LXDE-ubuntu-0.7.9-1067-arm64 *) bionic-containers-rockpro64-0.8.3-1141-arm64 Issue is- Whenever i flash these images to rockpro64, for some days autoboot works well such as if light goes and comes back then machines auto boot itself but after few days, auto boot does not happens with few machines and i have to press the "power button" to boot up. I thought with latest OS this issue will solve but same result with latest OS. Please suggest what can be the exact issue? is it OS related? if yes then why it is not happening in all the machines. Which OS should i use with rockpro64? Note- When i reflash the OS, then again auto boot happanes but again same result after few days. Eagerly waiting for the suggesstions. Thanks

I am running armbian buster Armbian_5.91_Rockpro64_Debian_buster_default_4.4.184_desktop.img. I need rt_preempt in order to run linuxcnc. I started with the 5.0.21.tar.gz kernel source from <https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/> and the rt_preempt patch 5.0.21-rt16.patch.gz from <https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/>. I applied the patch to the kernel source and compiled it on a 4gb RockPro64. It boots fine into a remote terminal using ssh but there is no display on my HDMI monitor. The white LED is showing but the red LED is not lit. I had an earlier version of linux-5.0-rt running on armbian stretch so I mistakenly thought this would be a walk in the park. Any ideas where to start looking? Alan

Hi! I've had for quite a while the following error messages at startup: [ 39.095667] zswap: default zpool zbud not available [ 39.095670] zswap: pool creation failed This has happened with various 5.0, 5.1, 5.2 and now 5.3 kernels. Any idea what I should do to fix it? Mathias

Does anyone have interest in this project? It looks quite promising! https://github.com/andreiw/rk3399-edk2/

Hi, I am using rockpro64 board (based on rk3399 chip). OS- ubuntu18.04 linux. I am building a project that requires Vulkan support for gpu acceleration. Can someone please suggest how can i get vulkan driver for rk3399? Thanks.

Hi! On my RockPro64, I usually run Armbian with Ayufan's 5.1 kernel (it runs very well and after manually compiling the dtb file most of the error messages at startup are gone). I've tried a few days ago to run Armbian's dev kernel (5.0), and both the sdcard and my usb3 attached ssd could not be detected. The network was also missing. I have pasted the output of armbianmonitor -U here. Mathias

5.1.0-1111-ayufan tag. Kernel crash when PCIE card is installed (thus pcie host root complex initialize). Will try previous tags soon, BTW, if anyone successfully run the "mainline" kernel with PCIE cards? [ 161.895780] io scheduler mq-deadline registered [ 161.897340] io scheduler kyber registered [ 161.911264] io scheduler bfq registered [ 162.136905] vcc5v0_host: supplied by vcc5v0_usb [ 162.740884] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 162.746764] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found [ 162.750391] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found [ 163.280713] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 163.284059] rockchip-pcie f8000000.pcie: MEM 0xfa000000..0xfbdfffff -> 0xf0 [ 163.286820] rockchip-pcie f8000000.pcie: IO 0xfbe00000..0xfbefffff -> 0xf0 [ 163.302884] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00 [ 163.305119] pci_bus 0000:00: root bus resource [bus 00-1f] [ 163.306968] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff] [ 163.310027] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus add) [ 163.542130] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reg [ 163.560746] SError Interrupt on CPU5, code 0xbf000002 -- SError [ 163.560932] CPU: 5 PID: 1 Comm: swapper/0 Tainted: G L 5.1.0-3 [ 163.561051] Hardware name: Pine64 RockPro64 (DT) [ 163.561157] pstate: 60000085 (nZCv daIf -PAN -UAO) [ 163.561258] pc : rockchip_pcie_rd_conf+0x1e8/0x280 [ 163.561356] lr : rockchip_pcie_rd_conf+0x214/0x280 [ 163.561440] sp : ffff00001004b7f0 [ 163.561527] x29: ffff00001004b7f0 x28: 0000000000000000 [ 163.561800] x27: 0000000000000000 x26: 0000000000000000 [ 163.562047] x25: 0000000000000004 x24: ffff800004de13c0 [ 163.562275] x23: 0000000000000000 x22: ffff8000f61d6800 [ 163.562499] x21: ffff00001004b894 x20: 0000000000100000 [ 163.562718] x19: 0000000000000000 x18: 0000000000000000 [ 163.562936] x17: 00000000250ca3fe x16: 000000009ae7c865 [ 163.563154] x15: ffffffffffffffff x14: ffff00001153d6c8 [ 163.563374] x13: ffff8000ec3df91c x12: ffff8000ec3df190 [ 163.563592] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f [ 163.563811] x9 : ff72646268756463 x8 : 00000000000003bd [ 163.564030] x7 : 0000000000000000 x6 : 0000000000000001 [ 163.564248] x5 : ffff00001060f630 x4 : 0000000000000000 [ 163.564466] x3 : 0000000000000000 x2 : 0000000000c00008 [ 163.564686] x1 : ffff000017c00008 x0 : 0000000000000000 [ 163.564961] Kernel panic - not syncing: Asynchronous SError Interrupt [ 163.565098] CPU: 5 PID: 1 Comm: swapper/0 Tainted: G L 5.1.0-3 [ 163.565196] Hardware name: Pine64 RockPro64 (DT) [ 163.565276] Call trace: [ 163.565367] dump_backtrace+0x0/0x168 [ 163.565452] show_stack+0x24/0x30 [ 163.565535] dump_stack+0xac/0xd4 [ 163.565617] panic+0x150/0x2e8 [ 163.565705] __stack_chk_fail+0x0/0x28 [ 163.565798] arm64_serror_panic+0x80/0x8c [ 163.565884] do_serror+0x11c/0x120 [ 163.565968] el1_error+0x84/0xf8 [ 163.566064] rockchip_pcie_rd_conf+0x1e8/0x280 [ 163.566164] pci_bus_read_config_dword+0xb8/0x108 [ 163.566271] pci_bus_generic_read_dev_vendor_id+0x40/0x1b8 [ 163.566368] pci_bus_read_dev_vendor_id+0x58/0x88 [ 163.566464] pci_scan_single_device+0x84/0xf8 [ 163.566556] pci_scan_slot+0x44/0x108 [ 163.566653] pci_scan_child_bus_extend+0x5c/0x350 [ 163.566749] pci_scan_bridge_extend+0x37c/0x518 [ 163.566849] pci_scan_child_bus_extend+0x204/0x350 [ 163.566945] pci_scan_root_bus_bridge+0x60/0xd0 [ 163.567042] rockchip_pcie_probe+0x5ec/0x718 [ 163.567135] platform_drv_probe+0x58/0xa8 [ 163.567223] really_probe+0x1f0/0x3d8

Dear all, I'm running latest Armbian Bionic on Pine64 RockPro64, trying to connect a Midi Keyboard device (having several of them for testing), but it is not recognized by ALSA. If I run acconnect -l After connecting the keyboard, it's not listed (same behavior with different keyboards). Does anyone possibly knows what module might be missing in the kernel? Thanks..

Hi, I got my RockPro64 board several days ago, and got *UPSTREAM* kernel (v5.1-rc5) and uboot (v2019.04) running on it using Archlinux ARM. (Sorry guys, I like upstream and Alarm more) The pull request for uboot-rockpro64 can be found here: https://github.com/archlinuxarm/PKGBUILDs/pull/1691 The upstream kernel is in the official core repor of Archlinuxarm (and that's why I like Alarm so much). It boots and runs mostly OK on full upstream kernel/u-boot setup. On rc-kernel it even has HDMI output working, but no hardware acceleration. I'm waiting panfrost as the open-source driver, so far it doesn't matter much as I don't plan to use it with X11/wayland anyway. But it's awesome that you can just run GNOME3 on wayland, using llvmpipe. And I even compiled mesa with panfrost natively on that board, so the future looks super bright. However the biggest problem I hit is, upstream (5.0.8 and 5.1-rc5) kernel has random panic. The panic itself is Async SError, and mostly happens for memory heavy operations (memtester and heavy file operations like checking out the whole kernel code). The last panic I hit has no meaningful kernel calltrace, just el0_error_naked (user space triggered, and memtester is running) At first I thought it's faulty ram, but when using the rockchip kernel from Armbian, it no longer crashes any more. I have no clue what's going wrong, device tree? idbloader? trust.img? Uboot? Or just upstream kernel sucks? (I really hate to admit the last one) Is there any upstream kernel precompiled in armbian for me to test so I could rule out one more problem? Thanks.

I prepared (last weekend? - don't remember anymore) a first step towards a merge of rk3399 (currently nanopi boards) with rockchip64 (more or less all the rest) so that both can be covered fully under one boardfamily (rockchip64). Patches are adjusted and dts support for nanopis in ayufans kernel is done as well. https://github.com/chwe17/build/tree/rk3399merge I would happily give it into 'someone others' hands cause time in the next month might be really rare. Basically it needs testing on the boards which got newly merged into rockchip64 (don't own any nanopi *4 board so I can't test it). And probably a small helper script to adjust the 'living' boards config so that they'll get updates in the future from their new boardfamily (this might be tricky and needs for sure a lot of testing, to ensure we don't break them) Would be nice if someone can review it and test it on the nanopis

Hello. I wanted preempt-rt kernel for my armbian rockpro64 so i have compiled and generated preempt-rt 4.4.167 deb kernel package. I have installed my custom kernel deb package but after reboot the system boot in old kernel not the custom kernel. How i can set the system to boot from custom installed kernel ?(4.4.167-rt176 is my custom kernel) $ ls -a /boot . boot.cmd dtb-4.4.174-rockchip64 System.map-4.4.174-rockchip64 .. boot-desktop.png Image uInitrd armbianEnv.txt boot.scr initrd.img-4.4.167-rt176 uInitrd-4.4.167-rt176 armbianEnv.txt.out config-4.4.167-rt176 initrd.img-4.4.174-rockchip64 uInitrd-4.4.174-rockchip64 armbian_first_run.txt.template config-4.4.174-rockchip64 .next vmlinuz-4.4.167-rt176 boot.bmp dtb System.map-4.4.167-rt176 vmlinuz-4.4.174-rockchip64

While running the debian stretch desktop, I'm able to set my scroll direction in the mouse/touchpad manager but only certain programs respond to the changes. The file manager and leafpad do but chromium and the terminal window don't. Anyone know anything about this?

I am using this image https://dl.armbian.com/rockpro64/nightly/Armbian_5.82.190422_Rockpro64_Debian_stretch_dev_5.0.0.7z Board start only without wifi & pcie. But i got this error. https://pastebin.com/gq2DpXaF

Hi so there is a wip for RockPro64 but Kernel development and some other builds like MrFixIt have made gr8 advancement. Wondering if you could start support for rp64 or maybe update the wip since kernel has greatly improved.