Jump to content
MottS

Animated lilo ..

Recommended Posts

Hi guys

 

I'm playing with Gentoo in those time and find out something interesting if you are bored of the lilo boot screen. This is an animated lilo screen asking you which os to choose.

 

http://www.gamers.org/~quinet/lilo/xray-green.html

http://www.gamers.org/~quinet/lilo/xray-blue.html

http://www.gamers.org/~quinet/lilo/penguins.html

http://www.gamers.org/~quinet/lilo/breakout.html

 

You only have to clic one of the above link and download the boot message. For instance, if you clic XRAY-BLUE.HTML, you have to download xray-blue.boot.gz (181 KB). Now, open up a console, cd to where you put the file and su to root. Unzip the file and put it in /boot.

 

gunzip xray-blue.boot.gz

cp xray-blue.boot /boot

 

Now, edit lilo (I use nano) and instead of message=/boot/message, put the following and run lilo

 

nano -w /etc/lilo.conf

--> message = /boot/xray-blue.boot <--

lilo

 

Here is my lilo.conf for reference:

 

vga=normal

message = /boot/xray-blue.boot

boot="/dev/hda"

prompt

map = /boot/System.map

lba32

timeout="150"

default=Gentoo_LinuX



image="/boot/bzImage"

       root="/dev/hda6"

       label="Gentoo_LinuX"

       initrd="/boot/initrd"

       vga="791"

       read-only



other = /dev/hda1

       label="Windows_XP"

       table = /dev/hda

 

Now reboot and enjoy ... :wink:

 

*Yes I reinstalled XP :cry:

 

MOttS

Share this post


Link to post
Share on other sites

might this be better put in the "tips and tricks"?

 

just a thought :)

 

edit: did this get moved or was i lost when i posted that? ^

Share this post


Link to post
Share on other sites
Guest bradenm

I can't get it to work on Mandrake 9. When I run "lilo -v", it says

Using MENU secondary loader

Calling map_insert_data

Mapping message file /boot/xray-blue.boot

Calling map_insert_file

Instead of

Using GRAPHIC secondary loader

Calling map_insert_data

Mapping message file /boot/message -> message-graphic

Calling map_insert_file

And upon bootup, I only get a text menu.

Here's my lilo.conf:

boot=/dev/hda

map=/boot/map

vga=normal

default=linux

keytable=/boot/us.klt

prompt

#nowarn

timeout=150

#message=/boot/message

message=/boot/xray-blue.boot

menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz

       label=linux

       root=/dev/hda5

       initrd=/boot/initrd.img

       append="quiet devfs=mount hdd=ide-scsi"

       vga=788

       read-only

image=/boot/vmlinuz

       label=linux-nonfb

       root=/dev/hda5

       initrd=/boot/initrd.img

       append="devfs=mount hdd=ide-scsi"

       read-only

other=/dev/hda1

       label=windows

       table=/dev/hda

image=/boot/vmlinuz

       label=failsafe

       root=/dev/hda5

       initrd=/boot/initrd.img

       append="failsafe devfs=nomount hdd=ide-scsi"

       read-only

using "LILO version 22.3.2"

Share this post


Link to post
Share on other sites

I would hide 'menu-scheme=wb:bw:wb:bw' and 'keytable=/boot/us.klt' and rerun lilo. Here is what I get when I type 'lilo -v'.

 

root@localhost gd # lilo -v

LILO version 22.3.3, Copyright (C) 1992-1998 Werner Almesberger

Development beyond version 21 Copyright (C) 1999-2002 John Coffman

Released 30-Aug-2002 and compiled at 14:38:01 on Feb  5 2003.



Reading boot sector from /dev/hda

Using MENU secondary loader

Calling map_insert_data

Mapping message file /boot/xray-blue.boot

Calling map_insert_file



Boot image: /boot/bzImage

Mapping RAM disk /boot/initrd

Added Gentoo_LinuX *



Boot other: /dev/hda1, on /dev/hda, loader CHAIN

Added Windows_XP



/boot/boot.0300 exists - no backup copy made.

Writing boot sector.

 

MottS

Share this post


Link to post
Share on other sites

It is probably not compatible with MDK .. I use Gentoo and LILO is 22.3.3.

 

Anyone got it to work on MDK ?

 

MOTtS

Share this post


Link to post
Share on other sites

http://www.gamers.org/~quinet/lilo/help.html Read this to find out why it didn't work.

 

Anyone got it to work on MDK ?
Yep....I think?I get the animated lilo boot prompt, but after that it's either scrolling text or the bootsplash themes from mandrake. I've tried it both ways. Is the animation or the animated image suppose to show while going through the boot processes? Or do I need to make a bootsplash theme with the background image?

 

From here;http://gnomesupport.org/forums/viewtopic.php?t=2043 I used this link; http://www-personal.umich.edu/~lrsmith/Lin...mated_lilo.html to download

 

gfxboot-1.4-30.i386.rpm

gfxboot-devel-1.4-30.i386.rpm

lilo-21.7.5-54.i386.rpm

 

 

-Backed up my current /etc/lilo.conf (just in case)

-made sure my floppy bootdisk worked (just in case)

 

rpm -e --nodeps lilo (to remove mdk's lilo)

 

rpm -ivh gfxboot-1.4-30.i386.rpm gfxboot-devel-1.4-30.i386.rpm lilo-21.7.5-54.i386.rpm (to install rh's lilo pkgs with the animated patches)

 

The first two times I ran lilo it said it couldn't because it couldn't find /boot/message. I guess reading from my /etc/lilo.conf. So I uninstalled the new lilo and reinstalled the mdk lilo, backed up /boot/messages, uninstalled mdk's lilo, reinstalled rh's lilo, went to copy /boot/messages backup to /boot but it was there so I tried to run lilo again and it worked???? Just thought I'd mention this in case anyone has the same prob.

 

edited /etc/lilo.conf

 

 

The Mandrake Control Center isn't liking this rh lilo pkg, so I'll have to see if it'll let me make a bootsplash-theme or try it manually I guess, which is the fun way anyway :wink:

 

 

[root@localhost bvc]# lilo -v

LILO version 21.7-5, Copyright © 1992-1998 Werner Almesberger

Linux Real Mode Interface library Copyright © 1998 Josh Vanderhoof

Development beyond version 21 Copyright © 1999-2001 John Coffman

Released 06-May-2001 and compiled at 16:08:07 on Feb  1 2002.

 

Reading boot sector from /dev/hda

Merging with /boot/boot.b

Mapping message file /boot/xray-blue.boot

Boot image: /boot/vmlinuz-2.4.19-16

Mapping RAM disk /boot/initrd-2.4.19-16.img

Added ML9.0 *

Boot image: /boot/vmlinuz

Mapping RAM disk /boot/initrd.img

Added Linux

Boot image: /boot/vmlinuz

Mapping RAM disk /boot/initrd.img

Added failsafe

Boot other: /dev/hda1, on /dev/hda, loader /boot/chain.b

Added Win98

Boot other: /dev/fd0, loader /boot/chain.b

Pseudo partition start: 0

Added floppy

/boot/boot.0300 exists - no backup copy made.

Writing boot sector.

[root@localhost bvc]#

:twisted::twisted: :P :shock: :lol:

Share this post


Link to post
Share on other sites

I can't use mcc>Boot>Boot Config to change boot-splash themes now :evil:

 

Have to manipulate this as well I guess. :wink: Will post back if I figure it out. I've got the images but I'll have to play in the gimp which is unchartered territory I've been meaning to learn..so here we go :!: :)

Share this post


Link to post
Share on other sites
http://www.gamers.org/~quinet/lilo/help.html Read this to find out why it didn't work.

 

Anyone got it to work on MDK ?
Yep....I think?I get the animated lilo boot prompt, but after that it's either scrolling text or the bootsplash themes from mandrake. I've tried it both ways. Is the animation or the animated image suppose to show while going through the boot processes? Or do I need to make a bootsplash theme with the background image?

 

The animated lilo boot prompt isn't supposed to show while going through the boot processes. Those two things are separated. Here is what I understand from LiLo (from my /etc/lilo.conf)

 

vga=normal

message = /boot/xray-blue.boot

boot="/dev/hda"

prompt

map = /boot/System.map

lba32

timeout="150"

default=Gentoo_LinuX

 

image="/boot/bzImage"

       root="/dev/hda6"

       label="Gentoo_LinuX"

       initrd="/boot/initrd"

#       append="quiet"

       vga="791"

       read-only

 

other = /dev/hda1

       label="Windows_XP"

       table = /dev/hda

 

The first part (before image="/boot/bzImage") is related to the lilo boot splash (the animated lilo screen in our case). The image (or animation) is message = /boot/xray-blue.boot. It can be named anything you want like 'message' for the default MDK lilo installation or xray-blue.boot for this post. All the rest isn't really important (lba32, prompt, timeout="150", default=Gentoo_LinuX, vga=normal) exept boot="/dev/hda".

 

Now, starting from image="/boot/bzImage" to other = /dev/hda1, is what is going to appear if I choose Gentoo_LinuX at the lilo boot prompt. The background image is initrd="/boot/initrd" and the size of this image is vga="791" (791=1024x786 and 788=800x600). The text is scrolling on top of that image. Notice that if the image (initrd) is 1024x786 and you write vga="788" in lilo.conf, you'll get white text on top of a plain black screen. So if you did not changed the default /boot/initrd, you'll get the kernel text inside the gray contour (with the mandrake star) and blue backgroud.

 

The Mandrake team just took the same image for both the boot process and the lilo boot splash. This make things homogeneous...

 

Hope this clarify things out a little..

 

MOttS

Share this post


Link to post
Share on other sites

NOTE: VGA color depth vs resolution chart

 

depth------640x480-----800x600-----1024x768-----1280x1024

256----------769----------771-----------773-------------775

32000-------784----------787-----------790-------------793

65000-------785----------788-----------791-------------794

16.7 Mill.----786----------789-----------792-------------795

 

from --> http://forums.gentoo.org/viewtopic.php?t=26494

 

MottS

Share this post


Link to post
Share on other sites

Thanks MottS but I gave up. I just can't get the 2 to run together. Programer I'm not. :roll: What would be great is to have the animation at lilo and as you go through the boot process. I fidled enough with the mdk scripts though to screw it up :lol: well, the drakboot script for mcc>Boot>Boot Config that is. No I didn't bk it up :shock: I was too involve at the moment and not well focused :roll: :oops: I was going to choose the animation over bootsplash anyway and will just have to do the changes for boot parameters via vim :wink: Still got the animation though!

Share this post


Link to post
Share on other sites

If some people want to get the animated Lilo boot splash in Mandrake 9.1, here is what I did (pretty much like bvc did)

 

1) Download the modified lilo and gfxboot with those links:

http://www-personal.umich.edu/~lrsmith/Lin...1.4-30.i386.rpm

http://www-personal.umich.edu/~lrsmith/Lin...7.5-54.i386.rpm

 

2) Download one of the 4 (you only need one!) animated lilo boot splash:

http://www.gamers.org/~quinet/lilo/xray-green.boot.gz

http://www.gamers.org/~quinet/lilo/xray-blue.boot.gz

http://www.gamers.org/~quinet/lilo/penguins.boot.gz

http://www.gamers.org/~quinet/lilo/breakout.boot.gz

 

3) Open a console (CTRL+T), su to root (su + password), cd to where you put the files and type the following commands:

gunzip AnimatedLiloBootSplash.boot.gz

mv AnimatedLiloBootSplash.boot /boot/

urpmi lilo-21.7.5-54.i386.rpm gfxboot-1.4-30.i386.rpm

The first two commands gunzip (unzip) the animated lilo boot splash and move the unzipped file to /boot. Replace 'AnimatedLiloBootSplash' by the file you downloaded in step 2. The last command install the modified version of lilo. The system will tell you that you need to uninstall the current lilo version. Just press enter here and it will uninstall lilo for you and install the version you just downloaded in step 1.

 

4) Modify /etc/lilo.conf to load your new boot splash instead of the boring one (message). Here is my /etc/lilo.conf. Notice that I only changed 'message=/boot/messages' for 'message/boot/xray-blue.boot'. I left the rest as it was.

vga=normal

message=/boot/xray-blue.boot

boot=/dev/hda

prompt

map=/boot/map

lba32

timeout=100

default="Linux"

image=/boot/vmlinuz

       label="Linux"

       root=/dev/hda6

       initrd=/boot/initrd.img

       append="quiet devfs=mount hdc=ide-scsi hdb=ide-scsi acpi=off"

       vga=788

       read-only

 

5) Run lilo !

/sbin/lilo -v

 

Reboot and enjoy !

 

MOttS

Share this post


Link to post
Share on other sites

Thanks... it works now :D I didn't have lba32 in my lilo.conf, but once I added it in I got rid of that pesky "Fatal geo_comp_addr: Cylinder number is too big" error

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...