kernel-packages team mailing list archive

Thread
Date

[Bug 1289746] Re: 14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: LennartP <1289746@xxxxxxxxxxxxxxxxxx>
Date: Sun, 11 Jan 2015 14:56:21 -0000
Reply-to: Bug 1289746 <1289746@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Description changed:

- 1) lsb_release -rd
- Description: Ubuntu 14.04.1 LTS
- Release: 14.04
-
- 2) apt-cache policy broadcom-sta-source
- broadcom-sta-source:
- Installed: 6.30.223.141-1
- Candidate: 6.30.223.141-1
- Version table:
- *** 6.30.223.141-1 0
- 500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
- 100 /var/lib/dpkg/status
-
- 3) What is expected to happen with my Asus 1225B-SIV047M laptop and
- DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver.
-
- 4) What happened instead: Almost nothing. There is a valid ARP entry for
- the AP in the ARP cache, but there are no replies from ping. The same
- problem existed in 13.10 with this computer about a month ago. However,
- this computer has been able to use the AP w/o problems running 12.04
- until about six months ago, when no longer connect to it. I tried
- upgrading the AP firmware to 1.04 B12 but this didn't change anything.
-
- I have two Android devices of different versions using the AP without
- problems.
-
- However, the wifi works with an AP from Huawei.
-
- uname -a
- Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
-
- lspci -vvnn | grep -A 9 Network
- 04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
- Subsystem: AzureWave Device [1a3b:2047]
- Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
- Latency: 0, Cache Line Size: 64 bytes
- Interrupt: pin A routed to IRQ 17
- Region 0: Memory at fea00000 (64-bit, non-prefetchable) [size=16K]
- Capabilities: <access denied>
- Kernel driver in use: wl
-
- sudo dmidecode -s bios-version
- 209
- sudo dmidecode -s bios-release-date
- 06/05/2012
+ [Impact]
+ Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint).

** Description changed:

[Impact]
- Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint).
+ Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.

** Description changed:

[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
+
+ While this is happening, devices using other software (e.g. Android) are
+ able to utilize WiFi with the same AP without problems.
+
+ The bug can also be reproduced using the ASUS WL-330N AP. There may be
+ other APs with which the bug can also be reproduced.

** Description changed:

While this is happening, devices using other software (e.g. Android) are
able to utilize WiFi with the same AP without problems.

The bug can also be reproduced using the ASUS WL-330N AP. There may be
other APs with which the bug can also be reproduced.
+
+ The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid
+ Vervet.

** Description changed:

While this is happening, devices using other software (e.g. Android) are
able to utilize WiFi with the same AP without problems.

The bug can also be reproduced using the ASUS WL-330N AP. There may be
other APs with which the bug can also be reproduced.

The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid
Vervet.
+
+ The bug should be back-ported to Ubuntu 14.04 because WiFi is a
+ fundamental function for laptops which has worked in Ubuntu LTS before.
+ Speaking for myself, I am reluctant to move to a development release of
+ Ubuntu such as Vivid because problems are to be expected with
+ applications running on top of Ubuntu, e.g. Virtualbox, in such a
+ release.

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1289746

Title:
14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP

Status in bcmwl package in Ubuntu:
Fix Released

Bug description:
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.

While this is happening, devices using other software (e.g. Android)
are able to utilize WiFi with the same AP without problems.

The bug can also be reproduced using the ASUS WL-330N AP. There may be
other APs with which the bug can also be reproduced.

The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid
Vervet.

The bug should be back-ported to Ubuntu 14.04 because WiFi is a
fundamental function for laptops which has worked in Ubuntu LTS
before. Speaking for myself, I am reluctant to move to a development
release of Ubuntu such as Vivid because problems are to be expected
with applications running on top of Ubuntu, e.g. Virtualbox, in such a
release.

[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.

1. Ascertain no other network connection (e.g. wired Ethernet) are
connected to DUT.

2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.

3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289746/+subscriptions