https://www.slackwiki.com/api.php?action=feedcontributions&feedformat=atom&user=Dijetlo 2026-04-08T11:20:36Z User contributions MediaWiki 1.40.0 https://www.slackwiki.com/index.php?title=Talk:Broadcom_Wireless&diff=963 2015-01-27T00:06:24Z

<p>Dijetlo: /* Issue with ssb as a dependency of the b44 module */ new section</p> <hr /> <div>I just made a couple of relatively minor edits to the page (20140402):<br /> First, admins shouldn't edit files in /lib/modprobe.d/ - those get overwritten on package upgrades; only /etc/modprobe.d/ or /run/modprobe.d/ should be used for local sysadmin edits, as they are not overwritten on upgrades. However, /run is on a tmpfs, so it is not persistent across reboots; as such, it would applicable for e.g. rules that are auto-generated on system startup based on some nonstable attributes (whether that's a good idea is another discussion entirely, but I think not). Given all of that, /etc/modprobe.d/ is the best location -- its intent is for sysadmins to copy files from /lib/modprobe.d/ and edit the copies if needed (same-named files in both /etc/modprobe.d/ and /lib/modprobe.d/ are handled such that the file in /etc/modprobe.d/ takes precedence). This leads up to my second point:<br /> Second, since there's no need in this particular case to override *all* of what's in /lib/modprobe.d/blacklist.conf (you only want to *add* content to it), it's a bit cleaner to just create a new file in /etc/modprobe.d/ with a sensible name and put what you want in it. --rworkman<br /> <br /> == Issue with ssb as a dependency of the b44 module ==<br /> <br /> Copying /lib/modprobe.d/bcm43xx.conf to /etc/modprobe.d/bcm43xx.conf and then adding the blacklist entries there worked except for the ssb module. It seems ssb is a dependency of module b44 and is being successfully loaded which blocked the function of the wl module.<br /> The fix was to run sbo packages b43-fwcutter and b43-firmware.<br /> <br /> This page is a valuable resource for checking compliance.<br /> http://linuxwireless.org/en/users/Drivers/b43/<br /> <br /> Does anybody mind if I add a section referencing that? At the check where the reader runs the blacklisted modules in lsmod expecting a null return, put a fork in there and suggest if he gets a value after blacklisting and reboot, try the b43-fwcutter/b43-firmware approach.<br /> Or he might check for b44 at the outset and opt for the sbo packages if it's loaded with ssb as a dependency.</div>

Dijetlo