Jason Thomas wrote:

the first splashimage entry is one that you must have added.  The second
one added after an update-grub is auto generated because it found a
splash image.

Just remove the first.
You are right - and wrong.
If you read the message carefully (and the comments in menu.lst) I have added the first one, true. But there is nothing wrong in adding a splashscreen at the very top, and it is my liberty to do so. How would I get a splashscreen then, as long as there is no kernel update ?? So the updater has to check if there is one already and not add a second one and thereby messing up the menu and display.

What you do not know: A year ago I had already noticed the two occurrences in another, earlier, install on another machine that had been screwed up as well and commented out the first one. Now take this: *this did not help*. The single, 'second' one above the kernel still screwed up the display and lead to not displaying the menu. So, the solution is not to delete the first, but not to auto-insert the second
1 . not without checking if another exists
2. not at that place

I haven't looked at the code, so I cannot tell you why this place above the kernel is so 'dangerous' and screws / might screw the display. In any case, blindly adding a second occurrence is shoddy coding. We must not put the constraints to the user side: "Never add a splashscreen manually"-"And if, delete your manual addition after an update" - "If things are still screwed, remove the later one and paste it on top".
I am sure everyone can agree here.

Thanks for looking into it,

Uwe

On Sun, Jul 17, 2005 at 11:30:54AM +0800, Uwe Dippel wrote:
Sorry, guys, for a new subject on a topic mentioned twice before:
I had reported about a messed up display; no grub menu showing; etc about a year ago.

Now I have the culprit: It is the kernel updater of grub; but eventually only on Debian ? And only when you use a splashscreen ?
Here is the proof:

This is menu.lst after fresh install; with some changes:
add Debian splash screen; add OpenBSD.
I have *not* touched the 'inner part' for autoupdates !


# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default         0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout         5

# Pretty colours
#color cyan/blue white/blue
# commented, because we have a SPLASH screen:
splashimage=(hd0,5)/grub/splash.xpm.gz

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title         Windows 95/98/NT/2000
# root          (hd0,0)
# makeactive
# chainloader   +1
#
# title         Linux
# root          (hd0,1)
# kernel        /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda7 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,5)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## ## End Default Options ##

title           Debian GNU/Linux, kernel 2.6.8-2-386
root            (hd0,5)
kernel          /vmlinuz-2.6.8-2-386 root=/dev/hda7 ro
initrd          /initrd.img-2.6.8-2-386
savedefault
boot

title           Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root            (hd0,5)
kernel          /vmlinuz-2.6.8-2-386 root=/dev/hda7 ro single
initrd          /initrd.img-2.6.8-2-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.

title
root

title           Other Operating Systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda2
title           Windozeexpee
root            (hd0,1)
savedefault
makeactive
chainloader     +1

# This entry added by Uwe for a manual install of OpenBSD

title           OpenBSD 3.7
root            (hd0,2)
makeactive
chainloader     +1

#
# done - UD



When I added the 686-kernel, the menu.lst looked identical, except the auto-updater had added the following:

@@ -93,6 +93,22 @@

## ## End Default Options ##

+splashimage=(hd0,5)/boot/grub/splash.xpm.gz
+
+title          Debian GNU/Linux, kernel 2.6.8-2-686
+root           (hd0,5)
+kernel         /vmlinuz-2.6.8-2-686 root=/dev/hda7 ro
+initrd         /initrd.img-2.6.8-2-686
+savedefault
+boot
+
+title          Debian GNU/Linux, kernel 2.6.8-2-686 (recovery mode)
+root           (hd0,5)
+kernel         /vmlinuz-2.6.8-2-686 root=/dev/hda7 ro single
+initrd         /initrd.img-2.6.8-2-686
+savedefault
+boot
+
title          Debian GNU/Linux, kernel 2.6.8-2-386
root           (hd0,5)
kernel         /vmlinuz-2.6.8-2-386 root=/dev/hda7 ro


From high up, it had taken the splashimage and added it here once again!

It only required me using vi and remove that second splashimage and everything was fine.

Question: does this happen on Debian only, or is it a general problem ??
I am running grub_0.95+cvs20040624-17_i386.deb


Uwe



_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-grub



_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-grub

Reply via email to