bcm43xx won't connect to wep secured network

Bug #230047 reported by mspanc
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am unable to connect with my bcm43xx to WEP-secured network.

WiFi card works perfectly under windows. I also use it under ubuntu 8.04 in different location, where WPA network exists with success. Password is something like ba4771af11 so it's propably hex 64-bit password?

syslog:

May 13 20:17:42 saepia kernel: [ 286.707293] eth2: authenticate with AP 00:17:9a:47:8f:a1
May 13 20:17:42 saepia kernel: [ 286.908674] eth2: authentication with AP 00:17:9a:47:8f:a1 timed out
May 13 20:17:48 saepia kernel: [ 292.137739] eth2: Initial auth_alg=0
May 13 20:17:48 saepia kernel: [ 292.137748] eth2: authenticate with AP 00:17:9a:47:8f:a1
May 13 20:17:48 saepia NetworkManager: <info> Old device 'eth2' activating, won't change.
May 13 20:17:48 saepia kernel: [ 292.338186] eth2: authenticate with AP 00:17:9a:47:8f:a1
May 13 20:17:48 saepia kernel: [ 292.539576] eth2: authenticate with AP 00:17:9a:47:8f:a1
May 13 20:17:48 saepia kernel: [ 292.740986] eth2: authentication with AP 00:17:9a:47:8f:a1 timed out

dmesg:

[ 303.802122] eth2: Initial auth_alg=0
[ 303.802132] eth2: authenticate with AP 00:17:9a:47:8f:a1
[ 304.002740] eth2: authenticate with AP 00:17:9a:47:8f:a1
[ 304.204128] eth2: authenticate with AP 00:17:9a:47:8f:a1
[ 304.405520] eth2: authentication with AP 00:17:9a:47:8f:a1 timed out

lsmod:
Module Size Used by
af_packet 23812 0
ipv6 267780 8
pppoatm 6656 0
ppp_generic 29588 1 pppoatm
slhc 7040 1 ppp_generic
binfmt_misc 12808 1
ppdev 10372 0
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
rfkill_input 5504 0
cpufreq_powersave 2688 0
cpufreq_stats 7104 0
cpufreq_userspace 5284 0
cpufreq_ondemand 9740 0
cpufreq_conservative 8712 0
freq_table 5536 2 cpufreq_stats,cpufreq_ondemand
container 5632 0
sbs 15112 0
sbshc 7680 1 sbs
dock 11280 0
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
sbp2 24072 0
parport_pc 36260 0
lp 12324 0
parport 37832 3 ppdev,parport_pc,lp
pcmcia 40876 0
joydev 13120 0
video 19856 0
output 4736 1 video
arc4 2944 2
ecb 4480 2
blkcipher 8324 1 ecb
b43 115104 0
snd_via82xx 29464 3
rfkill 8592 3 rfkill_input,b43
gameport 16008 1 snd_via82xx
snd_mpu401_uart 9728 1 snd_via82xx
mac80211 165652 1 b43
cfg80211 15112 1 mac80211
snd_seq_dummy 4868 0
led_class 6020 1 b43
input_polldev 5896 1 b43
snd_via82xx_modem 16264 0
snd_ac97_codec 101028 2 snd_via82xx,snd_via82xx_modem
serio_raw 7940 0
ac 6916 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
battery 14212 0
ac97_bus 3072 1 snd_ac97_codec
button 9232 0
snd_rawmidi 25760 2 snd_mpu401_uart,snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
snd_pcm 78596 4 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
i2c_viapro 9876 0
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
yenta_socket 27276 1
rsrc_nonstatic 13696 1 yenta_socket
evdev 13056 7
shpchp 34452 0
pci_hotplug 30880 1 shpchp
i2c_core 24832 1 i2c_viapro
via_agp 11136 1
agpgart 34760 1 via_agp
snd 56996 19 snd_via82xx,snd_mpu401_uart,snd_seq_dummy,snd_via82xx_modem,snd_ac97_codec,snd_seq_oss,snd_rawmidi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq,snd_timer,snd_seq_device
pcmcia_core 40596 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_page_alloc 11400 3 snd_via82xx,snd_via82xx_modem,snd_pcm
soundcore 8800 1 snd
pcspkr 4224 0
psmouse 40336 0
reiserfs 239616 1
sr_mod 17956 0
cdrom 37408 1 sr_mod
usbhid 31872 0
hid 38784 1 usbhid
sg 36880 0
sd_mod 30720 3
pata_via 13316 0
ata_generic 8324 0
via_rhine 26632 0
mii 6400 1 via_rhine
pata_acpi 8320 0
sata_via 12420 2
ehci_hcd 37900 0
uhci_hcd 27024 0
libata 159344 4 pata_via,ata_generic,pata_acpi,sata_via
ohci1394 33584 0
usbcore 146028 4 usbhid,ehci_hcd,uhci_hcd
scsi_mod 151436 5 sbp2,sr_mod,sg,sd_mod,libata
ieee1394 93752 2 sbp2,ohci1394
ssb 32260 1 b43
thermal 16796 0
processor 36872 2 thermal
fan 5636 0
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 1

Please let me know how to gather more detailed debug information.

Revision history for this message
Chris Pratt (pratt70) wrote :
Download full text (12.1 KiB)

Having same issue -- Broadcom using b43 module can do open and WPA, but not WEP:

Linux host 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686 GNU/Linux

0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 01)
 Subsystem: Dell Unknown device 0007
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 17
 Region 0: Memory at f9ffc000 (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 Legacy Endpoint IRQ 0
  Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
  Device: Latency L0s <4us, L1 unlimited
  Device: AtnBtn- AtnInd- PwrInd-
  Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
  Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
  Link: Latency L0s <4us, L1 <64us
  Link: ASPM L0s Enabled RCB 64 bytes CommClk+ ExtSynch-
  Link: Speed 2.5Gb/s, Width x1

Symptoms: NM keeps asking for WEP key/passphrase though input correctly each time and previously stored...

From syslog:

Jun 18 18:02:09 host NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'WIRELESS'.
Jun 18 18:02:09 host NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0) New wireless user key for network 'WIRELESS' received.
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jun 18 18:02:18 host NetworkManager: <info> Activation (wlan0/wireless): access point 'WIRELESS' is encrypted, and a key exists. No new key needed.
Jun 18 18:02:19 host NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jun 18 18:02:19 host NetworkManager: <info> SUP: response was 'OK'
Jun 18 18:02:20 host NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jun 18 18:02:20 host NetworkManager: <info> SUP: response was 'OK'
Jun 18 18:02:20 host NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jun 18 18:02:20 host NetworkManager: <info> SUP: response was '0'
Jun 18 18:02:20 host NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 564d4c414e'
Jun 18 1...

Revision history for this message
Alexander Sack (asac) wrote :

broadcom is a company completely neglecting linux. this is why we only have binary drivers, which noone in the linux community can fix. Wep might be one of the things you are out of luck. Most likely WPA works.

Remember when you next time buy a laptop or something to not buy anything from broadcom - at least not if they havent changed their attitude.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

please reboot, reproduce and attach the complete syslog

Revision history for this message
Alexander Sack (asac) wrote :

you might also want to try the latest firmware. use fwcutter to get and install that.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
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.