Re: Framebuffer drivers that break the boot on systemswithout thehardware

From: Rene Herman
Date: Sun Aug 10 2008 - 17:49:12 EST


On 09-08-08 23:19, Frans Pop wrote:

Rene Herman wrote:

Ingo Molnar posted a list of drivers he found to break the boot during
testing of randconfig kernels and among them are a number of FB drivers:

FB_VESA

This one is set to "y" in the kernel configs for the generic Debian kernels for i386 and x86_64 and is used by default for the graphical version of the Debian Installer, so I'd be very surprised if it broke very many systems...
AFAIK it is only actually enabled if the 'vga=' boot parameter is passed.

Ingo's mail also lists FRAMEBUFFER_CONSOLE which again is set to "y" in Debian's standard kernel configs for x86 (and probably most other arches).

Okay. MDA_CONSOLE was also in there impying RAM at 0xb0000 which might indicate a gun/foot situation here...

(and FB_VIRTUAL)

This one should be fixed with 2.6.27-rc1. The commit that fixes it is:
commit b604838ac6d233fd6bffc0e758a818133a01ff22
Author: Frans Pop <elendil@xxxxxxxxx>
Date: Wed Jul 23 21:31:26 2008 -0700
vfb: only enable if explicitly requested when compiled in

Ah, thanks.

Rene.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/