GeForce 6600 not supported

[iputz]

This driver simply does not work at all with the GeForce 6600; produces no output when X starts.

To reproduce:

Launch the Gnome Hardware Drivers tool: System > Administration > Hardware Drivers
Activate NVIDIA accelerated graphics driver revision 177
Reboot (system hangs just before GDM greeter, totally unresponsive)
Hard Reboot (GDM greeter launches, can hear the greeter sound, but no output to screen)
Control-Alt-F1 to console, run sudo dpkg-reconfigure xserver-xorg, accept defaults to undo the damage.

Vitals:
Ubuntu 8.10, 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Richard Seguin (sectech)]

Thank you for reporting this issue and trying to improve Ubuntu. As a bug triager I would like to see if anyone else is having the same issue with the GeForce 6600 before it gets marked as confirmed. Also by confirming your own bug you almost had the the triage team miss your report. We try and get as much information together in a bug report as possible before forwarding it to the developers. Please feel free to visit "https://wiki.ubuntu.com/Bugs/HowToTriage".

In regards to your issue I will need the following information to continue.

Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your display and video card? Please also attach the /var/log/Xorg.0.log from this attempt.

Also can you please indicate which version of Ubuntu you are running. This should be a good start so we can help solve your issue.

[Richard Seguin (sectech)]

* This bug has been marked as "incomplete" as a bug-control member has elected to triage it. The status will be changed to confirmed then to triaged once enough information has been gathered to assist the developers in resolving the issue.

[Richard Seguin (sectech)]

I have been searching forums to see if I could find a solution for this issue. I am sure it isn't a hardware problem (with your video card) and rather something that you might have to change in the setup.

Since X uses auto configuration it makes it a little more difficult to debug. Unfortunately it looks like I still need a little more information on this...

Please include the information requested at https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.

The good news is that some people have got it working, so we will keep working on the issue until it works for you. When we find out what fixes this it would be great to get that info to the developers so they can make this video card work "out of the box".

[iputz (naroza)]

Richard,

Here's that info you asked for:

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/319642

If you need anything else, please don't hesitate to post.

[Richard Seguin (sectech)]

There is enough information to confirm the bug as even the forums suggest that there isn't very good support for this card. Unfortunately for this issue with this version of Ubuntu our millage may vary on getting this actually fixed as the newer versions of Ubuntu are no longer dealing with restricted nvidia drivers. The restricted driver set will still be available, but they have come up with new open source drivers which they prefer us to use.

I'm not sure if you are interested in testing our new version Jaunty out, if you are it is fairly decent now I think

[iputz (naroza)]

Richard,

Thanks for your time and hard work on this issue. I'll live with the reduced performance until the official release of Jaunty, when (hopefully) the open source drivers are installed automagically.

Thanks again

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

[Diaa Sami (diaa.sami)]

I have a 6600 GT card and I'm using intrepid with no problems, I used 180 at first but I downgraded to 177 later because I experienced a bug with glyph rendering that happens with pre-Geforce 8 cards.

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[auxbuss (launchpad-auxbuss)]

Hi, I'm using a GeForce 6600 on Jaunty with the 180.44 drivers. I use KDE and Gnome. Here are the issues:

- Complex GL screensavers do not work, lightweight ones draw very, very slowly.
- Ctrl+Alt+F1, say, results in a strange fade effect on screen and then settles to black. The console never appears. I am able to switch back with Ctrl+Alt+F7.

I have reduced the composite effect, but not switched them off. For example, the cube and zooming. This improved screensaver performance, made it operational, but it still ~3fps.

[auxbuss (launchpad-auxbuss)]

Also, see:

  https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/210458

[auxbuss (launchpad-auxbuss)]

Anything more I can do to get attention here?

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[auxbuss (launchpad-auxbuss)]

If I understood the notes I would have tested. The notes make no sense to me at all. Judging by the lack of feedback, I guess that I'm not alone!

[Sameer Aslam (samalpha)]

jst run the update Manger...I had the same problem,some how couldn't download the right Package deb.My problem though is gone after 400Mb of complete system updates.

[llbbl (llbbl)]

This happened to me recently when I installed some updates via synaptic. I rebooted and it went to low graphics mode because X decided to overwrite (i assume) my conf file that WAS working just fine.

I fixed this problem by manually editing xorg.conf to the following values. I was able to boot into gnome but then I exited to the prompt via alt+cntrl+f3.

Section "Device"
Identifier "Nvidia Geforce 6600"
Driver "nvidia"
EndSection

[Bryce Harrington (bryce)]

The last few comments sound like perhaps a conflict between nvidia installed from the nvidia website, and the versions provided by Ubuntu. Since there's been no further information provided that can help debug it, I'm re-closing this bug.