d600 wireless doesn't work correctly

Bug #374603 reported by drick
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

after installing 9.04 and activating the broadcom b43 drivers, i can only stay connected to my wireless AP (linksys wrt600n) for 2-3 minutes at a time before being disconnected. i'm using wpa2 personal with aes encryption.

this seems to be a well documented problem with 9.04 (per the ubuntu forums), but there are no fixes for it.

i'm not sure what information you need, but here is what is requested below:

$ lsb_release -r
Release: 9.04

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/yelp
Package: yelp 2.25.1-0ubuntu5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
drick (crypton-ix) wrote :
Revision history for this message
drick (crypton-ix) wrote :
Download full text (15.0 KiB)

$ lspci -nn
02:03.0 Network controller [0280]: Broadcom Corporation BCM4309 802.11a/b/g [14e4:4324] (rev 03)

$ uname -m
i686

$ dmesg | grep -e ndis -e wlan
[ 24.384426] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 67.684472] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 67.686077] wlan0: authenticated
[ 67.686081] wlan0: associate with AP 00:1d:7e:10:55:e4
[ 67.688498] wlan0: RX AssocResp from 00:1d:7e:10:55:e4 (capab=0x411 status=0 aid=3)
[ 67.688502] wlan0: associated
[ 67.689599] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 78.500030] wlan0: no IPv6 routers present
[ 355.264773] wlan0: deauthenticated
[ 356.264071] wlan0: direct probe to AP 00:1d:7e:10:55:e4 try 1
[ 356.464061] wlan0: direct probe to AP 00:1d:7e:10:55:e4 try 2
[ 356.695487] wlan0: direct probe to AP 00:1d:7e:10:55:e4 try 3
[ 356.892079] wlan0: direct probe to AP 00:1d:7e:10:55:e4 timed out
[ 358.464749] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 358.472170] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 358.475053] wlan0: authenticated
[ 358.475062] wlan0: associate with AP 00:1d:7e:10:55:e4
[ 358.479608] wlan0: RX ReassocResp from 00:1d:7e:10:55:e4 (capab=0x411 status=0 aid=3)
[ 358.479617] wlan0: associated
[ 428.616398] wlan0: deauthenticated
[ 429.616051] wlan0: direct probe to AP 00:1d:7e:10:55:e4 try 1
[ 429.816066] wlan0: direct probe to AP 00:1d:7e:10:55:e4 try 2
[ 430.016051] wlan0: direct probe to AP 00:1d:7e:10:55:e4 try 3
[ 430.216052] wlan0: direct probe to AP 00:1d:7e:10:55:e4 timed out
[ 431.776736] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 431.784149] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 431.984053] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 432.184070] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 432.384060] wlan0: authentication with AP 00:1d:7e:10:55:e4 timed out
[ 443.324754] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 443.348058] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 443.548077] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 443.748066] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 443.948072] wlan0: authentication with AP 00:1d:7e:10:55:e4 timed out
[ 447.012276] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 447.212071] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 447.412069] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 447.612070] wlan0: authentication with AP 00:1d:7e:10:55:e4 timed out
[ 457.020724] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 457.028138] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 457.228073] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 457.229630] wlan0: authenticated
[ 457.229639] wlan0: associate with AP 00:1d:7e:10:55:e4
[ 457.428074] wlan0: associate with AP 00:1d:7e:10:55:e4
[ 457.628072] wlan0: associate with AP 00:1d:7e:10:55:e4
[ 457.828064] wlan0: association with AP 00:1d:7e:10:55:e4 timed out
[ 468.640823] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 468.648151] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 468.848068] wlan0: authenticate with AP 00:1d:7e:10:55:e4
[ 468.850474] wlan0: authenticated
[ 468.850484] wlan0: associate with AP 00:1d:7e:10:55:e4
[ 469.048080] wlan0: ...

Revision history for this message
drick (crypton-ix) wrote :

$ dmesg | grep b43
[ 3.279142] b43-pci-bridge 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
[ 12.547619] b43-phy0: Broadcom 4306 WLAN found
[ 23.836355] input: b43-phy0 as /devices/virtual/input/input9
[ 23.868059] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[ 23.969960] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[ 24.049508] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[ 24.152269] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[ 24.296043] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 24.371060] Registered led device: b43-phy0::tx
[ 24.371083] Registered led device: b43-phy0::rx
[ 24.371104] Registered led device: b43-phy0::radio
[ 24.384053] b43-phy0: Radio turned on by software
[ 1324.470968] b43-pci-bridge 0000:02:03.0: PCI INT A disabled
[ 1325.621015] b43-pci-bridge 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
[ 1325.621035] b43-pci-bridge 0000:02:03.0: restoring config space at offset 0x1 (was 0x102, writing 0x106)
[ 1327.603680] input: b43-phy0 as /devices/virtual/input/input10
[ 1327.752049] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 1327.806979] Registered led device: b43-phy0::tx
[ 1327.807028] Registered led device: b43-phy0::rx
[ 1327.807078] Registered led device: b43-phy0::radio

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this issue. This may seem highly ridiculous, but what video driver do you have? Looking through reports, bug 331952 concerns the B43 driver doing as you described, with Openchrome video drivers. Perhaps this is a duplicate, or there is another video driver causing issues.

Thanks again.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
drick (crypton-ix) wrote :
Download full text (5.4 KiB)

i'm not sure if this is the output you need in order to determine that (i'm a linux n00b), but this is what was posted in the other bug report.

$ lspci -v
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
 Flags: bus master, fast devsel, latency 0
 Memory at e0000000 (32-bit, prefetchable) [size=128M]
 Capabilities: <access denied>
 Kernel driver in use: agpgart-intel
 Kernel modules: intel-agp

00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
 Flags: bus master, 66MHz, fast devsel, latency 32
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
 I/O behind bridge: 0000c000-0000cfff
 Memory behind bridge: fc000000-fdffffff
 Prefetchable memory behind bridge: e8000000-efffffff
 Kernel modules: shpchp

00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
 Subsystem: Intel Corporation Device 4541
 Flags: bus master, medium devsel, latency 0, IRQ 11
 I/O ports at bf80 [size=32]
 Kernel driver in use: uhci_hcd

00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
 Subsystem: Intel Corporation Device 4541
 Flags: bus master, medium devsel, latency 0, IRQ 11
 I/O ports at bf40 [size=32]
 Kernel driver in use: uhci_hcd

00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
 Subsystem: Intel Corporation Device 4541
 Flags: bus master, medium devsel, latency 0, IRQ 11
 I/O ports at bf20 [size=32]
 Kernel driver in use: uhci_hcd

00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) (prog-if 20)
 Subsystem: Dell Device 011d
 Flags: bus master, medium devsel, latency 0, IRQ 11
 Memory at f4fffc00 (32-bit, non-prefetchable) [size=1K]
 Capabilities: <access denied>
 Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
 Flags: bus master, fast devsel, latency 0
 Bus: primary=00, secondary=02, subordinate=0a, sec-latency=32
 I/O behind bridge: 0000d000-0000efff
 Memory behind bridge: f6000000-fbffffff
 Prefetchable memory behind bridge: 50000000-57ffffff
 Kernel modules: shpchp

00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
 Flags: bus master, medium devsel, latency 0
 Kernel modules: iTCO_wdt, intel-rng

00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) (prog-if 8a [Master SecP PriP])
 Subsystem: Intel Corporation Device 4541
 Flags: bus master, medium devsel, latency 0, IRQ 11
 I/O ports at 01f0 [size=8]
 I/O ports at 03f4 [size=1]
 I/O ports at 0170 [size=8]
 I/O ports at 0374 [size=1]
 I/O ports at bfa0 [size=16]
 Memory at 58000000 (32-bit, non-prefetchable) [size=1K]
 Kernel driver in use: ata_piix

00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
 Subsystem: Dell Device 011d
 Flags: bus master, medium devsel, latency 0, IRQ 5
 I/O ports at b800 [size=256]
 I/O ports at bc40 [size=64]
 Memory at f4fff800 (32-bit, non-prefetchable) [size=512]
 Memory at f4fff400 (32-bi...

Read more...

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
drick (crypton-ix) wrote :

fyi, this has now deteriorated to the point that i cannot connect at all anymore

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, 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-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Jeremy Foshee (jeremyfoshee) 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 → Expired
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.