New display "Out of Range"

[HarryTheLesser]

I recently changed displays and booted into failsafe mode and ran sax2 -r. Sax correctly identified my monitor and video card, I saved the configuration and re booted. Got "Out of Range" message.

Have tried various display resolutions all to no avail.

Please HELP!!!

Running Suse 10.1

[oz]

Welcome to the forums!

Check for the correct vertical and horizontal refresh rates in your monitor manual and set them to the correct specifications in your /etc/X11/xorg.conf file, then start X:

su
nano /etc/X11/xorg.conf

[HarryTheLesser]

How do I do that, after I enter nano there is nothing there to edit?

[oz]

Be sure you use an uppercase X in the X11 part as in the example above. Commands, folders, and files are case sensitive under Linux.

[scrarfussi]

have you tried a different display one with a much higher resolution

[HarryTheLesser]

My previous monitor was a Viewsonic 17". I don't remember the model number but I ran it at 1280x1024 with no problems.
The new monitor is a Westinghouse 19" LCM-19W4 which wants to run at 1440x900 with a 60hz refresh rate. The manual doesn't list the refresh rates that it supports but the onscreen status display says H 55.8 Khz and V 59.8 hz when running winblows.
I have tried setting the rates using nano to no avail, get same message. Have tried selecting a generic lcd with sax with same result even with changing settings.
My card is a ATI Radeon 9600.
I have Googled the monitor, card and Linux and only learned people aren't too thrilled with the monitor and it needs a 60hz vertical refresh.
I just learned that ATI has a new Linux driver - 1/28/2008. I'm going to install that and cross my fingers. Because I suck at command line work I'm going to install another monitor (old crt) and try to install it with the Yast GUI.
Thanks for the replies, I let you know what happens!

[devils casper]

Out of Range error pops of coz of unsupported Refresh rates only. Have you tried Generic Refresh rates?

HorizSync 30 - 70
VertRefresh  50 - 100

Try using vesa driver instead of ati or radeon. It will fix GUI but vesa doesn't support 3D. You can install ATI driver later on.

[HarryTheLesser]

I tried the refresh rate change you suggested no change.

Switched to vesa driver - no change. Changed refresh rates in vesa driver - no change.

[oz]

onscreen status display says H 55.8 Khz and V 59.8 hz when running winblows

If it runs at that in Windows, it should run fine at that or something close to that under Linux. The 60 Hz sounds about right for the vertical refresh rate on an LCD display.

Are you sure that your edits are saving properly to the xorg.conf file?

[neognomic]

I recently changed displays and booted into failsafe mode and ran sax2 -r. Sax correctly identified my monitor and video card, I saved the configuration and re booted. Got "Out of Range" message.

Have tried various display resolutions all to no avail.

Please HELP!!!

Running Suse 10.1

eh, the parser probably left something in the file.
do a

su

provide root password.

mv /etc/X11/xorg.conf /etc/X11/xorg.conf-BORKED

then

ls -l /etc/X11/xorg.conf

There should not be any xorg.conf file
Then

touch /etc/X11/xorg.conf

Then run yast, or sax directly, to configure the card and monitor.
I rec' testing the display before quitting the SAX configurator.
( edit: Personally I do not like SAX so do not use it, ever. But if one needs graphical widgets, it's the way. I mention that because you should know that whatever SAX does, SAX does - not me. )


Hopefully since the file is empty, SAX can get it right this time. I would say that most likely yes but you might want to

less /etc/X11/xorg.conf

after it is done and look at what it created just to make sure the H & V sync ranges are within the accepted values.
My 17" PGS Synergy uses

  HorizSync    31.5-67.5 
  VertRefresh  60-75

Those are ranges the X Server can use. X server will choose the best value within the specified range at the resolution you specified during configuration to do the sync. If out of range shows up there is a problem, most likely, with sync at that res. It could be the driver(software) or hardware incompatibility.

BTW, errors for X are in /var/log/Xorg.0.log and in the ~/.xsession-errors files. You can look at them to get clues, or sometimes answers, for resolving problems.
And, the monitor acceptable values for ranges in the xorg.conf file can probably be found by using(as root)

hwinfo --monitor

EDID values reported by monitors are notoriously wrong, usually inflated, so be wise and do not use something that makes no sense whatsoever.