View previous topic :: View next topic |
Author |
Message |
QyRoN n00b
Joined: 28 Apr 2004 Posts: 31
|
Posted: Thu May 06, 2004 7:58 pm Post subject: Bootsplash doesn't load in time and doesn't refresh console |
|
|
Hi
I've installed Bootsplash as described in HOWTO:
enabled bootsplash support in 2.6 kernel (2.6.5-r1),
configured grub command line (vga=0x314 splash=silent initrd=...) and add bootspash to be loaded during boot (rc-update add bootsplash boot). The bootsplash starts but there are 2 problems:
1) It starts to late (2 seconds before the end actually ), when boot process is almost done. Is it possible to run bootspash in the beginning of booting?
2) When it starts, only text area is refreshed and anything out of the text area remains (first screenshot). When I switch consoles, everything looks properly (second screenshot).
How can I solve these problems?
http://myoffice.ru/albums/userpics/10851/unrefreshed.jpg
http://myoffice.ru/albums/userpics/10851/normal.jpg |
|
Back to top |
|
|
sorrodos n00b
Joined: 22 Apr 2004 Posts: 54 Location: Salt Lake City, UT *and* Spokane, WA
|
Posted: Thu May 06, 2004 8:15 pm Post subject: |
|
|
I just set this up for myself a week ago... and I think I experienced the same problem you are having.
Did you enable RAM disk and initrd support in your kernel? And then did you correctly setup the initrd image? I didn't get those steps correctly, and my screen looked like the first screenshot you posted.
Maybe I'm off, but I think you should take a look at step 6 where you create the initrd image, and then make sure you enable the following in your kernel...
Code: | Block Devices ->
[*] Loopback device support
[*] RAM disk support
(4096) Default RAM disk size
[*] Initial RAM disk (initrd) support
|
Let me know if this doesn't fix your problem...
Last edited by sorrodos on Thu May 06, 2004 9:28 pm; edited 2 times in total |
|
Back to top |
|
|
QyRoN n00b
Joined: 28 Apr 2004 Posts: 31
|
Posted: Thu May 06, 2004 9:22 pm Post subject: |
|
|
sorrodos
Oh, I didn't know about RAM disk option and I didn't enable it!! Thank you for advice |
|
Back to top |
|
|
QyRoN n00b
Joined: 28 Apr 2004 Posts: 31
|
Posted: Fri May 07, 2004 9:24 am Post subject: |
|
|
I enabled RAM disk support in kernel, but it doesn't help. I used one of the initrd's from /usr/share/bootsplash dir. Do I have to make the initrd manually? |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Sat May 08, 2004 8:25 pm Post subject: |
|
|
I suppose that might do the trick. Have you had any luck? I have the exact same problem that you're having, (and I did enable all the correct options in my kernel).
Also, does anyone have some input into the other problem, that the bootsplash executes 2 seconds before the boot is finished? Seems pointless to me, and I think it has something to do with initscripts and runlevels- but I haven't been able to find a solution yet.
Be careful with your initscripts if you don't know what you're doing -- I already had to rescue my system once using chroot from a livecd because it wouldn't boot when I tinkered with the bootsplash depend() function in its initscript.
Justin _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
sorrodos n00b
Joined: 22 Apr 2004 Posts: 54 Location: Salt Lake City, UT *and* Spokane, WA
|
Posted: Sun May 09, 2004 1:49 am Post subject: |
|
|
The initrd contains both a verbose bootsplash and a silent one. I'm not even sure why you need to add bootsplash to the default runlevel, because if I press F2 during boot to see startup messages, there is still a frame buffer image there. I have the bootsplash init script load a different console frame buffer image. If I just wanted to keep the same one that the initrd image contains, I don't think I'd have to execute the bootsplash script.
How are you creating your initrd? I tried simply copying one of the .cfg files over, but that never worked for me. I think you need to use the following command...
Code: | /sbin/splash -s -f /etc/bootsplash/default/config/bootsplash-1280x1024.cfg > /boot/initrd-1280x1024 |
If you haven't tried that yet, do that and see if it works. |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Sun May 09, 2004 5:45 pm Post subject: |
|
|
sorrodos wrote: |
How are you creating your initrd? I tried simply copying one of the .cfg files over, but that never worked for me. I think you need to use the following command...
Code: | /sbin/splash -s -f /etc/bootsplash/default/config/bootsplash-1280x1024.cfg > /boot/initrd-1280x1024 |
If you haven't tried that yet, do that and see if it works. |
Yeah, that code works, but it needs to go all on one line: Code: | /sbin/splash -s -f /etc/bootsplash... > /boot/... | + your boot partition needs to be mounted. _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
|
Back to top |
|
|
sorrodos n00b
Joined: 22 Apr 2004 Posts: 54 Location: Salt Lake City, UT *and* Spokane, WA
|
Posted: Sun May 09, 2004 7:25 pm Post subject: |
|
|
That WAS all on one line, it just got wrapped because its so long I shoulda clarified that. |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
|
Back to top |
|
|
[rush] n00b
Joined: 10 May 2004 Posts: 3 Location: Czech Republic
|
Posted: Mon May 10, 2004 9:18 am Post subject: |
|
|
QyRoN wrote: | I enabled RAM disk support in kernel, but it doesn't help. I used one of the initrd's from /usr/share/bootsplash dir. Do I have to make the initrd manually? |
I had the same problem on my box and for me it helped to re-compile kernel ( 2.6.5-gentoo-r1 ) without "register parameters", I guess.. I've seen some kernel <-> module Ooops on my console when starting bootsplash.bin and had no silent splash at all. Try to recompile your kernel without that experimental code, it should help as it did for me. _________________ .. nothing but straight logic.. |
|
Back to top |
|
|
AmosMutke Apprentice
Joined: 24 Dec 2003 Posts: 235 Location: Akita, Japan.
|
Posted: Mon May 10, 2004 9:41 pm Post subject: |
|
|
page 26 and 27 of the bootsplash thread lists these config options for RAM disk and initrd support
Code: |
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_LBD=y
|
go here for more info. |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Tue May 11, 2004 12:40 am Post subject: |
|
|
Hi,
This isn't the problem in my case -- like I said already -- bootsplash is WORKING!
(Just to clarify, I grep'd the kernel options you specified, and they are all there and correct)
The problem is the time during the boot process that bootsplash executes -- it happens much too late (and is pretty useless for those of us using a X, a windows manager, & a login manager. )
I want to see the boosplash image *while* the system is still booting. Any advice there?
JS _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
AmosMutke Apprentice
Joined: 24 Dec 2003 Posts: 235 Location: Akita, Japan.
|
Posted: Tue May 11, 2004 2:05 am Post subject: |
|
|
infamousmrsatan wrote: | Hi,
This isn't the problem in my case -- like I said already -- bootsplash is WORKING!
(Just to clarify, I grep'd the kernel options you specified, and they are all there and correct)
The problem is the time during the boot process that bootsplash executes -- it happens much too late (and is pretty useless for those of us using a X, a windows manager, & a login manager. )
I want to see the boosplash image *while* the system is still booting. Any advice there?
JS |
I remember reading a post where it recommended trying other resolutions... but the person with the problem never posted if it worked or not...
You also might want to verify that your initrd resolution matches your "vga=xxx" kernel parameter...
| 640x480 800x600 1024x768 1280x1024
----+-------------------------------------
256 | 0x301 0x303 0x305 0x307
32k | 0x310 0x313 0x316 0x319
64k | 0x311 0x314 0x317 0x31A
16M | 0x312 0x315 0x318 0x31B
Code: |
## example grub.conf ######
title= Gentoo Linux 2.6.3-r1
root (hd0,3)
kernel (hd0,5)/2.6.3 root=/dev/hda4 video=vesafb:ywrap,mtrr vga=0x317
initrd=/boot/bootsplash
|
maybe you could post your grub.conf or lilo.conf to see if anyone sees anything missing.
have you tried other bootsplash initrd's?
I guess I'm just checking the obvious solutions... grasping at straws never hurts.. |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Tue May 11, 2004 3:03 am Post subject: |
|
|
AmosMutke wrote: |
I remember reading a post where it recommended trying other resolutions... but the person with the problem never posted if it worked or not...
|
I had thought of changing resolutions, because when I first noticed the problem I thought it was due to higher resolution images taking a longer time to render. That wasn't it though, I don't think. Its the order in which the initscripts run that causes the problem, I'm pretty sure.
AmosMutke wrote: |
You also might want to verify that your initrd resolution matches your "vga=xxx" kernel parameter...
|
Check!
AmosMutke wrote: |
| 640x480 800x600 1024x768 1280x1024
----+-------------------------------------
256 | 0x301 0x303 0x305 0x307
32k | 0x310 0x313 0x316 0x319
64k | 0x311 0x314 0x317 0x31A
16M | 0x312 0x315 0x318 0x31B
|
Someone has reported problems using hex values for the vga parameter (in another post on the support thread, I think) There were some hex values that I tried that spit out errors at bootup, but others worked ok. I haven't tried specifying decimal values, but the resolution/depth that I want seems to work ok with the hex value.
AmosMutke wrote: |
maybe you could post your grub.conf or lilo.conf to see if anyone sees anything missing.
|
Will do, --I'll ssh to my gentoo box in a couple minutes, but I'm 99.999% certain that the problem is not in grub.conf
AmosMutke wrote: |
have you tried other bootsplash initrd's?
|
No. Not yet, just the default.
J _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Tue May 11, 2004 6:23 am Post subject: |
|
|
Ok here it is -- sorry, had to wait to get to my gentoo box because my wife caught me on the forums when I was supposed to be writing
grub.conf
Code: |
default 0
timeout 10
#Nice, fat splash-image to spice things up :)
splashimage=(hd0,0)/grub/splash.xpm.gz
### the following three configurations are the post fb kernels
# Yes Framebuffer, Yes Bootsplash
title=Gentoo Linux (Kernel 2.6.5) (+fb +splash)
root=(hd0,0)
kernel=(hd0,0)/kernel-2.6.5-fb-splash2
root=/dev/hda3
video=vesafb:ywrap,mtrr
vga=0x317
initrd=/boot/initrd-1024x768
splash=verbose
# Yes Framebuffer, No Bootsplash
title=Gentoo Linux (Kernel 2.6.5) (+fb -splash)
root=(hd0,0)
kernel=(hd0,0)/kernel-2.6.5-fb-splash2
root=/dev/hda3
video=vesafb:ywrap,mtrr
vga=0x317
# No Framebuffer, No Bootsplash
title=Gentoo Linux (Kernel 2.6.5) (-fb -splash)
root=(hd0,0)
kernel=(hd0,0)/kernel-2.6.5-fb-splash2 root=/dev/hda3
|
Please note that all the indented lines are actually on the same line as "kernel=..." _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
sorrodos n00b
Joined: 22 Apr 2004 Posts: 54 Location: Salt Lake City, UT *and* Spokane, WA
|
Posted: Tue May 11, 2004 6:42 am Post subject: |
|
|
Are you absolutely certain your kernel has been compiled correctly?
Like I said before, I had this EXACT same problem earlier. My bootsplash would load at the end of the boot process when the bootsplash script was executed.
The problem lay in my kernel configuration.
The bootsplash script itself doesn't actually load a bootsplash screen during boot time. That script only applies all frame buffer images to the other virtual consoles.
To see the splash while you are actually booting, you must have the correct kernel configuration, and a valid initrd image. The initrd actually contains the boot-time splash screen in it.
Make certain you have the right options enabled in the kernel, as well as the ones that need to be disabled set that way.
Try creating the initrd again as well. |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Tue May 11, 2004 4:03 pm Post subject: |
|
|
Ok -- I noticed that some of the kernel options that AmosMucke (sp?) is using, I don't have, but I thought that you specifically aren't supposed to enable the logo stuff.
I'll try it later tonight.
The options I tested for were in this this post.
Justin _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Tue May 11, 2004 10:28 pm Post subject: |
|
|
Ok, adding the logo stuff didn't help.
The only affect it had was that of adding a small "tux" logo in the upper left hand corner of the screen during the boot process. It didn't hurt either -- the framebuffer is still there, and the initrd splash image still initializes partway through the boot (towards the end).
Any other ideas? Could it have anything to do with agpart?
Thanks -- J _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
sorrodos n00b
Joined: 22 Apr 2004 Posts: 54 Location: Salt Lake City, UT *and* Spokane, WA
|
Posted: Wed May 12, 2004 6:13 am Post subject: |
|
|
Yeah, the howto says that agpart does give some people problems.
I'd follow what it says to do, disable agpart in the kernel, then add the line to your XF86Config it lists.
I'd also disable the logo thing, since the howto says to do so.
These are the options I'd go with.
Code: | 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 |
This is the thread I got all my info from. |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Fri May 14, 2004 7:47 am Post subject: |
|
|
Ok -- disabled AGPart, added the appropriate line to /etc/X11/XF86Config, removed logo stuff in kernel, reboot to new kernel, same problem.
Has anyone experiencing this problem found a fix yet? Please report back if you do!! I'm about out of ideas.
Any framebuffer/bootsplash experts out there know what might be the cause??
Justin
ps -- a little later, time permitting, I'll install the fbcapture utility and post some screenshots of my problem...
Thanks. _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
AmosMutke Apprentice
Joined: 24 Dec 2003 Posts: 235 Location: Akita, Japan.
|
Posted: Fri May 14, 2004 8:11 pm Post subject: |
|
|
infamousmrsatan wrote: |
Has anyone experiencing this problem found a fix yet? Please report back if you do!! I'm about out of ideas.
|
tell ya what.. e-mail me a copy of your kernel .config file and I'll compare it to mine then post the differences.... Maybe that will help isolate the problem..
my email is "mr_jobe at hotmail dot com"... Please make the subject descriptive so I don't delete it as spam..
P.S. Something must have changed with the boot logo stuff in the 2.6.5 kernel.. I have it enabled in my kernel and bootsplash still works just fine..
*shrug*
dunno why... it just does... |
|
Back to top |
|
|
Buchalka n00b
Joined: 04 May 2004 Posts: 20
|
Posted: Sat May 15, 2004 6:22 am Post subject: |
|
|
infamousmrsatan wrote: |
### the following three configurations are the post fb kernels
# Yes Framebuffer, Yes Bootsplash
title=Gentoo Linux (Kernel 2.6.5) (+fb +splash)
root=(hd0,0)
kernel=(hd0,0)/kernel-2.6.5-fb-splash2
root=/dev/hda3
video=vesafb:ywrap,mtrr
vga=0x317
initrd=/boot/initrd-1024x768
splash=verbose
|
The solution is so simple (I had the same problem and just figured it out by re-reading the how-to again).
the initrd=/boot/.... line has to be on a seperate line, so try this...
title=Gentoo Linux (Kernel 2.6.5) (+fb +splash)
root=(hd0,0)
kernel=(hd0,0)/kernel-2.6.5-fb-splash2
root=/dev/hda3
video=vesafb:ywrap,mtrr
vga=0x317
splash=verbose
initrd=/boot/initrd-1024x768
i.e. the initrd= is a seperate command to the kernel= command.
To make it work on my computer I put all the commands on one line like this...
title=Gentoo Linux (Kernel 2.6.5) (+fb +splash)
root=(hd0,0)
kernel=(hd0,0)/kernel-2.6.5-fb-splash2 root=/dev/hda3 video=vesafb:ywrap,mtrr vga=0x317 splash=verbose
initrd=/boot/initrd-1024x768
Hopefully this will fix your problem, it fixed it for me anyway!
Cheers
Tim |
|
Back to top |
|
|
infamousmrsatan Apprentice
Joined: 08 Jan 2004 Posts: 201 Location: California
|
Posted: Sun May 16, 2004 6:52 pm Post subject: |
|
|
Woo Hoo!! Yep this fixed my problem!!!
Its funny that it <i>sort of </i>worked with initrd on the same line.
Ok, so confirmed, to fix this problem
put kernel=... and initrd=.... on separate lines in your grub.conf.
Thanks again!! _________________ Registered Linux User 344425
Join the adopt an unanswered post initiative today!
Por favor, corrija mi espanol! |
|
Back to top |
|
|
sorrodos n00b
Joined: 22 Apr 2004 Posts: 54 Location: Salt Lake City, UT *and* Spokane, WA
|
Posted: Tue May 18, 2004 12:50 am Post subject: |
|
|
infamousmrsatan wrote: | Its funny that it <i>sort of </i>worked with initrd on the same line. |
It didn't work w/ them on the same line. Like I said before, the bootsplash script doesn't do anything ith the actual screen displayed at boot time. The bootsplash ONLY applies an image to the background of the framebuffer AFTER the system is booted. The actual initrd image handles a splash during boot completely.
The bootsplash HOWTO thread contained the answer you were looking for, but I'm glad you found it on here anyhow. |
|
Back to top |
|
|
|