945 choosing incorrect frequency for dell e207wfp

[Chris Jones]

Binary package hint: xserver-xorg-video-intel

I have an ASRock Conroe 945G uATX motherboard, which has onboard VGA and a
little riser card for the PCI-E x16 slot, with a DVI adapter.
http://www.asrock.com/mb/overview.asp?Model=CONROE945G-DVI

I have a Dell E207-WFP connected to the DVI port, which claims an optimum mode
of 1680x1050@60Hz. There is nothing connected to the VGA port.

I do not appear to be able to coax it into correctly displaying 1680x1050@60Hz,
despite it detecting it as an available mode.

[Chris Jones (cmsj)]

Created an attachment (id=11109)
Xorg log

[Chris Jones (cmsj)]

Created an attachment (id=11110)
lspci -vvnn

[Chris Jones (cmsj)]

Created an attachment (id=11111)
Xorg debugmode log

[Chris Jones (cmsj)]

Binary package hint: xserver-xorg-video-intel

I have an ASRock Conroe 945G uATX motherboard, which has onboard VGA and a
little riser card for the PCI-E x16 slot, with a DVI adapter.
http://www.asrock.com/mb/overview.asp?Model=CONROE945G-DVI

I have a Dell E207-WFP connected to the DVI port, which claims an optimum mode
of 1680x1050@60Hz. There is nothing connected to the VGA port.

I do not appear to be able to coax it into correctly displaying 1680x1050@60Hz,
despite it detecting it as an available mode.

[Chris Jones (cmsj)]

More details and logs are in the related freedesktop.org bug

[Chris Jones (cmsj)]

I should mention that this is in gutsy current.

[Chris Jones (cmsj)]

by way of confirmation it is setting incorrect frequencies - if I start X without a config file and let it pick a broken 1680 mode, then tell it to use 1024x768@60 by way of xrandr, it actually sets up 1024x768@75 according to the monitor

[Eric Anholt (eric-anholt)]

Please update to server and driver from git. There was a bug in each of them that could have explained your issue.

[Chris Jones (cmsj)]

Recent updates have fixed this. It now picks almost exactly the optimal mode.

[Gordon Jin (gordon-jin)]

Feedback time out.
Please reopen if you still see this issue with the latest driver.

[Timo Aaltonen (tjaalton)]

it was reported on launchpad.net that it works now :)

[Chris Jones (cmsj)]

indeed. apologies for not replying with info about a git test, by the time I got even close to figuring that out it was already fixed.