From: LostSon <lostson@lostsonsvault.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fbsplash problems
Date: Tue, 19 Jul 2005 15:51:47 -0500 [thread overview]
Message-ID: <1121806307.18048.1.camel@Angelina.www.Angelina.org> (raw)
In-Reply-To: <200507192145.47849.tony.davison2@ntlworld.com>
[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]
On Tue, 2005-07-19 at 21:45 +0100, Tony Davison wrote:
> On Tuesday 19 July 2005 21:27, charly ghislain wrote:
> > On Tue, 19 Jul 2005 22:12:38 +0200, Richard Fish
> > <bigfish@asmallpond.org>
> >
> > wrote:
> > > LostSon wrote:
> > >> On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
> > >>> LostSon wrote:
> > >>>> Hello I am trying to get fbsplash to work and am stuck. I have
> > >>>> followed the
> > >>>> directions on the gentoo-wiki site but still no luck. Im using
> > >>>> vesafb with a 2.6.12-r6 kernel. my grub.conf looks like this
> > >>>> title=Gentoo-2.6.12-r6-fbsplash
> > >>>> root (hd0,0)
> > >>>> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> > >>>> video=vesafb:ywrap,mtrr,1024x768@70 spla$
> > >>>> initrd (hd0,0)/fbsplash-gentoo-1024x768
> >
> > make sure nano didnt cut your kernel line. The video= option should
> > be on the same line than the kernel one. It should look like:
> >
> > title=Gentoo-2.6.12-r6-fbsplash
> > root (hd0,0)
> > kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> > video=vesafb:ywrap,mtrr,1024x768@70 splash=... #(one line)
> > initrd (hd0,0)/fbsplash-gentoo-1024x768
> >
> > This is very annoying, but while editing a line larger than the
> > console, nano cut it into two lines :( You have to check every time,
> > go to the end of the first part of the cuted line and press delete
> >
> Use nano -w <file.name> to avoid line wraps.
> --
> Tony Davison
> tony.davison2@ntlworld.com
I checked this per your instructions as well and no it hasnt cut it off
its all on one line. Still no luck im still just getting the cant open
config file on /etc/splash error and fd0 crap, heh
--
LostSon
http://www.lostsonsvault.org
Fox Cities Linux User Group = www.foxlug.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-19 21:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 14:51 [gentoo-user] fbsplash problems LostSon
2005-07-19 15:49 ` Ramón Gutiérrez
2005-07-19 18:49 ` Richard Fish
2005-07-19 15:50 ` Holly Bostick
2005-07-19 16:00 ` LostSon
2005-07-19 17:07 ` cafairle
2005-07-19 17:31 ` Christoph Eckert
2005-07-19 18:44 ` Richard Fish
2005-07-19 20:00 ` LostSon
2005-07-19 20:12 ` Richard Fish
2005-07-19 20:27 ` charly ghislain
2005-07-19 20:45 ` Tony Davison
2005-07-19 20:51 ` LostSon [this message]
2005-07-19 21:10 ` Christoph Eckert
2005-07-19 21:10 ` LostSon
2005-07-19 21:30 ` Christoph Eckert
2005-07-19 21:31 ` Holly Bostick
2005-07-19 22:03 ` LostSon
2005-07-19 22:38 ` Holly Bostick
2005-07-20 5:11 ` Richard Fish
2005-07-21 16:14 ` LostSon
2005-07-21 16:23 ` LostSon
2005-07-21 21:36 ` Richard Fish
2005-07-21 16:57 ` LostSon
2005-07-22 6:26 ` Vitaly Kovalyshyn aka samael
2005-07-22 15:00 ` Richard Fish
2005-07-25 6:48 ` Vitaly Kovalyshyn aka samael
2005-07-19 22:00 ` Richard Fish
2005-07-19 22:54 ` Christoph Eckert
2005-07-20 7:33 ` charly ghislain
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=1121806307.18048.1.camel@Angelina.www.Angelina.org \
--to=lostson@lostsonsvault.org \
--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