USplash/Splashy - Current status

djclue917 · 2007-04-18 03:59:06

I'm thinking of having our own splashy-themes package. If you created Splashy themes for Arch, then please let me know about it.

raymano · 2007-04-20 19:03:54

Great job djclue917. I'm using the 2.6.19 beyond kernel and followed your wiki and it works!

Some questions:

1) At boot up, is it normal to see "::Loading initramfs" right before the splash screen shows or have I missed something in the set up? If it is normal is there anyway of getting rid of it?
2) Is there a way or plans to integrate splashy with hibernate-scripts so that when suspending to disk, splashy shows a progress bar, similar to using suspend to disk with gensplash?
3) When I reboot or shutdown, the splashy screen flashes on to the screen for an instance and the screen changes to text, same as shutting down without splashy. Is this normal behavior?

Thank you,
Raymano

djclue917 · 2007-04-21 03:38:48

raymano wrote:

Great job djclue917. I'm using the 2.6.19 beyond kernel and followed your wiki and it works!
Some questions:
1) At boot up, is it normal to see "::Loading initramfs" right before the splash screen shows or have I missed something in the set up? If it is normal is there anyway of getting rid of it?

That is actually normal because Splashy is executed right before init starts.

2) Is there a way or plans to integrate splashy with hibernate-scripts so that when suspending to disk, splashy shows a progress bar, similar to using suspend to disk with gensplash?

I may look into that in the future. Currently, I'm focusing on ironing out bugs and finishing the basic functionalities.

3) When I reboot or shutdown, the splashy screen flashes on to the screen for an instance and the screen changes to text, same as shutting down without splashy. Is this normal behavior?
Thank you,
Raymano

That is actually normal. Remember that Splashy is a purely user-space application and that Arch's shutdown is actually very fast. Splashy terminates just before the "Sending SIGTERM To Processes" stat msg. Also, take note that the daemons listed in /etc/rc.conf and the currently running ones are almost instantaneously stopped. Meaning, the time it takes to stop all the daemons is roughly one second. Splashy, in that given time frame, will not be able to finish displaying the progress bar decreasing from 100% to 0% because that time frame is just to short. To be able to observe that without rebooting, try running splashy test 2>/dev/null as root. You should see how "slow" the progress bar moves.

Mhyrraner · 2007-04-21 17:21:00

mhn ... like it.
but it takes nearly 40s (old laptop) longer to boot with splash.
I think this is mainly because i start slim somewhere in rc.sysinit, and then start lots of daemons, most of them backgrounded. Is there a way to tell splashy to ignore at least the backgrounded daemons?

Thanks.
MyR

djclue917 · 2007-04-22 11:26:10

Well, in its current state, Splashy will display the progress of all daemons plus the stuff in rc.sysinit. I doubt that Splashy is the reason why your laptop is taking longer to boot because as soon as "/etc/rc.d/splashy start" has been executed, Splashy will terminate almost immediately. Also, the progress bar movement will be less accurate when you let Splashy "ignore" certain events.

Mhyrraner · 2007-04-22 15:12:26

ahh. I put splashy at the beginning of daemons list in rc.conf.
progress bar isn't that important to me, but now i get to X as fast as before ...

MyR

baze · 2007-04-22 16:45:05

after the update to initscripts 0.8-7 splashy doesn't fill the progress bar anymore and doesn't show text. can anyone confirm this?

djclue917 · 2007-04-23 05:13:53

baze wrote:

after the update to initscripts 0.8-7 splashy doesn't fill the progress bar anymore and doesn't show text. can anyone confirm this?

Sorry I forgot to tell you about this earlier... This is a known problem because Splashy works by using the redefined stat_bkgd() and stat_busy() functions in /etc/splashy/functions. There is really no way of redefining those functions other than making /etc/rc.d/functions source /etc/splashy/functions. Thus, when the initscripts package is upgraded, the line in /etc/rc.d/functions, which is ". /etc/splashy/functions", disappears.

The simple solution is to reinstall the Splashy package. I know that this is a bit of a hassle but this is really the only way of doing it right now.

I've already added this issue in the wiki.

iphitus · 2007-04-23 08:45:59

it might be cleaner to provide a new initscripts package, as has happened with other netscripts packages,

or.. file a feature request for an addition to /etc/rc.d/functions at the end, like:

if [ -n $SPLASH ]; then
 . /etc/$SPLASH/functions
fi

so, if SPLASH="splashy" is set in /etc/rc.conf, then it will use splashy. If it's undefined or blank, then it won't do anything.

James

deficite · 2007-04-23 20:40:32

Very good idea iph! I'd much prefer that over having to have alternate packages.

Last edited by deficite (2007-04-23 20:40:54)

djclue917 · 2007-04-24 08:03:00

iphitus wrote:

it might be cleaner to provide a new initscripts package, as has happened with other netscripts packages,
or.. file a feature request for an addition to /etc/rc.d/functions at the end, like:
if [ -n $SPLASH ]; then
 . /etc/$SPLASH/functions
fi
so, if SPLASH="splashy" is set in /etc/rc.conf, then it will use splashy. If it's undefined or blank, then it won't do anything.
James

I'm actually thinking about doing the latter because, in the original Debian package, that's really how it was done. I'd file a feature request soon after I've cleaned up Splashy some more, added more comments and documentation, and some other stuff. I was actually planning on orphaning Splashy and leaving the work to the devs/TUs who are interested in further improving Splashy on Arch.

djclue917 · 2007-04-24 08:42:29

iphitus wrote:

it might be cleaner to provide a new initscripts package, as has happened with other netscripts packages,
or.. file a feature request for an addition to /etc/rc.d/functions at the end, like:
if [ -n $SPLASH ]; then
 . /etc/$SPLASH/functions
fi
so, if SPLASH="splashy" is set in /etc/rc.conf, then it will use splashy. If it's undefined or blank, then it won't do anything.
James

iphitus, do you know of other userspace bootsplash managers other than Splashy and Usplash? Because if there aren't any, we could just simplify the code to:

if [ -f /etc/splashy/functions ]; then
  . /etc/splashy/functions
fi

and just omit the SPLASH variable in /etc/rc.conf. What do you think?

axelgenus · 2007-05-05 16:31:54

The download link is dead... some other mirror?

baze · 2007-05-05 19:00:59

i just found that you used the mant1core link in the pkgbuild, which was bad because that domain doesn't exist anymore

djclue917 · 2007-05-06 03:03:23

baze wrote:

i just found that you used the mant1core link in the pkgbuild, which was bad because that domain doesn't exist anymore

I've temporarily uploaded your theme to my server.

Romashka · 2007-05-07 19:42:15

djclue917 wrote:

iphitus wrote:
it might be cleaner to provide a new initscripts package, as has happened with other netscripts packages,
or.. file a feature request for an addition to /etc/rc.d/functions at the end, like:
if [ -n $SPLASH ]; then
 . /etc/$SPLASH/functions
fi
so, if SPLASH="splashy" is set in /etc/rc.conf, then it will use splashy. If it's undefined or blank, then it won't do anything.
James
iphitus, do you know of other userspace bootsplash managers other than Splashy and Usplash? Because if there aren't any, we could just simplify the code to:
if [ -f /etc/splashy/functions ]; then
  . /etc/splashy/functions
fi
and just omit the SPLASH variable in /etc/rc.conf. What do you think?

There is fbsplash/gensplashutils and bootsplash.org projects, that both need patching a kernel (the 1st seems to be dying while the 2nd is resurrected).
Though they are not supported in Arch it's better to have $SPLASH variable as a more generic solution (and for the future too).

Besides, this code:

if [ -f /etc/splashy/functions ]; then
  . /etc/splashy/functions
fi

is longer than

if [ -n $SPLASH ]; then
 . /etc/$SPLASH/functions
fi

Last edited by Romashka (2007-05-07 19:45:43)

dtw · 2007-05-07 23:40:58

I'm with Romashka. I plan to look at making an initscripts pkg for splashy...if necessary at least.

iphitus · 2007-05-08 00:31:26

i think the generic approach i suggested would be best.... and it lets people hook into the initscripts for more than just splashes. Like making them look entirely different or something silly like that,

James

p_schott · 2007-05-11 06:30:23

Thank you djclue917.
I installed splashy following the wiki. It works nice... excepted that after boot sequence, X is unable to start. I think it is related to vga=791 in menu.lst (as my usual resolution is 1280x1024). As suggested I tried other vga codes (namely 794 and 795), but I just got a "signal out of range" instead of the splash screen, and a freeze of the boot process .

Last edited by p_schott (2007-05-11 06:38:15)

p_schott · 2007-05-13 12:15:33

After ready in detail the error messages output, the solution was to set "UseFBdev" to "false" in xorg.conf

Section "Device"
Identifier "ATI Technologies, Inc. RV280 [Radeon 9200 SE]"
Driver "radeon"
BusID "PCI:1:0:0"
Option "UseFBDev" "false"
EndSection

I don't know why, but it works. :)

ahioros · 2007-05-14 19:25:11

Sometimes my boot is so slow, with halt and reboot freeze my pc :-S and dont halt.

baze · 2007-05-14 20:08:41

ahioros: it's a bug in -5 and -6 versions of the splashy.functions file. -4 shuts down just fine. and when your pc seems frozen on shut down, try to switch to either tty1 or 2 (alt+f1 or alt+f2) and this should switch to splashy, doing nothing. if it does, press esc and your pc should continue. i suggest to use splashy-0.3.2-4 for now, as that version works pretty fine.

tafsen · 2007-05-15 13:09:00

After I followed the wiki and installed splashy, my boot time was increase with a couple if minuts

ahioros · 2007-05-15 18:52:41

tafsen use splashy-0.3.2-4 :-)

tafsen · 2007-05-15 21:37:18

Even if -0.3.2-7 is out?

Arch Linux

#51 2007-04-18 03:59:06

Re: USplash/Splashy - Current status

#52 2007-04-20 19:03:54

Re: USplash/Splashy - Current status

#53 2007-04-21 03:38:48

Re: USplash/Splashy - Current status

#54 2007-04-21 17:21:00

Re: USplash/Splashy - Current status

#55 2007-04-22 11:26:10

Re: USplash/Splashy - Current status

#56 2007-04-22 15:12:26

Re: USplash/Splashy - Current status

#57 2007-04-22 16:45:05

Re: USplash/Splashy - Current status

#58 2007-04-23 05:13:53

Re: USplash/Splashy - Current status

#59 2007-04-23 08:45:59

Re: USplash/Splashy - Current status

#60 2007-04-23 20:40:32

Re: USplash/Splashy - Current status

#61 2007-04-24 08:03:00

Re: USplash/Splashy - Current status

#62 2007-04-24 08:42:29

Re: USplash/Splashy - Current status

#63 2007-05-05 16:31:54

Re: USplash/Splashy - Current status

#64 2007-05-05 19:00:59

Re: USplash/Splashy - Current status

#65 2007-05-06 03:03:23

Re: USplash/Splashy - Current status

#66 2007-05-07 19:42:15

Re: USplash/Splashy - Current status

#67 2007-05-07 23:40:58

Re: USplash/Splashy - Current status

#68 2007-05-08 00:31:26

Re: USplash/Splashy - Current status

#69 2007-05-11 06:30:23

Re: USplash/Splashy - Current status

#70 2007-05-13 12:15:33

Re: USplash/Splashy - Current status

#71 2007-05-14 19:25:11

Re: USplash/Splashy - Current status

#72 2007-05-14 20:08:41

Re: USplash/Splashy - Current status

#73 2007-05-15 13:09:00

Re: USplash/Splashy - Current status

#74 2007-05-15 18:52:41

Re: USplash/Splashy - Current status

#75 2007-05-15 21:37:18

Re: USplash/Splashy - Current status

Board footer