https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c1 Carl Fletcher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caf4926@opensuse-forums.org --- Comment #1 from Carl Fletcher 2013-02-07 15:42:20 UTC --- Seems to affect 02 as well. If you try rolling back, do you still get Nouveau? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c3 --- Comment #3 from Robert Munteanu 2013-02-07 16:26:57 UTC --- Some more information * it's not the nouveau driver that's being loaded, since after uninstalling it I still get the same problem * even after symlinking the driver to /lib/modules/3.4.11-2.16-desktop/weak-updates/updates I have to perform the insmod manually ; it is not loaded at startup -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c5 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #5 from Wolfgang Bauer 2013-02-07 19:23:53 UTC --- I had the same problem today. For some reason, Yast first installed G03 and afterwards removed G02 including the nouveau blacklist. Therefore on reboot the nouveau kernel module was loaded which prevented the loading of the nvidia driver. Workaround: - Remove the driver completely with Yast - Start Yast a second time and install your driver of choice Now everything should work again... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c7 --- Comment #7 from Wolfgang Bauer 2013-02-08 10:52:33 UTC --- (In reply to comment #6)

It seemed to drag in some unnecessary crud in the process.

Didn't happen here, only nvidia-computeG03, x11-video-nvidiaG03 and nvidia-gfxG03-kmp-desktop got installed. What unnecessary crud do you mean btw.? If it's gcc and its dependencies then that's needed because the kernel module is now compiled on installation.

Something is pretty wrong IMO This is just a workaround

Well, AFAICT the only thing that does not work is directly switching from G02 to G03 or vice versa. If you uninstall first and then install the other one everything works as expected. It did for me at least. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c Du Weihua changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |whdu@suse.com AssignedTo|bnc-team-screening@forge.pr |sndirsch@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |X11 3rd Party Driver QAContact|qa-bugs@suse.de |sndirsch@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c11 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |robert.munteanu@gmail.com --- Comment #11 from Stefan Dirsch 2013-02-27 13:05:30 UTC ---

$ rpm -qa | grep nvidia nvidia-gfxG03-kmp-desktop-310.32_k3.4.6_2.10-5.1.x86_64 x11-video-nvidiaG03-310.32-5.1.x86_64 nvidia-computeG03-310.32-5.1.x86_64

And with that you still see the issue? Please check also the output of rpm -V $(rpm -qa | grep nvidia) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c13 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #13 from Stefan Dirsch 2013-02-27 13:26:08 UTC --- Ok. Although the workaround works, I believe the explanation is wrong. Most likely you've ended up in having the wrong kernel module installed and loaded (G03 one) and still running the G02 X driver. The file for blacklisting the nouveau module is in both packages, so this would not have been deleted by RPM. Even if the G03 KMP package had replaced the G02 KMP. RPM installs the file from the new package and then removes the files of the old package, which are *not* part of the new package. Anyway, what you've done has been a manual package (de)selection, i.e. removed the nvidia-gfxG02 package and installed the nvidia-gfxG03 package. *And* ignored the other G02 packages,i.e. you didn't replace these as well. The result has been a driver messup. Package autoselection is not affected here. There are only a few supplements in the G03 package. And these are not part of the G02 package. Closing as INVALID therefore. Feel free to reopen in case you manage to have only G03 packages installed and the issue still exists. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c15 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #15 from Stefan Dirsch 2013-02-27 19:50:14 UTC --- Yeah. Seems in %postun of the old KMP the weak-update symlink to the installed kernel module gets removed. The issue is, that the %postun of the replaced KMP runs after %post of the new KMP. How to address that? No idea right now. But then we would have run into this issue each time one just updated the KMP. But we didn't, did we? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c16 --- Comment #16 from Wolfgang Bauer 2013-02-28 12:36:00 UTC --- (In reply to comment #15)

Yeah. Seems in %postun of the old KMP the weak-update symlink to the installed kernel module gets removed. The issue is, that the %postun of the replaced KMP runs after %post of the new KMP. How to address that? No idea right now.

Since %postun is run _after_ the packaged files are removed, you could maybe check if nvidia.ko exists and only remove the link if it doesn't? (Just an idea though, not sure if that would work...)

But then we would have run into this issue each time one just updated the KMP. But we didn't, did we?

Well, on package updates %postun is not run, so this issue cannot happen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c18 --- Comment #18 from Wolfgang Bauer 2013-03-01 11:42:09 UTC --- (In reply to comment #17)

Sure it *is* running.

When "updating" to the same version, %postun is not run (that's what I tried before writing this and I thought this was always the case). But yes, on update to a different version it _is_ running (after %post). Anyway, I never had an issue during update, only when switching between G02 and G03. So it seems /usr/lib/module-init-tools/weak-modules2 is handling the update case correctly. But I guess in the switching case it gets confused because the filenames of the kernel modules are the same but the package names are different (nvidia-gfxG02 vs nvidia-gfxG03)... So maybe this should be reported as bug against module-init-tools then? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c20 --- Comment #20 from Wolfgang Bauer 2013-03-04 09:19:15 UTC --- Still reproducible here: - installed G02 drivers, made X work with nvidia driver (the issue also occurs on switching from G03 to G02) rpm -qa|grep nvidia: x11-video-nvidiaG02-304.64-27.1.i586 nvidia-gfxG02-kmp-desktop-304.64_k3.4.6_2.10-26.1.i586 nvidia-computeG02-304.64-27.1.i586 ls -l /lib/modules/3.4.28-2.20-desktop/weak-updates/updates/ insgesamt 0 lrwxrwxrwx 1 root root 49 4. Mär 09:42 nvidia.ko -> /lib/modules/3.4.6-2.10-desktop/updates/nvidia.ko rpm -V $(rpm -qa | grep nvidia) 5S.T..... /usr/bin/X.x11-video-nvidiaG02 ...T..... /usr/lib/xorg/modules/updates/drivers/nvidia_drv.so - started YaST, marked the 3 G02 packages for deinstallation, selected the G03 packages for installation (kmp-default got selected automatically, I had to select kmp-desktop manually), clicked on "Accept", waited for installation to finish - after reboot: X starts using the nouveau driver: rpm -qa|grep nvidia: nvidia-gfxG03-kmp-desktop-310.32_k3.4.6_2.10-15.1.i586 nvidia-computeG03-310.32-15.1.i586 x11-video-nvidiaG03-310.32-15.1.i586 ls -l /lib/modules/3.4.28-2.20-desktop/weak-updates/updates/ insgesamt 0 rpm -V $(rpm -qa | grep nvidia) 5S.T..... /usr/bin/X.x11-video-nvidiaG03 ...T..... /usr/lib/xorg/modules/updates/drivers/nvidia_drv.so If I then create the link manually and run depmod -a, after a reboot the system starts correctly, using the nvidia driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c22 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@suse.com --- Comment #22 from Stefan Dirsch 2013-03-04 11:18:59 UTC --- Ok. I could reproduce the issue with the removed weak-updates symlink (nvidia-gfxG02-kmp-desktop --> nvidia-gfxG03-kmp-desktop update) when the kernel has been updated first. Creating the weak-updates symlink and running "depmod -a" fixes the issue. For some reason I don't see the issues when just updating nvidia-gfxG03-kmp-desktop package. I would have expected the same issue when looking at the %preun/%postun scripts. Michal, could it be that wm2 removes the symlink although the kernel module still exists, but only does that if it belongs to a different package? This would explain the behaviour. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c24 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mmarek@suse.com --- Comment #24 from Stefan Dirsch 2013-03-05 22:00:12 UTC --- Michal, see comment #22. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c27 --- Comment #27 from Michal Marek 2013-03-21 09:43:56 UTC --- First of all, I'm sorry for the delay. (In reply to comment #22)

For some reason I don't see the issues when just updating nvidia-gfxG03-kmp-desktop package. I would have expected the same issue when looking at the %preun/%postun scripts.

Did you test with the kernel that the KMP was built against? In this case the module is installed below /lib/modules/.../extra or .../updates and this is handled by rpm. Admittedly, rpm is lot smarter than the weak-modules2 script.

Michal, could it be that wm2 removes the symlink although the kernel module still exists, but only does that if it belongs to a different package? This would explain the behaviour.

Yes. weak-modules2 --remove-kmp always removes all the symlinks, and then looks for the newest among other versions of the kmp to create new symlinks. I.e. package renames are not handled. I will change it to also consider packages that contain the same set modules, which should handle the nvidia case. It will not handle the case when you rename a KMP _and_ add or remove modules at the same time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c28 --- Comment #28 from Stefan Dirsch 2013-03-21 10:21:36 UTC --- (In reply to comment #27)

First of all, I'm sorry for the delay.

(In reply to comment #22)

...

For some reason I don't see the issues when just updating nvidia-gfxG03-kmp-desktop package. I would have expected the same issue when looking at the %preun/%postun scripts.

Did you test with the kernel that the KMP was built against?

No, the kernel has been updated meanwhile. IIRC updating the kernel was necessary to reproduce the issue.

In this case the module is installed below /lib/modules/.../extra or .../updates and this is handled by rpm. Admittedly, rpm is lot smarter than the weak-modules2 script.

...

Michal, could it be that wm2 removes the symlink although the kernel module still exists, but only does that if it belongs to a different package? This would explain the behaviour.

Yes. weak-modules2 --remove-kmp always removes all the symlinks, and then looks for the newest among other versions of the kmp to create new symlinks. I.e. package renames are not handled. I will change it to also consider packages that contain the same set modules, which should handle the nvidia case. It will not handle the case when you rename a KMP _and_ add or remove modules at the same time.

Thanks. That would be great and covers perfectly this issue only containing one kernel module called "nvidia.ko". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c30 --- Comment #30 from Stefan Dirsch 2013-04-08 12:59:37 UTC --- Ok. Let's keep that one open as long as Michal didn't confirm that he adjusted weak-updates2 script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c32 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@suse.com --- Comment #32 from Stefan Dirsch 2013-06-18 04:43:00 UTC --- Interesting observation. Possibly Michael can explain the problem and how to resolve (or why it's not easily resolvable). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c34 --- Comment #34 from Wolfgang Bauer 2013-06-21 04:27:33 UTC --- (In reply to comment #33)

This happens when I try to install the G03 driver with SoftLocks on nvidia-gfxG02-kmp-desktop and nvidia-gfxG03-kmp-desktop. Then BOTH nvidia-gfxG02-kmp-default and nvidia-gfxG03-kmp-default get selected (with kernel-desktop installed).

Sorry that was a typo. It should read "This happens when I try to install the G02 driver" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c36 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mmarek@suse.com --- Comment #36 from Stefan Dirsch 2013-09-13 14:31:45 UTC --- Michal, ping? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=802624 https://bugzilla.novell.com/show_bug.cgi?id=802624#c37 --- Comment #37 from Michal Marek 2013-09-27 10:11:50 UTC --- Not yet, sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.