Search the Community

Was looking for a place to post a solution to this issue, but you guys have got there before me.As others have described, booting a (my) Pinebook with the latest version of Armbian (tried both Bionic and Buster) results in a blank screen seconds after boot.This is even after booting to multi-user.target when there should be no graphical display manager running.I got the latest kernel/version available for 19 and tried that (Kernel 5.4.62) and that worked.Previously I'd tried doing a full firmware upgrade, disabling the lightdm.service, setting the boot target to multi.user/3 and disabling the autologin (in case that had something to do with it) but under the 5.8 I got the blank screen each time.Not complaining here - just wanted to confirm I'd had the same issue.Love Armbian and all the great work that's being done - peace to all. Manjaro ARM also does the same thing, by the way, so it's not just an Armbian issue

UK (ISO) Keyboard problem - terminal won't display a 'pound' As a long-time user of various flavours of Armbian on headless sytems (OrangePi, NanoPi ...) I couldn't resist installing it on my new Pinebook Pro. Well it works like a dream and I am just sooo impressed by all the work that has clearly been done - audio works fine, armbian-config had me set up booting from emmc with my rootfs on nvme SSD in no time at all. BUT - one weird problem that has me baffled... I'm so used to headless Armbian boards that setting up keyboard and localisation is almost automatic to me - but can I get the PBPro keyboard to generate a 'pound' (GBP, '£') in a terminal window- no I cant!! I've set everything up as I think it should be - and every other key on the (ISO) keyboard is correct - but open a terminal window and shift-3 (which should be '£') displays nothing at all. Other applications (Firefox, LibreOffice ...) will display the £ just fine. Can anyone give me any clues??? Thanks!!

same issue here on pinebook. latest kernel that works for me is 5.7.15

also patching the keyboard/mouse firmware is a good idea nice.... i dunno the debian way, but I just booted manjaro on sd.. and did pacman -Sy pinebook-pro-keyboard-updater

Its already fixed And its also because supporting @lanefu Pinebook PRO support efforts. Nice to have this features there.

Changed back to kernel 5.8.5, and changing the brightness like this just shows me a brighter black screen ;-) Issue remains the same, no output to the pinebook's screen, can login by typing my password in the black screen, see the login happening via ssh..

Just an FYI... I've picked things up on the Pinebook Pro a bit... tracking here... https://armbian.atlassian.net/browse/AR-399 Thanks @chwe and everyone else that have done the hard parts.

maybe you should - like on my Pinebook- set the display brightness via /etc/rc.local? #set display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 I did read out the actual dim value as 2: #read-out display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness 2 and I did set (via /etc/rc.local) a for-me-default value of 8 A value of 10 (max.?)was to bright for me

We have nightly images built available for the boards below. Please help us test and report your experience via This Google Form. Images are available via our normal Armbian download page. Just scroll to the bottom to the "nightly build" section. Bananapi Bananapim2plus Bananapim2zero Bananapipro Clearfogbase Clearfogpro Cubietruck Espressobin Helios4 Lepotato Lime-a64 Nanopct4 Nanopiair Nanopim4 Nanopim4v2 Nanopi-r1 Nanopi-r2s Odroidc2 Odroidc4 Odroidn2 Odroidxu4 Orangepi3 Orangepi4 Orangepione Orangepipc Orangepipc2 Orangepipcplus Orangepizero Orangepizeroplus2-h3 Orangepizeroplus2-h5 Pine64 Pinebook-a64 Pineh64 Pineh64-b Rock64 Rockpi-4a Rockpi-4b Rockpi-e Teres-a64 Tinkerboard Tritium-h3 Tritium-h5

Some time ago I tried that joystick on Pinebook Pro and it did not work either, I think the same problem was with x86 PC in Linux, but have to check it again.

I've almost forgot one during my Allwinner garden tour : Pinebook-A64 ! Unfortunately, it seems that 5.8.y is broken somehow, the screen doesn't work after "starting kernel" ... It is not a DT issue, since I've tried to exchange DTB with my previous 5.7.6, so it must be in kernel binary. If someone else have time to test, I will be glad to get help to figure what is broken.

Added nightly images for testing: Bananapi Bananapim2plus Bananapim2zero Bananapipro Clearfogbase Clearfogpro Cubietruck Espressobin Helios4 Lepotato Lime-a64 Nanopct4 Nanopiair Nanopim4 Nanopim4v2 Nanopi-r1 Nanopi-r2s Odroidc2 Odroidc4 Odroidn2 Odroidxu4 Orangepi3 Orangepi4 Orangepione Orangepipc Orangepipc2 Orangepipcplus Orangepizero Orangepizeroplus2-h3 Orangepizeroplus2-h5 Pine64 Pinebook-a64 Pineh64 Pineh64-b Rock64 Rockpi-4a Rockpi-4b Rockpi-e Teres-a64 Tinkerboard Tritium-h3 Tritium-h5

@xmixahlx How much of what your pbp-tools scripts are doing is specifically tailored to the Pinebook Pro (and would cause incompatibilities elsewhere)? Can most of them be run on any RK3399 platform?

For my NanoPC-T4, I want to be able to install multiple kernel versions at the same time and boot a specific one by default. In addition, I would like to be able to select which kernel to start if necessary: Armbian_20.07_Arm-64_focal_dev Boot Options. 1: linux-default 2: 5.8.0-rc4-arm-64 3: 5.8.0-rc3-arm-64 4: 5.8.0-rc2-arm-64 5: 5.8.0-rc1-arm-64 6: linux-test To present my solution, I have used "Armbian_20.07_Arm-64_focal_dev_5.8.0-rc4.img.xz" and "u-boot-rk3399-nanopc-t4.img 07/10/2020 8:50am" on a microSD: With this scheme in place I am able to pull in a new kernel without the need to port over my local image configuration to a new image. If the new kernel is not working as expected all previous available ones are just a reboot away. If the new kernel version is suitable for boot on demand just a new boot stanza in extlinux.conf is nessesary. The mainline uboot for NanoPC-T4 has not yet enabled USB keyboard support. Therefor the on demand selection of a boot option will only work via the serial console keyboard. The build of uboot with the same options in nanopc-t4-rk3399_defconfig as it was done for Pinebook Pro and rockpro64, should probably enable it in a similar way. This means that only HDMI display and USB keyboard are required.

Hey! I recently accidentally made my eMMC unbootable. I ordered this adapter, but the eMMC isn't getting picked up by any of my microSD adapters. Is there a way to hotplug the eMMC chip while booting from SD, like with the Pinebook Pro (which is also RK3399 based)? I'd really like to either repair or clear the eMMC so i could continue using it. Thanks!

@Kwiboo did you have any idea about hantro encoding? ^ also, ffmpeg 4.3 and linux 5.8-rc1 are released and can't wait to update! fyi, i have a new project, pbp-tools on git that is collecting these hwaccel things for pinebook pro: https://github.com/xmixahlx/pbp-tools https://forum.pine64.org/showthread.php?tid=10190 any idea on the ffmpeg -decoders bug not listing v4lrequest? that seems to break things like mpv that use detection. ffmpeg and kodi work OK.

greetings, @AndreVallestero pointed me towards this thread and i wanted to share what's working for me on the pinebook pro (rk3399): mp2, vp8, vp9, h264 and h265 (8 and 10bit) hwaccel. as andre mentioned, i've collected resources and documented my testing in the mainline hardware acceleration thread on pine64 forums as well as some related system bits (mesa-git, kodi-git, etc.). hwaccel thread is here: https://forum.pine64.org/showthread.php?tid=9171 i was pulling patches out of kernel patchwork linux-rockchip and linux-media before finding that @Kwiboo and LibreElec were packaging these up nicely. awesome. thanks so much! you can review the last few posts starting from here to be up to speed: https://forum.pine64.org/showthread.php?tid=9171&pid=65712#pid65712 with Kwiboo's recent linux-rockchip and ffmpeg git activity, my system is using: manjaro pinebookpro 5.7-rc2 kernel branch patched to 5.7-rc6 LibreElec patches from Kwiboo's rk-5.6 branch (modified next/list) Kwiboo's linux-kernel 5.6 vs 5.6-hevc branch diff Kwiboo's ffmpeg 4.2.2 vs 4.2.2-rkvdec branch diff ffmpeg 4.2.3 kodi-git a few notable things with kodi (gbm+gles) and big buck bunny reencode samples: h264 10bit provides kernel hard lock and forced shutdown x265 12bit freezes the kodi interface, then recovers vp9 10/12bit give green image and correct audio 4K 60fps h264 file plays out of sync jellyfin-kodi working great with my htpc server, mostly x264 8bit video files i realize the formats above aren't expected to work, just sharing what happens when they don't. i've upped the ffmpeg log for 4.2.3-v4l2-request-hwaccel-rkvdec with a h265-10b sample here: https://pastebin.com/x7iNaY4M

just a short one.. and I didn't read all of it.. working on: rk3399 to 5.6 (more or less done with: https://github.com/armbian/build/pull/1759 but testing needed especially for everything except pbp) display of pinebook pro working with mainline kernel - same PR camera working on 4.4 for pinebook - not even started yet I would love to merge rk3399 and rockchip64 bsp kernels to keep maintenance easier there - let's see if we get the mali mess sorted out there rk1808 into wip - the boards are there.. but time is missing and kernel source will be a pain maybe further cleaning of opi 4b DT

I had the same or similar issue(missing taskbar, no icons on desktop just text, windows didn't appear) on (old) Pinebook, (Armbian_20.02.1_Pinebook-a64_bionic_current_5.4.20_desktop.img) Doing the above blacklist seems to work around it indeed, thank you!

Re: the built-in 16GB emmc on a 14" pinebook (early model). Applies to Armbian_20.02.1_Pinebook-a64_bionic_current_5.4.20.img and also to trunk build with dev kernel. Prevents installation to emmc from SD, which worked from trunk@3b1418fb5b58f187c658a050c592f2c50fb2db04 in January. I haven't managed to find from which commit it started failing yet. It is in some partial/invalid state in u-boot: => mmc list mmc@1c0f000: 0 (SD) mmc@1c10000: 2 mmc@1c11000: 1 => mmc dev 0 switch to partitions #0, OK mmc0 is current device => mmc info Device: mmc@1c0f000 Manufacturer ID: 1b OEM: 534d Name: 00000 Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 2.0 High Capacity: Yes Capacity: 7.6 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => mmc dev 1 => mmc info Device: mmc@1c0f000 Manufacturer ID: 1b OEM: 534d Name: 00000 Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 2.0 High Capacity: Yes Capacity: 7.6 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => mmc dev 2 Card did not respond to voltage select! It is absent when booted, though has a token line in the log as "mmc1": # dmesg | grep -i mmc [ 2.515757] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 2.541026] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB, uses new timings mode [ 2.542017] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq [ 2.560303] mmc0: error -110 whilst initialising SD card [ 2.565772] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB, uses new timings mode [ 2.584669] mmc1: new high speed SDIO card at address 0001 [ 2.592188] sunxi-mmc 1c11000.mmc: initialized, max. request size: 2048 KB, uses new timings mode [ 3.645870] mmc0: new high speed SDHC card at address 0001 [ 3.646999] mmcblk0: mmc0:0001 00000 7.61 GiB [ 3.649985] mmcblk0: p1 p2 [ 4.019864] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 5.389779] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro

with the newest pushed to my PR: https://github.com/armbian/build/pull/1759#issuecomment-601162767 dev images with a working display can be built, the display is currently rather dark (I guess we've to tweak the defaults from the pwm driver a bit I had it brighter in mind when using the stock OS).. The mouse is somehow bugged so an external mouse is needed and you need to build with extrawifi=no cause they didn't survive moving dev to 5.6 For those waiting for prebuilt images based on 5.6 this ain't gonna happen yet. it's simply not ready yet to deal with debug and users at the same time. And the PR involves to move pinebook to rk3399 with upstream u-boot but this goes in hand with a change in the bsp kernel (from ayufan to friendly arm) and guess what.. the display does not work there.. but mainline with 5.6-rc6 will work. The PR needs a lot of review tho.. for those wanna see a lot of errors in dmesg http://ix.io/2eGz so to summarize: display works wifi works keyboard works desktop works touchpad doesn't everything else was not tested (ah and restart doesn't work neither atm). PR needs quite some review work and testing for other boards cause.. well we all know what happens when we switch a kernel right?

I've created an armbian minimal image for my pinebook with luks encryption. It works fine but I cannot see the password prompt on screen... the boot process is: * The armbian uboot is displayed * Then a black screen... After a few seconds I'm assuming it is time to put my luks password, so I do it * Then the screen starts to show the boot text Is this expected? Am I doing something wrong? I don't want to install plymouth, just the usual LUKS password prompt. Thanks!

I tried but still black screen: root@pinebook-a64:/home/edu# uname -a Linux pinebook-a64 5.4.23-sunxi64 #trunk SMP Thu Mar 5 13:43:50 UTC 2020 aarch64 GNU/Linux root@pinebook-a64:/home/edu# zgrep "CONFIG_DRM_ANALOGIX_ANX6345" /proc/config.gz CONFIG_DRM_ANALOGIX_ANX6345=y

This script was made by/for people that start Unix in 90" or later. Close enough A few tips: - use mainstream repository https://github.com/armbian/build at least for the 1st time. - https://github.com/armbian/build#build-parameter-examples First example is the key you are missing. PinebookPRO is in the CSC/WIP section. - support for Vagrant (method I never used) is not the best. I suggest native or Docker. In case you get into the troubles, supply logs (output/debug) here https://forum.armbian.com/forum/12-armbian-build-framework/ Booting from SD card, running nand-sata-install and installing to BTRFS should get you there. It is also possible to create SD card with ready made BTRFS or even with LUKS ... but not recommended for 1st time build. I don't know how good and how bug-free those features are but consider software support for Pinebook PRO as experimental, fragile ... but developing fast.

I am guessing that this Armbian login is different from the Armbian login I've used. Or it was frozen or cancelled or pigs learned how to fly. I cloned cwhe's git tree, as my next step in learning about things. I'm a dinosaur (started with UNIX in 1984). I used a vagrant plugin that is not available in Debian (I run Devuan on most of my desktop type machines) to adjust the discsize of the Bionic 18.04 box to 60 GB. The "build" of the standard Armbian kernel picking Rock64 as the closest system went to completion. After cloning cwhe's git into a parallel directory, I let it build the tool chain (all the questions/options seemed the same), and then when menuconfig came up; there was nothing specific to pinebook (or pinebook pro). I saved the config and let it start compiling the kernel. It did not finish. There were errors about trying to save things into read only storage, and vagrant was completely locked. Vagrant halt in another terminal session didn't stop things (or didn't seem to). Vagrant -f halt seemed to work, a bit. A vagrant up would not work. Some lockfile was present? I found a vboxmanager command with the UUID of the box and --emergencystop which cleaned things up. On bringing this box up again, I looked for git tags. None seemed to be related to pinebook. Asking for a list of branches, only showed master. Trying to checkout pinebook said there was nothing (branch not valid)? It seems at some point, I need to "overlay?" the u-boot mainline on top of what Armbian has now? But basically, I am too much of a dinosaur; and lack 'fu' to do this modern CVS stuff. Could cwhe post a little more verbose instructions on how to get things to work? :-) My initial "need" is to get btrfs for home. I would like to get panfrost/MESA-(19|20) at some point. At some point, maybe play with mesh networking (I have a farm). Have a great day!