On Thu, 2 Aug 2007, Andy Green wrote: > Somebody in the thread at some point said: > > and, moving on, here's what appears to be the final(?) steps in the > > recipe (from > > http://forums.fedoraforum.org/forum/showthread.php?t=156282): > > > > > > # bcm43xx-fwcutter -w /lib/firmware ~fedora/wl_apsta.o > > # echo 'blacklist bcm43xx' >> /etc/modprobe.d/blacklist > > # modprobe -r bcm43xx > > # modprobe -r ieee80211softmac > > # modprobe -r ieee80211_crypt > > # modprobe -r ieee80211 > > # modprobe -r bcm43xx_mac80211 > > # modprobe bcm43xx_mac80211 > > > > "Then I plugged along and enabled NetworkManager and > > NetworkManagerDispatcher" > > > > does all of that sound sane? if so, i'll give it a shot. > > Since both the old ieee80211 stack driver and the new mac80211-based > one both want to own the same device ID at the moment, your > workaround sounds very needed. the workaround of the blacklisting, is that what you meant? and i just reproduced the above from the URL above, so it's not really *my* workaround, i just wanted a few more eyeballs to see if anything looked out of whack. ok, time to give it a shot. rday -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
