Hello everyone, 

Since I'm totally new to single board computers I have read a lot on the internet, but still have some questions.  Based on the specs, the Pine SBC seems the most interesting to me.  However I've read several posts about long and/or difficult shippings and on top of that the official website informs the potential buyers the shipping time is somewhere between 3 and 9 weeks or even longer.  Therefore I'm worried about this. 

At this point I'm hesitating between purchasing an 'old' Pine A64+ at a local reseller just around the corner or purchasing the 'new' Pine 64 - LTS through the webstore.  This brings me to the question I would like to ask to the forum members: Is it worth waiting an undefined time to get the 'new' LTS-version or should the 'old' A64+ be good enough to be used as simple file server ?  (only a few and small files between max 10 PC's)

Thanks in advance for your replies. 

Kind regards. 

PS: Sorry for my English. I'm dutch.

Hi everyone,

I am using Rock64 and trying to play mp3 files on headphone jack. The playback part is working fine. I having trouble with controlling the volume with amixer command. When I try amixer sset Master 100 it shows me error "Cannot find simple control 'Master',0"

The reason behind the use of amixer is I have ported this application from raspberry pi and I need to keep it consistent on either device. I am using Debian stretch minimal image.
Exact version:

Hey Guys,

I have some problems to pair my BT keyboard.
I am using Debian Jessie with Mate DE [3.10.102 BSP 2] by Lenny Raposo.
My keyboard is a Rapoo e6700. BT is the on Board modul.
My problem is, I can pair the device but a second later it is disconnected.
The keyboard works fine with other devices like iPad oder Galaxy Tab 10.1.

Can someone help me?

Thanks Sebastian

I have read that it is possible to flash u-boot to the SPI flash to have more choice on boot devices. I have also seen a tutorial in the wiki mentioning it. But what I could not find is a detailed description of what is actually going on when u-boot is starting:

* does it look for a certain device type or are all USB mass storage or UBS/SATA bridges supported?
* does it look for a certain position in the USB bus, for example always the first USB storage found anywhere or always only the first port on the first hub?
* does it search all devices and look for a partition with a certain label?

I cannot seem to find any documentation about this u-boot configuration, also generally I cannot find much documentation about the boot process of the Rock64,  for example if the SPI flash is erased, what does it look for if it comes out of reset, is there always a fixed minimal loader in mask ROM somewhere and is it documented? Is it possible to accidentally brick the device?

It would be nice if someone could give a detailed description of the boot process, please describe it as detailed and low level as possible, target audience for this description would be an embedded (cortex M0 and M4) bare metal programmer who has no fear of beginnig to learn about the low level stuff going on during initialization and boot  in the larger ARM processors.

Thank you.

Hi guys,

The performance with Rock64 and Lakka aren't good enough to have a good experience out of the box, I got a better experience with a PI2 and Retropie.
Probably Lakka needs a better tuning so I would like to understand where is the place to get help to solve these issues, I mean here or on the Libretro forum.

Thanks in advance,

Daniel

Please, i need to enable the P5+ header ethernet interface, but the latest ayufan's image have it disabled. How can I re-enable it?

I am trying to install NextCloud on my rock64 but i'm running into a problem.  NextCloud uses snapd to install its packages which is supposed to come with ubuntu 16.04 by default.  It does not appear to be installed on the rock64 xenial image version 0.5.15-136.  I tried installing it manually but it failed because it failed to mount the core.  The error was: "mount[31508]: mount: unknown filesystem type 'squashfs'".  I tried to do an internet search and it mentioned this can be an issue with custom linux kernals.  I wasn't able to find anything more helpful then that though in how to fix the issue.  Does anyone have any suggestions on how to fix this issue?  Also in case the forum manager sees this i might have made this thread on the wrong board earlier for the pine64.  If it did go through please remove it.

Hello.

I have some issue with setup remote connection to VNC bu using x11vnc. The main idea is provide remote connection to logon window .
What i did:
Make changes in:

Just received my Rock64.  I already have PIs, Wandboard Quads, Odroid-XU4, etc.  Loaded Stretch minimalon an SD, booted up and it booted right; everything worked.

I'll grant that I won't be using the multimedia features, but what I wanted was USB3, GB ethernet, quad core at a decent clock speed, and adequate RAM (4GB).  Not only that, this board is silent unlike the Odroid-XU4 which drives me a little crazy with the fan.

Currently, the Odroid functions as a NAS.  This board will replace it.  Very happy after spending a few hours doing Linuxy/Debiany type things with it.

I just wish there was a US distributor so it didn't take so long to get them.

Received Rock64 the other day found some time to mess with it. 

So finding there are some tools to add that I would like, just the same I decided to proceed without them, i.e. serial port setup, etc.  Hesitated a bit since I had not done one of these before, didn't want to hose it up beyond repair first time around.  But.. did anyway.

Loaded bionic.  Boots fine, do not have a working monitor on it, got to find the right combo.  I am logged in and updating bionic as I speak.

I have not pinpointed, but am investigating as I observe.  There is no apparent reason for it, do not know if it specifically has been mentioned, but ethernet is show RX errors, I noticed right off the bat.  Superficially, it should not have errors, i.e. a fairly new cable from Wally-World (it is one of those flat ones), but technically between my router and the rock64, the cable is the only thing.  Except for low level OS drivers... in ubuntu.  I am pretty confident in my network in house, as I am 4 TV cord cutter as well as internet... it is pretty solid.  And running ubuntu 17.10 vm under windows on the same subnet same route, no RX errors.

I have not noticed anyone else mentioning that, but have noticed the mention of poor network I/O.

Been trying to setup qemu dev environment for this (not really much luck booting anything on it).

Will continue to observe, and inform as I progress.