--- Begin Message --- In a message dated 1/18/2002 12:37:03 PM Mountain Standard Time, [EMAIL PROTECTED] writes:


Dave,

You must have missed my prior response to this:
This sounds like a problem, not necessarily something you did wrong.  Try
doing a "depmod -ae" command manually to see what errors get generated.
Hopefully that will indicate what symbols are missing from what module.

Mark Post


Guess I'm confused on why the RH OCO worked ok for my ramdisk
and not 2.4.9 system??  Seems like something just didn't get copied over to 2.4.9
by instoco or something like that??


Anyways...the depmod -ae showed about a dozen mods like this:
alloc_skb_Rsmp_nnnnnnn
init_etherdev_Rsmp_nnnnnn
init_fddidev_Rsmp_nnnnnn
eth_type_trans_Rsmp_nnnnnn
chandev_initnetdevice_Rsmp_nnnnn
-kfree_skb_Rsmp_nnnnnnn
etc...

Also... my lcs.o in /lib/modules/ibm (the oco modfied one..) looks like this:

-rw-r--r--    1 root     root        39768 Jan 17 17:22 lcs.o

and the one in   /lib/modules/2.4.9-17tape/kernel/net  looks like this:

-rw-r--r--    1 root     root        39696 Jan 18 14:52 lcs.o




--- End Message ---


Reply via email to