Re: Is there a nofb equivalent for grub menu display?

[Reshat Sabiq]

On Sun, 2005-05-08 at 04:29 +0200, Yoshinori K. Okuji wrote:
> On Monday 02 May 2005 23:15, Reshat Sabiq wrote:
> > My question is about the grub splash screen. When it's enabled in this
> > setup, no menu, in fact nothing, can be seen during boot, although if you
> > ht space, and then Enter it is equivalent to going to the menu and booting
> > the default option. I wonder if setting something like a nofb flag in grub
> > would make the splash screen work, but i suspect there is no such flag.
> 
> We do not have a splash screen. Ask your vendor.
> 
> Okuji

What i meant is that i have to comment out the following line in
grub.conf to be able to see anything grub has to show:
#splashimage=(hd0,3)/grub/splash.xpm.gz

This happens when the active monitor during boot is a BarcoMed monitor,
and the reason is it needs special drivers for any kind of X, which
probably aren't available in Linux distros. I was able to boot from
Rescue CD using this monitor using the nofb flag. However, the Rescue CD
also has a background image before entering nofb flag, and it was shown
just fine. So what i phrased as nofb probably isn't exactly accurate:
how grub could do whatever it takes for the rescue CD, for instance, to
display a background image when it is just displaying the first menu
with options of how to boot on non-standard monitors, such as BarcoMed
(256-color, greyscale).

In short, the problem with splashimage doesn't exist if active monitor
is set to be a regular VGA monitor. This could be marked a very low
priority issue, or a non-issue, because grub works just fine even with
BarcoMed being the active monitor once the splashimage is commented out.
I leave it up to you to decide if any thought needs to be given to this.
Perhaps if more people bring this up, it would be worth considering.

Thanks.

signature.asc
Description: This is a digitally signed message part