|
6/22 run of PBPs - is reimaging eMMC with new OS possible still?
|
08-30-2022, 06:54 PM
(This post was last modified: 08-30-2022, 07:01 PM by elitegamercody.)
(08-30-2022, 06:53 PM)wdt Wrote: YES, use tune2fs (-U) to change UUID to what it is looking for How do I change the UUID from initramfs/Busybox? Fsck is missing from Kali's Busybox configuration. I use Tow-Boot. fstab is empty. tried to unlock root using cryptroot-unlock, root directory is empty.
You don't seem to understand, change UUID of filesystem to match initrd
(from a SD card boot OR emmc in adapter) OR make a new initrd initrd is a gzipped cpio some useful commands zcat $1 | cpio --extract --verbose --quiet --list echo "========================================================================" zcat $1 | cpio --extract --verbose --quiet --to-stdout init these from lsinitrd, but what you want to do is expand it to a temp directory, that contains ONLY expanded contents, edit and then repack
08-31-2022, 08:34 AM
I just wanted to add that I've been flashing a LOT of images over the last few days on a brand new Pinebook Pro (the newer re-designed model, which also doesn't appear to have a functional eMMC-disable switch) and I've found that pretty much every image I flash using macOS will refuse to boot with flashing power light (kernel panic), with the sole exception of Armbian (which is much smaller than all the other images, which is what I imagine the difference is.)
However, booting into Armbian and flashing with `sudo dd if=/path/to/*.img of=/dev/mmcblk* bs=1M status=progress` has worked very consistently. Loading all of the WiFi firmware after the fact is a pain and the Debian install script requires a lot of modifications to work, but ultimately I've ended with an encrypted Debian installation on my eMMC with functional sleep and WiFi loading up with Tow-Boot.
08-31-2022, 10:06 AM
(08-20-2022, 02:44 PM)elitegamercody Wrote: Hi, (08-22-2022, 02:16 AM)KC9UDX Wrote: It should be. But most of the official images that worked are just not available anymore. Unless you can find a copy of one of those, you may have to cook your own.Same here! I had absolutely no difficulty with booting from SD on my first early production (2021) Pro, but this one is acting about a "proprietary" as a Mac! Using Baleenttcher to flash Armbian_22.05.1_Pinebook-pro_jammy_edge_5.18.0_xfce_desktop.img.xz, I get a perfect, uncompressed copy on the SD card. But when I try to boot from the card, all I get is a totally blank screen and a slowly blinking green power light. I can even remove the card, hot, and the Pinebook pro will immediately boot Manjaro, so t's fairly obvious that their Uboot is proprietary as hell. While I have long Linux experience (going back to Yggdrasil), I make no claims to being a developer or much more than a F77 and C patch programmer. But while I find Manjaro reliable enough, I have never been able to stand KDE, ever since its beginning, considering it bloatware. All that I, and apparently other users as well, am asking for is a simple uboot or towboot file with simple instructions about how to flash it. This really is the Achilles heel of the Pinebook Pro and, for that mater, the entire Pine64 program, and it's a shame.
while(!(succeed=try()));
08-31-2022, 04:12 PM
I came to the same conclusion about the U-Boot that comes with the new Manjaru. I could not boot anything but Manjaru until I got rid of it. However I didn't actually isolate it as the problem.
I wonder if the U-boot that comes with the latest NetBSD images will boot Linux; because it's pretty awesome.
08-31-2022, 04:30 PM
Well there is ,,, uboot-pinebookpro-bsp,,,, the 3 files are copied to /boot
and then you are supposed to use the dd commands to get them into the 1st 16M This is an offshoot from mrfixit's version
10-04-2022, 07:03 AM
(This post was last modified: 10-04-2022, 07:38 AM by elitegamercody.)
Hi,
After multiple renamings of the UUID of armbian_root, I still don't understand what's going on. Upon boot into the eMMC I reach the "Begin: Running /scripts/local-block ... done." loop. I have renamed the UUID of the eMMC root partition to fit what was in fstab, but then get ALERT! UUID=the_uuid_of_the_armbian_root_partition_on_the_eMMC_card does not exist, which is not true. I don't understand why this is so hard! I even have a RESUME=UUID=the_uuid_of_the_armbian_root_partition_on_the_eMMC_card in the initramfs-tools conf.d. This just doesn't make sense - are pinebook pros unable to read UUIDs properly? Can someone help? Btw WDT temp2fs is not usually in PATH you have to use /sbin/temp2fs. Also WDT please be mindful that a lot of people don't even have a bootable system or are able to boot but not enter their root partition, so they might be in a busybox/initramfs shell instead of a full Linux shell
10-04-2022, 09:31 AM
It is quite important that you have a bootable SD, when ALL other media are removed/disabled
OR a emmc carrier tune2fs, your typo made a bit confused, even tho permissions are 755 it is sort of a root operation, so /sbin maybe it is the quotes ("), it is not clear to me where they are required/mandatory
10-04-2022, 12:24 PM
(10-04-2022, 09:31 AM)wdt Wrote: It is quite important that you have a bootable SD, when ALL other media are removed/disabled I still don’t understand why, even after changing the UUID of the root partition to the one that matches my fstab, I am booting but unable to find root on the installation. Have you experienced this issue? I have installed tow-boot, I do not think I would need a new initrd if I have changed the UUID of the root partition to align with the current initrd. |
