I meant to post this to the list (which I have now done) but I think that I sent to Mark's address by mistake.
MJ Ray markj@cloaked.freeserve.co.uk wrote:
I have the recollection that there are modules not obviously related to iptables that are required. They are not built automatically because the configuration system can't cope with it. Here are relevant options on this box. Anything not mentioned is not set or really irrelevant. See how yours differ:
I religiously set my options to match your list but still got the same unresolved symbols list. So I thought I'd start from scratch. I deleted the kernel source code directory and re-unpacked the source code. Reloaded my saved configuration and re-compiled.
Now I'm even more mystified. I get an even longer list which includes some network drivers( 3c59x) which appeared to be ok before:
depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/drivers/net/3c59x.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/drivers/net/8390.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/drivers/net/dummy.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/drivers/net/pcmcia/pcnet_cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/drivers/net/ppp_async.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/drivers/net/ppp_generic.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/fs/smbfs/smbfs.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_conntrack.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv4/netfilter/ipt_MASQUERADE.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv4/netfilter/ipt_REJECT.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv4/netfilter/iptable_filter.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv4/netfilter/iptable_nat.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv6/ipv6.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv6/netfilter/ip6_tables.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/ipv6/netfilter/ip6table_filter.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/netlink/netlink_dev.o depmod: *** Unresolved symbols in /lib/modules/2.4.18/kernel/net/sunrpc/sunrpc.o
I can't help feeling that I'm doing (not doing) something very obvious.
I have compiled kernels many times in the past and have never had any trouble that wasn't of my own making.
On Sat, 6 Apr 2002 bsamuels@beenthere-donethat.org.uk wrote:
From the clean source code tree I did:
make dep make bzImage make modules make modules_install
copy bzImage and System.map to /boot. run lilo.
ok, a new thing to try =) "apt-get install kernel-package" then do your normal make (menu/x)config to build your kernel config then you can do a make-kpkg --revision whatever1.0 kernel_image and you will get a resultant .deb file in /usr/src that you can dpkg -i and this will have done all of the building and installing and running lilo that you need if it still doesn't work then something very odd is happening.
Adam
Adam Bower abower@thebowery.co.uk wrote:
if it still doesn't work then something very odd is happening.
Something very odd is happening - me!
I thought that I would have one last try before leaping off the roof and I have just rebooted into my 2.4 kernel with no 'unresolved symbols' messages.
I honestly don't know what I did or didn't do to make it work this time. I do, however, have 66 excuses.
One is that when the clocks change it makes me *really* tired for about a week.
The other 65 are years! When I was young my memory was never very good and I can assure you that it does *not* improve with the passing years.
Sorry for the wasted time everybody.
I have now tried endoshield and it seems to work. What a relief.
With reference to Adam's suggestion regarding kernel-package I prefer the old fashioned way at present but I'll have a look at it one day.
Many thanks to everyone who tried to help.
Barry Samuels
(Barry who? Oh you mean the old f**t who thinks a kernel is something found in a nut,)
This message comes to you courtesy of a 2.4 kernel.
bsamuels@beenthere-donethat.org.uk bsamuels@beenthere-donethat.org.uk wrote:
and I have just rebooted into my 2.4 kernel with no 'unresolved symbols' messages.
Hang on a mo... were these errors this last time coming from before you rebooted into the new kernel? That's sort-of normal if you're already running the same version as you're compiling, I think.
kernel-package still helps ;-)
MJ Ray markj@cloaked.freeserve.co.uk wrote:
and I have just rebooted into my 2.4 kernel with no 'unresolved symbols' messages.
Hang on a mo... were these errors this last time coming from before you rebooted into the new kernel?
I *think* I rebooted as I normally would but see my previous remarks about clocks and memory. You may wish to draw your own conclusions.
That's sort-of normal if you're already running the same version as you're compiling, I think.
kernel-package still helps ;-)
I'll have a look at it one day.
Barry Samuels
bsamuels@beenthere-donethat.org.uk
bsamuels@beenthere-donethat.org.uk wrote:
and I have just rebooted into my 2.4 kernel with no 'unresolved symbols' messages.
Hang on a mo... were these errors this last time coming from before
you
rebooted into the new kernel? That's sort-of normal if you're already running the same version as you're compiling, I think.
I had this a while ago, and it was due to the modules being compiled with version information. Which would add _x1n3jn3j4n or so on to the end of certain module symbols. As found, a reboot into the new kernel solves it.
Does that explain the problems?
Cheers
David.
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.338 / Virus Database: 189 - Release Date: 14/03/2002
On Sat, 6 Apr 2002 bsamuels@beenthere-donethat.org.uk wrote:
I religiously set my options to match your list but still got the same unresolved symbols list. So I thought I'd start from scratch. I deleted the kernel source code directory and re-unpacked the source code. Reloaded my saved configuration and re-compiled.
Oh, btw if you want a copy of my kernel config that i know works with modules for iptables you can get it here http://213.152.38.199/config-2.4.18
If that *still* doesn't work after what else i said about using make-kpkg and that config then there is something very very strange happening ;)
HTH Adam
bsamuels@beenthere-donethat.org.uk bsamuels@beenthere-donethat.org.uk wrote:
I meant to post this to the list (which I have now done) but I think that I sent to Mark's address by mistake.
My reply basically said "remove any unused modules from /lib/modules/2.4.18, do a depmod -ev and then we'll talk more. Oh, and try kernel-package to keep Adam happy.". ;-)
-
Adam Bower -
bsamuels＠beenthere-donethat.org.uk -
David Fairey -
MJ Ray