https://bugzilla.novell.com/show_bug.cgi?id=864701 https://bugzilla.novell.com/show_bug.cgi?id=864701#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Stefan Dirsch 2014-02-20 11:47:53 UTC --- NO_KMS_IN_INITRD just means that the KMS nouveau driver isn't loaded already in initrd, i.e. from the beginning. It's still loaded on demand when X is being started. I'm not aware of any differences in behaviour for the Xsession when it's loadied in initrd or later. Trying to revert it would possible mean changing it to a different value the user has set manually. That's the reason it is not reverted during %postun. And please don't rely on any comments in this forum thread. Already during browsing this thread I've seen a lot of arguments, which are simply wrong. -- 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=864701 https://bugzilla.novell.com/show_bug.cgi?id=864701#c2 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Wolfgang Bauer 2014-02-20 18:10:21 UTC --- (In reply to comment #1)

NO_KMS_IN_INITRD just means that the KMS nouveau driver isn't loaded already in initrd, i.e. from the beginning. It's still loaded on demand when X is being started. I'm not aware of any differences in behaviour for the Xsession when it's loadied in initrd or later. I thought so as well until yesterday.

But while this may be true in theory, I absolutely can reproduce an issue here (13.1, G03 driver, GTX 550 Ti card). In my case, nouveau is indeed used after uninstalling the nvidia driver, but it doesn't fully work obviously: KDE just hangs at the splash screen when logging in. Setting NO_KMS_IN_INITRD="no" and running mkinitrd fixes this. (disabling plymouth by adding "plymouth.enable=0" to the kernel boot options makes it work as well, even with NO_KMS_IN_INITRD="yes") So I really think the nvidia driver should set this back on uninstallation.

Trying to revert it would possible mean changing it to a different value the user has set manually. That's the reason it is not reverted during %postun. Well, but this argument could be turned to the opposite as well. If it was set to "no" before installing the driver (maybe even the user set it explicitely), it should be set back to this, especially if the system doesn't boot otherwise.

Maybe the rpm could remember whether it changed the setting in %post and only set it back in that case? There are only 2 possible settings anyway, "yes" or "no". OTOH, I'm not sure if NO_KMS_IN_INITRD="yes" is actually needed. It works fine here when I set it to "no" and recreate the initrd (with the nvidia driver installed), and the resulting initrd contains only the nvidia kernel module (no nouveau) and the blacklist /etc/modprobe.d/nvidia-desktop.conf. Shouldn't that be sufficient? But then I don't know really, so please forgive me if this is nonsense and there is a valid reason to set it to "yes". Please feel free to close this again if you disagree. -- 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=864701 https://bugzilla.novell.com/show_bug.cgi?id=864701#c4 --- Comment #4 from Stefan Dirsch 2014-02-21 11:31:29 UTC --- (In reply to comment #3)

...

OTOH, I'm not sure if NO_KMS_IN_INITRD="yes" is actually needed. It works fine here when I set it to "no" and recreate the initrd (with the nvidia driver installed), and the resulting initrd contains only the nvidia kernel module (no nouveau) and the blacklist /etc/modprobe.d/nvidia-desktop.conf. Shouldn't that be sufficient?

Hmm. Even better and easier, but I would like to verify this first.

Indeed this appears to work fine. At least on openSUSE 13.1. -- 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=864701 https://bugzilla.novell.com/show_bug.cgi?id=864701#c7 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #7 from Stefan Dirsch 2014-08-28 10:05:52 UTC --- Ok. It turned out, that this change for openSUSE >= 13.1 brought us more harm than benefit, when NVIDIA introduced nvidia-uvm module. See bnc#879767, comments #53 f. Hence reopening. -- 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=864701 https://bugzilla.novell.com/show_bug.cgi?id=864701#c9 --- Comment #9 from Wolfgang Bauer 2014-08-29 08:29:06 UTC --- (In reply to comment #8)

Ok. I've reverted this change now. Will be in place with next driver update (> 340.32). Closing as WONTFIX therefore.

Given the current circumstances, I do agree with that. Still I would like to see the change in NO_KMS_IN_INITRD being reverted when the driver package is uninstalled, which was the original purpose of this bug report. But as it should be fixed in Factory/13.2 anyway (as dracut ignores NO_KMS_IN_INITRD), it is not worth the effort, I suppose. -- 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.