From: "Matt H." <lkml@lpbproductions.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Invalid module format ?
Date: Fri, 11 Jun 2004 17:51:15 -0700 [thread overview]
Message-ID: <200406111751.15408.lkml@lpbproductions.com> (raw)
In-Reply-To: <20040612003846.GA4275@werewolf.able.es>
J.A. Magallon ,
Grab the latest offical nvidia driver 5336 , then patch it with the patch
aviable from http://www.minion.de/nvidia.html ( there patch allows the nvidia
driver to compile and work under gcc 3.4 ).
You also may want to make sure your using the latest module-init-tools.
Matt H.
On Friday 11 June 2004 5:38 pm, J.A. Magallon wrote:
> Hi all...
>
> First of all, I'm aware of the 'ask the vendor' answer. I just would like
> the reasons.
>
> With gcc-3.4.1 cvs, the nvidia module is miscompiled or something.
> The same sources that build and install with gcc-3.3, now build and give
> me this:
>
> werewolf:~# modinfo nvidia
> filename: /lib/modules/2.6.7-rc3-jam1/video/nvidia.ko
> license: NVIDIA
> werewolf:~# modprobe nvidia
> FATAL: Error inserting nvidia
> (/lib/modules/2.6.7-rc3-jam1/video/nvidia.ko): Invalid module format
>
> syslog:
>
> Jun 12 02:35:44 werewolf kernel: No module found in object
>
> werewolf:~# cat /proc/version
> Linux version 2.6.7-rc3-jam1 (root@werewolf.able.es) (gcc version 3.4.1
> (Mandrakelinux (Cooker) 3.4.1-0.2mdk)) #1 SMP Fri Jun 11 01:49:52 CEST 2004
>
> Any idea ?
next prev parent reply other threads:[~2004-06-12 0:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 0:38 J.A. Magallon
2004-06-12 0:51 ` Matt H. [this message]
2004-06-12 0:55 ` J.A. Magallon
2006-05-18 14:01 Invalid module format? Brian D. McGrew
2006-05-19 1:50 ` Arjan van de Ven
2006-05-19 17:11 Brian D. McGrew
2006-05-19 17:19 ` Randy.Dunlap
2006-05-19 17:55 ` Randy.Dunlap
2006-05-19 21:35 ` Sam Ravnborg
2006-05-19 17:23 Brian D. McGrew
2006-05-19 18:38 Brian D. McGrew
2006-05-19 20:21 ` Randy.Dunlap
2006-05-20 17:37 ` Randy.Dunlap
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=200406111751.15408.lkml@lpbproductions.com \
--to=lkml@lpbproductions.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@lpbproduction.scom \
/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®