On Fri, May 14, 2021 at 7:10 PM <mad.scientist.at.la...@tutanota.com> wrote:

> >
> Have you recompiled the kernel?  Could be a random, erroneous write to
> disk or something in the kernel compile didn't go well.  I'd suggest also
> rebuilding the initrd


Yes.  Same problems with several kernels and associated initrds, the latter
produced by genkernel or dracut or even some gibberish I pretended was an
initrd.  From grub debug output, I believe the problem exists right before
the kernel tries to use the initrd.  It’s contents are irrelevant at that
stage.

and reinstalling grub.


That may or may not be the answer, but it’s such an obvious step. Will
definitely give that a try.

I.e. I think there is likely a kernel compile issue since it doesn't ever
> launch the kernel succesfully either on autopilot or when you run grub
> interactive.  Might also recompile grub, perhaps there's a change in
> compiler options that produces an incompatible (at least partially).  I
> also suggest the rebuild so you can be sure you have the right initrd and
> matching kernel.


I don’t think it’s a kernel compile issue.  I just now used efibootmgr to
create a uefi entry with kernel command line parameters to define the root
fs and initrd.  That worked.  That result focuses the blame on grub.

John

>

Reply via email to