Yes, I spotted that too. I note it also happened under 32-bit feisty when everything was working fine.
EDIT: I was wrong, it didn't happen previously, I was reading the wrong log.
- log from when I was running 32-bit feisty today.
Both panels are connected via DVI to the one card right now. I only have one card in the machine at the moment to simplify diagnostics.
Just to clarify, the machine produces absolutely NO output on the display at *any* time. This includes the BIOS POST which prior to installing this driver worked fine.
I will try the 100.14.03 beta driver, but I would not be confident that the driver can undo what has been done.