Hi,

Does splashy work on slackware 13.1 x64?

I've been to Alien Bob's site only to find out that splashy is supported for slackware 12.0.

Many Thanks.

Try this discussion:

http://www.linuxquestions.org/questi...isited-823253/

Try this discussion:

http://www.linuxquestions.org/questi...isited-823253/

Thanks but I've already tried that, but after a lot of attempts it wasn't getting implemented somehow..Then I saw a video on youtube where guy shows his slack box ver:13 with a bootsplash using splashy. So am trying to do what he has achieved.

hi,
excuse me, my reply is a bit [OT] ... if you can recompile kernel there is also bootsplash (instead of splashy): http://x-softsi.com.br/site/?p=26
[/OT]

Thanks fabiuxz, will give this one a try in VM. If I must recompile my kernel then can I add an image in the background without using the initrd, just an image over which boot messages will be visible? I am least interested in progress bar stuff now 'coz I don't want to use initrd..

With the bootsplash patch and the utilities, you have to use an initrd which contains or consists of the image you want as the background. For current kernels it may be best to add the image to a normal initrd. (WIth earlier kernels you could easily use just the image as the full initrd.) Nowdays, the kernel looks for an initrd which consists of a cpio archive, so you just have to place the image inside that cpio -the image file contains 'magic bits' which the kernel identifies as being the image -it doesn't matter what the image file is named.

There is a still-good howto on the LQ slack wiki about how to apply the patch, recompile the kernel, and how to compile and use the splashutils to create the image, and to display any animations or progress-bar you use in your init scripts. You'll need to directly modify the boot scripts to insert lines which tell the progress-bar what to do. This is the same system as I am usinh on an old 2.4 kernel system -I have animated images along with the progress-bar.

The bootsplash-patched kernel may not play well with your VM, as reported by LQ-member jong-357. I still like bootsplash very much and miss it on my newer systems -just haven't gotten around to setting them up.

thanks also gnashley for detailed contribution ... I add

bootsplash works fine also with huge-kernel or static-kernel ... the trick is to load a void initrd that contains only background images ... furthermore you can also incorporate an initramfs in kernel at compilation time (in this case background images are inside a file named 'bootsplash' at root of initramfs)...

or else, at init (when filesystem is mounted) it is also possible to switch image background to console with 'splash' command ... so you don't need initrd, example:
where '-u 0' = first console, '-u 1' = second, etc. ...

I like old bootsplash ...

Hey thanks you guys, much appreciated

I followed the slackwiki article and used the 3.6.33 patch from: http://x-softsi.com.br/site/?p=26
Applied the patch and can see the bootsplash option in menuconfig. Recompiled kernel and followed the standard procedure.
Modified and ran lilo. I've also created initrd through this command:
"splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg >> /boot/initrd.splash"

However am not able to follow the article correctly for static kernel(it mingles between huge and generic but isn't specific for static one). What is the use of initrd for static kernel? Do I need to generate one?

I have customized the default kernel .config file and have disabled the 'use initrd' option(it works).
How to do it?
I've tried this as well:
"splash -s -n -u 0 /boot/bootsplash-1024x768.cfg" where the image files are at the location mentioned in cfg file.(The code was placed in rc.S before this line--> "# Try to mount /proc:")

still outta luck..

I think that in kernel .config must be:
No, you don't need it ... it was only an example ...

I think that 'splash' command works if exist /proc/splash entry ... /proc filesystem is umounted in your case ...
you can try 'splash' command in a text console when you logged in ... check also if exist /proc/splash

Note:
- in lilo.conf you must enable (globally) framebuffer resolution:
- preferred method is to load a "void" initrd ... add to lilo.conf this entry:

Perfect! it works nicely!! ^_^ Yeahh. Thanks a lot fabiuxz

You rock mate, ye're !

I think the SlackWiki should be updated for this and kudos for the kernel patches!