| 1 |
On Mon, 8 Jun 2020 11:38:03 -0400, Rich Freeman wrote: |
| 2 |
|
| 3 |
> > # cat /boot/loader/entries/30-gentoo-5.7.1.conf |
| 4 |
> > title Gentoo Linux 5.7.1 |
| 5 |
> > linux /vmlinuz-5.7.1-gentoo |
| 6 |
> > options root=/dev/nvme0n1p4 initrd=/intel-uc.img net.ifnames=0 |
| 7 |
> > raid=noautodetect |
| 8 |
> > |
| 9 |
> > That file hasn't changed, other than the kernel version. |
| 10 |
> > |
| 11 |
> > On booting with that setup, I got an error immediately (from the UEFI |
| 12 |
> > BIOS, I assume) complaining of an invalid parameter. A few seconds |
| 13 |
> > later the kernel panicked because it couldn't find the root device. |
| 14 |
> |
| 15 |
> Can you have your initrd launch a shell? I'm not sure if the |
| 16 |
> nomenclature for the root device has changed. It is also possible |
| 17 |
> you're missing some kernel option needed (maybe an NVME option got |
| 18 |
> renamed and you answered the new option No?). |
| 19 |
> |
| 20 |
> If it is running the initrd then you probably can get it to launch a |
| 21 |
> shell and then you can poke around and see what it is doing. |
| 22 |
|
| 23 |
That's not an initrd with a shell though, it's just the intel microcode |
| 24 |
update. You would need an additional dracut (or similar) generated initrd |
| 25 |
to do what you suggest. |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Neil Bothwick |
| 30 |
|
| 31 |
I am McCoy of Bo...Damnit! I'm a doctor, not a collective! |
Archives