public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: cafairle@engmail.uwaterloo.ca
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fbsplash problems
Date: Tue, 19 Jul 2005 13:07:21 -0400	[thread overview]
Message-ID: <1121792841.42dd33497d2f9@www.nexusmail.uwaterloo.ca> (raw)
In-Reply-To: <1121788823.8606.2.camel@Angelina.www.Angelina.org>

If you use the nvidia driver, you might have problems. I tried using fbsplash
with 2.6.12-r6 and -r4 using vidia 7667 drivers, but no luck with rivafb, vesafb
or nvidiafb. I then searched nvidia forums and read their readme and apparently
their driver deosnt support framebuffering very well.

So after spending a day messing with and research fb'ing, i gots nothing but
messed up fonts in xfce which i'm STILL trying to fix and actaully, i might send
a email to the list about it 

chris

Quoting LostSon <lostson@lostsonsvault.org>:

> On Tue, 2005-07-19 at 17:50 +0200, Holly Bostick wrote:
> > LostSon schreef:
> > >  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
> > > 
> > >  It tries to go to it but it just stays in text mode with no splash it
> > > doesnt even go to 1024x768. I get this when booting
> > > 
> > >  Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768@70
> > > splash=silent,theme:gentoo quiet CONSOLE=/dev/tty1
> > > 
> > >  Im not sure what that means though. Any ideas, thanks.
> > 
> > That means, afaik, that there is an error in the syntax of that specific 
> > line, and you need to fix it, as GRUB can't figure out or even guess 
> > what the heck you mean.
> > 
> > For reference, here's my kernel command line (splash does work for me):
> > 
> > kernel /vmlinuz root=/dev/hda5 
> > video=vesafb-tng:ywrap,mtrr,pmipal,1280x1024-32@60 
> > splash=silent,theme:emergence quiet CONSOLE=/dev/tty1
> > 
> > The (main) difference I see is that you have no bit depth specified in 
> > your video= command, but perhaps vesafb doesn't need one. I also see 
> > that I'm using pmipal and you aren't but since I don't even know what 
> > that is anyway, I'll assume it's not important.
> > 
> > So what I'm wondering is-- you're asking for vesafb in the command line, 
> > but is that actually the framebuffer that you've selected in the kernel 
> > (in menuconfig, Device Drivers section =>Graphics support, what is the 
> > actual name of the vesa framebuffer being built)?
> > 
> > Mine looks like
> > 
> > VESA VGA graphics support
> > 
> > VESA driver type (vesafb-tng)  --->
> > 
> > Does it actually say 'vesafb' between your parentheses (as I believe 
> > that vesafb-tng is the default if you enable VESA VGA graphics support)?
> > 
> > Also what version of splashutils, did you recently upgrade the kernel 
> > from 2.6.11, and if so, did you re-generate the splash initrd (there's 
> > an einfo to this effect in the recent splashutils ebuilds)?
> > 
> > HTH,
> > Holly
> 
>  Ok i tried adding that in my line but still no luck alot of what im
> getting is errors about not being able to load config files and fd0 or
> fb0 it goes by so fast and i cannot find these error messages in any of
> my logs either. Im using splashutils-1.1.9.7 btw, thanks
> -- 
> LostSon
> 
> http://www.lostsonsvault.org
> 
> Fox Cities Linux User Group = www.foxlug.org
> 




----------------------------------------
This mail sent through www.mywaterloo.ca
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-19 17:12 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 [this message]
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
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=1121792841.42dd33497d2f9@www.nexusmail.uwaterloo.ca \
    --to=cafairle@engmail.uwaterloo.ca \
    --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