Bug 26605

Summary: ATI X1250 can't handle HP LP3065 display
Product: xorg Reporter: Jonathan Davies <jpds>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log
none
Xorg conf
none
dmesg log none

Description Jonathan Davies 2010-02-17 02:56:57 UTC 
Created attachment 33356 [details] [review]
Xorg log

An ATI X1250 can't handle HP LP3065 display at 2560x1600 using a dual-link DVI cable on Ubuntu Karmic.

The display remains limited at 1280x800, returning:

(II) RADEON(0): Not using mode "2560x1600R" (mode clock too high)
(II) RADEON(0): Not using mode "2560x1600" (mode clock too high)

when set to 2560x1600 in xorg.conf.
Comment 1 Jonathan Davies 2010-02-17 02:57:20 UTC 
Created attachment 33357 [details] [review]
Xorg conf
Comment 2 Jonathan Davies 2010-02-17 02:57:42 UTC 
Created attachment 33358 [details]
dmesg log
Comment 3 Jonathan Davies 2010-02-17 02:58:11 UTC 
Launchpad bug report:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/495168
Comment 4 Alex Deucher 2010-02-17 09:48:44 UTC 
HDMI-A connectors are limited to single link.
Comment 5 daniel anliker 2010-02-18 04:31:55 UTC 
it is not cennected with HDMI-A it is a dual link dvi cable !

(see description)
Comment 6 Alex Deucher 2010-02-18 07:26:22 UTC 
(In reply to comment #5)
> it is not cennected with HDMI-A it is a dual link dvi cable !
> 
> (see description)
> 

The connector on your PC is HDMI-A though at least according to your log.  If the connector on your PC is not HDMI-A, then let me know.
Comment 7 Alex Deucher 2010-02-18 11:04:26 UTC 
Ok, I talked to Daniel and the system actually has a DVI port rather than and HDMI port.  I've added a proper quirk:
e68d3a3890fc81c51f2006b5548da1e8756ad2fd

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.