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..
I used the instructions: http://dev.gentoo.org/~spock/projects/gensplash/gensplash-in-10-easy-steps.php, but I get an error.
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?
I just got gensplash/fbsplash working with gentoo-dev-sources-2.6.8-r1. Great!
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.
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..
Thanks aslocum for figuring out the errors-works great!
Warning: config file for theme 'default', resolution 1024x768 does not exist!
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.
in your case. You also need to rename your config file to "1024x768.cfg"
The console 0 is throwing me off.
My kernel is enabled properly and it explains itself upon restarting since it works.
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.
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.
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.
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.
I get no frambuffer and no splash.
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.
The other configuration files have been renamed here to prevent possible system confusion.
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?
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.
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?
No, it doesnt requiere vesafb-tng to work, vesafb-tng is just another work from spock to set higher refresh rates and other things.
7) Can I use gensplash with vesafb instead of vesafb-tng if I jsut want the same old appearance of bootsplash?
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?
to add the framebuffer picture/theme to the kernel image?
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/gensplash/fbsplash-0.9-2.6.8-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.
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 [url]https://bugs.gentoo.org/show_bug.cgi?id=61262 patch I have succeeded in installing the splashutils and quingy and all runs now (including the nvidia with the pci=routeirq trick).
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.
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?
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.
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.
If this is how initramfs works, (loading midway), isn't this a step back?