|Search Linux Wireless
no 5ghz channels available for hostapd?
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Good evening; I've run into a problem with a wireless card (hardware ids: 168c:0029, ath9k) whose regdomain is programmed in the eeprom to 0x00. 'iw list' shows all channels in the 5GHz range as either "(passive scanning, no IBSS)" or "(disabled)". I'd used madwifi in the past successfully and only started seeing this problem after upgrading to kernel 3.2.5 and ath9k. After some digging I think I've found the culprit: $ iw reg get country 00: (2402 - 2472 @ 40), (6, 20) (2457 - 2482 @ 20), (6, 20), PASSIVE-SCAN, NO-IBSS (2474 - 2494 @ 20), (6, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS (5170 - 5250 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS (5735 - 5835 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS trying to fix this situation with 'iw reg set' does nothing, apparently by design of the driver. I'm in the US and clearly should be able to use at least 1 5GHz channel at some power level. The output of regdbdump tells the sorry tale: country '00' has a heavily restricted, 2.4-GHz-only policy. My guess as to how to proceed is twofold: 1) Find a way to modify the card's EEPROM and set the regdomain to whatever value corresponds to the USA. The probability of success on this seems to be low, as I have no idea what tools are capable of doing such modifications. 2) Modify the regulatory.bin file, copying the US values into the '00' country and replacing the original regulatory.bin with my modified one. Can someone provide an alternate solution? Thanks, Michael Mohr -- 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