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 121821 - Wrong XF86Config Vertical Syncronization for Syncmaster 192N
Wrong XF86Config Vertical Syncronization for Syncmaster 192N
Product: Fedora
Classification: Fedora
Component: hwdata (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-04-28 06:35 EDT by David Niemi
Modified: 2014-03-16 22:44 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-19 17:57:21 EDT
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 David Niemi 2004-04-28 06:35:25 EDT
Description of problem: Wrong vertical syncronization assigned for 
detected Syncmaster 192N lcd monitor, was 56 - 85, should be 56 - 75

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

How reproducible: On re-install of FC1

Steps to Reproduce:
Actual results:

Expected results:

Additional info: monitor also supports 1280x1024 resolution
Comment 1 Jeremy Katz 2004-05-05 19:32:35 EDT
Did you go with the automatically selected monitor or did you select
one by hand?  If the former, could you provide the output of running
Comment 2 David Niemi 2004-05-07 08:52:16 EDT
Videocard DDC probe results
Description:  ATI Technologies Inc. V280
Memory (MB):  128

Monitor DDC probe results
ID: SAM00a6
Name: SyncMaster
Horizontal Sync (kHZ): 30-81
Vertical Sync (HZ)  : 56-85
Width (mm): 380
Height(mm): 310
When I tried installing the FC1 x86_64 it wouldn't find the monitor 
at all.  The above configuration works with Knoppix but not with 
FC1.  FC1 I need to change the settings to V 56-75 and include 
Comment 3 Bill Nottingham 2004-05-19 17:57:21 EDT
This implies the monitor lies about what it supports. Not much we can
do here.

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