1.\" 2.\" Copyright (c) 1999 3.\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer as 11.\" the first lines of this file unmodified. 12.\" 2. Redistributions in binary form must reproduce the above copyright 13.\" notice, this list of conditions and the following disclaimer in the 14.\" documentation and/or other materials provided with the distribution. 15.\" 16.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 17.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 18.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 26.\" 27.\" $FreeBSD$ 28.\" 29.Dd January 15, 2006 30.Dt SPLASH 4 31.Os 32.Sh NAME 33.Nm splash 34.Nd splash screen / screen saver interface 35.Sh SYNOPSIS 36.Cd "device splash" 37.Sh DESCRIPTION 38The 39.Nm 40pseudo device driver adds support for the splash screen and screen 41savers to the kernel. 42This driver is required if the splash bitmap image is to be loaded or 43any screen saver is to be used. 44.Ss Splash screen 45You can load and display an arbitrary bitmap image file as a welcome banner 46on the screen when the system is about to start. 47This image will remain on the screen 48during kernel initialization process 49until the login prompt appears on the screen 50or until a screen saver is loaded and initialized. 51The image will also disappear if you hit any key, 52although this may not work immediately 53if the kernel is still probing devices. 54.Pp 55If you specify the 56.Fl c 57or 58.Fl v 59boot option when loading the kernel, the splash image will not appear. 60However, it 61is still loaded and can be used as a screen saver later: see below. 62.Pp 63In order to display the bitmap, the bitmap file itself and the 64matching splash image decoder module must be loaded by the boot loader. 65Currently the following decoder modules are available: 66.Pp 67.Bl -tag -width splash_decoder -compact 68.It Pa splash_bmp.ko 69W*ndows BMP file decoder. 70While the BMP file format allows images of various color depths, this 71decoder currently only handles 256 color bitmaps. 72Bitmaps of other color depths will not be displayed. 73.It Pa splash_pcx.ko 74ZSoft PCX decoder. 75This decoder currently only supports version 5 8-bpp single-plane 76images. 77.El 78.Pp 79The 80.Sx EXAMPLES 81section illustrates how to set up the splash screen. 82.Pp 83If the standard VGA video mode is used, 84the size of the bitmap must be 320x200 or less. 85If you enable the VESA mode support in the kernel, 86either by statically linking the VESA module or by loading the VESA module 87(see 88.Xr vga 4 ) , 89you can load bitmaps up to a resolution of 1024x768, depending on the VESA 90BIOS and the amount of video memory on the video card. 91.Ss Screen saver 92The screen saver will activate when the system is considered idle: i.e.\& 93when the user has not typed a key or moved the mouse for a specified period 94of time. 95As the screen saver is an optional module, 96it must be explicitly loaded into memory. 97Currently the following screen saver modules are available: 98.Pp 99.Bl -tag -width splash_module.ko -compact 100.It Pa blank_saver.ko 101This screen saver simply blanks the screen. 102.It Pa daemon_saver.ko 103Animated 104.Bx 105Daemon screen saver. 106.It Pa fade_saver.ko 107The screen will gradually fade away. 108.It Pa fire_saver.ko 109A fire which becomes higher as load increases. 110.It Pa green_saver.ko 111If the monitor supports power saving mode, it will be turned off. 112.It Pa logo_saver.ko 113Animated graphical 114.Bx 115Daemon. 116.It Pa rain_saver.ko 117Draws a shower on the screen. 118.It Pa snake_saver.ko 119Draws a snake of string. 120.It Pa star_saver.ko 121Twinkling stars. 122.It Pa warp_saver.ko 123Streaking stars. 124.El 125.Pp 126Screen saver modules can be loaded using 127.Xr kldload 8 : 128.Pp 129.Dl kldload logo_saver 130.Pp 131The timeout value in seconds can be specified as follows: 132.Pp 133.Dl vidcontrol -t N 134.Pp 135Alternatively, you can set the 136.Ar saver 137variable in the 138.Pa /etc/rc.conf 139to the screen saver of your choice and 140the timeout value to the 141.Ar blanktime 142variable so that the screen saver is automatically loaded 143and the timeout value is set when the system starts. 144.Pp 145The screen saver may be instantly activated by hitting the 146.Ar saver 147key: the defaults are 148.Em Shift-Pause 149on the AT enhanced keyboard and 150.Em Shift-Ctrl-NumLock/Pause 151on the AT 84 keyboard. 152You can change the 153.Ar saver 154key by modifying the keymap 155(see 156.Xr kbdcontrol 1 , 157.Xr keymap 5 ) , 158and assign the 159.Ar saver 160function to a key of your preference. 161.Pp 162The screen saver will not run if the screen is not in text mode. 163.Ss Splash screen as a screen saver 164If you load a splash image but do not load a screen saver, 165you can continue using the splash module as a screen saver. 166The screen blanking interval can be specified as described in the 167.Sx Screen saver 168section above. 169.\".Sh DRIVER CONFIGURATION 170.Sh FILES 171.Bl -tag -width /boot/kernel/splash_xxxx.ko -compact 172.It Pa /boot/defaults/loader.conf 173boot loader configuration defaults 174.It Pa /etc/rc.conf 175system configuration information 176.It Pa /boot/kernel/splash_*.ko 177splash image decoder modules 178.It Pa /boot/kernel/*_saver.ko 179screen saver modules 180.It Pa /boot/kernel/vesa.ko 181the VESA support module 182.El 183.Sh EXAMPLES 184In order to load the splash screen or the screen saver, you must 185have the following line in the kernel configuration file. 186.Pp 187.Dl device splash 188.Pp 189Next, edit 190.Pa /boot/loader.conf 191(see 192.Xr loader.conf 5 ) 193and include the following lines: 194.Bd -literal -offset indent 195splash_bmp_load="YES" 196bitmap_load="YES" 197bitmap_name="/boot/chuck.bmp" 198.Ed 199.Pp 200In the above example, the file 201.Pa /boot/chuck.bmp 202is loaded. 203In the following example, the VESA module 204is loaded so that a bitmap file which cannot be displayed in standard 205VGA modes may be shown using one of the VESA video modes. 206.Bd -literal -offset indent 207splash_pcx_load="YES" 208vesa_load="YES" 209bitmap_load="YES" 210bitmap_name="/boot/chuck.pcx" 211.Ed 212.Pp 213If the VESA support is statically linked to the kernel, it is not 214necessary to load the VESA module. 215Just load the bitmap file and the splash decoder module as in the 216first example above. 217.\".Sh DIAGNOSTICS 218.Sh CAVEATS 219Both the splash screen and the screen saver work with 220.Xr syscons 4 221only. 222.Sh SEE ALSO 223.Xr vidcontrol 1 , 224.Xr syscons 4 , 225.Xr vga 4 , 226.Xr loader.conf 5 , 227.Xr rc.conf 5 , 228.Xr kldload 8 , 229.Xr kldunload 8 230.Sh HISTORY 231The 232.Nm 233driver first appeared in 234.Fx 3.1 . 235.Sh AUTHORS 236.An -nosplit 237The 238.Nm 239driver and this manual page were written by 240.An Kazutaka Yokota Aq yokota@FreeBSD.org . 241The 242.Pa splash_bmp 243module was written by 244.An Michael Smith Aq msmith@FreeBSD.org 245and 246.An Kazutaka Yokota . 247The 248.Pa splash_pcx 249module was written by 250.An Dag-Erling Sm\(/orgrav Aq des@FreeBSD.org 251based on the 252.Pa splash_bmp 253code. 254.Sh BUGS 255If you load a screen saver while another screen saver has already 256been loaded, the first screen saver will not be automatically unloaded 257and will remain in memory, wasting kernel memory space. 258