<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-html" lang="x-unicode"> <br>
I've been testing the 12.04 Ubuntu release, and hit an immediate
issue with one machine; the live ISO boots only as far as the b43
driver, and then the machine is entirely non responsive and has to
be powered off.<br>
<br>
The last thing displayed is ..<br>
<br>
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found<br>
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found<br>
b43-phy0 ERROR: You must go to <a class="moz-txt-link-freetext"
href="http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware">http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware</a>
and download the correct firmware for this driver version. Please
carefully read all instructions on this website.<br>
<br>
If I put the following in the kernel command line<br>
<br>
b43.blacklist=yes<br>
<br>
the module behaves differently<br>
<br>
"b43: Unknown parameter 'blacklist'"<br>
<br>
and the problem goes away. There's probably a better way to
achieve the same goal, but this solution has the benefit that it
is easy to switch it on and off via grub.<br>
<br>
<br>
<br>
I've not attempted to install firmware, as for most 'normal'
users, the opportunity doesn't arise. Appreciate that for your
understanding that maybe of interest. Let me know.<br>
<br>
<br>
<br>
You may find further useful detail on the bug over at: <a
class="moz-txt-link-freetext"
href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950295">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/950295</a>
- including various diagnostic data that was captured
automatically for kernel issues.<br>
<br>
The system is 32bit.<br>
<br>
The 12.04 kernel is, currently: "Ubuntu 3.2.0-20.<wbr>32-generic-pae
3.2.12<wbr>"<br>
<br>
The only way to make that boot is with the kernel argument.<br>
<br>
<br>
<br>
As requested on the b43 linuxwireless.org page, please find below
the uname info and lspci info, and attached the dmesg.<br>
<br>
As part of the investigation for the ubuntu bug, I've been testing
Canonical's vanilla kernel builds; more info about those here: <a
class="moz-txt-link-freetext"
href="https://wiki.ubuntu.com/Kernel/MainlineBuilds">https://wiki.ubuntu.com/Kernel/MainlineBuilds</a><br>
<br>
I booted the system off a kernel that works; obviously the bug
isn't illustrated. This is the most recent canonical provided
mainline 'trunk' (3.x.0) kernel which boots.<br>
<br>
$ uname -a<br>
Linux tecumseh 3.1.0-030100-generic #201110241006 SMP Mon Oct 24
14:20:44 UTC 2011 i686 i686 i386 GNU/Linux<br>
<br>
ben@tecumseh:~$ lspci -vvn|grep 4318 -A7<br>
06:02.0 0280: 14e4:4318 (rev 02)<br>
Subsystem: 1468:0312<br>
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-<br>
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-<br>
Latency: 64<br>
Interrupt: pin A routed to IRQ 22<br>
Region 0: Memory at d0002000 (32-bit, non-prefetchable)
[size=8K]<br>
Kernel driver in use: b43-pci-bridge<br>
<br>
I've tried lots of other kernels; including<br>
<br>
3.3.0 - hangs<br>
3.2.0 - hangs<br>
<br>
I've also tested a few of the 3.2.0 release candidates. I worked
back to 3.2.0-rc2; It also hangs. Canonical didn't do a 32bit
3.2.0-rc1, so I can't test that.<br>
<br>
None of the kernels I've tested down the 3.1.x branch have the
problem.<br>
<br>
The Ubuntu bug page has all the kernels I've tried; where
/proc/cmdline doesn't show the argument, I was able to boot it.<br>
<br>
Please do let me know what other info / procedures would help to
troubleshoot this. <br>
<br>
thanks, Ben <br>
</div>
</body>
</html>