https://bugzilla.novell.com/show_bug.cgi?id=810022 https://bugzilla.novell.com/show_bug.cgi?id=810022#c0 Summary: nVidia proprietary drivers broken for 12.3 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: X11 3rd Party Driver AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tonysu@su-networking.com QAContact: sndirsch@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Scope of affected Users Unknown. I would guess should affect at least all who have avoided nouveau drivers in the past due to the notorious "kaleidescope" problem which has existed from approx openSUSE versions 11.1-12.2 Affects CUDA users Both KMS on/off Included are all the relevant logfiles I used to troubleshoot All logfiles were retrieved during the failed graphical boot by dropping into a command line console. Each of the logfiles were modified by adding as the first line the command used to retrieve that logfile Summary: Cause of problem appears to be Attempt to load non-existent "nevidia module" NOTE: Secondary issue, when changing from nVidia driver to nouveau or nv drivers, the xorg.conf file is not automatically modified or deleted, manual User intervention is required. apparently this is a long-standing unaddressed issue and unlike when the User is prompted to run nvidia.config when installing the proprietary nvidia driver, the User is not prompted or given any clue this is required when installing the nouveau or nv drivers. For this reason, although this is primarily a 3rd party driver problem, IMO the xorg.conf issue should be fixed by either whoever develops kdm or however the xorg-conf file is managed. Reproducible: Always Steps to Reproduce: Install or upgrade with nVidia Repo enabled. ftp://download.nvidia.com/opensuse/12.3/ As prompted, run nvidia-config to create the required xorg.config When booting, normally, click ESC to view the bootup sequence Immediately before reaching the Plymouth startup screen, note that bootup hangs on "Reached graphical user interface" This is where most people cannot proceed further Actual Results: System bootup hangs Expected Results: Proceed to Plymouth Proceeding from when the system hangs, It is at this point that the accompanying logs were retrieved Do not wait too long to escape to console by entering ALT-F1, otherwise after a minute or so the system will freeze. The following commands were used to retrieve the logs systemctl --all --type=target cat /var/log/boot.log journalctl -b systemctl status plymouth-start.service cat /var/log/Xorg.0.log IMO most important information from these logs, clearly the X server starts and an attempt is made to [LoadModule: "nvidia"] but failing that the Xserver stops. The system then attempts to connect to graphical.target and unable to find a running X server hangs (maybe there should also be a graceful fallback like automatically escape to console?) journal.log Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK xdm[736]: Starting service kdm..done Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started LSB: X Display Manager. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK acpid[580]: client connected from 801[0:0] Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK acpid[580]: 1 client rule loaded Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK kdm[771]: X server died during startup Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK kdm[771]: X server for display :0 cannot be started, session disabled Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK fail2ban[734]: Starting fail2ban ..done Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started LSB: Bans IPs with too many authentication failures. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Multi-User. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Reached target Multi-User. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Graphical Interface. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Reached target Graphical Interface. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Stop Read-Ahead Data Collection 10s After Completed Startup. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Update UTMP about System Runlevel Changes... Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started Update UTMP about System Runlevel Changes. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Startup finished in 3s 576ms 851us (kernel) + 4s 647ms 496us (userspace) = 8s 224ms 347us. Mar 17 18:12:51 SUSEMACHINE.LOCALNETWORK acpid[580]: client 801[0:0] has disconnected Xorg.0.log 7.899] Loading extension GLX [ 7.899] (II) LoadModule: "nvidia" [ 7.900] (WW) Warning, couldn't open module nvidia [ 7.900] (II) UnloadModule: "nvidia" [ 7.900] (II) Unloading nvidia [ 7.900] (EE) Failed to load module "nvidia" (module does not exist, 0) [ 7.900] (EE) No drivers available. [ 7.900] Fatal server error: [ 7.900] no screens found [ 7.900] (EE) -- 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.