uvesafb breaks after upgrade to 2.6.29-gentoo-r5 kernel.

[cbeley]

Today I upgraded from linux-2.6.24-gentoo-r8 to linux-2.6.27-gentoo-r8 and now when I boot I get a black screen. X starts fine, but I get a black screen if I try to view one of my consoles. While booting, I see the kernel starting, then my old splash screen appears for a second, then I end up with my black screen (at the point where it would load the splash screen from the harddrive instead of from my initrd image).

I seem to have the appropriate kernel settings selected and for kicks, I recompiled v86d and klibc with no luck.

EDIT: I'm very confused now. Even if I remove video from menu.lst on my kernel line, the screen still goes black :S
EDIT2: by removing uvesafb from my kernel I'm able to see my bootup screen again..but...I sort of want my splash screen working with uvesafb again.

Any idea what could be going on? Below is some potentially useful information:

Related Kernel Settings I have enabled:

[Peach]

I'd suggest you to follow spock's uvesafb howto to be sure everything has been correctly done.
after that, report in again to see what can be done.
_________________
Gentoo user since 2004.
"It's all fun and games, until someone loses an eye" - mom

[samo]

Some month ago I had similar problems with uvesfb and could solve them. Please read "uvesafb framebuffer support doesn't work [solved]"

[cbeley]

[samo]

In my config CONFIG_FB_VESA as well as CONFIG_VGACON_SOFT_SCROLLBACK are not set.

I'm using the following line in grub.conf

[cbeley]

fbsplash-emergence-1024x768 is now irrelevant to the problem since I now have grub set up like this:

[Peach]

that's good you've removed the splash, I was going to ask you for that.

anyway, since I don't know if you've selected something else on your kernel graphics section, it could be a good idea to see what these commands output:

[cbeley]

Well, I think I may have found a bug with ndiswrapper and VESA (When I had only that enabled....my network devices died after a few minutes, but its fine when I have uvesafb on).

Anyway, if I do cat /sys/class/graphics/fb0/modes I get

[cbeley]

ALRIGHT! I have found the culprit!

When I couldn't play fullscreen video that led me to believe that something was up with the new xorg-6, so, I decided to downgrade to xorg-5, which prompted me to look at a wiki page I was following referring to some xorg-6 specific features. One nice new thing about xorg-6 is the inclusion of kernel modesetting and to enable that I had "Enable modesetting on intel by default". I also noticed in the description that it said that would be loaded before any framebuffer (and VESA takes advantage of the modesetting actually...kind of neat to have both my screens used during boot with VESA). So, I downgraded to xorg-5 and got rid of that kernel option and now everything works (including my full-screen video issues).

However, this isn't the ideal solution. I do not seem to have the same sort of 3D performance I gained with xorg-6, my keyboard's arrow keys are acting a little funny (though, I don't think that should be too hard to fix), and why isn't uvesafb compatible with kernel modsetting? I definitely want to go back to xorg-6 once it becomes more stable and be able to use modsetting, but I also like my boot splash screen that requires uvesafb.

Anyway, is this considered a bug that I should report? I think I can say pretty confidently that modsetting and uvesafb don't get along with each other.

EDIT: Went ahead and re-enabled decorations and set my configuration to how it use to be. My boot screen is working like it use to, so that did the trick for everything.

[Peach]