1 |
On Wed, 10 Jun 2020 11:01:45 +0100, Peter Humphrey wrote: |
2 |
|
3 |
> > > Did you also remove the leading slash from the kernel? I'm still |
4 |
> > > running 5.4 but I tried removing the slashes from the kernel and |
5 |
> > > initrds and it booted fine. Thanks for the heads up, I'll be ready |
6 |
> > > when 5.7+ goes longterm. |
7 |
> > |
8 |
> > I didn't, no, but I'll try it. |
9 |
> |
10 |
> This is the new default boot entry: |
11 |
> |
12 |
> # cat /boot/loader/entries/30-gentoo-5.7.1.conf |
13 |
> title Gentoo Linux 5.7.1 |
14 |
> linux vmlinuz-5.7.1-gentoo |
15 |
> options root=/dev/nvme0n1p4 initrd=intel-uc.img net.ifnames=0 |
16 |
> raid=noautodetect |
17 |
> |
18 |
> I've just booted from it. |
19 |
> |
20 |
> I assume I wouldn't be able to if I removed the leading slash from root= |
21 |
|
22 |
I /think/ you're right there. |
23 |
|
24 |
Any reason you bury the iniitrd in the options list rather that having it |
25 |
on a separate line? This is what I'm now using: |
26 |
|
27 |
title Desktop |
28 |
version 5.4.38-gentoo |
29 |
linux vmlinuz-5.4.38-gentoo |
30 |
options root=LABEL=yooden rd.luks.uuid=luks-... |
31 |
initrd intel-uc.img |
32 |
initrd initramfs-5.4.38-gentoo.img |
33 |
|
34 |
|
35 |
-- |
36 |
Neil Bothwick |
37 |
|
38 |
Don't let your mind wander, it's too little to be let out alone. |