http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |X11 3rd Party Driver Assignee|screening-team-bugs@suse.de |gfx-bugs@suse.de QA Contact|qa-bugs@suse.de |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c2 --- Comment #2 from Episteme PROMENEUR --- I wonder if the NVIDIA driver update switches KDE GUI to use NVIDIA adapter instead of keep on using the intel IGP. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c4 --- Comment #4 from Episteme PROMENEUR --- AS I said in the description of the problem, I speak about a desktop not a laptop and the monitor is connected to the Intel IGP not to the Nvidia DGP. I assume this case is not a case well managed by the PRIME Technology. Nevertheless Suse Prime is in the good state "you use currently Intel". I checked after update in the text console with "prime-select intel" that intel adapter is already selected. Today in Konsole if I type "prime-select get-current" I get "Driver configured: undefined" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c6 --- Comment #6 from Episteme PROMENEUR --- Ok, but there is a problem. Packagekit does not respect yast2 software manager "taboo" feature. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c8 Episteme PROMENEUR changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(epistemepromeneur | |@free.fr) | --- Comment #8 from Episteme PROMENEUR --- I opened a bug report on 2 Jun 2019. https://github.com/PackageKit/PackageKit/issues/325 If I understand well, the following bug report says the issue is fixed on 17 Avril 2022. https://github.com/PackageKit/PackageKit/pull/543 What do you understand? The openSUSE date version of packagekit is 20 August 2021. If this is fixed, it would be a good thing to update packagekit with the version after 17 April 2022. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c10 --- Comment #10 from Episteme PROMENEUR --- I created a bug report here https://bugzilla.opensuse.org/show_bug.cgi?id=1199895 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c12 --- Comment #12 from Stefan Dirsch --- (In reply to Episteme PROMENEUR from comment #11)

Locking prime packets is just a workaround.

I still consider adding a nVidia card and not also using it for your monitor(s) a corner case. Having both enabled in a laptop by default is different to that!

May I suggest to extend prime technology to Desktop with an IGP and a DGP ?

I consider this a corner case and I don't think this will still happen with obsolete X11 technology.

Saving energy is today also a needing feature for a desktop.

I believe this already happens when nouveau driver is loaded. An unused nVidia card is not running in full speed then.

May I suggest some kind of "off" mode for prime in case for example we don't want to use the DGP or the IGP for the monitor ?

"prime-select offload" is already there for Laptop Optimus systems, so nVidia is only waked up if needed for 3D graphics rendering. But Turing platform or later is needed for this. See also https://github.com/openSUSE/SUSEPrime#installationusage https://download.nvidia.com/XFree86/Linux-x86_64/435.21/README/primerenderof... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c14 --- Comment #14 from Episteme PROMENEUR --- I don't know if this is related, but yesterday I enabled secure boot: all was enabled except "other OS" instead of "efi mode windows" in the bios. today i start the PC then i monitor that my computing was not running. with nvidia settings tool i see there no info about the card. with gkrellm no temperatures. i reinstalled nvidia compute G06 and kernel firmware nvidia. then nothing with gkrellm and nvidia settings. I get this localhost:~ # dmesg -c > /dev/null localhost:~ # modprobe nvidia modprobe: ERROR: could not insert 'nvidia': Key was rejected by service -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c16 --- Comment #16 from Stefan Dirsch --- When switchting to secure boot you need to reinstall the G06 KMP package and reboot your machine. More details here: https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 http://bugzilla.opensuse.org/show_bug.cgi?id=1199791#c18 --- Comment #18 from Stefan Dirsch --- (In reply to Episteme PROMENEUR from comment #17)

Thanks, computing again is running.

But deleting the G06 kmp package triggers the installation of about 10 packages , some about kmp preempt.

A good solution is to delete all packages about nvidia then reinstall all about nvidia.

I don't understand why all these are not automatic. Imagine Mr Jo installing an nvidia card!

Switching secure boot on/off I would call a corner case. Replacing the G06 KMP the "easiest" is rpm -e nvdia-gfxG06-kmp-default --nodeps zypper in nvdiia-gfxG06-kmp-default Signing for Secure Boot is done in %post of KMP package, if enabled. Since we don't want to confuse user without Secureboot for the next boot, where you need to accept the generated Secureboot key. Unfortunately we cannot presign the modules. We need to be built these on the target system. Things will improve with nVidias OpenSource drivers in the long run for (Turing platform and newer), for which we can prebuilt and Secureboot presigned kernel modules. -- You are receiving this mail because: You are on the CC list for the bug.