Using armbian bionic mainline kernel on A64-v1.1 board
Linux pine64 4.19.38-sunxi64 #5.83 SMP Fri May 3 21:02:31 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux

In RPI bionic could just set values in boot.txt.  Is this possible in armbian bionic mainline?

I know that one can use device tree overlays but can't find any examples specific to the A64.

Anyone have a dts file or otherwise know how to declare a pin as an interruptible input?  I've come across nothing in any A64 docs.

This is the software that came with my Pinebook 11.6" laptop but HDMI out doesn't work with XFCE or Plasma so I can't display on external screens. Everything else works well. Xubuntu is my preferred software so I don't want to install something else. How soon can this be fixed? Thanks

In my opinion, Armbian with LXDE as window manager is a good fitting combination for the limited power of the Pinebook. LXDE provides only few visual effects, so the system can be used with acceptable performance. Unfortunately, I had an issue with the battery plugin of the lxpanel (the bar where all current windows/processes are stacked into). 

Indication: Battery plugin (batt) of lxpanel does not show the current "capacity" (charged value in percent) of Pinebook's battery. Instead, it displays "0% charged" and continuously fires the low-battery alarm.

Reason: The integrated functionality of the battery plugin calculates the charged value by using the coulomb-based counters "charge_now" and "charge_full" (or alternatively "energy_now" and "energy_full"). These counters are usually provided by the power management unit's Linux kernel module. The kernel module (axp20x) for the AXP803 power management unit of the Pinebook does not provide "charge_now" and "charge_full" information. Instead, a percentage value for the current charge is provided as "capacity" (try 'cat /sys/class/power_supply/axp20x-battery/capacity').

Solution: I have changed the source code for the batt plugin with respect to the above mentioned reasons. Now, the percentage value is directly read from the corresponding sysfs file and not longer calculated indirectly.

The original code (lxpanel version 0.10.0) that you can find in 'lxpanel-0.10.0/plugins/batt/batt_sys.c' looked like this: 

Using armbian bionic mainline kernel on A64-v1.1 board
Linux pine64 4.19.38-sunxi64 #5.83 SMP Fri May 3 21:02:31 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux

Need to allow non-root access to gpio pins (i.e. gpio group with access to export and unexport etc) via udev.  I've done this successfully before on an RPI but no matter what I try the gpio group and permissions are not set.   Maybe it's something specific to Pine64 so asking here.  

here is one version of rules I've tried.   using udevadm I've confirmed the file is read and loaded but the changes are not made

Hi,

there is a new driver coming to the 5.2 linux kernel called Panfrost https://gitlab.freedesktop.org/panfrost. Afaik Rockpro6 has a Mali GPU and maybe it could use these drivers. Are there any plans to backport them to the current kernel or to jump to a newer kernel in the near future?
Kodi for example supports Panfrost and should be running much better with it.

Greetings,
Khaosgrille

Hi!

I recently bought a RockPro64 with 4GB and would like to control a 1.8 LCD screen with SPI interface using the pins on the GPIO header.

The system is running ayufan's Ubuntu minimal. 

I had success in simple GPIO switching by using the RP64-GPIO library:
https://forum.frank-mankel.org/topic/292...-rp64-gpio

However, I was not able to access SPI. I could not find any help or documentation on the internet, not even on the Wiki.

Anyone had success with this?

I tested both current Armbian mainline images (Armbian_5.86_Pinebook-a64_Ubuntu_bionic_next_4.19.38_desktop and Armbian_5.86_Pinebook-a64_Debian_stretch_next_4.19.38) with my Pinebook 11.6" shipped in May '19 and both images have issues with the display brightness settings. 

Indication: After boot up, the backlight is set to maximum brightness and resetting it to other values in /sys/class/backlight/backlight/brightness (or via desktop power manager tool) shows no effect. The brightness level stays the same, although 'cat  /sys/class/backlight/backlight/brightness' returns changed values.

Solution: I managed to work around the issue by modifying the sun50i-a64-pinebook.dtb in /boot/dtb/allwinner/ in the following way:

(You can convert the dtb file to human-readable dts-format with 'dtc -I dtb -O dts /boot/dtb/allwinner/sun50i-a64-pinebook.dtb > converted.dts')

Initial content was:

I can mount it manually fine off the CLI but if I add it to /etc/fstab it hangs the entire system when booting. I've got it on fstab as

I have several rock64 boards running bionic-containers-rock64-0.7.9-1067-arm64.img.xz
I now see there's a new pre-release/upgrade available bionic-containers-rock64-0.8.0rc14-1134-arm64.img.xz
My question is:
Is it enough to do
sudo apt-get update -y
sudo apt-get install linux-rock64 -y
..would that upgrade the 0.7.9 version to the 0.8.0 version? ..and how do I see that it's the 0.8.0 version?
..or do I need to take out the SD card, format it and install 0.8.0 from scratch?
I wouldn't like to re-format and re-install all the boards, as I have them all modified and fine-tuned with many features, settings and programs.

After having tried the install linux-rock64 command I now see this when logging in:
Welcome to Ubuntu 18.04.2 LTS (Gnu/Linux 4.4.167-1201-rockchip-ayufan-g74fa6c44ee39 aarch64)
Is that the 0.8.0 version linked above?

Krgds.

Using a SanDisk Extreme V30 128GB. Also tring with samsung Evo+

AOSC working without problems.

Each time I boot different errors, usually mounting /tmp, zram or other similar. Sometimes stack trace and automatic reboot.

Latest dev builds are broken?

Thanks