Looks like he's using 2.6.26. I'm using 2.6.26.3 and having a similar problem. I am using wiCD to connect with b43legacy. I'm planning on updating to 2.6.26.5 tonight and see if that helps. I just upgraded to the latest WiCD and need to test that out with my current kernel, before updating the kernel. I'll let you know if that makes any difference. It should be noted that I didn't have this problem before upgrading to 2.6.26.3 recently. Regards, Kurt
Message: 2 Date: Wed, 01 Oct 2008 17:36:01 -0500 From: Larry Finger <[EMAIL PROTECTED]> Subject: Re: b43 driver problems To: Vaidas Mikalauskas <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Vaidas Mikalauskas wrote: > Hello, > > my b43 driver is not working for me, but it was, i dont remember, maybe > after the kernel upgrade or sth it stopped working, well it actually > works, i can search for networks, associate with them, but after few > seconds or minutes (usually when i try to access some web page) it > disconnects. I dont understand why. > > I searched in forums and mailing lists for weeks and nothing helpes, > compiled kernel manualy and nothing, im in deep depression becouse of this. > > below info about my system: > > uname -a > Linux myhost 2.6.26-ARCH #1 SMP PREEMPT Tue Sep 9 10:15:21 UTC 2008 i686 > Mobile AMD Sempron(tm) Processor 3500+ AuthenticAMD GNU/Linux > > lspci -vvnn > 05:00.0 Network controller [0280]: Broadcom Corporation BCM4311 > 802.11b/g WLAN [14e4:4311] (rev 01) > Subsystem: Dell Wireless 1390 WLAN Mini-Card [1028:0007] > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 18 > Region 0: Memory at c0200000 (32-bit, non-prefetchable) [size=16K] > Capabilities: [40] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=2 PME- > Capabilities: [58] Message Signalled Interrupts: Mask- 64bit- > Queue=0/0 Enable- > Address: 00000000 Data: 0000 > Capabilities: [d0] Express (v1) Legacy Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, > L1 unlimited > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset- > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- > Unsupported- > RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- > MaxPayload 128 bytes, MaxReadReq 128 bytes > DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- > TransPend- > LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency > L0 <4us, L1 <64us > ClockPM- Suprise- LLActRep- BwNot- > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ > DLActive- BWMgmt- ABWMgmt- > Capabilities: [100] Advanced Error Reporting <?> > Capabilities: [13c] Virtual Channel <?> > Kernel driver in use: b43-pci-bridge > Kernel modules: ssb > > > > > dmesg > after ifconfig wlan0 up > input: b43-phy0 as /class/input/input8 > firmware: requesting b43/ucode5.fw > firmware: requesting b43/pcm5.fw > firmware: requesting b43/b0g0initvals5.fw > firmware: requesting b43/b0g0bsinitvals5.fw > b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) > Registered led device: b43-phy0::tx > Registered led device: b43-phy0::rx > Registered led device: b43-phy0::radio > > after iwconfig wlan0 essid AAAAAAA key s:LALALALALA && dhcpcd wlan0 > > wlan0: Initial auth_alg=0 > wlan0: authenticate with AP 00:18:e7:32:a0:a4 > wlan0: RX authentication from 00:18:e7:32:a0:a4 (alg=0 transaction=2 > status=0) > wlan0: authenticated > wlan0: associate with AP 00:18:e7:32:a0:a4 > wlan0: RX AssocResp from 00:18:e7:32:a0:a4 (capab=0x411 status=0 aid=2) > wlan0: invalid aid value 2; bits 15:14 not set > wlan0: associated > wlan0: switched to short barker preamble (BSSID=00:18:e7:32:a0:a4) > wlan0: switched to long barker preamble (BSSID=00:18:e7:32:a0:a4) > process `skype' is using obsolete setsockopt SO_BSDCOMPAT > hda-intel: Invalid position buffer, using LPIB read method instead. > b43-phy0 ERROR: PHY transmission error > wlan0: No ProbeResp from current AP 00:18:e7:32:a0:a4 - assume out of range What distro and kernel are you using? If NetworkManager is available, my experience is that it is more likely to reconnect. If your kernel is "old", you may find that wireless-testing works better. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
