I'm in the middle of installing Gentoo, and I've compiled a kernel with the radeonfb console driver. Here's what I have enabled: + Support for framebuffer devices + ATI Radeon display support + DDC/I2C for ATI Radeon support + Lots of debug output from Radeon drive + VGA text console + Framebuffer Console support In the grub.conf file, I have this at the end of the kernel line: video=radeonfb:1024x768 When booting up, radeonfb finds the device (A Radeon 7000 PCI card), the monitor flickers for a second, and then what I get is a 640x480 screen, but the kernel seems to think it's 1024x768, because text goes off the screen. I've googled for this, but what I find is old stuff where people are complaining about seeing a higher resolution than the one they asked for, with very little useful in response. I also can't find anything like this in the Gentoo bugzill database. This is the same kernel that comes with 2005.1, and that one seems to get the framebuffer to work. I can't figure out what I'm doing wrong, but there are no error messages that tell me anything has gone wrong.
Reopen if you can reproduce this problem with gentoo-sources-2.6.15-r5, we definitely won't be fixing 2.6.12 kernel since it doesn't exist in portage tree any more.
Well, I recently discovered that make oldconfig breaks things horribly if you try to go from 2.6.12 to 2.6.15, and I was told, by a gentoo developer, that I shouldn't even try. I spent literally hours combing through the kernel config trying to get the kernel configured the way I want it, and now you're telling me that I have to do it all over again? If so, please update the documentation to reflect this fact so that people don't get so horribly frustrated.
Ok, I've installed 2.6.15-gentoo-r5, and it has exactly the same problem.
I have, with the help of people on LKML, determined that this is an EDID problem. Disabling DDC/I2C support fixed the problem. So, there's some issue with DDC either with the driver or with my monitor. BTW, I apologize for my rudeness earlier. Dealing with a few kernel problems can't be anything compared to dealing with countless, ungrateful Linux users (such as myself) who don't give you credit for all the work you do pro bono. Sorry.
OK, since it works for you, I'm marking the bug as fixed. If you think the problem is with the driver and if it's reproducible with a vanilla kernel, you might want to try opening a bug at the kernel bugzilla (http://bugzilla.kernel.org/), or contacting the fbdev developers on the linux-fbdev-devel mailing list.
