Re: [2.5.68] no console messages after switch to FB (matrox

[Vagn Scott <vagn@ranok.com>]

Petr Vandrovec wrote:
> 
> > CONFIG_FB=y
> > CONFIG_FB_VESA=y
> > CONFIG_VIDEO_SELECT=y
> > CONFIG_FB_MATROX=y
> 
> Are you sure that your boot messages are directed to the matroxfb and
> not to the vesa?
> 
> In the past keyword for selecting matroxfb options was 'video=matrox:...',
> while now it is 'video=matroxfb:...', so you may have to modify your
> lilo.conf line (and do not ask me why these two letters were added if
> we have video= prefix... I do not know).

Adding video=matroxfb did the trick.  Thanks for the tip.

I still don't understand the logic of it, though.
If the kernel can find the resources to present the logo,
why can't it just keep using those resources for the rest
of the boot?

char *foo = find_a_home_for_tux();
if(foo) {
	logo_logo_logo(foo);
	keep_on_booting_baby(foo);
}
else {
	boot_or_die_trying("blinkenlights_n_beeperen");
}


what's next, rootname=/?

-- 
         _~|__
   >@   (vagn(     /
    \`-ooooooooo-'/
  ^^^^^^^^^^^^^^^^^^^^^^ The best pearls come from happy oysters. ^^^^^