While the behavior could certainly be better -- those console messages are certainly bug worthy -- the underlying problem seems to likely lie with DVI.

Indeed, the message could be better. The console errors led me to believe it was a software issue - perhaps a slightly borked Tiger->Leopard upgrade - when it's a hardware issue plain and simple.

Radar Bug #5664438.

bbum said on December 28, 2007:

Speaking rather cluelessly, does it provide a standard via which out-of-band data can be passed?

It must be something like that. It doesn't surprise me if I think about it - the earlier ADC connector sent USB signals over the same wire as the DVI signals, so perhaps we're letting that "one cable" thing toy with our minds. After all, it makes sense that information like this isn't part of the display signal and thus has to be sent separately.

The reason I unplugged the USB cable to begin with was because I'm trying to track down a consistent crashing and "funny drawing" problem I've been having since applying the ATI Radeon X1900 XT Firmware Update.

While the behavior could certainly be better -- those console messages are certainly bug worthy -- the underlying problem seems to likely lie with DVI.

Speaking rather cluelessly, does it provide a standard via which out-of-band data can be passed?