2009/4/13 Gábor Stefanik <netrolller.3d@xxxxxxxxx>: > On Mon, Apr 13, 2009 at 6:24 PM, Grzegorz Nowakowski <krecik@xxxxxxx> wrote: >> On Sat, Apr 11, 2009 at 05:19:55PM +0100, Tony Vroon wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Fri, 10 Apr 2009 23:39:58 +0200 >>> Grzegorz Nowakowski <krecik@xxxxxxx> wrote: >>> > The symptom is that with both NetworkManager and WICD (and "iwlist >>> > <if> scanning") I don't see my home network on the list. I see all >>> > other neighbouring networks around and I'm even able to connect if >>> > any is open. >>> >>> Please doublecheck your wireless regulatory setting. On the default >>> "world" domain, it is unlikely you will be able to see networks on >>> channel 13. You may well have chosen that specific channel because it >>> was so quiet. >> >> Gee, that was so stoopid! You have guessed correctly, the channel in >> use was indeed thirteenth and 13 was its number. After reconfiguring >> the AP to use another one everything seems to be working fine. >> >> But that leaves me with the question: why Windows XP on Atheros and Linux >> on Intel didn't have such trouble? > > Windows XP auto-configures the regulatory domain based on your > regional settings. Not quite. > Intel cards have semi-hardcoded regulatory > information in their EEPROMs, which allows Linux to automatically > select the right regulatory settings. Sort of right. > Atheros cards have no such > firmware-level regulatory enforcement. Wrong. The right answer is the windows Atheros driver uses the EEPROM for regulatory enforcement. The Intel drivers, depending on the card through different regulatory domain SKUs, also use their EEPROM information for regulatory compliance but are mostly always configured to a sort of world roaming regulatory domain. Both the Intel windows and Linux drivers make use of these regulatory domains. The reason why you may not see Channel 13 on ath5k is the old ath5k doesn't make use of the EEPROM to take advantage of setting your regulatory environment. As Bob indicated though and mainly thanks to his efforts, ath5k will soon be doing this so you won't have to be specifying your regulatory domain manually. Luis -- 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
