# Re: Fw: \[Bugme-new\] \[Bug 2916\] New: Console font became black on black after upgrade from 2.6.6 to 2.6.7

- From: Andrew Morton \<hidden\>
- Date: 2004-06-19 01:41:24 
- List: linux-fbdev
- Page: https://ratatoskr.run/linux-fbdev/2004/06/13453203
- Thread: https://ratatoskr.run/linux-fbdev/2004/06/13453200/t.md

```text
David Eger [ref] wrote:
>
> > # Graphics support
> > #
> > CONFIG_FB=y
> > CONFIG_FB_VESA=y
> > CONFIG_FB_RADEON=y
> > 
> > #
> > # Console display driver support
> > #
> > CONFIG_VGA_CONSOLE=y
> > CONFIG_DUMMY_CONSOLE=y
> > # CONFIG_FRAMEBUFFER_CONSOLE is not set
> 
> For a typical setup, framebuffer drivers (CONFIG_FB_VESA, CONFIG_FB_RADEON) 
> are only really useful if you want the console to live on top of them... 
> so use either:
> 
> (1) CONFIG_FB + (CONFIG_FB_VESA | CONFIG_FB_RADEON) + CONFIG_FRAMEBUFFER_CONSOLE
> 
> or
> 
> (2) CONFIG_VGA_CONSOLE

Thanks.

> Please let me know if any of these three setups work.  I wouldn't select
> both VESA and a specific driver.... eww... I'd guess they would get
> confused and try to access the same hardware...

This all sounds hard to express via kernel config, but it sounds pretty
easy to avoid via a few state variables in the kernel.

Do you think it's possible to prevent illegal things from happening at
runtime?



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
```