[Hardy][Nvidia][Dual-Screen] Fresh install, nvidia-new driver shown as unused, wrong resolution

Bug #223659 reported by Gabriel M.
0
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: xorg

After a fresh install of Hardy Heron, I have the following problems:

- On the login screen and after first login, resolution is 1600x1200, which is not supported by my secondary monitor, and makes my eyes cry on the main monitor. The refresh rate is 66 Hz, which causes a lot of flicker: I always used a resolution of 1024x768@85Hz with this monitor, be it under Windows or Gutsy.

- A quick look at the restricted drivers dialogue: it shows an entry for the nvidia-new driver, but marks it as disabled (screenshot included, sorry, it's in french).

- When I open the screen resolution tool (screenshot included), only one screen is detected.

I found vaguely similar bugs but not this exact one, at least not this particular combination.

Useful info:

Ubuntu version: Hardy Heron 8.04
xorg version: 1:7.3+10ubuntu10

$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation G70 [GeForce 7800 GS] [10de:00f5] (rev a2)

(Resolution after first login:)

$ xrandr
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
   1600x1200 66.0*
   1280x1024 76.0
   1024x768 85.0
   800x600 85.0
   640x480 86.0

(After I changed the resolution to stop my eyes from crying:)

$ xrandr
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1600 x 1200
default connected 1024x768+0+0 0mm x 0mm
   1600x1200 66.0
   1280x1024 76.0
   1024x768 85.0*
   800x600 85.0
   640x480 86.0

I'm attaching the longer logs/outputs as separate files.

Revision history for this message
Gabriel M. (gabrielm) wrote :
Revision history for this message
Gabriel M. (gabrielm) wrote :
Revision history for this message
Gabriel M. (gabrielm) wrote :
Revision history for this message
Gabriel M. (gabrielm) wrote :
Revision history for this message
Gabriel M. (gabrielm) wrote :
Revision history for this message
Gabriel M. (gabrielm) wrote :
Revision history for this message
Gabriel M. (gabrielm) wrote :

A little log of my attempts to fix my setup, in case it helps solve the bug(s) I just reported:

1. After noticing all that I'm describing above, I tried to enable graphical effects to see what would happen, but it fails telling me that visual effects could not be activated.

2. Then for the second time, I opened the restricted drivers dialog, the nvidia driver was actually listed by its full name (as on the second screenshot I'm including), unlike the first time where it was listed as "nvidia_new", but this time the checkbox next to it was unchecked (unlike this second screenshot). Checking the checkbox actually brought up a prompt asking me if I wanted to install the driver, and when I answered yes it proceeded to install the nvidia-glx-new driver, which apparently wasn't installed yet.

3. Opening the restricted drivers a third time shows exactly what you see on this second screenshot: the driver is checked again, but still marked as disabled.

4. I tried enabling visual effects again, but with the same failure as above.

5. As noted nvidia-glx-new doesn't work properly (maybe that's another bug report in itself?), and I double-checked it installed successfully at (2.) above. However, if I replace it with nvidia-glx it works as in Gutsy: I'm able to set up my system, along with dual-screen (Twinview), with the help of nvidia-xconfig and nvidia-settings.

Revision history for this message
Gabriel M. (gabrielm) wrote :

Okay, another update: you can ignore (3.), (4.) and (5.) in the previous comment: if after (2.) I reboot (as prompted, I had ignored the prompt :P), the driver works, is shown as enabled, and I can enable visual effects (compiz).
I still can't change the login screen resolution in an obvious, GUI way though: it's still stuck at 1600x1200@66Hz.

On top of that, after the reboot, the resolution choices I get are now... weird. The refresh rates for 1024x768 are now restricted between 65 Hz and 69 Hz. I'll just post the new xrandr output so you can see for yourself:

$ xrandr
Screen 0: minimum 320 x 175, current 1024 x 768, maximum 1600 x 1200
default connected 1024x768+0+0 0mm x 0mm
   1600x1200 50.0 51.0
   1600x1024 52.0
   1440x900 53.0
   1400x1050 54.0 55.0 56.0
   1280x1024 57.0 58.0
   1280x960 59.0
   1280x800 60.0
   1280x768 61.0
   1152x864 62.0 63.0
   1152x768 64.0
   1024x768 65.0* 66.0 67.0 68.0 69.0
   960x600 70.0
   960x529 71.0
   896x672 72.0
   840x525 73.0
   832x624 74.0
   800x600 75.0 76.0 77.0 78.0 79.0 80.0 81.0 82.0
   800x512 83.0
   720x450 84.0
   720x400 85.0
   640x512 86.0 87.0
   640x480 88.0 89.0 90.0 91.0 92.0
   640x400 93.0 94.0
   640x384 95.0
   640x350 96.0
   576x432 97.0 98.0
   576x384 99.0
   512x384 100.0 101.0 102.0 103.0 104.0
   416x312 105.0
   400x300 106.0 107.0 108.0 109.0 110.0
   360x200 111.0
   320x240 112.0 113.0 114.0 115.0
   320x200 116.0
   320x175 117.0

I'm also attaching the new Xorg.0.log for comparison.

Revision history for this message
Gabriel M. (gabrielm) wrote :

In the comment above, where I wrote "1600x1200@66Hz" it should just say 1600x1200, because I have no mean of checking the refresh rate. The resolution, I know it just by the looks of the screen, and because it hasn't changed since the first login screen.

I believe that's enough details for a bug ;) . Last thing I wanted to add: please do not suggest workarounds or "alternate" tools. I'm trying to help improve default Ubuntu, and I'm perfectly capable of finding workarounds on my own (I'll configure xorg.conf by hand if needed).

Bryce Harrington (bryce)
Changed in xorg:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Gabriel M. (gabrielm) wrote :

I understood the reason for the weird refresh rate: nvidia-settings uses virtual refresh rates which it replaces by its own parameters. It's all explained in the manual for the linux proprietary nvidia driver. But, understanding that doesn't resolve the problem this bug describes.

Bryce Harrington (bryce)
tags: added: hardy
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in linux-restricted-modules-2.6.24 (Ubuntu):
status: Triaged → New
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in linux-restricted-modules-2.6.24 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.