On 5/13/21 6:51 PM, John Blinka wrote:
On Thu, May 13, 2021 at 7:23 PM Jack <ostrof...@users.sourceforge.net
<mailto:ostrof...@users.sourceforge.net>> wrote:
I'd start by removing any "quiet" or "splash" from the kernel command
line. You should be able to see them when you hit "e". I'm not
sure
if it will actually help, but it should be a start.
Thanks, but neither one appears. My command line is
linux /vmlinuz… root=UUID=… ro loglevel=4 nomodeset
Here I’ve replaced the full name of the kernel and the uuid of the
boot partition with ellipses because it’s too tedious to type. I’ve
scrutinized the actual ones for typos and am convinced there are
none. Leaving out the loglevel command doesn’t change the behavior at
all.
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.
