From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>,
Jelle Geerts <jellegeerts@gmail.com>
Subject: Re: GRUB-1.96 won't boot, boots into rescue prompt
Date: Tue, 11 Mar 2008 11:57:15 -0400 [thread overview]
Message-ID: <1205251035.7067.12.camel@dv> (raw)
In-Reply-To: <bf2cff050803110300n21dd0152m4358d4fbc7d2034@mail.gmail.com>
On Tue, 2008-03-11 at 11:00 +0100, Jelle Geerts wrote:
> Phew, I uninstalled Gentoo and reinstalled Arch so I can't remember
> for sure what modules were listed :(
> I can remember 'ext2' was loaded.
Interesting. If some modules were loaded, then disk access was working
initially. But it stopped working at some point. Maybe it was the
"ata" module? It should not be loaded by default, but maybe it was
loaded for some reason.
> Also, 'insmod normal' resulted in the same "error: unknown device" error.
That's not surprising considering that no devices can be accessed.
I normally verify the GRUB installation by running this as root:
qemu -hda /dev/sda
where /dev/sda is the bootable hard drive. It should be safe if you
don't try to boot anything. It's even possible to install GRUB 2, test
it with qemu and then install GRUB 1 without having to reboot.
Checking with qemu can separate BIOS issues from issues with GRUB 2
itself (wrong module dependencies) and grub.cfg (loading "ata" module).
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-03-11 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 3:49 GRUB-1.96 won't boot, boots into rescue prompt Jelle Geerts
2008-03-10 14:20 ` Robert Millan
2008-03-11 10:00 ` Jelle Geerts
2008-03-11 15:57 ` Pavel Roskin [this message]
2008-03-11 21:16 ` Jelle Geerts
-- strict thread matches above, loose matches on Subject: below --
2008-03-09 23:07 Jelle Geerts
2008-03-09 23:58 ` Pavel Roskin
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=1205251035.7067.12.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
--cc=jellegeerts@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.