Re: [bootsplash] [ANNOUNCE] splashswitch - updated: 0.1.6

[Sebastian <se...@gm...>]

On Sunday 25 July 2004 20:56, Lasse Bigum wrote:
> On Fri, Jul 23, 2004 at 03:09:29PM +0200, Lasse Bigum wrote:
> > > That should do roughly what you asked for. It also should be a more
> > > flexible way, than to provide the stuff for different TTYs in every
> > > theme.
> > >
> > > Get the updated version at http://vizzzion.org/?id=splashswitch
> >
> > Just did, will experiment more with it, as the previous version didn't
> > seem to give me different bootsplashes on the different VT's.
>
> I still can't get it to work with different bootsplashes on the different
> VT's. 

Does it work with --switch-vt specified, what effect are you getting? Please 
also post your .scheme file, so I can try it here.

> Also, just using the symlinked initrd.current will give me an error 
> when GRUB tries to boot. I have to manually edit it to one of the
> initrd-files that has been placed there by splashswith.

Hm, symlinks (in general) do work very well for grub here, using reiserfs. I 
just pointed grub to load /boot/initrd.current. Could you check that this is 
also the case for you? I assume that the initrds splashswitch created are 
actually working, but that the initrd couldn't be loaded.

> Any suggestions other than trying to recompile my kernel with the latest
> bootsplash patch? I think the one I'm using is rather old, but still for
> the correct kernel though I think (I've deleted the patch itself
> unfortunately).

Hmm. Are you using a separate partition for /boot? In that case, it might be a 
better solution to use a relative symlink ... just a guess anyway. 
It should work also with "older" bootsplash patches, at least I wouldn't know 
why not. bootsplash v3 should be Ok, though. Maybe there are some other 
variables that have to be sorted out, before you recompile your kernel ...

cheers,
-- 
sebas
- - - - - - - - - - -
http://vizZzion.org
======================
Death solves all problems: no man, no problem. - Joseph Stalin