Search the Community

Hi, i'm new to armbian and i hope to write in the right place I have a rock64 and deployed it as a remote server. Since it is in a shared place, to better protect my and my user's privacy i enabled Full Disk Encryption (CRYPTROOT_ENABLE). Now, back to the question: is usb otg enabled by default? Can someone with physical access use an otg cable to read files from the rock64? I would try it by myself but i don't have physical access to the board. OS: Armbian 19.11.4 Bionic (5.4.28-rockchip64) Thanks

EDIT: Just realized I posted this in the bug tracker forum. My apologies! See:

Hello , i downloaded the latest Armbian Bionic for Rock64 (RK3288) but it would not boot with HDMI-to-VGA adapter. The same adapter boots happily if i use the Bionic Desktop image with Legacy Kernel 4.4 Do i need to add something to ArmbianEnv.txt? Thanks

Hello, can someone help me with my problem. I have a ROCK64 with 4GB of RAM and an ARMBIAN 5.75 stable Ubuntu 18.04.2 LTS 4.4.174-rockchip64, installed. My issue come with usb ports, from the three USB of the this device only works two: one 2.0 and 3.0. And when i have a disk connected towards usb 3.0 i have issues with port usb 2.0, it doesn't work well and I end up disconnecting the USB 3.0 to can work with my device connected towards USB 2.0 so I assume that the current power on the USB port is having issues or it's not working well. Anybody an idea? thanks!

The strangest thing happened today. I switched of my rok64 rev.2 and connected to my PC to move the files of my USB HDD. My plan was to change the disk format from NTFS to EXT4. Then when i plugged it back in the rock64 wouldn't boot properly. Turns out my USB 3 port isn't working anymore with the USB HDD or any other USB drive. The light comes on for my SSD but fdisk -l doesn't see it. Could one of the firmware updates broken it? UPDATE... I downloaded the latest Ayufun arm64 bionic build and booted from this. My USB 3 HDD was picked up fine. I've gone back to the new Armbian Bionic build and it doesn't work. Only on USB 2 ports. Something must have changed with the latest build (u-boot / firmware) that's caused this issue. If you need some logs, please let me know... Will need a hand with the commands to run.

Hi guys, I have recently bought a Rock64 to improve the performance of my VPN gateway. First tests look very promising as you can see here: root@rock64:~# openssl speed -evp aes-128-cbc -elapsed You have chosen to measure elapsed time instead of user CPU time. Doing aes-128-cbc for 3s on 16 size blocks: 15394610 aes-128-cbc's in 2.99s Doing aes-128-cbc for 3s on 64 size blocks: 12591175 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 6719021 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 2448108 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 352617 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 16384 size blocks: 177668 aes-128-cbc's in 3.00s OpenSSL 1.1.1d 10 Sep 2019 built on: Sat Oct 12 19:56:43 2019 UTC options:bn(64,64) rc4(char) des(int) aes(partial) blowfish(ptr) compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-H2OJIf/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 82379.18k 268611.73k 573356.46k 835620.86k 962879.49k 970304.17k root@rock64:~# openvpn --genkey --secret /tmp/secret root@rock64:~# time openvpn --test-crypto --secret /tmp/secret --verb 0 --tun-mtu 20000 --cipher aes-256-cbc Sat Dec 14 10:26:40 2019 disabling NCP mode (--ncp-disable) because not in P2MP client or server mode real 0m4.978s user 0m4.945s sys 0m0.032s Unfortunately when executing a simple curl, the throughput is very low: root@rock64:~# curl -L https://speed.hetzner.de/1GB.bin > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 2 1000M 2 29.9M 0 0 2090k 0 0:08:09 0:00:14 0:07:55 3106k When using Ubuntu 18.04 Bionic I am reaching speeds of 8,4MByte/s. I have checked the openvpn process and it seems that it is only using 25% of CPU, whereas when using in Ubuntu it is using 50-60%. What are the differences here and why is Armbian limiting the process to 25%? Thanks! Bye

I have a 4G Rev 2 Rock64 that is running like a champ on current - 5.4.2 as of this writing, as far as USB and Ethernet are concerned. I did have to blacklist UAS for all my USB drives, and now the board is rock solid even with heavy disk and network IO. I do have one problem though, I have no sound. I have the following loaded (automatically): root@chdock:/home/sugata# cat /proc/modules |grep snd snd_soc_rk3328 16384 0 - Live 0xffff800008dc9000 And yet, I get this: root@chdock:/home/sugata# aplay -l aplay: device_list:272: no soundcards found... I searched around this forum and nothing obvious came up. Any ideas?

I am running last stable armbian with kernel 4.4.192-rockchip64 on emmc - really everything works nice (only thunderbird is very slow) - thx a lot for your work. The only thing I could not figure out, how I can wake up from suspend by keyboard or mouse. The armbian image uses org.freedesktop.login1.suspend to suspend - normally I am used to upower or pm-utils and there it was until now all the time possible to wake up with keyboard. Its quite uncomfortable to wake up the Rock64 with the power button - hidden, very small hole, I just use now a wooden chopstick for wakeup. Does anybody know, how to configure wakeup-hooks / wakeup-events for systemd / logind.

serial terminal this unit was booting fine one day and then not the next. it will boot to the serial terminal but not far enough for ssh or even a functional ethernet. this is running on a rock64 w/16GB eMMC. nothing else is really unique about it.

Hi, I have armbian image with kernel 4.4.184-rockchip64. Now I want to connect with Wifi using commands but I dont know how to connect using commands. I am able to connect with WiFi using Graphical tool. Below are my observations: a) Instead of wlan0, p2p0 interface is used to connect with wireless network. b) I am able to scan with wlan0 using below command: iw dev wlan0 scan c) iw dev p2p0 scan gives output associated interface( the one connected using Graphical Tool). d) I created wpa_supplicant.conf file and executing below command shows wpa_supplicant initialized but does not get IP address. wpa_supplicant -Dnl0211 -iwlan0 -c/etc/wpa_supplicant.conf -B Can anyone please tell me how to connect to any network without using Graphical tool. In my case p2p0 interface is used for Wireless Connection instead of wlan0 interface.

Hey guys, I installed Armbian some months ago in my Rock64 and I had never updated the packages. Yesterday I decided to do an apt update + apt upgrade to update one of the applications I use. I noticed that meanwhile apt updated Armbian itself, and began to ask for a reboot. A few hours later I rebooted the board. At first I couldn't connect due to connection refusal, so I went plugged a keyboard and hdmi on the board to see what was happening. It looks like while doing this I unplugged the power source suddenly, and now the board won't boot the system in this OS. No image or response in the USB keyboard. I thought it could be SD corruption, but I'm able to open the SD card in my Desktop and see its contents. Since I had a lot of tweaking in the old system, is there a way to copy some parts of a new image and paste in the SD, so I can boot it again? Or maybe reflash the SD with the latest armbian, then pasting some folders over it (maybe home and /var/lib at least)? Thanks for the advices.

Hello, I have a Rock64 V2 which I am using as a Tvheadend server, among other stuff. For some months I put the kernel/dtb packages on hold, because I discovered that linux-image-rockchip64 after version 5.75 did not include the kernel module for th USB DVB-T stick I need (an EyeTV DVB-T device, i.e. a clone of Hauppauge), that is dvb-usb-dib0700 or the like (I am trying to remember). I have recently unhold the Linux packages and let apt to update them. Now at version 5.90, I see that the kernel module is still not included, and my USB device cannot be used. Going back to Linux image 5.75 makes the stick to work again, but I'd like to have the latest versions running. Questions: 1) Am I missing an extra package? 2) How can I get back on driver? (Well, a third one would be why it has been removed from the latest versions) Thanks!

Hi everybody, I recently set up a small server with the Rock64 booting armbian stretch 5.59 stable directly from a 120 GB SSD attached via USB3. Booting is handled with U-Boot from ayufan on the SPI flash. The Rock64 is board revision 2.0, the power supply is the original Pine64 one for the Rock. Besides the SSD, there are no other peripherals connected. The board often (3 out of 4 times) hangs when booting. In this case, all LEDs are lit, the orange network LED will flash and the board is not reachable by SSH and not pingable. My impression is, that it is stuck because the SSD either powered up too late or the USB connection is delayed. However, I cannot confirm my suspicion, because the board also does not output any HDMI signal to my monitor (even if it boots up correctly). If I cut power, re-power and give it another try, it will boot at some point and everything (except the HDMI) will work perfectly. My issue seems to identical to the one described here for the ayufan build. It is noted in that thread, that an external power supply for the SSD might mitigate the problem. I did not have a chance to test this, yet. But I also hope that you guys have a better insight into this and might catch a bug in the armbian image.

I have the Rock64 4G Version with emmc module Since the latest Kernel Update two weeks ago on friday the board does not boot up anymore. (I was on Stretch initially and updated regularly since.) Even with a newly flashed sd card and without emmc module the board will not but into armbian. I managed to boot into raspbian buster 5.91 once, but after rebooting it, it failed again and stayed that way. until now I have tried the latest 3 images. The Kernel is now 4.4182 and is unchanged whatever I do. with any armbian on an sd card i am getting: Failed to start armbian zram config - failed to start journal service Failed to flush Journal to Persitent Storage rockchip64 #6 and at some point the boot sequence stops with something like: work_pending+0x10/0x14 or I am getting consistent timeouts from "waiting for device" with the original emmc card it gives me: ... BUG: spinlock bad magic on CPU#2 goes to: secondary_start_kernel +0x190/0xbc 0x2cxa188 repeats and stops there also since the beginning I sometimes get: "fixing recursive fault. Reboot is needed!" - without reboot improving anything of course.. I am afraid that at this point of failure notices and kernel panics I have no idea how to proceed anymore.

The newest revision does not boot from current SD images. I'm working to debug why. If anyone else has a board and can test it out, let me know. The eMMC will boot, no problem, so it's just the SD itself. Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b50303930343200000000051f1a serial=f55c6806c317581 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device ** No partition table - mmc 1 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: Core Release: 3.10a USB3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning bus 3 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT Ideally getting old an new to boot would be ideal, @Igor this might mean a fragmentation for this board though, like having a V2 and older and a V3 and newer build if we can't make them all play nice with one bootloader.

I have a C++ app that wants to indicate its activity by blinking an LED on the Rock64. How can the LEDs be controlled? The sysfs leds do not appear to be present. I'm okay with libgpiod or sysfs gpios, but I don't know what gpio numbers represent the LEDs. Anyone know? Thanks. Linux rocky64 5.0.0-rockchip64 #5.85 SMP Wed May 8 19:38:28 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic

Can anyone recommend a usb adapter that works with Armbian on Rock64 wifi access point/hotspot. I tried a few I had but none work as access point. Thanks

I just purchased a 4GB Rock64. I've tried both the Ubuntu (Armbian Bionic Desktop 4.4.y) and Debian (Armbian Stretch Desktop 4.4.y) distros. I'm finding that the Debian distro is very sluggish compared to the Ubuntu distro. The desktop is sluggish in responding to mouse clicks and in Chromium, a basic web page takes about 3 seconds to display compared to about 1 second with Ubuntu. Is this the same performance difference that other people are finding with these distros on the Rock64? Is there some configuration tweak I need to make to improve Debian performance? Is there another distro that I should check out that would give me better performance?

How do you control which PHY the Rock64 is going to use? Android 9 is available for Rock64 now, https://github.com/a9rock64/manifests But it is configured to use the internal PHY and I need to change it over to the external one. Is this controlled in the DTS or someplace else? It is running on this kernel: https://github.com/rockchip-linux/kernel

Hi, my rock64 (rev2) with the latest build of Armbian randomly looses its network connection. I couldn't use the armbianmonitor -u as it had no network connection, but when i use ifconfig, I can see it's still got it's settings and is the NIC lights are on. ifconfig showed 6 TX errors. My NIC is set to DHCP with static reserved IP address to an ASUS router. I leave it on 24/7 and check it once a while as it pretty much is used as a NAS with a single USB 3 drive. This morning I connected up via HDMI and a USB keyboard and logged in successfully. I don't have much Linux experience so wasn't sure how to capture the logs to SD card so i could copy them up here later. The NIC dropouts occur about once a week at random days and times. I have tried use ifup and ifdown to try and re-enable the NIC, but when I did this I got a stack dump and I couldn't enter any further commands into Ubuntu. Next time the NIC fails, what command(s) should I use? I've had this issue before on the later ayufun arm64 ubuntu builds too. I see the kernel has been updated to v5 over at ayufun's github, maybe there are some code changes that might help. I did read that dropping the MTU down from 1500 to 1492 might help, but don't really want to make random changes. Any suggestions much appreciated.

My armbian-config went missing. I know it was there before, but apparently somehow I deleted it. "find / -mount -type f -name armbian-config" gets no hits. Is there a package I can refresh to get it back? Thanks.

Hi all! I'm having strange issue with Rock64. I downloaded latest Armbian 5.88 with 4.4.180 kernel. Installation and boot are ok, but when I try to do apt-get install lvm2 Package installs, configures and... update-initramfs: Generating /boot/initrd.img-4.4.180-rockchip64 update-initramfs: Converting to u-boot format Then I do root@rock64:~# sudo reboot And I'm getting a boot loop... Same effect, if I move system to SSD. At first I thought it was issue with ssd transferred system... But it clearly reproduced on freshly written with uSD only boot. I've dumped armbianmonitor output (just in case) on freshly flashed OS. MicroSD is old 2GB one (I'm planning to use SSD drive and use uSD only for boot). But same effect on other cards. Another one issue (which I probably can live with, but you may find this interesting). I install hostapd-rt along with using rtl8188eu dongle. Hostapd starts, but here are two points: Everything works with android It fails to authenticate with MacOS... But weirdest thing here - when I stop hostapd with systemctl, then start - it shows "Oops, SMP error" and reboots. Still not sure about revision (not v3 definately Thanks in advance for looking into it.

I have a ROCK64 4GB Rev. 2. When I flash armbian to a SD card the board will boot fine and I can do basically anything for example apt-get update / upgrade. The board runs fine and stable for several hours. But as soon as I reboot the board, the board will stop booting. There is no HDMI output and no ping response. Even after disconnecting power for several hours. Right now there is no way for me to get it to boot again except for flashing the fresh image to the SD-card. I‘ve tried several SD-cards. I am using the original 5 V 3 A PSU. There is nothing connected to the board except for ethernet and power. Anyone got an idea?

I have some bose speakers plugged into the A/V and i am getting no sound. does this feature work on the POCK 64? or is audio only through HDMI. my monitor has no audio support.

Hey guys, I heard that the USB3 port of the Rock64 outputs up to 950mA. I have this external HD (WD My Passport), one of those 2,5'' external HDDs that are powered solely by the USB3 port. From what I've gathered, this should need no more than 650mA. But it doesn't work on the Rock64. After mounting the thing, if I try to write and read, it just disconnects with a bunch of dmesg errors. It makes a little click sound after the spinning builds up. Looks like there's not enough energy (it works fine on my desktop). How can I check and monitor the voltage and current delivered by the USB3.0 on the Rock64? My power supply is kind of generic, even though it says 5V 3A. The rpi shows a lightning icon right, but the Rock64 doesn't, so I can't be sure the power supply is at fault.