From: Stuart Young <sgy@amc.com.au>
To: <linux-kernel@vger.kernel.org>
Cc: Erik Elmore <lk@bigsexymo.com>,
Michael Kummer <frost@packetst0rm.net>,
Stefan Smietanowski <stesmi@stesmi.com>
Subject: Re: NVIDIA kernel module
Date: Fri, 07 Dec 2001 10:57:15 +1100 [thread overview]
Message-ID: <5.1.0.14.0.20011207103824.00a17ec0@mail.amc.localnet> (raw)
In-Reply-To: <Pine.LNX.4.40.0112061618000.240-100000@warp4>
In-Reply-To: <3C0F8A5E.6060501@stesmi.com>
At 04:19 PM 6/12/01 +0100, Michael Kummer wrote:
>any1 got the NVIDIA module working when eg. the nvidia framebuffer code is
>enabled?
The RivaFB code and the Nvidia module stamp all over each other afaik. Have
you tried this with their latest binary module (1.0-2313)? Least that now
plays nicely with devfs. Only real way (afaik) is unload the RivaFB module
when the Nvidia module is loaded, and vice versa.
Of course, this means that while X is running the consoles won't have
FrameBuffer, but hey, them's the trade-offs. You can do this in
modules.conf (modutils stuff) using the pre-install option.
eg:
pre-install NVdriver rmmod rivafb
If the NVdriver module is unloaded when you quit X (depends if it was
dynamically loaded by X, which "should" work if modutils isn't broken [not
usual] and the appropriate stuff is placed there by the Nvidia install),
you could use a modutils post-remove option.
eg:
post-remove NVdriver modprobe rivafb
Of course, there is no guarantee that it will unload immediately (if at
all), so you may lose the FrameBuffer till NVdriver is purged/removed. I
have no idea if this would work, as I don't use the RivaFB module at all.
If I got this wrong, I'm sure Keith Owens will enlighten me (probably with
a large clue stick - since it's in relation to one of his pet hates,
Nvidia). *grin*
Stuart Young - sgy@amc.com.au
(aka Cefiar) - cefiar1@optushome.com.au
[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]
next prev parent reply other threads:[~2001-12-06 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 23:22 Erik Elmore
2001-12-05 23:29 ` Jeffrey H. Ingber
2001-12-06 2:27 ` Erik Elmore
2001-12-05 23:38 ` Miles Lane
2001-12-05 23:39 ` Chris Wedgwood
2001-12-06 15:10 ` Stefan Smietanowski
2001-12-06 15:19 ` Michael Kummer
2001-12-06 23:57 ` Stuart Young [this message]
[not found] <Pine.LNX.4.33.0112051719260.13083-100000@erik.bigsexymo.co m>
2001-12-05 23:46 ` Stuart Young
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=5.1.0.14.0.20011207103824.00a17ec0@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=frost@packetst0rm.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@bigsexymo.com \
--cc=stesmi@stesmi.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
all inboxes | Powered by JetHome®