SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Does slackware support a boot splash image ? I don't mean a lilo bootsplash image... but like... you know in Fedora core1 or in Gentoo, when the system scripts are run, they appear with a background image (saying press F2 for verbose mode etc. )
the progress bar didnt work..can you explain a lil' bit on this?
Basically you just have to add "progressbar x" (where x is a number between 0 - 100) throughout rc.S and rc.M.
Also, did you add "/etc/rc.d/rc.bootsplash" to the start of those files? I'm looking through my install doc, and I seem to have left that out, I might have to revise it. At first it was only meant as a supplement, but it's sorta halfway to a full guide now.
Check file:/usr/doc/bootsplash/samples for the sample of those files. although they don't have the "progreassbar x" line in them.
I really have to fix up my install file. Maybe make the whole thing a slackware tgz.
first of all thanks for the quick answers. It worked.. sort of... I have the background image, when I load Slackware but I don't have the progressbar, I've inserted in rc.M and rc.S at the beginning of these files, the line: /etc/rc.d/rc.bootsplash is that correct ? but when I load Linux it keeps saying: progressbar, command not found. Any ideas why this is happening ? Also... I don't know if I should start a new thread or not... I have a radeon 9200 graphics card. Has anyone tried to use the radeon framebuffer module from the kernel 2.6.6 ? Is it functional for this type of cards ?
okai I looked in the doc files and in the sample startup scripts and now it gives me no error, but still there is no progressbar, I've uncommented the progressbar function in rc.bootsplash and added animate startup to the rc.s and rc.M scripts, also i added . /etc/rc.d/rc.bootsplash (Could you please explain why I need that first point before /etc/rc.d/rc.bootsplash ? )
it worked man, but I must say, in rc.S and rc.M I was inspired by your sample files where it's written ". /etc/rc.d/rc.bootsplash" with the trailing point, if I don't put that trailing point I get: progressbar: command not found. So could you tell me what that point is for ?
No more ideas on how to fix this? Do you think it could maybe be the patch I used? I got bootsplash-3.1.3-2.6.5-vanilla.patch.gz from http://metawire.org/~bhaskar/kernel-patches/ I didn't have any problems installing that patch but that's the only thing I can think of that could have gone wrong. Any other ideas please.
Last edited by MustangCSA; 05-22-2004 at 08:04 PM.
Something is not right in your kernel. Either you missed something or it's built as a module...
<*> RAM disk support
(4096) Default RAM disk size [*] Initial RAM disk (initrd) support[*] VGA text console[*] Video mode selection support[*] Support for frame buffer devices (EXPERIMENTAL)[*] VESA VGA graphics console[*] Use splash screen instead of boot logo[*] Advanced low level driver options
<*> 8 bpp packed pixels support
<*> 24 bpp packed pixels support
<*> 32 bpp packed pixels support
And I suppose it could be the patch as well..... I used a 2.4.24 patch on a 2.4.25 kernel. Just changed all the refrences in the patch to corespond to my kernel version... So, I would look to your kernel before considering the patch... 10:1 it's just something you over looked....
Did you read the readme in that patch directory as well?
Oh.... It will also give you that error if you don't append "splash=silent" to your bootloader file...
And.... Make sure you stay on a 16 bit color depth.....
And... When in doubt, Rebuild your initrd splash file.... If your using Lilo, you may have to remake the initrd if you've changed something in your config just like you need to rewrite your MBR if you change your config.... Just a guess... I don't use Lilo for these reasons so I can't say for sure.... This isn't the case with grub.. Only if you move your / partition do you need to remake your initrd or rewrite your MBR...
What else?...... After all that I would either look to your syntax in the scripts or the patch itself.... Your also running a brand new kernel and patch..... Thats a recipe for headaches in my opinion. My kernel and patch have been around for months so thats plenty of time for bugs to be reported, therefore it just works... I would also take that into consideration.... Good luck..