On Tuesday, 9 June 2020 18:29:50 BST Neil Bothwick wrote: > On Tue, 09 Jun 2020 17:07:40 +0100, Peter Humphrey wrote: > > > Nope. Didn't help. All I have now is dredging through the kernel > > > config yet again, or possibly even trying an initrd. I hope I'm not > > > being forced down that road after all these years. > > > > It was so simple, and the clue was in an earlier message. > > > > # cat /boot/loader/entries/30-gentoo-5.7.1.conf > > title Gentoo Linux 5.7.1initrd=/intel-uc.img > > linux /vmlinuz-5.7.1-gentoo > > options root=/dev/nvme0n1p4 initrd=/intel-uc.img net.ifnames=0 > > raid=noautodetect
That's got corrupted somehow. My first post had it right, but the first line of the file above is not. > > All I had to do was to remove the slash from initrd=/intel-uc.img. I > > did that in all the .../entries files and 5.4.38 also still boots > > happily. > > Did you also remove the leading slash from the kernel? I'm still running > 5.4 but I tried removing the slashes from the kernel and initrds and it > booted fine. Thanks for the heads up, I'll be ready when 5.7+ goes > longterm. I didn't, no, but I'll try it. -- Regards, Peter.
