systemd-boot root=/dev/ram0

[g-w]

Today I installed Gentoo with OpenRC and systemd-boot. It created the following entry:

[jpsollie]

/dev/ram0 is the device name of your ramdisk.
When your kernel loads from an initial ramdisk, it creates a virtual device /dev/ram0 to boot from. the bootloader puts the ramdisk up there in memory, so your kernel can boot.
When you boot it, it will find things like kernel modules, basic settings etc in the ramdisk to instruct how to proceed.
The fact that it doesn't work sounds like:
-you didn't generate ramdisk correctly. Check the gentoo handbook / wiki for that, you may have missed something
-your fstab in the ramdisk has an incorrect device set for the root filesystem (/)
_________________
The power of Gentoo optimization (not overclocked): [img]https://www.passmark.com/baselines/V10/images/503714802842.png[/img]

[Phoenix591]

when trying to come up with the commandline to use for automatically generated entries, systemd-boot first looks at /etc/kernel/cmdline, and if it doesn't exist, looks at /usr/lib/kernel/cmdline, and if that also does not exist, falls back to /proc/cmdline ( the current commandline used for the kernel). This last option is what it did: it used the livecd's root=/dev/ram0 for your actual install.

[NeddySeagoon]

g-w,

/dev/ram0 is your first ram disk.

Once upon a time, the initrd was loaded into /dev/ram0 and the kernel was told to look for it there.
That's not been the case for a long time now. Your kernel may not even have ramdisk support enabled. Its been replaced with tmpfs.

There is much tighter integration between the kernel and initramfs these days. The kernel will use it if its there so root=/dev/ram0 is no longer required to mouth the temporary root filesystem.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.