How to prevent a module from being loaded

Question

So I have to use a command every time I boot my laptop in order to my wireless to work.

the command is:

sudo modprobe -r acer-wmi

I found that this is a common type of question but I didn't find a pattern in the answers.

possible duplicate of How to blacklist kernel modules?
– Braiam
Nov 8, 2014 at 0:55 — Braiam, Nov 8, 2014 at 0:55

chili555 · Accepted Answer · 2014-11-07 21:39:49Z

4

I suggest you blacklist the module so it never loads at all:

sudo -i
echo "blacklist acer-wmi"  >>  /etc/modprobe.d/blacklist.conf
exit

Reboot and test.

answered Nov 7, 2014 at 21:39

chili555

60.2k8 gold badges95 silver badges129 bronze badges

Add a comment |

David Foerster · Accepted Answer · 2017-08-16 15:41:26Z

2

You have to add a configuration file in /etc/modprobe.d/

Blacklisting modules

In your case since you don't want to load acer-wmi module automatically, you have to blacklist it.

First try this command:

sudo sh -c 'echo blacklist acer-wmi >> /etc/modprobe.d/blacklist.conf'

In the case where the module is still being load, it means that there is another module that depends on acer-wmi. So a workaround is to use:

sudo sh -c 'echo install acer-wmi /bin/false >> /etc/modprobe.d/blacklist.conf'

Edit: Rectification according to chili555's answer.

David Foerster

36.3k56 gold badges94 silver badges147 bronze badges

answered Nov 7, 2014 at 21:42

LeRieur

665 bronze badges

so the -r is to remove the module?
– Fernando Andrade
Nov 7, 2014 at 21:50
1

Yes. From man modprobe command: This option (-r or --remove) causes modprobe to remove rather than insert a module. If the modules it depends on are also unused, modprobe will try to remove them too.
– LeRieur
Nov 7, 2014 at 21:54
1

the echo didn't work but since you explained what it was supposed to do, I manually added the 'blacklist acer-wmi' to the modprobe blacklist file thanks I will also mark your answer as the correct, even if chili555 was right because you explained and you placed links to documentation. kudos for both :)
– Fernando Andrade
Nov 7, 2014 at 22:19
1

@LeRieur The correct file is not /etc/modprobe.d/blacklist, it is /etc/modprobe.d/blacklist.conf.
– chili555
Nov 7, 2014 at 22:57

Add a comment |