From: Oded Shimon <ods15@ods15.dyndns.org>
To: linux-kernel@vger.kernel.org
Subject: RivaFB on Geforce FX 5200
Date: Tue, 9 Nov 2004 14:58:06 +0200 [thread overview]
Message-ID: <200411091458.06585.ods15@ods15.dyndns.org> (raw)
Hi,
I'm trying to get the rivafb module to work on my Geforce FX, i used the
rivatv program as reference to simply add the PCI device to the list of
supported devices in riva/fbdev.c . After which I was surprised to find out
that after compiling and making a module it successfully modprobed, created
the /dev/fb device, and MPlayer and X used it happily.
I now managed to get it to work for FB console as well, but it has some
issues, and I really have no idea about the causes and solutions to these
problems.
One problem is when switching from X back to FB console, I can still see the X
cache (at the different res and color depth, it simply looks like noise...),
until some kind of modification has happenned in the console.
If i run any kind of program which modifies the frame buffer, for ex. fbset or
ppmtofb, the FB console is irreversibly ruined until reboot. (it looks mostly
like noise which you can barely make out the console text underneath).
The worst problem - no penguin at boot up. :( There is a black bar in the
area where its supposed to be, but no image...
My guess is the cause for most of these problem is me causing the driver to
think it can support my card, when it doesn't really have all the kinks
sorted out...
Up until now I've always used vesafb, and the "nvidia" binary module for X...
vesa is slow though, which is why I am trying to get rivafb to work.. I also
recently realized that the free "nv" module support geforce FX, and it works
good on my X...
- ods15
next reply other threads:[~2004-11-09 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 12:58 Oded Shimon [this message]
2004-11-09 20:11 ` RivaFB on Geforce FX 5200 Janusz Dziemidowicz
2004-11-09 20:32 ` Oded Shimon
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=200411091458.06585.ods15@ods15.dyndns.org \
--to=ods15@ods15.dyndns.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.