Gensplash-How-to with progressbar!!!!!

StifflerStealth · Retired Dev Joined: 03 Jul 2002 Posts: 968

I have an existing initrd image and I tried to do a:

Jakub · Posted: Tue Aug 31, 2004 12:26 pm Post subject:

garnie · Posted: Tue Aug 31, 2004 1:21 pm Post subject:

I can't get i to work

I am using the Aquamatrix theme from bootsplash.de.

first i converted it via the bootsplash2fbsplash program, then made the initrd and added it to grub.conf and menu.lst, of course i have added splash to default via rc-update.

motub · Posted: Tue Aug 31, 2004 1:37 pm Post subject:

Firstly, afaik, you no longer need the vga= option (you already have 1280x1024-32@60, which is the correct one with the new vesafb);

Secondly, did you check the conversion after using bootsplash2fbsplash (which I've never heard of before now, so thanks)? Did you look at the cfg file to make sure the paths were correct, that they pointed to the correct images, and that the images themselves were correctly moved to the new location?

As it rather seems that at least some of the images (the framebuffer backgrounds) are not being found.
_________________
Holly
--Why not adopt an unanswered post?--

upD8R · n00b Joined: 28 May 2004 Posts: 5

I've never used a bootsplash theme with an animation part. Anyway, Gensplash runs just fine here and because it should be compatible to bootsplash: How can I run animations with Gensplash?

Is there a HowTo available?

Thanks, Mario

spock_ · Posted: Tue Aug 31, 2004 7:05 pm Post subject:

A few things that I believe may use clearing up here:

1. You can't 'mknod' the fbsplash device. Fbsplash is a dynamic char device. Make it static and it will break sooner or later.

2. Fbsplash and splashutils are not in any way limited to Gentoo. "But the progress bar won't work, and it complains about /proc/splash all the time" you might scream.. Yeah, it does, but guess what - in order to make the progress bar work, the initscripts have to be prepared to feed data to splashutils. Your distro's scripts may be prepared to work with bootsplash, or they may not be prepared to work with anything. If you want to have a working progress bar, modify the scripts yourself or ask your devs to support fbsplash/splashutils. The patches and utilities are not in any way Gentoo-specific (or at least haven't been made so intentionally).

Your best chance of making the progress bar work is searching for /sbin/splash or /sbin/splash.bin in the initscripts and changing it to /sbin/splash_util (modifying the command line options of course.. splash_util -h will be your guide

)

3. Some Debian systems seem to halt when using vesafb-tng. So far people reported that this is caused by the reset_vga_palette() funtion in console-screen.sh. I don't know exactly what is causing it (and it's not fully reproducible). If you want to use vesafb-tng the best option for now might be throwing this function out (it's not that you really need to reset the VGA palette at boot) or (I guess) using pmipal with vesafb-tng.

4. If kernel messages at boot time appear sooooo scary to the windows users (which is strange, don't BIOS messages scary them even more?), you can always try the 'quiet' kernel command line option.

5. Fbsplash/splashutils don't use /proc for anything. If your initscripts complain about /proc/splash, it's because they have been made specifically to work with bootsplash.

6. Want to use bootsplash themes with fbsplash? Use the bootsplash2fbsplash utility from splashutils.

7. Want /sbin/splash and other stuff used in Gentoo? Download http://dev.gentoo.org/~spock/projects/gensplash/splashutils-gentoo-0.1.tar.bz2

8. Loopback device support isn't necessary, neither is RAM disk support. But if don't enable initrd, give up all hope of using initrds - you will have to compile the theme into the kernel.

9. Despite what people might be telling your, the theme: part in the kernel command line is necessary. Simple 'splash=silent' is NOT ENOUGH.

10. Want to change the font colors? man console_codes, look for 'set palette'.

11. You can't append initramfs data to an initrd image.

12. Making animations work with fbsplash should be no different than making them work with bootsplash. Gentoo currently doesn't support boot animations.

13. Splashutils compile errors ('modelist' incomplete type) are caused by a bug in the latest kernels' header files. I'm working on making splashuitls less vulnerable to this kind of bugs.
_________________
"In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move."

allan · Posted: Tue Aug 31, 2004 10:41 pm Post subject:

arch4nge1 · n00b Joined: 11 Aug 2004 Posts: 57

The splash appears when I press Ctrl-Alt-Del but when it boots up, I can see it switches resolution to the framebuffer, but no splash. It then shows just the verbose boot up messages and at some later stage it tries to show a progress bar which constantly appears and disappears with each progress update but no splash screen.

I've followed the 5 steps as described on Spock's site too(http://dev.gentoo.org/~spock/projects/gensplash/gensplash-in-5-easy-steps.php) and this is where I am stuck at the moment.

Also I keep seeing something like

upD8R · n00b Joined: 28 May 2004 Posts: 5

spock_

UberLord · Posted: Wed Sep 01, 2004 9:45 am Post subject:

spock_ · Posted: Wed Sep 01, 2004 9:55 am Post subject:

UberLord · Posted: Wed Sep 01, 2004 10:30 am Post subject:

Jakub · Posted: Wed Sep 01, 2004 10:32 am Post subject:

anyc · Tux's lil' helper Joined: 31 May 2004 Posts: 119

Hi

I've added "splash" to my default runlevel and uncommented

cloc3 · Posted: Wed Sep 01, 2004 6:54 pm Post subject:

spock_ · Posted: Wed Sep 01, 2004 7:05 pm Post subject:

Jakub · Posted: Wed Sep 01, 2004 9:59 pm Post subject:

Why the hell did I have to mess with it? It was perfect.

Now, when I get the "Setting framebuffer console images" (just before "Entering runlevel: 3" ) message during boot, my splash screen disappears for a moment. It's annoying because the text changes its position (goes a bit left). Then, after a moment, the text moves back right a bit and the splash screen reappears.

That's what i get in my logs:

Mr. Atoz · Posted: Wed Sep 01, 2004 11:29 pm Post subject:

After trials and tribulations, I _finally_ got mine working.... :-D

However, I HAVE to use the vga= in my grub.conf. Using the video= by itself never enables the fb. The neat thing about that is...my bootsplash comes up more or less instantly...no waiting. :-D

I am using ck-sources, 2.6.8-ck4, and I am using the stock vesafb, not vesafb-tng. Perhaps this is why the video lines don't buy me anything? Will the vesa-tng patch run cleanly against the 2.6.8-ck4 source?

I also get some funk in the kernel output, here is a snippet, I can post the whole thing if you like (it is rather long). It occurs right after the agp modules load. For this chipset, I have to load intel_agp, which auto-loads agpgart.

Jakub · Posted: Wed Sep 01, 2004 11:43 pm Post subject:

hoschi · Posted: Wed Sep 01, 2004 11:52 pm Post subject:

arch4nge1 · n00b Joined: 11 Aug 2004 Posts: 57

Paranoid · Posted: Thu Sep 02, 2004 7:57 am Post subject:

Jakub