Hello,
It's been a month since the last post in this forum and while i have my project "working" there is a ton of functionality that I thought i could get out of this board assuming an ASOP ROM with root access would be on the way.    Is this planned? I got two boards hoping that the RockPro64 could be the foundation of my projects but, not out of impatience just lack of being sure that this is still active, am thinking about moving to another arm board with more active development.  In any case: just a delay or is this not planned for the immediate future?
Thanks for your response

Hi,
Just got my Rock64Pro and installed Ubuntu 18.04 Bionic    LXDE Desktop aarch64  from SD card

All seemed to go well, but there is no "Top Menu" So i cannot find a way of accessing network settings, for example to setup wifi using a dongle.

previously using Debian on RPI.

Any ideas

Max

Hi Everyone,
I am new to Single Board Computers and Arm Architecture. I have been using GNU/Linux on my X86 as my main desktop Pc for a few years. This is my current configuration of my pc: Distro: Release Linux Mint 17.2 Rafaela 64-bit - Kernel Linux 3.16.0-38-generic x86_64 - Desktop Manager : MATE 1.10.2 - Hardware: Memory: 8:00 Gb - Processor: Intel® Core™2 Quad CPU Q6600 @ 2.40GHz × 4 This pc is connected to the cheap display via HDMI (A 40 in Westinghouse led TV) With these configurations I have everything I need for work, play and fun.
I would appreciated very much if anyone can help me with these ?:-)
What is the differences between the Rock64 vs RockPro64 ?
Is there any option for booting to the system with different OS like Grub loader?
Is the 1 Gb of Ram + add on Dac be good for Volumio?
Thanking in advance an Rock On:-)
Cheers,
Phamo

Hi Folks,

I've been building Linux kernels since 0.99.12, but I can't come up with a formula that allows me to build the kernel from the kernel-source package that is available for the 190531 release.

I'm trying to enable native SAS, scsi generic, and scsi tape support and add support for the HighPoint RR27XX card family.

EDIT - the RR27XX is seen properly by the kernel, and lspci reports proper configuration information.

Pointers and tips are highly welcomed

I have put the Rock64 Android 9 source code up here:
https://github.com/a9rock64/manifests

It boots but it needs work. 
Neither Ethernet or Wifi is properly configured.
It does not have gapps integrated.
Several more minor issues
On the plus side it looks like OTG/adb is working now.

This is not ready for a casual user.

If your are Android developer please give it a try and help fix the broken parts.
Send me email and I will give you write access to the repositories.

Hello!

I discover two issues with ROCKPro64 GPU drivers:

1. Constant screen flicker with display resolution above 2048x1280. For instance, I was able to reliable reproduce this with screen resolution 2560x1600 with LXDE, KDE and Mate.
I expected 2560x1600 to work as resolution is within the "4K Digital Video Out" spec advertised on product web-site. Issue is reproducible via both of HDMI and USB-C, by the way.

Switching from 2560x1600 to 2048x1280 as workaround is highly undesirable because image became blurry, which is very noticeable on 30 inch display.

2. Constant screen tearing, i.e. not working V-Sync in Xorg session (to reproduce this issue move windows around, play video in web-browser or desktop player). I hoped to get red of this issue by using Mutter Wayland session, but so far I found "Mutter on Mali" guides only for ODROID boards. On ROCKPro64 with installed Mali Wayland driver gdm3 just crash on start with both of enabled and disabled Wayland support in /etc/gdm3/custom.conf

I tried all combinations of modesetting dri2vsync and pageflip options, tried no compositing, default mate compositing, and all variants of kwin vsync options, issue is reproducible with every combination (which is why there is rkmpv wrapper that allow to watch video without tearing, I guess).

Is there any proper (not workaround-ish, like rkmpv, which is less then useful for my usecase, unfortunately) solution for these two issues? Like, maybe, newer GPU driver that not crash gdm3 and Mutter?

I was wondering if there will be only one USB-C port with video out? As there is no mention of any other outputs like hdmi or mini-dp, I suppose this will be the only video output.

Says pinebooks are out of stock.
Can you apply for in stock email?
Can you just pre order by purchasing even if there out of stock?

It is a good practice for lithium battery powered devices to briefly think about the charging configuration which can significantly influence the health and usable capacity over time of a battery. Typically, a LiPo battery -- as is also used in the Pinebook -- has a minimum voltage of 3.0 volts (falling below quickly damages the battery) and a maximum voltage of slightly above 4.2 volts (further charging can destroy the battery and even ignite a fire). 

The higher the difference of the battery voltage to these two extremes is, the longer it will keep its initial capacity and the less stress it has to withstand (temperature as another dimension can be critical also, but will be ignored for now). So, quite good voltage limits for charging your Pinebook may be 3.2 to 4.0 volts. The more tentative these limits are set, the less actual battery capacity will be usable, thus less time your Pinebook will be working on battery before it needs to charge.

Luckily, the power management unit AXP803 of the Pinebook allows you to configure, how you wish to set the voltage limits for your actual use case. To this end, you can use the virtual sysfs files in '/sys/class/power_supply/axp20x-battery/' which allow read and write access. I tested this on the current Armbian 5.86, but other distros may offer similar functionality, as they might use the same "axp20x" kernel module for accessing the AXP803 power management unit. 

With read access, you can find out how the limits are currently set. By echoing values into the virtual files, you can persistently write settings to the unit (yes, written values reside on the AXP803 and keep changed even after reboot or shutdown). As the AXP803, for instance, supports only four possible maximum voltages (4.10v, 4.15v, 4.20v, or 4.35v), invalid values as write attempts are caught by the operating system.

Hi,

Due to my external WiFi driver, I added,