Bug#495049: why is (fd0) hard-coded into the grub image?
fzielcke at z-51.de
Fri Aug 15 16:36:49 UTC 2008
Am Freitag, den 15.08.2008, 09:28 -0700 schrieb ian_bruce at fastmail.fm:
> I would have mentioned it before, except that it didn't seem relevant,
> because I don't have a floppy disk, and neither "device.map" nor
> "grub.cfg" refer to it.
Aha, it doestn't seem relevant because you don't have a floppy drive and
you didn't found a place why grub thinks that you have one.
> "because" -- I didn't say that. You made it up.
> > Please stop assuming things if you don't understand how GRUB works.
> If "the problem is that GRUB thinks fd0 is your bootdevice", then
> it seems that I understood the situation correctly.
>From your bug submission:
It turns out that the file "core.img" does not contain
the string "normal".
> >> -- why does adding an "fd0" entry to "device.map" not resolve this
> >> error?
> If (fd0) is an "unknown device", then why doesn't "(fd0) /dev/fd0" make
> it known?
Because the file is called device.map
Which means map linux devices to grub devices.
> > I assume you don't know enough C to understand the whole sourcecode.
> You assume wrong.
I still assume that, because you even failed to choose the right
severity of this report.
The Debian documentation about this is very clear.
Honourly I don't have still any motivation at all for this report.
Luckly I have already forwarded this to grub-devel and somebody had an
So now you can proof how much your C knowledge is and your understanding
of GRUB sourcecode.
please add to disk/lvm.c to the mod_init function:
grub_errno = GRUB_ERR_NONE;
please do not forgot to do grub-install /dev/sda or whatever the disk is
you boot from, else the real GRUB isn't updated but of course you know
More information about the Pkg-grub-devel