Splashy
From ArchWiki
| i18n |
|---|
| English |
| Русский |
| 简体中文 |
| Español |
Contents |
Introduction
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 Arch Linux forum for a repo you can add with working splashy packages. Splashy in AUR also works (see below).
Installation
Attention! "initscripts-splashy" is now a dependency of splashy. It replaces "initscripts", so some files in /etc will be backed up as *.pacsave.
- Install initscripts-splashy from AUR, build it via makepkg (or whatever makepkg wrapper you like) and install via Pacman.
- Grab the splashy package in AUR, build it via makepkg (or whatever makepkg wrapper you like) and install via Pacman.
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.)
- Add
splashyat the end of the HOOKS in /etc/mkinitcpio.conf, e.g.:HOOKS="base udev autodetect ide sata filesystems ... splashy"
- Rebuild initramfs image
# mkinitcpio -p <kernel name>
E.g.# mkinitcpio -p kernel26
Upgrading
Don't forget to rebuild the initramfs image after upgrading Splashy.
Themes
You can install splashy-themes in AUR to get a nice splashy theme. After installing, look at the available themes like so:
$ ls /usr/share/splashy/themes
The folder name is the theme name. Now edit /etc/splashy/config.xml and change the theme name to the want you want. Note that themes ending in 43 are 4:3 aspect ration, and the others are widescreen. Try "simplyblack" as a good first theme. After you set your theme (and any time you change your theme) you will need to again run
# mkinitcpio -p kernel26
Known Problems
- Splashy doesn't terminate or automatically switch to verbose mode if an error occurs or when an init script fails.
- 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.
- X can show artefacts on the top of the screen, if splashy is activated during bootup.
- Adding
<autoverboseonerror>no</autoverboseonerror>in /etc/splashy/config.xml may solve problems when booting in battery mode on laptops