On Sun, 2007-12-30 at 14:45 +0100, Steve_Tind wrote: > This is regarding a thread in the devel list: > > http://fcp.surfsite.org/modules/newbb/viewtopic.php?viewmode=flat&order=ASC&topic_id=45257&forum=11 [1] > > I hope you guys are reading this. > > I have managed to get mine working, but via a somewhat difficult route. > > I have used kmod-ndiswrapper and a driver I used (64 bit) successfully for some time. > > Whilst mucking around I noticed that after a rmmod ndiswrapper the logs showed a requirement for firmware, so I followed the link & instructions in the link (I needed to be using the ndiswrapper wireless to do this) : > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware [2] > > I used the firmware on that site, and populated /lib/firmware/b43 with the required firmware stuff. > > I then did rmmod ndiswrapper, modprobe b43 and about 20s later Network Manager re-established a connection using the b43-pci-bridge but the LED on the laptop wasn't on, but who cares. > > Yippee I though, not more ndiswrapper. > > However on next boot no wireless, even though all the logs seemed to show everything as OK. > > What I now do is use ndiswrapper to get the card into a warm state, and then rmmod ndiswrapper, modprobe b43 in rc.local > > I do this because the b43 driver runs my card better then ndiswrapper! Eh, did you edit /etc/modprobe.conf and change your driver from ndiswrapper to b43? > > It seems like I just need better firmware, however the b43-fwcutter doesn't recognise the checksum on the bcmwl5.sys I used for ndiswrapper. > > Where can I submit my bcmwl5.sys to be included as a recognised file by b43-fwcutter. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - We have enough youth, how about a fountain of SMART? - ----------------------------------------------------------------------
