From: John Blinka <john.blinka@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] boot hangs forever at “Loading initial ramdisk...”
Date: Fri, 14 May 2021 19:54:02 -0400 [thread overview]
Message-ID: <CAC_tCmoLVaUipqCMhxb3cw9JdtXcFkKZ8wGVjBpAEdAH1YzFHQ@mail.gmail.com> (raw)
In-Reply-To: <M_h8G9B--3-2@tutanota.com>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On Fri, May 14, 2021 at 7:10 PM <mad.scientist.at.large@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
>
[-- Attachment #2: Type: text/html, Size: 2224 bytes --]
next prev parent reply other threads:[~2021-05-14 23:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 23:06 [gentoo-user] boot hangs forever at “Loading initial ramdisk...” John Blinka
2021-05-13 23:22 ` Jack
2021-05-14 0:51 ` [gentoo-user] " John Blinka
2021-05-14 1:09 ` Dale
2021-05-14 1:34 ` [gentoo-user] " John Blinka
2021-05-14 1:12 ` Jack
2021-05-14 1:58 ` [gentoo-user] " John Blinka
2021-05-14 6:35 ` John Covici
2021-05-14 7:11 ` [gentoo-user] " William Kenworthy
2021-05-14 11:50 ` [gentoo-user] " John Blinka
2021-05-14 16:22 ` John Blinka
2021-05-14 11:44 ` John Blinka
2021-05-14 21:15 ` John Blinka
2021-05-14 23:10 ` mad.scientist.at.large
2021-05-14 23:31 ` Dale
2021-05-15 0:02 ` [gentoo-user] " John Blinka
2021-05-14 23:54 ` John Blinka [this message]
2021-05-15 8:31 ` [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] " Peter Humphrey
2021-05-16 2:07 ` William Kenworthy
2021-05-15 12:03 ` [gentoo-user] " Todd Goodman
2021-05-15 20:10 ` [gentoo-user] " John Blinka
2021-05-17 9:08 ` [gentoo-user] [SOLVED?] " John Blinka
2021-05-17 10:53 ` Neil Bothwick
2021-05-14 8:46 ` [gentoo-user] " Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC_tCmoLVaUipqCMhxb3cw9JdtXcFkKZ8wGVjBpAEdAH1YzFHQ@mail.gmail.com \
--to=john.blinka@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox