unres. symbols by issueing "insmod hostap_cs"

Thu Apr 24 16:11:59 PDT 2003

hi,

thanks for your hint.

it didn't really solve the problem (only the "smp"-stuff after 
_Rwhatever disappeared after disabling smp in the kernel config and 
recompiling), but it made me think of copying the kernel .config from 
the working system to the other machine. and what should i tell you? now 
it just works fine after recompiling the source (although i don't 
exactly know why - i should run a diff on those files).

but there's one cloud on the horizon: unfortunately it does not work 
with the mppe enabled kernel (the system simply freezes when the modules 
(partly directly after hostap, partly after *_crypt) are inserted) but 
anyway - it works with the standard kernel and this makes me a lucky man 
indeed.

thank you very much again.

-mp.

Peyush Agarwal schrieb:

>Hi,
>
>At the time of kernel compilation, remove the "Symmetric multiprocessor
>support" support and then compile your driver.
>
>Regds.
>Peyush.
>
>"m_pawlowski at t-online.de" wrote:
>
>  
>
>>hi, everybody.
>>
>>well ... i was trying to get hostap up and running for several days now.
>>unfortunately i wasn't able to set it up completely and i'm close to
>>going slightly mad about it.
>>
>>the distributions i used were rh 7.1 and 8.0 and i even installed it
>>freshly any time i was close to desperation. but although everything
>>compiled ok (make pccard and make install_pccard) and installed
>>correctly hostap_cs did not install itself when the wireless card was
>>inserted (Netgear MR401RA, i edited hostap_cs.conf to fit the desc and i
>>did edit the Makefile to point to the right location and added the line
>>EXTRA_CFLAGS=-DPRISM2_HOSTAPD to get the userspace-daemon). so i tried
>>to insmod it manually and strangely enough the following messages
>>appeared on the screen:
>>
>>["insmod hostap_cs" on RH71:]
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_get_stats_Rsmp_390a1e89
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_handle_sta_tx_Rsmp_46f640b0
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_check_sta_fw_version_Rsmp_42ed7e19
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_rx_Rsmp_b8370db9
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_netif_stop_queues_Rsmp_3a5a7aef
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_info_init_Rsmp_2c329034
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_get_porttype_Rsmp_62abd661
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_update_rx_stats_Rsmp_797a2ffa
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_dump_tx_header_Rsmp_3abcbf80
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_handle_sta_rx_Rsmp_5e5b501a
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_set_multicast_list_queue_Rsmp_c089a779
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_init_data_Rsmp_e87fbd5a
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_info_process_Rsmp_e0942f32
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_free_data_Rsmp_44cb068b
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_set_word_Rsmp_f1417d23
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_is_sta_assoc_Rsmp_4f6542f7
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_set_antsel_Rsmp_b80593b4
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_80211_get_hdrlen_Rsmp_6903f16c
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_init_proc_Rsmp_00cea015
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_update_sta_ps_Rsmp_45a63518
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_set_string_Rsmp_c7659074
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_dump_rx_header_Rsmp_27a069d6
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_80211_header_parse_Rsmp_5890fb53
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_set_encryption_Rsmp_8e5c034d
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_setup_dev_Rsmp_b7f64b28
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_handle_sta_release_Rsmp_27df6133
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_handle_sta_crypto_Rsmp_5084302a
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_netif_wake_queues_Rsmp_6f00495f
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_handle_sta_tx_exc_Rsmp_096fa615
>>/lib/modules/2.4.2-2/pcmcia/hostap_cs.o: unresolved symbol
>>hostap_remove_proc_Rsmp_51010be6
>>
>>there was no output from depmod concerning unresolved symbols; those
>>messages only appear when i try to insmod hostap_cs manually.
>>
>>CONFIG_MODVERSIONS didn't do the trick, either. the only thing that
>>differs then is the missing trailing _R* stuff when trying to insmod
>>hostap_cs.
>>
>>can anybody please tell me what i'm doing wrong?
>>
>>the weird thing is: on a system where hostapd is not intended to run
>>everything works fine (it's another laptop running RH 8.0), hostap_cs
>>automatically loads every time the card is inserted and i am sure that
>>the config's identical to the one on the system where hostap_cs does not
>>work.
>>
>>well, you shall say that surely enough there must be differences and
>>most probably you're right (excuse me for being that dull :). but i
>>can't figure out where the differences are ...
>>
>>oh - and: it doesn't matter whether i use the latest cvs-snapshot (which
>>runs fine on the system where hostapd is not intended to run) or v0.0.1.
>>
>>any help is gladly appreciated.
>>
>>thanks in advance.
>>
>>-mp.
>>
>>_______________________________________________
>>HostAP mailing list
>>HostAP at shmoo.com
>>http://lists.shmoo.com/mailman/listinfo/hostap
>>    
>>
>
>--
>______________________________________________________________
>Peyush Agarwal
>Sr. Engineer, Networking and Communications, Tata Elxsi Ltd.
>Phone number :: 91-80-8410220/1/2 ex. 415.  Fax ::  91-80-8410219.
>www.tataelxsi.com
>______________________________________________________________
>
>
>
>  
>