06-10-2020, 01:30 PM
In order to be able to boot from SD card I used "the U-Boot update script from the mrfixit2001 Debian" mentioned in the Pinebook Pro wiki, so I guess I have that U-Boot loader on my eMMC now. The strange thing now is: in at least a dozen attempts I could always boot the kernel, but often it does not find the eMMC anymore, and drops me to a shell:
I've seen different patterns, but to the same effect:
Looking for others with the same problem, and for possible solutions, I found this post in the Manjaro Linux Forum:
manjaro won't boot, eMMC, pinebookpro (Post #56)
Indeed after connecting my Pinebook Pro to the power cord I could boot from eMMC again, after several failed attempts (and having opened the case twice, to check the eMMC being attached properly).
Some speculation: The battery was at only about 30% - maybe it is a power issue?
Obviously it is not the Debian kernel, that is responsible. At least once I booted Manjaro (with its 5.6 kernel) from SD card and could see that /dev/mmcblk2 was not there, only /dev/mmcblk1 (the sd card).
Once, when on battery, the system even "lost" the eMMS it was running from. See the attached photograph for the kernel messages from that crash:
emmc_loss_pbp.jpg (Size: 399.74 KB / Downloads: 502)
Is anyone else here having similar issues? Any suggestions as to what I could do (apart from keeping the power adapter with me, or a backup system on sd card)? Maybe getting an NVMe and running a system from that would help?
Code:
[ 2.127663] debugfs: File ':interrupt-controller@fee00000' in directory 'doma
ins' already present!
[ 2.xxxxxx] debugfs: File ':interrupt-controller@fee00000' in directory 'doma
ins' already present!
[ 2.xxxxxx] debugfs: File ':interrupt-controller@fee00000' in directory 'doma
ins' already present!
[ 2.xxxxxx] debugfs: File ':interrupt-controller@fee00000' in directory 'doma
ins' already present!
[ 2.xxxxxx] debugfs: File ':interrupt-controller@fee00000' in directory 'doma
ins' already present!
[ 2.127790] debugfs: File ':interrupt-controller@fee00000' in directory 'doma
ins' already present!
[ 2.720138] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 3.023522] OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
[ 3.185664] vcc_sdio: unsupportable voltage range: 3300000-3000000uV
[ 3.317248] mmc2: mmc_select_hs200 failed, error -110
[ 3.317730] mmc2: error -110 whilst initialising MMC card
[ 3.4xxxxx] mmc2: mmc_select_hs200 failed, error -110
[ 3.4xxxxx] mmc2: error -110 whilst initialising MMC card
[ 3.5xxxxx] mmc2: mmc_select_hs200 failed, error -110
[ 3.5xxxxx] mmc2: error -110 whilst initialising MMC card
[ 3.7xxxxx] mmc2: mmc_select_hs200 failed, error -110
[ 3.7xxxxx] mmc2: error -110 whilst initialising MMC card
[ 4.196145] rockchip-dp ff970000.edp: no DP phy configured
BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) ...I've seen different patterns, but to the same effect:
Code:
[ 7.519011] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Begin: running / scripts/local-block ... done
Begin: running / scripts/local-block ... done
Begin: running / scripts/local-block ... done
[ 11.59xxxx] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Begin: running / scripts/local-block ... done
Begin: running / scripts/local-block ... done
Begin: running / scripts/local-block ... done
...
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! PARTLABEL=emmc-RootFS does not exist. Dropping to a shell!
BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) ...manjaro won't boot, eMMC, pinebookpro (Post #56)
Quote:I can confirm that my PBP has the same behaviour. I had the impression that the PBP boot succeeds more often when attached to the power supply.
Indeed after connecting my Pinebook Pro to the power cord I could boot from eMMC again, after several failed attempts (and having opened the case twice, to check the eMMC being attached properly).
Some speculation: The battery was at only about 30% - maybe it is a power issue?
Obviously it is not the Debian kernel, that is responsible. At least once I booted Manjaro (with its 5.6 kernel) from SD card and could see that /dev/mmcblk2 was not there, only /dev/mmcblk1 (the sd card).
Once, when on battery, the system even "lost" the eMMS it was running from. See the attached photograph for the kernel messages from that crash:
emmc_loss_pbp.jpg (Size: 399.74 KB / Downloads: 502)
Is anyone else here having similar issues? Any suggestions as to what I could do (apart from keeping the power adapter with me, or a backup system on sd card)? Maybe getting an NVMe and running a system from that would help?