[Bug 615680] New: KMS not active after update
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c0 Summary: KMS not active after update Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 7 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sndirsch@novell.com QAContact: jsrain@novell.com CC: eich@novell.com, mhopf@novell.com, tiwai@novell.com Found By: --- Blocker: --- Due to a missing 'Prereq: mkinitrd' in our kernel-<flavor> specfiles it can happen that the kernel package is updated before mkinitrd. The result is that the appropriate KMS modules are not being added to initrd by mkinitrd, since adding KMS modules is a new feature of mkinitrd in openSUSE 11.3. That issue is going to trigger a lot of bugreports like Bug #614734. I would appreciate it if we could still fix that issue for next RC or GM, since that would save me a lot of time when 11.3 is available for download/purchase. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c1 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rkrell@gmx.net --- Comment #1 from Stefan Dirsch <sndirsch@novell.com> 2010-06-19 09:16:01 UTC --- *** Bug 614734 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=614734 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c2 --- Comment #2 from Takashi Iwai <tiwai@novell.com> 2010-06-19 10:14:05 UTC --- Doesn't it need to give the specific version-release or such for prereq mkinitrd? Otherwise even an old mkinitrd without KMS hack would satisfy the requirement. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c3 --- Comment #3 from Stefan Dirsch <sndirsch@novell.com> 2010-06-19 10:52:30 UTC --- Good point. I didn't think about that. Unfortunately version number of mkinitrd didn't change since openSUSE 11.2 (still at 2.5.10). :-( So we would also need a higher version number for mkinitrd (> 2.5.10) and add 'Prereq: mkinitrd > 2.5.10' to kernel-<flavor> specfiles. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c4 --- Comment #4 from Michal Marek <mmarek@novell.com> 2010-06-21 11:36:02 UTC --- There is Requires(post): mkinitrd in the kernel spec files. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c5 --- Comment #5 from Takashi Iwai <tiwai@novell.com> 2010-06-21 11:54:57 UTC --- (In reply to comment #4)
There is Requires(post): mkinitrd in the kernel spec files.
Yeah but it alone doesn't help because of the reason in comment 2? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c6 --- Comment #6 from Michal Marek <mmarek@novell.com> 2010-06-21 11:59:18 UTC --- What happens if you boot the 11.3 kernel in an old system without kms-enabled X? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c7 --- Comment #7 from Takashi Iwai <tiwai@novell.com> 2010-06-21 12:07:07 UTC --- (In reply to comment #6)
What happens if you boot the 11.3 kernel in an old system without kms-enabled X?
It should work, no matter whether KMS is used or not (at the last time I tested quite ago). So, requiring the new mkinitrd doesn't break the old system, at least. OTOH, the new X with the old mkinitrd breaks. So, there are two things behind this issue: - who should give the dependency (and how) on a certain mkinitrd with KMS support - who triggers mkinitrd at which timing It doesn't have to be the kernel package who do the both, if there is a good alternative. The dependency could be in X, in theory. But triggering is obviously not... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c8 --- Comment #8 from Stefan Dirsch <sndirsch@novell.com> 2010-06-21 12:10:00 UTC --- (In reply to comment #6)
What happens if you boot the 11.3 kernel in an old system without kms-enabled X?
What's the background of this question? I mean do we need to officially support the 11.3 kernel on older systems? Why? In case you don't want to see a different X behaviour after updating kernel and mkinitrd you can still add 'nomodeset' as kernel boot option ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c9 --- Comment #9 from Michal Marek <mmarek@novell.com> 2010-06-21 12:50:40 UTC --- We do not officially support running new kernels in older systems, but we want it to work and to be as easy as possible (for our selfish reason - better testing coverage of the new kernel). Hence my question. Now from my understanding the situation is: new kernel + new X + new mkinitrd (i.e. 11.3 as is) -> GOOD new kernel + new X + old mkinitrd -> BAD new kernel + old X + any mkinitrd -> GOOD correct? IOW it's X that requires the mkinitrd kms scripts (and kms-capable kernel drivers), so the dependency could be added there. Another option would be %if 0%{?suse_version} >= 1130 Requires(post): mkinitrd >= 2.6.0 %else Requires(post): mkinitrd %endif in kernel-*.spec, so that users just wanting to try the new kernel on 11.2 or older won't be bothered by the dependency. BTW, I just submitted mkinitrd with a 2.6.0 version number to Factory. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c10 --- Comment #10 from Stefan Dirsch <sndirsch@novell.com> 2010-06-21 13:05:45 UTC --- I agree with your assumption. Just it wouldn't help to let X depend on an newer mkinitrd, since that wouldn't make sure that mkinitrd is installed before the kernel upgrade (the initial issue as reported here). Hence let's add the snippet to our kernel-<flavor> specfiles as you've suggested: %if 0%{?suse_version} >= 1130 Requires(post): mkinitrd >= 2.6.0 %else Requires(post): mkinitrd %endif -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c11 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #11 from Michal Marek <mmarek@novell.com> 2010-06-21 13:20:06 UTC --- OK, I added this to git. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c12 --- Comment #12 from Stefan Dirsch <sndirsch@novell.com> 2010-06-21 13:29:57 UTC --- (In reply to comment #11)
OK, I added this to git.
Thanks. Hope to see this still in 11.3 (>= RC2). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=615680 http://bugzilla.novell.com/show_bug.cgi?id=615680#c13 --- Comment #13 from Bernhard Wiedemann <bwiedemann@suse.com> --- This is an autogenerated message for OBS integration: This bug (615680) was mentioned in https://build.opensuse.org/request/show/42060 11.3:Test / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com