All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Robert Allerstorfer <linux-ra@anet.at>, linux-wireless@vger.kernel.org
Subject: Re: Operation "wpa_driver_wext_set_countermeasures" not supported
Date: Tue, 18 Dec 2007 14:13:29 +0100	[thread overview]
Message-ID: <200712181413.29569.mb@bu3sch.de> (raw)
In-Reply-To: <345588434.20071218123602@anet.at>

On Tuesday 18 December 2007 12:36:02 Robert Allerstorfer wrote:
> On Mon, 17 Dec 2007, 15:14 GMT+01 Michael Buesch wrote:
> 
> > Please test what I suggested.
> 
> done. I have recompiled and replaced the original b43.ko from
> 'kernel-2.6.23.9-90.fc8.src.rpm', with the modified 'phy.c' ["if
> (B43_DEBUG)" changed to "if (0)" on line 741]. Using Fedora's build
> mechanism, I had to built the entire (baseonly) kernel which took over
> 2 hours. 
> 
> Of course, there is now no more "Disabling TX power adjustment"
> warning in dmesg, but I can't see any other different behavior. I
> still can't connect to the WPA2 access point. dmesg still says
> 
> wlan0: RX ReassocResp from 00:11:22:33:44:55 (capab=0x431 status=0 aid=1)
> wlan0: associated
> wlan0: switched to short barker preamble (BSSID=00:11:22:33:44:55)
> wlan0: disassociate(reason=3) 

Uhm, that seems to be some mac80211 problem.
The driver is obviously able to transmit and receive data properly.
Otherwise it would not be able to associate.

> 
> and the debug output of wpa_supplicant still contains
> 
> wpa_driver_wext_set_countermeasures
> ioctl[SIOCSIWAUTH]: Operation not supported
> 
> What can I do to get it working one day?
> 
> rob.

-- 
Greetings Michael.

           reply	other threads:[~2007-12-18 13:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <345588434.20071218123602@anet.at>]

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=200712181413.29569.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-ra@anet.at \
    --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 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.