[Bug 463228] New: Can't login into KDE4 with nv opensource driver
https://bugzilla.novell.com/show_bug.cgi?id=463228 User registration@grek.tuffmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463228#c8 Summary: Can't login into KDE4 with nv opensource driver Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: registration@grek.tuffmail.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Opensuse 11.1 comes with opensource driver for NVIDIA card installed by default. For my hardware it seems to be broken because I can't login into KDE4. It simply comes back to login screen short after it tries to start KDE4. I previously reported this problem as comment #8 in bug 450893 (https://bugzilla.novell.com/show_bug.cgi?id=450893#c7) but at that time I didn't know what is the cause. I still could log into KDE3 but in KDE3 I noticed that sysinfo:/ didn't work. Of course, sysinfo displays some information about graphic card so I came to idea that this might be different aspect of the same issue. After installing nvidia proprietary driver all problems have disappeared. I rate this as critical bug because default setup (if KDE3 is not installed) simply does not work and user have hard times to figure out how to fix it. Here is info about my hardware: grek-laptop:~ # hwinfo --gfxcard 26: PCI 100.0: 0300 VGA compatible controller (VGA) [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_10de_427 Unique ID: VCu0.fn56P0wnBA1 Parent ID: vSkL.vB63rdHOxV8 SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0 SysFS BusID: 0000:01:00.0 Hardware Class: graphics card Model: "nVidia GeForce 8400M GS" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x0427 "GeForce 8400M GS" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x30cc Revision: 0xa1 Driver: "nvidia" Driver Modules: "nvidia" Memory Range: 0xce000000-0xceffffff (rw,non-prefetchable) Memory Range: 0xd0000000-0xdfffffff (rw,prefetchable) Memory Range: 0xcc000000-0xcdffffff (rw,non-prefetchable) I/O Ports: 0x2000-0x2fff (rw) IRQ: 16 (1297 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v000010DEd00000427sv0000103Csd000030CCbc03sc00i00" Driver Info #0: XFree86 v4 Server Module: nvidia Driver Info #1: XFree86 v4 Server Module: nvidia 3D Support: yes Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (PCI bridge) -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c1
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c2
Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c3
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c4
--- Comment #4 from Stefan Dirsch
For a clean reproduction I'm afraid you need to uninstall the nvidia driver and generate xorg.conf from scratch.
.., i.e. running 'sax2 -r'. -- 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=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c5
Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c6
--- Comment #6 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c7
--- Comment #7 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c8
--- Comment #8 from Stefan Dirsch
Created an attachment (id=263067) --> (https://bugzilla.novell.com/attachment.cgi?id=263067) [details] Log cotaining information about vesa driver crash
1. Xorg.1.log should only be used when you start a second Xsession, e.g. for a different user. It's definitely not the one I requested here (Xorg.0.log.old). 2. vesa driver doesn't make sense. SaX2 uses nv driver for this hardware if NVIDIA driver is not installed. -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c9
--- Comment #9 from Stefan Dirsch
Created an attachment (id=263068) --> (https://bugzilla.novell.com/attachment.cgi?id=263068) [details] SaX crash information
No idea why xfine (the tool to configure monitor geometry) crashed here. But it's unrelated. nv driver is used as expected. -- 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=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c10
--- Comment #10 from Grzegorz Kossakowski
1. Xorg.1.log should only be used when you start a second Xsession, e.g. for a different user. It's definitely not the one I requested here (Xorg.0.log.old).
Ok, I'll attach Xorg.0.log.old but I'm quite sure it does not contain anything special.
2. vesa driver doesn't make sense. SaX2 uses nv driver for this hardware if NVIDIA driver is not installed.
I've used a config that sax2 -r generated for me. After sax2 crash I rebooted my machine, called init 3 and then sax2 -r. This second attempt was succesful and vesa driver was chosen by sax2 not me. :-) -- 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=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c11
--- Comment #11 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c12
--- Comment #12 from Stefan Dirsch
There is one more thing, right after I removed nvidia driver I tried to run sax2 -r as suggested but it froze my machine completely. I attach sax2.log >that contains some information about sax2 crash.
nv/nvidia driver don't like each other. You might need to reboot before you use SaX2 to create a nv driver configuration. -- 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=463228
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c13
--- Comment #13 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c14
--- Comment #14 from Grzegorz Kossakowski
There is one more thing, right after I removed nvidia driver I tried to run sax2 -r as suggested but it froze my machine completely. I attach sax2.log >that contains some information about sax2 crash.
nv/nvidia driver don't like each other. You might need to reboot before you use SaX2 to create a nv driver configuration.
I can understand this but I would expect sax2 to refuse to start with some small explanation (like one given above) instead of freezing whole machine. -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c15
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c16
--- Comment #16 from Stefan Dirsch
What is purpose of xorg.nvidia-post file? It contains following entry: Section "Device" BoardName "GeForce 8400M GS" BusID "1:0:0" Driver "vesa" Identifier "Device[0]" Screen 0 VendorName "NVidia" EndSection
This was the previous configuration (you've updated from an older openSUSE release?). When uninstalling the NVIDIA driver it gets reenabled. Thus I asked you to uninstall the nvidia driver and then recreate xorg.conf via SaX2 from scratch afterwards. -- 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=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c17
--- Comment #17 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c18
Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c19
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c20
--- Comment #20 from Grzegorz Kossakowski
Great. So you reinstalled the NVIDIA driver again, which results in SaX2 creating a NVIDIA driver configuration. I'm afraid we're getting nowhere here. We're back to commment #3. Feel free to reopen if you want to go this way. It doesn't seem so.
Stefan, I followed what you suggested and reproduced the problem which looks rather serious to me (if it's not specific to my hardware). I've made a copy of all logs *before* reinstalling nvidia driver just to make sure that I don't give you false data. There is my fault that I forgot to back up all xorg.conf files at the same time but simply closing this bug is not the best way to deal with this situation. The computer I'm using at the moment is the only I can access to and I wasn't sure if you respond to my report within just a few minutes of few days. I want to help you to fix a bug but at the same time I need a working machine. Tell me exactly what you want from me, I mean: do you want me to uninstall nvidia driver *and* wait until you say you don't need anything else from me? -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c21
--- Comment #21 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c22
Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c23
Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c24
--- Comment #24 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c25
--- Comment #25 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c26
Stefan Dirsch
Created an attachment (id=263074) --> (https://bugzilla.novell.com/attachment.cgi?id=263074) [details] SaX.log - failed to test nv configuration
I attach sax log again because this time sax2 failed to let me test my configuration. After changing resolution to my native (1280x800) it asked me if I want to test it or save, I chose to test it. Sax tried to initialize graphic card in new mode but failed to display anything and returned back after about one second.
I don't know if it's relevant but I think it's better to inform you about this issue.
Thanks. The reason is the SaX.log sh: line 1: 3984 Segmentation fault /usr/sbin/xfine -display :99 > /dev/null 2>&1 Don't know why xfine crashes though. -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c27
--- Comment #27 from Stefan Dirsch
Created an attachment (id=263073) --> (https://bugzilla.novell.com/attachment.cgi?id=263073) [details] Xorg.0.log.old - with nv driver
Thanks. This one looks indeed truncated. Maybe KDE4 does some additional DDC probing, which terminates the driver. Would be interesting to see Xorg.0.log when using a KDE3 session. -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c28
--- Comment #28 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c29
--- Comment #29 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c30
--- Comment #30 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c31
--- Comment #31 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c32
--- Comment #32 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c33
--- Comment #33 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c34
--- Comment #34 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c35
--- Comment #35 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c36
--- Comment #36 from Grzegorz Kossakowski
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c37
--- Comment #37 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c38
--- Comment #38 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c39
--- Comment #39 from Grzegorz Kossakowski
Hmm. This error message doesn't look driver specific at all, but I'm not a KDE developer.
There is information related to graphic card displayed at sysinfo:/ page. For example, there is a name of the card and information if 3d acceleration is enabled. I don't know how this information is collected either but I'm sure that this is broken with nv driver and working with nvidia driver. (In reply to comment #38 from Stefan Dirsch)
I'm wondering if this issue couldn't be user specific. Does it also happen with a freshly created user?
Imagine desktop effects were enabled with nvidia driver with previous openSUSE version and now you're trying to run them with the new openSUSE release and nv driver, which does not support 3D at all. Just an example for a driver and user specific scenario.
Tried this long time ago when I faced this problem for a first time. The answer is that this problem is not user specific. Just to make sure that nothing has changed I've checked it with fresh user a moment ago. I've got the same problem with that user. -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c40
--- Comment #40 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c41
--- Comment #41 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User registration@grek.tuffmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c42
--- Comment #42 from Grzegorz Kossakowski
Maybe the best to figure out what's happening during KDE4 start is to run it manually.
1. Start Xserver:
X :1 & sleep 3; DISPLAY=:1 xterm
2. run /usr/bin/startkde in this xterminal
What's happening? Is KDE4 session started?
The observed symptoms are the same and of course KDE4 is not running. I've decided to run it second time in following way: (X :1 & sleep 3; DISPLAY=:1 xterm) &> X.log /usr/bin/startkde &> startkde.log in order to collect some logs. Here is the contents of X.log: X.Org X Server 1.5.2 Release Date: 10 October 2008 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux grek-laptop 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 Build Date: 03 December 2008 09:21:06AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Sun Jan 4 10:56:48 2009 (==) Using config file: "/etc/X11/xorg.conf" error setting MTRR (base = 0xd0000000, size = 0x07f00000, type = 1) Invalid argument (22) The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server Could not init font path element /usr/share/fonts/TTF/, removing from list! Could not init font path element /usr/share/fonts/OTF, removing from list! The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server Could not init font path element /usr/share/fonts/TTF/, removing from list! Could not init font path element /usr/share/fonts/OTF, removing from list! error setting MTRR (base = 0xd0000000, size = 0x07f00000, type = 1) Invalid argument (22)
startkde.log: startkde: Starting up... kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update kdeinit4: preparing to launch /usr/bin/kcminit_startup kdeinit4: preparing to launch /usr/bin/ksmserver startkde: Shutting down... klauncher: Exiting on signal 1 startkde: Running shutdown scripts... startkde: Done. -- 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=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c43
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=463228
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=463228#c44
--- Comment #44 from Stefan Dirsch
Ok. I'll see on monday what sysinfo:/ shows me with my setup in KDE3/KDE4.
Graphics Card ------------- Vendor: Mesa Project Model: Software Rasterizer Driver: 2.1 Mesa 7.2 No problem to display this page. -- 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.
participants (1)
-
bugzilla_noreply@novell.com