SliTaz Forum

romano

Member

Registered: 2011-12-08

Posts: 91

Loading Screen

is it possible to show image while loading in background?

i tried splash image but this one doesnt keep stay while slitaz loading.

thanks

lexeii

Administrator

Registered: 2012-03-21

Posts: 1,853

Re: Loading Screen

This thingy called 'bootsplash'. Forcing it to work is not a trivial task.

You need to patch kernel etc. How-to from ArchLinux you can find here:

https://wiki.archlinux.org/index.php/Category:Bootsplash

Arch differs with SliTaz, but I think there is a close direction. You can find SliTaz packages in http://pkgs.slitaz.org and you can find other linuxes' packages in http://pkgs.org and can try to convert it to SliTaz packages with 'tazpkg convert ...'

Trixar_za

Administrator

Registered: 2011-03-29

Posts: 1,506

Re: Loading Screen

Actually it's simpler than that Aleksej. SliTaz 4 has a package called slitaz-fbsplash which can do this. It should be enabled by default once you installed the package, so it should show up at next reboot.

Trixar_za

Administrator

Registered: 2011-03-29

Posts: 1,506

Re: Loading Screen

Er, don't. Seems it's broken and using it will keep SliTaz from booting...

romano

Member

Registered: 2011-12-08

Posts: 91

Re: Loading Screen

i hope in slitaz 5 can be much easier.

like parameters in menu.lst

romano

Member

Registered: 2011-12-08

Posts: 91

Re: Loading Screen

i use frugal installation. i guess not possible with slitaz-fbsplash.

oddowl

Member

Registered: 2012-10-03

Posts: 10

Re: Loading Screen

fbsplash still not working? OK, I undid FBSPLASH="no" in /etc/rcS.conf using rescue OS, and now I seem to have quiet boot. are there any other simple alternatives, plymouth may be?

dudu

Member

Registered: 2018-05-15

Posts: 8

Re: Loading Screen

To find a bootsplash or to start it is not the problem, there are the kernel logo, fbsplash or splashy

from ubuntu old releases. But during boot the bootsplash stops and the screen gets black. In the res-

ponsible file /etc/init.d/rcS there are tasks, that do not harmonize with the bootsplash, for example

configuring xorg or loading modules. When we use the frugal install, these tasks have to be done every

boot. So we use the full installation. If there are still any conflicts, we put the corresponding lines

at the end of the file, so they do not interrupt the bootsplash.

1) Install a slitaz 5.0 rolling to a partition.

   chmod u+s /bin/su

   rm /lib/udev/devices/null

   mknod /lib/udev/devices/null c 1 3

   chmod 666 /lib/udev/devices/null

2) Boot the system. When you see a changing resolution, this is the

   point, where a conflict exists and the bootsplash would disappear.

3) Open /etc/init.d/rcS and replace

   if [ "$UDEV" = 'yes' ]; then

   action 'Triggering udev events: --action=add'

   udevadm trigger --action=add

   status

   fi

   by

   if [ "$UDEV" == 'yes' ]; then

   echo -n 'Triggering udev events: --action=add'

   MODALIASES="[c]ls /sys/bus/*/devices/*/modalias | grep -v 0000:00:00.0 | grep -v 0000:00:02.0[/c]"

   for ONEMODALIAS in $MODALIASES

   do

   ONEPATH="[c]dirname $ONEMODALIAS[/c]"

   if [ -e ${ONEPATH}/uevent ];then

   echo add > ${ONEPATH}/uevent

   usleep 20000

   fi

   done

   udevadm trigger --action=add --subsystem-match="input" --subsystem-match="sound"

   status

   fi

   (sleep 2; /etc/init.d/$LOGIN_MANAGER start >/dev/null) &

   by

   (sleep 1; /etc/init.d/$LOGIN_MANAGER start >/dev/null) &

   if [ -n "$MESSAGE" ]; then

   newline

   colorize 32 "$MESSAGE"

   fi

   ;;

   by

   if [ -n "$MESSAGE" ]; then

   newline

   colorize 32 "$MESSAGE"

   fi

   echo add > /sys/bus/pci/devices/0000:00:00.0/uevent

   echo add > /sys/bus/pci/devices/0000:00:02.0/uevent

   ;;

After that it should be possible to get a bootsplash, until slim

starts. Of course there are still the messages about boot progress,

which can be removed. If you want to have a dynamic bootsplash with

changing images, you can use fbi from the package fbida.