From ArchWiki
Revision as of 11:49, 11 August 2011 by Det (talk | contribs) (Configuration)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Splashy#)


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).


  1. Grab splashy-full from the AUR. Instructions on installing packages from the AUR are available here.


Default Framebuffer

If your hardware does not support Uvesafb this will have to do.

  1. Find the kernel framebuffer mode number closest as possible to your monitor.
  2. Add quiet vga=mode_number splash to your kernel command line in /boot/grub/menu.lst.
    Example: kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro quiet vga=791 splash

It is recommended to use Uvesafb if your hardware supports it. This allows you to use the exact native resolution of your monitor (including wide screen splashes).

If you have a chipset that supports kernel mode setting (KMS), this is preferable to using Uvesafb.

  1. Add quiet splash to your kernel command line in /boot/grub/menu.lst.
    Example: kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro quiet splash

Other Configuration Files


Add this in Template:Filename, e.g.:



Remember to rebuild the initramfs image whenever Splashy's config changes. (E.g. Splashy theme was changed.) Install any themes before running this to prevent form having to do this twice!

  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 initramfs image
    # mkinitcpio -p <kernel name>
    # mkinitcpio -p kernel26

The kernel command line

You now need to set quiet splash as you kernel command line parametres in your bootloader. The following is an example for Grub2 and Template:Filename (the legacy Grub and Lilo follow the same pattern):

linux /boot/vmlinuz26 root=/dev/... ro quiet splash

You can force enable KMS early start by appending "radeon.modeset=1" (for radeon cards) or "i915.modeset=1" (for intel cards) to your kernel options:

linux /boot/vmlinuz26 root=/dev/... radeon.modeset=1
linux /boot/vmlinuz26 root=/dev/... i915.modeset=1

You may also edit the file Template:Filename and append your kernel options to the line GRUB_CMDLINE_LINUX_DEFAULT="". To re-generate Template:Filename run:

# grub-mkconfig -o /boot/grub/grub.cfg


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 one you want. Note that themes ending in 43 are 4:3 aspect ratio, and the others are widescreen. Try "archlinux-simplyblack" as a good first theme, e.g.:


Rebuild your kernel image (refer to the mkinitcpio article for more info):

# mkinitcpio -p [name of your kernel preset]

Known Problems

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Splashy#)
  1. Splashy doesn't terminate or automatically switch to verbose mode if an error occurs or when an init script fails. No longer true with splashy-full package.
  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.
  4. Adding <autoverboseonerror>no</autoverboseonerror> in /etc/splashy/config.xml may solve problems when booting in battery mode on laptops
  5. If you get a lot of directfb errors, change "1.2" to "1.4" in /lib/initcpio/install/splashy
  6. If you get an error with libjpeg, try installing libjpeg6
  7. If you use gsplashy and a theme does not appear on the list, make sure that config.xml in the folder of the theme is named theme.xml instead
  8. If you get a libz.so.1 error, try either symlinking /lib/libz.so.1 to /usr/lib/libz.so.1 or changing /lib/libz.so.1 to /usr/libz.so.1 in /lib/initcpio/install/splashy
  9. If you are using Gnome, and are starting GDM as a daemon, Splashy causes Gnome to not be able to properly shutdown/reboot. To fix this issue, remove GDM as a daemon from /etc/rc.conf, and set up GDM with the /etc/inittab file. This could possibly work with other display managers, but I can only confirm that this works with GDM.