From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: Re: framebuffer console problems
Date: Fri, 22 Oct 2004 16:14:00 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0410221604590.1287@debian-emach> (raw)
In-Reply-To: <417968FE.3070405@verizon.net>
On Fri, 22 Oct 2004, Jim Nelson wrote:
> If you are using a 2.6 kernel (and maybe the 2.4), the kernel module for
> the ATI Rage series of graphics systems is aty128fb, not atyfb. I've
> had problems with vesafb myself, but with really old hardware (Trident
> TGUI 9660 on an old Thinkpad).
Thanks for your response, Jim. Not sure if you recall what sort of card I
mentioned, but it's an older, onboard one with low memory. According to
an infomrational page I found at
www.sharplabs.com:8668/space/video+boot+arguments , I should be using the
atyfb module (and they do list the aty128fb there for other ATI Rage
models). So, do you still think I"m using the wrong module? I really
don't know. I consider myself a total neophyte at this
> If you are always going to use the framebuffer, go ahead and compile it
> into the kernel. Saves a bit of trouble, and if you don't need modules
> to load for accessing any of the devices necessary for reaching the init
> scripts, you can probably dump the initrd altogether. It's crucial on
> distro-provided kernels, since they have to support a broad array of
> equipment, but if this is a one-off kernel for your own personal
> equipment, and you don't need modules (i. e. nforce drivers from Nvidia,
> etc.) to access the boot disk, an initrd is not necessary. None of my
> systems use them.
Yes, I have in mind to compile myself a kernel at some point. Just trying
to defer it until I have some more basic problems solved. But they seem
to appear at least as fast as I can solve them :).
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-22 21:14 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 [this message]
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
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.0410221604590.1287@debian-emach \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.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