Search the Community

Hello, as already mentioned in topic USB C port doesn't work after upgrading to the latest kernel 6.6.2 . The previous problem with not working left usb 3 port persist no more. Everything is fine. As I remember , before update the usb c port has worked with the adapter and the devices like mouse, usb flash etc. Now it doesn't work any more, furthermore it gives no signal of life. There is 0 amps current measured, also dmesg -W gives no output at all after plugging in the device. PS: I was unable to upload the report file, also the service paste.armbian.com doesn't work at the moment.

Description Other devices could be added if whatever the regulator needed for UHS is enabled. Read perf def improved on the gnome disk benchmarks. Jira reference number [AR-9999] let's enable salva's UHS overlay for RK3399 tested on PBP with 2ghz with 64 gig samsung evo select i like using the yabs.sh fio benchmark for mixed r/w tests curl -sL yabs.sh | bash -s -- -i -g -n also did gnome disk utility read benchmark before kernel 6.6.10 yabs # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # # Yet-Another-Bench-Script # # v2024-01-01 # # https://github.com/masonr/yet-another-bench-script # # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # Sat Jan 6 05:59:38 PM EST 2024 ARM compatibility is considered *experimental* Basic System Information: --------------------------------- Uptime : 0 days, 0 hours, 2 minutes Processor : Cortex-A53 Cortex-A72 CPU cores : 6 @ 1512.0000 2016.0000 MHz AES-NI : ✔ Enabled VM-x/AMD-V : ❌ Disabled RAM : 3.7 GiB Swap : 1.9 GiB Disk : 57.5 GiB Distro : Armbian 23.08.0-trunk sid Armbian 23.08.0-trunk sid Kernel : 6.6.10-edge-rockchip64 VM Type : NONE IPv4/IPv6 : ✔ Online / ❌ Offline fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/mmcblk1p1): --------------------------------- Block Size | 4k (IOPS) | 64k (IOPS) ------ | --- ---- | ---- ---- Read | 1.82 MB/s (457) | 8.12 MB/s (126) Write | 1.85 MB/s (463) | 8.51 MB/s (133) Total | 3.68 MB/s (920) | 16.63 MB/s (259) | | Block Size | 512k (IOPS) | 1m (IOPS) ------ | --- ---- | ---- ---- Read | 12.39 MB/s (24) | 12.48 MB/s (12) Write | 13.51 MB/s (26) | 13.74 MB/s (13) Total | 25.90 MB/s (50) | 26.23 MB/s (25) gnome disk utility read benchmark (just defaults) Cool got some tiny gains on everything but 4k block after UHS enabled 6.6.10 yabs # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # # Yet-Another-Bench-Script # # v2024-01-01 # # https://github.com/masonr/yet-another-bench-script # # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # Sat Jan 6 06:05:48 PM EST 2024 ARM compatibility is considered *experimental* Basic System Information: --------------------------------- Uptime : 0 days, 0 hours, 0 minutes Processor : Cortex-A53 Cortex-A72 CPU cores : 6 @ 1512.0000 2016.0000 MHz AES-NI : ✔ Enabled VM-x/AMD-V : ❌ Disabled RAM : 3.7 GiB Swap : 1.9 GiB Disk : 57.5 GiB Distro : Armbian 23.08.0-trunk sid Armbian 23.08.0-trunk sid Kernel : 6.6.10-edge-rockchip64 VM Type : NONE IPv4/IPv6 : ✔ Online / ❌ Offline fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/mmcblk1p1): --------------------------------- Block Size | 4k (IOPS) | 64k (IOPS) ------ | --- ---- | ---- ---- Read | 1.85 MB/s (464) | 8.81 MB/s (137) Write | 1.88 MB/s (471) | 9.32 MB/s (145) Total | 3.74 MB/s (935) | 18.14 MB/s (282) | | Block Size | 512k (IOPS) | 1m (IOPS) ------ | --- ---- | ---- ---- Read | 13.06 MB/s (25) | 13.64 MB/s (13) Write | 14.38 MB/s (28) | 15.23 MB/s (14) Total | 27.44 MB/s (53) | 28.87 MB/s (27) gnome disk utility read benchmark (just defaults) View the full article

I slowly convinced myself that I wanted a PineBook Pro, some time after the first production run. But then COVID, parts shortages, etc. happened and they were not available again until about mid-2022. But when they were, I decided to snap one up. And since then I have not been able to get it to boot Armbian. It came from the factory with Manjaro, which for me being a Debian guy, might as well be useless. So the PBP sat around collecting dust. Since then I have tried a few times to get it to work. I read many forum posts, tried some things. I won't document all that in detail. In this post, I will continue from where I left off here. However to summarize, that was about comparing DTB/DTS files to Kali, which supposedly works. That may become useful later, but I don't think that's the main problem. I think that the main problem is that this new batch came from the factory with no bootloader flashed to the included SPI flash chip. This is a problem on PineBook Pro because the RK3399 has a kind of weird boot order: SPI, eMMC, SD card. Therefore, if you just put in some SD card you flashed, it still boots from the factory Manjaro from the eMMC. Whatever bootloader they are using also apparently will not recognize an otherwise working Armbian image on an SD card. Now, because of the weird boot situation, there is supposed to be a switch to turn off eMMC. However this did not work for me. Which means one of 2 things: The switch does not work. I read at least one other person saying this. Also on the new revision, it's in a slightly different place than the old revision (may be a clue, maybe not). I simply had a bad Armbian image (which I had burned to sd card) that would not boot for whatever reason.[0] But let's put that aside for a moment. As I still think the main problem is the (empty) SPI. And that will be the easiest/best path forward. I confirmed the 'blank SPI' theory 2 different ways. First, as mentioned in a follow-up to the linked post (4 paragraphs above): As Martijn Braam states here: Of course, I like to beat a horse until it's really dead be thorough in my investigations, so today I wasted a lot of time[1] verifying that this indeed was the case. I did so by dd'ing the /dev/mtd0 block device into a file[2]. When I examined the file, it contained all FF, and also it is about 16 MiB in size. To me this confirms that indeed, the SPI on the new batch comes from the factory empty. So what is next? I keep reading that the only people who had success first had to install something like tow-boot to the SPI. That will be my next step. But before I flashed anything to SPI, I wanted to see what really came from the factory (which I did above). I will continue to document my progress whenever time allows for me to work on this. [0] Once I got the bootloader situation sorted, I later used this same image (on the SD card) to boot and install Armbian, so I do not think this was the case. [1] In the end the solution was simple. But first I wasted a lot of time trying to get rkdeveloptool working in Manjaro on the PBP. Only to realize it's intended to be used from a second machine to read the SPI flash via USB in maskrom mode. Anyway, lesson learned. [2] I tried to attach it but maybe it's too big.

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

Hi all, I have a working Pinebook Pro Focal build with LUKS encryption enabled. The only issue I have is that when booting no progress or password prompt is displayed. As soon as I enter the password and hit enter I see the boot logo or console output depending on what is set in armbianEnv.txt. I will be continuing my research and learning about the boot process in general but wanted to check in here to see if people had any obvious pointers to share or whether maybe this is a known limitation that is going to be hard to resolve. Thanks, Matt

Hello all, I got a problem after new update of armbian firmware through your own module (script). The left USB port on pinebook pro has stoped working at all. Before that was occasionaly after 6 -7 boot ups only one time not working (it is used for mouse). Now after x rebooting it doesnt work at all. The right USB port works without problems. On the left, also USB flash drive doesn't work. No idea, what could it be? Before, as already said, it has worked in 90%. Before firmware upgrade.

I know for sure that booting from an sd card and then using dd to write the uncompressed image to the emmc device isn't what works. I'm talking about Armbian_22.02.1_Pinebook-pro_focal_current_5.15.25_xfce_desktop.img here. Because that essentially bricked my PBP. I have the little adapter to connect the emmc to a usd slot, and using balena etcher to write to that isn't it either. the uboot in that image prevents booting from sd automatically as well, and i didn't find any uboot documentation that made it clear how to manually boot from sd, though i did hook up a serial console. This is what it said. The LED never turned green, the display flashes once but displays no images or text.

Hello, I flashed the Armbian_22.11.1_Pinebook-pro_jammy_edge_6.0.10_gnome_desktop.img file on the 64GB eMMC card of my Pinebook Pro (PBP) laptop but although the eMMC recognizes the image (the ARM logo appears on the screen for a few seconds), booting stalls at (initramfs). I proceeded as follows: 1) First copied the image file from my PC on a 64GB SD card which I inserted into PBP, booted it from the SD card and installed Armbian-Ubuntu without any problem. 2) Downloaded the Armbian*.xz file a second time - this time from the SD card installation -, uncompressed it and flashed it to the eMMC with a USB-to-eMMC adapter after having formatted and partitioned the eMMC. 3) Removed the SD card and rebooted. Installation of Armbian-Ubuntu began but stalled after a few seconds at the (initramfs) prompt. Couldn't type any command (such as exit) after it. PBP only boots from the SD card, but not from eMMC. Nor does it find the SSD card which I inserted with an eNVME adapter on the laptop. Any hint or advice helping me to solve this issue would be very much appreciated.

I bought a Pinebook Pro two weeks ago. It came with Manjaro KDE preinstalled on EMMC. I wanted to try out Armbian, so I downloaded the Bookworm XFCE image from May 27th. In order to get the SD booted, I first flashed Tow-Boot for Pinebook Pro (pine64-pinebookPro-2021.10-005.tar.xz) from github Tow-Boot to the SPI. Then during boot after pressing ESC the menu lets you select the SD card for boot. The first boot to Armbian worked well. I could set up user, timezone and everything. The XFCE desktop looks very clean with a reasonable selection of software. Well done, team! But after I upgrade the system with apt update & upgrade, the next time the machine is booted and SD card is selected, armbian won't boot anymore 😞 The upgrade seem to have broken something. I tried it twice, the second time freezed the kernel-upgrades in the armbian-config tool prior to upgrading it. Didn't help. Manjaro from EMMC still boots ok. Attached is a screenshot of the failed boot process, after I selected SD card to boot on the Tow Boot menu.

Hi, I put the image on an SD card, but the machine fails to boot. Looking at the serial console, it just sits in a loop with the CPU constantly resetting after an exception. Serial console log is attached. Regards, Dianne. bootloop.txt

Hello! I don't really have a question, but just wanted to report I tried out the generic UEFI arm64 image on a Pinebook Pro, and it installed emmc and booted just fine! This was possible because I had installed Tow-Boot to the SPI flash, which supports UEFI booting. I had tried using the Pinebook Pro build of armbian, which worked fine when booting off the sdcard, but installing it to the emmc wasn't working. I'm using Tow-Boot 2021.10 then arbmian image Armbian_22.08.7_Uefi-arm64_jammy_current_5.15.74 . There's a few rough edges in the grub menu, but it boots the OS off the emmc just fine. Should the be mentioned on the Pinebook Pro page? Personally, having Tow-Boot installed to SPI is all around a much more "normal" laptop experience, so it seems like a good idea in general.

Hi al. I've finished my review of the PineBook Pro. I just love this thing. Runs great with Armbian. Here my video. Here all my gathered information:

the system does not start with emms, the red light lights up and that's it, I tried to record another version of the uboot, the armbian icon appears and the wheel spins does not respond to pressing the keys. I couldn't write the issue to the bugtracker....

I've just installed armbian to Pinebook Pro's eMCC using the full-disk encryption helper script from https://github.com/mmgen/mmgen-geek-tools The said script was executed inside an armbian installation in an sd card with official Pinebook Pro image. The eMCC installation almost worked - it boots to graphical desktop, however there's no wifi and bluetooth. I don't have any other way to connect the laptop to internet. I guess the way to fix this is to boot the sd card again because it has internet, then open the encrypted disk manually and chroot to its root, then run some command - but I don't know which one! Please help.

Hi, i got a Pinebook and install the latest Armbian Image. All is working fine, only the sound output make problems. It isn't matter if i play a mp3 file or a play a YT Video. The sound is just strechted, drawned, like in slow motion. What can i do to solve this issue? Any ideas? Thank you for your help.

Hi, I update Armbian (Debian) from Kernel 5.4 to the last version Armbina 20.08.2 with Kernel 5.8.6-sunxi64, but now I don't boot the GUI. I have connected only the power and I can use from other pc from ssh. Thank you for all!

https://zuckerbude.org/the-pinebook-pro/

Hi, I started using pinebook armbian buster when it was beta, it worked. From that beta I upgraded yeysterday and I see no display (LCD) after kernel starts (I only see the boot). The same using a new official image [1] I know there is another places to track this issue [2], but the thing is that in the official image page [1] it says it is fully working and that is not true. There are two options: - changing the status to something beta (like before) so you are less responsible of problems - putting an image that works [1] https://www.armbian.com/pinebook-a64/ [2] https://armbian.atlassian.net/browse/AR-443

Does anyone know the status of getting display to work over USB-C on Pinebook Pro? Thanks!

Is there any plan to port to the Pinebook Pro?

I have a latest ubuntu armbian on a pinebook pro, I use an DUB-1312 gigabit to usb 3.0 for wired connection, I plug it in the usb 3 port of the pinebook but I run iperf I see the same speeds as the other usb 2 port. $ iperf3 -c 192.168.0.34 Connecting to host 192.168.0.34, port 5201 [ 5] local 192.168.0.33 port 48140 connected to 192.168.0.34 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 41.7 MBytes 350 Mbits/sec 0 298 KBytes (More thread only made results worst) While the same DUB-1312 plugged in my amd64 ubuntu computer achieve 950Mb/s easly (capped by the other testing device (an odroid-hc1)). Same thing for a random usb 3.1 key I have laying around (so its very unlikely a problem with the ethernet over usb driver). It seems to me that the usb 3 port is only being used with usb 2. Am I the only with this issue ?

Yesterday my 14" Pinebook arrived so I thought I'll collect some already available information. A lot of work still has to be done to get a decent laptop experience with this hardware so this is neither a review nor a stupid Un-Review but just a preview instead. To get the idea about dimensions I added a 13" and a 15" laptop to the picture. Pinebook is wedge-shaped and thickness matches both the 2011 15" MacBook Pro and the 13" from 2015: Display size closely matches the 13" MacBook Pro (but of course pixel density / resolution don't match as well as quality: TN vs. IPS and coating -- it should be obvious if you've the 'you get what you pay for' principle in mind but I'm sure we'll see reviews somewhere else where people are comparing Pinebook with Chrome/MacBooks and think they would get the same display quality for a fraction of costs) Last hardware detail: heat dissipation. I've been curious how well the Pinebook's thermal design is and it looks pretty good. This is the moronic sysbench pseudo benchmark calculating prime numbers endlessly and the Pinebook sitting on a pillow to prevent airflow below the case bottom. Throttling settings are rather conservative with 65°C defined as first trip point and only after a couple of minutes the internal A64 SoC temperature reached this value and slight throttling occured (1.15 GHz down to 1.1 GHz, that's a 'difference' you won't be able to notice). So it seems the combination of a thermal pad with a large metal plate inside the case is rather sufficient: What you see here is a graph drawn by RPi-Monitor, one of my favourite tools to get a clue what's going on with ARM devices (since it's not a heavy monitoring tool that changes the way the OS behaves but it's pretty lightweight sp you can run it in the background and let it monitor/record stuff like cpufreq scaling, consumption and so on). Pinebook currently ships with a rather clean Ubuntu Xenial on the eMMC with Mate desktop environment based on latest BSP u-boot and kernel. To get RPi-Monitor installed on this Ubuntu @pfeerickprovides a script (please follow progress over there). When I played around with Wi-Fi I noticed that Wi-Fi powermanagement seems to be enabled (makes working via SSH close to impossible) and that MAC address changes on every reboot. To disable Wi-Fi powermanagement I simply used the Armbian way: root@pinebook:~# cat /etc/NetworkManager/dispatcher.d/99disable-power-management #!/bin/sh case "$2" in up) /sbin/iwconfig $1 power off || true ;; down) /sbin/iwconfig $1 power on || true ;; esac Unless Wi-Fi driver gets a fix to use a MAC address based on the SoC's individual so called SID one way to assign a fixed MAC address for the Wi-Fi is to add a wifi.cloned-mac-address property to all NetworkManager profiles after establishing a Wi-Fi connection first: nmcli con show | grep wlan | while read ; do set ${REPLY}; nmcli con modify "$1" wifi.cloned-mac-address $(cat /sys/class/net/$4/address); done (I'm pretty sure some masochistic people prefer fiddling around in /etc/network/interfaces instead so if you're not using your laptop as a laptop being carried around and seeing a lot of Wi-Fis you can also use the usual tweaks for the interfaces file. Please also note that using a random MAC address can be considered a privacy feature on laptops since it makes tracking of you in public environments harder). While watching the Pinebook's charging/discharging behaviour I noticed that consumption drawn from wall while charging oscillates between 9W and 15W while being used and display active so it's really great that Pine Inc fixed Pine64's design flaw N° 1: Pinebook is NOT equipped with shitty Micro USB for DC-IN leading to all sorts of trouble but just like SoPine baseboard now uses a 3.5mm/1.35mm barrel jack combined with a 5V/3A PSU (for other hardware details please refer to linux-sunxi wiki page). Battery status (health, capacity, voltage and so on) is already available through sysfs but some values are wrong or need calibration. This needs to be fixed with further upgrades. Also interesting: charging seems to be under control of the ARISC core inside A64 SoC and works together with Pinebook's AXP803 PMIC (powermanagement IC) even when there's no OS running. This will be somewhat challenging to implement later with mainline I would believe... I'll stop here for now since Pinebook is still stuff for developers and not end users. Just some resources for interested parties: https://github.com/ayufan-pine64/boot-tools (Kamil implemented an u-boot based approach to flash directly to eMMC and there you find the necessary BLOBs to convert other BSP based Pine64 images for Pinebook since different DRAM and other settings require different SPL+u-boot) https://github.com/ayufan-pine64/linux-pine64 (based on longsleep's BSP kernel but with more fixes currently for Pinebook) $mainline resources (I lost track where to find most recent stuff but will add this later) Wrt Armbian running on Pinebook we could now simply exchange u-boot+SPL+DT of our Xenial Desktop image... but I hope we won't do that but wait until dust has settled while helping with development efforts in the meantime. In other words: no Armbian on Pinebook (right) now

I installed the linux-image-dev-sunxi64 and linux-dtb-dev-sunxi64 packages, which pulls in the 5.1.5 kernel, and it seems something is amiss in the pinebook dtb. On the 4.19 kernel, pwm-backlight powers on, and you get video output, however, on 5.1.5 once u-boot loads the kernel and it is starting, video output goes away. In the 4.19 kernel, the kern.log shows the following output during boot: May 29 19:15:10 localhost kernel: [ 3.937999] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) May 29 19:15:10 localhost kernel: [ 5.573863] random: lvmconfig: uninitialized urandom read (4 bytes read) May 29 19:15:10 localhost kernel: [ 5.968672] random: systemd: uninitialized urandom read (16 bytes read) May 29 19:15:10 localhost kernel: [ 5.978739] random: systemd: uninitialized urandom read (16 bytes read) May 29 19:15:10 localhost kernel: [ 6.115937] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro May 29 19:15:10 localhost kernel: [ 6.767672] random: crng init done May 29 19:15:10 localhost kernel: [ 6.767681] random: 7 urandom warning(s) missed due to ratelimiting May 29 19:15:10 localhost kernel: [ 6.911809] Adding 4194300k swap on /var/swapfile. Priority:-2 extents:21 across:11288572k SSFS May 29 19:15:10 localhost kernel: [ 9.018020] pwm-backlight backlight: backlight supply power not found, using dummy regulator May 29 19:15:10 localhost kernel: [ 9.018134] pwm-backlight backlight: Linked as a consumer to regulator.0 May 29 19:15:10 localhost kernel: [ 9.018215] pwm-backlight backlight: Dropping the link to regulator.0 May 29 19:15:10 localhost kernel: [ 9.051632] cpu cpu0: Linked as a consumer to regulator.3 May 29 19:15:10 localhost kernel: [ 9.051705] cpu cpu0: Dropping the link to regulator.3 May 29 19:15:10 localhost kernel: [ 9.051919] cpu cpu0: Linked as a consumer to regulator.3 May 29 19:15:10 localhost kernel: [ 9.075427] pwm-backlight backlight: backlight supply power not found, using dummy regulator May 29 19:15:10 localhost kernel: [ 9.077644] pwm-backlight backlight: Linked as a consumer to regulator.0 May 29 19:15:10 localhost kernel: [ 9.110436] pwm-backlight backlight: Dropping the link to regulator.0 May 29 19:15:10 localhost kernel: [ 9.251253] pwm-backlight backlight: backlight supply power not found, using dummy regulator May 29 19:15:10 localhost kernel: [ 9.251354] pwm-backlight backlight: Linked as a consumer to regulator.0 May 29 19:15:10 localhost kernel: [ 9.329128] zram: Added device: zram0 May 29 19:15:10 localhost kernel: [ 9.345016] zram: Added device: zram1 May 29 19:15:10 localhost kernel: [ 9.345766] zram: Added device: zram2 May 29 19:15:10 localhost kernel: [ 9.353305] thermal thermal_zone0: failed to read out thermal zone (-110) However, with 5.1.5 May 30 22:55:04 localhost kernel: [ 4.994984] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) May 30 22:55:04 localhost kernel: [ 6.631175] random: lvmconfig: uninitialized urandom read (4 bytes read) May 30 22:55:04 localhost kernel: [ 7.044640] random: systemd: uninitialized urandom read (16 bytes read) May 30 22:55:04 localhost kernel: [ 7.054687] random: systemd: uninitialized urandom read (16 bytes read) May 30 22:55:04 localhost kernel: [ 7.191887] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro May 30 22:55:04 localhost kernel: [ 7.874481] Adding 4194300k swap on /var/swapfile. Priority:-2 extents:21 across:11288572k SSFS May 30 22:55:04 localhost kernel: [ 8.876110] random: crng init done May 30 22:55:04 localhost kernel: [ 8.876120] random: 7 urandom warning(s) missed due to ratelimiting May 30 22:55:04 localhost kernel: [ 9.665763] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 9.690621] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 9.806449] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 9.807498] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 9.828538] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 9.829826] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 9.935618] sun50i-a64-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator May 30 22:55:04 localhost kernel: [ 10.068063] thermal thermal_zone0: failed to read out thermal zone (-110) May 30 22:55:04 localhost kernel: [ 10.068121] thermal thermal_zone1: failed to read out thermal zone (-110) May 30 22:55:04 localhost kernel: [ 10.068145] thermal thermal_zone2: failed to read out thermal zone (-110) So I did a diff of the 4.19 sun50i-a64-pinebook.dts and the 5.1.5 sun50i-a64-pinebook.dts (using dtc -I dtb -O dts <kernel/path/dtb> from the respective dtb packages and then did a diff of the out files and came across the following: backlight { compatible = "pwm-backlight"; - pwms = < 0x43 0x00 0xc350 0x01 >; + pwms = < 0x48 0x00 0xc350 0x01 >; brightness-levels = < 0x00 0x05 0x0a 0x0f 0x14 0x1e 0x28 0x37 0x46 0x55 0x64 >; default-brightness-level = < 0x02 >; - enable-gpios = < 0x22 0x03 0x17 0x00 >; - phandle = < 0x98 >; + enable-gpios = < 0x26 0x03 0x17 0x00 >; + power-supply = < 0x49 >; + phandle = < 0x9d >; }; It seems like somehow the &pwm and &pio numbers are changed from 4.19 to 5.1.5 but I have no idea where to go from here. I'm assuming this is related to the "arm64: dts: allwinner: add backlight regulator for Pinebook" commit upstream, but I can't see why that commit would have changed the pwm or gpio used.

Hello - I have attempted an install of Armbian Stetch on a Pinebook (non HD) with the latest image from https://www.armbian.com/pinebook-a64/. I can power on the pinebook and can SSH in, and have successfully installed to the internal emmc, however the screen does not come on. This pinebook readily works with other OS images I've attempted. I suspect I'm just missing something somewhat obvious, but I can't find reference to this issue elsewhere - how do I enable access via the screen/keyboard on the device itself? Thanks!

It is possible to drag backlight control slider to far left position and this completely dims the screen's backlight. This might cause a lot of trouble, if backlight levels get saved by systemd service, as it will persist across reboots and will require you to shine a flashlight on a screen to actually see something and turn backlight back on.