Bug 136811

Summary:	Lockup when attempting to open hardware graphics menu in YAST2 - black screen
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Ashley Cook <ashleyc>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ashley Cook 2005-12-03 04:45:50 UTC

I have AMD x64 with 2 Geforce 6600GT SLI cards setup with SLI. Gigabyte K8N Ultra-SLI motherboard. 1024 Mb Ram.

Suse10 installed with 1280x1024 resolution, which is distorted on my screen. When I attempt to open, in YAST2, the Hardware/Graphics settings to change resolution, the screen goes black with a non-blinking cursor in the upper left corner of the screen. Nothing happens, and I have to cold boot my machine.

When attempting to change screen resolution form the right-click menu on the desktop, there are no other choices for screen resolution, only 1280x1024, which is distorted on my screen.

The graphics is very slow - web pages scroll VERY slowly.

I have the retail (purchased) boxed version of Suse10. I have installed all of the updates, including the nVidia update, with Susewatcher.

With huge regret, I've had to go back to WinXP, until I can get this fixed - I'm a Linux newbie, and have not been able to find a solution.

Comment 1 Michael Gross 2005-12-05 17:05:51 UTC

Are you sure that you're using the nvidia (accelerated) from NVidia itself (downloading the package does not automatically use the driver by default)? You can easily check this by typing `lsmod | grep nvidia' which should list you at least one line. If not, configure X.Org to use that module instead of nv. You can do this by editing /etc/X11/xorg.conf and changing the value in the section "Device" from "nv" to "nvidia" -- no more to it but to restart X then.

Some problems with the nv-driver (the open and unaccelerated module) can occur with 6*00-series. This was also written in the release notes (you can access them by executing susehelp, choosing ``release notes''). There are some options listed there that might solve your problem. The first thing you should try in that case, though, is to use the accelerated driver from NVidia.

If you're already using the closed source modules from NVidia, there is nothing that we can do, because we don't have any license that would allow us to. In that case you must wait for NVidia to solve this problem with their newer cards. A bug report directly to them might help then. It is a known and nasty problem that products are getting released with poorly tested and buggy drivers, that's why you should wait some time before purchasing a brand new product in this sector ;)

Please describe exactly what you have tried in your next comment. Thanks.

Comment 2 Michael Gross 2005-12-06 15:56:56 UTC

Reducing severity due to the nature of this problem (see last comment).

Comment 3 Michael Gross 2005-12-12 15:25:55 UTC

Please reopen this bug if the information asked for can be provided. I'll close it for now as a reminder.

Comment 4 Stephan Kulow 2008-06-25 09:34:17 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 5 Stephan Kulow 2008-06-25 09:36:16 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 6 Stephan Kulow 2008-06-25 09:41:41 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 7 Stephan Kulow 2008-06-25 09:53:08 UTC

Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(