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
  Upgrading Armbian from v24.2.1 gnome, breaks pinebook pro Sb2024 0 114 11-10-2024, 02:50 PM
Last Post: Sb2024
  Pinebook pro won't boot after bootloader installation jwensouls 4 939 08-21-2024, 04:17 AM
Last Post: KC9UDX
  [Pinebook Pro/Mobian/XFCE4] can fix touch or screen in greeter not both SynthGal 0 401 05-31-2024, 09:42 AM
Last Post: SynthGal
  Debian on Pinebook Pro u974615 7 2,891 03-31-2024, 10:11 AM
Last Post: u974615
  Pinebook Pro upgrading from the factory image yamsoup 12 4,109 02-22-2024, 04:02 PM
Last Post: tllim
  Help installing Manjaro on eMMC of Pinebook Pro pine4546464 4 3,221 12-13-2023, 07:22 PM
Last Post: trillobite
  Need Help Recovering Manjaro /boot Contents on Pinebook Pro calinb 6 3,511 12-11-2023, 03:47 AM
Last Post: calinb
  Gentoo on Pinebook Pro RELEASE jannik2099 54 103,546 12-08-2023, 11:25 PM
Last Post: tllim
  Boot Order in Pinebook Pro food 8 2,698 11-23-2023, 07:37 AM
Last Post: KC9UDX
  PineBook Pro seems to go to deep sleep, but doesn't wake up pogo 11 7,417 08-31-2023, 04:20 PM
Last Post: TRS-80

Forum Jump:


Users browsing this thread: 1 Guest(s)