linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: evilninja <evilninja@gmx.net>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: problem with insmod
Date: Thu, 04 Nov 2004 15:00:13 +0100	[thread overview]
Message-ID: <418A35ED.3090400@gmx.net> (raw)
In-Reply-To: <4189888E.5070906@vision.caltech.edu>

-----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'

Christian.
- --
BOFH excuse #391:

We already sent around a notice about that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBijXsC/PVm5+NVoYRAkspAJ9v5khRZVwpPxsmTL/v5tYKUUkrDgCg2np7
85mBGkq+rCRLwO7DJMNjoQA=
=xfHv
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-11-04 14:06 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 [this message]
2004-11-04 19:26   ` Arrigo Benedetti
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=418A35ED.3090400@gmx.net \
    --to=evilninja@gmx.net \
    --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).