... pcie_brcmstb to MODULES i.e MODULES=(pcie_brcmstb) 6) run mkinitcpio -P 7) edit /boot/boot.txt and add the new root partition to root= e.g. root=PARTUUID=XXXXXXXXXXX (run blkid to get the partuuid) 8) run ./mkscr 9) install uboot 2020.10 provided by mrtux (thank you) Shut down, remove sd card, ...

I did this to fix the boot issue on my rock64 v2. part uuid ${devtype} ${devnum}:${bootpart} uuid setenv bootargs console=ttyS2,1500000 root=PARTUUID=${uuid} rw rootwait earlycon=uart8250,mmio32,0xff130000 setenv fdtfile rockchip/rk3328-rock64.dtb setenv ramdisk_addr_r 0x06000000 <= Append Got ...

... root partition to the second partition of boot device part uuid ${devtype} ${devnum}:2 uuid setenv bootargs console=ttyS1,115200 console=tty0 root=PARTUUID=${uuid} rw rootwait smsc95xx.macaddr="${usbethaddr}" My root partition is the second partition of my boot device, I also tried to ...

All Filesystems have an UUID, run lsblk -f to list them. On GPT partitions you have also PARTLABEL, PARTUUID. Please read the note on PARTUUID when using MBR, Unlike a regular PARTUUID of a GPT partition, MBR's pseudo PARTUUID can change if the partition number changes. https://wiki.archlinux.org/index.php/Persistent_block_device_naming#by-partuuid

My 1st post has a link, which shows 3 ways to display the required info.

... happens, if you boot with disabled crypttab, and then invoke later the manual encryption, e,g, remote over ssh: sudo cryptsetup open /dev/disk/by-partuuid/0004a183-01 500go --key-file /etc/500go where PARTUUID=0004a183-01 from crypttab syntax matches /dev/disk/by-partuuid/0004a183-01 here.

... hdmi_force_hotplug=1 initramfs initramfs-linux.img followkernel [pi4] # Run as fast as firmware / board allows #arm_boost=1 And cmdline.txt root=PARTUUID=e9659c64-02 rootfstype=ext4 rw rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 ...

... * Disk identifier must be set. If left at `0x00000000` for some reason (e.g. came this way from factory), then `PARTUUID` won't be set either, and the card won't boot due to `/dev/disk/by-partuuid` not having the root partition entry (or boot, for that matter). ...

... [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129920 [ 0.000000] Kernel command line: console=tty0 console=ttyO0,115200n8 root=PARTUUID=b70943ba-01 rw rootwait [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: ...

... only the uImage and it seems, during the boot the kernel is unable to identify the root partition. It's not working with label and UUID, only with PARTUUID. Is this missing because of the lack of initrd? [ 2.800218] Waiting 10 sec before mounting root device... [ 3.778601] scsi 2:0:0:0: Direct-Access ...