[Info] Pinebook A64 Display Brightness at bootup with CLI-only-image

[guidol]

Normally when you have installed a XFCE-Desktop image for the Pinebook A64 you could set the display brigthness with the following pkexec command to a readable higher level - like I did in the past (possible brightness values are 1-10 - on startup this is only set to 2):

 

pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8

 

read-out command for the current value:

 

pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness

 

but on standard CLI-install pkexec and xfpm-power-backlight-helper are missing, so to use this command-line (in /etc/rc.local) you have to install these 2 packages:

 

sudo apt install xfce4-power-manager pkexec

 

[Gunjan Gupta]

quick look into xfpm-backlight-helper shows it is manipulating files in /sys/class/backlight. If the goal is to do it from /etc/rc.local, probably you can do the same as well.

[guidol]

@Gunjan Gupta

 

Today I did try the following images

 

Armbian_community_24.8.0-trunk.205_Pinebook-a64_noble_current_6.6.31_gnome_desktop.img

and

Armbian_community_24.8.0-trunk.205_Pinebook-a64_bookworm_current_6.6.31_minimal.img

 

on my 14" (1080p?) Pinebook non-Pro A64, but I do get only a black screen

It didnt help to use

echo 8 > /sys/devices/platform/backlight/backlight/backlight/actual_brightness

or the pkexec-command

The screen lights up, but to information on the screen.
I had only (sometimes) access via a USB-Ethernet-Adapter. But at some boots the ethernet wasnt recognized and the onboard-Wifi doesnt sho up

 

The last version I could get my screen to work - with a CLI-version of bookworm - is 24.2.0 of armbian (after update?)

 

I dont know how to switch via 720p/1080p for the different screensizes of the Pinebook A64 non-Pro (I have 14" and not 11.6")

 

BTW: after updateing the 24.2.0 of armbian via apt update/upgrade the system is also non-working
(Black screen and no ethernet and no Wifi)

 

Its has updated to kernel 6.6.31 and this was also the "death" to some of my OrangePi installations

 

The "Community Editions" are at this time unuseable (because non-tested) - this could end in a bad reputation also for the supported devices - as I think.

 

For me its software-obsoleszenz - rendering working hardware into a paperweight

Edited July 1, 2024 by guidol

[guidol]

Like on the OrangePi's which have problems with the latest Community Edition (kernel 6.6.x and their armbian-firmware) I went back to the most actual stable image before kernel 6.6.x  (non-Community Edition?) for the Pinebook A64 which can be found at
https://armbian.hosthatch.com/archive/pinebook-a64/archive/Armbian_23.11.1_Pinebook-a64_bookworm_current_6.1.63.img.xz

 

 

You do get a non-Desktop system with

Armbian 23.11.1 Pinebook-a64 bookworm current kernel 6.1.63

then do a Kernel-Freeze in armbian-config -> system
apt update/upgrade

 

and you will end with a stable
Armbian 24.5.1 Bookworm with Linux 6.1.63-current-sunxi64

 

This will recognize my 14" Screen, WiFi and Ethernet (USB)

 

 

 

[Hamid Reza Heydari]

Hello, I'm sorry, I didn't know where to ask. I have a nanopia 64 board. I installed Armbin 6.1.63 software from Archive, and after updating and upgrading, I encountered a problem and can't log in anymore. How can I solve the problem? Thanks.

[Jecht]

Hello

I don't know if anyone is currently looking for how to fix these problems.
I have a Pinebook 14" (720p) and tried the following:

Last published image: Armbian_community_25.2.0-trunk.377_Pinebook-a64_bookworm_current_6.6.72_minimal.img.xz

• The boot screen is displayed
• After the message "Starting kernel" the screen turns off completely for about 1 minute
• Then the backlight turns on but the screen stays black indefinitely
• The system is unusable

Last image available in the archive: Armbian_23.8.1_Pinebook-a64_bookworm_current_6.1.47.img.xz

• The system boots without showing the boot screen
• The message "Welcome to ARMBIAN" is displayed and the configuration process begins
• The system works correctly and allows installation on the eMMC
• After performing an "update" and "upgrade" the system is unusable as in the last published image.

Edited January 26 by Jecht