On 01/28/11 11:12, Brian Prodoehl wrote: > On Thu, Jan 27, 2011 at 6:21 PM, James <bjlockie@xxxxxxxxx> wrote: >> On 01/27/11 17:09, Hauke Mehrtens wrote: >>> On 01/27/2011 09:52 PM, James wrote: >>>> cfg80211: Calling CRDA to update world regulatory domain >>>> Compat-wireless backport release: compat-wireless-2011-01-06-3-g8db1608 >>>> Backport based on linux-next.git next-20110121 >>>> ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17 >>>> ath: EEPROM regdomain: 0x10 >>>> ath: EEPROM indicates we should expect a direct regpair map >>>> ath: Country alpha2 being used: CO >>>> ath: Regpair used: 0x10 >>>> ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' >>>> cfg80211: wext will not work because kernel was compiled with >>>> CONFIG_WIRELESS_EXT=n. Tools using wext interface, like iwconfig will >>>> not work. >>> WEXT is deactivated in compat-wireless because CONFIG_WIRELESS_EXT=y was >>> not set in your kernel config and iwconfig does not work without wext. >>> >>> See: http://www.spinics.net/lists/linux-wireless/msg63449.html >>> >>> Hauke >>> -- >> I'm not using any tools. >> The call trace happens after I do a modprobe. >> I'm guessing it doesn't like dhcpcd. >> >> Do I really need CONFIG_WIRELESS_EXT? > This still doesn't feel like the entire story. Do you have > NetworkManager running, by chance? > > -Brian > No Network Manager, I use Gentoo. dhcpcd is running I disabled wpa_suppliucant from auto starting. Any ideas of what other processes to check for? -- 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
