Difference between revisions of "Splashy"

From ArchWiki
Jump to: navigation, search
m (Installation)
(archive after 2 weeks: deprecated, not packaged)
 
(50 intermediate revisions by 19 users not shown)
Line 1: Line 1:
[[Category: Boot process (English)]]
 
[[Category: Eye candy (English)]]
 
{{i18n|Splashy}}
 
{{Out of date}}
 
  
==Introduction==
+
#redirect [[ArchWiki:Archive]]
[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].
+
[[Category:Archive]]
 
 
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).
 
 
 
==Installation==
 
 
 
# 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]].
 
 
 
==Configuration==
 
=== 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.
 
 
 
# Follow the instructions on the [[Uvesafb]] page to install and configure.
 
# 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>
 
 
 
=== Default Framebuffer ===
 
You can also use the default kernel framebuffer if your hardware does not support Uvesafb.
 
 
 
# [http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers Find the kernel framebuffer mode number closest as possible to your monitor].
 
# 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>
 
 
 
=== 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 <code>quiet splash</code> options in your grub config file.
 
 
 
=== Other Configuration Files ===
 
====/etc/rc.conf====
 
Add <code>SPLASH="splashy"</code> 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.)
 
'''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>
 
 
 
===Upgrading===
 
Don't forget to rebuild the initramfs image after upgrading Splashy.
 
 
 
===Themes===
 
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>
 
After you set your theme (and any time you change your theme) you will need to again run
 
# mkinitcpio -p kernel26
 
 
 
==Known Problems==
 
{{Poor writing}}
 
#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==
 
* http://splashy.alioth.debian.org
 
* http://www.directfb.org
 

Latest revision as of 12:13, 19 August 2018

Redirect to: