From: Janusz Dziemidowicz <rraptorr@nails.eu.org>
To: Oded Shimon <ods15@ods15.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RivaFB on Geforce FX 5200
Date: Tue, 9 Nov 2004 21:11:18 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.61.0411092106150.2007@cube.lan> (raw)
In-Reply-To: <200411091458.06585.ods15@ods15.dyndns.org>
On Tue, 9 Nov 2004, Oded Shimon wrote:
> 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...
Hi,
I assume You are trying to use rivafb with nvidia binary drivers? If
that's the case, then here's an excerpt from NVIDIA README file:
Q: My system hangs when vt-switching if I have rivafb enabled.
A: Using both rivafb and the NVIDIA kernel module at the same time is
currently broken. In general, using two independent software drivers
to drive the same piece of hardware is a bad idea.
So it is unlikely to make this two drivers to work together.
--
Janusz Dziemidowicz
rraptorr@nails.eu.org
next prev parent reply other threads:[~2004-11-09 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 12:58 Oded Shimon
2004-11-09 20:11 ` Janusz Dziemidowicz [this message]
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=Pine.LNX.4.61.0411092106150.2007@cube.lan \
--to=rraptorr@nails.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ods15@ods15.dyndns.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
all inboxes | Powered by JetHome®