Search the Community

I've got jammy running but I have a dsi display for the board and I'd like that to work (well the tp port too) with jammy. Looking at armbian config I see no setting for it. I know the display works fine as if I load an aryufan android image it works as it is set to use DSI by default. Does this kernel know about the DSI port? Do I have to build a custom kernel? If not then what boot env line will get it going?

Hello, I've installed the 22.11 version with the 5.15 kernel on the microSD card. I've a rockpro64 with the SSD adapter and a WD black 250GB nvme. The system doesn't recognizes this drive. I've tested the latest stable ayufan image (kernel 4.4) and it recognises it perfectly. Should I downgrade the kernel to the 4.4 branch? Any help would be appreciated. Thanks,

Dear Armbian community, Yesterday morning, after apt upgrade my Rockpro64 not boot (the white and red led stayed lit). After some tries I managed to get a boot again but I now have a "init not found" error, as you can see on the screenshot. What have been done so far : - Install an Ubuntu as "debug" platform - Follow the recovery steps from Armbian website - Put on eMMC storage a 5.15.63 by copying the files from Armbian - Check if UUID was consistent between partition, boot config, ... ==> this is the case - Made a fsck : no errors found ==> I would like to try this : https://askubuntu.com/questions/910218/sbin-init-no-such-file-or-directory-not-able-to-boot-ubuntu-desktop, but need to have a boot prompt (how to get it ?) If somebody has any other hint... I would take it I have spent hours on the setup of my Rockpro64, I would avoid to reinstall it. Regards.

is it possible to get edp on rockpro64 working with armbian

Hi all, I am a newbie here. Is there a way to install ZFS on RockPro64 RK3399 with the latest Armbian release (doesn't matter if it is bionic, buster or focal)?

Hi guys I have experienced a lot of system instability with the rockpro64 on debian and armbian as explained here: https://forum.pine64.org/showthread.php?tid=17083 and here: https://github.com/monero-project/monero/issues/8473 I think the solution lies in what the guys are discussing here: https://forum.pine64.org/showthread.php?tid=7387 Can someone please give me a clear set of instructions on how to create an image to boot with with lowered ddr clock frequency? Presumably from the files listed here?: https://github.com/rockchip-linux/rkbin/tree/master/bin/rk33 i.e.: files such as rk3399pro_ddr_666MHz_v1.27.bin rk3399pro_miniloader_v1.26.bin Thanks!

Im looking for a functioning, easy to install fan script for my RockPro64 installed with Armbian Jammy. Iv searched around and found a few unmaintained projects but Its not something iv ever done before so wanted to ask what others use. Although I do have some experience in the terminal I'm still relatively new to it so im hoping there is something with good step by step documentation. If anyone can assist Id be appreciative. Many thanks.

I'm trying to get this rockpro64 board to boot off of pxe/nfs. I'm able to get it to boot into armbian and to the point where it asks for the new root password. But something happens on the device where the network gets disabled which stops the NFS connectivity and the rest of the system with it. All traffic stops on the device and it becomes unreachable. NFS traffic stops, it no longer responds to pings, etc. It's not entirely frozen, for example it prints kernel messages to console if the ethernet is pulled. And after a few minutes the nfs connection times out and it starts printing this over and over. It always happens about 75 seconds after boot. It leads me to think there's some job or process that's running on the base OS install that somehow interrupts the connection. this is the pxe config file I'm using. and I'm using the current bullseye server image from Aug 31, 2022 default l0 menu title U-Boot menu prompt 0 timeout 50 label 10 menu default kernel root/boot/Image fdt root/boot/dtb/rockchip/rk3399-rockpro64.dtb initrd root/boot/uInitrd append loglevel=8 root=/dev/nfs ip=dhcp rootwait rw earlyprintk nfsroot=192.168.116.1:/rockpro64/root

Hi everyone. I’ve been facing some issues with my RockPro64 lately, running on a dedicated version of Ambian for this sbc. Earlier, I was using a USB Bluetooth module with it for playing audio on my speakers (via Logitech Bluetooth adapter), and it worked perfectly fine. I wanted to save some USB ports so I decided to replace the module with a ROCKPro64 1*1 Dual Band WIFI 802.11 AC/BLUETOOTH 5.0 MODULE. But ever since I’ve done that, the audio quality is choppy and inconsistent. Receiver and transmitter are located closely, so I don’t think it’s a signal issue. It seems like a hardware or a software issue, but I’m not sure what could it be. I’d appreciate any help with troubleshooting or diagnostics. Thanks in anticipation!

Hi, Has anyone tried compiling zfs? According to google it should work out of the box? However, when I try to install, zfs dkms is saying that the module will not be compiled due to missing kernel headers. Fine, but where are the headers? I'm using a fresh install from https://www.armbian.com/rockpro64/ armbian-config - Software - headers_install does nothing, installing linux-headers-current-rockchip64 installs 22.05.4, not 22.08.1 that I have, and "compiling headers", whatever that might be, fails how do I get a matching kernel and headers, any version? root@rockpro64:~# dpkg -l | fgrep rockchip ii linux-dtb-current-rockchip64 22.08.1 arm64 Armbian Linux DTB, version 5.15.63-rockchip64 current ii linux-image-current-rockchip64 22.08.1 arm64 Linux kernel, armbian version 5.15.63-rockchip64 current root@rockpro64:~# apt upgrade -y linux-headers-current-rockchip64 Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-current-rockchip64 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 12.1 MB of archives. After this operation, 80.2 MB of additional disk space will be used. Get:1 http://armbian.hosthatch.com/apt jammy/main arm64 linux-headers-current-rockchip64 arm64 22.05.4 [12.1 MB] Fetched 12.1 MB in 2s (6,470 kB/s) Selecting previously unselected package linux-headers-current-rockchip64. (Reading database ... 42002 files and directories currently installed.) Preparing to unpack .../linux-headers-current-rockchip64_22.05.4_arm64.deb ... Unpacking linux-headers-current-rockchip64 (22.05.4) ... Setting up linux-headers-current-rockchip64 (22.05.4) ... Compiling headers - please wait ... scripts/sign-file.c: In function ‘display_openssl_errors’: scripts/sign-file.c:89:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 89 | while ((e = ERR_get_error_line(&file, &line))) { | ^~~~~

I am able to boot and install with an sd card, but am unable to get through first boot with the image on an emmc card. The failure on the emmc card is between /scripts/local-premount and /scripts/local-block it fails with gave up waiting for root file system device ... alert! UUID=ed78b... does not exist. dropping to shell! and I am at a busybox shell in (intramfs) I was wondering if booting from the emmc card was expected to work, or if anyone could remember what needs to be tweaked for the kernel to find the root filesystem on the emmc card. Cheers

I've tried the latest CLI and GUI images. I tried different microSD cards but the result is the same. Both images get to Booting using the fdt blob and never progress. Is there anything I can try to get this working?

Only "chirps and chips" come through during extended playback. Only hdmisound device is affected, not analog. Duplicate of improperly "resolved" thread Armbian 22.02 Bullseye Kernel 5.15.25-rockchip64 Armbian 22.02 Bullseye Kernel 5.16.16-rockchip64 working in 5.10.60-rockchip64 steps to reproduce: aplay -D plughw:1,0 /usr/share/sounds/alsa/Front_Right.wav dmesg | grep es83 [ 10.077582] es8316 1-0011: Failed to get IRQ 0: -22 card 0: Analog [Analog], device 0: ff890000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0

I have installed clean CLi option of Armbian_21.08.1_Rockpro64_focal_current_5.10.60.img from the archives I have fully apt updated/upgrade OS and now am at 5.15.25-rockchip64 I noticed there was no sound coming out of the HMDI only from 3.5mm Jack Alsamixer has: (volume bar with up/down instead of 1 increments jumps 0>28>56>100 - I d like to fix this) Pulsemixer (CLi) solved my problem by simply while playing an audio stream/file I swapped (made default the bottom Built-in Audio Stereo) Also on Cards tab (use tab to move keys F1-F3 didnt work for me neither on Tinker nor here) i have. Sound now comes out of HDMI fine. Jack I swap back to top option I guess

In Alsamixer its missing the master volume. In older legacy images it was there and driver seemed to be a tinker rockchip driver? Any idea how to enable the master volume slider? If I increase volume in USB sound card (headphones) then no sound comes out at HDMI and only way to restore is to purge deb of pulseaudio and alsa and re-install. There are some errors also the moment i log into cli if I do above. If reproduced ill post here (update). Similar error posted on another topic/board If i test `aplay /usr/share/sounds/alsa/Front_Center.wav` its ok. After any change to alsamixer nothing comes out The errors that started after changing alsamixer volume as per above are:

Hello, using the image provided at https://www.armbian.com/rockpro64/ the board works when booted via uSD card but not via MMC. There appears to be no device mode USB drivers installed. I pulled the kernel sources with `armbian-config` and compiled them myself making sure to select dual-mode support for the DWC2 and DWC3 drivers. The kernel boots after install, but I still see nothing in /sys/class/udc and am unable to see any dwc2/3 drivers (save dwc2_pci and some dwc3 i3c drivers). I'm able to load libcomposite, the configfs driver, but that does not pull in a USB device mode driver. I'm unable to attach armbian monitor status right now but will update my post with it.

Hi, I have had some issues trying to boot from eMMC with the last version of Armbian (kernel v5.4) while it's working perfectly on Armbian with a v4.4 kernel. Images not working: https://dl.armbian.com/rockpro64/archive/Armbian_20.05.2_Rockpro64_bionic_current_5.4.43.img.xz https://dl.armbian.com/rockpro64/archive/Armbian_20.05.4_Rockpro64_focal_current_5.4.46.img.xz Working image: https://dl.armbian.com/_old/rockpro64/archive/Armbian_5.98_Rockpro64_Debian_buster_default_4.4.192.7z I though I messed up with the SPI or the eMMC card but after trying all I could, it finally worked using an old version of Armbian. The new images are working on a SD-Card but it's much slower to boot. On a eMMC card it get completely stuck (see attached file), I managed to get the "Done" displayed waiting much longer (just after the "Running /scripts/local-premount" step but nothing more). The CPU is becoming super hot while it stuck. I have the same issue on two different RockPro64 cards and with two different eMMC cards. I have tried the "Disable SPI while booting" step but it didn't help: https://wiki.pine64.org/index.php/ROCKPro64#Disable_SPI_.28while_booting.29 It would be great if I could have a kernel 5.4 running on eMMC on those cards, please let me know if I can help. Kind regards, Baptiste

I was trying to enable i2c on my RockPro64, and when looking at the documentation in the overlay directory, it states this: rockchip (Rockchip) ### Provided overlays: - i2c7, i2c8, pcie-gen2, spi-spidev, uart4, w1-gpio ### Overlay details: ### i2c7 Activates TWI/I2C bus 7 I2C7 pins (SCL, SDA): GPIO2-B0, GPIO2-A7 GPIO1-C5, GPIO1-C4 ### i2c8 Activates TWI/I2C bus 8 I2C8 pins (SCL, SDA): GPIO1-C5, GPIO1-C4 Note that the "GPIO1-C5, GPIO1-C4" from i2c8 is accidentally included on the i2c7 pins line. I would submit a PR for this change, but ... I'm not sure where this document actually lives, and it's not easy to figure out. I see that @Igor is listed as the maintainer of the package, but that's not helping me find the source to submit changes. Also, for clarity, it would be nice to include that i2c8 is the pi-connector, and i2c7 is the Digital Video Port Happy to submit changes if somebody can point me to the right place. Thanks

Hi, I am looking at investing in a RockPro64 NAS setup using the Pine64 Desktop casing and other necessary accessories. I'm hoping to run OpenMediaVault on it and have 2 3.5" HDDs attached. The entire setup would be configured to be a backup of my operational NAS (Helios4) in a different location (i.e. different room of the house). My reading of the forum and the armbian download section has me a bit confused. The download section indicates that the board is supported, but the forum indicates it's a WIP. Just trying to understand the status/stability of the board for what I'm planning on using it for and whether it would be a good investment or a waste of money. Also wondering whether this post regarding updating the CPU governor is related - and will be a benefit - to the RockPro64 as both the NanoPi M4 and RockPro64 share the same SoC RK3399. Thanks

U need ixgbe to run my Intel X550T 10G Ethernet NIC. That module seems to be a part of linux-modules-$(uname -r) package. My kernel version is 5.10.60-rockchip64. However, I do not have linux-modules-5.10.60-rockchip64 available via apt. # apt install linux-modules-$(uname -r) Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-modules-5.10.60-rockchip64 E: Couldn't find any package by glob 'linux-modules-5.10.60-rockchip64' I have apt downloaded linux-modules of some greater kernel release to make sure it provides ixgbe.ko. It does: # apt install --download-only linux-modules-5.11.0-40-generic # dpkg --contents /var/cache/apt/archives/linux-modules-5.11.0-40-generic_5.11.0-40.44~20.04.2_arm64.deb | grep ixgbe drwxr-xr-x root/root 0 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbe/ -rw-r--r-- root/root 665577 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko drwxr-xr-x root/root 0 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbevf/ -rw-r--r-- root/root 148153 2021-10-26 15:50 ./lib/modules/5.11.0-40-generic/kernel/drivers/net/ethernet/intel/ixgbevf/ixgbevf.ko How do I get ixgbe for my actual kernel? Thanks, - Aleksandr

Hello, I installed Armbian Hirsute xfce bleeding edge kernel 5.13.y on my RockPro64 4GB and updated it right after that. After restarting after the update, ethernet doesn't work anymore. (Wifi connecting icon is shown and no connection to ethernet) dsmesg says that the link is up. armbianmonitor: https://paste.ubuntu.com/p/9Yz8SJVrzS/ apt/history.log: https://paste.ubuntu.com/p/GQbfZp3Xch/ For apt history only the last two operations seem relevant. I assume the previous ones are made by whoever/whatever created the image.

Hi, I'm not sure if it is a bug as by board seems to work correctly, however I thought I should post it. In the latest version (5.10.60-rockchip64) I'm getting a few errors in dmesg: debugfs: Directory 'power-domain' with parent 'pm_genpd' already present! I hadn't seen these errors in the previous version (5.10.43) Logs are here: http://ix.io/3yY5 Regards,

After last apt upgrade (v21.05.4), lightdm on a RockPro64 does not start anymore. rockpro64:~:# systemctl status lightdm.service ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-06-20 16:13:01 CEST; 21min ago Docs: manlightdm(1) Process: 1877 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Process: 1880 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 1880 (code=exited, status=1/FAILURE) Jun 20 16:13:01 rockpro64 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. Jun 20 16:13:01 rockpro64 systemd[1]: Stopped Light Display Manager. Jun 20 16:13:01 rockpro64 systemd[1]: lightdm.service: Start request repeated too quickly. Jun 20 16:13:01 rockpro64 systemd[1]: lightdm.service: Failed with result 'exit-code'. Jun 20 16:13:01 rockpro64 systemd[1]: Failed to start Light Display Manager. and trying to start manually as root rockpro64:~:# systemctl start lightdm.service Job for lightdm.service failed because the control process exited with error code. See "systemctl status lightdm.service" and "journalctl -xe" for details. rockpro64:~:# journalctl -xe Jun 20 16:36:33 rockpro64 systemd[1]: Failed to start Light Display Manager. -- Subject: A start job for unit lightdm.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit lightdm.service has finished with a failure. -- -- The job identifier is 1583 and the job result is failed. Jun 20 16:36:33 rockpro64 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Automatic restarting of the unit lightdm.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jun 20 16:36:33 rockpro64 systemd[1]: Stopped Light Display Manager. -- Subject: A stop job for unit lightdm.service has finished -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A stop job for unit lightdm.service has finished. -- -- The job identifier is 1648 and the job result is done. Jun 20 16:36:33 rockpro64 systemd[1]: lightdm.service: Start request repeated too quickly. Jun 20 16:36:33 rockpro64 systemd[1]: lightdm.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit lightdm.service has entered the 'failed' state with result 'exit-code'. Jun 20 16:36:33 rockpro64 systemd[1]: Failed to start Light Display Manager. -- Subject: A start job for unit lightdm.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit lightdm.service has finished with a failure. -- -- The job identifier is 1648 and the job result is failed. running lightdm as root with debug enabled rockpro64:~:# lightdm --debug [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=3791 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /root/.local/share/flatpak/exports/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-slick-greeter.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/11-armbian.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.19s] DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs? [+0.20s] DEBUG: Monitoring logind for seats [+0.20s] DEBUG: New seat added from logind: seat0 [+0.20s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.20s] DEBUG: Seat seat0: Starting [+0.20s] DEBUG: Seat seat0: Creating greeter session [+0.20s] DEBUG: Seat seat0: Failed to find session configuration slick-greeter [+0.20s] DEBUG: Seat seat0: Failed to create greeter session [+0.20s] DEBUG: Failed to start seat: seat0 Any ideas how to drill further down the problem?

Hey folks... We are trying to use a DHT22 sensor on rockpro64 using armbian (buster)... Is there something we need to know about GPIO pin ? We are trying to compile and use this code as a starter... https://github.com/ayufan-pine64/dht22-pine64.git But we got a segfault when using it... thanks

Hi everyone, I tried the 20.11.3 version of Armbian, I have manually updated the SPI with U-boot using armbian-config (after an apt update && apt upgrade), but it doesn't start from a PCIe NVME SSD :-/ Is there something that I have missed? Any idea is more than welcome ! Here is my serial - USB console output: Kind regards, Baptiste