OK, I'm  sure there is something I'm not doing right, but the RTC has me stumped. I use the access point in the upper right of the Mate desktop to set the RTC to use my time zone and report time in 12, instead of 24 hour format. I do this as a user with Admin privileges. And the clock changes appropriately...until the next boot, whereupon I see that it has forgotten the settings and has gone back to defaults. The menus are very explicit about setting the system clock options. So what have I missed?

This is for those less familiar with Linux, or running Linux from an SD card.
When you flash Ubuntu Xenial onto an SD card, the root filesystem size is only big enough to fit the operating system.
This is intentional; to keep the size of the image file as small as possible, making it quicker to download and flash to any size SD card (within reason).
After flashing the sd card and booting up for the first time, log in and do the following to expand the root filesystem by following these instructions.
There's a lot of code below, but the whole process took me less than 2 minutes, and you should be able to safely accept the default response to all prompts.

1. Fix the partition table to reflect the size of the SD card:

Greetings,

The Rock64 often will not boot-up with a serial console connected to the console uart pins (6, 8, & 10).

Symptom:  lights come on, nothing happens at all.

Solution:  unplug the Tx line coming in on pin(10) prior to applying power for boot-up.

Nice install of Q4OS to microSD and transferred to the Pinebook internal drive. 

What is the proper procedure to log into Wireless? (I see 2 connections: waan0 and waan1)
Will the miniHDMI work?

Thanks, Stew

Hi everyone =) I just made first version of CAD drawings of Rock64, heights of chips are not precise for making multi chip heatsinks, but I'll fix it during next week, maybe with all-in-one masive AL heatsink...  

ver. 1  - All possible files available on my github ( https://github.com/TeaPackCZ/Rock64_drawings ) more info at Full description ver 1
ver. 2  - Added DAC board and pictures of models, more info at More info about ver. 2





____________________
Note: I'll edit this post to correspond with actual state...

Hi !!

Two days ago, I received the ROCK64 board. (Thank TL LIM !! )

After checking that almost all connectors are located in the same place as a Raspberry Pi 3
 
 I have made some modifications of the model case I make for Rasperry Pi 3 and here I have the first enclosure made for Rock64...

Rock64 Wooden emclosure

Soon it will be available to Amazon for sale.


Bye!!

I have a 2GB pine64 from July 2016. It has the android-7.1-r69.img installed on a 128GB card.

Now it happend two times that boot just hangs in that aninimated logo before the "Android" text appears. This is with a stock img. How can I check what it is waiting for, or what it is missing?

Is there a way to get not only the kernel messages on serial console, but also the 'adb logcat' output, or whatever else is Android logging during boot? So far I see the filesystems are mounted, some rc scripts are executed.

Thanks.

Hi Guys,

This morning I swapped out the 16 Gb emmc module for a bigger 64Gb one. Opening the case was easy! After rebooting from a know working SD card I simply tried to run
/usr/local/sbin/pine_install_to_emmc.sh xenial-mate I get 'You should boot from SD card' ,which I did....

Any help how to continue would be appreciated. Do I need to partition the drive first? I the emmc drive broken? (I checked it is firmly inserted...)


Erik

Hi,

I have downloaded and installed on my pine64+ the distro OMV_3_0_71_Pine64_3.10.105 based on Armbian_5.27_Pine64_Debian_jessie_default_3.10.105 .

After an update from OMV 3.0.71 to OMV 3.0.78 at the reboot the console shows "no interface available" so OMV hasn't an ip adress for the web ui. So i'm stuck in the consolle that is asking username and password.
The problem is that I don't know the username and the password for Debian_jessie and without logging in debian jessie as root I can't fix the problem with my ethernet ... could you help me ?
thanks

Greetings,

   The purpose of this post is to document the rock64_usb_power_service.sh script , provide instructions and notes for its correct use (tutorial) , and document the installation of the script as a systemd automated service.  

   The problem that we are solving is that the usb2.0 power regulators are controlled by a hardware line (EN) (gpio2) which is in a floating state when the Rock64 boots.   This often results in the usb2.0 ports losing power ( at least momentarily ).  

   The solution to this problem is to create an executable script , as well an automated service (systemd) , that will export the gpio2 line to user space ( setting it low & turning ON the power regulators ) while also allowing the system admin (user) to control the gpio2 for power cycling devices plugged into the usb2.0 port.  This approach to fixing this problem is a win-win in that the usb2.0 power remains on permanently after  boot-up for those who want it, and it also allows advanced users the flexibility of being able to power cycle their usb2.0 ports as designed by the Rock64 engineers ( very handy in many use cases ).

   The user has complete freedom and control because the script may be run manually (as root) or it may be installed as an automated systemd service.  The following tutorial will provide the codes first , then I will discuss how to use them , and finally how to install the usb_gpio_on.service  in systemd.  After each code section I will give instructions for 1) where to place the script, 2) what permissions to give it, 3) what ownership to give it, and finally how to run it.

The Scripts


   Before beginning switch into root operating mode ( and permissions ) with  sudo -i  (important).

rock64_usb_power_service.sh