Bug 174206

Summary: Apple Cinema Display 20" not properly detected (driver nv)
Product: [Fedora] Fedora Reporter: Jurgen Kramer <gtmkramer>
Component: hwdataAssignee: Phil Knirsch <pknirsch>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-01 14:52:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg.0.log none

Description Jurgen Kramer 2005-11-25 21:14:00 UTC
Description of problem:


Version-Release number of selected component (if applicable):
X Window System Version 6.99.99.902 (7.0.0 RC 2)

How reproducible:
Alway

Steps to Reproduce:
1. Hand select Apple Cinema Display 20" from firstboot (not detected
automatically during install)
2. Set display to max res. 1680x1050 24bits
3. 
  
Actual results:
X shows black bars on the right and left instead of proper full screen picture

Expected results:
Proper full screen picture

Additional info:
Videocard GeForce 6600 GT (PCI-E)

From Xorg.0.log:
(--) NV(0): DDC detected a DFP:
(II) NV(0): Manufacturer: APP  Model: 921d  Serial#: 50201046
(II) NV(0): Year: 2004  Week: 46
(II) NV(0): EDID Version: 1.3
(II) NV(0): Digital Display Input
(II) NV(0): Max H-Image Size [cm]: horiz.: 43  vert.: 27
(II) NV(0): Gamma: 2.20
(II) NV(0): DPMS capabilities: Off; RGB/Color Display
(II) NV(0): Default color space is primary color space
(II) NV(0): First detailed timing is preferred mode
(II) NV(0): redX: 0.640 redY: 0.340   greenX: 0.295 greenY: 0.610
(II) NV(0): blueX: 0.145 blueY: 0.070   whiteX: 0.312 whiteY: 0.329
(II) NV(0): Manufacturer's mask: 0
(II) NV(0): Supported Future Video Modes:
(II) NV(0): #0: hsize: 1680  vsize 1050  refresh: 60  vid: 179
(II) NV(0): Supported additional Video Mode:
(II) NV(0): clock: 119.0 MHz   Image Size:  433 x 270 mm
(II) NV(0): h_active: 1680  h_sync: 1728  h_sync_end 1760 h_blank_end 1840
h_border: 0
(II) NV(0): v_active: 1050  v_sync: 1053  v_sync_end 1059 v_blanking: 1080
v_border: 0
(II) NV(0): Monitor name: Cinema Displa
(II) NV(0): Monitor name: y
(II) NV(0): Number of EDID sections to follow: 1
(II) NV(0): Probing for EDID on I2C bus B...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0):   ... none found
(--) NV(0): CRTC 0 is currently programmed for DFP
(II) NV(0): Using DFP on CRTC 0
(--) NV(0): Panel size is 1680 x 1050
(II) NV(0): Panel is TMDS
(--) NV(0): VideoRAM: 131072 kBytes
(==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) NV(0): Monitor0: Using default hsync range of 64.67-67.41 kHz
(II) NV(0): Monitor0: Using default vrefresh range of 59.88-60.00 Hz
(II) NV(0): Clock range:  12.00 to 400.00 MHz

Which results in the following xorg.conf (driver nv):
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Apple Cinema Display 20 LCD"
        HorizSync    30.0 - 75.0
        VertRefresh  60.0 - 60.0

Horizontal refresh is not correct, it should be:

: Frequency information for DFP-1:
HorizSync   : 64.000-65.000 kHz
VertRefresh : 60.000 Hz

Comment 1 Jurgen Kramer 2005-11-25 21:14:00 UTC
Created attachment 121495 [details]
Xorg.0.log

Comment 2 Marius Andreiana 2005-11-25 21:43:26 UTC
*** Bug 174203 has been marked as a duplicate of this bug. ***

Comment 3 Mike A. Harris 2006-01-31 18:36:18 UTC
Monitor detection done during firstboot, is done by executing the ddcprobe
application, which is not part of the X Window System.  If ddcprobe can not
probe the display, or if you manually select the display from a list, the
horiz/vert rates that get used come straight from the MonitorsDb database,
which is part of the "hwdata" package.

Reassigning to "hwdata".


Comment 4 Phil Knirsch 2006-02-01 14:52:59 UTC
Fixed in current MonitorDB, i'm planing on building a new package either
today or tomorrow, so most likely will make it into FC5.

Read ya, Phil