From: Andreas Born <futur.andy@googlemail.com>
To: GRUB2 Devel <grub-devel@gnu.org>
Cc: Phillip Susi <psusi@cfl.rr.com>
Subject: Re: GRUB2 fails when booting from CD
Date: Tue, 28 Sep 2010 22:19:00 +0200 [thread overview]
Message-ID: <4CA24DB4.9050202@googlemail.com> (raw)
In-Reply-To: <4CA22FC6.9000701@cfl.rr.com>
Am 28.09.2010 20:11, schrieb Phillip Susi:
> On 9/28/2010 12:37 PM, Andreas Born wrote:
>
>> If I understood that part about hd emulation right, that would mean the
>> image wouldn't work on any machine? Or is it possible to switch
>> dynamically with one single image between hd emulation and native
>> el-torito?
>>
> That's true, if that were the problem the image would not work on any
> machine. If it works on other machines, then it seems to be a problem
> with the bios.
>
>
>> Output:
>> grub rescue> set
>> prefix=(hd111)/boot/grub/i386-pc/
>> root=hd111
>>
> The odd ( 111 ) hd number is a hint that the bios is broken. Does ls
> report any available drives? Maybe it is there, but the bios did not
> pass the correct number.
>
Yes, as I wrote in my first mail:
grub rescue> ls
(hd0)
grub rescue> ls (hd0)
error: unknown filesystem
Is there any way to clearly identify the BIOS as the culprit? Or maybe
even a chance to implement a workardound at some point if it really is a
problem with the BIOS?
I guess the fact that I don't have such problems with isolinux can be
explained with different use of BIOS functionality?
I'm not asking because it were a serious problem for me. I'd just like
to lower the probability that other users face unlike me a real problem.
At least if it's possible with considerable effort.
next prev parent reply other threads:[~2010-09-28 20:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 2:42 LiveCD bootloader Teresa e Junior
2010-09-08 5:09 ` Brendan Trotter
2010-09-08 5:24 ` Brendan Trotter
2010-09-08 8:34 ` Robert Millan
2010-09-08 22:47 ` Teresa e Junior
2010-09-08 22:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 23:00 ` Teresa e Junior
2010-09-08 23:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 23:46 ` Teresa e Junior
2010-09-09 1:33 ` Brendan Trotter
2010-09-09 6:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 8:36 ` Robert Millan
2010-09-08 22:46 ` Teresa e Junior
2010-09-09 7:53 ` future of grub commands setup and install ? Treutwein Bernhard
2010-09-09 12:14 ` Robert Millan
2010-09-10 6:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-10 6:38 ` Treutwein Bernhard
2010-09-08 15:28 ` LiveCD bootloader Andreas Born
2010-09-08 15:46 ` Colin Watson
2010-09-08 16:31 ` GRUB2 fails when booting from CD Andreas Born
2010-09-26 20:22 ` Andreas Born
2010-09-27 15:17 ` Phillip Susi
[not found] ` <4CA1FEF0.4000209@googlemail.com>
[not found] ` <4CA215C9.9060000@cfl.rr.com>
[not found] ` <4CA219B9.3020209@googlemail.com>
[not found] ` <4CA22FC6.9000701@cfl.rr.com>
2010-09-28 20:19 ` Andreas Born [this message]
2010-12-25 20:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-27 12:30 ` Andreas Born
2011-01-04 14:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 22:48 ` LiveCD bootloader Teresa e Junior
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=4CA24DB4.9050202@googlemail.com \
--to=futur.andy@googlemail.com \
--cc=grub-devel@gnu.org \
--cc=psusi@cfl.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).