Created attachment 18447 [details]
The Xorg configuration
I'm using Wintec Dual-DVI ADD2 card in DragonFly BSD system. Second output isn't activated any more with 2.4.x driver (I only briefly tested 2.4.0 to make sure that it's not 2.4.0 -> 2.4.1 regression). Switching back to 2.3.2 fixes the problem.
Created attachment 18448 [details]
Xorg log with driver 2.3.2
Xorg log with driver 2.3.2 with ModeDebug option on.
Created attachment 18449 [details]
Xorg log with driver 2.4.1
Xorg log with driver 2.4.1 with ModeDebug option on.
yeah, in 2.4 we'll first check if SDVO B/C port has been detected, otherwise driver won't try to enable it.
Do you try to boot with both DVI output connected on ADD2 card? Or you may hack in I830SetupOutputs() to force it to probe SDVOC.
> Do you try to boot with both DVI output connected on ADD2 card?
Both monitors are connected and switched on all the time.
> Or you may hack in I830SetupOutputs() to force it to probe SDVOC.
I don't need 2.4.x series so desperately :).
I'm also hitting this bug, under Gentoo Linux, and worked around it the same way (i.e. reverting to 2.3.2). This is with a G965 chipset and, again, a Wintec dual-DVI ADD2 card, with two monitors connected to it. The problem occurs with 2.4.1 and 2.4.2. I note that I've always gotten messages like:
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOC Slave 0x72.
(EE) intel(0): First SDVO output reported failure to sync
from the driver, even when everything works properly. (With 2.4, the above message about SDVOC is absent.)
I keep both monitors plugged in and turned on; but the second is quiescent (soft power-off) until X is started.
This seems dup with #16631. This should make it easier as we can reproduce it locally.
*** This bug has been marked as a duplicate of bug 16631 ***