From: John Blinka <john.blinka@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] boot hangs forever at “Loading initial ramdisk...”
Date: Thu, 13 May 2021 19:06:07 -0400 [thread overview]
Message-ID: <CAC_tCmrLhm_e6HY74a8ayuw6PaXaYM1KYjp64miOO_vrNr+9VA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
Hi, Gentooers,
New thread, next obstacle in booting new Asus mobo.
As the subject says, the boot hangs indefinitely. Output to the screen is
Booting a command list
Loading Linux 5.10.27-gentoo-x86_64 ...
Loading initial ramdisk ...
And there it stops forever.
The kernel is the latest stable gentoo-sources. I normally do a custom
configuration, but in this instance built it with “genkernel all”, using
whatever config genkernel produces. I use grub (grub2), and installed the
kernel and initrd with “grub-mkconfig -o /boot/grub/grub.cfg”, as I
normally do.
Googling around shows that this problem tends to occur when grub can’t find
the initrd.
So I looked at the grub boot script by pressing “e” just before the boot
starts to make sure that grub is looking in the right place for the kernel
and for the initrd. I think it is, since deliberately misspelling either
file name with the grub editor causes error messages saying grub can’t find
what I told it to look for. And those error messages do not occur with the
boot script that grub generated.
Normally, loading the initrd takes only a few seconds.
How does one debug this situation?
John
[-- Attachment #2: Type: text/html, Size: 1715 bytes --]
next reply other threads:[~2021-05-13 23:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 23:06 John Blinka [this message]
2021-05-13 23:22 ` [gentoo-user] boot hangs forever at “Loading initial ramdisk...” 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 ` [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] " John Blinka
2021-05-15 8:31 ` 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_tCmrLhm_e6HY74a8ayuw6PaXaYM1KYjp64miOO_vrNr+9VA@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