From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1EA7gM-0006pr-Eb for garchives@archives.gentoo.org; Tue, 30 Aug 2005 15:05:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7UF0hw2024404; Tue, 30 Aug 2005 15:00:43 GMT Received: from smtp14.wxs.nl (smtp14.wxs.nl [195.121.6.28]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7UEnP8b025588 for ; Tue, 30 Aug 2005 14:49:25 GMT Received: from [10.0.0.150] (ip3e83ab52.speed.planet.nl [62.131.171.82]) by smtp14.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IM100C1UILWDL@smtp14.wxs.nl> for gentoo-user@lists.gentoo.org; Tue, 30 Aug 2005 16:51:32 +0200 (CEST) Date: Tue, 30 Aug 2005 16:51:30 +0200 From: Holly Bostick Subject: Re: [gentoo-user] More splash problems In-reply-to: <200508301035.10439.bshlists@rogers.com> To: gentoo-user@lists.gentoo.org Message-id: <43147272.3070502@planet.nl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-Accept-Language: nl-NL, nl, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050803) X-Enigmail-Version: 0.92.0.0 References: <430ADD7B.5040208@gmail.com> <200508301035.10439.bshlists@rogers.com> X-Archives-Salt: 457b3db8-15ee-4b19-b71e-d2dc1286c36d X-Archives-Hash: d348e117c2b10bf455ab076ccf4bcf8f 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. HTH, Holly -- gentoo-user@gentoo.org mailing list