| 1 |
On Tuesday, 9 June 2020 18:29:50 BST Neil Bothwick wrote: |
| 2 |
> On Tue, 09 Jun 2020 17:07:40 +0100, Peter Humphrey wrote: |
| 3 |
> > > Nope. Didn't help. All I have now is dredging through the kernel |
| 4 |
> > > config yet again, or possibly even trying an initrd. I hope I'm not |
| 5 |
> > > being forced down that road after all these years. |
| 6 |
> > |
| 7 |
> > It was so simple, and the clue was in an earlier message. |
| 8 |
> > |
| 9 |
> > # cat /boot/loader/entries/30-gentoo-5.7.1.conf |
| 10 |
> > title Gentoo Linux 5.7.1initrd=/intel-uc.img |
| 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's got corrupted somehow. My first post had it right, but the first line of |
| 16 |
the file above is not. |
| 17 |
|
| 18 |
> > All I had to do was to remove the slash from initrd=/intel-uc.img. I |
| 19 |
> > did that in all the .../entries files and 5.4.38 also still boots |
| 20 |
> > happily. |
| 21 |
> |
| 22 |
> Did you also remove the leading slash from the kernel? I'm still running |
| 23 |
> 5.4 but I tried removing the slashes from the kernel and initrds and it |
| 24 |
> booted fine. Thanks for the heads up, I'll be ready when 5.7+ goes |
| 25 |
> longterm. |
| 26 |
|
| 27 |
I didn't, no, but I'll try it. |
| 28 |
|
| 29 |
-- |
| 30 |
Regards, |
| 31 |
Peter. |
Archives