Active Displayport Adapter Display issues

[hunuok]

Hey there,

I have been having an issue with the 10.4 pre and 10.4a pre drivers.

Upon installation, I started getting issues on the center (displayport adapter) display in 3 stages:

1. grey horizontal "interference" lines
2. intermittent display turning on/off
3. complete shutdown of center display

These drivers are the first to give "decent" frames using quadfire+eyefinity.

I've NEVER had these display issues with ANY of the previous drivers. Rolling back to 10.3 WHQL gave no problems again.

Unplugging the displayport adapter and replugging gave a temporary fix, but hardly an acceptable solution.

My active displayport adapter is certified by AMD-Accell Ultra AV DP to DVI-D Dual Link Adapter P/N B087B-002B.

I've read updating the card BIOS, updating the firmware on the adapter or RMAing the adapter are options.

My video cards are not overclocked and I installed catalyst software with default settings.

Frankly, I'm hesitant to flash the BIOS and RMAing the adapter isn't much of an option because I ordered from the US to Seoul. The shipping cost more than the adapter and they don't seem to sell them here.

Any suggestions or advice would be most welcome.

Cheers.

[caveman-jim]

Are you overclocking the HD 5970's?

Are they running 400e/1200m clocks in Eyefinity mode? Try using the overvolt tool to bump up the voltages and see if that makes a difference.

10.4 preview drivers are better for Quadfire HD 5970's but worse for Eyefinity. :\ 10.3b + App profile work best for Eyefinity for me on HD 5970, but 10.4 delivers performance scaling for CrossFireX.

[hunuok]

Hey there caveman,

I am running the cards @ stock speeds.

As far as I can tell, the clocks are running @ 400/1000.

I tried ATI overvolt and the display seems stable. I did have to disconnect the displayport once, but it does seem stable thus far.

BTW, is there any way AMD can merge the 10.3b and 10.4 drivers?lol

I find it increasingly annoying to use "adhoc" methods/hacks to try and get things "working" in drivers that previously worked before. I understand they're "beta" drivers, but "Why fix it if it ain't broke?"

Thanks again caveman for the heads up.

[caveman-jim]

Yeah, I understand. Hopefully it'll come together in 10.5