Thread (7 messages) flat view 7 messages, 4 authors, 2006-11-03

Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command

From: Ivan Matveich <hidden>
Date: 2006-11-02 18:30:45
Also in: lkml

On 11/2/06, Dan Williams [off-list ref] wrote:
It appears that the driver cannot talk to your card; see the "max tries
exceeded when issueing command".  Did this card work previously with a
kernel?  Can narrow down which kernels have problems and which don't?
It spontaneously stopped working about a week after I bought the
laptop and installed Linux. I tried kernel 2.6.12 and it had the same
problem. (Let me know if you'd like me to try a specific version.)

I'm hoping that the card has simply got itself into some kind of
invalid state, and not failed altogether.
It's a bit hard to figure out what firmware you have because the driver
can't talk to the card; can you boot under Windows and determine that
using the Cisco wireless utility?  You also need to flash the card under
Windows, not Linux, ideally to a version of firmware greater than
5.60.08.
I haven't run Windows in many years, so that's problematic. What's the
most straightforward way to boot into a Windows environment sufficient
to run the Cisco wireless utility?
reloading the driver (rmmod airo; modprobe airo) should reset the card.
Yeah, it unfortunately doesn't help. (Nor does rebooting or resetting
the bios.) I noticed a suspiciously relevant commit in the airo.c git
log:

    [wireless airo] reset card in init

    without this patch after an rmmod, modprobe the card won't work anymore
    until the next reboot.

    This patch seem safe to apply for all cards as the bsd driver already do
    that.

    I had to add a timeout because strange things happen (issuecommand will
    fail) if the card is already reseted (after a reboot).

    PS : it seems there are missing reset when leaving monitor mode...

    Signed-off-by: Matthieu CASTET [off-list ref]

and that makes me wonder if there might be some kind of subtle bug in
the card initialization sequence that manifests itself with my
particular card/firmware.

I think I'll burn a freebsd livecd today and see if their kernel works.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help