From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Nvidia drivers and 2.6.x kernel
Date: Thu, 22 Jan 2004 14:19:53 -0500 [thread overview]
Message-ID: <20040122191953.GA16677@forming> (raw)
In-Reply-To: <200401211824.10470.paul@misner.org>
On approximately Wed, Jan 21, 2004 at 06:24:10PM -0600, Paul Misner wrote:
> On Wednesday 21 January 2004 06:05 pm, Christian Unger wrote:
> > About module-init-tools ... dunno ... never heard of it, I'm on Slackware
> > 9.1 so ... dunno ... Not sure. But like you say, if i could not initalize
> > modules the nvidia module should be the least of my worries, plus
> > everything loads in 2.4.22
>
> The 2.6 kernel needs new tools to load the kernel modules, because they have a
> different format (not just a different extension with .ko).
> module-init-tools provides those necessary upgrades, and also aids in
> creating /etc/modprobe.conf, which is used instead of /etc/modules.conf under
> the 2.6 kernels for loading modules on startup. If you don't have
> module-init-tools, then I'm not surprised you are having problems. You
> probably need an updated mkinitrd as well if you are using an initrd on
> system startup.
>
> They should be at http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
>
> You probably want to read a document that summarized the changes that happened
> in 2.6, which is where the link above was located. It is
> http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt
>
> Not knowing much about Slackware, I couldn't give you much help about where
> the best place to get your tools from might be, except for the source above.
>
> > > What messages do you get about what is going wrong? What happens when
> > > you so a modprobe nvidia? What does your log file from XFree show?
> >
> > on make install i get:
> > FATAL: Error inserting nvidia (/lib/modules/2.6.1/kernel/drivers/video/
> > nvidia.ko): Invalid module format
> >
> > That's the same thing that modprobe nvidia gets.
> > I'll check the nv thing out.
> >
My guess is you need to have a "built" kernel tree. Basically just
build the kernel, install, reboot, then without touching the kernel
tree you built rebuild the nvidia driver. I hope that makes sense.
--
Josh McKinney | Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
| They that can give up essential liberty
Linux, the choice -o) | to obtain a little temporary safety deserve
of the GNU generation /\ | neither liberty or safety.
_\_v | -Benjamin Franklin
next prev parent reply other threads:[~2004-01-22 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 23:12 Nvidia drivers and 2.6.x kernel Christian Unger
2004-01-21 23:19 ` Tomasz Torcz
2004-01-21 23:28 ` Christian Unger
2004-01-22 8:38 ` Robin Rosenberg
2004-01-21 23:28 ` Diego Calleja
2004-01-21 23:44 ` Paul Misner
2004-01-22 0:05 ` Christian Unger
2004-01-22 0:24 ` Paul Misner
2004-01-22 0:38 ` Rob Couto
2004-01-22 19:19 ` Josh McKinney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 18:15 Bob Gill
2004-01-21 23:04 Christian Unger
[not found] ` <400FB4AA.8000109@yahoo.com.br>
2004-01-22 11:52 ` Christian Unger
2004-01-22 12:12 ` Kieran
2004-01-22 22:42 ` Christian Unger
[not found] ` <401052C6.7040500@ihateaol.co.uk>
2004-01-25 23:24 ` Christian Unger
2004-01-27 22:49 ` Charles Shannon Hendrix
2004-01-22 23:48 ` Charles Shannon Hendrix
2004-01-22 23:40 ` Charles Shannon Hendrix
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=20040122191953.GA16677@forming \
--to=forming@charter.net \
--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