Blacklisting modules doesn't work on custom Slackware ARM 14.0
Hi !
I did what i could, used /etc/modprobe.d/ files and the newer /lib/modprobe.d/, the modules i choose to blacklist are loaded. I had no problem with the 13.37 release. My custom version is not supposed to have been modified on these parts of the system. Seems that the bare 14.0 doesn't have this bug. And don't know where to begin the debug :/. |
Yes, I've discovered this too (though not on arm).
I believe it's the change to kmod that has affected this. The modprobe command now ignores the blacklist unless you specify the -b option, and rc.* files that load a module haven't been changed to run "modprobe -b" rather than "modprobe" I noticed it when I was trying to blacklist the alsa-oss modules which are loaded from rc.alsa. I was going to drop Pat a note about it, but was giving the poor chap time to recover after the release. |
Ok.
Thanks. So for those who need a workaround, edit the same files and put: install module_name /bin/false instead of blacklist module_name After that modprobe will not work, but you can use insmod. |
Changing any occurrences of "modprobe" to"modprobe -b" in the rc files seems to be the most sensible solution to me.
|
Ok, will take a look.
Thanks. |
Quote:
Code:
bash-4.2$ lsmod | grep joydev |
Quote:
Code:
root@ws1:~# lsmod |grep oss |
Also not working here on Slackware 14 x86. This is my "/lib/modprobe.d/blacklist":
Code:
blacklist lp |
Quote:
|
Solved.
The config file name must end with ".conf". There had not been such requirement before. |
All times are GMT -5. The time now is 07:11 PM. |