Question: Unresolved symbols vs configuration parameters in 2.3.42 

Forum: PCMCIA Installation and Configuration Issues
Date: 2000, Feb 07
From: Peter pfolk

So I got kernel 2.3.42 so that I could use netfilter and keep people from hijacking my 'net connection (the machine acts as a bridge between an ad-hoc 802.11 wireless network and the DSL line). Is 3.1.10 supposed to work with the new kernel, as a module? Compiling it as a static part of the kernel appears to work, except it doesn't find my PCMCIA adapter because I have to pass a configuration parameter (extra_sockets=1) to the i82365 driver. Is there a way to pass this information other than with insmod? Since afaik I have to use it as a module, I configured it as such using menuconfig, but I get unresolved symbols. In particular, depmod -ae sez: depmod: *** Unresolved symbols in /lib/modules/2.3.42/pcmcia/ds.o depmod: pcmcia_lookup_bus depmod: *** Unresolved symbols in /lib/modules/2.3.42/pcmcia/i82365.o depmod: dead_socket depmod: *** Unresolved symbols in /lib/modules/2.3.42/pcmcia/yenta.o depmod: pci_find_parent_resource depmod: probe_irq_mask I solved the dead_socket problem by defining it in i82365.c (it's just a static struct, normally resolved by linking with cs.o I assume), and got around the pcmcia_lookup_bus problem by not configuring CardBus support. The other two symbols are defined in arch/i386/kernel/irq.c and drivers/pci/pci.c (respectively) but I don't know what to do to get it to link against them. Is this a known problem, or something wrong with my system, or just a normal bug? Appologies for my lack of kernel-hacker savvy, Peter

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ All ]  Outline: [ 1 ]  [ 2 ]  [ All ] 

Question: Me too; please tell me exactly what you did Re: Question: Unresolved symbols vs configuration parameters in 2.3.42 (Peter) Date: 2000, Feb 08 From: cosmos

I experienced what you described on my Olivetti Echos 133DM with Xircom REM56G, compiling 2.3.42 and pcmcia-cs 3.1.10. Compiling kernel 2.3.X I set: General setup -> PCMCIA/CardBus support -> PCMCIA/CardBus support M General setup -> PCMCIA/CardBus support -> i82365 support Y Network device support -> Network device support Y Network device support -> Ethernet (10 or 100Mbit) Y Character device -> PCMCIA character device support -> PCMCIA serial device support M Character device -> PCMCIA character device support -> PCMCIA serial device support M But there is a problem with loading the module (during boot phase) i823565.o, there is an unresolved symbol: dead_socket Please tell me how to modify i82365.c to go forward (and solve next problems!). Thank you very much.

1. More: What I did by Peter, 2000, Feb 08

[ Add Message ]  to: "Unresolved symbols vs configuration parameters in 2.3.42"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]