LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-10-2008, 04:18 PM   #1
oxblood
Member
 
Registered: Jan 2004
Location: Atlanta, GA
Distribution: Slackware 12.2
Posts: 82

Rep: Reputation: 15
Resolution Mismatch in Dell S2209W with Radeon 7500 and Xorg


Hi,

I've just purchased a new monitor -- Dell S2209W, after the old one died. I am KVM'ing two systems with this monitor (just like with the old monitor). Dell S2209W works accordingly in Windows XP with the appropriate drivers and designated native resolution of 1920x1080@60Hz. I had assumed the old configuration of Xorg on Linux would also work just like before -- of course with suited configuration change in its config file.

The problem is not that I can't load X, but rather it seems as "radeon" driver loaded by the kernel prevents the monitor to run in its native resolution of 1920x1080 as I have configured it in "xorg.conf" file. Instead, it runs at 1280x1024@60Hz. The following list is my current system:

Code:
Slackware 10
Kernel Linux 2.6.14.3
Xorg 6.8.2
AGP Radeon 7500
Monitor Dell S2209W

I have the following drivers loaded:

Code:
# modprobe -l radeon*
/lib/modules/2.6.14.3/kernel/drivers/video/radeonfb.ko
/lib/modules/2.6.14.3/kernel/drivers/char/drm/radeon.ko
/lib/modules/2.6.14.3/kernel/drivers/char/agp/ati-agp.ko

# lsmod | grep radeon
radeon                105856  1

The preset Horizontal and Vertical range for this particular monitor at 1920x1080 can be found here:

https://support.dell.com/support/edocs/monitors/S2209W/en/ug/about.htm#preset



The spec for ATI Radeon 7500 confirms that it supports such resolution (16:9 ratio):

http://ati.amd.com/products/radeon75...500/specs.html

http://ati.amd.com/products/radeon75...00/faq.html#21



The following is the content of /etc/X11/xorg.conf:

Code:
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath     "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/freefont/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier  "Keyboard1"
    Driver      "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option     "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc101"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"   "xorg"
    Option "XkbModel"   "omnikey101"
    Option "XkbLayout"  "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "IMPS/2"
    Option "Device"      "/dev/mouse"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"        "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"  "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"  "9600"
#    Option "SampleRate"        "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "Dell S2209W"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   30-64

#    HorizSync  30-64         # multisync
#    HorizSync  31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 60-100

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

#Section "Device"
#    Identifier "Standard VGA"
#    VendorName "Unknown"
#    BoardName  "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

#    Driver     "radeon"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam   256

#    Clocks     25.2 28.3

#EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "ATI Radeon 7500"
    Driver      "radeon"
    Option "AGPMode" "4"
    Option "AGPFastWrite" "True"
    Option "EnablePageFlip" "True"
    Option "RenderAccl" "on"
    Option "EnableAGPDMA" "on"
    #VideoRam    65536
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "ATI Radeon 7500"
    Monitor     "Dell S2209W"
    DefaultDepth 24

 #   Subsection "Display"
 #       Depth       8
 #       Modes       "1280x1024" "1024x768" "800x600" "640x480"
 #       ViewPort    0 0
 #   EndSubsection
 #   Subsection "Display"
 #       Depth       16
 #       Modes       "1280x1024" "1024x768" "800x600" "640x480"
 #       ViewPort    0 0
 #   EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1920x1080"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection
Section "Extensions"
   Option "Composite" "Enable"
EndSection

Section "DRI"
   Mode 0666
EndSection


And finally, this the Xorg log file which I placed on pastebin due to its size:

http://pastebin.com/m75f3f3a6



So my issue is that no matter how I configure the monitor to display at 1920x1080, it reverts back to 1280x1024. Any help would be much appreciated.

Sincerely
 
Old 12-10-2008, 04:49 PM   #2
barn63
Member
 
Registered: Jan 2006
Location: Macomb, IL
Distribution: Slackware 13.1
Posts: 150

Rep: Reputation: 17
Set your HorizSync to 30-83 and set the VertRefresh to 50-76 under the monitor section for your xorg.conf.
 
Old 12-10-2008, 05:31 PM   #3
oxblood
Member
 
Registered: Jan 2004
Location: Atlanta, GA
Distribution: Slackware 12.2
Posts: 82

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by barn63 View Post
Set your HorizSync to 30-83 and set the VertRefresh to 50-76 under the monitor section for your xorg.conf.
Doing so would cause the monitor not to even start X or fail and revert back to console mode. It totally craps out and gives out a manufacturer's message that the input timing is wrong and it has to be changed to 1920x1080@60Hz.

If I change back the config to HorizSync 30-64 and VertRefresh of 60-100, I can load X but only at 1280x1024@60Hz. Quite honestly, I don't understand why it reacts to other sort of refreshing ranges. I even tried larger ranges (i.e. HorizSync 30-140 and VertRefersh 50-140) but the monitor just gave up with the same input timing message without allowing me to revert back to the console mode to view the log file -- I had to reboot eventually.


Any idea?
 
Old 12-10-2008, 06:55 PM   #4
barn63
Member
 
Registered: Jan 2006
Location: Macomb, IL
Distribution: Slackware 13.1
Posts: 150

Rep: Reputation: 17
What happens if you set the HorizSync and VertRefresh to the exact specs from that page as defined by 1920x1080 resolution? I believe they list HorizSync at 55.62 and VertRefresh at 49.92.

Also when I ran an ATI card I used the fglrx driver. I never had an issue running it.
 
Old 12-10-2008, 10:08 PM   #5
oxblood
Member
 
Registered: Jan 2004
Location: Atlanta, GA
Distribution: Slackware 12.2
Posts: 82

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by barn63 View Post
What happens if you set the HorizSync and VertRefresh to the exact specs from that page as defined by 1920x1080 resolution? I believe they list HorizSync at 55.62 and VertRefresh at 49.92.


I have been experimenting with various refresh ranges horizontal and vertical and came up with the following results:

"HorizSync range and VertRefresh range and the resulting resolution"

Code:
# 60-86 and 45-100 results in SHUTDOWN
# 70-86 and 60-100 results in SHUTDOWN

# 55-60 and 40-55  X craps out with error message
# 55-60 and 49-50  X craps out with error message
# 60-70 and 49-55  X craps out with error message

# 55-60 and 70-80  sets the resolution to 1024x786@75Hz

# 40-60 and 50-86  sets the resolution to 1280x960@60Hz
# 55-60 and 50-60  sets the resolution to 1280x960@60Hz
# 55-60 and 60-70  sets the resolution to 1280x960@60Hz

# 40-65 and 30-86  sets the resolution to 1680x1050@60Hz
# 40-65 and 30-140 sets the resolution to 1680x1050@60Hz
# 40-70 and 50-86  sets the resolution to 1680x1050@60Hz
# 60-70 and 50-85  sets the resolution to 1680x1050@60Hz
# 60-70 and 55-95  sets the resolution to 1680x1050@60Hz
# 60-70 and 60-100 sets the resolution to 1680x1050@60Hz

# 40-76 and 30-100 sets the resolution to 1600x1200@60Hz
# 40-76 and 40-100 sets the resolution to 1600x1200@60Hz
# 40-76 and 50-86  sets the resolution to 1600x1200@60Hz
# 40-76 and 50-100 sets the resolution to 1600x1200@60Hz
# 50-76 and 45-100 sets the resolution to 1600x1200@60Hz
# 50-76 and 40-100 sets the resolution to 1600x1200@60Hz

And by "SHUTDOWN" the monitor simply displays a warning message that the input timing should be adjusted and it won't dump back to the console mode or anything. It simply sits there and I have to reboot mechanically. "X craps out with error message" pretty much dumps me back to the console screen with error message that it could not load X. Every other setting, I can get to X but with the designated resolution mentioned above. I haven't been able to load X with the optimal resolution of 1920x1080@60Hz.


Quote:
Also when I ran an ATI card I used the fglrx driver. I never had an issue running it.
You mentioned fglrx driver by ATI (AMD). I don't think those drivers support rv200 (Radeon 7500) chip, do they? What ATI card do you have, if I may ask?


Sincerely,
 
Old 12-10-2008, 10:37 PM   #6
barn63
Member
 
Registered: Jan 2006
Location: Macomb, IL
Distribution: Slackware 13.1
Posts: 150

Rep: Reputation: 17
When it goes to the manufacture warning have you tried hitting Ctrl+Alt+F1 to go back to the first terminal. You might be able to kill startx and go back to the terminal without having to hard reset.

I had an ATI Radeon X700 pro. I have been looking and can't confirm if the fglrx driver will support your card. I also looked to see the supported resolutions for the radeon driver but can't seem to find much. I will keep looking though.
 
Old 12-10-2008, 10:55 PM   #7
oxblood
Member
 
Registered: Jan 2004
Location: Atlanta, GA
Distribution: Slackware 12.2
Posts: 82

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by barn63 View Post
I had an ATI Radeon X700 pro. I have been looking and can't confirm if the fglrx driver will support your card. I also looked to see the supported resolutions for the radeon driver but can't seem to find much. I will keep looking though.

Your help is much appreciated. It seems like your card is well supported with ATI Linux driver(s) and unfortunately, my card is a legacy one which didn't have a manufacturer's support, not back when I purchased it, not now. Which is a main reason I believe I ended up using Xorg's dri/radeon drivers for 3D acceleration and what not -- I don't even remember when that was, perhaps more than 4 years ago.

Here's a few pages I came across with regard to Xorg radeon/ati drivers:

http://www.x.org/wiki/radeon

http://dri.freedesktop.org/wiki/ATIRadeon


The latest ati drivers (including `radeon') but of course, I need a latest Xorg server (1.5.x or 1.4.2+) or Xorg collective R7.4 in its entirety:

http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/

I actually tried to compile this one but it requires a number of xorg server macros that I don't have and frankly, do not know where to get. Although I doubt even if I manage to compile the drivers, they would work -- either fizzle out with the old Xorg R6.8.2 or have any effect on resolving the resolution issue.


As I re-iterated before, both the video card and the monitor support this native resolution of 1920x1080 according to the specs.:

http://ati.amd.com/products/radeon75...00/faq.html#21
http://ati.amd.com/products/radeon75...500/specs.html
https://support.dell.com/support/edo...out.htm#preset



Sincerely,
 
  


Reply

Tags
monitor, resolution, xorg, xorgconfig


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
xorg and old radeon 7500 Almucantarat Slackware 4 09-05-2006 01:54 PM
Can't configure 1280x1024 resolution with Radeon X800 in XOrg in Ubuntu 5.10 habiblove Ubuntu 10 02-23-2006 03:35 PM
Can't change xorg resolution with radeon beaucoup Linux - Software 1 10-23-2004 12:41 PM
Dual head second monitor resolution problem ATI Radeon Mobility 7500 Redhat 9 kragemp3 Linux - Hardware 0 05-06-2004 09:05 PM
best drivers (radeon 7500) watashiwaotaku7 Linux - General 1 08-29-2003 09:02 AM


All times are GMT -5. The time now is 07:01 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration