I just wondered if anyone was aware of these?

http://my.bitscope.com/store/?p=view&i=product+BR20A

I have one here now, the BB02A blades seem to work just great with the Rock64 with slight modification.

The plastic spacer needs to be either replaced with a slightly longer one or some nylon washers added to give a tiny bit more height.

Hi,

I kave some problems with my new rock64 sbc (4Go, Ubuntu on 16Go eMMC, wifi). Here they are:

1: generally the first starts crash, with the red led on. After few restarts (or/and time of use), i have the impression that the board works better. Perhaps that a required working  temperature is not reached before a given time (?)

2: after the start-up, the board always give the error: Fail to apply network settings. You light not able to connect to bluetooth network via this machine. Exception: org.freedesktop.DBus.Error.Spawn.ExecFailed: fait to execute program org.blueman.Mechanism: Permission denied

3 the highligthing of the menus items are very very slow to follow the mouse cursor

4 taking a screenshot does not work

that's all for now. Someone can help
Regards
Pascal

Reference :
Product page  in Pine64 shop : PINE A64 / PINE H64 / ROCKPro64 ACRYLIC OPEN ENCLOSURE
Product page in the Pine64 shop : ROCKPro64 Heatsink

Does an owner know the M(etric)-size and length of the standoffs/spacers/pillars used in the case ?

From the tech drawing, it looks like the height of the heatsink is 30 mm. But it is blurry. Can an owner please confirm the 30 mm height ?

Cheers.

Hi all, the below link describes how to set up a Tor Relay on the "Pi"
Can this be done to the Pine A64(+) using a similar instruction set?


https://www.linux.com/blog/intro-to-linu...relay-node

I tested 'mele F10' on rock64 with official Android TV 0.3.13 image and it is NOT working. Can anybody confirm this?
Tried connecting dongle on usb2 and usb3 port and using power supply 3A. Still not worked. This classic airmouse works on every other board since the age of cubieboard.

Hello everyone
I need help. how to make cnc motion control by Rock64 with linuxcnc .
Thanks

Hey guys!
 
I need to change a few lines of code in the android kernel. I'm using this build but can't seem to find the kernel sources used to compile it. I tried to compile these sources up to the 3.10.104 merge tag but I get a lot of compilation errors. What gcc version should I be using? And once I compile the kernel how do I flash it to the rock64? Do I just use the compiled Image file as the kernel.img in AndroidTool or do I have to package it somehow?

Thanks!

I have been looking for benchmark results of disks connected through the SATA interface card and the PCIe slot, but haven't seen anything so far. As a matter of fact, I have not seen any news about a working PCIe SATA interface card at all. What I have come across is a solution for a working PCIe NVMe card, but only after removing a resistor. Bullet64 reported the following:

Bullet64 Wrote: Yes, i have remove the resistor on preproduction rockpro64!!!! Please take care, that is not without danger!

My resistor has removed a specialist.

After this on NVMe Card the red LED is ON And the NVMe card works.

On the SATA-Card is an white(?) LED. But this LED isn't ON. So maybe wrong pcie-regulator ???

Hello community!

I have wrote a tutorial how to install OpenBSD on a ROCK64 media board.
The tutorial is on my Github page available:

Tutorial to install OpenBSD


Check it out!

Cheers

krjdev

**Server setup**

Rock 64 4GB
Xenial minimal: Ubuntu 16.04.4 LTS (GNU/Linux 4.4.126-rockchip-ayufan-227 aarch64)

**Problem**

I recently did a full "sudo apt update && sudo apt full-upgrade" (not sure it's related), and had a lot problems since.

My "load average" and core use is recently very high. If I examine using htop, I notice a lot of it is taken up by sabnzbd (which I'm running in a docker container). I used to have a "load average" in use of 2-3, max 4-5 and now it easily gets up to 8-9 when downloading two files.

I also had a bunch of system crashes, which I can't seem to replicate, which I'm now assuming was due to high load.

I'm not sure it's related, but I checked out the kern.log and syslog and saw nothing out of the ordinary, except for an incredible amount of these errors (or similar):