All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Tscharner <starfire@dplanet.ch>
To: Guido Volpi <lugburz@tiscalinet.it>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: oproblem with nvidia driver
Date: Tue, 26 Feb 2002 19:28:15 +0100	[thread overview]
Message-ID: <20020226192815.4061fb76.starfire@dplanet.ch> (raw)
In-Reply-To: <200202261447.g1QElLO02468@localhost.localdomain>
In-Reply-To: <200202261447.g1QElLO02468@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Tue, 26 Feb 2002 14:47:21 +0000
Guido Volpi <lugburz@tiscalinet.it> wrote:

> it's all right: nvidia modules depend only by nvidia, but i don't understand 
> why a module that is perfect (or so) with 2.4.17 in 2.4.18-rc4 is no more 
> usabily.

I think you're mixing up two different things.

The NVidia drivers from NVidia will work with the 2.4.x kernel series

But
in the 2.5.x kernel series internal stuff has been changed, and therefore, the modules won't work any longer...

Regards
	Andreas
-- 
Andreas Tscharner                                     starfire@dplanet.ch
-------------------------------------------------------------------------
"Programming today is a race between software engineers striving to build 
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning." -- Rich Cook 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2002-02-26 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 14:47 oproblem with nvidia driver Guido Volpi
2002-02-26 14:27 ` DevilKin
2002-02-26 14:38 ` J.A. Magallon
2002-02-26 15:11 ` Richard B. Johnson
2002-02-26 17:39 ` J Sloan
2002-02-26 18:28 ` Andreas Tscharner [this message]

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=20020226192815.4061fb76.starfire@dplanet.ch \
    --to=starfire@dplanet.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lugburz@tiscalinet.it \
    /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.