Splashy

From ArchWiki
Revision as of 15:51, 6 July 2008 by Georgia tech swagger (Talk | contribs) (Link to forum thread on the matter front and center)

Jump to: navigation, search

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n links end

Splashy is a userspace implementation of a splash screen for Linux systems. It provides a graphical environment during system boot using the Linux framebuffer layer via directfb.

Please see this post on the ArchLinux forum for a repo you can add with more up to date and modified splashy packages.


Installation

  1. Grab the package in AUR and build it via makepkg (or whatever makepkg wrapper you like) and install via Pacman.

Attention! "initscripts-splash" is now a dependency of splashy. It replaces "initscripts", so some files in /etc will be backuped as *.pacsave.

Configuration

/boot/grub/menu.lst

Add quiet vga=791 splash to your kernel command line in /boot/grub/menu.lst. e.g.:

kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro quiet vga=791 splash

/etc/rc.conf

Add SPLASH="splashy" in /etc/rc.conf. e.g.:

SPLASH="splashy"

/etc/mkinitcpio.conf

  • Remember to rebuild the initramfs image whenever Splashy's config changes. (e.g. Splashy theme was changed)
  1. Add splashy at the end of the HOOKS in /etc/mkinitcpio.conf. e.g.:
    HOOKS="base udev autodetect ide sata filesystems ... splashy"
  2. Rebuild kernel image
    # mkinitcpio -p <kernel name>
    e.g.
    # mkinitcpio -p kernel26

Upgrading

  • Don't forget to rebuild the initramfs image after upgrading Splashy.

Known Problems

  1. Splashy doesn't terminate or automatically switch to verbose mode if an error occurs or when an init script fails.
  2. Something goes "terribly wrong" when a forced filesystem check commences while Splashy is running. For some unknown reason (yet), the system reboots itself after the fsck.
  3. X can show artefacts on the top of the screen, if splashy is activated during bootup.

Links