Difference between revisions of "Splashy"

From ArchWiki
Jump to: navigation, search
m (Installation)
Line 11: Line 11:
# Grab the [http://aur.archlinux.org/packages.php?ID=27916 splashy-full package] in AUR, build it via makepkg (or whatever makepkg wrapper you like) and install via Pacman.
# Grab [http://aur.archlinux.org/packages.php?ID=27916 splashy-full] from the [[AUR]]. Instructions on installing packages from the AUR are available [[AUR_User_Guidelines#Installing_Packages_from_the_AUR|here]].

Revision as of 11:38, 11 August 2011

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.


Uvesafb Framebuffer (Preferred)

It is recommended to use Uvesafb if your hardware supports it (unless your hardware also supports KMS, see below). This allows you to use the exact native resolution of your monitor. It also allows you a widescreen boot splash.

  1. Follow the instructions on the Uvesafb page to install and configure.
  2. Add quiet splash to your kernel command line in /boot/grub/menu.lst.
    Example: kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro quiet splash

Default Framebuffer

You can also use the default kernel framebuffer if your hardware does not support Uvesafb.

  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

Kernel Mode Setting

If you have a chipset that supports kernel mode setting (KMS), this is preferable to using Uvesafb. Note that when KMS is enabled you should always disable Uvesafb, as well as any "vga=" and "video=" options in your bootloader as these will conflict with the native resolution enabled by KMS. You still have to add the quiet splash options in your grub config file.

Other Configuration Files


Add SPLASH="splashy" in /etc/rc.conf, 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


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


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


After you set your theme (and any time you change your theme) you will need to again run

# mkinitcpio -p kernel26

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.