linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Using compat-wireless w/ 2.6.27.26
Date: Sun, 19 Jul 2009 10:55:16 -0700	[thread overview]
Message-ID: <4A635E04.4050204@redfish-solutions.com> (raw)
In-Reply-To: <b6c5339f0907190638jc1bdacbo801adcd39a1cf5@mail.gmail.com>

Bob Copeland wrote:
> On Fri, Jul 17, 2009 at 9:27 PM, Philip A.
> Prindeville<philipp_subx@redfish-solutions.com> wrote:
>> + modprobe ath5k
>> ath5k phy0: Atheros AR5413 chip found (MAC: 0xa4, PHY: 0x61)
>>
>> + iw dev wlan0 interface add ap0 type managed
>> + ip link set ap0 up
>> + iw dev ap0 connect xxxx
>> command failed: Operation not supported (-95)
> 
> Why are you adding another interface?  Should be able to use "iw dev wlan0..."

Because I might want to run two access points (two SSIDs, anyway) on the same radio...  one with WEP on one VLAN (for Wifi SIP handsets), and one with WPA-PSK2 on another VLAN (for laptops, etc).

>> pbx ~ # iw phy phy0 info
>> command failed: No buffer space available (-105)
> 
> Means the netlink buffer was exceeded.  In the past this was because there
> were too many channels -- are you sure you're loading the compat-wireless
> ath5k instead of the .29 one (and not using all_channels modparam)?
> 

Reasonably sure, yes.  I stopped the distro build and did an "ls -R" after building linux, and there were no drivers other than cfg80211.ko and mac80211.ko that get duplicated.

After resuming the rest of the build, there were drivers from compat-wireless including ath5k, and cfg80211.ko and mac80211.ko also had refreshed timestamps matching everything else.

But, if you think there's still a doubt, what to look for in the modinfo?

-Philip

  reply	other threads:[~2009-07-19 17:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  1:27 Using compat-wireless w/ 2.6.27.26 Philip A. Prindeville
2009-07-19  8:58 ` Philip A. Prindeville
2009-07-19 13:38 ` Bob Copeland
2009-07-19 17:55   ` Philip A. Prindeville [this message]
2009-07-19 20:31     ` Bob Copeland
2009-07-20  3:05       ` Philip A. Prindeville
2009-07-20 11:52         ` Bob Copeland
2009-07-20 19:16           ` Philip A. Prindeville
2009-07-20 19:47             ` Luis R. Rodriguez
2009-07-20 23:52               ` Philip A. Prindeville
2009-07-21 20:10                 ` Philip A. Prindeville
2009-07-21 23:24                   ` Luis R. Rodriguez
2009-07-22  3:28                   ` Bob Copeland
2009-07-23 11:24                   ` Bob Copeland
2009-07-23 11:59                     ` Bob Copeland
2009-07-23 20:29                       ` Philip A. Prindeville
2009-07-23 20:33                         ` Bob Copeland
2009-07-23 21:53                         ` Philip A. Prindeville
2009-07-23 22:21                           ` Bob Copeland
2009-07-23 22:45                             ` Philip A. Prindeville
2009-07-24 13:58                               ` Bob Copeland
2009-07-30  4:36                                 ` Philip A. Prindeville
2009-07-21 23:26               ` Luis R. Rodriguez

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=4A635E04.4050204@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    /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).