My country has the following regulatory.bin lines: country PT: (2402.000 - 2482.000 @ 40.000), (N/A, 20.00) (5170.000 - 5250.000 @ 40.000), (N/A, 20.00) (5250.000 - 5330.000 @ 40.000), (N/A, 20.00), DFS <------ removed whole line (5490.000 - 5710.000 @ 40.000), (N/A, 27.00), DFS <------ removed whole line If I remove the last two lines, everything works as expected, i.e., NO "Microsode SW error". If I include any of the last two, the Microcode will issue an error. I've tried every combination of those lines except just one of "(5250.000 - 5330.000 @ 40.000), (N/A, 20.00), DFS" OR "(5490.000 - 5710.000 @ 40.000), (N/A, 27.00), DFS". Next week I'll look at the source code. On Thu, Nov 24, 2011 at 12:54 PM, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: > Hi Pedro > > On Thu, Nov 24, 2011 at 11:49:30AM +0000, Pedro Francisco wrote: >> iwl3945 has had firmware errors triggered 'by' NM after started using >> nl80211 instead of wext. Since Intel has stopped supporting iwl3945, >> no firmware fix has been possible. It has been workarounded by >> disable_hw_scan=1 as default, with the penalty of network performance >> being lower and frequent 'hangs' on the connection. > Eh, we changed to software scan by default for workaround various > problems. Unfortunately that is causing other problems for other > users. For now, do not exist best default disable_hw_scan= value, that > would pleased everyone :-( > >> I was able to trigger the firmware error by doing "iw dev wlan0 scan >> passive". By comparison, "iw dev wlan0 scan" does NOT trigger the >> firmware error. > >> Having activated firmware debugging, it would seem a firmware error >> occurs when a full passive scan is done. If all channels 1-140 are >> scanned passively, a firmware error occurs. If at least one of those >> channels is actively scanned, no error occurs. >> >> Where should I look next? > Good finding, I'm able to reproduce that firmware error too. Perhaps > you could install older kernel ie. 2.6.32 or even 2.6.24 and see if you > can recreate problem there (but I'm not sure if on older kernel > "iw dev wlan0 scan passive" command will work). If you will find kernel > version, where issue is not present, you might figure out what is > different regarding setting up SCAN command, or let me know so I > will look at that :-) If that is broken also on old kernels, we > perhaps could modify code that will disallow to do all passive > channels scan. > > Thanks > Stanislaw -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
