Pinebook Pro sometimes Does not boot up correctly
#1
Hi,
I recently installed Arch Linux on my Pinebook Pro. /dev/mmcblk2p1 is my boot partition and p2 is my root partition. The problem is that sometimes Linux cannot detect /dev/mmcblk2p2. Sometimes, it works fine. Here is the output:

Quote::: running early hook [udev]
Starting version 245.6-8-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/mmcblk2p2 ...
ERROR: device '/dev/mmcblk2p2' not found. Skipping fsck.
:: mounting '/dev/mmcblk2p2' on real root
mount: /new_root: special device /dev/mmcblk2p2 does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#


It was working fine a while ago, it only happens sometimes. Using UUID on the extlinux config also results in the same.
I had recently soft bricked my PBP and had to switch off the emmc but it is fixed now, if that is relevant.

Apparently running:

Quote:echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind

echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind

As suggested by randomuser987987 in the thread Pinebook Pro dead after updating u-boot works in getting the partition to show in /dev. The question is will the changes persist forever?

(07-15-2020, 08:50 PM)decisivedove Wrote: Hi,
I recently installed Arch Linux on my Pinebook Pro. /dev/mmcblk2p1 is my boot partition and p2 is my root partition. The problem is that sometimes Linux cannot detect /dev/mmcblk2p2. Sometimes, it works fine. Here is the output:

Quote::: running early hook [udev]
Starting version 245.6-8-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/mmcblk2p2 ...
ERROR: device '/dev/mmcblk2p2' not found. Skipping fsck.
:: mounting '/dev/mmcblk2p2' on real root
mount: /new_root: special device /dev/mmcblk2p2 does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#


It was working fine a while ago, it only happens sometimes. Using UUID on the extlinux config also results in the same.
I had recently soft bricked my PBP and had to switch off the emmc but it is fixed now, if that is relevant.

Apparently running:

Quote:echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind

echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind

As suggested by randomuser987987 in the thread Pinebook Pro dead after updating u-boot works in getting the partition to show in /dev. The question is will the changes persist forever?
It turns out that the changes do not persist. It only works when it wants to. Is there any way to make these changes persist permanently?
#2
I run arch as you, wich version of upower are you using ?
I ran the one packaged on https://nhp.sh/pinebookpro/ , but if it comes with some benefits (swithing led colors for each boot process, really fast, nearly upstream), it has some high percentage of failure mounting emmc partitions.
I now run the one packaged from manjaro for a week, it is much longer to boot, but it has 100% boot success so far.

git clone https://gitlab.manjaro.org/manjaro-arm/p...ookpro-bsp
cd uboot-pinebook-bsp
sudo dd if=idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
sudo dd if=uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc
sudo dd if=trust.img of=/dev/mmcblk2 seek=24576 conv=notrunc
#3
(07-17-2020, 10:57 AM)rimaille Wrote: I run arch as you, wich version of upower are you using ?
I ran the one packaged on https://nhp.sh/pinebookpro/ , but if it comes with some benefits (swithing led colors for each boot process, really fast, nearly upstream), it has some high percentage of failure mounting emmc partitions.
I now run the one packaged from manjaro for a week, it is much longer to boot, but it has 100% boot success so far.

git clone https://gitlab.manjaro.org/manjaro-arm/p...ookpro-bsp
cd uboot-pinebook-bsp
sudo dd if=idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
sudo dd if=uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc
sudo dd if=trust.img of=/dev/mmcblk2 seek=24576 conv=notrunc
i used the one in the Arch Pine 64 repository of the Arch image. The package was uboot-pbp, I believe. I will try the Manjaro package. Thank you!


Possibly Related Threads…
Thread Author Replies Views Last Post
  PineBook Pro seems to go to deep sleep, but doesn't wake up pogo 3 938 03-23-2023, 06:24 PM
Last Post: xp19375
  Need Help Recovering Manjaro /boot Contents on Pinebook Pro calinb 5 139 03-21-2023, 11:21 PM
Last Post: calinb
  slarm64 (unofficial slackware) Pinebook Pro RK3399 (aarch64) mara 41 29,134 03-18-2023, 04:39 AM
Last Post: mara
  Kali Linux for Pinebook Pro Luke 97 121,818 01-30-2023, 02:46 PM
Last Post: dachalife
  Help installing Manjaro on eMMC of Pinebook Pro pine4546464 2 493 12-31-2022, 12:18 PM
Last Post: pine4546464
  Armbian is [edit: no longer] dropping support for Pinebook Pro TRS-80 4 2,835 12-23-2022, 12:01 AM
Last Post: TRS-80
  Pinebook Pro wifi not working Queliffrel 1 560 11-30-2022, 06:30 AM
Last Post: myself600
  DiY - Installing Void Linux ARM On The Pinebook Pro vincele 1 501 11-28-2022, 05:03 PM
Last Post: tllim
  WiFi stopped on Pinebook Pro after update tkudog 3 1,067 11-24-2022, 04:32 PM
Last Post: tkudog
  Tow Boot install help Paulie420 7 1,530 11-24-2022, 10:24 AM
Last Post: myself600

Forum Jump:


Users browsing this thread: 1 Guest(s)