mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cefiar <cefiar1@optushome.com.au>
To: Gregor Essers <gregor.essers@web.de>, linux-kernel@vger.kernel.org
Subject: Re: bug of Nvidia (0.9.5) Drivers in 2.4 Kernel Enviroment
Date: Sat, 06 Jan 2001 14:22:35 +1100	[thread overview]
Message-ID: <4.3.2.7.2.20010106140627.00b06c60@mail> (raw)
In-Reply-To: <01010522072100.03671@saintx.saintx.de>

At 10:07 PM 5/01/01 +0100, Gregor Essers wrote:
> From the pre9 relaese to the final of the 2.4 Kernel i become this Errors,
>can someone help me or have someone an idea what this mean ??.
>
>I will build this with the src.rpm from Nvidia with the spec file
>
>In file included from nv.c:52:
>nv.h:131: warning: #warning This driver is not officially supported on
>post-2.2
>kernels
>nv.c: In function `nv_lock_pages':
>nv.c:556: warning: implicit declaration of function `mem_map_inc_count'
>nv.c: In function `nv_unlock_pages':
>nv.c:583: warning: implicit declaration of function `mem_map_dec_count'
>nv.c: At top level:
>nv.c:853: unknown field `unmap' specified in initializer
>nv.c:853: warning: initialization from incompatible pointer type
>make: *** [nv.o] Fehler 1
>Bad exit status from /var/tmp/rpm-tmp.37085 (%build)

You need to patch the Nvidia kernel driver to handle changes made in the 
2.4 tree. You can either:

1> Get on irc (Server: irc.openprojects.net, Channel #nvidia) and request 
the patch from there. (You need to be able to do DCC transfers for this to 
work). There is patches for 2.4.0-test1[0-3] and for 
2.4.0-[prerelease/final], so get what you need that way. The bot to request 
from is usually iCE-DCC, and you can request a list using '/msg iCE-DCC 
xdcc list' and request a file using eg: '/msg iCE-DCC xdcc send #10' (if 
you wanted file 10 that is).

2> Alternatively, if you e-mail me, I could probably forward you the patch 
or, if people don't mind too much, I could post it to the list (I'll wait 
for comments on this first!).

The patch is about 1k for test10, and about 3k for prerelease/final. 
Remember, this patches Nvidia's driver shim source code, and not the 
kernel. You could unpack the .src.rpm and add the patch to the compile 
process if you were really game, but I did it from the .tar.gz and it works 
fine for me. YMMV of course.

BTW: Common problem is that people complain that the make still gets 
includes wrong. Make sure you compile the kernel and it's modules 
completely. I compiled the kernel and modules, rebooted into the new 
kernel, and then compiled the Nvidia driver. The last step of Nvidia's make 
process (for the .tar.gz) is to actually insmod the driver to make sure it 
worked, which will probably fail on any other version of the kernel.

Of note: Nvidia have a new driver in the works, that should be much nicer 
re: kernel interface.

--
  -=[ Stuart Young (Aka Cefiar) ]=-------------------------------
  | http://amarok.glasswings.com.au/ | cefiar1@optushome.com.au |
  ---------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-06  3:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 21:07 Gregor Essers
2001-01-06  3:22 ` Cefiar [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=4.3.2.7.2.20010106140627.00b06c60@mail \
    --to=cefiar1@optushome.com.au \
    --cc=gregor.essers@web.de \
    --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 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®