Hi all.
I've been experiencing random lock-ups on my Acer Aspire 1692WLMi laptop when the iwi interface (2200BG) is up. When this happens the machine is totally irresponsive, does not answer to pings, the keyboard is dead, and I can't even break into ddb. That's apart from the interface firmware getting "stuck" in "state 4" from time to time, and the monitor mode not working after I switched to the 7.x branch...
So... I'd like to know:
a. Is anyone else seeing such things with iwi or is it just an Acer/2200BG thing?
b. How could I go about debugging this situation? The way it is right now, I can't break into ddb and there is no crash/core file to look into.
c. What is the status of monitor mode with iwi and what's the status of iwi in general on 7.x? Is it seeing active support/development or has FBSD moved on to N-class adapters and left iwi behind?
Thanks in advance.
\n\n
I've been experiencing random lock-ups on my Acer Aspire 1692WLMi laptop when the iwi interface (2200BG) is up. When this happens the machine is totally irresponsive, does not answer to pings, the keyboard is dead, and I can't even break into ddb. That's apart from the interface firmware getting "stuck" in "state 4" from time to time, and the monitor mode not working after I switched to the 7.x branch...
So... I'd like to know:
a. Is anyone else seeing such things with iwi or is it just an Acer/2200BG thing?
b. How could I go about debugging this situation? The way it is right now, I can't break into ddb and there is no crash/core file to look into.
c. What is the status of monitor mode with iwi and what's the status of iwi in general on 7.x? Is it seeing active support/development or has FBSD moved on to N-class adapters and left iwi behind?
Thanks in advance.
\n\n