[Bug 543021] Re: KMS broken with Radeon HD 4670 (RV730XT) and Samsung 305T
Jason Gerard DeRose
jderose at jasonderose.org
Sat Mar 20 23:23:51 UTC 2010
KMS works fine with my other monitor, a Samsung 245BW (1920x1200). So
this is an issue that for me only occurs with my Samsung 305T. I
attached my Xorg.0.log, and here's the output of `xrandr --verbose` when
using my 305T monitor (note I had to boot with "nomodeset"):
Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 2560 x 2560
DVI-1 connected 2560x1600+0+0 (0x53) normal (normal left inverted right x axis y axis) 646mm x 406mm
Identifier: 0x51
Timestamp: 20754
Subpixel: horizontal rgb
Clones:
CRTC: 0
CRTCs: 0 1
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
EDID:
00ffffffffffff004c2d360230335548
0e1301038040287828fe87a3574a9c25
13505400000001010101010101010101
010101010101bc1b00a0502017303020
360086962100001ab06800a0a0402e60
3020360086962100001a000000fc0053
796e634d61737465720a2020000000ff
00485655533430303032380a2020003d
dvi_monitor_type: auto
scaler: full
coherent_mode: 1 (0x00000001) range: (0,1)
load_detection: 1 (0x00000001) range: (0,1)
2560x1600 (0x53) 268.0MHz +HSync -VSync *current
h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 98.5KHz
v: height 1600 start 1603 end 1609 total 1646 clock 59.9Hz
1280x800 (0x54) 71.0MHz +HSync -VSync
h: width 1280 start 1328 end 1360 total 1440 skew 0 clock 49.3KHz
v: height 800 start 803 end 809 total 823 clock 59.9Hz
DVI-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x52
Timestamp: 20754
Subpixel: no subpixels
Clones:
CRTCs: 0 1
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
dvi_monitor_type: auto
scaler: full
coherent_mode: 1 (0x00000001) range: (0,1)
load_detection: 1 (0x00000001) range: (0,1)
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/41460447/Xorg.0.log
--
KMS broken with Radeon HD 4670 (RV730XT) and Samsung 305T
https://bugs.launchpad.net/bugs/543021
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.
More information about the kernel-bugs
mailing list