[Bug 1199791] New: nvidia update => text console instead of kde gui
http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 Bug ID: 1199791 Summary: nvidia update => text console instead of kde gui Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: epistemepromeneur@free.fr QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My desktop PC : - an intel IGP (the monitor is connected to) - an NVIDIA DGP (used for OpenCL and CUDA only) : NVIDIA GeForce GT 1030 The G06 and kernel-firmware-nvidia rpms are installed. Each time nvidia packages are updated when restarting the PC, we get a text console instead of the KDE GUI. I must use yast2 software manager to delete all about NVIDIA, then reinstall all NVIDIA packages for computing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199791 Andreas Stieger <Andreas.Stieger@gmx.de> 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#c1 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |epistemepromeneur@free.fr Assignee|gfx-bugs@suse.de |sndirsch@suse.com Flags| |needinfo?(epistemepromeneur | |@free.fr) --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> --- Ok. I suggest to run the next time after update: dmesg -c > /dev/null modprobe nvidia Then add here the output when running dmesg -- 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 <epistemepromeneur@free.fr> --- 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#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- I don't think so. Most likely there is an issue with compiling and/or installing the updated nvidia kernel modules. Therefore I need the information I requested above. If I understood correctly you're using suse-prime in nvidia mode ("prime-select nvidia"). For this a working nvdiai X server module is needed. This needs working nvidia kernel modules. -- 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 <epistemepromeneur@free.fr> --- 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#c5 --- Comment #5 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. Maybe that's a problem. In %post of nvidia-glG06 package 'prime-select nvidia' is executed if "prime-select get-current" results in "....undefined". And suse-prime is autoselected to be installed if the nvidia packages are installed and an Intel GPU exists. We assume an Laptop Optimus system (Laptop with Intel + nVidia GPU) in that case. Desktop system with active Intel and nVidia GPUs are indeed rare. I suggest to uninstall suse-prime package and taboo it in your case. Could be that this already fixes the issue. -- 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 <epistemepromeneur@free.fr> --- 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#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- Ok. I don't know. Could be. I suggest to open a ticket for this against Packagekit. Or just use PackageKit as notification, that there are updates and use YaST or zypper to do the update. -- 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 <epistemepromeneur@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(epistemepromeneur | |@free.fr) | --- Comment #8 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- 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#c9 --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Episteme PROMENEUR from comment #8)
I opened a bug report on 2 Jun 2019.
Still open.
If I understand well, the following bug report says the issue is fixed on 17 Avril 2022.
Still open.
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.
It's not fixed. You could open a separate opensuse ticket and request to add the fix from github to our package, since apparently nobody is looking into the issue and the fix upstream. :-( -- 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 <epistemepromeneur@free.fr> --- 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#c11 --- Comment #11 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- Locking prime packets is just a workaround. May I suggest to extend prime technology to Desktop with an IGP and a DGP ? Saving energy is today also a needing feature for a desktop. 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 ? 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#c12 --- Comment #12 from Stefan Dirsch <sndirsch@suse.com> --- (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#c13 --- Comment #13 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Episteme PROMENEUR from comment #10)
I created a bug report here https://bugzilla.opensuse.org/show_bug.cgi?id=1199895
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#c14 --- Comment #14 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- 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#c15 --- Comment #15 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- I disabled secure boot then now again computing with nvidia card is running. No more problem. I must add this: with secure boot enabled when executing gub menu "opensuse leap 15.3" then I get a text window with an error message : creating ..<something> ERR..G <something> Sorry, I can't stop the screen to write the message. -- 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 <sndirsch@suse.com> --- 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#c17 --- Comment #17 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- 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! -- 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 <sndirsch@suse.com> --- (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.
participants (1)
-
bugzilla_noreply＠suse.com