Problem: wireless not working even using bcm43xx fwcutter trick used on previous occasions successfully.<\/p>\n
Looked in system log – System>Administration>SystemLog kern.log
\nERROR: Firmware file “b43\/ucode5.fw” not found or load failed.
\nHuh? That’s not even a file made by bcm43xx.<\/p>\n
Initial diagnostics:
\nlspci | grep Network
\nreturned:
\n02:0b.0 Network controller: Broadcom Corporation BCM4306 802.11b\/g Wireless LAN Controller (rev 03)<\/p>\n
Solution: NB don’t bother using make etc on the tarball – just grab the suitable deb file from the hardy util site. Get by searching for Hardy util b43. Obviously, if I had access to the internet I could use synaptic or apt-get but no wireless = no internet (see Catch 22 ;-)).<\/p>\n then gksu b43-fwcutter -w \/lib\/firmware ~Desktop\/wl_apsta-3.130.20.0.o Working on the assumption that I can use the legacy v3 file (incorrect – see below).<\/p>\n Still a problem – there is now a folder called \/lib\/firmware\/b43legacy New issue (possibly progress though): Hmmm – deleted all old bcm43xx firmware files from main \/lib\/firmware folder. Rebooted.<\/p>\n Nope.<\/p>\n Ah – download v4 wl_apsta.o file get wl_apsta.o from inside that file and put on desktop. <\/p>\n then sudo b43-fwcutter -w \/lib\/firmware ~Desktop\/wl_apsta.o<\/p>\n Right – everything was automatically put it in b43 subfolder, not b43legacy. Starting to click into place. As is often the case, it all makes total sense backwards \ud83d\ude09 .<\/p>\n Looking good – can see my wireless network showing with a decent signal. Supply password. Hmmm waiting for network key.<\/p>\n To be continued …<\/p>\n [Easter 2008] – use latest, v4 wl_apsta.o And continued …<\/p>\n [Hardy Heron RC] Problem: wireless not working even using bcm43xx fwcutter trick used on previous occasions successfully. Looked in system log – System>Administration>SystemLog kern.log ERROR: Firmware file “b43\/ucode5.fw” not found or load failed. Huh? That’s not even a file made by bcm43xx. Initial … Continue reading
\nDon’t use BCM43xx any more – doesn’t work. Use b43-fwcutter. See http:\/\/linuxwireless.org\/en\/users\/Drivers\/b43#fw-b43legacy<\/a><\/p>\n
\nNB gksu not sudo when a graphical application<\/p>\n
\nSo tried:
\nsudo nautilus \/lib\/firmware\/b43legacy and it contains ucode5.fw etc
\nShame the folder has legacy as part of its name
\nRenamed the folder to b43 in a shameless attempt to get the system going<\/p>\n
\nb43-phy0 ERROR: YOUR FIRMWARE IS TOO OLD. Firmware from binary drivers older than version 4.x is unsupported. You must upgrade your firmware files.<\/p>\n
\nsudo rm -r \/lib\/firmware\/b43legacy<\/p>\n
\nwget http:\/\/downloads.openwrt.org\/sources\/broadcom-wl-4.80.53.0.tar.bz2<\/p>\n
\nsudo b43-fwcutter -w \/lib\/firmware ~Desktop\/wl_apsta.o
\nHmm still waiting for network key.
\nEven tried unsecured neighbourhood wireless network. Still no success.<\/p>\n
\nWaiting for network key (sigh …)
\nAt least dual\/multiple monitor support is getting much better.
\nIntrepid Ibex
\nHmmm try v11 rather than v8 of b43-fwcutter deb (google b43 deb)
\nNope<\/p>\n","protected":false},"excerpt":{"rendered":"