Gentoo Archives: gentoo-user

From: Rich Freeman <rich0@g.o>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Gentoo-sources 5.7.x
Date: Mon, 08 Jun 2020 15:38:23
In Reply to: [gentoo-user] Gentoo-sources 5.7.x by Peter Humphrey
1 On Mon, Jun 8, 2020 at 11:06 AM Peter Humphrey <peter@××××××××××××.uk> wrote:
2 >
3 > Afternoon all,
4 >
5 > Is there something special for me to set in the kernel config to enable it to
6 > find the root partition? I copied the config from 5.4.38, ran oldconfig and
7 > followed most of the suggested answers; but it won't boot.
8 >
9 > # cat /boot/loader/entries/30-gentoo-5.7.1.conf
10 > title Gentoo Linux 5.7.1
11 > linux /vmlinuz-5.7.1-gentoo
12 > options root=/dev/nvme0n1p4 initrd=/intel-uc.img net.ifnames=0
13 > raid=noautodetect
14 >
15 > That file hasn't changed, other than the kernel version.
16 >
17 > On booting with that setup, I got an error immediately (from the UEFI BIOS, I
18 > assume) complaining of an invalid parameter. A few seconds later the kernel
19 > panicked because it couldn't find the root device.
21 Can you have your initrd launch a shell? I'm not sure if the
22 nomenclature for the root device has changed. It is also possible
23 you're missing some kernel option needed (maybe an NVME option got
24 renamed and you answered the new option No?).
26 If it is running the initrd then you probably can get it to launch a
27 shell and then you can poke around and see what it is doing.
29 Offhand though those are my two guesses:
30 1. Driver config option got renamed and the new option is disabled.
31 2. Some kernel change alters the naming of the root device so you're
32 giving it the wrong name now.
34 If you're using an initrd you should consider using a UUID/lable/etc
35 to identify the root device if possible. That tends to be more robust
36 when stuff like this happens, though it won't help in #1.
38 --
39 Rich


Subject Author
Re: [gentoo-user] Gentoo-sources 5.7.x Neil Bothwick <neil@××××××××××.uk>