Are all the USB ports on the rock64 on separate bus. I dont have a rock64, else I could check using lsusb on linux.

I need to connect camera and a sensor on two different USB ports. If they are on the same bus it results to decreased or dropped frames from the camera.

If anyone operating linux on rock64 can give me the output of lsusb command, it would be helpful.

Can almost guarantee this has been discussed and answered, but my searching ability eludes me.

Is there a way to clone the whole SD Card installation onto the eMMC? I would like to install KDE Neon onto my onboard eMMC, but I can't seem to find a version for eMMC installation. A direct clone would be awesome, but I'm happy if there's maybe an imgflash approach.

I can completely understand the issues with the keyboard. But, with a heavy hand or a slight modification it becomes a non-issue.

But does anyone else find the trackpad completely erratic?

Example, I'll try and move the cursor a couple of pixels diagonally. A precise finger movement causes the mouse to do a Torvil-and-Dean-level flick and twist, and end up further away than before.

Other times, I feel like I've suddenly turned into Edward Cullen as the trackpad flat out refuses to react to my touch, especially if you have sweaty hands. I try to use heavier movements, but I end up accidentally dragging my desktop icons into the recycling bin, or the application launcher.

Does anyone else find the trackpad absolutely unusable? I understand that there's no specific driver so it uses a generic PS2 input driver, but daaammmnnn there must be something better?! Currently using either a USB mouse or KDE Connect wireless input mode.

How to install and boot ROCK64 from eMMC? - https://forum.pine64.org/showthread.php?tid=4713
    shows
boot priority:
eMMC--> SPI flash-->  SD card

But, with both eMMC and microSD installed, I am seeing my Rock64 boot to microSD. How can this be?

1. Has the priority of the devices changed generally for the Rock64, or is it just my unit?
2. Does one of the devices boot directly, i.e. not use/require the SPI flash?
3. I found the following.
    Flashing and Erasing the SPI - https://github.com/ayufan-rock64/linux-b...ash-spi.md
Traditionally, booting Linux on the ROCK64 required an eMMC or microSD card, however it is now possible to boot without those, assuming the SPI memory has been flashed. The ROCK64 contains an onboard 128Mbit SPI flash memory, which can be flashed with U-Boot in order to provide additional boot options:
    USB2 / USB3 drive
    PXE
    microSD
    eMMC
Boot order:

1. SPI flash
   
2. eMMC (disable with jumper)
   
3. microSD
   
4. USB drive
   
5. PXE
   

I see that the current board version of rock64 is 1.1 as per rock64_link.

However i have seen youtube videos and images where version 2.0 is printed on top of rock64 board (rock64_youtube link)

I would like to know if version 2.0 is the latest one.

Also where can I find any release notes stating the differences between version 1.1 and version 2.0

       
Found this copper cooler on ebay. Fits nicely except the area around the WIFI/Bluetooth card attaches so had to bend the fins a little bit. But all in all a nice passive cooler. it does have a fan that comes with it but would need connection modification. Just wanted to share this.

Hi,

even though the sopine64 module itself supports PXE boot I read some post that u cant PXE boot all the boards on a clusterboard. Currently you can only boot up to 6 sopines from the 7th.

Another ways is having your independet Linux on each Sopine and update them manually or by some tools like cssh or writing your own scripts..


Am I missing something?

Greetings,
Khaosgrille

Verified in the image ubuntu - lxde

when logout, and login again, seems that the power for pwm is Cut-Off.

• If pwm value is high,
  Fan will continue spinning before stop, and when pwm restored, fan can continue(because it doesn't stopped at all).
  
• But if pwn is low,
  Lets say 35 or 50, when power is cutoff, fan will stop,The power is restored then, but too late...fan already stoped, and it cannot start with a value so low as 35 or lets say 50.
  

Hello.

We ordered four of these, and have tested two of them so far and them seem to be having locking up issue. After about three days of running, the units will freeze up, and need to be rebooted. Will be testing the other two soon. One of the two tested has a CPU heatsink.

Anyone else having issues with that?

Hi, I am new owner of Rock64 4GB powered by genuine 3A psu and storage on Samsung MicroSDHC 32GB EVO Plus UHS-I U1 card.
I will try to share all my findings about this interesting board.
My goal is to achive stable h265 htpc for my old samsung tv.

First of all I was very disappointed how unstable is the stock board. I have tryed Android 7.1 TV, Android 7.1, Bionic minimal linux, Android 8.1, LibreElec and Recalbox. All systems except Android 8.1 and Bionic minimal were randomly freezing or crashing even with heatsinks on cpu and mem.

I have managed to install Kodi 17.6 on Android 8.1, but h265 hd iptv stream was choppy.

Then I reached recalbox installation and was impressed how seamless kodi worked, untill crash.
I suspect overheating to be main problem on my board. Maybe it's bad soldering, design or initial setup. It looks like most systems are crashing above 60'C
I have managed to reach console through ssh and lowered cpu frequency by setting governor to powersave.
Cpu frequency has been reported about 400MHz, I dont remember exact value, and temperature mostly did not exceeded 60'C. 
System was stable for at least 20 minutes and h265 playback was perfect.

I have few questions.

1/ Why the temperatures were so high even on powersave governor (cpu usage was low (top )) ?
2/ Can we lower voltage to cpu, mem and default cpu frequency to lower overheating ?
3/ Is genuine aluminium casing effective against overheating problem ?

Meanwhile I will try to use active cooling and test if my system is stable enough.