FB Radeon and fglrx used together is a known problem its best not to use the radeon FB driver.
On Tue, 2005-01-18 at 17:06 +0930, Iain Buchanan wrote: > I've been using the ati-drivers (pre 8.x) with FB_VESA_TNG for a while > now, and I get a nice 1280x1024 text console on my 1680x1050 laptop lcd. > I also just tried the new ati-drivers (8.8.25.1) which work quite well, > and the text console works as per normal. > > Now, I have the BIOS set to "not enlarge" non-native resolutions, > because I don't like the blurring effect on the LCD. So to get rid of > the black bars on each edge of my text console, and get the full > 1680x1050, I tried enabling FB_RADEON and FB_RADEON_I2C into the kernel. > > This boots up fine, the radeon fb driver detects the native 1680x1050, > and then the vesafb-tng driver seems to do the rest. X starts up > nicely, with the fglrx module, but when I switch back to the consol > (ctrl-alt-f1) the display get corrupted (various short white lines on a > black background) and the laptop becomes unresponsive, even to pings. > The only thing I can do is reboot. > > This _doesn't_ happen when I _don't_ use fglrx, but of course then I > don't get the nice 3D performance. > > Can anyone suggest any hints? I've tried various vesafb options from > grub, and so on, but to no avail... > > MTIA, -- Douglas James Dunn cell: (724) 316-8266 Secretary Phi Mu Delta Mu Theta chapter Indiana University of Pennsylvania () The ASCII Ribbon Campaign - against HTML Email, /\ vCards, and proprietary formats. . .vir. d$b .d$$$$$$b. .cd$$b. .d$$b. d$$$$$$$$$$$b .d$$b. .d$$b. $$$$( )$$$b d$$$()$$$. d$$$$$$$b Q$$$$$$$P$$$P.$$$$$$$b. .$$$$$$$b. Q$$$$$$$$$$B$$$$$$$$P" d$$$PQ$$$$b. $$$$. .$$$P' `$$$ .$$$P' `$$$ "$$$$$$$P Q$$$$$$$b d$$$P Q$$$$b $$$$b $$$$b..d$$$ $$$$b..d$$$ d$$$$$$P" "$$$$$$$$ Q$$$ Q$$$$ $$$$$ `Q$$$$$$$P `Q$$$$$$$P $$$$$$$P `""""" "" "" Q$$$P "Q$$$P" "Q$$$P" `Q$$P" """
signature.asc
Description: This is a digitally signed message part