Bug 639929 - the error in menu.lst after installation
Summary: the error in menu.lst after installation
Status: RESOLVED DUPLICATE of bug 626132
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: Final
Hardware: i686 openSUSE 11.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Josef Reidinger
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-16 22:42 UTC by Petr Matula
Modified: 2010-10-06 11:49 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Matula 2010-09-16 22:42:04 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8

Afer installation system not booted
 
in menu.lst :
---
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,11)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3...................
    root (hd0,11)
    kernel /boot/vmlinuz-2.6...............

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3................
    root (hd0,11)
    kernel /boot/vmlinuz-2.6............



---
my config:
md0 (RAID1) /dev/sda1 /dev/sdb1   swap
md1 (RAID1) /dev/sda2 /dev/sdb2   /




I've got change menu.lst to:
---
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3...................
    root (hd0,1)
    kernel /boot/vmlinuz-2.6...............

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3................
    root (hd0,1)
    kernel /boot/vmlinuz-2.6............
-----



After update kernel problem is back.
In menu.lst is hd0,11 again.
----
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3 - 2.6.34.4-0.1
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.34.4-0.1-desktop root=/dev/disk/by-id/md-uuid-8a22452a:86e50319:a6c3f8e1:d5816a12 resume=/dev/disk/by-id/md-uuid-6a64eca0:f41cbfcf:b5d656b9:b0b46598 splash=silent quiet showopts vga=0x322
    initrd /boot/initrd-2.6.34.4-0.1-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3 - 2.6.34.4-0.1
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.34.4-0.1-desktop root=/dev/disk/by-id/md-uuid-8a22452a:86e50319:a6c3f8e1:d5816a12 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x322
    initrd /boot/initrd-2.6.34.4-0.1-desktop
---



Reproducible: Always
Comment 1 Petr Matula 2010-09-16 22:46:42 UTC
Sorry, menu.lst after update kernel


default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,11)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.3 - 2.6.34.4-0.1
    root (hd0,11)
    kernel /boot/vmlinuz-2.6.34.4-0.1-desktop
root=/dev/disk/by-id/md-uuid-8a22452a:86e50319:a6c3f8e1:d5816a12
resume=/dev/disk/by-id/md-uuid-6a64eca0:f41cbfcf:b5d656b9:b0b46598
splash=silent quiet showopts vga=0x322
    initrd /boot/initrd-2.6.34.4-0.1-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3 - 2.6.34.4-0.1
    root (hd0,11)
    kernel /boot/vmlinuz-2.6.34.4-0.1-desktop
root=/dev/disk/by-id/md-uuid-8a22452a:86e50319:a6c3f8e1:d5816a12 showopts
apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off
processor.max_cstate=1 nomodeset x11failsafe vga=0x322
    initrd /boot/initrd-2.6.34.4-0.1-desktop
Comment 2 Josef Reidinger 2010-10-06 11:49:36 UTC
thanks for report.
It is already reported and it should be in maintenance update process already, so I hope that next kernel update should work as expected.

*** This bug has been marked as a duplicate of bug 626132 ***