Bug#280086: update-grub generates bad splashimage if /boot is not /
Jay Berkenbilt
Jay Berkenbilt <ejb@ql.org>, 280086@bugs.debian.org
Sat, 06 Nov 2004 22:30:45 -0500
Package: grub
Version: 0.95+cvs20040624-10
Severity: important
Note: I've classified this bug as important because the manifestation
of it could be an unreadable boot screen if /boot/grub/splash.xpm.gz
exists and the boot partition is not /.
My /boot is (hd0,1) and is a separate partition from /. If I create
/boot/splash.xpm.gz, update-grub generates the line
splashimage=(hd0,1)/boot/grub/splash-xpm.gz
instead of the line
splashimage=(hd0,1)/grub/splash-xpm.gz
which is really what is required. In other words, update-grub should
compute the path to the splashimage relative to the root of the boot
partition, whatever that is. The same logic is already applied in
update-grub for computing the correct path to the kernel and initial
ramdisk images, so the change should be straightforward.
On my system, the result is that the grub menu doesn't display and the
console font once the system boots is so mangled you can't read
anything on the screen, hence my classification of this bug as
important.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages grub depends on:
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
-- no debconf information