You are not logged in.
Pages: 1
Which is important on a computer like mine, where the /dev/sdX1 path changes, depending on (apparently) the BIOS's view of the situation.
I don't know if its the BIOS causing the problem but it does bring up a question. Have you updated the bios to the lastest version available from the motherboard manufacture? It might be a good idea to do that, especially if it is UEFI.
I don't think the lack of an initrd in salix should have any impact on devuan. Lilo is happy to boot an OS with or without initrd. It's just a matter of getting the stanza right.
In generral this is true however the OP has choosen to used UUIDs in th path for liloconfig root file systems directive (i.e. root_) lilo cannot pass root file system paths to the kernel when UUIDs are used. This requires a initrd.
The Slackware installer, and therefore, Salix installer installs the kernel-huge as default. This kernel has everthing but the kitchen sink complied into it so as to work on as many different system. Slackware does not recommand that user contiune to used the kernel-huge but rather recommends that a the user either complies thier own kernel or use the generic kernel with an initrd.
image=/media/username/9d2c1561-d6d7-4651-9373-bcd440c289dd/boot/vmlinuz
It is correct. This path is not the one that gets passed to the kernel. It specifies where the kernel image can be found in the currently running OS.
Pages: 1