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.
and run ./autogen.sh --prefix=/ && make && make install
- edited the file /etc/splashy/config.xml and added the line
Code:
<fifo>/etc/splashy/splashy.fifo</fifo>
within the section <splashy></splashy>.
- added in /etc/rc.d/rc.S after
Code:
if grep -wq sysfs /proc/mounts && grep -wq tmpfs /proc/filesystems ; then
if ! grep -wq nohotplug /proc/cmdline ; then
if [ -x /etc/rc.d/rc.udev ]; then
/bin/sh /etc/rc.d/rc.udev start
fi
fi
fi
/sbin/splashy boot # <--- HERE !!!
- added after every "fi" in /etc/rc.d/rc.S and /etc/rc.d/rc.M the line
Code:
/sbin/splashy_update "progress nn"
to update the progressbar. For "nn" set numbers from "00" in the very beginning of the rc.S up to "100" at the end of rc.M.
- added in /etc/rc.d/rc.local
Code:
/sbin/splashy_update exit
to finish the progressbar.
- added to my /etc/lilo.conf the append
Code:
append = "splash quiet"
and run lilo -v to install the changes.
My video card is a GMA915 which uses the framebuffer device with vesafb.
I added the start of the splashy process after the udev process will start, because before this process will start there was an error message, that "splashy boot" cannot access the device /dev/fb0, it doesn't exist at this process of booting the system.
I try to figure out how to run the splashy with an initrd.gz, so that the splashy will appear quite in the beginning of the boot process ...
If you've got a gig of hard disk space kicking around you might want to test out splashys on your system by doing this!
I don't think splashys should be too hard for Slackware 12, too bad it doesn't come with one already setup that you can configure as you would gdmsetup.
and run ./autogen.sh --prefix=/ && make && make install
- edited the file /etc/splashy/config.xml and added the line
Code:
<fifo>/etc/splashy/splashy.fifo</fifo>
within the section <splashy></splashy>.
- added in /etc/rc.d/rc.S after
Code:
if grep -wq sysfs /proc/mounts && grep -wq tmpfs /proc/filesystems ; then
if ! grep -wq nohotplug /proc/cmdline ; then
if [ -x /etc/rc.d/rc.udev ]; then
/bin/sh /etc/rc.d/rc.udev start
fi
fi
fi
/sbin/splashy boot # <--- HERE !!!
- added after every "fi" in /etc/rc.d/rc.S and /etc/rc.d/rc.M the line
Code:
/sbin/splashy_update "progress nn"
to update the progressbar. For "nn" set numbers from "00" in the very beginning of the rc.S up to "100" at the end of rc.M.
- added in /etc/rc.d/rc.local
Code:
/sbin/splashy_update exit
to finish the progressbar.
- added to my /etc/lilo.conf the append
Code:
append = "splash quiet"
and run lilo -v to install the changes.
My video card is a GMA915 which uses the framebuffer device with vesafb.
I added the start of the splashy process after the udev process will start, because before this process will start there was an error message, that "splashy boot" cannot access the device /dev/fb0, it doesn't exist at this process of booting the system.
I try to figure out how to run the splashy with an initrd.gz, so that the splashy will appear quite in the beginning of the boot process ...
Fluxx.
I downloaded and untarred something calling itself splashy-0.3.5 but a directory called splashy-0.1.6 showed up with no line 47 (it only had 32 lines... a bad sign)
I've checkinstall'ed the DirectFB package and it's ready to go!
Code:
**********************************************************************
Done. The new package has been saved to
/home/perry/Desktop/DirectFB-1.1.0/DirectFB-1.1.0-i386-1.tgz
You can install it in your system anytime using:
installpkg DirectFB-1.1.0-i386-1.tgz
**********************************************************************
And would like to give 0.3.5 a try. took reviewed the boot-splashy product, looks dicey...
Here's a link to the debian page for splashy_0.3.5. Unusually there is no debian patch, this seems to be software written by/for debian and so there is no patching to do to make it debian-compatible. http://packages.debian.org/unstable/graphics/splashy
I've done a lot of research on splash screens the last couple of weeks. splashy itself may be obsoleted in debian by the usplash utility. usplash is a ubuntu project that appears to be a fork of splashy. But because of more interest and development it may replace the original. The plus-side to using either one is that they bot operate entirely in user-space and require no kernel patches. The drawback is that they both leave a 'gap' between the finish of the init process and the starting of the display manager -up to a couple of seconds on older machines. Also, they are unable to show a splash screen early during the boot process, unless you create a special(and bulky?) intrd. Even then, it seems likely that a second blank(black screen with text) will appear during early boot-up as the kernel switches from the initrd to mounting the / partition.
The old bootsplash method(and its' offshoot fbsplash/gensplash from gentoo) was much more complete, but requires patching the kernel to be able to use it so it requires someone who stays interested enough to maintain the patches at least.
I installed Eric's version of slashy 0.3.5 and directfb 1.1.0 and ran splashy test/preview and did a reboot.
The splash screen came up but was crooked... who knows why?
The other options looked even dicier. If Eric hasn't provided a how-to on how to install this thing other than an installpkg and a man splashy then it's not ready for main stream use by Slackware. Not wasting my time on it.
Too bad though, Vector's splash screen comes up no problem (when I boot the Vector partition) I wonder how they did it...!
The splash screen came up but was crooked... who knows why?
Read the documentation, especially on directfb, fbset and look at /etc/fb.modes .
Quote:
The other options looked even dicier. If Eric hasn't provided a how-to on how to install this thing other than an installpkg and a man splashy then it's not ready for main stream use by Slackware. Not wasting my time on it.
It will never be ready for mainstream use by Slackware - it will never get included. My build was a courtesy to someone else.
Splashy package requires that you work on it yourself.
I was interested enough to maintain a bootsplash patch for personal reasons and for personal use only. Which I did up to the 2.6.29 kernel release. I am not the only one who did this.
After the 2.6.29.x and later kernels came up with KMS, after I tested KMS and got used to it, I discovered that the old bootsplash method did not work at all. I tried. Perhaps someone could make it work again, without the normal VESA console, making use of KMS.
After trying unsuccessfully with splashy, and even with plymouth (which says it supports KMS), I had almost given up and thought about going back to the old VESA fb, which is noticeably slower than the KMS inteldrmfb. Until I checked fbsplash (and fbcondecor).
So far, I have managed to make it work with KMS. It works better with fbcondecor, by the way, so maybe there could be possible to make a complete newer implementation of the old bootsplash. So far, the silent and verbose mode do work specifying which mode I want directly in lilo.conf. I haven't succeeded at switching between modes using F2. I haven't succeeded at making the progress bar work -properly.
It does work at 1280x800, so any laptop users there willing to do some research...
As I have succeeded, by messing with my init scripts, at booting in less than 25 seconds (19 without CUPS, 23 with CUPS), I lost some interest.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.