Bug 364555 (kegmeon)

Summary: nvidia: blank black screen on switch to terminals & on turning off monitor (regression since 169.xx)
Product: [openSUSE] openSUSE 10.3 Reporter: Somebody Luxemburg <gruenzone>
Component: X11 3rd Party DriverAssignee: Roland Hui <rohui>
Status: RESOLVED WONTFIX QA Contact: Stefan Dirsch <sndirsch>
Severity: Normal    
Priority: P5 - None CC: rohui
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 10.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: lspci output
hwinfo output
xorg.conf

Description Somebody Luxemburg 2008-02-25 15:47:05 UTC
Created attachment 196952 [details]
lspci output

Hardware Information in attachments.

kernel 2.6.22.17-0.1-default
openSUSE 10.3 (i586)
KDE 3.5.7
Noteboook HP Pavillion dv6313eu
nvidia Driver 169.09

After installing the kernel-update via openSuse repository, this bug (https://bugzilla.novell.com/show_bug.cgi?id=331747) was fixed, but a new one occurred:

Machine starts normally; after entering the Desktop Environment (or more precise the openSuse login screen) no switching to other terminals (with CTRL+ALT+F1-6) possible -> blank black screen instead of command line. 

The same effect occurs if monitor is forced to (by "xset dpms force off") respectively turn automatically off. On mouse or key event the screen turn on again and shows only this blank black. To get back to KDE I have to use CTRL+ALT+F1-6 (to switch to another blank screen^^) and then CTRL+ALT+F7.

On shoutdown, after leaving KDE the same blank black screen appears. Then after a while (after the shutdown process) it turns off.

All in all it seems to be a very strange bug.
Comment 1 Somebody Luxemburg 2008-02-25 15:47:44 UTC
Created attachment 196953 [details]
hwinfo output
Comment 2 Somebody Luxemburg 2008-02-25 15:48:11 UTC
Created attachment 196954 [details]
xorg.conf
Comment 3 Jeff Mahoney 2008-03-28 19:53:34 UTC
Are you able to reproduce this without the binary-only nvidia driver?
Comment 4 Thomas Renninger 2008-03-30 09:52:32 UTC
Stefan has the nvidia driver version changed while 10.3 is out?
This sound graphics driver related?
Comment 5 Stefan Dirsch 2008-03-30 10:08:35 UTC
Yes, it has been updated several times. 169.12 is the current version, so the reporter does no use he latest one.
Comment 6 Somebody Luxemburg 2008-03-30 12:15:54 UTC
I just installed the 169.12 version of the nvidia driver but it doesn't changed anything.
Comment 7 Somebody Luxemburg 2008-03-30 12:18:58 UTC
Oh, sry I forgot: with the nv driver it works. But I really need 3D programms. Is there any alternative too the nvidia driver?
Comment 8 Jeff Mahoney 2008-03-30 13:55:52 UTC
There's the Nouveau driver at http://nouveau.freedesktop.org/wiki/, but I don't have any idea how developed it is.

We can't support the nvidia driver. A lot of time it "just works," but it's impossible for us to debug problems with it. Our support policy is to decline to diagnose bugs with closed-source drivers loaded. In this case, it's doubly so: The problem is display related and goes away without the driver loaded. My apologies, but I'm going to have to close this one as INVALID.
Comment 9 Stefan Dirsch 2008-03-30 15:52:13 UTC
It might be a regression of the NVIDIA driver. For openSUSE 10.3 the driver has been updated 

100.14.19 --> 169.07 --> 169.09 --> 169.12

I suggest to try 169.07 and possibly 100.14.19 to figure this out (use the official NVIDIA installer for these, there are no openSUSE RPMs available). If you figure out it's a regression we can reopen the bugreport and reassign it to NVIDIA.



Comment 10 Somebody Luxemburg 2008-03-30 17:14:15 UTC
WOW! What an Idea, Stefan!

There is a regression:

100.14.19: Works fine
169.xx: Bug described as above

Thank you very much!
Comment 11 Stefan Dirsch 2008-03-30 17:18:58 UTC
reopen.
Comment 12 Stefan Dirsch 2008-05-28 14:32:42 UTC
I finally decided to no longer track proprietary NVIDIA driver bugs
against openSUSE. Therefore I'm closing these now as WONTFIX.

In case you're using our SLES/SLED products and can reproduce this
issue also on thesed products feel free to reopen. These are still
tracked, since customers of these products depend on the proprietary
driver for newer NVIDIA hardware.

Be aware that you need a privilleged account to track anything against
our SLES/SLED products. So if this not an option for you I suggest to
report the problem to the official NVIDIA driver feedback channels
(forum/email; see NVIDIA driver download site) and refer to this
bugreport.