Bug 551713 - Broken menu.lst and initrd after updating from rc1 to rc2
Summary: Broken menu.lst and initrd after updating from rc1 to rc2
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Kernel (show other bugs)
Version: RC 2
Hardware: x86-64 openSUSE 11.2
: P3 - Medium : Major with 5 votes (vote)
Target Milestone: ---
Assignee: Michal Marek
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-01 12:47 UTC by Forgotten User v5inq2MBSE
Modified: 2012-08-02 16:00 UTC (History)
4 users (show)

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


Attachments
Modified /lib/mkinitrd/scripts/setup-modules.sh (12.55 KB, text/plain)
2009-11-01 12:47 UTC, Forgotten User v5inq2MBSE
Details
/boot/grub/menu.lst before update (1.16 KB, text/plain)
2009-11-01 12:50 UTC, Forgotten User v5inq2MBSE
Details
/boot/grub/menu.lst after update (362 bytes, text/plain)
2009-11-01 12:51 UTC, Forgotten User v5inq2MBSE
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User v5inq2MBSE 2009-11-01 12:47:07 UTC
Created attachment 325015 [details]
Modified /lib/mkinitrd/scripts/setup-modules.sh

User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.1 (like Gecko) SUSE

It's taken a long time to find out, rc2 repository is available in factory-snapshot and not in factory, but today I've updated my Latitude D620 from rc1 to rc2.
The kernel update resulted in a menu.lst without entries and a non existing initrd. I've copied the menu.lst.old and changed kernel versions by hand and tried to let run mkinitrd, but it resulted in a:

Kernel image:   /boot/vmlinuz-2.6.31.5-0.1-desktop
Initrd image:   /boot/initrd-2.6.31.5-0.1-desktop
Root device:    /dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO936400A2160AGN-part3 (/dev/sda3) (mounted on / as ext4)
Resume device:  /dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO936400A2160AGN-part2 (/dev/sda2)
Kernel Modules: thermal_sys thermal pata_acpi processor fan intel-agp drm video i2c-algo-bit i915 modeset=1 crc16 jbd2 ext4
Module modeset=1 not found.

Yes I'm using KMS for my intel chipset gpu. I've modified /lib/mkinitrd/scripts/setup-modules.sh to get my initrd, but I'm not happy with this workaround.

Reproducible: Always

Steps to Reproduce:
1. install rc1
2. use i915.modeset=1 as kernel parameter
3. update to rc2
Actual Results:  
Broken /boot/grub/menu.lst
Missing /boot/initrd-2.6.31.5-0.1-desktop

Expected Results:  
Updated /boot/grub/menu.lst
Crated /boot/initrd-2.6.31.5-0.1-desktop
Comment 1 Forgotten User v5inq2MBSE 2009-11-01 12:50:20 UTC
Created attachment 325017 [details]
/boot/grub/menu.lst before update
Comment 2 Forgotten User v5inq2MBSE 2009-11-01 12:51:21 UTC
Created attachment 325018 [details]
/boot/grub/menu.lst after update
Comment 3 Michal Marek 2009-11-05 10:15:20 UTC
Do you have "i915 modeset=1"  in /etc/sysconfig/kernel:INITRD_MODULES? Did you manually add it or did the installer do this?
Comment 4 Forgotten User v5inq2MBSE 2009-11-05 20:49:22 UTC
There's no modeset=1 in INITRD_MODULES:

INITRD_MODULES="thermal pata_acpi processor fan intel_agp drm i915"

I've added it manually in /etc/sysconfig/bootloader

DEFAULT_APPEND="resume=/dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO936400A2160AGN-part2 splash=silent quiet showopts i915.modeset=1"

and removed the entry in FAILSAFE_VGA.

And no, modeset was not activated by default.
Comment 5 Monnom Ammoi 2009-11-25 23:18:50 UTC
Same problem with opensuse 11.2 final (x86).

I didn't wrote "modeset=1" in /boot/grub/menu.lst. There isn't any "modeset" character string in /etc nor /boot files.

If I add "i915" manually in /etc/sysconfig/kernel:INITRD_MODULES and then execute "mkinitrd", the bug appears ("Module modeset=1 not found"). Idem if I modify sysconfig files with Yast.
Comment 7 Jeff Mahoney 2012-08-02 15:59:40 UTC
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users.  We're working hard to make openSUSE 12.2 the best openSUSE release yet!
Comment 8 Jeff Mahoney 2012-08-02 16:00:38 UTC
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users.  We're working hard to make openSUSE 12.2 the best openSUSE release yet!