From: Daniel Mierswa <impulze@impulze.org>
To: grub-devel@gnu.org
Subject: Re: Faulty BIOS or GRUB issue (USB Stick won't boot)
Date: Thu, 01 Oct 2009 15:05:27 +0200 [thread overview]
Message-ID: <4AC4A917.10805@impulze.org> (raw)
In-Reply-To: <4AC466A9.8030805@gmail.com>
On 01.10.2009 10:22, Vladimir 'phcoder' Serbinenko wrote:
> To simulate brain damage of your BIOS
*shrug* I wonder how you can manage to simulate _that_ severe damage.
> echo '(hd0) /dev/loop0'> /boot/grub/device.map
D'oh, didn't think of hardcoding it, I thought GRUB detects it properly.
However, phcoder, there were some crackheads back in January taking some
time with that matter and I tried almost every hack discussed on the
net. And out of nothing comes you, applying yet another hack and it just
seems to work. You're a true hero. :D
However when doing "ls (hd0)" in the GRUB rescue shell that fires up,
I'm getting "Partition table". I guess this is part of the hack?
Is it possible to apply this workaround in the codebase so that others
with that broken BIOS (remember I have another MBR file of a guy who
reported identical behaviour) or is this something that should be left
to people with broken BIOS?
All in all, thank you very much, now that I have a rescue shell, I can
start playing.
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22
next prev parent reply other threads:[~2009-10-01 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 1:12 Faulty BIOS or GRUB issue (USB Stick won't boot) Daniel Mierswa
2009-09-30 6:20 ` Vladimir 'phcoder' Serbinenko
2009-09-30 19:11 ` Daniel Mierswa
2009-10-01 8:22 ` Vladimir 'phcoder' Serbinenko
2009-10-01 13:05 ` Daniel Mierswa [this message]
2009-09-30 8:26 ` James Courtier-Dutton
2009-09-30 19:10 ` Daniel Mierswa
2009-10-01 8:49 ` James Courtier-Dutton
2009-10-01 13:05 ` Daniel Mierswa
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=4AC4A917.10805@impulze.org \
--to=impulze@impulze.org \
--cc=grub-devel@gnu.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 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.