sidux.com :: View topic - Broadcom Wireless Trouble

sidux.com

Networking - Broadcom Wireless Trouble

ICU_RN - Apr 22, 2008 - 12:35 AM
Post subject: Broadcom Wireless Trouble

I just updated my PC to sidux Nyx, official release, and I am trying to get my broadcom wireless wifi card to connect to the web, but no success. The driver seems to be installed but I just can't get connected using Linux. I did connect to the web using Windows XP so I know the hardware works. I don't know how to configure Ceni or use resolvconf. Anyone have any suggestions?

RobF - Apr 22, 2008 - 09:52 AM
Post subject: Re: Broadcom Wireless Trouble

ICU_RN wrote:

There are two ways of getting the Broadcom cards to work in sidux:

1. Using the native Linux drivers b43 or bcm43xx (that's the current default)

In sidux set up a wired ethernet connection using Ceni from KMenu>Internet>Ceni (Internet access is required to download proprietory driver firmware), open a console as root and run

apt-get install bcm43xx-fwcutter b43-fwcutter

Reboot and run Ceni to configure the wireless interface wlan0 which should now be recognized.

2. Using a Windows driver via ndiswrapper

In sidux set up a wired ethernet connection and download the Windows XP driver appropriate for your Broadcom card. E.g. you can get it from the support webpage of your laptop maker or from your Windows installation or from

http://ndiswrapper.sourceforge.net/joom ... id,list_b/

You need the .inf, .sys and .cat files, all in one folder.

Open a console as root and run

ndiswrapper -i /path_to_driver_folder/drivername.inf [this sets up the Windows driver, needs to be done only once]
ndiswrapper -l [you should get the message: xxxxxx : driver installed ... device (xxxx:xxxx) present]
rmmod ndiswrapper
rmmod b43
rmmod b43legacy
rmmod bcm43xx
rmmod b44
rmmod ohci_hcd
rmmod ssb
modprobe ndiswrapper [WiFi light comes on as the ndiswrapper kernel module is loaded and the driver is installed]

Then run Ceni to configure the wireless interface wlan0. You should be connected. If not, check with # route -n whether there is a route to WAN through the default gateway. If there isn't, as root run

route add default gateway IP_address_of_your_gateway

Method #1 doesn't seem to work well on my system (bcm4311, using WPA-TSK). E.g. a full system upgrade that involved a mere 75 MB of upgrades and run via the smxi script took 2 hours, and downloading the Jave runtime environment (around 35 MB) took more than half an hour, with DL speeds of between 1 and 10 Kb/sec. Similarly, rendering webpages is very sluggish. Method #2, on the other hand, provides fairly snappy internet access.

daves - Apr 22, 2008 - 02:11 PM
Post subject: RE: Re: Broadcom Wireless Trouble

I think option 1 is funny. For some people, a wired connection is just not possible (at University, for instance, where the dorms are only provided wireless Internet). (Believe me, there are situations like this.) It presents a conundrum such as:

Person 1: "How do I get my Internet connection going?"

Person 2: "Just 'apt-get install' your firmware for your wireless card."

Person 1: "But my Internet's not working to begin with."

Person 2: (silence)

There really needs to be a way that people can download a package/script from a friend's computer or a computer at work or something where they just copy it over to their sidux install and run it.

ICU_RN - Apr 22, 2008 - 02:21 PM
Post subject:

Thanks RobF, I will try suggestion #1. I tried using Ceni but have problems using the DHCP option. For example, the default submask setting is 255.255.255.255 but should be 255.255.255.0. How can I change this number. Anyway, I will post what the Ceni program says once I configure it and perhaps someone can help me trouble shoot. I have spent many months trying to get this wifi card to work. Thanks for your prompt reply!

RuralRob - Apr 22, 2008 - 03:48 PM
Post subject:

ICU_RN wrote:

Thanks RobF, I will try suggestion #1.

If your machine is relatively new and has a draft-N Wifi chip, like the BCM4328, then you will need to go with method #2, as the Linux native (b43) driver does not yet support the newer chips.

slam - Apr 22, 2008 - 07:30 PM
Post subject: Re: RE: Re: Broadcom Wireless Trouble

daves wrote:

That's exactly what you should do: Download the firmware package(s) you need, copy them over to the installed systems and install them there.
Greetings,
Chris

IamNobody - Apr 22, 2008 - 11:39 PM
Post subject: RE: Re: RE: Re: Broadcom Wireless Trouble

I have a new Dell 1721 with the new 4328 chip. I have loaded the driver with ndiswrapper and it is listed as installed and present however I am unable to configure it. It does not show in ceni or sidux control center network configuration. I just uninstalled from ndiswrapper and am trying method 2 but when I type mmod in the root console it says unknown command. Any ideas?

IamNobody - Apr 22, 2008 - 11:43 PM
Post subject: RE: Re: RE: Re: Broadcom Wireless Trouble

Also when I type ndiswrapper -l it shows that it is using an alternate driver and ssb. Is this the problem?

damentz - Apr 22, 2008 - 11:45 PM
Post subject: RE: Re: RE: Re: Broadcom Wireless Trouble

Quote:

I just uninstalled from ndiswrapper and am trying method 2 but when I type mmod in the root console it says unknown command. Any ideas?

Ya, mmod isn't a command. Did you want modprobe to load modules or rmmod to unload?
And two, of course, you need to be root.

ICU_RN - Apr 22, 2008 - 11:54 PM
Post subject:

Is there any other linux tool to use besides Ceni to configure the wifi card?

IamNobody - Apr 22, 2008 - 11:57 PM
Post subject: RE: Re: RE: Re: Broadcom Wireless Trouble

ok..if mmod isn't a command then why is it mentioned as part of the code? I am root.. This is what ndiswrapper returns:

root@mainserver:~# ndiswrapper -l
bcmwl6 : driver installed
device (14E4:4328) present (alternate driver: ssb)

and this is from sidux control center:

Host/Kernel/OS "mainserver" running Linux 2.6.24-2.6.24.5.slh.1-sidux-amd64 x86_64 [ sidux 2008-01 Νυξ - kde-full - (200804120109) ]
CPU Info (1) AMD Turion 64 X2 Mobile TL-60 512 KB cache flags( sse3 nx lm svm ) clocked at [ 2000.000 MHz ]
(2) AMD Turion 64 X2 Mobile TL-60 512 KB cache flags( sse3 nx lm svm ) clocked at [ 2000.000 MHz ]
Videocard ATI RS690M [Radeon X1200 Series] X.Org 1.4.0.90 [ 1440x900@60.0hz ]
Network cards Broadcom BCM4328 802.11a/b/g/n
Broadcom BCM4401-B0 100Base-TX
Processes 108 | Uptime 59min | Memory 172.2/1761.2MB | HDD ATA SAMSUNG HM250JI Size 250GB (4%used) | Client Shell wrapper | Infobash v3.01

The system sees the card but I cannot configure it. What is the problem?

RuralRob - Apr 23, 2008 - 01:34 AM
Post subject: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

IamNobody wrote:

Also when I type ndiswrapper -l it shows that it is using an alternate driver and ssb. Is this the problem?

That is indeed the problem. Your computer must also have a Broadcom-controlled wired Ethernet port. The b44 driver that controls it will also grab the WiFi chip, blocking ndiswrapper's access to it. This is a bug that cropped up with the 2.6.24 kernel, and apparently, due to hostility towards ndiswrapper's violations of the GPL license, the kernel developers have no intention of fixing this. They basically want to force everyone off of ndiswrapper over time with the new kernels. So bottom line, you need to remove the b44 driver (and lose your wired Ethernet port), or don't use ndiswrapper.

IamNobody - Apr 23, 2008 - 04:30 AM
Post subject: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

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.

RuralRob - Apr 23, 2008 - 06:34 AM
Post subject: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

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.

IamNobody - Apr 23, 2008 - 07:57 AM
Post subject: RE: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

Thanks again RuralRob! You've been a big help!

IamNobody - Apr 23, 2008 - 09:38 AM
Post subject: RE: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

i've been looking for one of last years releases but cannot seem to find one. Any idea where one is available?

IamNobody - Apr 23, 2008 - 09:49 AM
Post subject: RE: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

ok...I was able to install kernel 2.6.23.16 by doing the dist update in siduxcc. I skipped the updates and went straight to kernel install and then advanced install. It gave me a list of about 8 kernels. There are even some older then 2.6.23.16.

fjayn - Apr 24, 2008 - 08:55 PM
Post subject: RE: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

it is possible to install older kernels after the d-u part in smxi.

ICU_RN - Apr 26, 2008 - 12:29 AM
Post subject: Configuring Ceni

I installed the broadcom driver onto my sidux linux computer and turned on the wifi card, wlan0, and turned off the eth0 card. Then launched Ceni and configured the wlan0:

Here is some info:

root@siduxbox:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"belkin54g"
Mode:Managed Frequency:2.462 GHz Access Point: 00:11:50:D3:D7:5A
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:3B5D-3C7D-207E-37DC-EEED-D301-E3
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@siduxbox:~# fw-detect
root@siduxbox:~# dmesg |grep -i wireless
root@siduxbox:~# lspci -vv |grep -i wireless

02:0c.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

This is what Ceni reports when wlan0 was configured for DHCP:

root@siduxbox:~# ceni
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/virtualbox-ose
run-parts: executing /etc/network/if-pre-up.d/whereami
Continuing at if-pre-up,wlan0
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
Internet Systems Consortium DHCP Client V3.1.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:60:be:10:de
Sending on LPF/wlan0/00:1d:60:be:10:de
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

What is wrong here. Why can't I connect to the web? One thing I do see is Ceni wants the subnet to be 255.255.255.255. I think this should be 255.255.255.0 but how do I change this?

mb - Apr 28, 2008 - 07:23 PM
Post subject:

I recently had difficulty with a broadcom wireless card for my laptop. It seemed no matter what modules/drivers I loaded for the card it just would not work. Here is what I did:

1. install ndiswrapper

2. find a the proper driver. I found mine on the sourceforge.net ndiswrapper page. Install it into ndiswrapper application.

3. black list the drivers which are currently being loaded automatically at start up. For example one might be" bcm43xx".

4. Hopefully it will work for as it did for me but I am truly no expert with wireless networking. Google would help you to find more detailed tutorials. I am also sure if I made any mistakes/oversights others will correct me.

5. Just as an aside I believe the upcoming kernel release 2.6.25 will have native broadcom support so perhaps all the ndiswrapper stuff may not be needed.

mdmarmer - Apr 29, 2008 - 12:20 AM
Post subject:

mine was working with kernel 2.6.23, and it works on 64-bit 2.6.24, but with 32-bit 2.6.24 the wireless won't work. The native driver won't find wlan0 and doesn't allow me to reinstall the firmware, and ndiswrapper shows the driver is installed, but it shows alternate driver ssb (which is needed by ohci_hcd, and the system doesn't work at all without ohci_hcd). In ndiswrapper I can't bring up wlan0 -- it doesn't connect to my access point.

This is HP L2000 laptop with RTL-8139 ethernet and Broadcom BCM-4318 wireless (Air Force One 54g)

Ethernet works fine, and wireless worked with older kernels. I really don't want to use older kernel because fglrx video driver works better with 2.6.24

Any ideas?

Thanks!

Mike

ICU_RN - May 04, 2008 - 12:43 AM
Post subject:

Thanks mdmarmer, I will wait until kernel 2.6.25 is released and then try to reinstall the wifi. I'm not sure what to do next? I will wait to see what some of you linux pros conclude when 2.6.25 is tested and keep reading this post. Thanks.

Brandon - May 21, 2008 - 03:49 AM
Post subject: Broadcom 4328

Has anyone got broadcom 4328 rev 3 to work? I have tied everything I found in the forums and cant get it work. I am new to linux and do not know any commands hardly. I need help as my laptop doesnt have a regular pcmia slot and need wireless to work.

Thanks

ICU_RN - May 31, 2008 - 10:24 PM
Post subject:

I just reinstalled sidux nyx (32bit) and then dist-upgraded it and installed kernel 2.6.25 as previously recommended. I have to get my Broadcom 4318 wifi to work. Now what? Do I use ndswrapper or fwcutter? RuralRob wrote: "If your machine is relatively new and has a draft-N Wifi chip, like the BCM4328, then you will need to go with method #2, as the Linux native (b43) driver does not yet support the newer chips." Any suggestions?

slh - May 31, 2008 - 10:36 PM
Post subject:

BCM4318 should be well supported by native drivers.

ICU_RN - Jun 02, 2008 - 08:24 AM
Post subject:

I currently am using kernel 2.6.25.4 and using fwcutter I installed the b43 driver. Using the Control Panel, I deactivated my eth0 and activated wlan0. The wifi beacon icon on my task bar shows red but blinking. When I mouse over it it says it is communicating with my wifi router, belkin54g, but there is no actual data being transferred back and forth. I set up the wifi card to DHCP and WEP encryption using HEX. I still can't get a web page to show up in my browser, meaning I am not connected to the internet. Anyone have any suggestions what went wrong? Thanks for your support!

ICU_RN - Jun 27, 2008 - 05:27 PM
Post subject:

I still cannot get my Broadcom BCM4318 wifi to work. Does anyone know if I need to blacklist the ndiswrapper or am I missing something? If so, how is this actually done. Thanks for all your help and patience with us newbies Embarassed

slh - Jun 27, 2008 - 05:57 PM
Post subject:

If you installed ndiswrapper windows drivers for broadcom in the past, you might have still blacklisted b43/ ssb somehow - additionally you need to install b43-fwcutter.

ICU_RN - Jun 28, 2008 - 12:17 AM
Post subject:

Hi slh. I did not use ndiswrapper. I used fwcutter to install the b43 driver.

root@siduxbox:~# lspci -vv |grep -i wireless

02:0c.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

The wifi beacon icon on my task bar shows red but blinking. When I mouse over it it says it is communicating with my wifi router, belkin54g, but there is no actual data being transferred back and forth. I set up the wifi card to DHCP and WEP encryption using HEX. I still can't get a web page to show up in my browser, meaning I am not connected to the internet.

root@siduxbox:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"belkin54g"
Mode:Managed Frequency:2.462 GHz Access Point: 00:11:50:D3:D7:5A
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:3B5D-3C7D-207E-37DC-EEED-D301-E3
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ICU_RN - Jun 30, 2008 - 11:57 AM
Post subject: Wifi LAN

Anyone familiar with Linuxant's DriverLoader software ($20)

http://www.linuxant.com/driverloader/

hoogewoud - Jul 02, 2008 - 02:26 PM
Post subject: RE: Wifi LAN

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 - Jul 03, 2008 - 02:52 AM
Post subject: RE: Wifi LAN

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.

Craigus - Jul 04, 2008 - 11:29 AM
Post subject:

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 - Jul 04, 2008 - 11:53 AM
Post subject:

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 - Jul 04, 2008 - 11:37 PM
Post subject:

Thanks, slh - is that with WPA 1 ?

slh - Jul 04, 2008 - 11:47 PM
Post subject:

wpa2psk/ ccmp (AES).

Craigus - Jul 09, 2008 - 08:30 AM
Post subject:

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 - Jul 16, 2008 - 09:42 PM
Post subject: Re: RE: Re: RE: Re: RE: Re: Broadcom Wireless Trouble

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.

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