From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] boot hangs forever at “Loading initial ramdisk...”
Date: Fri, 14 May 2021 09:46:13 +0100 [thread overview]
Message-ID: <3373032.iIbC2pHGDl@peak> (raw)
In-Reply-To: <CAC_tCmrLhm_e6HY74a8ayuw6PaXaYM1KYjp64miOO_vrNr+9VA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On Friday, 14 May 2021 00:06:07 BST John Blinka wrote:
> How does one debug this situation?
Just coming to this belatedly, not having noticed what may be a connection until now. I
have an Asus X99-A motherboard, and I never got grub to work at all. I use a
combination of efibootmgr and bootctl to manage my boot process. (Bootctl is in sys-
boot/systemd-boot; that's the only systemd package I have on this openrc system.)
You could look at the handbook [1] for how to set these up. I had to develop my own
method by picking bits out of it. I use efibootmgr to create entries in the UEFI BIOS, then
bootctl to keep them up to date. Oh, and I had to leave a small, otherwise unused
partition before the FAT32 boot partition. From parted:
Number Start End Size File system Name Flags
1 1.00MiB 9.00MiB 8.00MiB
2 9.00MiB 1025MiB 1016MiB fat32 boot, esp
3 1025MiB 50176MiB 49151MiB linux-swap(v1) swap
4 50176MiB 66560MiB 16384MiB ext4
5 66560MiB 132096MiB 65536MiB ext4
[...]
This may be a red herring of course; I wouldn't be too surprised if I'm doing things all
wrong, and your motherboard may differ from mine in many ways.
1. https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader[1]
--
Regards,
Peter.
--------
[1] https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
[-- Attachment #2: Type: text/html, Size: 2408 bytes --]
prev parent reply other threads:[~2021-05-14 8:46 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 ` [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 ` Peter Humphrey [this message]
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=3373032.iIbC2pHGDl@peak \
--to=peter@prh.myzen.co.uk \
--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