[Bug 983934] New: X not coming up after latest nvidia update

bugzilla_noreply＠novell.com

9 Jun 2016 9 Jun '16

10:20

http://bugzilla.suse.com/show_bug.cgi?id=983934 Bug ID: 983934 Summary: X not coming up after latest nvidia update Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: holgi@suse.com QA Contact: sndirsch@suse.com Found By: --- Blocker: --- Created attachment 680285 --> http://bugzilla.suse.com/attachment.cgi?id=680285&action=edit Xorg.0.logs.tgz I updated my Leap 42.1 to nvidia-gfxG04-kmp-default (367.18_k4.1.12_1 25.1) and related other nvidia packages and after a reboot the X-system is not coming up again. Xorg.0.logs attached. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 2.5 KB)

Show replies by date

bugzilla_noreply＠novell.com

9 Jun 9 Jun

15:56

New subject: [Bug 983934] X not coming up after latest nvidia update

http://bugzilla.suse.com/show_bug.cgi?id=983934 http://bugzilla.suse.com/show_bug.cgi?id=983934#c7 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cvn@transpute.nl --- Comment #7 from Stefan Dirsch --- *** Bug 983927 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10 Jun 10 Jun

09:39

New subject: [Bug 983934] X not coming up after latest nvidia update

http://bugzilla.suse.com/show_bug.cgi?id=983934 http://bugzilla.suse.com/show_bug.cgi?id=983934#c10 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(trenn@suse.com) | --- Comment #10 from Stefan Dirsch --- Ok. The issue was homebrewn. This change fixed it for me. ------------------------------------------------------------------- Fri Jun 10 08:59:47 UTC 2016 - sndirsch@suse.com - Xwrapper: unload new nvidia_drm module first, i.e. definitely before nvidia_modeset (bnc#983934) Index: Xwrapper =================================================================== --- Xwrapper (revision 46) +++ Xwrapper (working copy) @@ -7,6 +7,8 @@ # rmmod nvidia_uvm first mods=$(lsmod | grep -v -E "nvidia_agp|nvidiafb" | grep -o -E "^(nvidia_uvm|nvidia|nvidia_modeset|fglrx)" | sort -u | tac) if [ $? -eq 0 ]; then + # new since release 367; sitting on top of nvidia_modeset; needs to be unloaded first + /sbin/rmmod -v nvidia_drm || true for m in ${mods}; do # bail out, if an existing module cannot be unloaded # this can happen if a second Xsession starts --> /usr/bin/X.x11-video-nvidiaG04 on the system Can anyone confirm this? Well, probably not. The repo has been rolled back to 361.42, which unfortunately currently is in a broken state. :-( (bnc#984111) So I will push this to NVIDIA and hope that things are then fixed for everyone. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:57

New subject: [Bug 983934] X not coming up after latest nvidia update

http://bugzilla.suse.com/show_bug.cgi?id=983934 http://bugzilla.suse.com/show_bug.cgi?id=983934#c11 --- Comment #11 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #10)

...

So I will push this fix to NVIDIA and hope that things are then fixed for everyone.

Done. It will take some time until the repo has been updated with the lastest 367.18 packages again. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:03

New subject: [Bug 983934] X not coming up after latest nvidia update

http://bugzilla.suse.com/show_bug.cgi?id=983934 http://bugzilla.suse.com/show_bug.cgi?id=983934#c12 --- Comment #12 from Holger Sickenberg --- (In reply to Stefan Dirsch from comment #11)

...

(In reply to Stefan Dirsch from comment #10)

...
So I will push this fix to NVIDIA and hope that things are then fixed for everyone.

Done. It will take some time until the repo has been updated with the lastest 367.18 packages again.

Thanks Stefan. I will try it once it is available via the repo. -- You are receiving this mail because: You are on the CC list for the bug.