On 05/04/2017 01:28 PM, David De Graaf wrote:
Is blacklisting broken?
I've created /etc/modprobe.d/wireless.conf with one line:
blacklist r8712u
and yet, after a reboot, the r8712u module is installed.
I don't think it's broken, no. The man page for modprobe.conf indicates
that blacklisting a module will cause modprobe to disregard the aliases
within the module that associate it with the PCI ID of the device it
supports. If you load the module directly, by name, blacklist doesn't
prevent the module from loading.
On my laptop, the ethernet module is built in to the initramfs, but the
wireless module isn't. All the same, you could try "lsmod
/boot/initramfs-<kver>" to see if the module is loaded there.
Otherwise, if "lspci -v" shows the kernel module in use for your
wireless interface as the module you want to use, I wouldn't worry too
much about another module being loaded, even if I can't explain why it is.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
