Trouble using bcm4318 compact flash with b43 driver

Larry Finger Larry.Finger at lwfinger.net
Tue Jan 18 09:34:46 EST 2011


On 01/18/2011 04:58 AM, dylan cristiani wrote:
> On Mon, 17 Jan 2011 14:51:06 +0100
> dylan cristiani <d.cristiani at idem-tech.it> wrote:
> 
> ...snipped
>> here comes the 'iw event -t -f' log:
>>
>> nylux:~ #iw event -t -f
>> 1229947332.952454: wlan0 (phy #0): scan started
>> 1229947334.360008: wlan0 (phy #0): scan finished: 2412 2417 2422 2427
>> 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, "bancoliniaes"
>> 1229947334.406591: wlan0 (phy #0): auth 00:15:70:e2:3c:a1 ->
>> 14:0b:6b:1e:3e:86 status: 0: Successful [frame: b0 08 40 01 14 0b 6b
>> 1e 3e 86 00 15 70 e2 3c a1 00 15 70 e2 3c a1 80 7d 00 00 02 00 00 00]
>> 1229947334.417716: wlan0: new station 00:15:70:e2:3c:a1
>> 1229947334.430558: wlan0 (phy #0): assoc 00:15:70:e2:3c:a1 ->
>> 14:0b:6b:1e:3e:86 status: 0: Successful [frame: 10 00 40 01 14 0b 6b
>> 1e 3e 86 00 15 70 e2 3c a1 00 15 70 e2 3c a1 90 7d 11 04 00 00 01 c0
>> 01 08 82 84 8b 0c 12 96 18 24 32 05 24 30 48 60 6c] 
>> 1229947334.431352: wlan0 (phy #0): connected to 00:15:70:e2:3c:a1 
>> 1229947340.620737: wlan0 (phy #0): deauth 14:0b:6b:1e:3e:86 ->
>> 00:15:70:e2:3c:a1 reason 4: Disassociated due to inactivity [frame: c0
>> 00 00 00 00 15 70 e2 3c a1 14 0b 6b 1e 3e 86 00 15 70 e2 3c a1 00 00
>> 04 00] 
>> 1229947340.621700: wlan0 (phy #0): disconnected (local request)
>> 1229947340.740407: wlan0 (phy #0): scan started 
>> 1229947342.169816: wlan0 (phy #0): scan finished: 2412 2417 2422 2427
>> 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, ""
>> 1229947342.791016: wlan0 (phy #0): auth: timed out 
>> 1229947342.791700: wlan0 (phy #0): failed to connect to
>> 00:15:70:e2:3c:a1, status: 1: Unspecified failure 
>> 1229947352.221068: wlan0 (phy #0): scan started 
>> 1229947353.654043: wlan0 (phy #0): scan finished: 2412 2417 2422 2427
>> 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, "bancoliniaes"
>> 1229947358.680398: wlan0 (phy #0): scan started
>> 1229947360.110101: wlan0 (phy #0): scan finished: 2412 2417 2422 2427
>> 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, ""
>> 1229947365.130440: wlan0 (phy #0): scan started 
>> 1229947366.559799: wlan0 (phy #0): scan finished: 2412 2417 2422 2427
>> 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, "bancoliniaes"
>>
>>
>> As you can see the module get associated to AP whose ssid is
>> "bancoliniaes", get connected but few time after it disassociates:
>> 'reason 4: Disassociated due to inactivity' i dunno why is this
>> happening...
>> after this i cutted the log because it loops forever between 'scan
>> started' and 'scan finished' without any more association between the
>> module and the AP! i hope this logs can tell you something to help me.
>> for now tks  
> Hi Larry i've some news: i tryied with kernel 2.6.35 and it works!
> the module associates to AP and i can browse the net, ping external
> addresses and so on...; it seems that some drivers' changes made things
> go worste for my 'platform': do you have any suggestions?
> Note that all kernel settings are the same in 2.6.35, 2.6.36 and 2.6.37
> except, obviously, for the new kernel's parameters of the latter two.

The usual advice offered in cases like yours is to install a git tree and bisect
the issue. As you have a problem with mainline kernels, I definitely recommend
the linux-2.6.git tree as it bisects better than development trees like
wireless-testing.git. Your number of trials should not be too bad as you know it
broke between 2.6.35 and 2.6.36.

Larry



More information about the b43-dev mailing list