<div dir="ltr">for good measure, i thought it was clear that the script would do that.<br>and to your point - i will, honestly i wanted too, but it did not work for me. compromising as i am, i need my wireless to function.<br>
<br>Ehud<br><br><br><div class="gmail_quote">On Mon, Apr 26, 2010 at 10:43 PM, Tony Godshall <span dir="ltr"><<a href="mailto:tony@of.net">tony@of.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Gah! That installs their whole driver.<br>
<br>
When I did it I just extracted the .fw file and put it in the place<br>
the good open source kernel driver (b43) could find it (/lib/firmware)<br>
<br>
What you just did blocked the open source kernel driver and said use<br>
the proprietary driver.<br>
<br>
It's bad enough to use a proprietary blob for the firmware- I'd avoid<br>
using a proprietary blob driver since it will break future kernels.<br>
<br>
Best Regards.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
On Mon, Apr 26, 2010 at 21:17, Ehud Kaldor <<a href="mailto:ehud.kaldor@gmail.com">ehud.kaldor@gmail.com</a>> wrote:<br>
> thanks.<br>
> as i mentioned, i found the driver buried in the Broadcom, in the basement<br>
> of the planning office, where both the lights and stairs had been removed,<br>
> in an old<br>
> filing cabinet locked in a disused lavatory with a sign on the door saying<br>
> “Beware of the Leopard.” here:<br>
> <a href="http://www.broadcom.com/support/802.11/linux_sta.php" target="_blank">http://www.broadcom.com/support/802.11/linux_sta.php</a><br>
> the readme includes detailed instructions on how to install, which i<br>
> summarized in the following script:<br>
><br>
> #broadcom wireless driver<br>
> yum install -y gcc kernel-devel kernel-headers wget #needed to build<br>
> mkdir broadcom<br>
> cd broadcom<br>
> wget<br>
> <a href="http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5.60.48.36.tar.gz" target="_blank">http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5.60.48.36.tar.gz</a><br>
> tar xvf hybrid-portsrc-x86_32-v5.60.48.36.tar.gz<br>
> make clean<br>
> make<br>
> rmmod b43<br>
> rmmod ssb<br>
> rmmod wl<br>
> echo "blacklist ssb" >> /etc/modprobe.d/blacklist.conf<br>
> echo "blacklist b43" >> /etc/modprobe.d/blacklist.conf<br>
> modprobe lib80211<br>
> modprobe ieee80211_crypt_tkip<br>
> insmod wl.ko<br>
> cp wl.ko /lib/modules/`uname -r`/kernel/drivers/net/wireless<br>
> depmod -a<br>
> echo modeprobe wl >> /etc/rc.local<br>
> cd ..<br>
> rm -rf broadcom<br>
> rm -f hybrid-portsrc-x86_32-v5.60.48.36.tar.gz<br>
><br>
> worked for me (unfortunately, more than once). half my kingdom for whoever<br>
> writes a default package that includes low-level driver for the major arch's<br>
> of wireless out there.<br>
><br>
> Ehud<br>
><br>
><br>
><br>
> On Mon, Apr 26, 2010 at 5:53 PM, Tony Godshall <<a href="mailto:tony@of.net">tony@of.net</a>> wrote:<br>
>><br>
>> ...<br>
>> [Rick wrote]<br>
>> > And, you know what? I'm betting that your sole problem is not having<br>
>> > that firmware image, so you may now be in luck.<br>
>> ...<br>
>><br>
>> [my 2c]<br>
>> If the system identifies the right driver but there's no firmware for<br>
>> it, dmesg should show you a message to that effect. It did when I had<br>
>> to configure "the dreaded b43".<br>
>> # dmesg|egrep -i 'firmware|b43'<br>
>><br>
>> Tony<br>
><br>
><br>
</div></div></blockquote></div><br></div>