| 2007-03-11 01:48:09 |
Paul McGarry |
bug |
|
|
added bug |
| 2007-03-11 01:52:40 |
Paul McGarry |
bug |
|
|
added attachment 'Xorg.20.log' (Nvidia Log file from Dapper when it worked) |
| 2007-03-11 01:58:34 |
Paul McGarry |
bug |
|
|
added attachment 'Xorg.0.log.nvidia' (NVidia Log file from Feisty when it failed) |
| 2007-03-11 01:59:25 |
Paul McGarry |
bug |
|
|
added attachment 'Xorg.0.log.nv' (nv from Feisty when it worked) |
| 2007-03-11 02:01:48 |
Paul McGarry |
description |
Binary package hint: nvidia-glx-legacy
I have a PC with a Nvidia TNT2 card in it.
It was running Dapper and I upgraded it to Edgy without any problems (using update-manager).
I then upgraded (again using update-manager) to Feisty and after the reboot my X came back at a low resolution rather than the 1600x1200 I usually have.
Switching to the nv driver everything worked again.
Looking at the Xorg log files it seems that when using the Feisty binary Nvidia driver it wasn't picking up the Horizontal and Vertical refresh rates from my monitor and was using very low defaults.
I got it to work by taking the refresh rates as discovered by the nv driver and manually defining them in the xorg.conf file. This got things working properly, but presumably the loss of the "automatic" functionality that had it working out of the box that was present in Dapper and Edgy is a regression. |
Binary package hint: nvidia-glx-legacy
I have a PC with a Nvidia TNT2 card in it.
It was running Dapper and I upgraded it to Edgy without any problems (using update-manager).
I then upgraded (again using update-manager) to Feisty and after the reboot my X came back at a low resolution rather than the 1600x1200 I usually have.
Switching to the nv driver everything worked again.
Looking at the Xorg log files it seems that when using the Feisty binary Nvidia driver it wasn't picking up the Horizontal and Vertical refresh rates from my monitor and was using very low defaults.
I got it to work by taking the refresh rates as discovered by the nv driver and manually defining them in the xorg.conf file in the monitor section, ie:
HorizSync 30-95
VertRefresh 50-160
This got things working properly, but presumably the loss of whatever functionality that had it working out of the box in Dapper and Edgy is a regression. |
|
| 2007-04-04 17:59:57 |
Marcel van der Ham |
bug |
|
|
added attachment 'xorg.conf' (xorg.conf) |
| 2007-04-15 12:20:53 |
Sitsofe Wheeler |
title |
Resolutions lost on upgrade from Edgy to Feisty |
[nvidia-glx-legacy] Resolutions lost on upgrade from Edgy to Feisty |
|
| 2007-04-22 16:41:47 |
Sitsofe Wheeler |
linux-restricted-modules-2.6.20: status |
Unconfirmed |
Confirmed |
|
| 2007-04-22 16:41:47 |
Sitsofe Wheeler |
linux-restricted-modules-2.6.20: statusexplanation |
|
I've hit this with a GeForce 1 on a clean Feisty install. I too needed to add HorizSync/VertRefresh lines in order to get the desired resolutions. Confirming. |
|
| 2007-04-24 20:00:09 |
Sitsofe Wheeler |
title |
[nvidia-glx-legacy] Resolutions lost on upgrade from Edgy to Feisty |
[nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new] |
|
| 2007-05-01 00:22:06 |
Tim Hollen |
bug |
|
|
added attachment 'xorg.conf' (xorg.conf) |
| 2007-06-29 23:25:49 |
Jonathan Lozinski |
bug |
|
|
added attachment 'edid-loz.bin' (Modified EDID.bin dump to correct EDID size data.) |
| 2008-05-21 03:54:14 |
spekorea |
bug |
|
|
added attachment 'unnamed' (unnamed) |
| 2008-06-14 18:43:52 |
TEN |
bug |
|
|
added attachment 'xorg.conf' (xorg.conf) |
| 2008-10-11 02:57:39 |
Bryce Harrington |
linux-restricted-modules-2.6.20: status |
Confirmed |
Won't Fix |
|
| 2009-03-02 19:47:34 |
Mesbah Uddin |
bug |
|
|
added attachment 'xorg.conf.1' (xorg.conf.1) |
