The Gentoo Framebuffer, Bootsplash & Grubsplash How-To

[Narada]

The Gentoo Framebuffer, Bootsplash & Grubsplash How-To
(now updated for 2.6.x kernel tree)

Post documentation, tips and tricks on this thread.
Post questions, problems and answers on the support thread.
Post topic related gentoo specific bugs on the bugs site.

Translation or Reproduction of Guide

If you want to translate or reproduce this guide there is no longer any need to seek permission as long as you follow the standard practices given below.

• Acknowledge the original author and link to his profile
• Acknowledge the original guide and link to it
• Mention that only this guide will be updated by the original author
• Kindly send me a link via PM to any translation or reproduction once completed so I can link to it

Latest Screenshot

Self Portrait (Kernel 2.6.7) (image / default config file)

2.4.X Patches

• 2.4.20 | Origin
• 2.4.21 | Origin
• 2.4.22 | Origin
• 2.4.24 | Origin
• 2.4.25 | Origin
• 2.4.26 | Origin - New!

2.6.X Patches

• 2.6.0 | Origin
• 2.6.1 | Origin
• 2.6.2 | Origin
• 2.6.3 | Origin
• 2.6.4 | Origin
• 2.6.5 | Origin
• 2.6.6 | Origin
• 2.6.7 | Origin
• 2.6.8.1 | Origin - New!

The author acknowledges and thanks the supplier(s) of all the above patches.

Objectives

• High resolution framebuffer (example)
• High resolution bootsplash image (example)
• Smaller fonts on framebuffer for greater area (example)
• Greater choice of fonts for varied appearance
• Personalising your bootsplash theme (example)
• Taking screenshots of your framebuffer and bootsplash
• Using multimedia apps and graphical browser on framebuffer
• Personalising your grub splash screen image
• Extending framebuffer and bootsplash to all 12 virtual terminals

Benefits

• Higher resolution
• Configurable and pretty appearance
• Multimedia and graphical browser capability on VTs
• Framebuffer will work on any kernel version

Drawbacks

• Slow scrolling of text output on VTs
• Reduced or zero scroll back buffer

High resolution framebuffer & bootsplash!

1. Update portage tree.

   Code: Select all

   emerge sync

2. Emerge media-gfx/bootsplash (graphical backgrounds for frame buffer consoles).

   Code: Select all

   emerge bootsplash

   Overwrite your old bootsplash configuration files.

   Code: Select all

   etc-update

3. Check that the symbolic link /usr/src/linux is pointing to the kernel of your choice.

   Code: Select all

   ls -l /usr/src/

   Some kernels such as gentoo-sources, gaming-sources and xfs-sources already have the bootsplash patch built in. Check whether your kernel supplies bootsplash and if it does not have it then patch the kernel as below.

   Code: Select all

   ebuild /var/db/pkg/media-gfx/bootsplash-0.6-r2/bootsplash-0.6-r9.ebuild config

   Or you can run the following command which takes an additional argument and executes the line above.

   Code: Select all

   bootsplash_patch

4. Enter the kernel configuration.

   Code: Select all

   cd /usr/src/linux
   make menuconfig

   For all kernel trees build these options directly into your kernel. Do NOT make them modules and do not enable nvidia or ATi specific options.
   
   For 2.6.x kernel tree enable the following options.

   Code: Select all

   Code maturity level options  --->
       [*] Prompt for development and/or incomplete code/drivers
   Processor type and features  --->
       [*] MTRR (Memory Type Range Register) support
   Device Drivers  --->
       Block devices  --->
           <*> Loopback device support
           <*> RAM disk support
           (4096) Default RAM disk size
           [*]   Initial RAM disk (initrd) support
   Graphics support  --->
       [*] Support for frame buffer devices
       [*]   VESA VGA graphics support
       Console display driver support  --->
           [*]   Video mode selection support
           <*> Framebuffer Console support
       Bootsplash configuration  --->
           [*] Bootup splash screen
   

   For 2.4.x kernel tree enable the following options.

   Code: Select all

   Code maturity level options  --->
       [*] Prompt for development and/or incomplete code/drivers
   Processor type and features  --->
       [*] MTRR (Memory Type Range Register) support
   Block Devices ->
       [*] Loopback device support
       [*] RAM disk support
       (4096)   Default RAM disk size
       [*] Initial RAM disk (initrd) support
   Console Drivers ->
       [*] VGA text console
       [*] Video mode selection support
   Console Drivers -> Frame-buffer support ->
       [*] Support for frame buffer devices
       [*] VESA VGA graphics console
       [*] Use splash screen instead of boot logo
   

   For any kernel do NOT enable the following options or else you risk bootsplash not working or framebuffer corruption when switching VTs.

   Code: Select all

   Device Drivers  --->
       Graphics support  --->
               < >   nVidia Riva support  (do not enable!)
           Logo configuration  --->
               [ ] Bootup logo  (do not enable!)
   

   If you have problems later disable the following option in kernel

   Code: Select all

   Device Drivers  --->
       Character devices  --->
           < > /dev/agpgart (AGP Support)

   And add the following line to your /etc/X11/XF86Config[-4] file.

   Code: Select all

   Option          "NvAGP"         "1"

5. Compile your kernel as below for 2.6.x kernel.

   Code: Select all

   make

   Compile your kernel as below for 2.4.x kernel.

   Code: Select all

   make dep && make clean bzImage modules modules_install

   Install your kernel as below but do NOT unmount /boot and do NOT reboot until asked to later.

   Code: Select all

   mount /boot
   mv /boot/bzImage /boot/bzImage.old
   cp /usr/src/linux/arch/i386/boot/bzImage /boot/

   If you get errors during kernel compilation or missing options during configuration do as below.

   Code: Select all

   cd /usr/src/linux/
   mv .config ~/kernel.config
   make mrproper
   mv ~/kernel.config .config
   make oldconfig
   make menuconfig
   

6. Assuming /boot is mounted set an image to appear during the boot process.

   Code: Select all

   /sbin/splash -s -f /etc/bootsplash/default/config/bootsplash-1280x1024.cfg >> /boot/initrd-1280x1024

   Or you can copy an already exisiting initrd image that is provided with the bootsplash package.

   Code: Select all

   cp /usr/share/bootsplash/initrd-1280x1024 /boot/

7. Edit your /boot/grub/grub.conf file. The example below has been provided for your convenience. Here are the meanings of the various parameters.
   
   • video= goes on kernel line and controls display options such as ywrap and mtrr which speed up framebuffer scrolling
   • vga= goes on kernel line and controls the resolution and colour depth of framebuffer
   • splash= goes on kernel line and takes either 'silent' or 'verbose' but silent boots may not work
   • initrd= goes on a new line after kernel line and loads an image during the booting process.

   Code: Select all

   default 0
   timeout 10
   splashimage=(hd0,0)/boot/grub/splash.xpm.gz
   
   # With both framebuffer and bootsplash
   title=Gentoo GNU/Linux 1.4 (+fb +splash)
   root=(hd0,0)
   kernel=(hd0,0)/boot/bzImage root=/dev/hda3 video=vesafb:ywrap,mtrr vga=0x31A
   initrd=/boot/initrd-1280x1024
   
   # With framebuffer but without bootsplash
   title=Gentoo GNU/Linux 1.4 (+fb -splash)
   root=(hd0,0)
   kernel=(hd0,0)/boot/bzImage root=/dev/hda3 video=vesafb:ywrap,mtrr vga=0x31A
   
   # Without both framebuffer and bootsplash
   title=Gentoo GNU/Linux 1.4 (-fb -splash)
   root=(hd0,0)
   kernel=(hd0,0)/boot/bzImage root=/dev/hda3

   Here is a lilo.conf example configuration courtesy of ophidia.

   Code: Select all

   image="/boot/bzImage" 
   vga=0x31A 
   root="/dev/hdb2" 
   label="2.4.20-r4" 
   read-only # read-only for checking 
   append="hdc=ide-scsi video=vesafb:ywrap,mtrr" 
   initrd=/boot/initrd-1280x1024

   Note that in the above grub and lilo configuration examples the keyword 'vesafb' is applicable to 2.6.x kernels. For 2.4.x kernels it should be changed to 'vesa'.
   
   Here is a chart of kernel mode numbers for the 'vga=' boot parameter.

   Code: Select all

       | 640x480  800x600  1024x768 1280x1024
   ----+-------------------------------------
   256 |  0x301    0x303    0x305    0x307   
   32k |  0x310    0x313    0x316    0x319   
   64k |  0x311    0x314    0x317    0x31A   
   16M |  0x312    0x315    0x318    0x31B

   If you want to find ALL video modes for use with the framebuffer look at this forum post for further information on how to find it yourself.
   
   Look at the following reference files if you need more detailed information.
   

   Code: Select all

   /usr/share/bootsplash/grub.conf.sample
   /usr/src/linux/Documentation/fb/vesafb.txt
   /usr/src/linux/Documentation/svga.txt

8. Add bootsplash to the default run level so that it starts on every boot.

   Code: Select all

   rc-update add bootsplash default

9. Reboot and bask in the glory of bootplash wonder. To remind yourself of what kernel parameters you booted with do as below.

   Code: Select all

   cat /proc/cmdline

Setting framebuffer without bootsplash!

• To have a framebuffer only without bootsplash for greater area remove bootsplash from your default run level and reboot.

  Code: Select all

  rc-update del bootsplash default

• Remove or comment out this line from your chosen menu entry in grub.conf.

  Code: Select all

  initrd=/boot/initrd-1280x1024

Smaller fonts on framebuffer for greater area!

• Open /etc/rc.conf and change the following variable.

  Code: Select all

  CONSOLEFONT="default8x9"

• To see what other fonts are available for use look in the following location and add the name without the extension to /etc/rc.conf.

  Code: Select all

  /usr/share/consolefonts

Extending consolefont, framebuffer and bootsplash to all 12 virtual terminals!

• Open /etc/init.d/consolefont and change all instances of

  Code: Select all

  for x in 1 2 3 4 5 6 7 8 9 10

  to

  Code: Select all

  for x in `seq 1 12`

• Open /etc/conf.d/bootsplash.conf and change the following variable as below.

  Code: Select all

  BOOTSPLASH_TTYS="0 1 2 3 4 5 7 8 9 10 11"

• For the above changes to take effect you can either reboot or restart the above init.d scripts as below. Voila!

  Code: Select all

  /etc/init.d/consolefont restart
  /etc/init.d/bootsplash restart

Personalising your bootsplash theme!

• Create your own directory structure called 'personal'.

  Code: Select all

  mkdir -p /etc/bootsplash/personal/images/
  cp -r /etc/bootsplash/default/config /etc/bootsplash/personal/

• Change the symbolic link for the default theme.

  Code: Select all

  rm /etc/bootsplash/default
  ln -s /etc/bootsplash/personal /etc/bootsplash/default

• Open /etc/conf.d/bootsplash.conf and change as below.

  Code: Select all

  BOOTSPLASH_THEME=personal

• Copy images of your choice and of correct resolution and depth into /etc/bootsplash/personal/images/. Make sure images have a resolution of 96x96 and not 300x300. Note that this is not image size but rather 'pixels per inch'. For more information look here.
• Open /etc/bootsplash/personal/config/bootsplash-1280x1024.cfg and change paths below to point to your images.

  Code: Select all

  jpeg=/etc/bootsplash/gentoo/images/bootsplash-1280x1024.jpg
  silentjpeg=/etc/bootsplash/gentoo/images/silent-1280x1024.jpg

• To have your image appear during boot add it to /boot otherwise omit this step.

  Code: Select all

  mount /boot
  /sbin/splash -s -f /etc/bootsplash/default/config/bootsplash-1280x1024.cfg > /boot/initrd-1280x1024

• Reboot, test and post feedback.

Taking screenshots!

• To use fbgrab emerge it as root and execute it as normal user on terminal 1.

  Code: Select all

  emerge fbgrab
  fbgrab ~/console.png

Personalising your grub splash image!

• To change your grub splash image create an image then move it to /boot/grub. As root do the following.

  Code: Select all

  emerge gimp
  wget http://dhruba.codewordt.co.uk/files/grub-image.scm -P ~
  mv ~/grub-image.scm /usr/share/gimp/1.2/scripts/

• Start gimp and open an image of your choice. Right click on the image, select File, Grub Boot Image and save in your home directory. A sample image is provided in instructions below for you to try. Other images can be found here which is a very useful resource.

  Code: Select all

  mount /boot
  wget http://linux.tkdack.com/downloads/grub/powered-by.xpm.gz -P ~
  mv ~powered-by.xpm.gz /boot/grub/

• Modify /boot/grub/grub.conf to point to the new image.

  Code: Select all

  splashimage=(hd0,0)/boot/grub/gentoo-boot.xpm.gz

• To create images of the correct kind either follow the command line instructions at linux.tkdack.com duplicated below for convenience or use the gimp plugin.

  Code: Select all

  convert -size 800x600 file.jpg -resize 640x480 -colors 15 -profile '*' file.xpm

  Code: Select all

  gzip file.xpm

Feedback: Since this thread is now split into two here's how to decide which thread to post on. If you are asking questions about problems or are helping another user with problems then post on the support thread. Remember to provide kernel name and version, contents of your grub.conf file and make, model and driver version of your graphics card. Everthing else can be posted in this thread including comments on improving this guide or correcting mistakes which are both welcome! Remember that if you have general problems unrelated to this guide then file bugs immediately so that hacks are no longer necessary and that problems are resolved officially for future users.

Latest news: As you can tell by the number of times that this post has been edited the guide is undergoing continual overhaul as a result of feedback from users. It is now much more concise and has recently been expanded to fit new content. Look here for people who have it working: quikchaos, basquiat, mojo, danb, maw, Cappy!

Trivia: For trivia first emerge aalib, svgalib and DirectFB. Mplayer on framebuffer: Try 'emerge mplayer' and then 'mplayer -vo svga <filename>'. Have you managed to get mplayer working under framebuffer? If so, post details! Graphical browser on framebuffer: (1) emerge links (2) chown root.root /usr/bin/links2 (3) chmod +s /usr/bin/links2 (4) links2 -g www.gentoo.org -driver directfb. Other drivers are X, vesa, svgalib and fb. Try them all and see what works best for you. How did links go for you?

Still to come: Separate sections for framebuffer, bootsplash and grubsplash (done!); Extending to all 12 VTs (done!); Using your own themes with bootsplash (done!); Smaller fonts for greater area (done!); Binding a key for taking framebuffer screenshots; Modifying console fonts! Bear with me - hugely busy atm!

Acknowledgements: devs: TaD, LiveWire; #gentoo: r2d2, Malketh, antifa, kote, Hayl, cybbe; beejay; forums: quikchaos, aardvark, allucid, tkdack; anubis2002; ophidia; other: HandyAndE, Tyrant.

[quikchaos]

Thanks for the updated How-To. I also think it was in need.

I just wanted to say that the 2.4.20-gaming-r2 kernel already has the patch applied also.

Here is a link to my current bootsplash.
http://forums.gentoo.org/viewtopic.php?p=256931#256931

[linde002]

Thank you so much man, i have been looking everywhere for this thing ever since i´ve installed gentoo on my laptop with the 1,4 rc4 livecd

-Robert

[aardvark]

Hmmm , you don't need the "nVidia riva support" in your kernel even if you have a nvidia graphicscard. Actually, when you use the closed source nvidia-drivers, you should only use the VESA fb driver, or else you might get into trouble.

[Yinchie]

Wow thanks for this excellent guide.
I got it working and it loooooooooooooooks sooo goood !

[Yinchie]

It works good for me.
Ermm I already said that

Code: Select all

yinchie@celeronator (~) (pts/0) 
$ cat /proc/splash 
Splash screen v3.0.7-2003/03/10 (0x07, 1024x768): on

2 result screenshots:
http://www.relaxz.net/archives/vc-fb.png
http://www.relaxz.net/archives/vc-fb-2.png

I am using gentoo-sources-r3

My grub.conf

Code: Select all

default 0
timeout 15
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=Gentoo GNU/Linux 1.4 [gentoo-sources-2.4.20-r3]
root (hd0,0)
kernel (hd0,0)/boot/bzImage-21april root=/dev/hda2 hdc=ide-scsi vga=0x317 video=vesa:1024x768@72
initrd=/boot/initrd-1024x768

title=Gentoo Linux Old [backup working kernel]
root (hd0,0)
kernel (hd0,0)/boot/bzImage-16april root=/dev/hda2

[BWW]

I got mine to work, using the gentoo-sources-2.4.20-r2 kernel and patching and recompiling the kernel per your instructions. Like some others, after rebooting and doing "cat /proc/splash", splash was nowhere to be found. I had to first edit grub.conf by adding just the "vga=0x317 video=vesa:1280x1024@72" line as shown below in my grub.conf:

default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=Gentoo Linux
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/hda3 hdd=ide-scsi vga=0x317 video=vesa:1280x1024@72

I left off the "initrd=/initrd-1280x1024" line as grub would not boot yet with it. After rebooting again, doing "cat /proc/splash" finally found splash, and I was able to follow the rest of your process, editing grub.conf again (be sure to mount /boot first!) to add the "initrd=/initrd-1280x1024" line on the end and *hoowah* I had the splash screens. I just installed the newest Gentoo Linux 1.4_rc4 over the weekend, after playing around with some other distros for a few months, and I believe I'll just hang on to this one. Congrats on a fine tutorial, it really polishes up Gentoo.

[irasnyd]

I got mine to work, using the gentoo-sources-2.4.20-r2 kernel and patching and recompiling the kernel per your instructions. Like some others, after rebooting and doing "cat /proc/splash", splash was nowhere to be found. I had to first edit grub.conf by adding just the "vga=0x317 video=vesa:1280x1024@72" line as shown below in my grub.conf:

default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=Gentoo Linux
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/hda3 hdd=ide-scsi vga=0x317 video=vesa:1280x1024@72

I left off the "initrd=/initrd-1280x1024" line as grub would not boot yet with it. After rebooting again, doing "cat /proc/splash" finally found splash, and I was able to follow the rest of your process, editing grub.conf again (be sure to mount /boot first!) to add the "initrd=/initrd-1280x1024" line on the end and *hoowah* I had the splash screens. I just installed the newest Gentoo Linux 1.4_rc4 over the weekend, after playing around with some other distros for a few months, and I believe I'll just hang on to this one. Congrats on a fine tutorial, it really polishes up Gentoo.

This also allowed my /proc/splash to work. Thanks!!!!!

My Boot Line:

Code: Select all

title=Gentoo Linux FB
root (hd0,2)
kernel (hd0,2)/boot/bzImage root=/dev/hda7 vga=0x317 video=vesa:1024x768@72

[basquiat]

Another successfull report can be filed...

It's working like a charm, I put a screenshot on http://www.basquiat.de/gallery/album08/aab.

I'm using a Sony VAIO GRX notebook with an integrated ATI 7500 Radeon Mobility card. Kernelversion is 2.4.20-xfs-r3, grub's menu.lst looks like this:

Code: Select all

title=Gentoo 1.4 GNU/Linux 2.4.20-xfs-r3
root (hd0,5)
kernel /boot/bzImage root=/dev/hda8 hdc=ide-scsi vga=0x31A video=vesa:1280x1024@60
initrd=/boot/initrd-1280x1024

So thanks for this great HOW-TO.

Regards,
Jens

--
"If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system."
(By Linus Torvalds)

[mojo]

i got it work with the wolk-sources. i am using the 2.4.20-rc2 version (the newer version won't compile on my machine).
when i applied the bootsplash-3.0.7-2.4.20-vanilla.diff the second and third hunk in /usr/src/linux/drivers/video/Config.in was not updated correctly, or better: the automatical patch failed when it updates this parts. but it is no problem to edit the bootsplash-3.0.7-2.4.20-vanilla.diff and the Config.in and patch the Config.in by comparing the two files manually. then you can search the parts that weren't modified automatically in the Config.in and update them by yourself. Then you can follow the instructions that were given in the beginning.

This is my grub.conf:

default 0
timeout 10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=Gentoo Linux
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/hda6 vga=0x317 video=mtrr,vesa:1024x768@72
initrd=/boot/initrd-1024x768


when you use vga=0x318 it won't work (for me maybe), because you will see the wolk-sources logo in the beginning not the bootsplash screen (what makes me wonder because it wasn't compiled in (so maybe it is standard and activated).
I get this also sometimes when i use vga=0x317 but when it exports the bootsplash to other consoles the bootsplash got activated and the screen changed to my favorite screen .

i dunno why it behaves this way but well it works

[psiXaos]

Coool... My windozer work-pals just amazed with that

[basquiat]

Yea, there is if you are using bootsplash version .5 or greater I just noticed that version .6 is out....will have to see if the progress bar works now

Apparently not, as I tried 0.6 with "splash=silent" and the Gentoo "Silent Splashscreen" showed up, but the area where the bar should progress stayed blank during the whole boot process, not showing any changes. Also all other consoles seem to be "blocked", not showing the normal splash screen after bootup, but the silent one, without any prompt.

Regards,
basquiat

--
<@Logan> I spent a minute looking at my own code by accident.
<@Logan> I was thinking "What the hell is this guy doing?"
-- IRC Quote Database

[allucid]

works fine for me with ck6. and it does not work with any 2.5.x kernels. if you can patch the kernel successfully, than chances are it works with that kernel. the only kernel's i can verify that it does _not_ work with are WOLK and 2.5.x kernels.

[allucid]

Problems: Problems with silent splash screen and progress bar? Read on: I've just spoken to LiveWire (dev) on #gentoo and learnt that silent splash tends not to work with kernels based on ck. Wolk-sources was recommended instead. Allucid would be an exception to both pieces of advice! Also, the progress bar on the silent splash screen won't yet work with Gentoo since it uses the init system and the gentoo scripts are not suited for this feature as yet. I guess we have to give it time.

hehe. to clarify bootsplash 0.5 does not work with linux-2.4.20-wolk4.0s-rc4 and does work with ck4 and ck6. i have not tried bootsplash 0.6 yet and i have never used silent splash (and never will ) so i can't comment on that.

[allucid]

Code: Select all

 *
 * Patching the kernel in /usr/src/linux ...
 *
patching file drivers/char/console.c
Hunk #1 succeeded at 3025 (offset 18 lines).
patching file drivers/char/keyboard.c
Hunk #1 succeeded at 262 with fuzz 2 (offset 23 lines).
patching file drivers/char/n_tty.c
patching file drivers/video/Config.in
Hunk #1 succeeded at 338 (offset 116 lines).
Hunk #2 FAILED at 456.
Hunk #3 FAILED at 475.
2 out of 3 hunks FAILED -- saving rejects to file drivers/video/Config.in.rej
patching file drivers/video/Makefile
Hunk #2 succeeded at 152 (offset 5 lines).
patching file drivers/video/fbcon-jpegdec.c
patching file drivers/video/fbcon-jpegdec.h
patching file drivers/video/fbcon-splash.c
patching file drivers/video/fbcon-splash.h
patching file drivers/video/fbcon-splash16.c
patching file drivers/video/fbcon.c
Hunk #1 succeeded at 79 (offset 3 lines).
Hunk #3 succeeded at 497 (offset 1 line).
Hunk #5 succeeded at 559 (offset 1 line).
Hunk #7 succeeded at 793 (offset 2 lines).
Hunk #9 succeeded at 1449 (offset 2 lines).
Hunk #11 succeeded at 1585 (offset 2 lines).
Hunk #12 succeeded at 1655 (offset 9 lines).
Hunk #13 succeeded at 1690 (offset 2 lines).
Hunk #14 succeeded at 1890 (offset 9 lines).
Hunk #15 succeeded at 2320 (offset 4 lines).
Hunk #16 succeeded at 2589 (offset 9 lines).
patching file include/video/fbcon.h
patching file kernel/panic.c
Hunk #1 succeeded at 253 (offset 178 lines).
Hunk #2 succeeded at 102 with fuzz 2.

!!! ERROR: media-gfx/bootsplash-0.6 failed.
!!! Function pkg_config, Line 108, Exitcode 1
!!! (no error message)

bootsplash 0.6 doesn't work with wolk either. i did a fresh emerge of wolk-sources just to make sure. maybe it will work if manually patched? i may try this later...

[Bangz]

There is a fault in the guide.

In step 8, you say to reboot. Except, it is not until step 12 where you actually copy the bootsplash into /initrd ...

[Narada]

There is a fault in the guide. In step 8, you say to reboot. Except, it is not until step 12 where you actually copy the bootsplash into /initrd

Thank you for pointing this out. It has now been fixed. Please post if you can think of further corrections or improvements. The guide is constantly being overhauled in response to feedback and problems noted in irc and here. Step numbering has also changed as the guide is now much shorter but hopefully that won't cause any problems.

[mikki]

Hey, now I have really nice ttys! (pseudo-ttys?)

A couple of notes on the instructions - I was messed up for quite awhile because I had enabled both vesa and tdfxfb console fbs. Nope. Not only did the tdfx not work, but even having it as fb1 broke things. The nice screen would come up for a second, then fracture into splinters when the second frame buffer initialized.

The second thing is just a nit. You refer to the example config file to use as /etc/bootsplash/gentoo/... in one place and /etc/bootsplash/default/... in another. I finally looked and saw that one was a like to the other, but if you are editing anyway...

Muchos Gracias Amigo(s)! Now I can walk proudly past my SuSE-snobbing friends!

[nempo]

Can anyone take a look at http://www.bootsplash.org/user.html and then provide us with a patch or instructions on how to implement these changes (more specifically the progress bar). Some help might come from this thread.
I don't know bash so I can't work on this myself.

[Narada]

The second thing is just a nit. You refer to the example config file to use as /etc/bootsplash/gentoo/... in one place and /etc/bootsplash/default/... in another. I finally looked and saw that one was a like to the other, but if you are editing anyway.

That's a good point. I've amended the guide to be consistent (using default rather than gentoo) which is always good although I'll leave the image locations in bootsplash-1280x1024.cfg untouched. What are you referring to when you say tdfxb or tdfx? Glad you got it working and are happy with it.

[Narada]

Thanks for the HOWTO. It all worked as it was supposed to until I added splash=silent to the kernel line in GRUB. This made absolutely no difference. I still get the splash images, but I also still get the boot messages.

The splash= option does not work with most kernels at the moment and progress bar is not supported by the gentoo init scripts as yet. I have added a note in the guide now to say so early on. If you wish to have a silent splash screen without a progress bar speak to 'basquiat' on this thread about what kernel he is using. He has this working according to his earlier message.

[mojo]

so as i wrote IT IS possible to patch the wolk-kernel. you only have to patch ONE config file manually. but so far it seems that this is too hard for some people without any help.

so let me guide you:

first apply the patch to the wolk-kernel.

Second you have to edit the file the two hunks failed:

nano -w /usr/src/linux/driver/video/Config.in

(the first hunk was successful so i will tell you to update the two faults):

you have to search for THIS line:

"$CONFIG_FB_SIS" = "y" -o "$CONFIG_FB_SA1100" = "y" -o

three lines later there is a line that looks like:

define_tristate CONFIG_FBCON_CFB16 y <- this line you must delete

instead you add:
if [ "$CONFIG_FBCON_CFB16" != "m" ]; then
define_tristate CONFIG_FBCON_CFB16 y
fi

so the first problem is solved.

now to solve the other fault you have to search for this line (THIS LINE COMES AFTER THE FIRST SO THERE IS NO NEED TO GO TO THE BEGINNING OF THE FILE):

"$CONFIG_FB_SA1100" = "m" -o "$CONFIG_FB_RADEON" = "m" -o

three lines later this line appears:

define_tristate CONFIG_FBCON_CFB16 m <- delete this line

and then you add:

if [ "$CONFIG_FBCON_CFB16" != "y" ]; then
define_tristate CONFIG_FBCON_CFB16 m
fi



So now you are ready . You can follow the first post (the guide) and configure your kernel and so on .

I tried this with the wolk_rc2 and the wolk_rc5_final (wich is not currently in the portage). So i think this will work too with the other wolk-kernel versions.

[chr1z]

60hz makes my eyes bleed
someone must fix this soon

[allucid]

so as i wrote IT IS possible to patch the wolk-kernel. you only have to patch ONE config file manually. but so far it seems that this is too hard for some people without any help.

hehe, you must be referring to me.
thx for the info! i am working on setting the refresh rate for my getty's and seeing if i can get the bootsplash patch to work with radeonfb, haven't gotten around to messing with wolk and trying to patch it manually (i just tried the ebuild) but you saved me the trouble, thx again.

[Lockup]

nice howto, i have a little suggestion on something that could be added to it though...
the part about how to create your own bootsplash image(the grub one is there but youre missing the framebuffer background one)
maybe a small little part about how to change console fonts would be nice too
thanks