Интерактивная система просмотра системных руководств (man-ов)
>> screensaver (4) ( FreeBSD man: Специальные файлы /dev/* )
- splash screen / screen saver interface
pseudo device driver adds support for the splash screen and screen
savers to the kernel.
This driver is required if the splash bitmap image is to be loaded or
any screen saver is to be used.
You can load and display an arbitrary bitmap image file as a welcome banner
on the screen when the system is about to start.
This image will remain on the screen
during kernel initialization process
until the login prompt appears on the screen
or until a screen saver is loaded and initialized.
The image will also disappear if you hit any key,
although this may not work immediately
if the kernel is still probing devices.
If you specify the
boot option when loading the kernel, the splash image will not appear.
is still loaded and can be used as a screen saver later: see below.
In order to display the bitmap, the bitmap file itself and the
matching splash image decoder module must be loaded by the boot loader.
Currently the following decoder modules are available:
W*ndows BMP file decoder.
While the BMP file format allows images of various color depths, this
decoder currently only handles 256 color bitmaps.
Bitmaps of other color depths will not be displayed.
ZSoft PCX decoder.
This decoder currently only supports version 5 8-bpp single-plane
section illustrates how to set up the splash screen.
If the standard VGA video mode is used,
the size of the bitmap must be 320x200 or less.
If you enable the VESA mode support in the kernel,
either by statically linking the VESA module or by loading the VESA module
you can load bitmaps up to a resolution of 1024x768, depending on the VESA
BIOS and the amount of video memory on the video card.
The screen saver will activate when the system is considered idle: i.e.
when the user has not typed a key or moved the mouse for a specified period
As the screen saver is an optional module,
it must be explicitly loaded into memory.
Currently the following screen saver modules are available:
This screen saver simply blanks the screen.
BSD Daemon screen saver.
The screen will gradually fade away.
A fire which becomes higher as load increases.
If the monitor supports power saving mode, it will be turned off.
Draws a shower on the screen.
Draws a snake of string.
Screen saver modules can be loaded using
The timeout value in seconds can be specified as follows:
vidcontrol -t N
Alternatively, you can set the
variable in the
to the screen saver of your choice and
the timeout value to the
variable so that the screen saver is automatically loaded
and the timeout value is set when the system starts.
The screen saver may be instantly activated by hitting the
key: the defaults are
on the AT enhanced keyboard and
on the AT 84 keyboard.
You can change the
key by modifying the keymap
and assign the
function to a key of your preference.
The screen saver will not run if the screen is not in text mode.
Splash screen as a screen saver
If you load a splash image but do not load a screen saver,
you can continue using the splash module as a screen saver.
The screen blanking interval can be specified as described in the
Sx Screen saver
boot loader configuration defaults
system configuration information
splash image decoder modules
screen saver modules
the VESA support module
In order to load the splash screen or the screen saver, you must
have the following line in the kernel configuration file.
and include the following lines:
In the above example, the file
In the following example, the VESA module
is loaded so that a bitmap file which cannot be displayed in standard
VGA modes may be shown using one of the VESA video modes.
driver and this manual page were written by
An Kazutaka Yokota Aq yokota@FreeBSD.org .
module was written by
An Michael Smith Aq msmith@FreeBSD.org
An Kazutaka Yokota .
module was written by
An Dag-Erling Sm/orgrav Aq des@FreeBSD.org
based on the
If you load a screen saver while another screen saver has already
been loaded, the first screen saver will not be automatically unloaded
and will remain in memory, wasting kernel memory space.