07-15-2020, 08:50 PM
(This post was last modified: 07-15-2020, 09:39 PM by decisivedove.)
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:
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:
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?
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,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?
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?