Search the Community

Hi, I received my new rock64 today and I downloaded this image https://dl.armbian.com/rock64/Debian_stretch_default_desktop.7z I used Etcher as recommended to create the SD card and booted off of it with just power and network connected as I assumed it would boot, assign a dhcp address and bring up sshd so I could remote onto it. I scanned my network to see if any new devices had been added with dhcp, but couldn't see anything new so I connected the rock64 up to a TV and then booted it up, connected up a keyboard and noticed it ran through an install process on first local login. I followed all the directions and a desktop appeared on screen. However, there was no network connectivity so I had a look at /etc/network/interfaces and could see that nothing at all had been set for eth0. Only the loopback interface was defined. I manually edited /etc/network/interfaces and added my eth0 static IP config in there and rebooted and the eth0 network came up as expected. source /etc/network/interfaces.d/* # Network is managed by Network manager auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet static address 10.0.0.42/24 gateway 10.0.0.2 dns-nameservers 10.0.0.2 Is this expected behaviour for the rock64 Debian image? In that, you have to manually configure eth0 after running through the install process or is this a bug? Thanks very much for your help and for maintaining a distribution for the rock64.

Trying to choose between an eMMC module or a USB Flash drive for the boot volume on a Rock64. I have a few Rock64's that I'm building as various services (Nextcloud, Pi-Hole, VPN, OMV, and/or Netatalk Backup). None of these devices will need large boot volumes as the data will be in secondary (Hard or SSD) Drives or will require VERY little data storage. On the RPi's that the Rock64's are replacing, I've been using USB Flash drives for booting. I get the feeling that an eMMC module is a better choice, but do have any real knowledge. Are the eMMC modules more reliable and less prone to corruption that USB Flash Drives? I do have some 32GB and 64GB eMMC models from Pine64 and am going to try them out shortly. Any thoughts and advice? Thank you all in advance. Armbian ROCKS!

I'm building a portable battery powered NAS because syncing and having everything multiple times on all my Android devices sucks. I took my old Banana Pi connected a SSD to the SATA port and made it a access point (no Samba yet installed). Booting from the 16GB SanDisk Ultra A1 is 27 seconds. Moving everything to the SSD in armbian config is also 27 seconds (no difference?) I know the Banana has not the fastest SATA and NIC and that USB 3 on the Rock64 is faster. But i don't copy tons of gigabyte to the device everyday and for streaming over the WiFi stick it's fast enough. I'm interested on the boot time of the Rock64 (eMMC or USB/SSD). If its not much faster then i see no reason to by a Rock64 for that. Also the Banana has the advantage that you can solder a battery to it.

Hello, Each time I'm booting the Rock64, it starts on Jan, 21 of 2016 but the filesystem has a superblock on Jan,28 of 2018, so in the future. It's inconsistant and the filesystem is checking each time and I'm waiting a few seconds. How can I avoid this trouble ? Here is the screen shot of logs through the tty/usb console. I'm booting from the spi flash and a sd-card with Ubuntu 18.04.1.

I'm trying to switch the upper USB port to peripheral mode so I can use the ethernet gadget on it. Has anyone done anything like that before? I've got an issue here https://github.com/ayufan-rock64/linux-build/issues/117 with some of the things I've tried already.

Good evening, I have a Rock64/4G board and just downloaded and installed the Armbian_5.42_Rock64_Debian_stretch_default_4.4.124_desktop.7z to the SD card. After the reboot I saw X11 login interface and everything was great. After that I installed the latest packages with an apt update and then apt upgrade and restarted. Now I only see "rock64 login:" on the screen. The Xorg.0.log I have attached looks actually quite good. Xorg.0.log

I'm trying to get wifi working on my Rock64 running the nightly server image. Is this possible?

rock64 rk3328 orange pi one Can the rock64 rk3328 run several programs simultaneously? Browse internet with little latency? When I tested orange pi one youtube would stutter. Thank you.

New user of a Rock64 board, I've tinkered with a RaspberryPi and BeagleBone before but wanted something to set up as a home media server. I flashed the SD card with an "Armbian_5.42_Rock64_Ubuntu_xenial_default_4.4.124" image and it worked perfectly fine at home, connecting to my network, etc. However, I took it to a new location and it straight up refuses to boot. I've tried it on several displays and with several HDMI cables. It hangs for a solid 30-45 seconds after initiating boot with a black HDMI screen, and then turns off and back on dumping a log citing either spinup shutdown errors or a temperature shutdown on Core 0. I've flashed a separate SD card with the same image as well as the stretch image off the main Armbian page and both of them work for a short while but then proceed to crash seemingly without change ~24 hours later. Is there a large chance my board is simply intermittently dead or is the Rock64 known for being extremely picky with HDMI cables/monitors at boot? Edit: Got it home to my original setup and I have no dice there. I'm at a loss - everything seems to work perfectly with the board after flashing but only for a day or so, then it gets stuck on boot. At this point I'm keen to put it down as a defective board, I'm not sure what else it would be after trying different images, SD cards, HDMI cables, and monitors.

I do have a setup: 2.5" disks connected to the powered USB 3.0 hub. The power adapter is 10A. If I do start rsync copy from one disk to another after a while I'm getting the error: rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] All disks disappired. There is no way to return them back, only reboot helps. In dmesg I could find that device jsut stopped and disappired: [ 2342.927583] usb 5-1.1: USB disconnect, device number 3 [ 2342.931057] usb 4-1: USB disconnect, device number 2 [ 2342.931975] usb 5-1: USB disconnect, device number 2 [ 2345.629932] usb 5-1.3: USB disconnect, device number 4 [ 2345.663838] usb 5-1.4: USB disconnect, device number 5 [ 2342.904003] xhci-hcd xhci-hcd.9.auto: xHCI host not responding to stop endpoint command. [ 2342.904016] xhci-hcd xhci-hcd.9.auto: Assuming host is dying, halting host. [ 2342.927380] xhci-hcd xhci-hcd.9.auto: Host not halted after 16000 microseconds. [ 2342.927400] xhci-hcd xhci-hcd.9.auto: Non-responsive xHCI host is not halting. [ 2342.927416] xhci-hcd xhci-hcd.9.auto: Completing active URBs anyway. [ 2342.927502] xhci-hcd xhci-hcd.9.auto: HC died; cleaning up [ 2342.927543] xhci-hcd xhci-hcd.9.auto: xHCI host not responding to stop endpoint command. [ 2342.927552] xhci-hcd xhci-hcd.9.auto: Assuming host is dying, halting host. [ 2342.930928] xhci-hcd xhci-hcd.9.auto: HC died; cleaning up Any ideas? How to find the reason of this crash?

I'm trying to use it with a TV that has HDMI input but it's 1360x766. xrandr says it's running at 1920x1080. It's very small, like keep a magnifying glass handy, and I don't have the bottom of the screen where LXDE puts the pager and buttons. I thought from my Raspberry Pi experience that I'd just change the mode in my config.txt https://www.raspberrypi.org/documentation/configuration/config-txt/video.md but apparently the Rock64 isn't that evolved. Can I set an HDMI mode in my armbianEnv.txt? Can it use CVT modes? The standard 1360x768 mode isn't quite right. I've been around this stuff since you had to work out an xfree86.conf file on paper and take timings into account but that was with CRT monitors where the resolution didn't have to exactly match LCD resolutions. Where do I change it? I have a couple monitors that a Pi's EDID parser doesn't work right on either, which is OK as long as there's a way to set the mode manually. FWIW this is an Axess TVD-1801 a couple years old. The PDF I just grabbed says 1366x768, something else said 766 vertically.

Hey fellow tinkerers, I'm pretty happy with my Rock64 boards so far, however, when I recently upgraded the kernel on the oldest one and rebooted, I couldn't ssh back in. So I hooked it up to a monitor and was blown away from all the error-like text that kept flowing on my screen. Since I have if this is logged anywhere (I looked but couldn't find anything after mounting the sdcard in my laptop), I had to film it. See attached video. It basically consists of lots of errors formatted like this: [<ffffffxxxxxxxxxx>] and a lot of errors looking like this: dma-pl330 ff1f0000.dmac: pl330_update:1783 Unexpected! Is there any way to salvage this? Eg, tinker with some boot file? Or should I just be done with it and reinstall the entire system? Is it board-related aka is my board done and needs to be replaced? System info: Rock64 with 4GB RAM, running Armbian Ubuntu 16.04. Has been working solid before the kernel upgrade and reboot. VID_20180617_094424_1_1.mp4

Hi, I'm unable to get my Rock64 to boot either the Xenial or Stretch Armbian images from SD or Emmc. I can get all of the other OS's to boot fine off of either media. Ive tried with multiple Emmc chips, SD cards and Rock64's with the same results so its not the hardware. Seems like it cant find the boot loader. Ive used win32diskimager, Etcher and the Rock64 instakk software. I've formatted the SD card completely, used new SD cards... I'm stuck! Any suggestions Thanks!

Is there a guide somewhere how to enable 1wire support on a rock64 using stretch or xenial. Im trying to read a dallas DS18b20 sensor. I see some examples for other boards but cant figure out how to apply them to the Rock64. Thanks

Has anyone here tested the Rock64 successfully with an u-boot version which is not the one from ayufan? I did not have much luck with the rk3328 default config and mainline u-boot when I tried it a while back. The same is true when I tried to use the board config from ayufan with mainline u-boot. The version by ayufan is working in principle but also is rather dated as far as I know and therefore does not support some newer features. Anyone knows if the version from ayufan will be bumped or has a working config for a more recent u-boot version?

Hello, I need some help to find an U-Boot image to flash on rock64 so that armbian boots directly from USB3. Where can I find it. If your answer is to build my own U-Boot image, please give me step by step instructions. Thanks a lot

I got the Rock64 specifically for router-like functionality. In addition to the native ethernet port, I've added two USB3 RTL8153 Gigabit adapters: http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=56&Level=5&Conn=4&ProdID=326 I've tried multiple 0.5.x and 0.6.x Ayufan images, and also Stretch armbian here (which also uses the Ayufan kernel). I've tried both the 4.4 kernel all these distros come with, and up to 4.17 as well. In all cases I see terrible and unreliable USB3/USB2 and ethernet performance. In the Armbian Sketch image I see 'eth1' go up and down contstantly: Jun 17 09:48:44 localhost avahi-daemon[712]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::e824:33dd:2309:841c. Jun 17 09:48:44 localhost avahi-daemon[712]: New relevant interface eth1.IPv6 for mDNS. Jun 17 09:48:44 localhost avahi-daemon[712]: Registering new address record for fe80::e824:33dd:2309:841c on eth1.*. Jun 17 09:48:45 localhost kernel: [ 249.804881] Rockchip integrated EPHY stmmac-1:00: rockchip_integrated_phy_fixup_100M: reset phy Jun 17 09:48:47 localhost kernel: [ 251.863022] rk_gmac-dwmac ff550000.ethernet eth1: Link is Down Jun 17 09:48:48 localhost kernel: [ 252.865169] rk_gmac-dwmac ff550000.ethernet eth1: Link is Up - 100Mbps/Half - flow con8:48 localhost NetworkManager[708]: <info> [1529228928.6344] deort 67 interval 5 Jun 17 09:48:56 localhost systemd[1]: Starte00: rockchip_integrated_phy_fixup_100M: reset phy Jun 17 09:49:04 localhost kernel: [ 268.951741] rk_gmac-dwmac ff550000.ethernet eth1: Link is Down Jun 17 09:49:05 localhost kernel: [ 269.953899] rk_gmac-dwmac ff550000.ethernet eth1: Link is Up - 100Mbps/Half - flow control off Jun 17 09:49:05 localhost NetworkManager[708]: <info> [1529228945.7255] device (eth1): link connected Jun 17 09:49:07 localhost dhclient[3157]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21 Jun 17 09:49:19 localhost kernel: [ 283.986689] Rockchip integrated EPHY stmmac-1:00: rockchip_integrated_phy_fixup_100M: reset phy Jun 17 09:49:21 localhost kernel: [ 286.046267] rk_gmac-dwmac ff550000.ethernet eth1: Link is Down Jun 17 09:49:22 localhost kernel: [ 287.048219] rk_gmac-dwmac ff550000.ethernet eth1: Link is Up - 100Mbps/Half - flow control off Jun 17 09:49:22 localhost NetworkManager[708]: <info> [1529228962.8166] device (eth1): link connected Jun 17 09:49:27 localhost NetworkManager[708]: <warn> [1529228967.8545] dhcp4 (eth1): request timed out Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.8553] dhcp4 (eth1): state changed unknown -> timeout Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.8724] dhcp4 (eth1): canceled DHCP transaction, DHCP client pid 3157 Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.8728] dhcp4 (eth1): state changed timeout -> done Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.8792] device (eth1): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Jun 17 09:49:27 localhost NetworkManager[708]: <warn> [1529228967.8834] device (eth1): Activation: failed for connection 'Wired connection 2' Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.8915] device (eth1): state change: failed -> disconnected (reason 'none') [120 30 0] Jun 17 09:49:27 localhost avahi-daemon[712]: Withdrawing address record for fe80::e824:33dd:2309:841c on eth1. Jun 17 09:49:27 localhost avahi-daemon[712]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::e824:33dd:2309:841c. Jun 17 09:49:27 localhost avahi-daemon[712]: Interface eth1.IPv6 no longer relevant for mDNS. Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.9290] policy: auto-activating connection 'Wired connection 2' Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.9487] device (eth1): Activation: starting connection 'Wired connection 2' (2f03db29-a92b-3782-86d7-64b613f8e9d0) Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.9530] device (eth1): state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.9630] device (eth1): state change: prepare -> config (reason 'none') [40 50 0] Jun 17 09:49:27 localhost NetworkManager[708]: <info> [1529228967.9829] device (eth1): state change: config -> ip-config (reason 'none') [50 70 0] Jun 17 09:49:28 localhost NetworkManager[708]: <info> [1529228967.9949] dhcp4 (eth1): activation: beginning transaction (timeout in 45 seconds) Jun 17 09:49:28 localhost NetworkManager[708]: <info> [1529228968.0254] dhcp4 (eth1): dhclient started with pid 3425 Jun 17 09:49:28 localhost dhclient[3425]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 I've read now multiple reports of these issues. See: * https://github.com/ayufan-rock64/linux-build/issues/112#issuecomment-397817650 * https://forum.pine64.org/showthread.php?tid=5557 What I can't find is how to resolve this? It seems Rock64 don't actually support this board properly, and just rely on Ayufan.

/usr/lib/dri/rockchip_dri.so just doesn't exist but not really sure if the xorg package is the xenial one or rockchip one. If it is the rockchip one then for some reason rockchip_dri.so isn't being built. On a startx it gives it a good go but always drops out to software rendering because its missing the above.

Debian Stretch and Nextcloud 13.0.2 Image available for testing at https://ownyourbits.com/downloads Initial testing shows no problems other that some small adjustments that need to be made for all armbian images: static IP and mDNS. More testing is welcome and feedback appreciated! Cheers, Nacho

Hello, I was able to overclock the CPU to 1.488Ghz by editing rk3328-rock64.dtb file. But I can not figure out how to set the RAM-clock-speed. Is there any chance to ramp up the RAM clock?

Hello, I have been able to run the rock64 testing image posted in https://www.armbian.com/rock64/ I want to customize this image through userpatches/customize-image.sh, as I have done in the past with the odroid HC1. The plan is to create more SD card images with NextCloudPi As a first step, I want to replicate that testing image, that works for me. Following Igor's advice in this post, I tried with the following command ./compile.sh docker \ BOARD=rock64\ BRANCH=default\ KERNEL_ONLY=no\ KERNEL_CONFIGURE=no\ RELEASE=stretch\ BUILD_DESKTOP=no\ EXPERT=yes I was asked a few questions regarding kernel configuration ( see attached file ). Seems like defconf doesn't cover all options. I tried the defaults and the resulting image doesn't boot. What am I missing in order to replicate said working test image? Thanks! rockbuild.txt

Hello. Please could someone help me to solve this issue? I have a wifi dongle recognized as: Bus 002 Device 002: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter I am trying to use it on my Rock64 and ARMBIAN 5.42 testing Debian GNU/Linux 9 (stretch) 4.4.124-rk3328 uname -a: Linux rock64 4.4.124-rk3328 #24 SMP Wed Mar 28 17:15:52 CEST 2018 aarch64 GNU/Linux It seems it is recognized correctly: Using Network Manager had no luck, the device was always listed as disconnected. So I tried to configure it manually in /etc/network/interfaces, adding this entry: auto wlx441ca87f7a19 iface wlx441ca87f7a19 inet dhcp wpa-ssid mySSID wpa-psk [key removed] Still no luck, this is the log of networking service: I also tried to add: options rt2800usb nohwcrypt=y in /etc/modprobe.d/rt2800usb.conf, as I read somewhere and removed and reloaded the modules, no change Trying the scan manually I get no results: wlx441ca87f7a19 IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off sudo iwlist wlx441ca87f7a19 scan wlx441ca87f7a19 No scan results I also connected the module to my laptop (running Ubuntu 17.10) to be sure it works, and from there I can connect to my wifi just fine (using Network Manager). I also can connect to wifi using another usb adapter (Realtek 8188EU USB) on Rock64 with Network Manager. Any idea? Thanks in advance.

I tried the stable Arabian image for rock 64 and found out that full HD video is played with strong brakes, when playing HEVC image is missing How to force video to be reproduced normally, maybe I don't understand something ?

The xenial img from dl.armbian.com works fine, but doesn't have SCTP support, so I wanted to compile my own image. Did a "show kernel config" and built an img. When I boot: In LPDDR3 786MHz Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB ddrconfig:7 OUT Boot1 Release Time: 2017-05-18, version: 2.43 ChipType = 0x11, 128 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=29820MB FwPartOffset=2000 , 2000 SdmmcInit=0 2 StorageInit ok = 267624 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 LoadTrustBL No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x97af0 RunBL31 0x10000 ␁NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 11:37:09, May 4 2018 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using rkfiq sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2018.01-rc2-armbian (May 04 2018 - 13:03:35 -0400) Model: Pine64 Rock64 DRAM: 4 GiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 Card did not respond to voltage select! mmc_init: -95, time 9 *** Warning - No block device, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2923 bytes read in 29 ms (97.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 215 bytes read in 23 ms (8.8 KiB/s) ## Error: Can't overwrite "ethaddr" himport_r: can't insert "ethaddr=02:38:a0:82:2d:c0" into hash table ## Error: Can't overwrite "eth1addr" himport_r: can't insert "eth1addr=02:38:a0:82:2e:c1" into hash table 5420341 bytes read in 707 ms (7.3 MiB/s) 11837952 bytes read in 1491 ms (7.6 MiB/s) 33587 bytes read in 41 ms (799.8 KiB/s) ** File not found /boot/dtb/rockchip/overlay/rk3328-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 5420277 Bytes = 5.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to fc9e4000, end fcf0f4f5 ... OK reserving fdt memory region: addr=1f00000 size=6e000 Loading Device Tree to 00000000fc973000, end 00000000fc9e3fff ... OK Starting kernel ...

Hello, I want to try out Armbian OS as opposed to Ubuntu Artful 17.10 on my Rock64, mainly to see how it compares(I am aware Armbian minimal for Rock64 is derived from Ubuntu Xenial, but I understand it's optimized for ARM CPUs) Long story short, I have a 32GB eMMC and a eMMC to USB adapter from Pine64 and would like to run Rock64 Armbian off it, but I was unable to simply flash Armbian to it using 'dd' or Etcher as with ayufan's Ubuntu images. I am aware it's possible to boot from an microSD card and use the "nand-sata-install" bash script to achieve this as described in the Armbian documentation, so I am inquiring if I can bypass using the microSD card. * I want to know if it's possible to flash Ubuntu Xenial 16.04 on my eMMC, mount it in my Rock64 and attempt to an build Armbian image, which I can later copy to a separate storage media and flash to my eMMC card. If this is indeed achievable, I will share the Armbian eMMC rock64 image for all to enjoy. Regards,