Help - Search - Members - Calendar
Full Version: What No Firmware - Wifi Misery
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
stormer
I have 4 wifi cards, three report missing primary firmware after a few minutes use the other a senao intersil prism card has the fantastic ability to periodically tell me that my access point is out of range even though it is within 2 meters of mt C3100 at the time.

The other 3 cards are a Dlink DWL-660W, Ambicom WL1100C, elink XI815
All are prism cards, I have tried firmware upgrades and downgrades only to find that as soon as I want to do anything useful dmesg reports "no primary F/W"

Typically I can do an ipkg update sucessfully but as soon as I try to install or browse more than a couple of pages my wifi dies.

One or even two cards going faulty and producing the same error is plausible - just about, but 3 cards going faulty, two of them purchased within the last 2 months going faulty makes me suspect my hostap drivers. Why does the hostap driver try and reload firmware to the card after a few minutes/megs?
is there any way to stop it doing this?

Am I the only one experiencing this?

DMESG from just after the card (ambicom) is inserted

hostap_cs: 0.4.7 - 2005-11-20 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 135, io 0xf6000000-0xf600003f
prism2_hw_init: initialized in 200 ms
wifi0: NIC: id=0x801b v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: registered netdevice wlan0
prism2: wlan0: operating mode changed 3 -> 2
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:10:7a:59:e2:f2 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x4108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:10:7a:59:e2:f2 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: LinkStatus=6 (Association failed)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:90:4b:c7:15:2f
root-smile.gif



example DMESG prior to this segment I had been surfing with firefox for a few minutes, I dont understand why hostap suddenly decides I need to download firmware

wifi0: LinkStatus=5 (Access point in range)
wifi0: LinkStatus: BSSID=00:90:4b:c7:15:2f
wifi0: LinkStatus=4 (Access point out of range)
wifi0: LinkStatus: BSSID=00:90:4b:c7:15:2f
wifi0: Interrupt, but SWSUPPORT0 does not match: 01FF != 8A32 - card removed?
wifi0: scheduled card reset
hostap_cs: wifi0: resetting card
prism2_pccard_cor_sreset: original COR ff
hostap_cs: assuming no Primary image in flash - card initialization not completed
wifi0: test Genesis mode with HCR 0x1f
prism2_pccard_cor_sreset: original COR ff
prism2_pccard_genesis_sreset: original COR ff
Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 00 00 00
wifi0: test Genesis mode with HCR 0x0f
prism2_pccard_cor_sreset: original COR ff
prism2_pccard_genesis_sreset: original COR ff
Readback test failed, HCR 0x0f write 00 e1 a1 ff read 00 00 00 00
prism2_pccard_genesis_sreset: original COR ff
wifi0: cannot get RID fd51 (len=6) - no PRI f/w

C3100 - PdaXii Akita - SaLLY 3.5.2
Capn_Fish
I have the Ambicom, and have used it without problems on betas 1 and 3 as well as r121.
ArchiMark
FWIW, I'm using my Ambicom WiFi card and it works fine....

HTH,

Mark
stormer
Seems to work if I use orinoco rather than hostap, through the very blunt instrument of renaming hostap_cs.conf and letting the hermes_cs.conf pick up the cards instead, I just cannot figure out why hostap on Pdax decides that a working card has lost it's firmware?

I know that I should probably just leave this alone as it is working but where would the fun be in that!

Also orinoco doesnt really handle the transition back from Kismet very well!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.