All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Bob Copeland <me@bobcopeland.com>, linux-wireless@vger.kernel.org
Subject: Re: Using compat-wireless w/ 2.6.27.26
Date: Tue, 21 Jul 2009 13:10:33 -0700	[thread overview]
Message-ID: <4A6620B9.4@redfish-solutions.com> (raw)
In-Reply-To: <4A650331.9020409@redfish-solutions.com>

Philip A. Prindeville wrote:
> Luis R. Rodriguez wrote:
>   
>> On Mon, Jul 20, 2009 at 12:16 PM, Philip A.
>> Prindeville<philipp_subx@redfish-solutions.com> wrote:
>>     
>>> Bob Copeland wrote:
>>>       
>>>> On Sun, Jul 19, 2009 at 08:05:47PM -0700, Philip A. Prindeville wrote:
>>>>         
>>>>> Actually, it's saying:
>>>>>
>>>>> filename:       /lib/modules/2.6.27.26-astlinux/kernel/drivers/net/wireless/ath5k/ath5k.ko
>>>>> depends:        mac80211,cfg80211
>>>>>
>>>>> And the 0.6.0 version number matches ath5k/base.c in the compat-wireless
>>>>> sources as well.
>>>>>           
>>>> Yeah, ignore the module version number, no one ever changes it.
>>>>
>>>>         
>>>>> Not seeing the dependency on "ath", which is strange.  Is that common code
>>>>> that's shared in 2.6.30 for the Atheros drivers?
>>>>>           
>>>> In 2.6.31, yes.
>>>>
>>>>         
>>>>>> The fix was merged after 2.6.30, IIRC, but it should definitely be in
>>>>>> compat-wireless.  Also check your modules directory for an old ath5k.ko
>>>>>> sitting in drivers/.../wireless/ath5k.  It should now be in ath/ath5k.
>>>>>>             
>>>> See above, the fix was post-2.6.30, however compat-wireless should have
>>>> it.  The module should now be in drivers/net/wireless/ath/ath5k, not
>>>> drivers/net/wireless/ath5k.
>>>>
>>>>         
>>> I'm using the tarball out of:
>>>
>>> http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.30
>>>
>>> perhaps I should be using a different one?  I tried 2.6.31-rc1, but it doesn't build against 2.6.27.
>>>       
>> I have to fix this, will do so in a bit, will also update it to
>> account for the new rc3.
>>
>>   Luis
>>     
>
> Well, while waiting for a "blessed" (or at least, 'stable') tarball to be pushed out, I tried running 2009-06-30, and I'm seeing a lot of:
>
> mgmt::proberesp cb
> Probe Request from 00:21:29:69:3e:a0 for broadcast SSID ignored
> STA 00:21:29:69:3e:a0 sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> ...
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) ACK
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) ACK
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> STA 00:21:e9:6e:a7:4f sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> Probe Request from 00:21:e9:6e:a7:4f for broadcast SSID ignored
> STA 00:21:29:69:3e:a0 sent probe request for our SSID
> Probe Request from 00:21:29:69:3e:a0 for broadcast SSID ignored
> MGMT (TX callback) ACK
> mgmt::proberesp cb
> STA 00:21:29:69:3e:a0 sent probe request for our SSID
> MGMT (TX callback) fail
> mgmt::proberesp cb
>
>
>
> 00:21:29:69:3e:a0 is a PC running Vista SP2.
>
> 00:21:e9:6e:a7:4f is an iPhone running 3.0.
>
> The iPhone should be scanning for available networks, but it's also been explicitly configured with this particular AP (and SSID).
>
> Is this a known issue?
>
> -Philip
>   

A little progress:  I build 2009-07-10 with 2.6.27.26, and I can get the
Vista box to associate, but not an iPhone running 3.0...

I have traces if anyone is interested.

-Philip


  reply	other threads:[~2009-07-21 20:11 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
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 [this message]
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=4A6620B9.4@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.