mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Antony Suter <suterant@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Cc: m.c.p@kernel.linux-systeme.com, Ralf.Hildebrandt@charite.de,
	sleightofmind@xs4all.nl
Subject: Re: nvidia binary driver broken with 2.6.6-rc{1,2}, reverting a -mm patch makes it work
Date: Sat, 24 Apr 2004 02:43:05 +1000	[thread overview]
Message-ID: <1082738585.26812.14.camel@hikaru.lan> (raw)

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

Marc wrote:
> On Friday 23 April 2004 10:30, Ralf Hildebrandt wrote:
> Hi Ralf,
> 
> > > Because of a patch from -mm merged in mainstream i cannot get the
nvidia
> > > binary to work with the 2.6.6 release candidates. I get this
message
> > > when doing `modprobe nvidia`:
> 
> > $ uname -a
> > Linux hummus2 2.6.6-rc2-bk1 #1 Thu Apr 22 14:15:08 CEST 2004 i686
> > GNU/Linux
> > nvidia works like a charm here.
> 
> that's the problem. It works for many people, for many others not. It
always 
> worked fine for me too but I had to rip that out of my 2.6-WOLK tree
to 
> satisfy all people using wolk and lack of knowledge to fix that by
myself.

I had this problem, and I resolved it for me like this: In the
NVIDIA-Linux-x86-1.0-5336-pkg?.run archive from Nvidia are multiple make
files. By default, my distro was using the make file "makefile" and it
stopped working. I switched to using "Makefile.kbuild", which is
oriented to 2.6 kernels, and it works again. Comments within
Makefile.kbuild touch on changes to module handling in 2.6 compared to
2.4.

-- 
- Antony Suter  (suterant users sourceforge net)  "Bonta"
- "...through shadows falling, out of memory and time..."

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-04-23 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 16:43 Antony Suter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-23  8:20 Rik van Ballegooijen
2004-04-23  8:30 ` Ralf Hildebrandt
2004-04-23  8:37   ` Marc-Christian Petersen
2004-04-23  8:41     ` Ralf Hildebrandt
2004-04-23 14:36 ` Brian Gerst

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=1082738585.26812.14.camel@hikaru.lan \
    --to=suterant@users.sourceforge.net \
    --cc=Ralf.Hildebrandt@charite.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@kernel.linux-systeme.com \
    --cc=sleightofmind@xs4all.nl \
    /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®