From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Problem with b43
Date: Tue, 22 Jun 2010 10:09:00 -0500 [thread overview]
Message-ID: <4C20D20C.6000606@lwfinger.net> (raw)
In-Reply-To: <AANLkTili3ExOipmXzdd9JMMMhiyc8KUZoND-3KaznevA@mail.gmail.com>
On 06/21/2010 06:22 PM, G?bor Stefanik wrote:
> 2010/6/22 Fabrizio Regalli <fabreg@gmail.com>:
>> Ok, I put "options b43 pio=0 qos=0" in /etc/modprobe.d/b43.conf
>> And now the message is changed:
>>
>>
>> ...
>> [ 745.708045] b43-phy1: Loading firmware version 410.2160 (2007-05-26
>> 15:32:10)
>> [ 745.724051] b43-phy1 debug: Chip initialized
>> [ 745.724189] b43-phy1 debug: 32-bit DMA initialized
>> [ 745.724198] b43-phy1 debug: QoS disabled
>> [ 745.744374] b43-phy1 debug: Wireless interface started
>> [ 745.768105] b43-phy1 debug: Adding Interface type 2
>> [ 745.796352] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [ 748.160267] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)
>> [ 748.161313] wlan0: authenticated
>> [ 748.161425] wlan0: associate with 00:18:4d:2e:85:4a (try 1)
>> [ 748.162831] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431
>> status=0 aid=1)
>> [ 748.162835] wlan0: associated
>> [ 748.163348] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
>> [ 748.168313] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local
>> choice (reason=3)
>> [ 748.168466] cfg80211: Calling CRDA to update world regulatory domain
>> [ 749.496214] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)
>> [ 749.497126] wlan0: authenticated
>> [ 749.497240] wlan0: associate with 00:18:4d:2e:85:4a (try 1)
>> [ 749.498655] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431
>> status=0 aid=1)
>> [ 749.498659] wlan0: associated
>> [ 749.504316] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local
>> choice (reason=3)
>> [ 749.504523] cfg80211: Calling CRDA to update world regulatory domain
>>
>>
>> But unfortunately does not work.
>>
>> I can obtain just the ip address:
>>
>> # ifconfig wlan0 |grep inet
>> inet addr:192.168.0.100
>>
>> but iwconfig show me there isn't any access point associeted:
>>
>> wlan0 IEEE 802.11bg ESSID:off/any
>> Mode:Managed Frequency:2.472 GHz Access Point: Not-Associated
>> Tx-Power=20 dBm
>> Retry long limit:7 RTS thr:off Fragment thr:off
>> Encryption key:off
>> Power Management:off
>>
>>
>
> Did you shut down NetworkManager?
>
> Also, why are you disabling QoS? Unless you are using OpenFWWF, QoS
> shouldn't need to be disabled.
I will describe some recent findings in a separate email; however, to use
the BCM4312 in PIO mode, you do need to disable QoS AND hardware
encryption. Add "nohwcrypt=1" to b43.conf and leave the "qos=0" in.
Larry
next prev parent reply other threads:[~2010-06-22 15:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 21:45 Problem with b43 Fabrizio Regalli
2010-06-01 2:17 ` William Bourque
2010-06-01 8:39 ` Martino Salvetti
2010-06-20 12:04 ` Fabrizio Regalli
2010-06-20 18:12 ` Gábor Stefanik
[not found] ` <AANLkTimpDoxIjIBVOPug5uLADaV5oX6RX8se9VC1x6Pd@mail.gmail.com>
2010-06-21 23:22 ` Gábor Stefanik
2010-06-22 15:09 ` Larry Finger [this message]
2010-06-22 18:54 ` Fabrizio Regalli
2010-06-22 19:46 ` Larry Finger
2010-06-22 20:40 ` Fabrizio Regalli
2010-06-24 21:50 ` Fabrizio Regalli
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 16:55 problem " Cyrille
2010-09-24 17:06 ` Gábor Stefanik
2010-09-24 17:06 ` Gábor Stefanik
2010-09-24 17:21 ` John W. Linville
2010-09-24 17:21 ` John W. Linville
2010-09-24 17:30 ` Gábor Stefanik
2010-09-24 17:30 ` Gábor Stefanik
2010-09-24 17:43 ` Michael Büsch
2010-09-24 17:43 ` Michael Büsch
2010-09-24 17:39 ` Cyrille
2010-09-24 17:39 ` Cyrille
2010-09-24 17:10 ` Rafał Miłecki
[not found] ` <20100924191547.59c58e7b.cyrille@cbiot.fr>
2010-09-24 17:28 ` Rafał Miłecki
2010-09-24 17:32 ` Cyrille
2010-09-24 17:46 ` Rafał Miłecki
2010-09-24 18:32 ` Cyrille
2010-09-24 18:39 ` Peter Stuge
2010-09-24 19:28 ` Nicolas de Pesloüan
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=4C20D20C.6000606@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.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.