I just installed orinoco 0.15RC1 and the card can get monitor mode:
orinoco 0.15rc1STA (David Gibson <[EMAIL PROTECTED]>, Pavel Roskin <[EMAIL PROTECTED]>, et al)
orinoco_cs 0.15rc1STA (David Gibson <[EMAIL PROTECTED]>, Pavel Roskin <[EMAIL PROTECTED]>, et al)
eth2: Hardware identity 8000:0001:0000:0000
eth2: Station identity 001f:0002:0002:0001
eth2: Firmware determined as Symbol V2.90-58
eth2: Ad-hoc demo mode supported
eth2: IEEE standard IBSS ad-hoc mode supported
eth2: WEP supported, 104-bit key
eth2: MAC address 00:A0:F8:42:88:B5
eth2: Station name "Prism I"
eth2: ready
eth2: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x0147
#iwconfig eth2 mode monitor
#iwconfig eth2
eth2 IEEE 802.11-DS ESSID:"" Nickname:"Prism I"
Mode:Monitor Frequency:2.427 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:16 RTS thr:off Fragment thr=0 B
Encryption key:off
Power Management:off
Link Quality=0/92 Signal level=134/153 Noise level=134/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Running kismet (with orinoco_14 driver) I experiment strange things. 1) the kernel log is full of line like this: .... eth2: oversized monitor frame, data length = 46553 eth2: oversized monitor frame, data length = 46553 eth2: oversized monitor frame, data length = 63268 eth2: oversized monitor frame, data length = 22239 eth2: oversized monitor frame, data length = 21616 eth2: oversized monitor frame, data length = 49468 eth2: oversized monitor frame, data length = 49468 .... What are those ?
2) kismet reports a lots of "Association Request" and "Unrecognized(Reserved Frame)" that the hostap and wlan-ng driver with a Prism2.5 card do not reveal. Why ?
Do you still think is a firmware problem ?
I had a very exrensive look to google searching about Symbol firmware but I was not able to find nothing interesting.
On the Symbol web site one can dowload the buggy windoze driver, firmware update utility (which does not works on winXP) but no firmware image or documentation.
Anybody exprerimented Symbol Firmware ? Thans
Mike Kershaw wrote:
hermes @ IO 0x100: Timeout waiting for card to reset (reg=0x0080)! hermes @ IO 0x100: Timeout waiting for command completion. eth2: error -110 reading info frame. Frame dropped. hermes @ IO 0x100: Error -16 issuing command. hermes @ IO 0x100: Error -16 issuing command. hermes @ IO 0x100: Error -16 issuing command. hermes @ IO 0x100: Error -16 issuing command. ....... <many of this messages>
What's wrong with my driver or my card ?
Thats the driver thrashing waiting for the firmware to acknowledge and its never happening -- definitely a driver/firmware level interaction. It's getting locked into an unresponsive state and then everything the driver tries to do times out and fails.
Best I can suggest is to try a different firmware version on your card (you'll need to use windows to reflash the card) and see if that alleviates some of the problems. I don't know much about the symbol firmware revisions so I don't know if you should go down or up for your firmware. Google would probably be able to tell you.
-m
_______________________________________________ BAWUG's general wireless chat mailing list [unsubscribe] http://lists.bawug.org/mailman/listinfo/wireless
