From: George Nychis <gnychis@cmu.edu>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cannot load *any* modules with 2.4 kernel
Date: Sat, 20 May 2006 20:05:55 -0400 [thread overview]
Message-ID: <446FAEE3.6060003@cmu.edu> (raw)
In-Reply-To: <20060520162529.GT11191@w.ods.org>
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
So maybe now that you have more info, we can figure something out.
Thanks!
George
Willy Tarreau wrote:
> Hi,
>
> On Sat, May 20, 2006 at 12:10:18PM -0400, George Nychis wrote:
>> Hi,
>>
>> I boot two kernels, a 2.6.9 kernel and just recently built a 2.4.32 kernel
>>
>> In the 2.4.32 kernel I have =y for:
>> CONFIG_MODULES
>> CONFIG_MODVERSIONS
>> CONFIG_KMOD
>>
>> I then build my kernel, with some modules, install the modules, and boot
>> my 2.4.32 kernel successfully
>>
>> when i do lsmod, it is completely empty, no modules are loaded. This
>> only happens for my 2.4.32 kernel though, modules load fine in 2.6.9
>
> What's your modutils version ? -> lsmod -V
> You must use modutils and not modules-utils under 2.4, and I suspect
> that if you jumped back from 2.6 to 2.4, you might not have the right
> package. Note that modules-utils contains a wrapper to call the right
> modutils when you are running 2.4, so you should really do lsmod -V
> when running 2.4.
>
>> If i try to manually insert with insmod or modprobe, i get unresolved
>> external symbols for things that I am sure should be resolved... for
>> example, i get unresolved external symbol for printk
>>
>> I'll give some other common unresolved smybols and maybe someone can
>> point me in the right direction of what else i need to specify to you
>> guys so that you can help me out further.
>>
>> prinkt
>> add_timer
>> dev_mc_add
>> CardServices
>> kfree
>> cpu_raise_softirq
>> free_irq
>> kmalloc
>>
>> Thanks!
>> George
>
> Regards,
> Willy
>
>
next prev parent reply other threads:[~2006-05-21 0:04 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 [this message]
2006-05-21 5:48 ` Willy Tarreau
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=446FAEE3.6060003@cmu.edu \
--to=gnychis@cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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