From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Grub: for the love of almighty Zardoz the magniicent....
Date: Wed, 01 Jul 2020 09:45:45 +0100 [thread overview]
Message-ID: <4242826.LvFx2qVVIh@lenovo.localdomain> (raw)
In-Reply-To: <20200701091510.0220a9cc@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
On Wednesday, 1 July 2020 09:15:10 BST Neil Bothwick wrote:
> On Wed, 1 Jul 2020 01:40:54 +0000 (UTC), Alan Grimes wrote:
> > I RMA'd my normal mobo as previously discussed.
> > I went to grab my previous motherboard and it turns out that it had
> > actually released a goodly chunk of it's Magic Smoke (tm) while I
> > hadn't been looking. So I went down to the Quickie Mart and grabbed a
> > motherboard that was still compatible with the rusty old 1800x... The
> > error was Unable to load "/grub/i386-pc/normal.mod"
Some short explanation of what Live image you're trying to boot with and at
least your partitioning scheme might help.
The GRUB error is indicative of GRUB not finding the partition in which the
normal.mod module is stored.
> > I had to buy some
> > more USB sticks (my optical drive seems functional but will not boot
> > the machine...)
Why not? There should be no difference between a LiveCD and a LiveUSB. If
anything booting off a USB on some MoBos could be more troublesome. Have you
looked into this problem to find out if there was some MoBo setting you had to
change (physical jumper/switch/cable, or firmware)?
> > and used gparted to get into the partition, .........
> > =((( All my .mod files were in x86_64-efi
> >
> > >>> AND IT WAS WORKING ON THE OTHER MOTHERBOARD!!! <<<
> >
> > =~((((((((
> > Dear beloved Zardoz, what have I done to deserve your wrath???
>
> Is the replacement motherboard UEFI and is t set that way in the firmware
> menus?
>
> I think Zardoz would ask why you are subjecting yourself to GRUB when you
> have much simpler options with UEFI hardware.
Assuming this is a UEFI MoBo you can boot any kernel images on disk directly,
as long as you can point the UEFI firmware to them.
Have a look here:
https://wiki.gentoo.org/wiki/EFI_stub_kernel
and perhaps here:
https://wiki.gentoo.org/wiki/Efibootmgr
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-01 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 21:19 [gentoo-user] Gentoo chroot with old glibc Hervé Guillemet
2020-06-21 17:06 ` Michael
2020-06-21 19:43 ` Hervé Guillemet
2020-06-21 20:03 ` Michael
2020-06-21 22:52 ` Hervé Guillemet
2020-06-30 8:26 ` Andreas K. Huettel
2020-06-30 16:29 ` Laurence Perkins
2020-07-01 1:40 ` [gentoo-user] Grub: for the love of almighty Zardoz the magniicent Alan Grimes
2020-07-01 8:15 ` Neil Bothwick
2020-07-01 8:45 ` Michael [this message]
2020-07-02 4:20 ` Alan Grimes
2020-07-01 1:30 ` [gentoo-user] Gentoo chroot with old glibc Thomas Mueller
[not found] ` <20200701013122.CE9C8E08AE@pigeon.gentoo.org>
2020-07-01 14:47 ` Andreas K. Huettel
2021-01-04 11:57 ` Thomas Mueller
[not found] ` <20210104115748.50A5EE0930@pigeon.gentoo.org>
2021-01-08 23:37 ` Andreas K. Hüttel
2020-06-21 21:08 ` Rich Freeman
2020-06-21 22:34 ` Hervé Guillemet
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=4242826.LvFx2qVVIh@lenovo.localdomain \
--to=confabulate@kintzios.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