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

Message

lokojones · Post by **lokojones** » Sat Aug 21, 2004 6:51 pm

aslocum, I've got the same problem here... silent works fine, but with verbose I get the same as u... Only with love sources, with gentoo-dev-sources I dont get that problem..

jguc · Post by **jguc** » Sat Aug 21, 2004 7:35 pm

I used the instructions: http://dev.gentoo.org/~spock/projects/g ... -steps.php, but I get an error.

My kernel config:

Code: Select all

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_VESA_STD is not set
CONFIG_FB_VESA_TNG=y
CONFIG_FB_VESA_DEFAULT_MODE="1024-768@85"
# CONFIG_VIDEO_SELECT is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
# CONFIG_LOGO is not set
CONFIG_FB_SPLASH=y

Error:

Code: Select all

...
Kernel command line: ro root=/dev/hdb3 video=vesafb:ywrap,pmipal,1024x768-32@85 splash=silent,theme:emergence
fbsplash: silent
fbsplash: theme emergence
...
vesafb: NVIDIA Corporation, NV34 Board - p162-1n , Chip Rev    (OEM: NVIDIA)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:dfe0
vesafb: pmi: set display start = c00ce016, set palette = c00ce080
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: hardware supports DCC2 transfers
vesafb: monitor limits: vf = 150 Hz, hf = 70 kHz, clk = 2550 MHz
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1024x76832bpp not found
vesafb: mode 1153x86432bpp not found
vesafb: mode 1280x96032bpp not found
vesafb: mode 1280x102432bpp not found
vesafb: no matching VBE mode found
vesafb: probe of vesafb0 failed with error -22
...

My kernel: 2.6.8-gentoo-r1

Illissius · Post by **Illissius** » Sat Aug 21, 2004 8:05 pm

Shouldn't CONFIG_FB_VESA_DEFAULT_MODE be 1024x768@85?
Otherwise that is eerily similar to the errors I'm having, except in my case it also says it doesn't support DCC transfers and lists all the refreshes as 0Hz max. Have you tried it at 16bpp?

jguc · Post by **jguc** » Sat Aug 21, 2004 8:10 pm

HermanR wrote:I just got gensplash/fbsplash working with gentoo-dev-sources-2.6.8-r1. Great!

Just a question: What do I have to do when I change to a new kernel. Does everything has to be done anew? The kernel patches are in gentoo-dev-sources now, but do I need to re-emerge splashutils and do
Code: Select all
splash_geninitramfs -v -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 emergence
again?

I couldn't find this in the docs and howto's. Thanks.

Can you send you grub and kernel config? I'm still trying to configure the same kernel with gensplash.

jguc · Post by **jguc** » Sat Aug 21, 2004 8:12 pm

Illissius wrote:Shouldn't CONFIG_FB_VESA_DEFAULT_MODE be 1024x768@85?
Otherwise that is eerily similar to the errors I'm having, except in my case it also says it doesn't support DCC transfers and lists all the refreshes as 0Hz max. Have you tried it at 16bpp?

It doesn't work with 16bpp, 32bpp, 60Hz, 70Hz... nothing

lokojones · Post by **lokojones** » Sat Aug 21, 2004 8:14 pm

That shouldnt affect if other res specified, I think.. have u tried setting other resolutions? what says "ls /etc/splash/emergence"? It could be that you havent set up your 1024x768.cfg..

anyway, not sure

Paranoid · Post by **Paranoid** » Sat Aug 21, 2004 9:31 pm

Thanks aslocum for figuring out the errors-works great!

raid517 · Post by **raid517** » Sun Aug 22, 2004 1:49 am

Is anybodty still watching this thread? If so can you tell me why when I get to this part

Code: Select all

splash_geninitramfs -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 default

I just get an output saying:

Code: Select all

plash_geninitramfs -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 default
Warning: config file for theme 'default', resolution 1024x768 does not exist!

Where exactly is it looking for it? My config file is located at:

Code: Select all

/etc/splash/config/bootsplash-1024x768.cfg

I have edited my config file to point to my desired images at :

Code: Select all

/etc/splash/images

I have patched and built my kernel as per the recomendations.

The instructions appear to be a little incomplete as to where to place the config files so that they can be incorporated into the compressed rom image.

Other than this I have no issues to report so far.

Thanks for the input.

GJ

count_zero · Post by **count_zero** » Sun Aug 22, 2004 3:34 am

I believe that you need to make a symlink, "default" in /etc/splash/ and make it point to the directory where you're keeping your config file. i.e.,

Code: Select all

unlink /etc/splash/default
ln -s /etc/splash/config /etc/splash/default

in your case. You also need to rename your config file to "1024x768.cfg"

iverson0881 · Post by **iverson0881** » Sun Aug 22, 2004 4:04 am

I'm having a strange problem. The splash works correctly under verbose and silent but only when restarting. Upon startup it doesn't show any FBsplash images and just the plain black. One thing I noticed is that it says:

Code: Select all


dmesg | grep fbsplash
fbsplash: silent
fbsplash: console 0 using theme 'default'

The console 0 is throwing me off.

My kernel is enabled properly and it explains itself upon restarting since it works.

Thanks

Oh yeah here is my grub.conf

Code: Select all

  GNU nano 1.3.2                                                          File: grub.conf

default 0
timeout 5
splashimage=(hd0,1)/grub/splash.xpm.gz

title=Gentoo Linux 2.6.8-r1
root (hd0,1)
kernel=/vmlinuz-2.6.8-gentoo-r1 root=/dev/hda4 video=vesafb:ywrap,mtrr,1280x1024-32@75 splash=silent hdc=ide-cd devfs=nomount
initrd=/boot/fb_splash-emergence-1280x1024

title=Windows XP SP2
root (hd0,0)
chainloader +1

count_zero · Post by **count_zero** » Sun Aug 22, 2004 4:17 am

Did you run splash_geninitramfs and make bzImage? If so, you don't need the initrd in your /boot or grub.conf. I'll bet you did the old "splash" command. Check out the first post in this thread for more info.

iverson0881 · Post by **iverson0881** » Sun Aug 22, 2004 5:05 am

Well it works now. I added "theme:emergence" into the kernel line and it works now. Is this still proper? It works though

Headrush · Post by **Headrush** » Sun Aug 22, 2004 1:56 pm

I am thoroughly confused by the change to gensplash and have a few questions that might help others too.

1) In the latest gentoo-dev-sources (2.6.8-r1), you can select vesafb or vesafb-tng. Am I right in thinking that they both provide framebuffer support but vesafb-tng provides new features like setting refresh rates?

2) Both bootsplash and gensplash provide graphic bootup screens using the framebuffer?

3) Gensplash is the new direction for bootup splash screens in Gentoo and is the only one provided in the latest gentoo-dev-sources. Gensplash requires vesafb-tng support to work?

I have recompiled my kernel and made the new bzImage and modified my grub.conf.

Code: Select all


title Gentoo Linux Test
kernel (hd1,1)/boot/kernel-2.6.8-gentoo-r1 root=/dev/hde2 video=vesafb:ywrap,mtrr,1024x768-16@60 splash=silent

When I restart, I get a page of so of textual kernel messages, then the Emergence boot theme appears (silent) and seems to work. After a few lines it switches to verbose mode, but I believe that is mentioned already in this forum. So it seems to work.

On the vesafb-tng site, http://dev.gentoo.org/~spock/, it says that NVIDIA 5900 boards have a BIOS problem and might not work well.

4) Would this be the cause of my system showing text messages first before switching to framebuffer? (NVidia 5900)

5) If the above is true, and Gensplash will be used instead of bootsplash in future gentoo-dev-sources, does this mean all us Nvidia 5900 are screwed without trying a risky BIOS upgrade?

6) Does anyone with a Nvidia 5900 have gensplash working perfectly?

7) Can I use gensplash with vesafb instead of vesafb-tng if I just want the same old appearance of bootsplash? And, can you use vesafb-tng with bootsplash instead of gensplash?

I know I can add bootsplash support back in this kernel, but this may become harder with future kernels and would like to stick with want the Gentoo standards will be.

ANy help appreciated.

raid517 · Post by **raid517** » Sun Aug 22, 2004 2:46 pm

OK thanks for the input, but I officially don't get it now

If I followed the guide and insert the line in grub as foolows as describes (adapted for my prefered configuration)

Code: Select all

kernel /2.6.8.1-test3 root=/dev/hda2 elevator=cfq video=vesafb:ywrap,mtrr,1024x768-32@85 splash=silent

I get no frambuffer and no splash.

If I change this slightly (after reading around) to:

Code: Select all

kernel (hd0,1)/boot/kernel-2.6.8.1-test3 root=/dev/hda2 elevator=cfq video=vesafb:ywrap,mtrr,1024x768 vga=0x317 splash=silent

I at least get a framebuffer wiith a tux logo, but I don't get a bootsplash.

Possibly the above line might seem a little random, but I didn't want to seem as if I hadn't tried various thing or tried reading elsewhere before asking.

But anyway, just to clarify, my configuration file (as far as I'm aware having followed the instructions here pretty exactly) is located at /etc/splash/config and is now called 1024x768.cfg.

a dir of this directory on the command line gives:

Code: Select all

1024x768.cfg  bootsplash-1280x1024.cfg.bak
bootsplash-1024x768.cfg.bak  bootsplash-800x600.cfg.bak

The other configuration files have been renamed here to prevent possible system confusion.

The actual images for my splash theme are located at:

/etc/splash/images

The output of dir from this directory gives:

Code: Select all

root@2[images]# dir
bootsplash-1024x768.jpg   bootsplash-800x600.jpg  silent-1280x1024.jpg
bootsplash-1280x1024.jpg  silent-1024x768.jpg     silent-800x600.jpg

The actual configuration file I am using (or attempting to use) at /etc/splash/config/1024x768.cfg reads as follows:

Code: Select all

# This is a bootsplash configuration file for 
# theme SuSE, resolution 1024x768. See
# ftp://ftp.suse.com/pub/people/stepan/bootsplash for
# more information. Comments are welcome by stepan@suse.de

# config file version
version=3

# should the picture be displayed?
state=1

# fgcolor is the text forground color.
# bgcolor is the text background (i.e. transparent) color.
fgcolor=7
bgcolor=0

# (tx, ty) are the (x, y) coordinates of the text window in pixels.
# tw/th is the width/height of the text window in pixels.
tx=25
ty=28 
tw=979
th=691

# ttf message output parameters
text_x=204
text_y=544
text_size=26
text_color=0xeef4ff

# name of the picture file (full path recommended)
/etc/splash/images/bootsplash-1024x768.jpg
silentjpeg=/etc/splash/images/silent-1280x1024.jpg

progress_enable=1

# background
box silent noover  204 582 820 612 #04045498
box silent inter 204 583 204 611 #ffffff #ffffff #526bb0 #526bb0
box silent       204 583 820 611 #ffffff #ffffff #526bb0 #526bb0
# black border

box silent         204 582 820 582 #313234
box silent         204 612 820 612 #eef4ff
box silent         204 582 204 612 #313234
box silent         820 582 820 612 #eef4ff

# text box (left, top)
box     19 19  19 720 #313234
box     19 19 1005 19 #313234
# (right, bottom)
box     1005 19 1005 720 #eef4ff
box     19 720 1005 720 #eef4ff

# box itself
box noover 20 20 1004 719 #04045498

overpaintok=1

Dmesg gives the following output:

Code: Select all

vesafb: framebuffer at 0xd0000000, mapped to 0xe0808000, size 3072k
vesafb: mode is 1024x768x16, linelength=2048, pages=9
vesafb: protected mode interface info at c000:57b3
vesafb: pmi: set display start = c00c5847, set palette = c00c5893
vesafb: pmi: ports = b010 b016 b054 b038 b03c b05c b000 b004 b0b0 b0b2 b0b4
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device

And:

Code: Select all

fbsplash: console 0 using theme 'default'

When issuing the command to build my initramfs I did the following:

Code: Select all

splash_geninitramfs -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 defaulcd /usr/src/linux
make bzImage
mount /boot 
cp arch/i386/boot/bzImage /boot/YOUR-BZIMAGE-NAME

So the question is, where am I going wrong

I compiled my kernel with vesa frambuffer support, I removed all other options beyond the vesa framebuffer driver, I selected framebuffer console support and support for frambuffer splash, I also chose support for intrid compressed rom file systems and CramFs support. AFAIK I have done everything correctly on the kernel side.

I tried just using the love source and the nitro sources, but the first wouldn't boot and the second just wouldn't compile. So it looks like that is out of the window. It's a bit too much 'experimentation' for my tastes anyway.

The question is, where am I going wrong?

Any input would be welcome.

GJ

Headrush · Post by **Headrush** » Sun Aug 22, 2004 2:59 pm

Raid517,

I think you need video=vesafb-tng to use the new gensplash.

When you have video=vesafb, you are using the older framebuffer support which uses the vga= syntax. You get nothing after the logo appears because you no longer have bootsplash but gensplash.

raid517 · Post by **raid517** » Sun Aug 22, 2004 3:08 pm

Ok, so I remove the vga=line? I'll give it a go. thanks. One other thing I don't get is here where the autor specifies 1400x1050-32@85

I though specifying the colour depth and the refresh rate wasn't possible using the ordianry vesa drivers? I mean does the patching suggested here allow this? What is this saying anyway? That he is using a depth of 32bits @85Hz?

I thought the maximum depth for the normal FB drivers was 16?

GJ

lokojones · Post by **lokojones** » Sun Aug 22, 2004 3:09 pm

1) In the latest gentoo-dev-sources (2.6.8-r1), you can select vesafb or vesafb-tng. Am I right in thinking that they both provide framebuffer support but vesafb-tng provides new features like setting refresh rates?

Yes, you're right. With vesa-tng, you use "video" insted of "vga" in the kernel command line

2) Both bootsplash and gensplash provide graphic bootup screens using the framebuffer?

Yes, spock was the manteiner for bootsplash, and he decided not to do it anymore, putting instead of bootsplash his gensplash... It works better for gentoo, and it solves some problems (with bootsplash, silent boot didnt work for much people, for example)

3) Gensplash is the new direction for bootup splash screens in Gentoo and is the only one provided in the latest gentoo-dev-sources. Gensplash requires vesafb-tng support to work?

No, it doesnt requiere vesafb-tng to work, vesafb-tng is just another work from spock to set higher refresh rates and other things.

When I restart, I get a page of so of textual kernel messages, then the Emergence boot theme appears (silent) and seems to work. After a few lines it switches to verbose mode, but I believe that is mentioned already in this forum. So it seems to work.

That could be because of vesafb-tng.. not sure why, but a screen without framebuffer (default resolution) appear with some lines, and then it switches to bootsplash themes.. with normal vesafb the lines appear with your framebuffer resolution, but u dont have spock's improvements. Nothing of that should be related with having a 5900 I think.. It happens to me with a GeForce4 MX440

7) Can I use gensplash with vesafb instead of vesafb-tng if I jsut want the same old appearance of bootsplash?

What old appearence?

lokojones · Post by **lokojones** » Sun Aug 22, 2004 3:11 pm

raid517, vesafb-tng allows that. It is alredy in gentoo-dev-sources-r1, u will not need to patch it manually. Same for gensplash

Headrush · Post by **Headrush** » Sun Aug 22, 2004 3:23 pm

Thanks for the help Lokojones.

So to summarize, if I had vesafb support and bootsplash working properly before, I should be able to stay with vesafb (not vesafb-tng), and make the switch to gensplash and my graphic boot screens should work the same?

So in grub.conf I should use vga= if I stay with vesafb and not vesafb-tng support?

When I used bootsplash I had an initial ramdisk support (initrd=). So If I use gensplash I don't use this and use:

Code: Select all

splash_geninitramfs -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 default

to add the framebuffer picture/theme to the kernel image?

raid517 · Post by **raid517** » Sun Aug 22, 2004 3:39 pm

Ok well I have a small dilema I am trying to patch a friend's PC who isn't connected to the net at home. Is there somewhere I can tell him download (from work) a completed set of the latest gentoo development sources, or any sources (exept love and nitro) that include all the patches that he needs to set this up?

He lives quite a distance from me so it's not so simple as me getting them ad just taking them over there.

The thing is I'm not sure how well all this patching has gone.

I tried following the guide (so I could tell him what to do) but the original patch http://dev.gentoo.org/~spock/projects/g ... -rc1.patch isn't even avaiable any more..

It is in the archive, but I couldn't for the life of me figure out why it was needed (or safe) to use a patch that wen't back to almost the development stages of the 2.6x kernels. Trying to apply it in any case failed horribly.

Only when I tried patching with the latest patch fbsplash-0.9-r5-2.6.8-rc3.patch on a cleanly complieled kernel from kernel.org did I have any luck. Or at least the bootsplash option was avaiable in the kernel.

The original patch authot makes no reference in any case in his instruction set towards using older patches, or patching older patches, or patching kernel already patched with older patches. Why would this be needed? Why not just write one patch and be done with it?

In any case currently I have found that if I remove the VGA= line from Grub, then I loose the framebuffer completely, so clearly the patch is not working as intended.

Any input you guys can offer would be appreciated.

GJ

Gergan Penkov · Post by **Gergan Penkov** » Sun Aug 22, 2004 4:07 pm

Ok I have tried the spock's fbsplash patch against the 2.6.8.1-mm3-sources, but they could not be patched with the last fbsplash, because it is for the 2.6.8 tree. Well, I have hand merged and modified a little bit the patch to allow the splashutils compilation

. Using the vesafb-tng and the modified fbsplash http://bugs.gentoo.org/show_bug.cgi?id= ... k). Gergan

Headrush · Post by **Headrush** » Sun Aug 22, 2004 4:14 pm

I've tried using gensplash with the vesafb support (not vesafb-tng) and all I get is the requested framebuffer but no graphical boot screens. So maybe gensplash needs vesafb-tng.

Paranoid · Post by **Paranoid** » Sun Aug 22, 2004 4:16 pm

First let me say my gensplash works fine but I noticed after updating splashutils today spock had updated his gensplash how-to. He now has the initrd line in the kernel config. Now I don't have this and it works fine-what gives? Is there some benefit in using the initrd?

raid517 · Post by **raid517** » Sun Aug 22, 2004 5:00 pm

God knows. The only thing I do know is I need to find somehwere I can download the latest Gentoo development-sources without portage. I think that's the only way I (and my friend) can move forward with this.

GJ

Headrush · Post by **Headrush** » Sun Aug 22, 2004 5:03 pm

I've tried using initrd= set to the created initramfs but still doesn't start with framebuffer.

According to Spock's web site, initramfs is loaded in the middle of the kernel loading process.

Does anyone on any kernel have a bootscreen that comes up without displaying an initial group of kernel messages? (using gensplash and vesafb-tng)

If this is how initramfs works, (loading midway), isn't this a step back?

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

I can't make gensplash work