From: James <bjlockie@lockie.ca>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: did compat-wireless-2011-01-27 crash dhcpcd?
Date: Thu, 27 Jan 2011 18:21:27 -0500 [thread overview]
Message-ID: <4D41FDF7.3040805@lockie.ca> (raw)
In-Reply-To: <4D41ED24.9010005@hauke-m.de>
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?
next prev parent reply other threads:[~2011-01-27 23:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 20:52 did compat-wireless-2011-01-27 crash dhcpcd? James
2011-01-27 22:09 ` Hauke Mehrtens
2011-01-27 23:21 ` James [this message]
2011-01-27 23:39 ` Brian Prodoehl
2011-01-28 9:25 ` Johannes Berg
2011-01-28 16:07 ` enable CONFIG_WIRELESS_EXT James
2011-01-28 16:49 ` Randy Dunlap
2011-01-28 16:12 ` did compat-wireless-2011-01-27 crash dhcpcd? Brian Prodoehl
2011-01-29 3:01 ` James
2011-01-29 6:31 ` Brian Prodoehl
2011-02-02 19:08 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D41FDF7.3040805@lockie.ca \
--to=bjlockie@lockie.ca \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).