> There is a boot option to do this, but I can't remember what it is :-)
What you mean, I believe, is "quiet".
> LILO loading linux...
> Uncompressing the kernel...
Yeah, these can be easily supressed, somewhere in arch/i386/boot/compressed
Are you in effect saying that Linux is *not* reinitializing the display,
but the bootloader is? That would be interesting, I'd have to write some-
where else :P
> > There is a boot option to do this, but I can't remember what it is :-)
> What you mean, I believe, is "quiet".
Yep, that's it :-)
> > LILO loading linux...
> > Uncompressing the kernel...
> Yeah, these can be easily supressed, somewhere in arch/i386/boot/compressed
>
> Are you in effect saying that Linux is *not* reinitializing the display,
> but the bootloader is?
No.
If you use the framebuffer, the kernel re-initialises the display when
it boots.
John.
* John Bradford <[email protected]> [030128 11:52]:
> > Yeah, these can be easily supressed, somewhere in arch/i386/boot/compressed
> >
> > Are you in effect saying that Linux is *not* reinitializing the display,
> > but the bootloader is?
>
> No.
>
> If you use the framebuffer, the kernel re-initialises the display when
> it boots.
In vesafb this is different. The video mode is set before 32bit mode is
entered, then the 32bit part of the kernel just assumes it can paint to
some memory found attached to the graphics device.
Still, for painting a bootsplash screen using fbcon, this does not
matter as all you need is the framebuffer memory.
Stefan
--
The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense. -- E. W. Dijkstra