LinuxQuestions.org - Using a different slack.bmp image in Lilo

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Using a different slack.bmp image in Lilo (https://www.linuxquestions.org/questions/slackware-14/using-a-different-slack-bmp-image-in-lilo-827466/)

Using a different slack.bmp image in Lilo

Hi, I want to use a different bmp image in Lilo when the system boots up. What I want to know is how do I get this new image to confirm to the specs as detailed in liloconfig. Or are these specifications only a guideline? Please advise.

this page helped me...
http://www.yzzerdd.net/index.php?pag...are/bootsplash

But I did not compile a new kernel for the verbose/silent splash
images...I only changed the slack.bmp.
HTH

Basically all I did was replace the slack.bmp image with
the one from that page and adjusted part of lilo.conf
to move the timer count down to the lower left of the screen
and to put my operating system choices at the upper right...
and then just ran lilo:

Quote:

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 236,,,254,,
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 1,30,236,0

no wonder, it was created in 2006, where the bootsplash patches were not yet included in the kernel
right now, you can just change the .bmp in /etc/lilo.conf and re-run lilo :D

Thank you so much! That page was very helpful. :)

Nice to see people still using Lilo! :D

i have a wallpaper that i made myself an has now become my gdm, xfce splash an wallpaper.
i used gimp to turn it onto .bmp renamed it to slack.bmp an moved the original elsewhere but when i ran lilo it came up sayin (off memory) something about invalid bit map or words to that effect, any ideas?

EDIT: here is the link to the pack i made http://xfce-look.org/content/show.ph...content=128689

either of these pics will work with the standard lilo layout as the "detail" is centred

I think using the slack.dat provided in lilo's slackbuild source would be helpful.

Quote:

Originally Posted by corbis_demon (Post 4072548)

I think using the slack.dat provided in lilo's slackbuild source would be helpful.

ok dumbass moment but can you go into more detail please
i.e. will this muck up my current lilo config etc etc ( i am a former buntu user so used to the "babysitting", lol)

He He..no problem. I was referring to this file.
I'm not sure you mean liloconfig or lilo.conf; I'm guessing you mean the /etc/lilo.conf file. No, this file is a generated companion file to the slack.bmp that can be found here, and it won't alter your lilo.conf. It'd really help you , if you were to go to the link provided aocab, in his earlier post.

so how would i use this as it looks like a sample of the lilo config (to me anyway)

here is my current lilo config

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
compact
lba32

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 10
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
# Linux bootable partition config ends

Quote:

Originally Posted by try-alls (Post 4072542)

lilo it came up sayin (off memory) something about invalid bit map or words to that effect, any ideas?

It's probably a problem with size or bit depth.

You can use the "lilo -E" command on your image file to adjust it's color,table and timer variables.

EDIT: I mentioned the slack.dat so that it might serve as a reference. It is generated when you run the "lilo -E filename.bmp" command.

Quote:

Originally Posted by corbis_demon (Post 4072574)

ah cool, as the post above this mentions bit depth etc the image does have rgb on it (well thats what comes up in the title bar on gimp lol)

i will give this command a go now an reboot to see if its worked an report back, thanks people

EDIT: ran the command (whilst the image was in my pictures folder) an it said "bash: lilo: command not found"

ah the command is /sbin/lilo -E FILENAME* but now it give me some options to which i am noobishly unsure:

Quote:

rich@AMILO ~> /sbin/lilo -E slack.bmp
Editing contents of bitmap file: slack.bmp

Table dimensions:
Number of columns: 1
Entries per column (number of rows): 25
Table upper left corner:
Column(X): 13 (chars) or 96p (pixels) Row(Y): 6 (chars) or 80p (pixels)

Text colors:
Normal: Foreground: 7 Background: transparent Shadow: none
Highlight: Foreground: 15 Background: transparent Shadow: none
Timer: Foreground: 7 Background: 0 Shadow: none
Timer position:
Column(X): 65 (chars) or 512p (pixels) Row(Y): 3 (chars) or 32p (pixels)

Commands are: L)ayout, C)olors, T)imer, Q)uit, W)rite:

how would i use these options

i went for broke and just write then yes for the next two questions and it still returns with "fatal unsupported bitmap", if there are any gimp masters (wow that sounds a lil wierd) that could give me info an how to make it supported with gimp that may make this easier,
i know some of you could prob do it for me but thats not the point i need to learn lol

thanks again in advance

What does Gimp say about your bmp? Dimensions, depth etc..

Quote:

Originally Posted by corbis_demon (Post 4072539)

Nice to see people still using Lilo! :D

Lilo is the best...

Quote:

Originally Posted by try-alls (Post 4072648)

how would i use these options

Open the file in Gimp, and go to Image -> Mode -> Indexed. Now under "Generate Optimum Palette" choose the maximum number of colors to be 255 (Well, I chose 255. Dunno how selecting a different number will affect this. I'm no graphics guru ;) ). Click "Convert" and save. I think that should do it.
Now, the slack.dat file details the dimensional, positional and color parameters of the image (if I'm not wrong). Keep this file open alongside for reference when you are editing the variables. I'm sure it'll help.

Ok, I guess this would help:

Code:

root [ ~ ]# lilo -E silentwww-640x480.bmp                                  

Editing contents of bitmap file:  silentwww-640x480.bmp



Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 13 (chars) or 96p (pixels)  Row(Y): 6 (chars) or 80p (pixels)



Text colors:

  Normal:  Foreground: 7  Background: transparent  Shadow: none

Highlight:  Foreground: 15  Background: transparent  Shadow: none

    Timer:  Foreground: 7  Background: 0  Shadow: none

Timer position:

  Column(X): 65 (chars) or 512p (pixels)  Row(Y): 3 (chars) or 32p (pixels)



Commands are:  L)ayout, C)olors, T)imer, Q)uit, W)rite:  L



Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 13 (chars) or 96p (pixels)  Row(Y): 6 (chars) or 80p (pixels)



Layout options:  D)imensions, P)osition, B)ack:  D



Number of columns (1..5) [1]:  1

Entries per column (1..30) [25]:  25





Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 13 (chars) or 96p (pixels)  Row(Y): 6 (chars) or 80p (pixels)



Layout options:  D)imensions, P)osition, B)ack:  P



Table UL column (1..80) or (8p..632p) [13 or 96p]: 60p

Table UL row (1..30) or (16p..464p) [6 or 80p]: 175p





Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 8+ (chars) or 60p (pixels)  Row(Y): 11+ (chars) or 175p (pixels)



Layout options:  D)imensions, P)osition, B)ack:  B







Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 8+ (chars) or 60p (pixels)  Row(Y): 11+ (chars) or 175p (pixels)



Text colors:

  Normal:  Foreground: 7  Background: transparent  Shadow: none

Highlight:  Foreground: 15  Background: transparent  Shadow: none

    Timer:  Foreground: 7  Background: 0  Shadow: none

Timer position:

  Column(X): 65 (chars) or 512p (pixels)  Row(Y): 3 (chars) or 32p (pixels)



Commands are:  L)ayout, C)olors, T)imer, Q)uit, W)rite:  C



  Normal:  Foreground: 7  Background: transparent  Shadow: none

Highlight:  Foreground: 15  Background: transparent  Shadow: none

    Timer:  Foreground: 7  Background: 0  Shadow: none



Text color options:  N)ormal, H)ighlight, T)imer, B)ack:  N



Normal text text fg color (0..255) [7]: 254

Normal text text bg color (0..255,transparent) [transparent]: 

Normal text text sh color (0..255,none) [none]: 19





  Normal:  Foreground: 254  Background: transparent  Shadow: 19

Highlight:  Foreground: 15  Background: transparent  Shadow: none

    Timer:  Foreground: 7  Background: 0  Shadow: none



Text color options:  N)ormal, H)ighlight, T)imer, B)ack:  H



Highlight text text fg color (0..255) [15]: 19

Highlight text text bg color (0..255,transparent) [transparent]: 

Highlight text text sh color (0..255,none) [none]: 254





  Normal:  Foreground: 254  Background: transparent  Shadow: 19

Highlight:  Foreground: 19  Background: transparent  Shadow: 254

    Timer:  Foreground: 7  Background: 0  Shadow: none



Text color options:  N)ormal, H)ighlight, T)imer, B)ack:  B







Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 8+ (chars) or 60p (pixels)  Row(Y): 11+ (chars) or 175p (pixels)



Text colors:

  Normal:  Foreground: 254  Background: transparent  Shadow: 19

Highlight:  Foreground: 19  Background: transparent  Shadow: 254

    Timer:  Foreground: 7  Background: 0  Shadow: none

Timer position:

  Column(X): 65 (chars) or 512p (pixels)  Row(Y): 3 (chars) or 32p (pixels)



Commands are:  L)ayout, C)olors, T)imer, Q)uit, W)rite:  T



Timer colors:

    Timer:  Foreground: 7  Background: 0  Shadow: none

Timer position:

  Column(X): 65 (chars) or 512p (pixels)  Row(Y): 3 (chars) or 32p (pixels)



Timer setup:  C)olors, P)osition, D)isable, B)ack:  C



Timer text fg color (0..255) [7]: 254

Timer text bg color (0..255,transparent) [0]: 0

Timer text sh color (0..255,none) [none]: 19





Timer colors:

    Timer:  Foreground: 254  Background: 0  Shadow: 19

Timer position:

  Column(X): 65 (chars) or 512p (pixels)  Row(Y): 3 (chars) or 32p (pixels)



Timer setup:  C)olors, P)osition, D)isable, B)ack:  P



Timer col (1..80) or (8p..632p) [65 or 512p]: 30p

Timer row (1..30) or (16p..464p) [3 or 32p]: 434p





Timer colors:

    Timer:  Foreground: 254  Background: 0  Shadow: 19

Timer position:

  Column(X): 4+ (chars) or 30p (pixels)  Row(Y): 28+ (chars) or 434p (pixels)



Timer setup:  C)olors, P)osition, D)isable, B)ack:  B







Table dimensions:

  Number of columns:  1

  Entries per column (number of rows):  25

Table upper left corner:

  Column(X): 8+ (chars) or 60p (pixels)  Row(Y): 11+ (chars) or 175p (pixels)



Text colors:

  Normal:  Foreground: 254  Background: transparent  Shadow: 19

Highlight:  Foreground: 19  Background: transparent  Shadow: 254

    Timer:  Foreground: 254  Background: 0  Shadow: 19

Timer position:

  Column(X): 4+ (chars) or 30p (pixels)  Row(Y): 28+ (chars) or 434p (pixels)



Commands are:  L)ayout, C)olors, T)imer, Q)uit, W)rite:  W

Save companion configuration file? (yes or no) [N]:  yes

Save changes to bitmap file? (yes or no) [N]:  yes

Writing output file:  silentwww-640x480.bmp

This is how you should go about if you were to get the parameters in the text file that I linked to in my previous post.

ok cool, so gonna sound dumb again just reading through it, will this work with any image, i.e. how do i know how many columns, row etc will i need or is it just a case of hit an miss

Quote:

Originally Posted by try-alls (Post 4073066)

ok cool, so gonna sound dumb again just reading through it, will this work with any image, i.e. how do i know how many columns, row etc will i need or is it just a case of hit an miss

Ok, that output was generated when I used this image. Of course, I scaled it down, and converted it. Using those same variable values on your image might not produce the desired result ( I tried it on my image, and it got spliced). So yes, it is a bit of trial and error, unless you are an expert in graphics. But please don't get exasperated now that you've gotten this far. Also, if you haven't visited the link that aocab provided, I suggest you do. I got all the info that I'm now disseminating from that link.

Quote:

Originally Posted by try-alls (Post 4072648)

ah the command is /sbin/lilo -E FILENAME* but now it give me some options to which i am noobishly unsure:

how would i use these options

i went for broke and just write then yes for the next two questions and it still returns with "fatal unsupported bitmap", if there are any gimp masters (wow that sounds a lil wierd) that could give me info an how to make it supported with gimp that may make this easier,
i know some of you could prob do it for me but thats not the point i need to learn lol

thanks again in advance

Quote:

3) you can use lilo.conf or the bmp file itself to tell lilo the color information (for your text and timer-box)

Using /sbin/lilo -E FILENAME sets the color information in the bmp file.
I did not use that method.

I modified lilo.conf to set the color information.

Code:

man lilo.conf

has all the details on how to set the various settings (and was a little easier for me to understand).

Cheers
HTH

Thanks for clearing it up, aocab :) . But will it work for any image file that I might use?

Quote:

Originally Posted by corbis_demon (Post 4073092)

Thanks for clearing it up, aocab :) . But will it work for any image file that I might use?

From what I've read, the image has to be
a 640x480 BMP with 256 colors (or less) and indexed.

tried with the link and the image turns to complete black so gonna spend a fair bit o time with this tryin different settings

(i am happy with lilo's standard setup i.e. where the timer is etc just a shame it's not as simple as just swap the files, lol)

cheers for the help will report back once successsful

Quote:

Originally Posted by try-alls (Post 4073333)

I'm not quite sure which image you are referring to...
this is the one I used:
http://www.yzzerdd.net/images/boot/s...40x480x256.bmp

Could you possibly post the image you are trying to use?

Hmm...Something interesting happened after I fed the info into my lilo.conf. I ran lilo, and got this:

Code:

root [ ~ ]# lilo                                                            

Warning: LBA32 addressing assumed

Warning: Unable to determine video adapter in use in the present system.

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Added Slack *

And now there's no bootloader :( Darn.

Quote:

Originally Posted by corbis_demon (Post 4073407)

Hmm...Something interesting happened after I fed the info into my lilo.conf. I ran lilo, and got this:

Code:

root [ ~ ]# lilo                                                            

Warning: LBA32 addressing assumed

Warning: Unable to determine video adapter in use in the present system.

Warning: Video adapter does not support VESA BIOS extensions needed for

  display of 256 colors.  Boot loader will fall back to TEXT only operation.

Added Slack *

And now there's no bootloader :( Darn.

You should still have a bootloader (those are just warnings)...?
I've gotten those messages before when I had to chroot into the system to run lilo when something went wrong. I would just re-run lilo again as root once I could get back into the system in runlevel 3.

Sorry, I made a typo in the .conf . root got assigned to a non-existent boot image. :). But yes, you're right, those are just warnings. But the interesting bit is that no warnings (other than the LB32 one) were issued when I ran the command from inside a chroot. Not important, I'm sure. Sorry to bother. Thanks for taking time out to reply. :)

EDIT: Really sorry to take the discussion somewhat off the track, but kernel 2.6.35.2 seems to have got serious bug that's causing boot failures. Is there a fix available in 2.6.35.3? I mean it's a pain recompiling now that I compiled 2.6.35.2 a few days back.

Quote:

Originally Posted by corbis_demon (Post 4073433)

you can get rid of the lba32 warning by adding "lba32"
(without quotes) to the beginning of lilo.conf.

i too had this but it was when i added "compact" to lilo which is most useful, lba32 is needed for larger sized hard-drives