http://bugzilla.rpmfusion.org/show_bug.cgi?id=96
--- Comment #13 from Chris Nolan <[EMAIL PROTECTED]> 2008-11-02 17:39:07 --- (In reply to comment #12) > Just a reminder for the next time: All packages normally should "just work" -- > hence if you always need to do something manually to make the software that is > being packaged work (like you did) then you should make the package do it for > everyone. Sure. I was thinking that the ndiswrapper package doesn't blacklist any modules when installed (the user has to do it manually) but I understand now that this is because ndiswrapper may be used for a variety of drivers so the blacklisted modules would be different depending on the driver(s) installed using ndiswrapper. > Then you should add a file /etc/modprobe.d/blacklist-for-broadcom-wl (or > something like that; just "blacklist" is to generic and might conflict with > other packages) with that stuff in it to the package. > > Note that this will blacklist b43 even for broadcom hardware that is not > supported by b43. We should in the long term work towards a better solution > that doesn't have this problem. Ok, I've now included /etc/modprobe.d/broadcom-wl-blacklist file in the userland package. > > echo "alias wlan0 wl" >> /etc/modprobe.conf > > Is this really needed? That will break if people have more then one wlan > device > in their system. I've tested it without this alias and it seems it is not needed (at least on my setup). I will maybe include something about it in the README.txt because it may be required for some people or for people who wish to configure their broadcom card to use a specific interface. > You choice. Stripped down is likely easier to maintain. Think I'll go with a new README.txt since the information we should provide probably differs significantly from the info in the standard README.txt -- Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
