Search the Community

One minute ago ..... on Pinebook buster .... ansible@pinebook:~$ LANG=C LANGUAGE=C sudo apt update Hit:1 http://ftp.fr.debian.org/debian buster-backports InRelease Hit:2 http://ftp.debian.org/debian buster InRelease Hit:3 http://security.debian.org buster/updates InRelease Hit:4 http://ftp.fr.debian.org/debian buster-updates InRelease Ign:5 http://ftp.debian.org/debian stretch InRelease Hit:7 http://ftp.debian.org/debian stretch Release Ign:6 https://apt.armbian.com buster InRelease Err:8 https://apt.armbian.com buster Release Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 193.40.103.96 443] Reading package lists... Done W: http://apt.armbian.com/dists/buster/InRelease: No system certificates available. Try installing ca-certificates. W: http://apt.armbian.com/dists/buster/Release: No system certificates available. Try installing ca-certificates. E: The repository 'http://apt.armbian.com buster Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

have the same kernel and we don't support 3rd party hardware if its not specifically declared. As you can see on the download pages ... some 3rd party works, for else is everything but switching it on. Modern kernel is basically written from scratch by community. And if we (community) didn't develop that, support for that LCD does not exits. Displays are not my field so I can't give you any useful tip except ... have you tried to boot images for Pinebook perhaps?

hi, you need to overid the dtp file in here ll /boot/dtb-5.1.7-sunxi64/allwinner/ total 968 drwxr-xr-x 3 root root 4096 Jun 15 12:19 ./ drwxr-xr-x 3 root root 4096 Jun 15 12:21 ../ drwxr-xr-x 2 root root 4096 Jun 15 12:19 overlay/ -rw-r--r-- 1 root root 33668 Jun 14 23:52 sun50i-a64-amarula-relic.dtb -rw-r--r-- 1 root root 35345 Jun 14 23:52 sun50i-a64-bananapi-m64.dtb -rw-r--r-- 1 root root 34228 Jun 14 23:52 sun50i-a64-nanopi-a64.dtb -rw-r--r-- 1 root root 35180 Jun 14 23:52 sun50i-a64-olinuxino.dtb -rw-r--r-- 1 root root 35776 Jun 14 23:52 sun50i-a64-orangepi-win.dtb -rw-r--r-- 1 root root 34570 Jun 14 23:52 sun50i-a64-pine64-lts.dtb -rw-r--r-- 1 root root 35082 Jun 14 23:52 sun50i-a64-pine64-plus.dtb -rw-r--r-- 1 root root 35004 Jun 14 23:52 sun50i-a64-pine64.dtb -rw-r--r-- 1 root root 36584 Jun 14 23:52 sun50i-a64-pinebook.dtb -rw-r--r-- 1 root root 34582 Jun 14 23:52 sun50i-a64-sopine-baseboard.dtb -rw-r--r-- 1 root root 36526 Jun 14 23:52 sun50i-a64-teres-i.dtb -rw-r--r-- 1 root root 31397 Jun 14 23:52 sun50i-h5-bananapi-m2-plus-v1.2.dtb -rw-r--r-- 1 root root 31004 Jun 14 23:52 sun50i-h5-bananapi-m2-plus.dtb -rw-r--r-- 1 root root 29328 Jun 14 23:52 sun50i-h5-emlid-neutis-n5-devboard.dtb -rw-r--r-- 1 root root 29798 Jun 14 23:52 sun50i-h5-libretech-all-h3-cc.dtb -rw-r--r-- 1 root root 32108 Jun 14 23:52 sun50i-h5-nanopi-k1-plus.dtb -rw-r--r-- 1 root root 29396 Jun 14 23:52 sun50i-h5-nanopi-m1-plus2.dtb -rw-r--r-- 1 root root 29316 Jun 14 23:52 sun50i-h5-nanopi-neo-core2.dtb -rw-r--r-- 1 root root 29412 Jun 14 23:52 sun50i-h5-nanopi-neo-plus2.dtb -rw-r--r-- 1 root root 29061 Jun 14 23:52 sun50i-h5-nanopi-neo2-v1.1.dtb -rw-r--r-- 1 root root 29065 Jun 14 23:52 sun50i-h5-nanopi-neo2.dtb -rw-r--r-- 1 root root 29991 Jun 14 23:52 sun50i-h5-orangepi-pc2.dtb -rw-r--r-- 1 root root 29918 Jun 14 23:52 sun50i-h5-orangepi-prime.dtb -rw-r--r-- 1 root root 29138 Jun 14 23:52 sun50i-h5-orangepi-zero-plus.dtb -rw-r--r-- 1 root root 29143 Jun 14 23:52 sun50i-h5-orangepi-zero-plus2.dtb -rw-r--r-- 1 root root 27608 May 30 22:14 sun50i-h6-orangepi-3.dtb <---------------------------------------- -rw-r--r-- 1 root root 27359 Jun 14 23:52 sun50i-h6-orangepi-lite2.dtb -rw-r--r-- 1 root root 26874 Jun 14 23:52 sun50i-h6-orangepi-one-plus.dtb -rw-r--r-- 1 root root 27617 Jun 14 23:52 sun50i-h6-pine-h64.dtb

Installed the 5.1.6 -dev build. Same no backlight with the LCD, however, reverting https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/xxx-pinebook-revert-pwm-polairity-TEMP-WORKAROUND.patch and then adding in the https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/need-to-check/fix-pinebook-backlight.patch both seem to work here, working backlight with the LCD. Tested multiple reboots as well as startup from shutting down.

So, because I got on the idea of "is the hdmi broken" - I took the tape off... it would appear that with the Armbian 5.1.5 kernel..... hdmi output is happening... Boot output goes to the hdmi monitor, and not the pinebook lcd, however the login is definitely on the pinebook's lcd - blindly logging in works, but the lcd is still considered primary, so the menu and so forth is on the pinebook itself, the external hdmi monitor does show a background image and I can move the cursor around on it. Interestingly enough, not distorted at all, although all it has is the background image. The LCD backlight still doesn't appear to be powering on. Looking through the patches, I saw https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/need-to-check/fix-pinebook-backlight.patch - and figured I'd give it a shot... with that applied, which removes the "backlight:" the lcd flickers twice during boot, and then about 2 or 3 minutes later, the backlight turns on (sadly, nothing seems to be in dmesg output) - however, as soon as I attempted to log in, the lcd backlight shut off again. Unfortunately, I haven't been able to reproduce that, it only happened that one time. I definitely think something is up when hdmi is enabled now, so that's where I'll dig. I apologize if I'm updating too often, I'm kind of using this as a stream of consciousness as I work through the patches.

A bit more digging - taking the dts from 5.1.5/5.1.6 without any changes has a working backlight (and audio!) - so it's definitely something in the patches applied on Arabian. I'm going to start digging through them. I'm not sure if it matters or not, but my Pinebook showed up with tape over the hdmi port, could it be that hdmi is completely broken with the 1080p lcd on 11"?

That indeed isn't good at all. I'm from Europe so I haven't got a clue where to buy when you're from South-America. It's this PSU. https://www.cloudmedia.com/?product=rock64-pinebook-pine-h64-5v-3a-switching-power-supply I'm using a different one for it, a 4A EU PSU. But 3A should be sufficient. This is what you need to look for : 5V (at least) 3A Type H 3.5mm OD/1.35mm ID barrel ‘coaxial’ type I'd trow away that PSU you've got before it damages anything(hd/sd-card). I've seen a lot of undervolting in my times but under 4V is very rare. With a good PSU/cable you should never go under 4.8V. (tell that to the raspberry pi foundation) Good luck, greetings.

Double check if this is not solo a problem of our patch set, which it is different than mainline in some details. Especially this patch https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/xxx-pinebook-revert-pwm-polairity-TEMP-WORKAROUND.patch which naming tells things will be changed, but we didn't get that far yet to sort things out ...

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.

I don't have a pinebook, so not sure if this is helpful... someone should give it a try... GETTING A VIRTUAL TERMINAL Linux provides six virtual consoles (text-based command-line interfaces). Simultaneously, pressing the Control (Ctrl) and Alternate (Alt) keys with any of the functions keys from F1 through F6. For example, press Ctrl-Alt-F1. Return to the graphics screen by pressing Ctrl-Alt-F7.

From what I know, Sleep/Hibernate works only on Legacy, since it rely on AR100 ARISC co-processor, not yet supported on Mainline. That is true for all AllWinner SoC, not only H6 ... For more details, here is http://linux-sunxi.org/AR100 For example, it is well known that Pinebook with Mainline, doing sleep simply returns to normal desktop, without even doing a reboot.

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