xrandr -s 800x600 Black Screen (Out of Range)

[Sven Rojek]

I got out of range messages in several games (BOS, Nimuh) trying to start them in fullscreen mode.
Then i found out that the 800x600 resolution can't be displayed because of an out of
range error.

Settings:
OS: Ubuntu 8.04
GfxCard: GeForce FX 5900XT (Nvidia Chip)
GfxDriver: Newest Nvidia Driver
Monitor: LG Flatron L1716S (H-Freq: 30-83KHz, V-Freq: 56-75Hz)
normal used Resolution: 1280x1024

I tried to get help in the nimuh Forum, where i included the xrandr outputs
and they suggested that i should start an bug report
http://www.nimuh.com/phpBB3/viewtopic.php?f=6&t=25

ottk3

[Sven Rojek (ottk3)]

some more information:

- if i change the resolution via the gnome gui to 800x600 it works, and all games run perfectly.
- still if i use "xrandr -s 800x600" it can't be displayed
- if i use "xrandr -s 800x600 --rate 75" it works perfectly

Seems to me that xrandr tries to run the resolution in a wrong frequency range? How can I check that?

[Bryce Harrington (bryce)]

Hi ottk3,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

[Roman Odaisky (to-roma-from-lp)]

Greetings,

This is also an issue for me with Kubuntu 8.04.

When an application requests an 800x600 mode, the monitor only displays ‘Out of range’, xrandr -s 800x600 causes the same.

After setting the Nvidia parameter ‘DynamicTwinView’ to false, here’s what xrandr -q shows:
Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
   1280x1024 60.0* 75.0
   1024x768 75.0 70.0 60.0
   1152x864 75.0
   800x600 130.0 120.0 75.0 72.0 60.0 56.0
   640x480 120.0 75.0 73.0 60.0
   1280x960 60.0
and so on.

The figure of 130.0 is suspicious for me. Does X try to set the refresh rate to 130 Hz for the 800x600 mode? I have set the HorizSync and VertRefresh parameters, but they don’t seem to be taken into account.

Here’s what xvidtune shows while in the strange mode:
~ :) xrandr -s 800x600; xvidtune -show; xrandr -s 0
"800x600" 87.75 800 832 928 1080 600 300 301 312 +hsync +vsync doublescan

(I understand not a single figure apart of 800x600 :-)

My hardware is Nvidia 6600GT, LG L1730B monitor. Xorg.0.log shows nothing interesting:
II) NVIDIA(0): Setting mode "800x600"
(II) NVIDIA(0): Setting mode "1280x1024"
(II) NVIDIA(0): Setting mode "800x600_60"
(II) NVIDIA(0): Setting mode "1280x1024"
(II) NVIDIA(0): Setting mode "800x600"
(II) NVIDIA(0): Setting mode "1280x1024"

[Roman Odaisky (to-roma-from-lp)]

Also, this doesn’t look like a bug of xrandr. I got the error first when trying to play Tuxracer. It seems that whenever an 800x600 mode (640x480 works fine) is requested without specifying the refresh rate, X makes the wrong choice.

[Bryce Harrington (bryce)]

More likely is a bug in -nvidia. Also, we still need you to attach your Xorg.0.log and output of lspci -vvnn. Please also re-test against Jaunty.

[Bryce Harrington (bryce)]

Hi ottk3,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[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

[Bryce Harrington (bryce)]

xrandr is the wrong package for this

[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

[Bryce Harrington (bryce)]

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.