iwconfig trouble

[Jerry]

>so what exactly should I do?
>I edited the modules.conf, removing the lines that lead to the old driver
>and when I insert the card, the hostap and hostap_cs modules get loaded
>and a wifi0 interface appear but it doesn't seem work (the led of the card
>is not fixed). the dmesg gived this messages:

That appears to have been the correct things to do. As what follows is the
initialization of the card..

>hostap_cs: 0.2.5  -  2004-10-03 (Jouni Malinen <jkmaline at cc.hut.fi>)
>hostap_cs: setting Vcc=33 (constant)
>hostap_cs: CS_EVENT_CARD_INSERTION
>hostap_cs: setting Vcc=33 (from config)
>Checking CFTABLE_ 0x01 (default 0x01)
>IO window setting: cfg->io.nwin=1 dftl.io.nwin=1
>io->flags = 0x0046, io.base=0x0000, len=64
>hostap_cs: Registered netdevice wifi0
>hostap_cs: index 0x01: Vcc 3.3, irq 5, 0x0100-0x013f0
>prism2_hw_init: initialized in 100 ms
>wifi0: NIC: id=0x8002 v1.0.1
>wifi0: PRI: id=0x15 v0.3.0
>wifi0: STA: id=0xaf v0.8.0
>wifi0: defaulting for host-based encryption as a workaround for firmware
>bug in Host AP mode WEP
>wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in
>Host AP mode WDS
>using data:: nullfunc ACK workaround - firmware upgrade recommended
>wifi0: registered netdevice wlan0



>any hint for me?
>Dom

at this point you SHOULD probably ram update the firmware...as that is what
this is telling you:

>wifi0: defaulting for host-based encryption as a workaround for firmware
>bug in Host AP mode WEP
>wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in
>Host AP mode WDS
>using data:: nullfunc ACK workaround - firmware upgrade recommended
>wifi0: registered netdevice wlan0

But it isnt completely necessary, just highly recommended.    When it shows
the following:

 >prism2_hw_init: initialized in 100 ms
>wifi0: NIC: id=0x8002 v1.0.1
>wifi0: PRI: id=0x15 v0.3.0
>wifi0: STA: id=0xaf v0.8.0

or something similar, you know it has properly initialized the card, what
you need to do next is 'ifconfig wlan0 up'   to bring the card "up", or by
simply giving  the interface an IP will also do this.  When you bring it up
the light should come on and it should be ready to "use".  You will, of
course, have to set the essid and wep and so forth, and the mode as well,
because it will default to 'AP mode' if that is not what you want.

But still recommended is the firmware update. I would firware update to ram
at least in the beginning, maybe later I would try to do it permanently.
prism2_srec wlan0 ru010506.hex (without any parameters, to see which version
is compatible first, it wont "do" anything, just check it)  If the output is
correct, then you can ram update it with: prism2_param wlan0 -r
ru010506.hex.  (it may not be ru010506.hex, this is for example)

good luck

Jerryf