Bug#546021: Thanks for the clarification
Felix Zielcke
fzielcke at z-51.de
Wed Nov 11 18:20:41 UTC 2009
Am Mittwoch, den 11.11.2009, 13:01 -0500 schrieb Ron Murray:
> Ah, thanks for clearing that up. Again, sorry for the confusion.
>
> The problem, then, seems to be that grub is going into rescue mode
> when it first comes up. On my machines, at least, it looks for a
> floppy, can't find one, gives up, then manages to go into its normal
> boot mode after all.
> Do you know why it would be doing this? I can't find any settings
> anywhere to invoke recue mode on initial boot (and it doesn't sound
> like it's something you'd need anyway). I haven't been able to find
> any documentation on it either; I'm loth to dig into the source code,
> but I'm prepared to do that if there's no other way. Admittedly, this
> is not a serious bug (the only real effect is that the boxes take
> about 30 seconds longer to boot), but it's annoying. Especially since
> grub2 doesn't seem to have a working savedefault option, so if I want
> to boot into the non-default operating system (Windows), I have to sit
> and wait while grub goes through its rescue disk antics.
It's normal that first rescue mode gets loaded and then normal mode.
If it wouldn't you can't access rescue mode if it fails to load normal
mode.
If it loads normal mode automatically and you don't need to type any
commands then there's no problem with the embed core.img.
If you don't use/need the floppy much then just disable it in BIOS.
Then at least real GRUB can't access it at all.
I don't know if Windows/Linux still would check if it exists.
savedefault has been integrated in the uploaded version to experimental.
Ubuntu karmic has released with it integrated so I hope this doestn't
need much testing to get merged into trunk and so the unstable uploads.
> I suspect that this problem may be the cause of some other grub-pc
> bugs too: 549905, for one. And, as you suggested,
>
> > I think it's the same bug as 546021 from Arthur.
> > (Message #22 is the actual start of the bug report, he wrongly
> > misused the original report for his bug.)
>
> ... except that 546021 is this bug. Which one did you mean?
>
> Thanks for your help,
Args once again I fail at copy&paste
I meant #530357
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
More information about the Pkg-grub-devel
mailing list