Difference between revisions of "Splashy"

From ArchWiki
Jump to: navigation, search
(Configuration)
(Remove out of date info. Mark configuration out of date.)
(36 intermediate revisions by 12 users not shown)
Line 1: Line 1:
[[Category: Boot process (English)]]
+
[[Category:Bootsplash]]
[[Category: Eye candy (English)]]
+
[[es:Splashy]]
{{i18n|Splashy}}
+
[[ru:Splashy]]
{{Out of date}}
+
[[zh-CN:Splashy]]
 +
[http://alioth.debian.org/projects/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 [http://www.directfb.org directfb].
  
==Introduction==
+
==Installation==
[http://splashy.alioth.debian.org 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 [http://www.directfb.org directfb].
+
  
Please see [http://bbs.archlinux.org/viewtopic.php?id=48978 this post] on the Arch Linux forum for a repo you can add with working splashy packages.   Splashy in AUR also works (see below).
+
Before you can use Splashy, you should enable [[Kernel Mode Setting]]. Please refer to the specific instructions for [[ATI#Kernel_mode-setting_.28KMS.29|ATI cards]], [[Intel#KMS_.28Kernel_Mode_Setting.29|Intel cards]] or [[Nouveau#KMS|Nvidia cards]].  
  
==Installation==
+
Install {{AUR|splashy-full}} from the [[Arch User Repository]].
  
# 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]].
+
You may also check out [https://bbs.archlinux.org/viewtopic.php?id=48978 this topic] on the [https://bbs.archlinux.org/ Arch Linux forum] for a repository you can add with working splashy packages.
  
 
==Configuration==
 
==Configuration==
=== Default Framebuffer ===
+
{{Out of date|Update for systemd.}}
If your hardware does not support Uvesafb this will have to do.
+
  
# [http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers Find the kernel framebuffer mode number closest as possible to your monitor].
+
===/etc/rc.conf===
# Add <code>quiet vga='''mode_number''' splash</code> to your kernel command line in ''/boot/grub/menu.lst''. <br>Example: <code>kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro '''quiet vga=791 splash'''</code>
+
  
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).
+
Add this in {{ic|/etc/[[rc.conf]]}}:
 +
{{hc|/etc/rc.conf|2=SPLASH="splashy"}}
  
If you have a chipset that supports kernel mode setting ([[KMS]]), this is preferable to using Uvesafb.
+
===Including Splashy in initramfs===
  
# Add <code>quiet splash</code> to your kernel command line in ''/boot/grub/menu.lst''. <br>Example: <code>kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro '''quiet splash'''</code>
+
Add Splashy to the HOOKS array in {{ic|/etc/[[mkinitcpio.conf]]}}. It '''must''' be added ''after'' '''base''', '''udev''' and '''autodetect''' for it to work:
 +
{{hc|/etc/mkinitcpio.conf|2=HOOKS="base udev autodetect splashy [...]"}}
  
=== Other Configuration Files ===
+
For early KMS start add the module [[radeon]] (for radeon cards), [[Intel|i915]] (for intel cards) or [[nouveau]] (for nvidia cards) to the MODULES line in {{ic|/etc/mkinitcpio.conf}}:
====/etc/rc.conf====
+
{{hc|/etc/mkinitcpio.conf|2=MODULES="i915"
Add this in {{Filename|/etc/[[rc.conf]]}}, e.g.:
+
'''or'''
SPLASH="splashy"
+
MODULES="radeon"
 +
'''or'''
 +
MODULES="nouveau"}}
  
====/etc/mkinitcpio.conf====
+
Rebuild your kernel image (refer to the [[mkinitcpio]] article for more info):
'''Remember to rebuild the initramfs image whenever Splashy's config changes.''' (E.g. Splashy theme was changed.)
+
{{bc|# mkinitcpio -p [name of your kernel preset]}}
'''Install any themes before running this to prevent form having to do this twice!
+
#Add '''<code>splashy</code>''' at the '''end''' of the HOOKS in ''/etc/mkinitcpio.conf'', e.g.:<pre>HOOKS="base udev autodetect ide sata filesystems ... splashy"</pre>
+
#Rebuild initramfs image<pre># mkinitcpio -p <kernel name></pre>E.g.<pre># mkinitcpio -p kernel26</pre>
+
  
 
===The kernel command line===
 
===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 {{Filename|/boot/grub/grub.cfg}} (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:
+
You now need to set {{ic|quiet splash}} as you kernel command line parameters in your bootloader. See [[Kernel parameters]] for more info.
  
linux /boot/vmlinuz26 root=/dev/... radeon.modeset=1
+
===Themes===
  
linux /boot/vmlinuz26 root=/dev/... i915.modeset=1
+
You can install {{AUR|splashy-themes}} from the AUR. After installing, look at the available themes like so:
 +
{{bc|ls /usr/share/splashy/themes}}
  
You may also edit the file {{Filename|/etc/default/grub}} and append your kernel options to the line ''GRUB_CMDLINE_LINUX_DEFAULT=""''. To re-generate {{Filename|grub.cfg}} run:
+
The folder name is the theme name. Now change the theme to the one you want, eg.:
# grub-mkconfig -o /boot/grub/grub.cfg
+
{{bc|# splashy_config -s darch-white}}
  
===Themes===
+
{{Note|Themes ending in 43 are of 4:3 aspect ratio - the others are widescreen.}}
You can install [http://aur.archlinux.org/packages.php?ID=19626 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.:
+
<current_theme>archlinux-simplyblack</current_theme>
+
Rebuild your kernel image (refer to the [[mkinitcpio]] article for more info):
+
# mkinitcpio -p [name of your kernel preset]
+
  
==Known Problems==
+
Rebuild your kernel image with:
{{Poor writing}}
+
{{bc|# mkinitcpio -p [name of your kernel preset]}}
#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.'''
+
#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 <code><autoverboseonerror>no</autoverboseonerror></code> in /etc/splashy/config.xml may solve problems when booting in battery mode on laptops
+
#If you get a lot of directfb errors, change "1.2" to "1.4" in /lib/initcpio/install/splashy
+
#If you get an error with libjpeg, try installing libjpeg6
+
#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
+
#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
+
#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 [http://wiki.archlinux.org/index.php/GDM#inittab_method /etc/inittab file].  This could possibly work with other display managers, but I can only confirm that this works with GDM.
+
  
==Links==
+
and reboot.
* http://splashy.alioth.debian.org
+
* http://www.directfb.org
+

Revision as of 13:00, 1 August 2013

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.

Installation

Before you can use Splashy, you should enable Kernel Mode Setting. Please refer to the specific instructions for ATI cards, Intel cards or Nvidia cards.

Install splashy-fullAUR from the Arch User Repository.

You may also check out this topic on the Arch Linux forum for a repository you can add with working splashy packages.

Configuration

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

Reason: Update for systemd. (Discuss in Talk:Splashy#)

/etc/rc.conf

Add this in /etc/rc.conf:

/etc/rc.conf
SPLASH="splashy"

Including Splashy in initramfs

Add Splashy to the HOOKS array in /etc/mkinitcpio.conf. It must be added after base, udev and autodetect for it to work:

/etc/mkinitcpio.conf
HOOKS="base udev autodetect splashy [...]"

For early KMS start add the module radeon (for radeon cards), i915 (for intel cards) or nouveau (for nvidia cards) to the MODULES line in /etc/mkinitcpio.conf:

/etc/mkinitcpio.conf
MODULES="i915"
or
MODULES="radeon"
or
MODULES="nouveau"

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

# mkinitcpio -p [name of your kernel preset]

The kernel command line

You now need to set quiet splash as you kernel command line parameters in your bootloader. See Kernel parameters for more info.

Themes

You can install splashy-themesAUR from the AUR. After installing, look at the available themes like so:

ls /usr/share/splashy/themes

The folder name is the theme name. Now change the theme to the one you want, eg.:

# splashy_config -s darch-white
Note: Themes ending in 43 are of 4:3 aspect ratio - the others are widescreen.

Rebuild your kernel image with:

# mkinitcpio -p [name of your kernel preset]

and reboot.