Some more developments about the trouble with Intrepid (yes, I know this bug is about Hardy but I think the problems in Hardy and Intrepid are related, as I'll point out below)
I decided to try Intrepid using the VGA cable instead of DVI, and the display worked, except the resolution was set to 1600x1024, so I set it 1440x900, and everything was fine (so it seems both Hardy and Intrepid initialize at the wrong resolution).
* anyone who's had the same/similar problem, definitely read this paragraph *
Knowing that the resolution was initializing wrong, I switched back to the DVI cable to try alt+F2 to open the run box, then type "xrandr -s 1440x900" (blindly, since the monitor is blank, :) ), hit return, wait a few seconds, and success!
I guess if the monitor is using DVI input and the resolution is anything greater than 1440x900, it just flashes "Input Not Supported"
Some more developments about the trouble with Intrepid (yes, I know this bug is about Hardy but I think the problems in Hardy and Intrepid are related, as I'll point out below)
I decided to try Intrepid using the VGA cable instead of DVI, and the display worked, except the resolution was set to 1600x1024, so I set it 1440x900, and everything was fine (so it seems both Hardy and Intrepid initialize at the wrong resolution).
* anyone who's had the same/similar problem, definitely read this paragraph *
Knowing that the resolution was initializing wrong, I switched back to the DVI cable to try alt+F2 to open the run box, then type "xrandr -s 1440x900" (blindly, since the monitor is blank, :) ), hit return, wait a few seconds, and success!
I guess if the monitor is using DVI input and the resolution is anything greater than 1440x900, it just flashes "Input Not Supported"