From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Invalid module format ?
Date: Sat, 12 Jun 2004 02:55:24 +0200 [thread overview]
Message-ID: <20040612005524.GA5506@werewolf.able.es> (raw)
In-Reply-To: <200406111751.15408.lkml@lpbproductions.com> (from lkml@lpbproductions.com on Sat, Jun 12, 2004 at 02:51:15 +0200)
On 06.12, Matt H. wrote:
> 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 ).
>
I've got that patches ;).
I think the problem is gcc-3.4.1.
Why can a module give that error ?
Any header info, some MODULE_INFO, what ?
werewolf:~> rpm -q module-init-tools
module-init-tools-3.0-2mdk
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Cooker) for i586
Linux 2.6.5-rc1-jam3 (gcc 3.4.1 (Mandrakelinux (Cooker) 3.4.1-0.3mdk)) #3
next prev parent reply other threads:[~2004-06-12 0:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 0:38 Invalid module format ? J.A. Magallon
2004-06-12 0:51 ` Matt H.
2004-06-12 0:55 ` J.A. Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20040612005524.GA5506@werewolf.able.es \
--to=jamagallon@able.es \
--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