ubuntu-x-swat team mailing list archive

[Mark Shuttleworth <mark@xxxxxxxxxxxxx>]

On 26/10/09 12:55, Steve Langasek wrote:
> Is it possible for you to confirm whether plugging the monitor into the
> other card does cause the crash with white?
>    

Interestingly, it did not cause a crash. So, white worked in the case 
where the monitor was connected to the card it picked, and it did not 
crash when the monitor was connected to a different card.

More interestingly, though, the monitor stayed completely dark when it 
was connected to the other card. The BIOS and boot sequence just didn't 
display at all. It's as if the top card (the one picked by white) is 
used at POST. I don't know if that's just luck, or if it's some 
convention in the BIOS, or how this is generally determined, but trying 
to boot with the monitor connected any other way just shows nothing.

The machine does boot, however, so I captured a Xorg log for that case. 
It shows no crash, but it shows that there were no connected monitors. 
Interestingly, plugging a monitor in after the boot did not bring 
anything up on that monitor.

I don't think this provides enough new insight to decide what the likely 
impact of the patch is on the average dual-card system, or other systems.

Mark

-- 
X server aborts if two primary devices found
https://bugs.launchpad.net/bugs/459512
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.