Search the Community

Just to follow up, I reinstalled from the Pinebook Pro Cinnamon image listed here: https://www.armbian.com/pinebook-pro/ Using the 6.1.11-rockchip64 kernel things seem fine. I'm keeping kernel updates frozen and sticking to the stable distribution, so hopefully things will continue to work. If anyone does have any questions I'm happy to do testing. Otherwise I will probably leave this alone (I had been updating the kernel trying to get suspend working but at this point I'd prefer to keep acceleration working and just shutdown the device when I'm not using it).

I have been running Armbian on a Pinebook Pro without issues. I use the stable distribution, but after an update about a week ago (I think) the Panfrost driver has stopped working. When logging into the desktop environment (Cinnamon) the symptom is a black screen with a cursor visible but nothing else. Checking the logs I see a bunch of lines like: > Mar 20 09:29:05 pine kernel: [ 534.502108] panfrost ff9a0000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0xb9f2b40, tail=0xb9f2b40 If I log in by disabling hardware rendering (choosing "Cinnamon (Software Rendering)") then the desktop does display and work (albeit very slowly). After things broke I enabled the unstable updates, but this didn't seem to fix the problem. Unfortunately I can't remember exactly which software I updated but I assume it was either the kernel or a user space program that works with Panfrost. Has anyone else seen this issue? I'm happy to provide any more details or try other steps if it would help debug the issue. Thanks!

I have got Armbian working, on SD card and/or eMMC installed images, without needing to open the case. Detailed instructions (and some detailed investigative reasoning along the way) can be found in a new thread I started a few days ago: https://forum.armbian.com/topic/27598-getting-armbian-working-on-second-batch-mid-2022-pinebook-pro/

In the following thread I essentially did all the steps I had mentioned above. Proceeding slowly and carefully, I felt confident to flash the SPI, once I had determined that indeed it was empty. In the end you were right, the key is putting tow-boot on the SPI. I mean, that is certainly the easiest way I think. And the way I did it, I did not even have to open the case (which I was getting very tired of doing by this point, LOL). I have got Armbian working now both via SD card (the other day) and/or eMMC (just tonight). Detailed instructions can be found here: https://forum.armbian.com/topic/27598-getting-armbian-working-on-second-batch-mid-2022-pinebook-pro/

After the better part of a year being unable to use this device, I am pleased to announce my first successful boot into Armbian. I accomplished this by installing tow-boot to the SPI. If you check their instructions for the PineBook Pro, it says to install some 'installer' version first to an SD card, and then boot that, and use it to install to the SPI chip (or other media). I did not want to do that for a few reasons: I don't understand why all the faffing about with an indirect installation method via SD card? I don't seem to be able to boot via SD card anyway. I am really not interested in removing all those $#%^# screws from the back case again, just so I can flip a switch, then put them all back (twice, maybe more).[0] So what I did was dig around a little more until I found this issue from last year where people were saying just to do the following, essentially: dd if=Tow-boot.spi.bin of=/dev/mtd0 So I downloaded latest release of tow-boot, which comes as an xz compressed tar archive. After opening that up the usual way with: tar -xf pine64-pinebookPro-2021.10-005.tar.xz Under the binaries folder I found the Tow-Boot.spi.bin file. I copied that over to PBP and then executed the above mentioned 'dd' command (via sudo). I powered off and then back on, I knew it was successful because I saw the Tow Boot logo. So I powered off and then inserted SD card I had prepared a while back with Armbian on it. And yet it still booted into Manjaro on the eMMC. So once Manjaro finished booting, I powered back down, then back on, this time pressing <ESC> to bring up tow-boot's boot menu. After selecting 'SD card' I was able to boot into Armbian image on the SD card, which did the normal expansion and first run setup (entering passwords, locale, etc.). Now this is interesting, because I had tried to boot this very same SD card before, without any luck. Even turning the (previously mentioned) 'eMMC switch' to both positions[0], I could never get it to work. So maybe there is something to the 'switch is broken on the new batch' theory? Anyway, I guess that's it, as I finally have Armbian running on here. It's a minimal/CLI image, so I still have my work cut out for me getting this all set up, but hopefully I can just install my preferred desktop packages and we will see how it goes. But that's another project for another day. [0] Which involves removing quite a number of tiny little screws and removal of the entire back cover. And then putting them all back. In the meantime you can't really use the keyboard or anything, so you pretty much have to do the whole %&#@%# process every time. After doing this a few times, it starts turning into a hassle.

I am working on this now. I guess they need to be similar kernel versions to be useful (i.e., both 6.1.y)? EDIT: I am downloading: Armbian_23.02.0-trunk_Pinebook-pro_sid_edge_6.1.11_xfce_desktop.img.xz now to compare with kali-linux-2023.1-pinebook-pro-arm64.img.xz Which appears to be 6.1.0. Close enough? EDIT2: OK, I attached both decompiled DTS files. Hopefully someone who actually knows what they are doing can take a gander at them in their diff tool of choice. EDIT3: It's pure wizardry, I tell you! But here is the diff: EDIT4: I am not sure if above is the problem or not. Many people seem to think the problem is with Manjaro's boot loader. I am also trying to see what came on SPI from factory, I suspect it's empty on this new batch but I want to confirm that. Armbian_rk3399-pinebook-pro.dts Kali_rk3399-pinebook-pro.dts

Looks like you asked awhile ago, hopefully this is still relevant. I've been successfully running Armbian off of EMMC on my Pinebook Pro. Before installing Armbian I actually flashed Tow-boot onto the PBP's SPI (replacing the built-in boot loader). Then I was able to run the Armbian installer and installed directly to the EMMC. This set up seems to work fine for me. Hope this helps, good luck!

I am running Armbian 22.11 on my PineBook Pro from both eMMC and SD and have installed the latest upgrades. It is now the end of February and I have still not found any way to get BlueTooth or the camera to work. If anyone has a solution, I sure would appreciate some insight.

hello guys bluetooth stopped working uname -a Linux pinebook 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 GNU/Linux dmesg | grep Bluetooth [ 9.863147] Bluetooth: Core ver 2.22 [ 9.863249] Bluetooth: HCI device and connection manager initialized [ 9.863261] Bluetooth: HCI socket layer initialized [ 9.863266] Bluetooth: L2CAP socket layer initialized [ 9.863276] Bluetooth: SCO socket layer initialized [ 9.972130] Bluetooth: HCI UART driver ver 2.3 [ 9.972144] Bluetooth: HCI UART protocol H4 registered [ 9.972147] Bluetooth: HCI UART protocol BCSP registered [ 9.972218] Bluetooth: HCI UART protocol LL registered [ 9.972222] Bluetooth: HCI UART protocol ATH3K registered [ 9.972261] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 9.972460] Bluetooth: HCI UART protocol Intel registered [ 9.972609] Bluetooth: HCI UART protocol Broadcom registered [ 9.972646] Bluetooth: HCI UART protocol QCA registered [ 9.972649] Bluetooth: HCI UART protocol AG6XX registered [ 9.972688] Bluetooth: HCI UART protocol Marvell registered [ 12.322372] Bluetooth: hci0: command 0xfc18 tx timeout [ 20.450331] Bluetooth: hci0: BCM: failed to write update baudrate (-110) [ 20.450363] Bluetooth: hci0: Failed to set baudrate [ 20.799400] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.799435] Bluetooth: BNEP filters: protocol multicast [ 20.799461] Bluetooth: BNEP socket layer initialized blueman-manager blueman-manager 14.32.28 ERROR Manager:147 on_dbus_name_appeared: Default adapter not found, blueman-manager 14.32.28 ERROR Manager:151 on_dbus_name_appeared: No adapter(s) found, exitin stopped working after last system update

@Artem Komissarov Thank you for your reply, Artem. I did try to run armbian-config several times with ext4 and all other available install options but it stalled after the initial booting with the u-boot logo and before the armbian ubuntu logo appeared. During the installation phase, it did not recognize the eMMC nor any mmcblk2 partition, but only the mmcblk1 partition where armbian-ubuntu was installed from the sd card which I flashed it to. Although I surely must have missed some basic command somewhere during installation, it nonetheless seems that with the factory pre-installed manjaro on Pinebook Pro any attempt at installing another OS might make the eMMC unreacheable. No resetting of the PBP will have any effect, leaving booting from the sd card as the only choice. Any further hint or advice on how to solve this issue would be very much appreciated.

Description A patch for Pinebook Pro was not applying cleaning on current 5.15 rockchip64 kernel flavour, turns out that Orange Pi 4 LTS has no more HDMI video output and dmesg is lamenting about a missing extcon connector over fusb driver. fusb driver has the control over video output since it has the capacity to steer video output from HDMI to DP via USB type-c connector. A broken fusb driver causes broken video output; this problem can be shared among all boards that depend upon it. This pull request fixes the application of the Pinebook Pro patch, and perhaps fixes the Orange Pi 4 LTS broken video output. edit: I confirm, fixing the patch fixes also video output on Opi4 LTS Jira reference number AR-1517 How Has This Been Tested? [x] Patch application [x] Compilation of the deb kernel packages [x] Testing on existing Orange Pi 4 LTS installation Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

This is a (somewhat) long standing and well known issue, check PineBook Pro subforum here, there are a number of threads about various booting issues (including eMMC specifically). I think the problem (with the latest batch of PBP which were shipped, anyway) is that those came with Manjaro on the eMMC and no universal bootloader (tow boot) flashed on the SPI chip. Well thinking about that now, I guess burning to eMMC should still work, but it doesn't for some reason. Have you tried using armbian-config (and/or (the unfortunately named) nand-sata-install which can also be reached from there) to try and write the image to the eMMC? If you already overwrote the eMMC previously I guess there is nothing left to lose. I have this hardware but I just acquired an old headphone cable which I still need to fashion into a serial cable before I can proceed further. And I have yet to collect enough 'tuits' of the round variety.

I am surely no expert, but starting to wonder if something Manjaro put in their bootloader is not compatible with Armbian. This is not directly related to what NicoD was saying above, but I did want to report my experience. I have tried burning both the following images to SD card, in both cases I just get a blinking green power light: Armbian_22.08.1_Pinebook-pro_bullseye_current_5.15.63.img Armbian_22.11.1_Pinebook-pro_jammy_edge_6.0.10_xfce_desktop.img As a reminder, I have one of the newer (2022-06) production run of PineBook Pro, which comes with Manjaro pre-installed on the eMMC from PINE64. I have been unable to get Armbian working on it in any way, shape, or form ever since I bought it. So I don't use it at all (as I can't stand Manjaro nor KDE, personally). Anyway, I took a look at the eMMC (had to boot into Manjaro to do so) and it seems there are 2 partitions, one for /boot and one for /. Oh yes and BTW there is a switch by the eMMC which is supposed to bypass it (otherwise on RK3399 the boot order is SPI, eMMC, SD card), when I do that I get a steady orange light. But still no boot.[0] Even though I never use the pre-installed Manjaro image, I am still too afraid to flash anything directly to the eMMC (especially after reading many reports it doesn't work). I am going to order the special 'headphone to serial' cable that is required for the PineBook Pro, in hopes that I might be able to contribute further useful information. [0] OK, truth be told, I only tried this with the 22.08.1 image, as I didn't want to take out all those damn screws again just to get to that switch. ¯\_(ツ)_/¯

Downgrade from armbian-config, broke boot for me too Just take image from https://imola.armbian.com/archive/pinebook-pro/archive/ for example https://imola.armbian.com/archive/pinebook-pro/archive/Armbian_22.08.1_Pinebook-pro_bullseye_current_5.15.63.img.xz and don't forget "armbian-config -> System -> Freeze" for prevent kernel update

@ivan_holmes I just tried from inside armbian-config to roll back to older kernel 5.15.74-rockchip64 and it soft bricked the Pinebook Pro. how did you install 5.15.74 did you do it from inside of the armbian-config , others to switch kernel (since that did not work for me). or some other method? I now have newest Armbian Gnome SD card booted up on PbPro using the EMMC switch trick (emmc switch off, hit power button, count 2-3 seconds , push switch back on). on SD boot, Armbian Gnome , Bluetooth also does not work, using the Gui settings, no matter how many times I hit Bluetooth on, it doesn't turn on. Are there any command line options I could check?

I used Armbian Build for Pinebook Pro laptop, Armbian 22.11 Jammy XFCE Nov 30, 2022. built onto SD card. Booted to Armbian SD card used armbian-config installed Bluetooth from armbian-config I saw icon show on on the task bar , when i clicked it to start Bluetooth, it crashed. I tried Removing and Installing Bluetooth many times and shutting down and restarting laptop. the Bluetooth Icon does no appear in the task bar. and the blueman-manager and adapter do not open when I type them in the run box. Bluetooth hardware works on this pinebook Pro Laptop, but only when i tried things like Manajaro XFCE And KDE on Emmc . on manjaro, Bluetooth works on both of those and I see icon in task bar and I connected 3 different bluetooth /BLE devices. It just doesn't work for Armbian i have freshly loaded. I also tried 4 different SD cards now all with armbian. Other things run fine, Internet , wifi, etc, just not the Bluetooth. Only on Armbian, I'm not seeing the Bluetooth Icon in taskbard and Blueman keeps crashing. I have uninstalled and reinstalled it at least 10 times now using armbian-config. I also checked did armbian Updates. Nothing will bring the bluetooth icon back and I can't connect devices (bluetooth hardware seems to work fine on other distros with same laptop). is this a Bug or something I am doing wrong with the Install of Bluetooth?

bluetooth is also not working for me in newest build. I have pinebook Pro. thanks any advice?

Hi, I'm experiencing the same problem. Rolling back to kernel pinebook 5.15.74-rockchip64 made Bluetooth work again. Cheers, Ivan

This config simplifies the U-Boot build only scenario. If this switch is set, then KERNEL_ONLY is implied to "yes". The U-Boot only build also ensures proper host prepare and any other validation, the default build procedure performs. The motivation is to simplify UBOOT_ONLY building by just one compile parameter / switch, but keeping the default dependent compile procedures like e.g. host compare and other pre-config validations as is. This makes it also useful for CICD compile configurations. Changes lib/functions/main/config-prepare.sh: imply to set KERNEL_ONLY=yes, if UBOOT_ONLY is set "yes" lib/functions/main/default-build.sh: changed do_default(): added appropriateif {U-Boot compiling} else {Kernel and other compiling} fi Closes issue #4421 Test [x] Tested - see log of bash terminal output (cut in the middle to shorten for the relevant here): user@HOST:~/Projects/Armbian/build$ ./compile.sh BOARD=cubietruck BRANCH=current RELEASE=focal BUILD_MINIMAL=yes BUILD_DESKTOP=no UBOOT_ONLY=yes KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,7z SYNC_CLOCK=no [ warn ] This script requires root privileges, trying to use sudo [ o.k. ] Using config file [ /home/mhoffrog/Projects/Armbian/build/userpatches/config-example.conf ] [ o.k. ] Command line: setting BOARD to [ cubietruck ] [ o.k. ] Command line: setting BRANCH to [ current ] [ o.k. ] Command line: setting RELEASE to [ focal ] [ o.k. ] Command line: setting BUILD_MINIMAL to [ yes ] [ o.k. ] Command line: setting BUILD_DESKTOP to [ no ] [ o.k. ] Command line: setting UBOOT_ONLY to [ yes ] [ o.k. ] Command line: setting KERNEL_CONFIGURE to [ no ] [ o.k. ] Command line: setting COMPRESS_OUTPUTIMAGE to [ sha,gpg,7z ] [ o.k. ] Command line: setting SYNC_CLOCK to [ no ] [ .... ] Extension being added [ sunxi-tools :: added by functions/cli/cli-entrypoint.sh:105 -> functions/main/config-prepare.sh:140 -> functions/configuration/main-config.sh:174 -> config/sources/families/sun7i.conf:1 -> config/sources/families/include/sunxi_common.inc:1 ] [ o.k. ] Extension manager [ processed 3 Extension Methods calls and 3 Extension Method implementations ] [ o.k. ] Using user configuration override [ /home/mhoffrog/Projects/Armbian/build/userpatches/lib.config ] [ o.k. ] Preparing [ host ] [ o.k. ] Build host OS release [ focal ] [ .... ] Installing build dependencies [ o.k. ] Checking for external GCC compilers [ o.k. ] Downloading sources [ o.k. ] Checking git sources [ u-boot v2022.07 ] [ .... ] Cleaning .... [ 93 files ] [ o.k. ] Checking git sources [ linux-mainline/5.15 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.gitorigin/linux-5.15.y ] [ .... ] Switch v5.15.77 = da3267ca3045f6958b56cbd9d185b68f7e14216d [ o.k. ] Checking git sources [ sunxi-tools master ] [ .... ] Up to date [ o.k. ] Cleaning /home/mhoffrog/Projects/Armbian/build/output/debs for [ cubietruck current ] [ o.k. ] Cleaning [ u-boot/v2022.07 ] [ o.k. ] Compiling u-boot [ 2022.07 ] [ o.k. ] Compiler version [ arm-none-linux-gnueabihf-gcc 9.2.1 ] [ .... ] Checking out to clean sources [ o.k. ] Cleaning [ u-boot/v2022.07 ] [ o.k. ] Started patching process for [ u-boot sunxi-cubietruck-current ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-sunxi ] [ o.k. ] * [l][c] 0000-sunxi-allwinner-a10-spi-driver.patch [ o.k. ] * [l][c] 0001-add-orange-pi-3-lts-support.patch [ o.k. ] * [l][c] Bananapro-01-add-hdmi-de-reg_ahci_5v.patch [ o.k. ] * [l][c] Bananapro-02-add-AXP209-regulators.patch [ o.k. ] * [l][c] Merrii_Hummingbird_A20.patch [ o.k. ] * [l][c] add-a20-optional-eMMC.patch [ o.k. ] * [l][c] add-a64-olinuxino-emmc-support.patch [ o.k. ] * [l][c] add-a64-olinuxino-spl-spi.patch [ o.k. ] * [l][c] add-awsom-defconfig.patch [ o.k. ] * [l][c] add-emmc_support_to_neo1_and_2.patch [ o.k. ] * [l][c] add-h616-THS-workaround.patch [ o.k. ] * [l][c] add-nanopi-air-emmc.patch [ o.k. ] * [l][c] add-nanopi-duo.patch [ o.k. ] * [l][c] add-nanopi-m1-plus2-emmc.patch [ o.k. ] * [l][c] add-nanopi-neo-core.patch [ o.k. ] * [l][c] add-orangepi-plus2-emmc.patch [ o.k. ] * [l][c] add-orangepi-zero-plus-pxe-support.patch [ o.k. ] * [l][c] add-orangepi-zero-usb-boot-support.patch [ o.k. ] * [l][c] add-orangepi-zeroplus2_h3.patch [ o.k. ] * [l][c] add-sunvell-r69.patch [ o.k. ] * [l][c] add-xx-boot-auto-dt-select-neo2.patch [ o.k. ] * [l][c] add-xx-nanopi-k1-plus-emmc.patch [ o.k. ] * [l][c] add-xx-nanopineocore2.patch [ o.k. ] * [l][c] add-zeropi.patch [ o.k. ] * [l][c] adjust-default-dram-clockspeeds.patch [ o.k. ] * [l][c] adjust-small-boards-cpufreq.patch [ o.k. ] * [l][c] enable-autoboot-keyed.patch [ o.k. ] * [l][c] enable-ethernet-orangepiprime.patch [ o.k. ] * [l][c] enable-r_pio-gpio-access-h3-h5.patch [ o.k. ] * [l][c] fdt-setprop-fix-unaligned-access.patch [ o.k. ] * [l][c] fix-sunxi-nand-spl.patch [ o.k. ] * [l][c] fix-usb1-vbus-opiwin.patch [ o.k. ] * [l][c] h3-Fix-PLL1-setup-to-never-use-dividers.patch [ o.k. ] * [l][c] h3-enable-power-led.patch [ o.k. ] * [l][c] h3-set-safe-axi_apb-clock-dividers.patch [ o.k. ] * [l][c] lower-default-DRAM-freq-A64-H5.patch [ o.k. ] * [l][c] pinebook-add-rare-panel-support.patch [ o.k. ] * [l][c] sun8i-set-machid.patch [ o.k. ] * [l][c] sunxi-boot-splash.patch [ o.k. ] * [l][c] sunxi_H616_GPU_enable_hack.patch [ o.k. ] * [l][c] xxx-disable-de2-to-improve-edid-detection.patch HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o YACC scripts/kconfig/zconf.tab.c ... CAT u-boot-dtb.bin COPY u-boot.dtb COPY u-boot.bin MKIMAGE u-boot.img MKIMAGE u-boot-dtb.img BINMAN all [ o.k. ] Building deb [ linux-u-boot-current-cubietruck_22.11.0-trunk_armhf.deb ] [ o.k. ] U-Boot build done [ @host ] [ o.k. ] Target directory [ /home/mhoffrog/Projects/Armbian/build/output/debs/ ] [ o.k. ] File name [ linux-u-boot-current-cubietruck_22.11.0-trunk_armhf.deb ] [ o.k. ] Runtime [ 0 min ] [ o.k. ] Repeat Build Options [ ./compile.sh BOARD=cubietruck BRANCH=current RELEASE=focal BUILD_MINIMAL=yes BUILD_DESKTOP=no UBOOT_ONLY=yes KERNEL_ONLY=yes KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,7z ] user@HOST:~/Projects/Armbian/build$ Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I will create appropriate pull request to the documentation in separate Armbian doc repo [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Understand, but you will need to workaround each time ... He hasn't showed up for a while, but we recreated and tested images last night https://www.armbian.com/pinebook-pro/ (kernel 6.0.6) and they boot normally. From SD and from (some) eMMC. It is Pine64 responsibility to deal with low level problems. Its only our good will if we invest into their business. Do they deserve? https://blog.brixit.nl/why-i-left-pine64/

Thanks. However, I have a working solution (using the Kali dtb) and I have no motivation to go chasing this down... I'm not an Armbian dev and don't have the time to put into this. I would hope that the Pinebook Pro maintainer would be able to do it.

I need to know if those that were rebuilt works: https://stpete-mirror.armbian.com/dl/pinebook-pro/archive/

Only main link works until syncing is not done. https://imola.armbian.com/dl/pinebook-pro/archive/

@WernerImages seem to be not available here. Always either 404 or https://armbian.hosthatch.com/dl/pinebook-pro/archive/Armbian_22.08.10_Pinebook-pro_jammy_edge_6.0.6_gnome_desktop.img.xz when I click one of the download links. Downloading from archives image from 22/10/02.

Updated images are ready https://www.armbian.com/pinebook-pro/ (just kernel 6.x / EDGE)