blacklist.conf

Archived topics about LMDE 1 and LMDE 2
Locked
5oak

blacklist.conf

Post by 5oak »

Hi,

I accidentally overwrote the original. Could someone please hand me an unmodified version? Don't want to mess up my system... (come to think of it, seems like I already did huh? :D)

Best regards,

Stijn

P.S. To those who don't know, it's in /etc/modprobe.d/
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
DrHu

Re: blacklist.conf

Post by DrHu »

http://kernel-handbook.alioth.debian.or ... dules.html
  • Sometimes two different modules claim support for the same device, usually because two slightly different versions of the device exist, requiring different kernel modules to operate. In such situation udev loads both kernel modules, with unpredictable results. To avoid this problem, you can prevent any module (let's say, tulip) from loading by creating an arbitrarily named file, containing a line
    blacklist tulip
http://linux.die.net/man/5/modprobe.d

Just use an empty file

Code: Select all

touch /etc/modprobe.d/blacklist.conf
--or empty out the contents of the one you have and begin again with any blacklist modules you want to use ?
5oak

Re: blacklist.conf

Post by 5oak »

I don't understand. I thought the purpose of this file was to blacklist hardware that's not compatible or whatever you want to call it. Doesn't it matter if it's completely empty?

To avoid any (further) misunderstanding: I have no idea which hardware should be blacklisted.
Locked

Return to “LMDE Archive”