From: Erik Mouw <erik@harddisk-recovery.com>
To: Ben Srour <srour@cs.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiling modules after 2.4.* --> 2.6.0 upgrade
Date: Tue, 23 Dec 2003 17:25:15 +0100 [thread overview]
Message-ID: <20031223162515.GD26750@bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0312230211500.28609-100000@data.upl.cs.wisc.edu>
On Tue, Dec 23, 2003 at 02:20:06AM -0600, Ben Srour wrote:
> I'm attempting to port a module I wrote for the 2.4 series to 2.6 but I
> get the following error when I try and insmod:
>
> root@dimension# /usr/sbin/insmod gpstest.o
> insmod: error inserting 'gpstest.o': -1 Invalid module format
> root@dimension#
You want the .ko file, not the .o file. See also:
- http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt
- http://lwn.net/Articles/driver-porting/
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2003-12-23 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 5:11 2.6.0-mm1 Andrew Morton
2003-12-23 5:27 ` 2.6.0-mm1 Valdis.Kletnieks
2003-12-23 5:28 ` 2.6.0-mm1 Marcos D. Marado Torres
2003-12-23 5:28 ` 2.6.0-mm1 Andrew Morton
2003-12-23 5:40 ` 2.6.0-mm1 Stan Bubrouski
2003-12-23 7:57 ` 2.6.0-mm1 Andrew Walrond
2003-12-23 8:20 ` compiling modules after 2.4.* --> 2.6.0 upgrade Ben Srour
2003-12-23 16:25 ` Erik Mouw [this message]
2003-12-23 16:27 ` Jonathan Corbet
2003-12-23 16:39 ` Randy.Dunlap
2003-12-23 7:30 ` 2.6.0-mm1 Martin J. Bligh
2003-12-23 17:29 ` 2.6.0-mm1 Tom Rini
2003-12-23 17:31 ` 2.6.0-mm1 Tom Rini
2003-12-23 21:08 ` 2.6.0-mm1 viro
2003-12-24 13:09 ` 2.6.0-mm1 William Lee Irwin III
2003-12-24 14:26 ` 2.6.0-mm1 William Lee Irwin III
2003-12-24 15:39 ` 2.6.0-mm1 Gene Heskett
2003-12-28 3:43 ` [PATCH] 2.6.0-mm1 Ramón Rey Vicente
2003-12-28 10:58 ` 2.6.0-mm1 Christoph Hellwig
2003-12-28 19:49 ` 2.6.0-mm1 Andrew Morton
2003-12-28 19:52 ` 2.6.0-mm1 Christoph Hellwig
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=20031223162515.GD26750@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srour@cs.wisc.edu \
/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