[bcm43xx] Flight 6 Install Detecting Network Hardware freezes

Bug #39885 reported by Aaron Throckmorton
12
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I have a Dell Inspiron 5100 laptop. It has been running Breezy fine with no issues. I have been trying to get Dapper installed. I boot from the CD select language and keyboard layout, but when it gets to the "Detecting network hardware" screen it locks up and won't go any further. I can't even ALT-CTRL-F2 to get to another console to see what's going on.

If I disable my Wireless network card, which is a broadcom chipset (Dell TrueMobile 1400 Dual Band WLAN mini-PCI Card. I have been using ndiswrapper with the bcmwl5.sys driver from Dell in Breezy), the installation works fine. In that case, if I re-enable my wireless card and attempt to boot it locks up at hardware detection during boot and won't go any further. Disabling again allows a normal boot.

After installing and booting with the card disabled, I did an apt-get update, apt-get upgrade, re-enabled the card and still had the same problem.

The live CD boots normally. I don't have wireless available, but I can at least get to the desktop.

I'm not sure what other information to post, but I'll get whatever info you need from me.

Revision history for this message
Aaron Throckmorton (opus) wrote :

This issue is still occuring with Dapper Beta 1. I used the system upgrade feature to upgrade my breezy to dapper and am running dapper, but I still cannot get the system to boot if the wireless card is enabled.

Revision history for this message
ShamrockUK (uplift) wrote :

Try adding bcm43xx to /etc/modprobe.d/blacklist and restarting before you modprobe ndiswrapper.

I can never get ndiswrapper to work as it did in breezy without doing this first - a big regression IMO.

Revision history for this message
Aaron Throckmorton (opus) wrote :

I added bcm42xx to /etc/modprobe.d/blacklist, rebooted, enabled the wireless card in bios, and let ubuntu boot. Lo and behold it booted fine. After a quick modprobe ndiswrapper, networkmanager found and connected to my wireless network.

This still seems like a bug to me. What is the bcm43xx module? If it is a native linux driver it doesn't work very well with this card. Otherwise, why is it being loaded?

Revision history for this message
ShamrockUK (uplift) wrote :

I don't understand it exactly - it is a native Linux driver but I don't think it's complete. Walkthroughs say you have to use another programme to 'cut' the relevent windows files and then combine them.

It has managed to break ndiswrapper on every single Dapper install I've done, on a variety of machines, so I think it's a huge bug. Not really knowing enough about what bcm4xxx does though I've never felt knowledgeable enough to bugreport it.

By all means file a report (or confirm an existing one) though if it broke ndiswrapper for you - with only 3 weeks to go there's not much time left :)

Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 39885] Re: [bcm43xx] Flight 6 Install Detecting Network Hardware freezes

bcm43xx is indeed the native linux driver. You need to instaal the
firmware for it manually since broadcom has not gien us permission to
distribute it. That is definitely easier than ndiswrapper though.

Revision history for this message
Martin Pitt (pitti) wrote :

Can you please try a dapper or current edgy live CD to check whether this problem still exists in the newer kernels?

BTW, Dapper's and Edgy's kernel also have native support for Broadcom chipsets now, so if you install the firmware, you do not need to bother with ndiswrapper any more.

Changed in hal:
status: Unconfirmed → Needs Info
Revision history for this message
Geoffrey Buck (moncalcruiser) wrote :

With Dapper (kernel 2.6.15-26) on a Dell Latitude D600 with TrueMobile 1400 (Broadcom 4309 chipset): After extracting firmware from any version of the driver with bcm43xx-fwcutter the system does a hard lock when the driver is loaded.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-source-2.6.17 (Ubuntu) because there has been no activity for 60 days.]

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.