[nvidia-glx-legacy] Feisty Gnome Xorg Resolution

[Gordo]

I installed the Beta of Feisty tonight... Looks awesome. After installation I had 1024x768 resolution using the open source Nvidia driver. I used the restricted driver manager to install the 3D Nvidia driver and rebooted. After rebooting I can only get 800x600 max. I tried to add 1152x864 to the modelines like I did with all previous versions of Ubuntu to get my preferred resolution (1024x768 is still there too) but the highest resolution I can get is 800x600.

I have a GeForce4 440MX 64MB card with has working in 3D mode flawlessly with all previous versions of Ubuntu.

Thanks,
Gord

ProblemType: Bug
Architecture: i386
Date: Fri Mar 30 08:05:37 2007
DistroRelease: Ubuntu 7.04
Uname: Linux neo 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

[Cesare Tirabassi (norsetto)]

I don't have an NVIDIA myself, so I might be totally wrong, but I read that the most recent NVIDIA proprietary drivers do not support very well (if at all) some old cards like the GeForce4 440 MX.
For these, the nvidia-legacy driver should be used.

[Gordo (gordo)]

Cesare,

Ya, I know about all that. The restricted drivers utility did actually
install the legacy driver. I am using the legacy driver in Edgy with my
little card and it works flawlessly. I am able to run the 3D OpenGL
screensavers and UT and Quake 3 all without any problems.

Thanks,
Gord

On 3/30/07, Cesare Tirabassi <email address hidden> wrote:
>
> I don't have an NVIDIA myself, so I might be totally wrong, but I read
> that the most recent NVIDIA proprietary drivers do not support very well (if
> at all) some old cards like the GeForce4 440 MX.
> For these, the nvidia-legacy driver should be used.
>
> --
> Feisty Gnome Xorg Resolution
> https://launchpad.net/bugs/99022
>

[Timo Aaltonen (tjaalton)]

using nvidia-glx-legacy

[Gordo (gordo)]

Update: I just noticed that in the restricted drivers manager under the status column it next to the NVIDIA driver line it always says "Needs computer restart". No matter how many times I restart, this message never goes away. But, interestingly the 3D support appears to be working fine. If I could just get the resolution to go higher than 800x600 I would be happy.

Gord

[Marcel van der Ham (marcel-van-der-ham)]

I also had a problem with nvidia-glx-legacy driver not getting higher than 800x600.
See https://bugs.launchpad.net/bugs/91292 (same issue?)

[Sitsofe Wheeler (sitsofe)]

This could be down to your monitor lying about what it can actually do or incorrect settings in xorg.conf ...

Timo, Gordo, Marcel:
Could you each attach your
/var/log/Xorg.0.log
and
/etc/X11/xorg.conf
files to this bug report?

[Marcel van der Ham (marcel-van-der-ham)]

I have attached my Xorg logging and config files
- Xorg.0.NOK.log -> incorrect resolution of 800x600
- Xorg.0.OK.log -> correct resolution of 1280x1024
- xorg.NOK.conf -> incorrect resolution of 800x600
- xorg.OK.conf -> correct resolution of 1280x1024

I have a Philips 190S monitor connected through VGA. The natural resolution of this monitor is 1280x1024.
My video card is a NGeForce2 MX100 DDR/200 DDR

[Gordo (gordo)]

I will send you mine when I get home from work tonight...

Gordo

On 4/12/07, Sitsofe Wheeler <email address hidden> wrote:
>
> This could be down to your monitor lying about what it can actually do
> or incorrect settings in xorg.conf ...
>
> Timo, Gordo, Marcel:
> Could you each attach your
> /var/log/Xorg.0.log
> and
> /etc/X11/xorg.conf
> files to this bug report?
>
> --
> Feisty Gnome Xorg Resolution
> https://bugs.launchpad.net/bugs/99022
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Gordo (gordo)]

Here are the requested files...

FYI, after manually adding my monitor's HorizSync and VertRefresh settings I was able to use the correct resolution settings. Also after the latest round of updates the Restricted Drivers Manager is showing my Nvidia driver as "In Use"...

Thanks,
Gordo

[Sitsofe Wheeler (sitsofe)]

Gordo:
Could you attach the output of
sudo xresprobe nvidia

However, from what you are saying (with regard to fixing up HorizSync and VertRefresh) it sounds more and more like your monitor is giving back incorrect information. Looking at your logs your monitor claims to have a HorizSync of 30.00-72.00 and a VertRefresh of 50.00-130.00. What is the exact model of your monitor and does its manual (or Windows driver) tell you that it has refresh/sync ranges different to the aforementioned ones?

If so I suspect you will always have to manually correct your xorg file with this monitor unless Ubuntu implements a monitor database...

[Sitsofe Wheeler (sitsofe)]

This looks similar to Bug #91292 .

[Sitsofe Wheeler (sitsofe)]

Setting to needsinfo pending reply from Gordo.

[Gordo (gordo)]

Sitsofe,

I am running the final release of Fiesty, just installed it today. I still
had to manually enter my H & V settings into xorg.conf but other than that
this is the best Linux I have ever tried. Other than that short visit to the
command line I have been able to configured and install all needed software,
etc through the gui tools!!!!

So, when I try to run: sudo xresprobe nvidia

I get command not found... is there a certain package that needs to be
installed?

Thanks,
Gordo

On 4/13/07, Sitsofe Wheeler <email address hidden> wrote:
>
> Gordo:
> Could you attach the output of
> sudo xresprobe nvidia
>
> However, from what you are saying (with regard to fixing up HorizSync
> and VertRefresh) it sounds more and more like your monitor is giving
> back incorrect information. Looking at your logs your monitor claims to
> have a HorizSync of 30.00-72.00 and a VertRefresh of 50.00-130.00. What
> is the exact model of your monitor and does its manual (or Windows
> driver) tell you that it has refresh/sync ranges different to the
> aforementioned ones?
>
> If so I suspect you will always have to manually correct your xorg file
> with this monitor unless Ubuntu implements a monitor database...
>
> --
> Feisty Gnome Xorg Resolution
> https://bugs.launchpad.net/bugs/99022
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Sitsofe Wheeler (sitsofe)]

Gordo:
Thanks for the reply. This looks identical to Bug #91292 so I'm gong to close this and mark it as a duplicate. If it turns out to be different please reopen this bug and unduplicate it.