public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tony Davison <tony.davison2@ntlworld.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] More splash problems
Date: Tue, 30 Aug 2005 18:36:16 +0100	[thread overview]
Message-ID: <200508301836.16922.tony.davison2@ntlworld.com> (raw)
In-Reply-To: <43147272.3070502@planet.nl>

On Tuesday 30 August 2005 15:51, Holly Bostick wrote:
> bshlists schreef:
> > Using all the suggestions on this thread I was able to get
> > gensplash up and running.  I however have one small problem  the
> > bootsplash come up some 1/3 the way through the bootup process. 
> > Now I remember seeing somewhere a change to a config file which
> > would change when the bootsplash started.
> >
> > I'd appreciate it if someone would remind me how to do this.
>
> Afaik, it's not a change to a config file, it's a change in the way
> you generate the initramfs.
>
> If you compile it into the kernel (instructions on the Wiki; see
> How-to fbsplash), it will start up at the very start.
>
> If you load it as a separate initrd, you have to wait for the
> framebuffer to initialize before the splash can start (which takes a
> short while).
>
> Naturally, if you change from loading an initrd to compiling the
> initrd into the kernel, you do have to change a config file
> (grub.conf, to remove the initrd= line, since you no longer have
> one), but changing the file alone won't make any difference if you
> haven't changed the way you create the initrd in the first place.
>
I have two 2.6.12-r9 kernels ATM one which has framebuffer splash on all 
ttys and the other which only has boot splash.
The bootsplash one starts after the udev message and the other one 
starts after the initial uncompressing kernel message (which IIRC is 
when the framebuffer starts, for sure its when the console changes to 
1024x768 on this box)
As far as I know the .config files were the same apart from the fbsplash 
support.
(can't check now as I've been kernel compiling to test some new scsi 
hardware:-( and forgot to save the old .config )
If this is not very clear, both kernels have framebuffers, one has 
bootsplash, and the other has bootsplash and pretty pictures on tty1-6. 
the initrd is the same in both cases, not in the kernel.
Wonderful are the ways of splash.
Tony Davison
tony.davison2@ntlworld.com
-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2005-08-30 17:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23  8:25 [gentoo-user] More splash problems Nagatoro
2005-08-23  9:07 ` Michael Kintzios
2005-08-23  9:44   ` Nagatoro
2005-08-23 10:48 ` Uwe Thiem
2005-08-23 12:23   ` Nagatoro
2005-08-23 12:53     ` Michael Kintzios
2005-08-23 17:46       ` Nagatoro
2005-08-23 14:59 ` Holly Bostick
2005-08-23 17:50   ` Nagatoro
2005-08-23 18:27     ` Holly Bostick
2005-08-23 18:50     ` Matthias Krebs
2005-08-23 19:14       ` Holly Bostick
2005-08-23 20:08         ` Matthias Krebs
2005-08-23 23:14           ` Holly Bostick
2005-08-24  5:01         ` Nagatoro
2005-08-24  7:23         ` Uwe Thiem
2005-08-24  7:27         ` Uwe Thiem
2005-08-23 19:43       ` Nagatoro
2005-08-30 14:35 ` bshlists
2005-08-30 14:51   ` Holly Bostick
2005-08-30 15:31     ` bshlists
2005-08-30 15:42       ` Holly Bostick
2005-08-31  8:02       ` Uwe Thiem
2005-08-31 14:06         ` bshlists
2005-08-30 17:36     ` Tony Davison [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200508301836.16922.tony.davison2@ntlworld.com \
    --to=tony.davison2@ntlworld.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox