Search the Community

Yes. It seems not all boards are affected ... I tested only one Lime and Pinebook IIRC and found no troubles. Reverting back to BOOTSOURCE='https://github.com/anarsoul/u-boot-pine64' BOOTBRANCH='branch:pinebook-wip-20181109' seems like a fix (workaround). Still testing and looking into ...

This is interesting... https://www.cnx-software.com/2019/05/04/pinebook-pro-arm-laptop-video-demo/

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!

root@ICS-Pine64:~# fdtdump / boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb | grep erra **** fdtdump is a low-level debugging tool, not meant for general use. **** If you want to decompile a dtb, you probably want **** dtc -I dtb -O dts <filename> Couldn't open blob from '/ boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb': No such file or directory FATAL ERROR: could not read: / boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb root@ICS-Pine64:/boot/dtb/allwinner# ls overlay sun50i-h5-nanopi-k1-plus.dtb sun50i-a64-amarula-relic.dtb sun50i-h5-nanopi-m1-plus2.dtb sun50i-a64-bananapi-m64.dtb sun50i-h5-nanopi-neo2.dtb sun50i-a64-nanopi-a64.dtb sun50i-h5-nanopi-neo2-v1.1.dtb sun50i-a64-olinuxino.dtb sun50i-h5-nanopi-neo-core2.dtb sun50i-a64-orangepi-win.dtb sun50i-h5-nanopi-neo-plus2.dtb sun50i-a64-pine64.dtb sun50i-h5-orangepi-pc2.dtb sun50i-a64-pine64-lts.dtb sun50i-h5-orangepi-prime.dtb sun50i-a64-pine64-plus.dtb sun50i-h5-orangepi-zero-plus2.dtb sun50i-a64-pine64-plus.dtb-ORIGINAL sun50i-h5-orangepi-zero-plus.dtb sun50i-a64-pinebook.dtb sun50i-h6-orangepi-lite2.dtb sun50i-a64-sopine-baseboard.dtb sun50i-h6-orangepi-one-plus.dtb sun50i-a64-teres-i.dtb sun50i-h6-pine-h64.dtb sun50i-h5-libretech-all-h3-cc.dtb Getting an error here: root@ICS-Pine64:/boot# git-work/dtc/dtc -I dtb -O dts -o sun50i-a64-pine64-plus.dts /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb -bash: git-work/dtc/dtc: No such file or directory root@ICS-Pine64:/boot/dtb/allwinner# git-work/dtc/dtc -bash: git-work/dtc/dtc: No such file or directory

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.

I got here from the lst compile Welcome to ARMBIAN 5.78 user-built Debian GNU/Linux 9 (stretch) 5.0.7-sunxi64 package bsp-kernel[5.78] u-boot[5.78] dtb[5.78] firmware[5.77] config[5.78] Linux npi-a64 5.0.7-sunxi64 #5.78 SMP Wed Apr 10 09:20:27 +03 2019 aarch64 GNU/Linux defconfig for this image seems to come from ./build/cache/sources/u-boot/pinebook-wip-20181109/configs/nanopi_a64_defconfig but also here only the lower usb-port does work also upper-port-usb doesnt work at the normal mainline-image ARMBIAN 5.78 user-built Debian GNU/Linux 9 (stretch) 4.19.25-sunxi64 Linux nanopia64 4.19.25-sunxi64 #5.78 SMP Wed Apr 10 13:20:03 +03 2019 aarch64 GNU/Linux

@martinayotte Thank you for the suggestion. I changed to same, rebooted with no luck. Anything else I'm missing like do another make or something? For reference herewith my armbianEnv.txt: verbosity=1 console=both disp_mode=720p60 camera_type=none pine64_lcd=off rootdev=UUID=2a9ed406-bd1a-46ce-b16b-908ee24b8eeb rootfstype=ext4 overlay_prefix=sun50i-a64 overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=0 param_spidev_max_freq=100000000 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u And the contents of my dtb: dtb-3.10.107-pine64 sun50iw1p1-nanopim64.dtb sun50iw1p1-pine64.dtb sun50iw1p1-pine64so.dtb sun50iw1p1-bananapim64.dtb sun50iw1p1-olinuxino-a64.dtb sun50iw1p1-pine64-pinebook.dtb sun50iw1p1-soc.dtb sun50iw1p1-fpga.dtb sun50iw1p1-orangepiwin.dtb sun50iw1p1-pine64-plus.dtb sun50iw1p1-teres.dtb Lastly The test I do to see if it is available is to check /dev for some flavour of SPI?

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 !

As always the question is what you want to do with it I'm typing this on a Pinebook which is fast enough for what I use it for. My Orange Pi Zero is fast enough for file and network services that I use it for. My RPi Zero is fast enough for running RISC OS. It's all down to your use case.

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

There is a RTL8723BS on OrangePiPrime (and in Pinebook too if I recall correctly), and it is working fine with both NEXT or DEV images.

Doesn't seems to work on Pinebook with Armbian 4.20.y. I will probably check with an Ayufan image later ...

My last update on this issue in case someone is working to get sound on A64 (>= 4.20). I tried every patch out there, triple checked the code , same situation, no sound. I must have missed something or overlooked something. I finally tried Vasily's kernel and for my surprise no sound. Last hope, i tried Vasily ARCH img, no luck, no sound even on Pine64. Maybe it works on Pinebook,....

Any objections to merge/move H5 and A64 from https://forum.armbian.com/forum/18-allwinner-a64-h5-h6/ to https://forum.armbian.com/forum/27-mainline-kernel/ ? Before Allwinner A64, H5 & H6 Pine64, H64, Pinebook, Olimex Teres, Olinuxino A64, Orange Pi PC2, Zero+ 2 H5, Prime, Win; NanoPi Neo 2, Neo+ 2, M1 Plus 2, FriendlyElec K1+ After Allwinner H6 Pine H64, Orange Pi One +, Lite2

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"?

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)?

You need a special version for that one to work ... but just for trying. Nobody will waste time on kernel 3.10.y Its all written here: https://www.armbian.com/pinebook-a64/ While with modern kernel - one SD card works on both: Today/tomorrow images will be updated and tested once again.

This one from the website downloads https://dl.armbian.com/pinebook-a64/Debian_stretch_dev_desktop.7z It boots up fine now that I swapped to a 1920x1080 LCD. Before I didn't even see the boot text messages, now I do and it starts all the way into the desktop. Of course now the Armbian Bionic Legacy Kernel 3.10 that used to work, no longer does but I kind of expected that.

Did you try to boot the console or the Desktop version? I did find armbian 5.56 only with kernel 3.10 in the downloads. This is the "oldest" 4.19 download (but with armbian 5.67): https://dl.armbian.com/pinebook-a64/archive/Armbian_5.67_Pinebook-a64_Debian_stretch_dev_4.19.2_desktop.7z The latest 5.59 nightly is at kernel 4.18: https://dl.armbian.com/pinebook-a64/nightly/Armbian_5.59.180830_Pinebook-a64_Debian_stretch_dev_4.18.5_desktop.7z Which download-link did you use?

Mine is also the Non-HD 1366x768 Pinebook

Today I compiled DEV for the Pinebook via the armbian-build-system and the created stretch-Desktop-image ARMBIAN 5.68 user-built Debian GNU/Linux 9 (stretch) 4.19.12-sunxi64 Linux pinebook 4.19.12-sunxi64 #5.68 SMP Mon Jan 7 12:43:14 +03 2019 aarch64 GNU/Linux did boot without problems from my sdcard on my Non-HD-Pinebook Also did install & boot from eMMC (did use ext4-format)

I see. It will work this way: https://github.com/armbian/build/blob/tvboxes/config/packages/99-board/dedicated/pinebook-a64/armbian.postinst.bash

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.

Haven't found the problem either, but I applied a dirty fix that we have at least screen. https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/xxx-pinebook-revert-pwm-polairity-TEMP-WORKAROUND.patch This gives screen but kills pwm control. https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/Revert_BT_HCIUART_RTL_ACPI_dependency.patch Fix to make bluetooth part compilable, but I could not get it working yet.

Outside of the PineBook and the RPi based items... ChromeOS - Samsung Chromebook Plus (1st gen) and Acer R13 (CB5-312T-K5X4) support Crostini (Linux KVM as guest OS running Debian) and Android's Google Play Store... both of these are ARM based, and there are other ARM chromebooks that might also be useful...