If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I'm not sure that 1.2.4 completely supports the 4670 though, will check... EDIT - yeah, should be OK. I also checked the H and V frequencies and confirmed that they were in range as well. Might be something related to "TMDS Coherent Mode", I think radeonhd defaults to incoherent; if so then trying coherent would be a good next step (TMDS coherent mode refers to the detailed timing relationship between clock edges and data transitions, nothing to do with the developers state of mind ).

The "radeon" driver you used (6.8.0) is much too old to support 4670; we're at 6.12.2 today.

Comment

You might also want to try xf86-video-ati from git. I just added support for fractional feedback dividers which should allows us to hit much closer to the target dot clock since 156.8 MHz can not be hit exactly with most common reference clocks.

Comment

I tried adding an Option "coherent" line, but it seems to work with or without it.

I had to hit the "source" button on the monitor to get it to pick up. Maybe because I turned on the monitor before the computer? I guess I didn't try hard enough the first time; I changed both the monitor and card at the same time.

Thanks for your efforts.

Comment

Most monitors let you cycle through inputs, and one of the options in the cycle is "auto" (which looks for an active input). If the monitor wasn't set to DVI or "auto" then I don't think power-up sequence would make a difference.