From: Christian Unger <chakkerz@optusnet.com.au>
To: Paul Misner <paul@misner.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Nvidia drivers and 2.6.x kernel
Date: Thu, 22 Jan 2004 11:05:12 +1100 [thread overview]
Message-ID: <200401221105.12148.chakkerz@optusnet.com.au> (raw)
In-Reply-To: <200401211744.04064.paul@misner.org>
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
>
> 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.
One interesting error / warning i get during boot is this (from /var/log/
syslog) :
Jan 22 10:43:08 stormcrow kernel: nvidia: version magic '2.6.1 preempt K7
gcc-3.2' should be '2.6.1 preempt K7 gcc-3.3'
Jan 22 10:46:15 stormcrow kernel: nvidia: version magic '2.6.1 preempt K7
gcc-3.2' should be '2.6.1 preempt K7 gcc-3.3'
Not sure what to make of this. I know that 4496 had issues with the gcc
version i was running a while backed, and i had to hack the installer script
to ignore that (though i'm sure there is a switch for this stuff ... i was
over reading at that point).
As for the XFree log ... i don't have that one ...
--
with kind regards,
Christian Unger
"You don't need eyes to see, you need vision" (Faithless - Reverence)
Mobile: 0402 268904
Internet: http://naiv.sourceforge.net
NAIV Status:
Stable Testing Development
0.2.3r2 0.3.0 0.3.1 - File Handling
"May there be mercy on man and machine for their sins" (Animatrix)
next prev parent reply other threads:[~2004-01-22 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 23:12 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 [this message]
2004-01-22 0:24 ` Paul Misner
2004-01-22 0:38 ` Rob Couto
2004-01-22 19:19 ` Josh McKinney
-- 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=200401221105.12148.chakkerz@optusnet.com.au \
--to=chakkerz@optusnet.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@misner.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
Powered by JetHome