From: Ralf Baechle <ralf@linux-mips.org>
To: eric@egaulin.com
Cc: linux-mips@linux-mips.org
Subject: Re: insmod: ELF file not for this architecture
Date: Thu, 23 Mar 2006 23:30:08 +0000 [thread overview]
Message-ID: <20060323233008.GA4030@linux-mips.org> (raw)
In-Reply-To: <7f0c7cce0603231337g3d6534c9p@mail.gmail.com>
On Thu, Mar 23, 2006 at 04:37:56PM -0500, Eric Gaulin wrote:
> I built linux 2.6.11 with amd patch for Alchemy Au1200 and also built the
> mae-driver.ko. When i load the driver i get this error "insmod: ELF file not
> for this architecture". I was told on #elinux irc channel tha i need to
> enable ELF support in my kernel configuration! There is no such option!
Good and correct advice but yet besides the point, so let's sort this out.
The #elinux guys were speaking about the CONFIG_BINFMT_ELF option which
needs to be enabled for the kernel to execute ELF applications. Note
I'm saying applications, not kernel modules. For Linux/MIPS all
applications use the ELF format, so there is no point in ever disabling
this option and so all the default configuration files included with the
kernel have this option set.
Now, what does your error message actually mean? First of all it's an
error message which seems to come from the old modutils, so you seem to
be using Linux 2.4 kernel. Nice fossil, btw ;-) And the message simply
indicates you're trying to load a non-MIPS binary into a MIPS system.
Chances are you build your module using the host instead of the cross
compiler - something like that. Try ``file mae-driver.ko´´.
For Linux/MIPS specific advice you may want to drop by in #mipslinux.
Ralf
prev parent reply other threads:[~2006-03-23 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 21:37 insmod: ELF file not for this architecture Eric Gaulin
2006-03-23 23:30 ` Ralf Baechle [this message]
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=20060323233008.GA4030@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=eric@egaulin.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.