Pinebook Pro no boot progress indication

Hi guys,

At some point (after an update, I surmise), I stopped getting the manjaro logo when booting my Pinebook Pro. It pretty much gives me a black screen (often with a single blinking cursor, i.e. blank text mode) until lightdm starts and shows the login screen. (Everything else works fine)

Not sure where to start troubleshooting (or even which package provides the boot screen). Any pointers?

Much thanks, as always to this wonderful community.

inxi output
$ inxi -Fxxxza --no-host
System:    Kernel: 5.13.4-1-MANJARO-ARM aarch64 bits: 64 compiler: gcc v: 10.2.0 
           parameters: initrd=/initramfs-linux.img console=tty1 console=ttyS2,1500000 root=LABEL=ROOT_MNJRO rw rootwait 
           Desktop: i3 4.19.1 info: i3bar vt: 7 dm: LightDM 1.30.0 Distro: Manjaro ARM base: Arch Linux 
Machine:   Type: ARM Device System: Pine64 Pinebook Pro details: N/A serial: <filter> 
Battery:   ID-1: cw2015-battery charge: 68% condition: N/A volts: 3.9 min: N/A model: N/A type: Li-ion serial: N/A 
           status: Discharging 
CPU:       Info: 6-Core (2-Die) model: N/A variant-1: cortex-a53 variant-2: cortex-a72 bits: 64 type: MCP MCM arch: ARMv8 
           family: 8 model-id: 0 stepping: 4 
           features: Use -f option to see features bogomips: 0 
           Speed: 1200 MHz min/max: 408/1416:1800 MHz Core speeds (MHz): 1: 408 2: 408 3: 408 4: 408 5: 1200 6: 1200 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 mitigation: __user pointer sanitization 
           Type: spectre_v2 mitigation: Branch predictor hardening 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: display-subsystem driver: rockchip_drm v: N/A bus-ID: N/A chip-ID: rockchip:display-subsystem 
           class-ID: display-subsystem 
           Device-2: rk3399-mali driver: panfrost v: kernel bus-ID: N/A chip-ID: rockchip:ff9a0000 class-ID: gpu 
           Device-3: Microdia HP Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-1.2:3 chip-ID: 0c45:6321 
           class-ID: 0e02 
           Display: x11 server: X.Org 1.20.12 driver: loaded: fbturbo display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23") 
           Monitor-1: default res: 1920x1080 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: simple-audio-card driver: asoc_simple_card bus-ID: N/A chip-ID: simple-audio-card:es8316-sound 
           class-ID: es8316-sound 
           Device-2: simple-audio-card driver: N/A bus-ID: N/A chip-ID: simple-audio-card:hdmi-sound class-ID: hdmi-sound 
           Sound Server-1: ALSA v: k5.13.4-1-MANJARO-ARM running: yes 
           Sound Server-2: JACK v: 0.125.0 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
           Sound Server-4: PipeWire v: 0.3.32 running: no 
Network:   Message: No ARM data found for this feature. 
           IF-ID-1: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: rk3399-uart driver: dw_apb_uart bus-ID: N/A chip-ID: rockchip:ff180000 class-ID: serial 
           Report: rfkill ID: hci1 rfk-id: 1 state: down bt-service: enabled,running rfk-block: hardware: no software: yes 
           address: see --recommends 
           Report-ID: ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes 
           address: N/A 
Drives:    Local Storage: total: 58.24 GiB used: 24.27 GiB (41.7%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/mmcblk2 maj-min: 179:0 vendor: SanDisk model: DA4064 size: 58.24 GiB block-size: physical: 512 B 
           logical: 512 B rotation: SSD serial: <filter> rev: 0x8 scheme: MBR 
Partition: ID-1: / raw-size: 58 GiB size: 57.03 GiB (98.33%) used: 24.23 GiB (42.5%) fs: ext4 dev: /dev/mmcblk2p2 
           maj-min: 179:2 
           ID-2: /boot raw-size: 213.6 MiB size: 213.4 MiB (99.89%) used: 47 MiB (22.0%) fs: vfat dev: /dev/mmcblk2p1 
           maj-min: 179:1 
Swap:      Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
           ID-1: swap-1 type: zram size: 5.66 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 
Sensors:   System Temperatures: cpu: 40.6 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 190 Uptime: 8m Memory: 3.77 GiB used: 964.5 MiB (25.0%) Init: systemd v: 249 tool: systemctl Compilers: 
           gcc: 10.2.0 Packages: pacman: 1035 lib: 262 Shell: Bash v: 5.1.8 running-in: lxterminal inxi: 3.3.05 

That’s because as of kernel 5.13, we stopped patching in the unmaintained kernel bootsplash to our kernel.

To change to the currently used bootsplash (plymouth) see the guide in this post:

1 Like

Forgive my unfamiliarity with this setup, but how do I edit the boot parms? It doesn’t seem to be using grub.

The only file I found with a reference to splash within /boot was /boot/extlinux/extlinux.conf.

Is there a command I need to run once I edit that file?

Much thanks.

The quote says which command to run to enable the theme.

And yes, the boot script is extlinux.conf on the Pinebook Pro.

Thanks. That seems to have fixed it for me.

The only issue I have now is that I get a momentary error message while booting. I don’t know if it’s important:

1.4074571 OF: graph: no port node found in /i2ceff3d0000/fusb30x@22

2.077711] rockchip-pcie f8000000.pcie: PCIe link training gen1 'timeout!
2.384831] rockchip-dp ff970000.edp: no DP phy configured


These are common informational stuff on the Pinebook Pro. It was just hidden before.

You can hide it all again, by removing the console=tty3 part in your extlinux.conf.

1 Like

Thank you!

I had one other minor issue, and I wasn’t sure whether I should post it here, or on the pine64 forum.

Whenever I do a reboot, it boots up into a blurry white screen. A hard shut down and start up again always fixes it.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.