SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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
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?
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)
Last edited by try-alls; 08-20-2010 at 11:35 AM.
Reason: typo's
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.
Last edited by corbis_demon; 08-20-2010 at 11:53 AM.
Reason: added information
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
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)
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.