bcm5755m controller prevents Dell D531 from booting Gutsy

Bug #184446 reported by Marc Tardif on 2008-01-19
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

After installing Gutsy from an alternate image on a Dell D531 laptop, the boot process stops at the following line:

  * Running local boot scripts (/etc/rc.local)

Then, the following lines are printed over and over again:

  [ 47.8000000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.

Is there a way to circumvent this problem so that the machine can boot and perhaps another microcode file can be installed?

Marc Tardif (cr3) wrote :

After disabling the wireless controller in the BIOS, the bcm43xx error message is no longer displayed but the live image still seems to block on:

  * Running local boot scripts (/etc/rc.local)

The alternate image is now working though, but there is no networking during the installation. To be continued...

Nick_Hill (nick-nickhill) wrote :

BCM4301 blocks boot on Hardy. bug218256
May or may not be related.

Hi Marc,

Was this issue ever resolved with Hardy's final release?

Changed in linux:
status: New → Incomplete

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Manoj Iyer (manjo) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers