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: Sun, 21 May 2006 03:00:39 -0400 [thread overview]
Message-ID: <44701017.8000803@cmu.edu> (raw)
In-Reply-To: <20060521054826.GA14334@w.ods.org>
Thanks for all the help Willy,
Nothing from the grep:
[root@emu-5 net]# grep 8390.o /lib/modules/2.4.32/modules.dep
[root@emu-5 net]#
Exact list:
enable_irq
eth_type_trans
__kfree_skb
alloc_skb
ether_setup
crc32_le
kmalloc
cpu_raise_softirq
alloc_netdev
__out_of_line_bug
disable_irq_nosync
netif_rx
skb_over_panic
bitreverse
jiffies
softnet_data
prink
__const_udelay
Grepping 2 or 3:
[root@emu-5 net]# grep enable_irq /proc/ksyms
c010a5e0 enable_irq_R__ver_enable_irq
c0343610 matroxfb_enable_irq_R__ver_matroxfb_enable_irq
[root@emu-5 net]# grep printk /proc/ksyms
c011aee0 printk_R__ver_printk
[root@emu-5 net]# grep kmalloc /proc/ksyms
c0132c60 kmalloc_R__ver_kmalloc
c03c07e0 sock_kmalloc_R__ver_sock_kmalloc
binutils version: 2.15.92.0.2 20040927
gcc: 3.4.2 20041017
My .config can be found here:
http://www.andrew.cmu.edu/user/gnychis/.config
And I will try taking out CONFIG_MODVERSIONS support and let you know
how it goes!
By the way, i'm not keen on inserting 8390.o into the kernel, it was
simply the first thing i saw in my /lib/modules/2.4.32 directory, my
goal is to get any module at all to insert, because it seems none will
insert.
Thanks again!
George
Willy Tarreau wrote:
> 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 6:58 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
2006-05-21 7:00 ` George Nychis [this message]
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=44701017.8000803@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 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.