Hardy 8.04 hangs on boot with Broadcom BCM4301 Wireless mini-PCI card. b43legacy-phy0:Broadcom 4301 WLAN found

Bug #218256 reported by Nick_Hill
This bug report is a duplicate of:  Bug #192720: Loading b43legacy freezes computer. Edit Remove
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: hal

Boot Hardy 8.04 beta CD on a laptop. Laptop hangs with progress bar frozen.

Boot laptop again, at option screen press F6 delete quiet and change splash to nospash to show boot details.

User will see: [142.93849] b43legacy-phy0:Broadcom 4301 WLAN found

as the final boot message when machine hangs.

Dismantle laptop and remove Broadcom mini-PCI card. Laptop boots normally with 8.04 CD.

Broadcom card is known working with Windows XP, and card does not prevent 7.10 cd from booting.

The test machine is a Toshiba Satellite Pro 4600 800Mhz P3 I815 chipset.

description: updated
Revision history for this message
Nick_Hill (nick-nickhill) wrote : Re: Hardy 8.04 beta CD hangs on boot at b43legacy-phy0: Broadcom 4301 WLAN found

Install 8.04 with Broadcom mini-PCI removed. Re-boot with card inserted. Booting hangs in same place as with CD.

Will next remove card, run updates, then try again.

Revision history for this message
Nick_Hill (nick-nickhill) wrote :

Run upates on system. Made no difference. System hangs on boot with Broadcom card connected.

Revision history for this message
Nick_Hill (nick-nickhill) wrote :

Swapped card from a BCM4301 to a BCM4306. System does not hang with BCM4306.

description: updated
Revision history for this message
Josip Sokcevic (sokcevic) wrote :

I have the same problem with my notebook. Anyone have solution?

Revision history for this message
Ryan Stutsman (stutsman-cs) wrote :

Likewise same problem. Total deadlock, CPU spins. BCM4301 MiniPCI as well.

Revision history for this message
Ryan Stutsman (stutsman-cs) wrote :

This is an issue with the kernel module not hal. Couldn't find a way to file this against linux-image-2.6.24-16-386 so this is the next best place.

Revision history for this message
Nick_Hill (nick-nickhill) wrote :

Given that three sources have verified this bug, and there is enough information to validate, this passes as confirmed.

This is a complete killer for those with built-in BCM4301 mini-PCI cards, (which are fairly common in older P3 / Athlon M laptops), Their computers will simply stop booting on upgrade to 8,04.

I can loan a BCM4301 mini-PCI card to a developer working on this issue.

Changed in linux:
status: New → Confirmed
Revision history for this message
Kristoffer Broberg (kristoffer-broberg) wrote :

Same here. Total lockup.

Revision history for this message
BJDelta (bjdelta) wrote :

Same problem here.
Just to give a clue, the system hangs up with 2.6.24 kernel where the wireless chip is detected as 4301, but if I choose kernel 2.6.22 at boot, the system starts up and the chip – tiping in the terminal “lspci | grep Broadcom” – is detected as 4303. So, bad detection by the kernel 2.6.24? Anyway also with kernel 2.6.22 the wireless card doesn’t work (tiping “iwconfig” in the terminal “no wireless extension” is returned) either with the repository driver or the “b43” and “b43legacy” open source driver downloaded from http://downloads.openwrt.org/sources/ , nonetheless the total remove of old bmc43xxx driver and Ndiswrapper from system.

Revision history for this message
Nick_Hill (nick-nickhill) wrote :

BjDelta, When my system hangs on default Hardy, the actual chip is 4301 according to markings on chip, so the reported number is correct. However, the driver parameters or register set may be mis-selected.

Revision history for this message
Saivann Carignan (oxmosys) 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 192720, 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.