https://bugzilla.novell.com/show_bug.cgi?id=725965 https://bugzilla.novell.com/show_bug.cgi?id=725965#c5 --- Comment #5 from Michael Chang <mchang@suse.com> 2011-12-02 08:44:01 UTC --- I think I know the cause, that's because the modeinfo not delivered from loader (grub2) to kernel thus efifb won't start. Kernel boots in pure text mode. This wouldn't be a problem if bios leaves a text mode to loader. But if this mode is graphical mode this problem will occur. The text console won't work in a graphical mode. I took a bit look at grub2's code, the fix wouldn't trivial .. That's because it relies on an (video) adapter object be in active state to query what's the mode set to kernel. This object would not be created unless someone (eg, gfxterm) made a set video mode request. We can't force creating it to fix the issue, as this means force to set a mode which not applicable. We have to let the grub2 aware the initial mode bios leaves to it and take actions accordingly (for eg, create object during initial holding correct modeinfo). But this would not work because, as far as I can see so far, no viable interface defined in video driver for knowing the current mode . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.