Jay Estabrook wrote: > Have you tried Xorg 7.0.x WITHOUT the radeonfb driver?
Tried that last night, and the bad news is it made only a slight difference. "X -probeonly" (with the radeon driver specified in xorg.conf) permanently blanked the display as before, but there was no accompanying kernel "Oops". Machine was still functional as far as being able to login remotely, but the console was dead (as verified by numlock/capslock LEDs not working). When I tried firing up gdm just for grins, that didn't kill the machine immediately: I could examine the Xorg.0.log file and do a bit of poking around on the system (via remote login) until I touched the console keyboard, at which point the machine locked up hard -- reset switch required. Also tried the extra framebuffer boot parameter to explicitly note the CRT was attached to the secondary (VGA) connector, which likewise made no difference in how the xorg.conf fbdev driver behaved. This still seems to be the most promising approach short of downgrading the X11 packages. I'll be trying a DVI <--> VGA adapter later today to move the CRT to the DVI port. If that works, we can at least move forward with working out the kinks in Xorg 7.0.X. -- ----------------------------------------------------------------------- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] ----------------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]