Working wireless for Linux on a Dell C400
26 Oct 2007Turns out you can get the built-in Broadcom wireless card in my laptop (Dell C400) to work, but it did take me a bit of effort.
First off, I'd been looking at the wrong web page for the BCM43XX project — the right one, as Prakash pointed out, is much more up-to-date.
Second, again at Prakash's suggestion (thanks for that!), I downloaded the drivers for the Dell 1370. Running the .exe in Wine extracted the .sys file successfully. However, when I pointed fwcutter at them I got this message:
Sorry, the input file is either wrong or not supported by b43-fwcutter. This file has an unknown MD5sum 8d49f11238815a320880fee9f98b2c92.
So that .sys file was one not supported…at least, not for a while now. That commit message was one of the few I could find that mentioned this number. So I checked out revision 396 from the Subversion repo, compiled it and pointed at the sys file…success! Extraction!
Except that it still didn't work:
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Turns out it had extracted all the files to /lib/firmware/bcm430x_*
,
rather than /lib/firmware/bcm43xx_*
. Quick little shell-fu:
for i in bcm430x_* ; do j=$(echo $i | sed -e's/bcm430x/bcm43xx/') ; sudo ln -s $i $j ; done
and it worked when next I inserted the module…working right now, in fact, despite lots of error messages like:
bcm43xx: WARNING: Writing invalid LOpair (low: 0, high: -115, index: 120) [<d0ba6ebb>] bcm43xx_phy_lo_adjust+0x1e6/0x223 [bcm43xx] [<d0ba7d04>] bcm43xx_phy_lo_g_measure+0x915/0xaeb [bcm43xx] [<c01eb6db>] bit_cursor+0x479/0x48e [<c02a4416>] __sched_text_start+0x686/0x73b [<d0b9dde4>] bcm43xx_periodic_work_handler+0x15c/0x407 [bcm43xx] [<d0b9dc88>] bcm43xx_periodic_work_handler+0x0/0x407 [bcm43xx] [<c0130260>] run_workqueue+0x7d/0x109 [<c0133308>] prepare_to_wait+0x12/0x49 [<c0130a5d>] worker_thread+0x0/0xc7 [<c0130b17>] worker_thread+0xba/0xc7 [<c01331f5>] autoremove_wake_function+0x0/0x35 [<c013312e>] kthread+0x38/0x5e [<c01330f6>] kthread+0x0/0x5e [<c01049c3>] kernel_thread_helper+0x7/0x10
in the kernel log.
No idea why I had to go through so much rigamarole, but hopefully this will save time for someone else. Oh, and for the record: this is with Debian Etch, 2.6.22 kernel from backports.org.
Add a comment:
Name and email required; email is not displayed.
Related Posts
QRP weekend 08 Oct 2018
Open Source Cubesat Workshop 2018 03 Oct 2018
mpd crash? try removing files in /var/lib/mpd/ 11 Aug 2018