> John Dangler schreef:
> 
>>Holly~
>>Maybe you can get this to work with this page...
>>
> 
> http://gentoo-wiki.com/HOWTO_fbsplash#Option_1:_Compiling_The_initramfs_Imag
> 
>>e_Directly_Into_The_Kernel
>>
>>There's a section somewhere in here that talks about that exact error.
>>
>>John D
>>
> 
> 
> Thank you, John-- that is what I've been doing (which is a change from
> my original behaviour, which was to compile a separate initrd). Doing so
> did improve the situation in that using the livecd theme now allows the
> computer to boot (whereas the initrd using the silent splash would
> result in a kernel panic and halt).
> 
> But I still get the message that 'no 8bpp pics are specified in the
> theme file' (twice) and then the message that the silent or verbose
> (whichever I've specified) image cannot be found, after which the system
> continues to boot. The console images are said to be being set (no
> message that they cannot be found), but (of course) do not appear.
> 

OK, more information, maybe... I think I might have found what's not
working (but I don't know why its not working).

I went back through the various links that explain how to do this, and
found the Gentoo Weekly Newsletter from 18 April 2005
( http://lwn.net/Articles/132803/ ).

Now the Tips and Tricks section, titled "Bootup with the Gentoo 2005.0
logo" says (and I quote):

Code Listing 5.3:                                                       |
|Configure the                                                            |
bootloader-----------------------------------------------------------------
--------
|                                                                         |
|# nano -w /boot/grub/menu.lst                                            |
|First change your kernel-boot-line to something like this (depends on    |
|your used framebuffer and further kernel-parameters):                    |
|kernel /boot/kernel-2.6.11-r6 root=/dev/hda3 video=vesafb:[EMAIL PROTECTED] |
|  splash=silent,theme:livecd-2005.0 quiet CONSOLE=/dev/tty1              |
===>|You must use more than 8bpp (in this example it is 32,
      ===>|
===>|specified by [EMAIL PROTECTED]).

This is supported by the fact that neither the 2005.0 or 2005.1 themes
specify an 8bpp picture in their config files, and in fact do not even
contain 8bpp files, afaics

Now, splash_geninitfs does allow you to specify --no8bpp (which didn't
work for me either), but from the GWN, that is not necessary anyway:

| Code Listing 5.2:                                                       |
|Creation of an initrd with the                                           |
2005.0-splash--------------------------------------------------------------
-----------
|                                                                         |
|Be sure that /boot is mounted before you call the command                |
|# splash_geninitramfs -v -g /boot/splash-livecd-2005.0-1024x768 \        |
|  -r 1024x768 livecd-2005.0                                              |

As you see, --no8bpp is not specified, which you'd think meant that it's
not needed (since the author knows that the theme doesn't contain a
specification for 8bpp, and this instruction comes before the other one
that deals with 8bpp at all).

So why, when my grub.conf says

 kernel /vmlinuz ro quiet root=/dev/hda5
video=vesafb-tng:ywrap,mtrr,[EMAIL PROTECTED]
splash=verbose,fadein,theme:livecd-2005.1 CONSOLE=/dev/tty1

clearly specifying more than 8bpp as instructed, is the splash failing
to load because no 8bpp picture is specified in the theme file (which if
it had to be specified in the theme file, surely it would have been, but
it's not, so presumably it doesn't have to be), and therefore fails to
find the silent or verbose image?

Logically, this must mean that my console is 8bpp??? That's the only
reason that it would be looking for the 8bpp picture. Why is my console
8bpp, when the message is being displayed on a 1280x1024 framebuffer
meaning that the framebuffer is loaded.... oh, shit. Shit, shit,
shit.... Sorry.

I think I got it.

I have vesafb-tng specified in the kernel as so:

[EMAIL PROTECTED]

but it should be

[EMAIL PROTECTED], shouldn't it? Or else the stupid framebuffer defaults
to 8bpp or something, doesn't it?

Just changed my kernel config, recompiling. I'll let you know how it goes.

That really might be it. Damn, I feel stupid, but it's not like any of
these bloody instructions remind you to set the %$#^&*$% bit depth in
your kernel vesafb-tng setting, either.

Brb,
Holy




I feel that "we" are close to a solution here (I think the splash will
work perfectly once it stops looking for an 8bpp picture; I also think
that's why emergence works, because it has one already), but I am over
my head here.

Please help :) .

Holly

-- 
gentoo-user@gentoo.org mailing list

Reply via email to