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

Message

snekiepete · Post by **snekiepete** » Thu Aug 05, 2004 7:01 pm

Version 2.0 of this document. edited 08/23/2004 8:48

Some preliminary information can be found here: (faq)
http://forums.gentoo.org/viewtopic.php? ... &start=100

and here: (homepage)
http://dev.gentoo.org/~spock/

Alot of things have changed, most notably an improved default theme with more resolutions and the addition of splashutils into portage.

If your kernel is already patched with the fbsplash patch, start here: (mount /boot at this point)

http://dev.gentoo.org/~spock/projects/g ... -steps.txt

Most new kernels (newer releases above 2.6.8-rc1 depending on the sources) are including this patch now. most notably:

Gentoo-Dev-Sources
Nitro-Sources
CK-Sources
Mafteah-Sources
others?????

I would check the changelog or release info to make sure the patch exists first since these are subject to change per eash release.

Patching your kernel.

----> If your kernel is patched with the bootsplash patch, you must reverse it before applying the fbsplash patch <----

You can get the fbsplash patch here:

http://dev.gentoo.org/~spock/projects/gensplash/

Code: Select all

# cd /usr/src/linux
# cat /path/to/fbsplash/patch | patch -p1
# make menuconfig

(go to )
Device Drivers ---> Graphics support ---> [*] Support for frame buffer devices
<*> Compile in your framebuffer device
Console display driver support --->
[*] Video mode selection support
<*> Framebuffer Console support
Logo configuration --->
[*] Bootup logo
[*] Standard 224-color Linux logo (NEW)
[*] Support for the framebuffer splash

Code: Select all

# make bzImage..........and copy it to /boot.

Converting bootsplash themes: page 6

http://forums.gentoo.org/viewtopic.php? ... 59#1467059

gatiba · Post by **gatiba** » Thu Aug 05, 2004 7:16 pm

Emerge of splashutils stops with this error:

Code: Select all

../klibc/include/stdio.h: At top level:
../klibc/include/stdio.h:66: error: syntax error before "ftell"
../klibc/include/stdio.h:67: warning: return type defaults to `int'
../klibc/include/stdio.h: In function `ftell':
../klibc/include/stdio.h:68: error: syntax error before "lseek"
make[1]: *** [vsnprintf.o] Error 1
make: *** [klibc] Error 2

!!! ERROR: media-gfx/splashutils-0.9_pre03 failed.
!!! Function src_install, Line 27, Exitcode 2
!!! (no error message)

bash-2.05b#

snekiepete · Post by **snekiepete** » Thu Aug 05, 2004 7:36 pm

Was you kernel already patched and rebooted prior to the emerge? I am not sure if reboot is necessary, but that might be a possiblilty.

or

if you are using a pre-patched kernel, you may need to check to see if you have the most recent kernel patch?

just some ideas.

ck42 · Post by **ck42** » Thu Aug 05, 2004 8:58 pm

My splashutils build fails with this:

tests/mmaptest.c:14: warning: unused parameter `argc'
tests/mmaptest.c:14: warning: unused parameter `argv'
CONF libjpeg
MAKE libjpeg
CONF zlib
MAKE zlib
CONF libpng
MAKE libpng
CC kernel/splash_kernel.o
distcc[19989] ERROR: compile /root/.ccache/splash_ker.tmp.Gentoobox.19985.i on localhost failed
splash_kernel.c: In function `main':
splash_kernel.c:33: error: `FB_SPLASH_IO_ORIG_KERNEL' undeclared (first use in this function)
splash_kernel.c:33: error: (Each undeclared identifier is reported only once
splash_kernel.c:33: error: for each function it appears in.)
splash_kernel.c:77: error: `FB_SPLASH_IO_ORIG_USER' undeclared (first use in this function)
make: *** [kernel/splash_kernel.o] Error 1

>>> Install splashutils-0.9_pre03 into /var/tmp/portage/splashutils-0.9_pre03/image/ category media-gfx
CC kernel/splash_kernel.o
distcc[20231] ERROR: compile /root/.ccache/splash_ker.tmp.Gentoobox.20227.i on localhost failed
splash_kernel.c: In function `main':
splash_kernel.c:33: error: `FB_SPLASH_IO_ORIG_KERNEL' undeclared (first use in this function)
splash_kernel.c:33: error: (Each undeclared identifier is reported only once
splash_kernel.c:33: error: for each function it appears in.)
splash_kernel.c:77: error: `FB_SPLASH_IO_ORIG_USER' undeclared (first use in this function)
make: *** [kernel/splash_kernel.o] Error 1

!!! ERROR: media-gfx/splashutils-0.9_pre03 failed.
!!! Function src_install, Line 27, Exitcode 2
!!! (no error message)

Using love-2.6.8-rc2-love3

I've already been trying to get this going via the other thread. I've already config'd the kernel and rebooted but didn't get any splash.

snekiepete · Post by **snekiepete** » Thu Aug 05, 2004 9:17 pm

It looks like a problem with the kernel patch. Unless you reversed the patch that came with love-sources and repatched with the new one, it won't work I dont think. Let me know if this is the case, I can help get the right patch to your kernel if need be.

The kernel I use is development-sources patched with:

development-sources-2.6.8-rc3
vesafb-tng-0.9-rc3-r3-2.6.8-rc1.patch.bz2.
fbsplash-0.9-r2-2.6.8-rc3.patch
from_2.6.8-rc2_to_staircase7.E
supermount-ng204.diff.bz2

2.6.8-rc2-love3 has:

vesafb-tng-0.9-rc3-r2-2.6.8-rc2-bk2.diff
fbsplash-0.9-2.6.8-rc2-bk4.diff

so that may be the problem......unless you reverse these and patch the new ones, especially the fbsplash, I am not sure if the vesafb-tng would be the culprit.

If you're intersted, there is Mafteah-sources that has both of these already

here is a link to a patch to mm-sources-2.6.8-rc2-mm2

http://forums.gentoo.org/viewtopic.php? ... ovesources

and a link to a patch to development-sources-2.6.8-rc3

http://forums.gentoo.org/viewtopic.php? ... highlight=

ck42 · Post by **ck42** » Thu Aug 05, 2004 9:44 pm

Ok....now see, this is where I'm getting all weirded out

I'm not sure of what exactly is needed, as far as patches, for the kernel. The other thread *seemed* to indicate that the love sources kernel was 'ready to go' and didn't need any patches.

When I tried to patch the kernel using the fbsplash patch, I got this:

/usr/src/linux
cat fbsplash-0.9-r2-2.6.8-rc3.patch | patch -p1
patching file Documentation/fb/00-INDEX
Reversed (or previously applied) patch detected! Assume -R? [n]

Can you say exactly which patches are needed for the 2.6.8-rc2-love3 kernel?

Also, not being very familiar with applying patches, I'm still getting konfoozed with the terminology. When you say 'reverse' a patch, I'm assuming you mean to 'uninstall' a patch that has been applied already, correct?

Does the -R prompt from the above attempted patch mean to 'reverse' the patch instead of re-applying it?

As for the vesafb-tng patch:

/usr/src/linux
bzip2 -dc vesafb-tng-0.9-rc3-r3-2.6.8-rc1.patch.bz2 | patch -p1
patching file arch/i386/boot/video.S
Reversed (or previously applied) patch detected! Assume -R? [n]

gatiba · Post by **gatiba** » Thu Aug 05, 2004 9:52 pm

I use love-2.6.8-rc2-love3 also...
How can i reverse the patches?

snekiepete · Post by **snekiepete** » Fri Aug 06, 2004 2:48 am

EDIT -- this has been added to the howto

this should work.

download this (original patch)

http://dev.gentoo.org/~spock/projects/g ... -rc1.patch

and this patch (new patch)

http://dev.gentoo.org/~spock/projects/g ... -rc1.patch

now this is the original patch from spock, the patch to love-sources could be a little different, but this is worth a try.

Code: Select all

# cd /usr/src/linux
# cat fbsplash-0.9-2.6.8-rc1.patch | patch -Rp1

then patch in the new patch:

Code: Select all

# cat /path/to/fbsplash-0.9-r2-2.6.8-rc1.patch | patch -p1

when patching the new patch, it is possible (likely due to the np cpu sceduler patch) you will get a failed hunk at 133, or the sysctl file. Here you will have to manually patch

Code: Select all

# nano -w include/linux/sysctl.h

scroll down to where you see:

KERN_SCHED_TIMESLICE=66 (this is done by the np scheduler, other kernel sources may not have this line)

on the next line after that (or on anyline that =66 if you are using other sources)

Enter:

Code: Select all

KERN_FBSPLASH=66, /* string: path to fbsplash helper */

save the file, rebuild the kernel and save to /boot.

Code: Select all

# make clean bzImage modules modules_install
# mount /boot (if not already)
# cp arch/i386/boot/bzImage /boot/.......

I do not know if there are problems reversing with the patch from spock or if you'll need the exact one from the love-sources dev's.

More than likely the next love will have the new patch, which should be soon.

gatiba · Post by **gatiba** » Fri Aug 06, 2004 7:01 am

TX!

I'll try it this evening!

Frodg · Post by **Frodg** » Fri Aug 06, 2004 12:16 pm

Yippee - Got it working.... it needed grub to have splash=silent and Bob's your uncle

Frodg · Post by **Frodg** » Sun Aug 08, 2004 12:13 am

A small but annoying issue

Everything works perfectly but at boot time I get this message several times at odd interval (paraphrased):

splash_util: error on loading libjpeg.so.62: cannot locate file - no such file or directory.

As it is just a warning message what does it mean if everything is working...?

I have looked for a cfg file for splash_utils that includes a reference to libjpeg but can't find one... Could it be a path issue ???
and where would I change the reference to libjpeg to clear the error message ?

Any Ideas.....

ck42 · Post by **ck42** » Sun Aug 08, 2004 12:27 am

I get a repeating /sbin/splash line 68 syntax error.

ck42 · Post by **ck42** » Sun Aug 08, 2004 12:35 am

snekiepete:

In part 3.5, the line:

# rm /etc/splash/default

I thought that 'default' was a directory (for some reason). Using rm implies that 'default' is a file?? If so, what is in this file? and where should it be located?

I'm a little unclear as to WHAT the file and directory structure of all this should look like. Can you/someone list what directories should exist, in the etc/splash path and what files are needed within each dir?

btw...I'm trying to set this up for the emergence theme @1280x1024.

snekiepete · Post by **snekiepete** » Sun Aug 08, 2004 1:26 am

ck42 wrote:snekiepete:

In part 3.5, the line:

# rm /etc/splash/default

I thought that 'default' was a directory (for some reason). Using rm implies that 'default' is a file?? If so, what is in this file? and where should it be located?

I'm a little unclear as to WHAT the file and directory structure of all this should look like. Can you/someone list what directories should exist, in the etc/splash path and what files are needed within each dir?

btw...I'm trying to set this up for the emergence theme @1280x1024.

the "default" emergence theme does not have any other resolutions besides 1024x768. I have edited the how-to and added links to places to get themes. There is an emergence theme there, but it may be different than spocks?

/etc/splash/default should be a symbolic link, therefore no -r is needed.
it should link to the theme you want to use, for example i have this:

Code: Select all

bash-2.05b$ ls /etc/splash
default  emergence

where default is a symbolic link to emergence. I am not sure if this is necessary, but it makes it easier for me since I have not investigated changing and of the config files to point to a different theme name.

now the "emergence theme" is installed by emerge splashutils. It is setup correctly as far as file structure, if you want to use a different theme and resolution, you do this: (example shown is for a bootsplash theme copied over to run as a gensplash theme at 1280x1024)

1. Copy your theme to /etc/splash (let's call our theme ck42 and say that it resides in /etc/bootsplash/themes)

Code: Select all

# cp -r /etc/bootsplash/themes/ck42 /etc/splash
# ls /etc/splash
default emergence ck42
# rm /etc/splash/default (this removes the symlink to emergence)
# ln -s /etc/splash/ck42 /etc/splash/default

ok with me so far? The rest is just making some minor changes to convert the bootsplash theme to gensplash theme:

2.

Code: Select all

# cp /etc/splash/default/config/bootsplash-1280x1024.cfg /etc/splash/default/1280x1024.cfg
# gedit(or some-other-editor) /etc/splash/default/1280x1024.cfg

find these lines:

pic=/etc/bootsplash/themes/ck42/images/verbose-1024x768.png
silentpic=/etc/bootsplash/themes/ck42/images/silent-1024x768.jpg

and change them to

pic=/etc/splash/ck42/images/verbose-1024x768.png
silentpic=/etc/splash/ck42/images/silent-1024x768.jpg

then goto step 4 and five of the "Customizing your theme" section of the how to.

snekiepete · Post by **snekiepete** » Sun Aug 08, 2004 1:35 am

Frogd

I remember having this error myself, but I can't remember how I fixed it.

btw are you using splashutils-0.9-pre04-gentoo-r1

and

fbsplash-0.9-r5-2.6.8-rc3.patch?

ck42 · Post by **ck42** » Sun Aug 08, 2004 2:55 am

snekiepete:

Thanks for the clarification.

One thing that came up that I'm not sure is a prob or not though.

When doing:
# splash_geninitramfs -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1280x1024 default

I get this results:
cpio: File ./img.cpio.gz grew, 131072 new bytes not copied

I'm going to reboot and try it out anyway but still want to confirm if that result is an issue or not.

snekiepete · Post by **snekiepete** » Sun Aug 08, 2004 3:04 am

this is not a problem, I get it too, I don't quite understand what it means, but everything should work!

ck42 · Post by **ck42** » Sun Aug 08, 2004 3:14 am

No worky. Another question I keep forgetting to ask.

Does the verbose image HAVE to be a .png file format?

Strange that the silent splash is a .jpg but the other is a .png

I'll take a look again at the paths I've got setup. I prolly typo'd somewhere.

snekiepete · Post by **snekiepete** » Sun Aug 08, 2004 3:25 am

it shouldn't matter what the format is for the pic.

make sure /boot is mounted.

make sure you changed the filenames accordingly in /etc/splash/default/1280x1024.cfg

ck42 · Post by **ck42** » Sun Aug 08, 2004 5:09 am

Ok....looks like I'm getting somewhere now. modified my menu.lst file with the kernel option: splash=verbose,theme:default

I assume the 'default' part is what points to the default dir symlinked to my theme dir. I also just like starting in verbose mode.

NOW.

What I get is a blue OPAQUE screen that nearly fills the entire viewing area with white text giving me verbose boot info. I can see the edges of the theme .jpg behind this blue window though....so the theme *is* being found and thrown up on the screen...it's just being covered up.

Any ideas what this blue window is or how I can change it to be transparent?

snekiepete · Post by **snekiepete** » Sun Aug 08, 2004 5:28 am

what theme are you using?

ck42 · Post by **ck42** » Sun Aug 08, 2004 12:55 pm

emergance

ck42 · Post by **ck42** » Sun Aug 08, 2004 7:05 pm

It wasn't mentioned in the instructions but is there a need to modify the kernel boot line in GRUB?

Here's my current line:
kernel (hd0,0)/boot/bzImage-2.6.8-rc2-love3 root=/dev/hda3 ro video=vesafb:ywrap,pmipal,1280x1024-24@75 splash=verbose,theme:default

the video=.......... section was put there manually.
In trying to eliminate the blue opaque screen, I changed the line to:
kernel (hd0,0)/boot/bzImage-2.6.8-rc2-love3 root=/dev/hda3 ro splash=verbose,theme:default

With that, I get the full size fonts, but no more blue screen section....but also NO emergance splash.

snekiepete · Post by **snekiepete** » Mon Aug 09, 2004 12:05 am

I don't think I am getting what you are trying to say.

You want verbose splash so you want to see the boot process messages right?

If you are using the latest version of splashutils, verbose is chosen by default, therefore to get the silent boot image, you must have splash=silent in the grub line.

if you have splash=silent in you grub line you will see this image: (if you are not using the default emergence theme with the ebuild but the one from bootsplash)
http://www.bootsplash.de/files/themes/s ... silent.png

if you have splash=verbose, you will see this:
http://www.bootsplash.de/files/themes/s ... se-top.png

The instructions have a place to change the grub line right after step 3 which was pointed out by Frogd earlier.

ck42 · Post by **ck42** » Mon Aug 09, 2004 12:55 am

"You want verbose splash so you want to see the boot process messages right?"

Correct.

"If you are using the latest version of splashutils, verbose is chosen by default, therefore to get the silent boot image, you must have splash=silent in the grub line."

Ok...so I can just leave out the 'splash=" section. I think the same holds true for the 'theme=' setting. If it's not there, it defaults to 'default' which is symlinked to my actual theme.

EDIT:

Got things working. Took the shotgun approach and re-did everything. Also notifed that my grub initrd was 1280x1024. Set it all up for 1024 mode and just gave up trying to get the gensplash working @ 1280.

I'm happy with it for now.