after every reboot I have to execute modprobe for the broadcom kernel modules (b43) by hand in order to have wlan.
what should I do / where to write the commands to have that done automatically after reboot?
(why are the modules not loaded automatically?)
Make sure b43 is not blacklisted in /etc/modprobe.d/50-blacklist.conf ( egrep -in b43 /etc/modprobe.d/50-blacklist.conf )
If you’ve been toying around with different bcm drivers (like those from Packman) it may have been added there.
thanks - that was it.
although the module was not blacklisted in the file you mentioned.
broadcom modules have a separate blacklist file in the same directory
On 2015-01-27 21:16, suse paul wrote:
>
> thanks - that was it.
> although the module was not blacklisted in the file you mentioned.
> broadcom modules have a separate blacklist file in the same directory
Interesting.
Just commenting, because it does not apply to your case: at least one
developer I know says that if a module doesn’t load automatically, and
you have to modprobe it, it is a bug that should be reported in Bugzilla
against the kernel.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Not when it’s blacklisted.
On 2015-01-27 22:46, deano ferrari wrote:
>
> robin_listas;2691626 Wrote:
> Not when it’s blacklisted.
Well, I said “it does not apply to your case” (his case, of course, not
yours) 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Hi,
Might not be related but a recursive search would be
grep -Ein b43 /etc/modprobe.d/*.conf
An aside note egrep and fgrep are deprecated, just saying
Well, the developer comment goes without saying. It’s the job of the kernel to load the correct drivers automatically and if it doesn’t, of course there is a problem 