BCM4312 802.11b/g [14e4:4315] (rev 01) wireless card not working in Ubuntu

Asked by sig_alph

After most recent update, my wireless stopped working in my Dell Mini?

I just updated my Mini using the internal wireless, after the update I went to go back online but the Wireless network is gone. I tried to change the properties but the wireless option was not listed.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#1

Hi,

Please first connect your network card to the wireless router using a LAN cable.

Then please follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->
Terminal"

Step 2: Run the following commands (type each then hit <enter>)

sudo iwlist scanning
nm-tool
iwconfig
ifconfig
sudo lshw -C network
lspci -nn
lsusb
uname -a
dmesg | grep ound
dmesg | grep illswitch

Step 3: Post results (cut/paste terminal output from each command) here

Regards,

Mark

Revision history for this message
sig_alph (sig-alph) said :
#2

I will give it a shot!

Revision history for this message
juancarlospaco (juancarlospaco) said :
#3

Optional (you need Windows Drivers):
sudo apt-get install ndisgtk

Revision history for this message
sig_alph (sig-alph) said :
#4

I am having trouble getting the LAN to work. It will not login?

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#5

Hi,

What do you mean by "it will not login"?

Have you tried powercycling the router? Try turning the router off for at least half an hour, turn it on again and then turn your pc back on. Does the pc get a valid IP address from the router after rebooting the router, while using the wired connection?

Do you have other pc's connected to the router? Can those other pc's connect to the Internet?

Regards,

Mark

Revision history for this message
sig_alph (sig-alph) said :
#6

Bad connection at first. I took it to work and tried the commands:

First command:

scott@scott:~$ sudo iwlist scanning
[sudo] password for scott:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

scott@scott:~$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Revision history for this message
sig_alph (sig-alph) said :
#7

2nd Command:

scott@scott:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0 ----------------------------------------------------------------
  NM Path: /org/freedesktop/NetworkManager/Devices/eth0
  Type: Wired
  Driver: r8169
  Active: yes
  HW Address: 00:21:70:D0:CE:93

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

  Wired Settings
    Hardware Link: yes

  IP Settings:
    IP Address: 10.0.0.56
    Subnet Mask: 255.255.255.0
    Broadcast: 10.0.0.255
    Gateway: 10.0.0.1
    Primary DNS: 10.0.0.10
    Secondary DNS: 0.0.0.0

Revision history for this message
sig_alph (sig-alph) said :
#8

3rd

scott@scott:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

Revision history for this message
sig_alph (sig-alph) said :
#9

4th:

scott@scott:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:70:d0:ce:93
          inet addr:10.0.0.56 Bcast:10.0.0.255 Mask:255.255.255.0
          inet6 addr: fe80::221:70ff:fed0:ce93/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1601 errors:0 dropped:292558059 overruns:0 frame:0
          TX packets:1509 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1256850 (1.1 MB) TX bytes:250018 (244.1 KB)
          Interrupt:220 Base address:0x6000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:1065 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1065 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:63360 (61.8 KB) TX bytes:63360 (61.8 KB)

Revision history for this message
sig_alph (sig-alph) said :
#10

5th

scott@scott:~$ sudo ishw -C network
sudo: ishw: command not found

6th:

scott@scott:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 02)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 [8086:27d2] (rev 02)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 [8086:27d4] (rev 02)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 02)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 02)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 02)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 02)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 02)
02:00.0 System peripheral [0880]: JMicron Technologies, Inc. Unknown device [197b:2382]
02:00.2 SD Host controller [0805]: JMicron Technologies, Inc. Unknown device [197b:2381]
02:00.3 System peripheral [0880]: JMicron Technologies, Inc. Unknown device [197b:2383]
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)

7th:

scott@scott:~$ lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Revision history for this message
sig_alph (sig-alph) said :
#11

8th:scott@scott:~$ uname -a
Linux scott 2.6.24-19-lpia #1 SMP Mon Nov 3 15:25:26 UTC 2008 i686 GNU/Linux

9th

scott@scott:~$ dmesg l grep ound
Usage: dmesg [-c] [-n level] [-s bufsize]

10th

scott@scott:~$ dmesg l grep illswitch
Usage: dmesg [-c] [-n level] [-s bufsize]

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#12

Hi,

Can you please send the output of the following commands:

dmesg | grep ound
dmesg | grep illswitch

The character between dmesg and grep is the pipe character, it is not the L in small letters. The sign is | not l

On an azerty keyboard, you can find the pipe character under the 1 key, next to the & symbol.

Regards,

Mark

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#13

Hi,

Or you can just copy paste what I wrote on this thread and paste it into the terminal, instead of typing it.

Regards,

Mark

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#14

Hi,

Please also send output of following command:

sudo lshw -C network

The l in lshw is a small L, not an i

Regards,

Mark

Revision history for this message
sig_alph (sig-alph) said :
#15

scott@scott:~$ dmesg | grep ound
[ 0.000000] found SMP MP-table at 000f7fa0
[ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
[ 9.081024] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
[ 9.349714] No dock devices found.
[ 9.511984] pnp: PnP ACPI: found 11 devices
[ 10.079142] assign_interrupt_mode Found MSI capability
[ 10.079480] assign_interrupt_mode Found MSI capability
[ 10.079823] assign_interrupt_mode Found MSI capability
[ 10.597652] hub 1-0:1.0: USB hub found
[ 10.699120] hub 2-0:1.0: USB hub found
[ 10.803013] hub 3-0:1.0: USB hub found
[ 10.906912] hub 4-0:1.0: USB hub found
[ 12.221804] sdhci: SDHCI controller found at 0000:02:00.2 [197b:2381] (rev 0)
[ 12.609079] hub 5-0:1.0: USB hub found
[ 16.932037] iTCO_wdt: Found a ICH7-M TCO device (Version=2, TCOBASE=0x1060)
scott@scott:~$ dmesg | grep illswitch
scott@scott:~$
scott@scott:~$ dmesg | grep illswitch
scott@scott:~$
scott@scott:~$ sudo lshw -C network
[sudo] password for scott:
sudo: lshw: command not found
scott@scott:~$ sudo lshw -C network
sudo: lshw: command not found
scott@scott:~$
scott@scott:~$ sudo lshw -C network
sudo: lshw: command not found

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#16

Hi,

OK, you have a special version of Broadcom chipset, 14e4:4315, which requires a special installation routine.

Please try the following installation procedure:

Boot your laptop and enter BIOS setup utility: choose option "load default values".

Insert the Ubuntu 8.10 LiveCD. Boot from this CD and install Ubuntu 8.10 onto your harddisk using the LiveCD session.

After installation, reboot into the installed Ubuntu 8.10 system.

Download the following drivers:

http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5_10_27_14.tar.gz

which come from this site:

http://www.broadcom.com/support/802.11/linux_sta.php

Follow these build and installation instructions carefully:

http://www.broadcom.com/docs/linux_sta/README.txt

In a terminal, type : sudo gedit /etc/modules

Add the following line to the end of the modules file

wl

sudo gedit /etc/modprobe.d/blacklist

Add the following lines to the end of the blacklist file

blacklist b43
blacklist bcm43xx
blacklist b43legacy
blacklist ndiswrapper

Reboot and then test wireless.

Regards,

Mark

Revision history for this message
Peter Whittaker (pwwnow) said :
#17

A couple of comments re the previous post:

The DELL Mini does not come with a CD so the instructions provided will not work: If someone wants to migrate their DELL Mini to Ubuntu 8.10, they must create a live USB stick. And while this is not necessarily the end of the world (it is relatively straightforward), I don't think we should be recommending it, for two reasons.

First, and most importantly, Ubuntu 8.04 is an LTS release: That is, users should be able to use it and live with it for years. Most importantly in this case, Ubuntu LTS is what DELL shipped and all that DELL is likely to support. I'm of the opinion that recommending a course of action likely to impact someone's paid support is inadvisable.

Second, and almost as importantly, the DELL Mini ships with a number of utilities and programs that are not in the standard repositories or at least that are not installed by default. I've been told flat out by my daughter not to "fix" the wireless on her Mini if it means losing the programs that are installed out of the box. I'm not taking the chance. She's happy without the wireless and happy with what's installed.

If we are to recommend a corrective course of action, then it should, wait, MUST, be non-destructive. That is, it must preserve all of the functionality of the existing box while correcting any errors.

The ideal would be for some brave soul to experiment with their Mini and find a a) "fix LTS wifi" path (best case) or b) "get to 8.10 and preserve all existing apps" path. Option (a) is the one most likely to preserve the customer's support investment. Either path should be relatively straightforward for the less technical.

Also, please note that the DELL Mini does NOT ship with lshw. I had to install manually:

sudo apt-get install lshw

That worked fine. And lshw does not have to been run as root for this case - and anytime you can avoid using root privileges, you should (I'm a security consultant, free security advice is an occupational hazard :->).

Can you help with this problem?

Provide an answer of your own, or ask sig_alph for more information if necessary.

To post a message you must log in.