From: Arrigo Benedetti <arrigo@vision.caltech.edu>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: problem with insmod
Date: Thu, 04 Nov 2004 11:26:52 -0800 [thread overview]
Message-ID: <418A827C.9090802@vision.caltech.edu> (raw)
In-Reply-To: <418A35ED.3090400@gmx.net>
evilninja wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Arrigo Benedetti schrieb:
>
>
>>After some research I found that to load a module on the 2.6 kernel one
>>
>>
>
>yes, http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt is a good
>start for 2.4 -> 2.6 upgrades.
>
>
>
>>So I compile and install module-init-tools, but I get the same error.
>>Does anyone know what's going on?
>>
>>
>
>hm, are you sure the new "insmod" and "modprobe" are the *right* ones?
>the PATH variable will help here or try to specify the exact path on the
>cmd line. here i have:
>
>evil@prinz:~$ /sbin/modprobe -V
>module-init-tools version 3.1-pre6
>vil@prinz:~$ file /sbin/modprobe*
>/sbin/modprobe: ELF 32-bit LSB executable, Intel 80386, [...]
>/sbin/modprobe.Lmodutils: symbolic link to `insmod'
>/sbin/modprobe.modutils: symbolic link to `insmod.modutils'
>
>
>
Yes, I have verified that. Someone has also suggested to check that the
compiler used to build the module
is the same compiler that build the kernel. The Makefile is below and it
seems that this is also ok.
-Arrigo
ifndef KERNELRELEASE
LINUX ?= /usr/src/linux-2.6
PWD := $(shell pwd)
all:
$(MAKE) -C $(LINUX) SUBDIRS=$(PWD) modules
clean:
rm -f *.o *.ko *~ core .depend *.mod.c *.cmd
else
obj-m := empty.o
endif
next prev parent reply other threads:[~2004-11-04 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 1:40 problem with insmod Arrigo Benedetti
2004-11-04 14:00 ` evilninja
2004-11-04 19:26 ` Arrigo Benedetti [this message]
2004-11-04 23:31 ` evilninja
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=418A827C.9090802@vision.caltech.edu \
--to=arrigo@vision.caltech.edu \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).