Search the Community

I was wondering if there is a solution to boot from a USB thumb drive and flash the OS to an eMMC. Currently I´m running ARMbian on a Rock64 with an eMMC module installed. Since I´m still trying to figure out how to set up the device I keep reinstalling the OS. So it would be nice to have a way without opening the case, take out the eMMC, hook it up to the PC to flash and reinserting. Thanks in advance.

From the media script thread: Chromium is unusable right now. I'm having to use Firefox. EDIT1: I ran the media-script .sh and it auto installed the default selection and I also ticked "streaming" which I know is Chromium... EDIT2: I'm on the latest Chromium for Ubuntu bionic... 73.x EDIT3: This is what Chromium says under "chrome://gpu": What am I doing wrong? es2_info: and glxgears:

I have seen many problems with the Rock64 v3 in the last few days. Many customers have told me that existing Rock64 images suddenly no longer boot in v3. We have verified this and found that apparently v3 can not cope with many SD cards. The booting of eMMC goes without problems. If a customer has bought a new v3 and nothing works, contact us, we will send you an emmc card for the purchase price without any profit. markus@humberg.de

Hey all! Finally got my Rock64 booted up and running. I set up a Samba server and a Plex share so I can access an attached USB3 RAID array as a media server. Initially I was getting speeds of ~3 MB/s write and attributed it to transferring over wifi with an ancient Airport Express Draft-N router. Upgraded to a Netgear R7000P and the issue still persists so I figured it would be worth it to post here. I would've attributed it to the USB3 to eSata converter going to the RAID array but doing some disk speed tests on the Rock64 shows it getting about 130 MB/s read/write speed over the connection so I doubt it's that. Samba setup is stock and my share described below. " read only = no create mask = 0777 directory mask = 0777 follow symlinks = yes wide links = yes browsable = yes " My Rock64 boots up saying it's running 5.65 stable Ubuntu 18.04.1 LTS 4.4.162-rockchip64

Hi all. In download section i do see "large heatsink required" for Rock64. Can anyone post any links to eamples of good heatsink with proper size ? I will be migrating "home server" from Cubieboard2 to Rock64 and chasing long-term stable operation. When board just booted and "does nothing", cpu remains pretty cool. However i'd better be prepared. thanks in advance for tips.

Hi, I've built the Ubuntu 18.04 image with legacy kernel (4.4) and tried to install wireguard. The problem was the kernel module which seems to be build by dkms. I've installed kernel headers from the linux-headers-rk3328_5.44_arm64.deb (built by armbian's build procedure) and tried to install wireguard-dkms package. It fails: Unpacking wireguard-dkms (0.0.20180513-wg1~bionic) over (0.0.20180513-wg1~bionic) ... Setting up wireguard-dkms (0.0.20180513-wg1~bionic) ... Loading new wireguard-0.0.20180513 DKMS files... Building for 4.4.131-rk3328 Building initial module for 4.4.131-rk3328 Error! Bad return status for module build on kernel: 4.4.131-rk3328 (aarch64) Consult /var/lib/dkms/wireguard/0.0.20180513/build/make.log for more information. The content of make.log DKMS make.log for wireguard-0.0.20180513 for kernel 4.4.131-rk3328 (aarch64) Thu May 17 21:24:11 UTC 2018 make: Entering directory '/usr/src/linux-headers-4.4.131-rk3328' Makefile:643: arch//Makefile: No such file or directory make: *** No rule to make target 'arch//Makefile'. Stop. make: Leaving directory '/usr/src/linux-headers-4.4.131-rk3328' The line 643 is include arch/$(SRCARCH)/Makefile so SRCARCH is not set for some reason. Any suggestions how to fix it? Also I've tired to build wireguard module manually with dkms and/or from source. In both cases it fails because of absent scripts/recordmcount. I've tried to build that stuff with 'make scripts' in the /usr/src/linux-headers-4.4.131-rk3328 and this fails too: HOSTCC scripts/selinux/genheaders/genheaders scripts/selinux/genheaders/genheaders.c:13:10: fatal error: classmap.h: No such file or directory #include "classmap.h" This classmap.h exists in the kernel source tree, but was not included into kernel-headers deb. Do I need to fix something in kernel makefiles?

Hi, Is it possible to boot from SSD? How it should be partitioned? Can I use any arbitrary partition for rootfs? Should I follow the procedure from this thread ? It assumes I should write the armbian image to a whole drive instead of partition, right? Well, I actually tried some way... First, I've tried to just run some utility from ambian-config that transfers rootfs to a partition. Device did not boot after this (with SD card ejected). Then I've flashed the ayufan's u-boot-flash-spi-rock64.img.xz. This also fails (boot log is attached) but the log looks promising. BTW, I'm experimenting with Ubuntu 18.04 image built by myself from armbian's development branch. Should I use 16.04 instead? Does armbian have its own image/procedure to place uboot into SPI? Just in case here is the drive partitioning (fdisk log from Linux PC): Disk /dev/sde: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: dos Disk identifier: 0x22138112 Device Boot Start End Sectors Size Id Type /dev/sde1 2048 119769087 119767040 57.1G 83 Linux /dev/sde2 156354560 488396799 332042240 158.3G 83 Linux /dev/sde3 * 119769088 156354559 36585472 17.5G 83 Linux Partition table entries are not in disk order. And I'm trying to use third partition for rootfs. This partition was actually created after shrinking partition 1 in the freed space. Drive is attached to USB3. minicom.cap

I am so frustrated with my rock64 (SoC RK3328), there is no support. Pine 64 takes the money and dumps all the issues on a community. The product is a lemon. Can’t watch YouTube, there is no audio I am very disappointed in Pine64, I will try and return this device.

Hello I built a new kernel for my rock64, how do I install it so I can boot on it I am trying to go from 4.4.174 to 4.14.106

Hi. I have problem with Rock64 and ICYBOX IB-RD2253-U31 (USB3.1 Raid Enclosure) Kernel: Linux rock64 4.4.167-rockchip64 #3 SMP Sat Jan 12 18:58:23 CET 2019 aarch64 GNU/Linux dmesg on ICYBOX connected: [ 3.112348] usb 1-1: New USB device found, idVendor=1234, idProduct=5678 [ 3.112362] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 3.112368] usb 1-1: Product: ASM1352R-Safe [ 3.112374] usb 1-1: Manufacturer: Asmedia [ 3.112379] usb 1-1: SerialNumber: 123412341249 [ 3.113303] input: Asmedia ASM1352R-Safe as /devices/platform/ff580000.usb/usb1/1-1/1-1:1.0/input/input1 Rock64#lsusb -v -t -d 1234:5678 /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usbtouchscreen, 480M As you can see Mass Storage uses Driver=usbtouchscreen and I can't change it using udev mapping ACTION=="add", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="5678", RUN+="/sbin/modprobe uas" RUN+="/bin/sh -c 'echo 1234 5678 > /sys/bus/usb/drivers/uas/new_id'" After udev: rock64:~# lsusb -v -t -d 1234:5678 /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usbtouchscreen, 480M On Debian9 x86_64 and RaspberryPi 2, ICYBOX work perfectly. Any ideas why it doesn't work on Rock64?

When plugging in a RTL8153 gigabit ethernet adaptor, it shows up when using lsusb, however there is no driver found for it. I also went to the Realtek website and tried to compile the proper drivers for it, however, the Make process always fails. Do you have any suggestions as to how to get this to work? The adaptor says it is supported on the Armbian website. Thanks!

I'm trying to run the example.cpp that comes with Pine64-CPP but I am throwing segmentation faults. The man-setup() call initialzes the board with the following if statement in the setup() function in gpio.cpp if((uint64_t)gpio_mem % PAGE_SIZE) and the this->gpioMap = statement that uses SUNXI_GPIO_BASE In the example code, I initialize the pin with man->pinMode (PI_GPIO_24, OUTPUT); The pinMode function in gpio.cpp, launches _setPullupdn with gpio=78 and pud = 1. As expected Inside _setPullupdn, the following is set bank= 2 index = 0 offset = 28 The segmentation fault seems to come from this line: regval = *(&pio->PULL[0] + index); I have a 4 GB Rock64 running the latest Armbian desktop from this site. sudo cat /sys/kernel/debug/gpio gives me GPIOs 0-31, platform/pinctrl, gpio0: gpio-0 ( |vcc_host_5v ) out hi gpio-2 ( |? ) out lo gpio-30 ( |vcc_sd ) out lo GPIOs 32-63, platform/pinctrl, gpio1: gpio-50 ( |mdio-reset ) out hi GPIOs 64-95, platform/pinctrl, gpio2: GPIOs 96-127, platform/pinctrl, gpio3: GPIOs 510-511, platform/rk8xx-gpio, rk8xx-gpio, can sleep: gpio-510 ( |? ) out lo gpio-511 ( |? ) out lo Anyone have any thoughts? Thanks.

I see the latest images for the Rock64 are marked as desktop. I am looking for a lightweight server only version. I still have an older server version that I downloaded a while ago, specifically 5.59. If I install 5.59, can I do and apt-get update/apt-get upgrade to get to the latest version? Any issues with that approach? Thanks!

Hi All, Below command works well on my other boards(Intel with Fedora and Ubuntu) $ compton -b --backend xrender This command make windows background transparent so it doesn't hide lower window completely. But same command doesn't work on RK3288/RK3399 board. Any idea what should be done to achieve same. Does anyone have idea if anything customized in x-server related to this?

Hello, I have using "rock64" board. I have installed gstreamer and mpp for rockchip. Can you provide me exact pipeline for gstreamer in which we can use mpp-hardware codec? Thanks and Regards, Kishan Patel.

Hey I'am searching the Linux kernel headers for 4.4.162-rockchip64 only have found the 4.4.152 can any one help me? thanks

Hi everyone, Big fan of debian based distro's. Have six Rock64's and looking for a newer kernel (4.9+) with default Ubuntu modules list. 3 have eMMC cards and 3 using the Pine64 USB->SATA adapter with SSD drives. I have powered usb hub, y cables, etc but am using USB2 without powered hub because it's reliable as is and USB3 boot with any distro power injection seems unreliable. Not too concerned about throughput. Ayufan's release bionic-minimal-rock64-0.7.11-1075-arm64.img.xz with 4.4 is very stable on these. However Ayufan's mainline kernels after 4.4 are stripped right back. I spent a couple days compiling kernels with Ayufan's 4.4 module set and variations merged with Ubuntu etc but never got a stable build happening. So I've been trying out Arch Linux and it was stable with 4.18 but not supported by the tools I want to use (kubespray, other ansible playbooks). I went through a converted a bunch of my Ansible stuff to suit both Ubuntu and Arch but kubespray is a beast and decided too much effort (also they don't want to support Arch if do PR which is fair enough - github issue by someone else). This led me to Armbian. I see there are later kernels here: https://apt.armbian.com/pool/main/l/ Before getting to this I put extracted Armbian_5.65_Rock64_Ubuntu_bionic_default_4.4.162.7z (.img) onto one of the SSD's with `dd`. It booted the first time, but wouldn't boot the second time. Re-`dd`ed the image on there. Any `apt upgrade` or just `reboot` would prevent future boots from happening. Tried downgrading to 5.59 without luck. Eventually got it to boot again but not sure what was different, then tried updating kernels and all was fine. Tried dd back to 5.65 and stuck again. Keep getting various crashes even after dd image again. Have tried powered USB for SSD's as well even though not needed with ayufan bionic build. Having a go at building new img now with the dev kernel to see if that will boot more reliably. The docs are great, thanks for all the hard work on this, I know the SBC manufacturers don't make it easy to get all these devices going and well supported by mainline. Any suggestions would be most welcome.

On Rock64, I use youtube-dl CLI app.to download the video (720p) during my off-peak bandwidth time, and watch with MPV or VLC later in fullscreen (1920x1080). It plays OK, but this drives the temperature up to 89-92 ! This is a monitor of the results: http://davekimble.net/problem.video.replay.txt . I think the dropped frames are because of 25 fps v 60 fps of the monitor. I know it is a lot of work, but any ideas for reducing the workload welcome. Anybody else get this?

Gentlemen, I have a rock64 board, and I would like to use an external RTC module with DS1307 chip. Unfortunately the armbian kernel does not provide DS1307 driver by default: root@rock64:~# cat /boot/config-4.4.162-rockchip64 | grep DS1307 # CONFIG_RTC_DRV_DS1307 is not set I don't have the programming skills for sending a pull request to enable this module. Could you please enable this module for ROCK64? I believe other ROCK64 owners may also benefit from this driver, as the board does not expose a working RTC, and DS1307 is a very common RTC chip. Thanks in advance.

I have a Rock64 powered by Armbian version 5.60 kernel 4.4.162-rockchip64 Ubuntu Bionic How can I activate i2c0 and i2s0 ports for connecting a 16x2 characters LCD display like 1602LCD and a PCM5102 DAC ? I'm trying armbian-config and I'm reading https://docs.armbian.com/User-Guide_Allwinner_overlays/ but I'm getting no help. Thanks for advance.

So now I am playing with Rock64 4GB. I installed the Armbian_5.65 server edition OS and then installed xorg, lxde, and lxdm., then rebooted into a working system. Final stage of setting up was to test rhythmbox_3.4.2 and there was no sound. pavucontrol > playback shows the app is running and the worm is leaping about, but absolutely no sound. Same playing a .wav file with mpv, or indeed any player. Is there something unusual about the audio socket, or some other limitation. armbianmonitor -u = http://ix.io/ltt0

Hi, the rockchip64 missing the gre modules for ipv4 and ipv6. they had been existing in 4.4.156-rockchip64 /lib/modules/4.4.156-rockchip64/kernel/net/ipv4/gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/ipv4/netfilter/nf_nat_proto_gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/ipv4/ip_gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/netfilter/nf_conntrack_proto_gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/ipv6/ip6_gre.ko is it possible to add these? thx in advance meno

Can someone please help me understand how Armbian for Rock64 is developed? In the past, there was an image for the Rock64 that was a server image, not a desktop image. Now, I see Ubuntu and a Debian Stretch desktop images, no server image. Is there a plan to build a server image going forward? Also, will a newer kernel be built at some point? Not trying to stir the pot or cause trouble, just trying to understand where the Rock64 support is going in the future. Thank you for all the spectacular work the Armbian team does.

Hello. I bought a Rock64 and I have a lot of errors. Im using a eMMC 32GB Storage with Armbian 5.65 stretch 4.4.162 Desktop, Ethernet connection with TP-Link switch, a Wireless Keyboard with touch pad and the original 5V 3A Power Supply. HDMI is connect to a HDMI Splitter/Switch. The Rock64 is placed in the Aluminum casing. Full-Log: http://ix.io/1rce The system is reboot very often before i see the Desktop. Sometimes only after several resets. Can someone help me?

Hello! I've recently installed NextCloudPi, which ships Linux 4.4 by default (linux-image-rockchip64 - Linux kernel, version 4.4.159-rockchip64). Is it OK to update to linux-image-arm64? As far as I understood, mainline Linux supports RK3328 chip since version 4.14. Thanks a lot!