From: Willy Tarreau <willy@w.ods.org>
To: George Nychis <gnychis@cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cannot load *any* modules with 2.4 kernel
Date: Sun, 21 May 2006 07:48:26 +0200 [thread overview]
Message-ID: <20060521054826.GA14334@w.ods.org> (raw)
In-Reply-To: <446FAEE3.6060003@cmu.edu>
On Sat, May 20, 2006 at 08:05:55PM -0400, George Nychis wrote:
> Okay, so heres what I did. I downloaded modutils version 2.4.27 and
> extracted it to /usr/local/modutils
>
> Then in my 2.4.32 kernel's Makefile, I changed the DEPMOD variable to
> point to /usr/local/modutils/sbin/depmod
>
> Then I build the kernel with:
> make dep && make bzImage modules modules_install && make install
>
> So then my initrd gets generated, I reboot to the 2.4.32 kernel, and
> thats where i'm at now.
>
> So then for instance I goto /lib/modules/2.4.32/net and do:
> /usr/local/modutils/sbin/insmod 8390.o
>
> and I see all those unresolved symbols
Hmmm 8390.o needs crc32.o (or maybe you built it into your kernel).
Could you please :
- grep 8390.o /lib/modules/2.4.32/modules.dep
- post the exact list of unresolved symbols that insmod outputs
- grep 2 or 3 of them in /proc/ksyms (eg: printk)
- post your .config so that we can find a way to reproduce your problem.
> So maybe now that you have more info, we can figure something out.
By the time you do this, it would also be interesting to retry without
CONFIG_MODVERSIONS. Oh, and please report your gcc and binutils versions
so that we can be as close as possible to your conditions when trying
to reproduce.
> Thanks!
> George
Regards,
willy
next prev parent reply other threads:[~2006-05-21 5:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 16:10 cannot load *any* modules with 2.4 kernel George Nychis
2006-05-20 16:25 ` Willy Tarreau
2006-05-21 0:05 ` George Nychis
2006-05-21 5:48 ` Willy Tarreau [this message]
2006-05-21 7:00 ` George Nychis
2006-05-21 8:40 ` Willy Tarreau
2006-05-22 1:53 ` Keith Owens
2006-05-22 13:21 ` George Nychis
2006-05-21 7:32 ` Nick Warne
2006-05-21 14:43 ` George Nychis
2006-05-21 15:34 ` Nick Warne
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=20060521054826.GA14334@w.ods.org \
--to=willy@w.ods.org \
--cc=gnychis@cmu.edu \
--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