Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 216409 - X server won't pick highest possible refresh rate
X server won't pick highest possible refresh rate
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xorg-x11-server (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Depends On:
  Show dependency treegraph
Reported: 2006-11-20 05:11 EST by Stephan Wiesand
Modified: 2008-08-02 19:40 EDT (History)
0 users

See Also:
Fixed In Version: rhel 5.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-19 11:12:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephan Wiesand 2006-11-20 05:11:56 EST
Description of problem:
When the monitor parameters specified in xorg.conf allow for 1152x864 at 75 or
85 Hz, the server will pick 75.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. specify these in xorg.conf:
Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "NEC"
        ModelName    "NEC FE750+"
        HorizSync    31.0 - 96.0
        VertRefresh  74.0 - 91.0
        DisplaySize  330   240
Section "Screen"
        Identifier  "Screen0"
        Device      "Card0"
        Monitor     "Monitor0"
        DefaultDepth  16
        Subsection "Display"
                Viewport   0 0
                Depth     16
                Modes     "1152x864" "1024x768" "800x600" "640x480"
Actual results:
refresh rate is 75 Hz; 85 is available but not the default

Expected results:
85 Hz used by default

Additional info:
Comment 1 Matěj Cepl 2007-10-22 18:21:26 EDT
Reporter, is this problem reproducable on the released RHEL, please?
Comment 2 Stephan Wiesand 2007-11-17 07:13:12 EST
No. At least in 5.1 it's gone. Thanks for caring.
Comment 3 Matěj Cepl 2007-11-19 11:12:25 EST
Thanks for letting us know.

Note You need to log in before you can comment on or make changes to this bug.