tomas at slax
Sep 1, 2007, 2:23 AM
Post #3 of 4
> It's a bit messy, because syslinux will reset the screen in order to
> write the "Loading" message;
When syslinux loads the kernel, it's already out of vesamenu control.
So perhaps add two options
- one for vesamenu.c32, to retain the image
(or preferably to display a new one when the menu finishes,
which will be shown during kernel startup)
(so it can display a text like 'Linux is loading, wait')
- another option for syslinux/isolinux/etc, to be quiet and don't reset
> however, it's just a matter of sorting out
> the proper loose ends.
> I think I'd like to leave this for post-3.52, but that doesn't mean I'm
> rejecting the idea, just that I'd like to get 3.52 out the door.
I'd be very happy if the retained image could appear soon.
As I try LILO and the bmp-retain option, it seems it works only
partially. If the kernel starts to output any text, image vanishes. And
my kernel 126.96.36.199 outputs something even with 'quiet' boot parameter.
So before the implementation for syslinux starts, I'd suggest to verify
whether it is even possible to completely start Linux kernel (up to
/sbin/init execution) with an image on the screen.
SYSLINUX mailing list
Submissions to SYSLINUX [at] zytor
Unsubscribe or set options at:
Please do not send private replies to mailing list traffic.