View topic - Broadcom Wireless Trouble :: sidux.com :: debian based live cd development

Menu

News

Announcing the winner from the "Ourea" Wallpaper Competition (Aug 19, 2008)
sidux-manuals goes Greek -el (Jul 29, 2008)
Resolved: No Dist-Upgrade! (Jul 17, 2008)

Give back

Last 3 Contributions
20-08-2008	15.00
18-08-2008	15.00
17-08-2008	5.00

Donate

Sponsor

Languages

Preferred language:

Broadcom Wireless Trouble
Previous 1, 2, 3

sidux.com Forum Index » English Forum » Networking

Author

Message

hoogewoud

Post subject: RE: Wifi LAN

Posted: Jul 02, 2008 - 03:26 PM

Joined: Dec 12, 2006
Posts: 133
Location: switzerland
Status: Offline

as your hardware is recognized you may try two other tricks:

first try to configure with Ceni as root (apt-get install Ceni )
and second check if you must enter your password as hex or as clear.

greetings

damentz

Post subject: RE: Wifi LAN

Posted: Jul 03, 2008 - 03:52 AM

Joined: Dec 01, 2006
Posts: 713

Status: Offline

With ceni you can also choose to use wireless-tools or wpasupplicant... try both.

And make sure you have b43-fwcutter, not bcm43xx-fwcutter, which is deprecated.

_________________
"Cool was never cool until the cool guys at Cool industries developed a cool new product: Cool."

Craigus

Post subject:

Posted: Jul 04, 2008 - 12:29 PM

Joined: Jul 04, 2008
Posts: 3

Status: Offline

Using b43-fwcutter(b43legacy / ssb) on a Toshiba Satellite Pro 4600 with a bcm4306:

Code:

craigus@sidux4600:~$ ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=6.33 ms

bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=11.3 ms

bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=5.94 ms

bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.80 ms

bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=5.79 ms

bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=23.4 ms

bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=5.85 ms

bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=33.0 ms

bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=7.27 ms

bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=8.94 ms

bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=12.8 ms

bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=10.5 ms

bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=5.89 ms

bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=5.97 ms

bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=7.74 ms

bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=18.3 ms

bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=6.23 ms

^C

--- 192.168.1.1 ping statistics ---

packets transmitted, 17 received, 0% packet loss, time 16016ms

rtt min/avg/max/mdev = 5.797/10.670/33.069/7.387 ms

craigus@sidux4600:~$

This is the best performance I ever get; packet loss can be up to 100% at times.

With ndiswrapper:

Code:

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.88 ms

bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.75 ms

bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.24 ms

bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.77 ms

bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2.45 ms

bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.72 ms

bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2.08 ms

bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.01 ms

bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.72 ms

bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=2.08 ms

bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.79 ms

bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.76 ms

bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.23 ms

bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.76 ms

bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.72 ms

bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.72 ms

bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.81 ms

bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.76 ms

^C

--- 192.168.1.1 ping statistics ---

packets transmitted, 18 received, 0% packet loss, time 17016ms

rtt min/avg/max/mdev = 1.724/1.962/3.244/0.372 ms

craigus@sidux4600:~$

slh

Post subject:

Posted: Jul 04, 2008 - 12:53 PM

Joined: Nov 25, 2006
Posts: 2383

Status: Offline

b43-phy0: Broadcom 4306 WLAN found
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)

03:00.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)

Code:

wlan1     IEEE 802.11g  ESSID:"xxxxx"

          Mode:Managed  Frequency:2.422 GHz  Access Point: xx:xx:xx:xx:xx:xx

          Bit Rate=54 Mb/s   Tx-Power=20 dBm

          Retry min limit:7   RTS thr:off   Fragment thr=2352 B

          Link Quality=86/100  Signal level=-43 dBm  Noise level=-68 dBm

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Code:

$ ping 192.168.0.252

PING 192.168.0.252 (192.168.0.252) 56(84) bytes of data.

bytes from 192.168.0.252: icmp_seq=1 ttl=64 time=1.93 ms

bytes from 192.168.0.252: icmp_seq=2 ttl=64 time=1.37 ms

bytes from 192.168.0.252: icmp_seq=3 ttl=64 time=1.25 ms

bytes from 192.168.0.252: icmp_seq=4 ttl=64 time=1.36 ms

bytes from 192.168.0.252: icmp_seq=5 ttl=64 time=1.29 ms

bytes from 192.168.0.252: icmp_seq=6 ttl=64 time=1.27 ms

bytes from 192.168.0.252: icmp_seq=7 ttl=64 time=1.31 ms

bytes from 192.168.0.252: icmp_seq=8 ttl=64 time=2.22 ms

bytes from 192.168.0.252: icmp_seq=9 ttl=64 time=1.44 ms

bytes from 192.168.0.252: icmp_seq=10 ttl=64 time=1.39 ms

bytes from 192.168.0.252: icmp_seq=11 ttl=64 time=1.27 ms

bytes from 192.168.0.252: icmp_seq=12 ttl=64 time=1.26 ms

bytes from 192.168.0.252: icmp_seq=13 ttl=64 time=1.25 ms

bytes from 192.168.0.252: icmp_seq=14 ttl=64 time=1.48 ms

bytes from 192.168.0.252: icmp_seq=15 ttl=64 time=1.26 ms

bytes from 192.168.0.252: icmp_seq=16 ttl=64 time=1.28 ms

bytes from 192.168.0.252: icmp_seq=17 ttl=64 time=1.39 ms

bytes from 192.168.0.252: icmp_seq=18 ttl=64 time=1.28 ms

bytes from 192.168.0.252: icmp_seq=19 ttl=64 time=1.27 ms

bytes from 192.168.0.252: icmp_seq=20 ttl=64 time=1.38 ms

^C

--- 192.168.0.252 ping statistics ---

packets transmitted, 20 received, 0% packet loss, time 19019ms

rtt min/avg/max/mdev = 1.256/1.401/2.227/0.243 ms

b43-phy0: Broadcom 4306 WLAN found
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)

02:00.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)

Code:

wlan1     IEEE 802.11g  ESSID:"xxxxx"

          Mode:Managed  Frequency:2.422 GHz  Access Point: xx:xx:xx:xx:xx:xx

          Bit Rate=54 Mb/s   Tx-Power=27 dBm

          Retry min limit:7   RTS thr:off   Fragment thr=2352 B

          Link Quality=70/100  Signal level=-60 dBm  Noise level=-67 dBm

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Code:

$ ping 192.168.0.252

PING 192.168.0.252 (192.168.0.252) 56(84) bytes of data.

bytes from 192.168.0.252: icmp_seq=1 ttl=64 time=1.74 ms

bytes from 192.168.0.252: icmp_seq=2 ttl=64 time=1.51 ms

bytes from 192.168.0.252: icmp_seq=3 ttl=64 time=1.42 ms

bytes from 192.168.0.252: icmp_seq=4 ttl=64 time=1.73 ms

bytes from 192.168.0.252: icmp_seq=5 ttl=64 time=1.48 ms

bytes from 192.168.0.252: icmp_seq=6 ttl=64 time=1.59 ms

bytes from 192.168.0.252: icmp_seq=7 ttl=64 time=1.47 ms

bytes from 192.168.0.252: icmp_seq=8 ttl=64 time=1.77 ms

bytes from 192.168.0.252: icmp_seq=9 ttl=64 time=1.49 ms

bytes from 192.168.0.252: icmp_seq=10 ttl=64 time=1.54 ms

bytes from 192.168.0.252: icmp_seq=11 ttl=64 time=1.58 ms

bytes from 192.168.0.252: icmp_seq=12 ttl=64 time=1.73 ms

bytes from 192.168.0.252: icmp_seq=13 ttl=64 time=1.60 ms

bytes from 192.168.0.252: icmp_seq=14 ttl=64 time=1.51 ms

bytes from 192.168.0.252: icmp_seq=15 ttl=64 time=1.40 ms

bytes from 192.168.0.252: icmp_seq=16 ttl=64 time=1.71 ms

bytes from 192.168.0.252: icmp_seq=17 ttl=64 time=1.47 ms

bytes from 192.168.0.252: icmp_seq=18 ttl=64 time=1.47 ms

bytes from 192.168.0.252: icmp_seq=19 ttl=64 time=1.60 ms

bytes from 192.168.0.252: icmp_seq=20 ttl=64 time=1.51 ms

^C

--- 192.168.0.252 ping statistics ---

packets transmitted, 20 received, 0% packet loss, time 19020ms

rtt min/avg/max/mdev = 1.402/1.570/1.776/0.121 ms

Craigus

Post subject:

Posted: Jul 05, 2008 - 12:37 AM

Joined: Jul 04, 2008
Posts: 3

Status: Offline

Thanks, slh - is that with WPA 1 ?

slh

Post subject:

Posted: Jul 05, 2008 - 12:47 AM

Joined: Nov 25, 2006
Posts: 2383

Status: Offline

wpa2psk/ ccmp (AES).

Craigus

Post subject:

Posted: Jul 09, 2008 - 09:30 AM

Joined: Jul 04, 2008
Posts: 3

Status: Offline

Still having this issue:

Code:

craigus@sidux4600:~$ ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=11.0 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=14.6 ms

^C

--- 192.168.1.1 ping statistics ---

15 packets transmitted, 2 received, 86% packet loss, time 14001ms

rtt min/avg/max/mdev = 11.069/12.847/14.625/1.778 ms

craigus@sidux4600:~$ su

Password: 

root@sidux4600:/home/craigus# rmmod b43legacy

root@sidux4600:/home/craigus# rmmod ssb

root@sidux4600:/home/craigus# modprobe ndiswrapper

root@sidux4600:/home/craigus# dhclient3 wlan0

Internet Systems Consortium DHCP Client V3.1.1

Copyright 2004-2008 Internet Systems Consortium.

All rights reserved.

For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:f5:33:ff:0a

Sending on   LPF/wlan0/00:11:f5:33:ff:0a

Sending on   Socket/fallback

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

DHCPOFFER from 192.168.1.1

DHCPREQUEST on wlan0 to 255.255.255.255 port 67

DHCPACK from 192.168.1.1

bound to 192.168.1.193 -- renewal in 3252 seconds.

root@sidux4600:/home/craigus# ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.85 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.76 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.92 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.74 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.72 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.73 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.76 ms

^C

--- 192.168.1.1 ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 6005ms

rtt min/avg/max/mdev = 1.728/1.788/1.926/0.088 ms

root@sidux4600:/home/craigus#

Could someone suggest where I should start troubleshooting ?

Thanks.

houms

Post subject: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

Posted: Jul 16, 2008 - 10:42 PM

Joined: Nov 21, 2007
Posts: 47
Location: US
Status: Offline

RuralRob wrote:

IamNobody wrote:

Thank you RuralRob. Would going to an earlier kernel then 2.6.24 allow me to use both wired and wireless? I only really need wireless but would like to have the wired connection as a backup.

Using a 2.6.23 kernel will solve the problem. My Dell Vostro laptop (with Broadcom Wifi and Ethernet) is still running with 2.6.23.16, after I ran into the problem upgrading to 2.6.24. I'm not sure if there is still an easy way to roll back to a 2.6.23 kernel (doing an "apt-cache search 2.6.23" shows nothing available). So you might have to re-install sidux from one of last year's ISO releases.

Actually I think this can be done via smxi script under kernel options.

Jump to:

All times are GMT - 1 Hours

Previous 1, 2, 3

sidux.com Forum Index » English Forum » Networking