Am Samstag, den 17.10.2009, 02:39 -0400 schrieb Ron Murray:
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like I should file bug reports soon after doing the research,
not several weeks later. The root device is apparently chosen
(incorrectly, IMHO) by a line in /etc/grub.d/00_header:
prepare_grub_to_access_device `${grub_probe} --target=device \
${GRUB_FONT_PATH}`
which, of course, is the path to the fonts, not the pixmaps. Sorry for
the confusion.
Which is totally correct, because the GRUB root device is not the same
as the Linux kernel root= parameter.
It's the same in the sense that the value of root specifies the /
filesystem.
This is not at all incorrect.
The root value gets again set right inside the menu entry in case
your /boot is a different GRUB device then /usr.
Either we use
set root=(hd0,1)
loadfont /usr/share/grub/unicode.pf2
or we would need to use
loadfont (hd0,1)/usr/share/grub/unicode.pf2
but the first one is easier to create in scripts and only that one works
with the search command.
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.)
If 'ls -l' or `ls (hdx,y)' in real GRUB shows the right UUID but search
fails to find it then it is.
To avoid it you can set GRUB_FONT=/boot/grub/unicode.pf2
in /etc/default/grub and run update-grub.
Or you can even use ascii.pf2 if you don't need the full unicode set for
the menu entrys. Just make sure the font is copied from /usr/share/grub/
first.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
