[bcm43xx] No matter what it simply will not connect. It scan and sees the networks, but it cannot connect.

Bug #37765 reported by ViriiGuy
18
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I am using a Broadcom 4306 wireless card in my Emachines M6805 laptop. I have installed fwcutter and used it to load the needed files.

I can scan and see my wireless networks.. One is only secured by MAC address and one is secured by 128bit WEP. But I cannot connect to either. I then installed Network manager and nm-applet. I commented out my metwork devices as instructed and it is working fine. It sees my wireless networks, but again simply cannot connect.

On the WEP secured network, it will ask me for the key. I put it in and it never connects. On the MAC Secured network, it doe snot ask for a key but again it cannot connect.

I have included a text file with the various log snippits I have been asked for on the forums.

Ok I cannot find the upload button, but here is the text.

dmesg | grep ipw
Nothing returned

dmesg |grep eth0
Code:

[4294710.548000] ADDRCONF(NETDEV_UP): eth0: link is not ready

dmesg | grep ieee80211
Code:

[4294691.427000] ieee80211_crypt: registered algorithm 'NULL' [4294691.441000] ieee80211: 802.11 data/management/control stack, git-1.1.7 [4294691.441000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>

lsmod | grep ipw
Nothing returned.

route -n
Code:

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

contents of
ls /lib/firmware/`uname -r`
Code:

acx bcm43xx_initval05.fw atmel_at76c502_3com.bin bcm43xx_initval06.fw atmel_at76c502_3com-wpa.bin bcm43xx_initval07.fw atmel_at76c502.bin bcm43xx_initval09.fw atmel_at76c502d.bin bcm43xx_initval10.fw atmel_at76c502d-wpa.bin bcm43xx_microcode2.fw atmel_at76c502e.bin bcm43xx_microcode4.fw atmel_at76c502e-wpa.bin bcm43xx_microcode5.fw atmel_at76c502-wpa.bin bcm43xx_pcm4.fw atmel_at76c503-i3861.bin bcm43xx_pcm5.fw atmel_at76c503-i3863.bin ipw2100-1.3.fw atmel_at76c503-rfmd-0.90.2-140.bin ipw2100-1.3-i.fw atmel_at76c503-rfmd-acc.bin ipw2100-1.3-p.fw atmel_at76c503-rfmd.bin ipw2200-bss.fw atmel_at76c504_2958-wpa.bin ipw2200-ibss.fw atmel_at76c504a_2958-wpa.bin ipw2200-sniffer.fw atmel_at76c504.bin isl3890 atmel_at76c504c-wpa.bin zd1211b-WS11Ub.fw atmel_at76c505a-rfmd2958.bin zd1211b-WS11UPh.fw atmel_at76c505-rfmd2958.bin zd1211b-WS11UPhm.fw atmel_at76c505-rfmd.bin zd1211b-WS11UPhR.fw atmel_at76c506.bin zd1211b-WS11Ur.fw atmel_at76c506-wpa.bin zd1211-WS11Ub.fw bcm43xx_initval01.fw zd1211-WS11UPh.fw bcm43xx_initval02.fw zd1211-WS11UPhm.fw bcm43xx_initval03.fw zd1211-WS11UPhR.fw bcm43xx_initval04.fw zd1211-WS11Ur.fw

iwconfig
Code:

lo no wireless extensions. eth0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4306" Mode:Managed Frequency=2.437 GHz Access Point: Invalid Bit Rate=54 Mb/s Tx-Power=15 dBm RTS thr:off Fragment thr:off eth1 no wireless extensions. sit0 no wireless extensions.

iwlist eth0 scan
Code:

eth0 Scan completed : Cell 01 - Address: 00:13:10:4B:FD:18 ESSID:"Sneezer" Protocol:IEEE 802.11g Mode:Master Channel:6 Encryption key:on Bit Rates:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Quality=100/100 Signal level=-32 dBm Extra: Last beacon: 8ms ago Cell 02 - Address: 00:0F:3D:5A:3A:C0 ESSID:"default" Protocol:IEEE 802.11bg Mode:Master Channel:6 Encryption key:on Bit Rates:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Quality=100/100 Signal level=-80 dBm Extra: Last beacon: 5716ms ago

ping 192.168.1.1
Code:

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.81 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.783 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.730 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.730 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.728 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.718 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.719 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.790 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.716 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.717 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.720 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.718 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.706 ms

Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 37765] No matter what it simply will not connect. It scan and sees the networks, but it cannot connect.

> Bit Rates:54 Mb/s

Set the bitrate to 11mbit.

Revision history for this message
ViriiGuy (viriiguy) wrote : Re: No matter what it simply will not connect. It scan and sees the networks, but it cannot connect.

Ok I tried setting my bitrate to 11Mb/s But this did not solve the problem.

Now this is what I get from dmesg....

[4344296.577000] SoftMAC: Authentication response received from 00:0f:3d:5a:3a:c0 but no queue item exists.
[4344297.806000] SoftMAC: Authentication response received from 00:0f:3d:5a:3a:c0 but no queue item exists.
[4344300.264000] SoftMAC: Authentication response received from 00:0f:3d:5a:3a:c0 but no queue item exists.
[4344300.498000] SoftMAC: Open Authentication completed with 00:13:10:4b:fd:18
[4344304.566000] SoftMAC: Authentication response received from 00:0f:3d:5a:3a:c0 but no queue item exists.
[4344313.168000] SoftMAC: Authentication response received from 00:0f:3d:5a:3a:c0 but no queue item exists.
[4344313.519000] SoftMAC: Open Authentication completed with 00:13:10:4b:fd:18
[4344336.620000] eth1: no IPv6 routers present

Revision history for this message
neoflight (srnvas) wrote :

I have similar experience with my tp-42 laptop with ipw2200.
I CAN connect to the wireless at school with vpnc. Wired is also ok. I cannot connect at home wher we use WEP. we dont transmit the essid.
1. i am surprised that i was never asked for a password (even to generate) by the keyring manager. I have installed it and its there...

2. nm-applet shows the network (after i enter the essid and hex key)
but there is no signal. I could see all the network from our neighbors with the signal strength. When i try to connect using nm-applet then it repeatedly keep asking the WEP key with no result.

3. wireless without encryption is ok as far as i could see...

Revision history for this message
neoflight (srnvas) wrote :

to add to my previous message..i could connect to the same home network with windows -XP... !!!

Revision history for this message
Mike Homer (homerhomer) wrote :

I'm i the same boat with the same issue. I also have a bcm43xx card in compaq persario av2102 ( pretty-sorry-ohh ).
The only way around it that I have found is to go to command line and connect there.
?

Revision history for this message
ViriiGuy (viriiguy) wrote :

I cannot even make mine work from terminal. I have been trying and trying and trying. I never see a request for IP on my router from my laptop under linux.

I am utterly convinced that for whatever reason my card is only able to recieve but not send. At least this is how it seems to me.
I have tried on every type of wireless network you can imagine.
Under none of the options do the results change.

The card DOES work, I use it in windows on a nearly daily basis for gaming.

Revision history for this message
ViriiGuy (viriiguy) wrote :

Whoops!!
I don't know exactly how that happened.
My bad.

Revision history for this message
Ben Collins (ben-collins) wrote :

Please test latest 2.6.15-20 kernels.

Revision history for this message
ViriiGuy (viriiguy) wrote :

Ok Ben, I updated and tried again. Much MUCH closer!!!!
It actually connected to a MAC address secured only wireless network. I have not tried other configs yet, I will tomorrow.

But it still does not get online. It is able to connect, but it reports a 0% connection and still no IP. I am 3 foot from the router, and have and excellent signal for at least another 200 foot diameter in windows.

Below I have my dmesg, ifconfig and iwconfig readouts.

dmesg
[4295418.654000] SoftMAC: Open Authentication completed with 00:blah:blah:blah

ifconfig
eth0 Link encap:Ethernet HWaddr 00:90:96:AD:A9:F2
          inet addr:169.254.182.211 Bcast:169.254.255.255 Mask:255.255.0.0
          inet6 addr: fe80::290:96ff:fead:a9f2/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:17 errors:0 dropped:99 overruns:0 frame:0
          TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4613 (4.5 KiB) TX bytes:7305 (7.1 KiB)
          Interrupt:9 Base address:0xc000

iwconfig
eth0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4306"
          Mode:Managed Frequency=2.484 GHz Access Point: Invalid
          Bit Rate=11 Mb/s Tx-Power=15 dBm
          RTS thr:off Fragment thr:off

I am not sure what you changed, but it almost worked!!! Please keep up the good work and cut my cable :D

Randy

Revision history for this message
Ivan Matveich (ivan-matveich) wrote :

Try running "iwlist scan" now.

That's what makes mine start working.

Revision history for this message
ViriiGuy (viriiguy) wrote :

Running iwlist scan makes no differance for me.

I tried today with a WEP network, and no luck. It will not authenticate.

My Dmesg reports,
[4297010.801000] printk: 2 messages suppressed.
[4297010.801000] SoftMAC: Can't perform deauthentication, network is not authenticated.

So as it stands I can connect to a open system, but cannot get an IP from it still. And the signal reports as zero. I still cannot connect to a WEP at all.

Thanks,
Randy

Revision history for this message
GonzO (gonzo) wrote :

ViriiGuy: which WEP key are you using? Is it the first one (slot 1) available in your router, or is it another one? I was having difficulty connecting with key 4 set as default (now bug 42860), but when I put the same key in the router's first available key slot and told the router to use WEP key 1, it connected fine.

Revision history for this message
ViriiGuy (viriiguy) wrote : Re: [Bug 37765] Re: [bcm43xx] No matter what it simply will not connect. It scan and sees the networks, but it cannot connect.

It is the first one. But like I said, no matter what wireless security
all the way
to no security, it will not connect :(

On 5/4/06, GonzO <email address hidden> wrote:
> ViriiGuy: which WEP key are you using? Is it the first one (slot 1)
> available in your router, or is it another one? I was having difficulty
> connecting with key 4 set as default (now bug 42860), but when I put the
> same key in the router's first available key slot and told the router to
> use WEP key 1, it connected fine.
>
> --
> [bcm43xx] No matter what it simply will not connect. It scan and sees the networks, but it cannot connect.
> https://launchpad.net/bugs/37765
>

Revision history for this message
darksarin (ben-orchard) wrote :

I have the bcm4309 (I think), which now Identifies as bcm 1390 Mini-PCI. It will not connect, even when I have the network completely unsecured (which _should_ be the easiest way to connect.

It WILL NOT connect. The entire thing just does not work. Not open, not WEP, not WPA.

Please help!

Revision history for this message
darksarin (ben-orchard) wrote :

I got it to connect (once!) using WPA, but it wouldn't go to the outside world--it just hit the router, then nothing. this is sitting about 2 ft from the router with 0 interference, and the manager seeing 100% signal strength.

Help!

Revision history for this message
Christopher Denter (dennda) wrote : [gutsy] [bcm43xx] No matter what it simply will not connect. It scan and sees the networks, but it cannot connect.

Hi.
Please see this bug: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/124159
I attached a bugreport.
I think these two bugs are somehow related.

regards

Revision history for this message
Christopher Denter (dennda) wrote :

Hi.
I was able to solve my issue by executing "sudo iwconfig eth1 rate 5.5M".
The only issue related to broadcom left (for me) is the lights being always on as reported in another bug.

Read here for further information: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/124159

Could you please verify if this solves your problems, too?

regards

Revision history for this message
piotr (peter-hartmann) wrote :

thanks dennda,

"sudo iwconfig eth1 rate 5.5M" worked for me. I had the same problem that I could scan the network but not connect.

Gabriel Ruiz (anakron)
Changed in linux-source-2.6.15:
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
ViriiGuy (viriiguy) wrote : Invitation to connect on LinkedIn

LinkedIn
------------

Bug,

I have been asked by several people in the past to join this site, so I finally figured it was time.

Most of you in this list I have worked with in one form or another. Some of you have only had email correspondence with me, however here is to the chance to work together in the future.

- Randy Walker

Learn more:
https://www.linkedin.com/e/isd/528000134/ERjSxvOI/

------------------------------------------

What is LinkedIn and why should you join?
http://learn.linkedin.com/what-is-linkedin

------
(c) 2009, LinkedIn Corporation

Revision history for this message
ViriiGuy (viriiguy) wrote : My deepest apologies...

It has come to my attention, that when I joined a popular networking site
for IT professionals, called LinkedIn.com, I inadvertently added every
single person whom I have ever replied to with my gmail account to be
invited. This was certainly not intentional. As a matter of fact I
only selected about 50 of you. The rest of you, were not supposed to be
invited. Some of you have joined Linkedin because of me. Others of you have
only recieved emails from Linkedin asking you to join. Again, I am sorry.
I have yet to figure out exactly how this happened, but rest assured this is
the last time I ever let a site just "sync" to my contact list. I knew
better, but yet I still did it.
Again, I apologize and it will not happen again. I am still trying to get
all the errant contacts that were added to be invited, removed. So for the
time being, please bear with me and ignore any future emails from Linkedin,
unless of coarse you are an IT Pro that I have worked with. Then by all
means, please join my network.

Again, I apologize for any inconvenience.

Thank you,

Randy Walker
Sr. Technician/Network Administrator
LM Computers Ltd.
(902)-928-0189

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Can anyone confirm this issue remains with the latest Jaunty 9.04 release? http://www.ubuntu.com/getubuntu/download . Thanks.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.