On Fri, Sep 19, 2008 at 01:01:15PM -0700, Celejar wrote: > I think the problem I had was that on boot, the b43 / 80211 modules get > loaded, but they don't seem to be calling CRDA, and I can't access my > hidden essid AP. Doing the module removal and reloading that Luis > suggested causes CRDA to be called, and then things work fine. b43 drivers don't yet use regulatory_hint() so you get stuck with the defualt regulatory domain, which is world. To get out of world you can use iw to set the regulatory domain as follows: iw reg set US this would be for the United States regulatory domain. To find your alpha2 please check: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 Our current database can be viewed here: Web view: http://wireless.kernel.org/en/developers/Regulatory/Database gitweb: http://git.kernel.org/?p=linux/kernel/git/mcgrof/crda.git;a=blob;f=db.txt;hb=HEAD (Note: this database will soon be moved to another separate tree apart from crda) If you have updates for this database please read this: http://wireless.kernel.org/en/developers/Regulatory#Sendingupdatestotheregulatorydatabase Please note though that you *don't have to reload the module* to fix this issue, all you have to do is to use iw to set the regulatory domain. Eventually what can be done is userspace networking applets like NetworkManager can send the same nl80211 request to the wireless core after bootup. A country can then be configurable by the user through the applet. Another alternative is for distributions to call the iw command on the country alpha2 based on the locale. Basically there's many ways to do it. Drivers can also just call the regulatory hint based on their EEPROM, an example driver doing this already is zd1211rw. 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
