Date: Tue, 15 Jun 1999 22:48:57 +0100 From: Mark Ovens <markov@globalnet.co.uk> To: Andrew Boothman <andrew@cream.org> Cc: "Jason L. Schwab" <jschwab@royal.net>, questions@freebsd.org Subject: Re: pseudo-device splash Message-ID: <19990615224856.B254@marder-1> In-Reply-To: <XFMail.990615223146.andrew@cream.org>; from Andrew Boothman on Tue, Jun 15, 1999 at 10:31:46PM %2B0100 References: <199906131731.NAA21104@pop03.globecomm.net> <XFMail.990615223146.andrew@cream.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 15, 1999 at 10:31:46PM +0100, Andrew Boothman wrote: > Some information on this is available on http://advocacy.freebsd.org > > Have a look around and try and find their list of available splash screens, > because that page contains information on how to get them working. > http://www.baldwin.cx/splash/ although the server appears to be down at the moment so I've included the instructions from the site which I d/l a while ago (in 3.1 days, but they should be valid for 3.2) ------- begin included file sc_update.txt ------- Last update: 4 Feb. 1999. Kazutaka YOKOTA yokota@FreeBSD.ORG ----------------------------------------------------------------------- I) Syscons Update II) Splash Screen III) Splash Screen/Screen Saver FAQ ----------------------------------------------------------------------- I) Syscons Update Major update for the console driver started on 10 January. New keyboard and video card drivers have been introduced (This is just the begining. There will be more updates to follow in the next few months.) Because of these changes, you must update several things in your -current system. 1. You are required to update your kernel configuration file. If you are using syscons, controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? tty pseudo-device splash Note that `splash' is required if you intend to use screen savers or splash screen. !!IMPORTANT!! -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Due to sloppy programming of mine, the pseudo-device splash is ALWAYS needed for the syscons driver at the moment. The problem will be fixed soon. (12 Jan. 1999) -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Fixed. You don't need the splash device if you don't use screen savers and splash screen. (13 Jan. 1999) -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ If you are pcvt user, controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vt0 at isa? tty 2. The following options for syscons are replaced by new ones. SC_ALT_SEQACCESS-> VGA_ALT_SEQACCESS SLOW_VGA -> VGA_SLOW_IOACCESS 3. The following flags for syscons are no longer available. 0x08 Force detection of keyboard. 0x10 Old-style (XT) keyboard support. 0x20 Don't reset keyboard. Use corresponding new flags for atkbd instead. 0x01 Don't install the keyboard driver if no keyboard is found, else we always assume a keyboard. 0x02 Don't reset keyboard. 0x04 XT keyboard support. 4. You must recompile screen saver modules and the vesa module in /sys/modules, as well as kbdcontrol and vidcontrol in /usr/src/usr.sbin. If you regularly do `make world', you will be in good shape. If you don't do it often, this may be a good opportunity. II) Splash Screen A splash screen module has been added. See /sys/modules/splash. This version has rather limited capabilities: it can handle W*ndows 256 color BMP file only (other color depth probably won't work); the size of the image must be 320x200 or less if the standard VGA video mode is used. If you enable the VESA mode support in the kernel, you can load as large bitmap as 1024x768, depending on the VESA BIOS and the amount of video memory on your video card. In order to see splash image when your kernel loads, do the following: Make sure the following line is added to your kernel configuration file and rebuild a new kernel. pseudo-device splash Copy your favorite W*ndows BMP file to somewhere the boot loader can see. When the boot loader starts, load kernel, splash image file and the splash image decoder module as follows. load kernel load -t splash_image_data _your_BMP_file_ load splash_bmp boot "-t splash_image_data" is extremely important as the the decoder will look for this tag for the bitmap data. If you want to enable the VESA support in the kernel, you should either 1) write the following options in your kernel configuration file when you generate a new kernel. options "VM86" options VESA 2) Or, you write options "VM86" in your kernel configration file when you build a new kernel and load the VESA module when you boot the kernel. In this case you load the modules as follows: load kernel load -t splash_image_data _your_BMP_file_ load vesa load splash_bmp boot After the boot command is run, you should see the image on your screen as soon as the kernel loads. If you specify -c or -v options to the boot command, the splash image won't appear. (But is loaded and can be used as a screen saver later; see below.) Note also that the splash screen won't be available if you use pcvt driver. You must be using syscons. The splash screen will go away if you hit any key (this may not work immediately if the kernel is still probing devices), or you load a screen saver. If you load the splash image decoder module but don't load a screen saver, you can continue using the splash module as a screen saver. Specify timeout value by running vidcontrol. vidcontrol -t timeout Then, the splash screen image will come back after the specified time. (You cannot use the regular screen saver as a splash screen, though.) There is a little-known feature of kbdcontrol which you might be interested in. You can define the `saver' key in the keymap. You press the `saver' key, then the current screen saver (or the splash screen if no screen saver is loaded) will immediately pops up. For example, if you want to assign the `saver' key to the Pause key, whose key number is 104, find the line for the4 key 104 and change it to 104 saver saver saver saver saver saver saver saver O Then reload the keymap. kbdcontrol -l mykeymap The `saver' key has no effect in the X session. III) Splash Screen/Screen Saver FAQ -------------------------------------- Q. Do I need the pseudo-device splash in order to use `blank' or `green' savers? A. Yes. The splash device is required for ANY screen savers and splash screen. -------------------------------------- Q. I loaded kernel, a bitmap file and the splash_bmp module as instructed, but got the following error. What gives? Preloaded elf module "splash_bmp.ko" at XXXXXX. module_register_init: module_register(splash_bmp, YYYYYY, 0) error 19 A. The current version of splash_bmp.ko is very limited. The color depth must be 8 bpp (256 color), and the size must be 320x200 or smaller if the VESA support is not included in the kernel. If your BMP file doesn't satisfy these conditions, splash_bmp.ko will return error 19 (ENODEV). If the VESA support is compiled in the kernel or the VESA modules is preloaded by the boot loader, larger bitmap may be used. Another possible cause of error is that the video driver finds it unable to switch video modes on your video card and splash_bmp.ko is failing. Run the `dmesg' command and see if it shows something like "...video mode switching is only partially supported..." among boot messages. There is no fix for this at the moment. Sorry. -------------------------------------- Q. Can we have splash screen and screen savers on the Alpha architecture? A. Not at the moment. -------------------------------------- ---- End of File ---- -- FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://www.users.globalnet.co.uk/~markov _______________________________________________________________ Mark Ovens, CNC Apps Engineer, Radan Computational Ltd. Bath UK CAD/CAM solutions for Sheetmetal Working Industry mailto:marko@uk.radan.com http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990615224856.B254>