Upgrading from Ub. 10.10 to 11.04 makes Broad-com Wireless Adapter Fail

Bug #774300 reported by Erwin Michel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-nettool

After Upgrading to 11.04 from 10.10 my internal Broadcom Wireless adapter does not work. wlan devices does not exist.
PC: Acer Aspire 5601Z
See output of lshw - c network:

@laptop:~$ sudo lshw -C network
  *-network
       description: Network controller
       product: BCM4311 802.11b/g WLAN
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:05:00.0
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=b43-pci-bridge latency=0
       resources: irq:19 memory:d0000000-d0003fff
  *-network
       description: Ethernet interface
       product: BCM4401-B0 100Base-TX
       vendor: Broadcom Corporation
       physical id: 1
       bus info: pci@0000:06:01.0
       logical name: eth0
       version: 02
       serial: 00:16:d4:dd:6e:37
       size: 100Mbit/s
       capacity: 100Mbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=2.0 duplex=full ip=192.168.1.69 latency=64 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:21 memory:d0100000-d0101fff

Output of lspci
05:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)

Under Additional Drivers it says Broadcom STA Wireless Driver is activated and in use.

Thanks for the help.
Erv

Revision history for this message
Erwin Michel (erwin-swisscc) wrote :

NM-Tool output.... only sees Auto eth0

laptop:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0 [Auto eth0] ----------------------------------------------------
  Type: Wired
  Driver: b44
  State: connected
  Default: yes
  HW Address: 00:16:D4:DD:6E:37

  Capabilities:
    Carrier Detect: yes
    Speed: 100 Mb/s

  Wired Properties
    Carrier: on

  IPv4 Settings:
    Address: 192.168.1.69
    Prefix: 24 (255.255.255.0)
    Gateway: 192.168.1.254

    DNS: 192.168.1.254

Gary M (garym)
affects: gnome-nettool (Ubuntu) → ubuntu
tags: added: hw-specific natty needs-reassignment regression-release
removed: issue upgrade
affects: ubuntu → linux (Ubuntu)
tags: removed: needs-reassignment
Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

Please post the output of:
lspci -k | grep Network --after-context 3
to see what drivers are availabe/in use.

Revision history for this message
Wolfgang Kufner (wolfgangkufner) wrote :

And:
lspci -vvnn | grep Network
to see the exact type of hardware.

Revision history for this message
Erwin Michel (erwin-swisscc) wrote :

output of lspci -k | grep Network --after-context 3

~$ lspci -k | grep Network --after-context 3
05:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
 Subsystem: AMBIT Microsystem Corp. Device 0422
 Kernel driver in use: b43-pci-bridge
 Kernel modules: wl, ssb

Output of 0lspci -vvnn | grep network.

05:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)

Revision history for this message
Erwin Michel (erwin-swisscc) wrote :

Aftre the upgrade when it did not work, I took out the Restricted Broadcom Driver, and then used the GUI under System to reinstall.

Same issues.

Erv

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #732677, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.