On Thu, 2007-07-12 at 13:08 -0700, Randy Dunlap wrote: 
> Hi,
> 
> Is there some kernel config or video config (possibly set at boot time
> via vga=xyz or video=wxy) where one or more of the logos is not
> applicable?  or the other way:  are there certain kernel or video
> configs where only certain logos are applicable?
> 
> 
> I've tested vesafb with LOGO_LINUX_VGA16 but I can't see the logo.
> I do see an empty space for it at the top of the screen area, however.
> (booting with vga=0x317 in /etc/lilo.conf file)
> 
> When I use LOGO_LINUX_CLUT224 instead, I do see the logo.
> 
> or when I use FB_VGA16 instead of vesafb and also use LOGO_LINUX_VGA16,
> I can see the logo.
> 
> I'm just trying to understand when/why I should expect (or not expect)
> to see a logo (if it is enabled).

It's a bug. And I've been wanting to fix that for some time. Logo's with
depths <= the fb depth should still be shown. The problem is that VGA16
and monochrome logos do not contain color information, so we have to use
the console palette (and not create a new one). Try the attached patch.

Tony