From: James Miller <jamtat@mailsnare.net>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: framebuffer console problems: not enough video RAM?
Date: Sun, 24 Oct 2004 00:45:48 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0410240025400.1287@debian-emach> (raw)
In-Reply-To: <5.1.0.14.1.20041023211235.01feb690@celine>
On Sat, 23 Oct 2004, Ray Olszewski wrote:
> On that score ... just a wild, blue-sky thought here ... maybe your trying
> to use an 8 MB SGRAM on a card that only supports 4 MB is introducing a
> problem. Does anything improve if you remove this module and use only the
> onboard 4 MB?
Well, if I do that I won't get my 1280x1024 display under X. I upgraded
the video memory on this especially because the 4MB that came with it
would not do X at the proper resolution on this monitor. And it does the
job. As soon as I put that 8MB chip in there, copied over my XF86Config-4
from the other machine that was using this same monitor, it booted into X
like a champ (instead of that wimpy 1024x768 X display it used to give
with only 4MB). Much as I'd like to see what effect that would have on
this framebuffer failure, I'm reluctant . . .
> For the right form for lilo (or in your case grub) arguments, try the
> kernel source. (If you don't have enough room for the source tree, at least
> install the kernel-doc Debian package for your kernel.) I've been
> consulting the various docs in ./Documentation/fb/, and the actual source
> in ./drivers/video/ . From the first, I get (among other things) this:
>
> "To specify a video mode at bootup, use the following boot options:
> video=<driver>:<xres>x<yres>[-<bpp>][@refresh]
>
> where <driver> is a name from the table below." (atyfb is listed in this
> table; so is aty128fb.)
>
> Short of the actual source that parses this sfuff, that's about as
> definitive as you get. Hence my exact suggestion above.
Thanks for that pointer. I thought it should be somewhere.
> This card name does not *quite* match anything in the Hardware
> Compabibility HowTo. What X driver does it use? (Look in
> /etc/X11/XF86Config-4, under "Device", for the Driver entry.) If it uses
> ati, then you are probably treating it correctly. If it uses r128, then you
> should try the ati128fb framebuffer instead of atyfb.
I have "ati" in that stanza. Another item I note in XF86Config-4 but
can't tell if it's relevant is that I have; Option "UseFBDev" "true."
Could that have any significance? I think I've tried it both with
UseFBDev true as well as UseFBDev false and it made no difference.
A final stray thought: don't know if you caught my earlier statement about
entering atyfb in /etc/modules. I created an initrd that, so far as I can
tell, contains this module. However when I boot with the video=atyfb:etc,
the module doesn't seem to load. So I resorted to adding atyfb to
/etc/modules, after which it started loading and showing up in dmesg--such
as in portions I've included in previous messages. Ideally, I should have
this module compiled into the kernel, I suppose. But I'm trying to defer
anything like that in hopes that I can see if it even works first (e.g.,
if I have sufficient video RAM to support the resolution I need atyfb
for).
Thanks, James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-10-24 5:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 16:42 framebuffer console problems James Miller
2004-10-22 19:00 ` James Miller
2004-10-22 20:08 ` Ray Olszewski
2004-10-22 21:02 ` James Miller
2004-10-22 21:49 ` James Miller
2004-10-22 20:09 ` Jim Nelson
2004-10-22 21:14 ` James Miller
2004-10-22 22:42 ` Jim Nelson
2004-10-23 4:40 ` James Miller
2004-10-23 20:06 ` framebuffer console problems: not enough video RAM? James Miller
2004-10-23 22:00 ` Ray Olszewski
2004-10-24 3:16 ` James Miller
2004-10-24 5:02 ` Ray Olszewski
2004-10-24 5:45 ` James Miller [this message]
2004-10-24 16:07 ` Ray Olszewski
2004-10-24 20:00 ` James Miller
2004-10-25 17:43 ` What distributions support dual processors 'out of the box' ? chuck gelm
2004-10-25 20:26 ` Owen Ford
2004-10-27 12:59 ` framebuffer console problems: not enough video RAM? Stephen Samuel
2004-10-23 22:17 ` Ray Olszewski
2004-10-24 3:25 ` James Miller
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=Pine.LNX.4.58.0410240025400.1287@debian-emach \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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