Please could you share how your entry to point to your nvme looks like?
Did you use the uboot-update afterwards?
I’m afraid it will crush some dtb settings. cwt warned me it might do this.
Here are all my block devices:
myBlockDevices.json (22.5 KB)
I believe what I want to be booting to is this:
“uuid”: “d65e91f4-ea2f-444f-bf86-d95f1096a83d”
I’m thinking:
root=LABEL=rootpart
Gets changed to
root=UUID=d65e91f4-ea2f-444f-bf86-d95f1096a83d
BEFORE:
$ cat /boot/boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT visionfive2
MENU TITLE starfive visionfive2 boot options
LABEL visionfive2
MENU LABEL visionfive2
LINUX ../../vmlinuz-5.15.0-vf2-260+
INITRD ../../initrd.img-5.15.0-vf2-260+
FDTDIR ../../dtb-5.15.0-vf2-260+
APPEND root=LABEL=rootpart rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0 apparmor=0
AFTER CHANGE:
$ cat /boot/boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT visionfive2
MENU TITLE starfive visionfive2 boot options
LABEL visionfive2
MENU LABEL visionfive2
LINUX ../../vmlinuz-5.15.0-vf2-260+
INITRD ../../initrd.img-5.15.0-vf2-260+
FDTDIR ../../dtb-5.15.0-vf2-260+
APPEND root=UUID=d65e91f4-ea2f-444f-bf86-d95f1096a83d rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0 apparmor=0
Is that ok? Do I need to do uboot-update afterwards?