I'm running the ubuntu 18.04 image for the rockpro64. Whenever I try to run a virtual arm host, I always get this no matter what gic_version I use:
libvirtError: internal error: process exited while connecting to monitor: 2019-03-29T01:23:38.158817Z qemu-system-aarch64: -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1: MSI-X is not supported by interrupt controller


I've even tried passing pci=nomsi on the virtual. 

Any advice here? I've done the updates, and am wondering if anyone has suggestions before I build the latest libvirt, virt-tools and qemu.

Hello,

i'll trying since days to boot following image on my Rock64:
Armbian_5.75_Rock64_Debian_stretch_default_4.4.174

Flashed it via etcher without any problem.

As soon as I boot I'll get after one minte a Exception stack ....
Exception Stack

I'm able to flash and boot Ubuntu 18.04 Bionic minimal 32bit Image.
There I have troubles to find/install the WLAN adapter.

I wanted to buil a Home-SIEM with the Rock64 (https://medium.com/@fbotes2/secure-dns-i...faa85bd833)

My Setup:
ROCK64 SINGLE BOARD COMPUTER
DRAM: 4GB 
ROCK64 USB 3.0 Dual Band 1200Mbps WIFI 802.11A/B/G/N/AC (RTL8812AU) Adapter
1 $21.99
32GB CLASS10 MICROSD CARD

Have somebody a clue or hint?

I've installed Ayufan's kernels on Armbian (both 5.0 and 4.20 work great, after fixing a missing link in /boot: uInitrd -> uInitrd-5.0.0-1103-ayufan-g5cdba61f032d).

But I've noticed that cpu-intensive tasks keep moving around the cores as if the operating system has no clue which ones are the big cores and which ones the little ones. I had to run "taskset -p -c 5-6 xxx" to force PID xxx to run on the A72 cores. When I do lscpu, I don't see that there are different classes of cores.
The raid benchmarks (in dmesg, at start of the system) gets results much lower than under Armbian's 4.4.174 kernel, which is consistent with the system running them on A57 cores instead of A72. I'm still using dtb-4.4.174 in /boot, so the kernel can pick the dtb from there.

It seems to have no effect, so I guess, that in Ayufan's kernels the dtb is compiled into the kernel? Has somebody else noticed this?Is there an easy way to use Armbian's DTB (when decompiling Armbian's DTB, it generates a DTS that has much more details than the DTS in Ayufan's kernels)?

Thanks,
Mathias

Hi. I am making I2C test source using Android studio now. But it's very difficult to me...

Can i get I2C sample program with Android 8.1?

Hello,

I have observed that Rock64 supports RTL8723BU WiFi/Bluetooth Module

Hence i would like to know how should i connect the RTL8723BU Chip to Rock64 to get WiFi and Bluetooth Working.

Attached is the Chip Pinout Diagram and their functions i got from the chip manufacturer.

What's clear in my mind: Connect D+ and D- to USB's Data+ and Data- lines, 3.3V and GND to Respective pins of Rock64

I have checked the Technical Reference Manual and Datasheet (Pg.33) for RK3328 and it says that I2S1 supports PCM

But as can be seen in the Pinout, there is SYNC pin as well.

So these are my doubts:
1. Can I connect PCM pins IN, OUT from RTL8723BU to Rock64's I2S1_LRCKTX and I2S1_LRCKRX respectively?
2. To which pins of RTL8723BU should i connect Rock64's I2S1_MCLK and I2S1_SCLK?
3. To which pins of RTL8723BU should i connect Rock64's I2S1_SDI and I2S1_SDO?
4. Where should i connect RTL8723BU's Suspend and WO_WLAN pins

Attached Files

Thumbnail(s)
   

I installed OMV from ayufan
then I want to config the interface from DHCP to static ip. But When I applied after saved it, there is an "networking.service - Raise network interfaces" error occured.
I logged in and input the "hostname -I" command, it print two ip addresses as:
192.168.0.9 192.168.0.100
the first ip is from dhcp, and the second ip is static ip I hope it to be.
and I input "ifconfig eth0", there is only one ip displayed, it is 192.168.0.9.
So I had to change static ip to dhcp again, and the network is ok now.
So, the question is: how can I set static ip for it?

I'm building a NAS with the Rock64 and Openmediavault. To connect an external SSD I read that it is a good idea to get a case with a JMS578 controller.

So I buyed this one:
https://www.inateck.com/fe2005-2-5-withd...osure.html

I connected my SSD with this case. But unfortunately the case only works in USB2 mode. This can be seen from the LED that lights up white for USB2 and blue for USB3. In addition, the performance of the SSD was very bad. 

So this doesn't work.

Can you recommend a 2.5 HDD case for an SSD drive that works well and reliably with the Rock64?

I ran into an interesting problem, I can boot the mrfixit2001 Debian image without any issue but for some reason I am unable to boot up any other image. Even more problematic is that the serial port just does not seem to work at all, I suppose I might have at some point had the USB-Serial set to 5v and blew the UART, only reason I can think why I cannot get anything out of the serial connection, so I cannot really debug the low level boot messages.

My question, does anyone what the config is mrfixit2001 use for the kernel build? Ideally I would like to use Fedora, but I will settle for Bionic until I can figure out why the serial is not working 0 or maybe get a new board...

Any hints would be greatly appreciated

VMan

I'm trying out Ayufan's ARM64 and ARMHF Openmediavault images for the Rock64. Seems the Arm64 has less compatibility issues. I have installed an rtl8723bu driver but it does not see 5G Wifi.  The access points that are 2G are visible but no 5G access point is visible. 

I've tried omv-firstaid but it does not config the wifi card correctly. It's putzed around with nmtui but it also does not correctly config the wifi card.  

Does anyone know how to manually config a usb wifi in Debian / OMV4 on the Rock64 releases?

Just received my RP64, PSU, heatsink w/fan and (2) 64Gb SDHCs.
-- I Flashed Bionoc/LXDE with Etcher.
-- Connected the 12V/5A PSU, GRN power LED illuminates WHT LED illuminates.
-- Pressed power button for 1s, WHT LED turns off, RED LED blinks, and that's that. Nothing.
-- I've used Etcher to flash SDHCs for my Pi 3Bs and Odroid XU4 without any problems.
-- Looks like the SBC is dead.
Q1: Does the fan spin up automatically or is it a PWM fan?
Q2: What to do from here?

TIA,
/Faradn