On 14/5/21 2:35 pm, John Covici wrote: > On Thu, 13 May 2021 21:58:25 -0400, > John Blinka wrote: >> [1 <text/plain; UTF-8 (quoted-printable)>] >> On Thu, May 13, 2021 at 9:12 PM Jack <ostrof...@users.sourceforge.net> >> wrote: >> >>> Given you say the UUID is for the boot partition, then both the linux and >>> initrd should just have the name of the kernel and initrd files (without >>> leading "/boot",) which sounds like what you've got. I'd next wonder if >>> something is missing from the kernel/initrd combination, such as a kernel >>> module necessary for some early part of the boot process or a file system >>> (per Dale's suggestion.) Assuming that you ran genkernel after booting a >>> live image and chrooting into the new system, then we know the hardware can >>> boot a good kernel/image combo. Mainly I'm just thinking out loud here, >>> trying to coax someone's little gray cells into action. >>> >> In my early linux days, I thought it would be clever to include kernel >> support for my root filesystem in a module. Whose code resided on the root >> filesystem... That didn’t work, of course, but at least the kernel started >> to boot and threw out an error message. Here, I just get complete >> silence. So, I doubt that file system support is an issue. >> >> John > I would look in the grub.cfg and give us exactly what is in the stanza > you are using, including where it thinks the root file system is, > etc. Also, see if there is any genkernel option to get some debugging > info out of the initrd, I know using dracut you can get breakpoints > during the process and see how its doing. > Try https://wiki.ubuntu.com/DebuggingKernelBoot ... I am not sure genkernel uses that exact name but I did need to find the initramfs boot log to diagnose a failure in a genkernel initramfs at one time.
BillK
