Search the Community

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

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

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!

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)

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.

We are facing an issue on Pinebook Desktop A64 HDMI under 5.0.y ... It is booting, but as soon as HDMI is switching from plain text console to graphic, the screen stays blank ... I didn't get chance to investigate, I need help here from any Devs who has a Pinebook !

Hello! I'm using Armbian Stretch for 1080P Pinebook A64. I've installed Armbian Stretch about 2 months ago, when it was still "Unsupported" and in-development. Now, however, it's supported. Currently, I'm on Armbian Stretch 5.60 and dev branch. I would like to update to 5.69 and next branch. However, from armbian-config, I'm only able to go from stable to nightly build (5.68, but still dev branch). Moreover, I can't select next kernel from Other menu. Is there a way to switch branches (barring re-flashing from latest image)?

Hi all. Last weekend PINE64 was on FOSDEM with many new products. The PineBook Pro with RK3399. The new designed PINE H64 with the H6, now with wifi on-board and a small form-factor. That one's comming out next week. The PinePhone. A prototype of the PinePhone with an A64 SoC and 2GB of RAM. The PineCam. A multi-funtional network camera. A new SNES case. Exciting times to come with all that. I've made a video about it all. You can see it here. Greetings, NicoD

Armbian Legacy 5.56 Kernel 3.10 boots and installs to the eMMC (as long as ext2fs is picked). Armbian Dev 5.56 Kernel 4.19 does not boot from the SD Card at all (power LED and black screen). I don't have the serial console adapter (yet) so I don't know if there is something useful there.

Hi. My PBP is very new; I bought it within the last couple of months. I decompiled the two .dtb files using dtc, but there are a lot of differences and I'm a bit out of my depth here. Also, it's probably better to look at the source files rather than the decompiled .dtbs because they will have comments and symbols. Anyway, for what it is worth, I have attached the two decompiled dtb files. The kali one works and the armbian one does not, when booting from the emmc. armbian-rk3399-pinebook-pro.dts kali-linux-rk3399-pinebook-pro.dts

So, just to close this out: Writing directly to the emmc did not work. The system was unable to find the root file system. It had the wrong UUID somehow, so I changed it with tune2fs. Still no luck. I then replaced the rk3399-pinebook-pro.dtb with the one that ships with Manjaro. That booted, but the laptop screen did not come on. I could only access it via the serial port. Finally, I saw this post: https://forum.pine64.org/showthread.php?tid=17215 When I replaced rk3399-pinebook-pro.dtb with the version from Kali Linux, it booted, I got the display, and everything worked. I now finally have Armbian running from the emmc, albeit with the device tree blob from Kali Linux.

UPDATE: For whatever reason, /boot/boot.scr was corrupt; it had a bunch of garbage prior to the "# DO NOT EDIT THIS FILE" line. I removed that garbage and now the Pinebook PRO boots... into Manjaro. Here's the relevant serial console output: Scanning mmc 1 for bootable partitions... Scanning mmc 1:1 for extlinux or boot scripts... Found U-Boot script /boot/boot.scr 3113 bytes read in 19 ms (159.2 KiB/s) ## Executing script at 00500000 Wrong image format for "source" command SCRIPT FAILED: continuing... EDIT: Meh, I guess the junk is needed as it's a legacy uImage. So that's not it. But obviously the junk at the top of boot.scr is not the correct junk.

In the FriendlyARM thread http://www.friendlyarm.com/Forum/viewtopic.php?f=53&amp;t=1427&amp;p=5685#p5685 we did try to use A64 images from the Pine64 or the BananaPi M64 with the NanoPi A64. The last times we did that with less success - OK Sytem is running but Network/Sound has to added via USB. No suppport for the onboard devices But today a user did wrote that - with the actual stable Pine64-image ( Armbian_5.69_Pine64_Debian_stretch_next_4.19.13 ) WiFi is useable. So I flasded the Pine64-image to a MicroSDCard and did boot. Additiionally I did see with "aplay -l" the HDMI and the analog Sound-device. But ethernet isnt "connected" right via the .dtb armbian inside can see the ethernet-part of the SoC (set IP and see MAC) and the external RTL8122E Phy blinks the Link and Transfered-Packets via LED.... My first idea was to edit the Pine64 DTB to match the NanoPI A64 DTB in the ethernet-part - but with these Pins & PHandle's I did get stuck BUT my second idea did work much better, because in the armbian-build-system I also did see the sun50i-a64-nanopi-a64.dtb So I checked the board-config-file for the pine64.conf ( under ./build/config/boards/ ) - there is an entry for a defconfig file and the armbin-build-system has also a defonfig file for the nanopi-a64 ./build/cache/sources/u-boot/v2018.11/configs/nanopi_a64_defconfig while the NanoPi A64 isnt (official) supported by the Meneu-System of the armbian-build-system. So I copied ./build/config/boards/pine64.conf to ./build/config/boards/nanopia64.conf and did edit it like in the following way: # A64 quad core 512MB-2GB SoC GBE BOARD_NAME="NanoPiA64" BOARDFAMILY="sun50iw1" BOOTCONFIG_DEFAULT="sun50iw1p1_config" BOOTCONFIG="nanopi_a64_defconfig" # MODULES="sunxi_codec sunxi_i2s sunxi_sndcodec 8723bs" MODULES_NEXT="" # KERNEL_TARGET="default,next,dev" CLI_TARGET="bionic,stretch:next" DESKTOP_TARGET="xenial:default" # CLI_BETA_TARGET="" DESKTOP_BETA_TARGET="" and did compile for the NanoPi A64 with ./compile.sh EXPERT="yes" in ./build/ Now I could select the NanoPi A64 (falsely) as supported board and did select DEV (armbian 5.71 with Kernel 4.20) I did build the console and the Desktop-version. In the console-version I was happy to see eth0 & wlan0 working, but the HDMI and analog soundsystem is missing (which was visible in Pine64 next 4.19.13) So there was no need for a RTL8211E-driver (because its only a PHY) like I did read before at http://linux-sunxi.org/Ethernet#Realtek_RTL8211E In the Desktop-version the GUI did start without problems (not fast, but useable) - like on a older pinebook (a64) build Maybe DEV was "too much"? I will try the NEXT for my NanoPi A64 File Or maybe the nanopi A64 dtb isnt correct on the "sound-part"?

Hi, just a quick sanity check - is install to eMMC on pinebook known to be working (with recent Armbian images from the wip section), and is nand-sata-install the right way to do it? It just occurred to me that I might be spinning my wheels trying to figure out something that just isn't ready yet Thanks, James