| View previous topic :: View next topic |
| Author |
Message |
patrickbores
Apprentice
Joined: 19 May 2003
Posts: 276
Location: Minneapolis, MN, USA
|
 Posted: Sat Mar 06, 2004 3:38 am Post subject: Bootsplash questions |
 |
|
Hello. I think I need a few things cleared up about setting up a bootsplash image. I'm using development-sources-2.6.3. This kernel is not patched to be able to do bootsplash right? I assume this because the guide I'm reading says:
| Quote: |
Now you have to change your kernel configuration, using make config, make menuconfig or make xconfig. Go to "Console drivers" -> "Frame-Buffer support" and select "VESA VGA graphics console" (or possibly another framebuffer driver, if one is available for your graphics hardware) and turn on "Use splash screen instead of boot logo". Also be sure to enable "Initial Ramdisk support" in "Block Devices" Save your new config and compile a new kernel. Copy the kernel to your /boot directory and make sure that you have a boot entry for it in your bootloader config.
|
I have none of these options when I do menuconfig. However, I do have these:
Device Drivers -> Graphics support -> Console display driver support -> Framebuffer console support
Device Drivers -> Graphics support -> Logo configuration -> Bootup logo
None of the guides I've read mention this setup. By enabling these, I'm able to get Tux to appear in the corner of my screen at bootup. But I can't get any of the themes in /etc/bootsplash to come up.
Also, what exactly does passing "--bootsplash" to genkernel do? Does it simply include a bootsplash image in the initrd? How does it know which one?
I've also seen the vga, video, and BOOT_IMAGE kernel parameter mentioned. What do these mean?
Sorry about the long post, but I've read every word of every bootsplash guide I can find, and none of them seem to apply to my system. Any suggestions on how to get this stuff working?
_________________
P.S. - this is what part of the alphabet would look like if Q and R were eliminated. |
|
| Back to top |
|
 |
shiftzero
Tux's lil' helper
Joined: 16 Mar 2003
Posts: 89
|
|
| Back to top |
|
|
patrickbores
Apprentice
Joined: 19 May 2003
Posts: 276
Location: Minneapolis, MN, USA
|
| Posted: Sat Mar 06, 2004 5:56 am Post subject: |
|
|
Thanks for the info. I've made a little progress. I got the patch installed, and now I have /proc/splash, but the /etc/init.d/bootsplash script uses /sbin/fbresolution to figure out which image to use. However, fbresolution reports that /dev/fb/0 and /dev/fb0 do not exist.
How might I get these to show up (using udev)?
Thanks,
Patrick
_________________
P.S. - this is what part of the alphabet would look like if Q and R were eliminated. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 737
|
| Posted: Thu Mar 11, 2004 1:48 am Post subject: |
|
|
| I have the same questions as you patrick. I have disabled the boot logo and I get a nice high resolution boot screen, but I get no images. I alos get a no such file or dir when I do a and I get a seg fault during the final stages of boot that will disappear if I remove the bootsplash default at start up. I have been trying for several days to get this to work properly and I haven't yet. I am using the gentoo-dev-sources 2.6.3-r2 and I belive the kernel is patched during the emerge peocess. Hopefully sombody can provide us with some more answers soon. |
|
| Back to top |
|
|
patrickbores
Apprentice
Joined: 19 May 2003
Posts: 276
Location: Minneapolis, MN, USA
|
| Posted: Thu Mar 11, 2004 3:04 am Post subject: |
|
|
It's puzzling. I replaced fbresolution with a shell script that simply echoed "1024x768" (my laptop's screen resolution). That made the errors about /dev/fb0 go away, but certainly not my bootsplash problems.
The bootsplash init script would set the console framebuffer image for all the ttys, except the main one, tty0. splash was having a segmentation fault when it tried to set it on tty0.
But, I still have no "boot" image. It's just a black screen. And all of this sporatically causes strange behavior in X. I'm hoping that the Gentoo devs eventually fully integrate the bootsplash stuff, so it "just works", like most other things on Gentoo.
Until, then I've given up and reverted back to no bootsplash, no console image, etc...
Patrick
_________________
P.S. - this is what part of the alphabet would look like if Q and R were eliminated. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 737
|
| Posted: Thu Mar 11, 2004 9:22 pm Post subject: |
|
|
I am not sure what was the exact problem however the bootsplash screen is working just fine. I can only say it must have been a coruprt bootsplash emerge. I unmerged the exsiting one and emerged the a new copy did an etc-update to make sure all configs were over writen. Remove the links to the old default config and the initrd from my /boot dir. Then I went back to the Bootsplash How To and followed the instructions completely again. I double checked each step and when I was sure I had everything right I rebooted.
Everything worked as it should have and now I am ready to install a custom bootspllash..................Worked Great..............Thanks
Some interesting things to note are.
1. Make damn sure you do not have USE BOOT LOGO selected in your kernel.
2. Do not use a color depth setting higher than 64k ie.........for 1024x768 use vga=0x317 in your kernel line and not 0x318. I am not sure that anyone is using a higher setting successfully. It would be intresting to know if anyone is though.
3. When creating the link /sbin/splash make sure /boot is mounted and that you do it from /.
If you do it while you are in /boot it will create a boot@ in your /boot dir and you will need to have your gurb initrd line read initrd=/boot/initrd-whatever.
If you do it from / your grub initrd line will simply be initrd=/initrd-whatever.
If you get this wrong you won't be able to boot your kernel and you will have to use the live cd to get back in and repair the errors.
WARRNING I am a noob and these are my experiences and may not be what is reguired for your configuation or kernel ver. Use this info at your own risk................... 
I hope this is helpful to some. |
|
| Back to top |
|
|
|
Other Things Gentoo
