The first thing comes in my mind - does /dev/nvme0n1 exist on your
system? Maybe you don't have enough kernel modules for that.
Second - what does /proc/cmdline shows? Does it have correct boot arguments?
Third - I'm not a systemd-boot user, but as I'm reading a wiki
https://wiki.gentoo.org/wiki/Systemd/systemd-boot - it seems that
/etc/kernel/cmdline is used by kernel-install. I suppose you have to run
it after you make changes in /etc/kernel/cmdline?
If you have only one kernel, you can just manually create a standard
entry in /efi/loader/entries/gentoo-sources-kernel.conf and specify the
default in /efi/loader/loader.conf instead of using kernel-install.
On 10.02.2026 10:13, [email protected] wrote:
Greetings,
I've just finished installing a new system, choosing systemd-boot rather than
grub. The handbook says that /etc/kernel/cmdline should contain 'quiet splash',
but that's clearly not the whole story so I improvised.
'blkid | grep nvme0n1p5' shows this:
/dev/nvme0n1p5: LABEL="RootFS" UUID="7ab169d9-03cb-44ce-98f6-1955c2458a4c" BLOCK_SIZE="4096"
TYPE="ext4" PARTLABEL="root" PARTUUID="aeb1b1eb-7995-44ac-84ad-0e999ff4459d"
...so I put this into /etc/kernel/cmdline:
root=UUID=7ab169d9-03cb-44ce-98f6-1955c2458a4c quiet splash
Then on rebooting, I get 'Cannot open blockdev' or similar.
Should there be some punctuation in my command line? Or perhaps I should have
specified the PARTUUID instead of the device UUID. This is one of the few
places where the handbook doesn't show an example.
I can't check online at the moment because the site's down.
