bcm4328 chipset not supported by hardy heron

Bug #208183 reported by notarnet
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Medium
Fabián Rodríguez
Nominated for Karmic by benske

Bug Description

The broadcom chipset bcm4328 in not supported in Ubuntu 8.04 beta. In gutsy I used it with ndiswrapper but in hardy don't work.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

NDISWrapper and Windows XP drivers for bcm4328 work just fine for me.

I am running Hardy beta with latest updates, I have been using wireless wince alpha 4 without problems with an HP Pavilion tx1220ca which reports this from lspci:
03:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)

The drivers with NDISwrappers are for Windos XP, and are available here:
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-53245-1&lc=en&cc=ca&dlc=en&product=3444231&os=228

Once i had the SP36684.exe file, I had to install the "wine" package and run it. The installer crashes however the files remain installed at ~/.wine/drive_c/SWSetup/SP36684A. I also install ndsigtk (which brings along all ndiswrapper dependencies) and using the following command I point at the INF file in the above directory:
sudo ndisgtk

Then wireless drivers load and after a few minutes all surrounding wireless networks are visible and can be used.

Revision history for this message
eljacob (tech-celeritas) wrote :

Thank you Fabián,

I've been trying to make my new Acer Ferrari 1100 internal wifi card (BCM4328 rev 01) work with Ubuntu 8.04 for 2 days without success.

I tried Acer's native driver, ndiswrapper, installed Ubuntu x86 and Ubuntu AMD64 final releases, but I simply couldn't connect.

Your hint worked, and I am posting from my newly connected notebook!

Thanks!

Revision history for this message
Matt Schulte (gimpyestrada) wrote :

I also have the BCM4328 (Rev 03) chipset. It is not detected by the default Hardy 8.04 install, as advertised.

Likewise I have had some success with the ndiswrapper. I have a Dell Inspiron 1721, and am using an XP driver that I found on their website.

I don't have a lot of experience with ndiswrapper, so I don't know if this is to be expected, but it seems to take an inordinate amount of time for the wireless to connect up and get an ip address.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Matt, the drivers I linked to are for an HP system. Generally speaking you should try and use drivers for your system if /when using NDISwrapper.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

notarnet, care to share your system's brand and model, as well as the output of the following command ?:
lspci

Thank you.

Revision history for this message
notarnet (notarnet-msn) wrote :
Revision history for this message
Sean Hodges (seanhodges) wrote :

The native Broadcom modules in Linux do not support bcm4328 yet: https://lists.berlios.de/pipermail/bcm43xx-dev/2008-May/007517.html

Best to stick with ndiswrapper for now (or buy a supported wireless card...) The following driver is reported to work with ndiswrapper on Dell machines: http://ftp.us.dell.com/network/R151517.EXE

Revision history for this message
James Schriver (dashua) wrote :

The Broadcom driver for 4318 works flawlessly on the BCM4328. I installed it via restricted drivers manager on Hardy and built the LKM on Intrepid. Better signal strength, connects fasters on start up/suspend.

Revision history for this message
James Schriver (dashua) wrote :

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

That is the driver that works which has also been added to linux-restricted-modules-2.6.24.

https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24 (* Upgrade Broadcom to 5.10.27)

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Correct, in Intrepid a bunch of Broadcom chipsets are now supported out of the box following a commercial agreement between Canonical and Broadcom.

But for Hardy NDISwrapper + Windows drivers as I described initially is the only way this can work.

Now closing this as fix released.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.