blacklist.conf

Archived topics about LMDE 1
Forum rules
User avatar
5oak
Level 1
Level 1
Posts: 31
Joined: Fri Jan 25, 2008 4:39 pm

blacklist.conf

Postby 5oak » Fri Nov 11, 2011 4:23 pm

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/

User avatar
DrHu
Level 17
Level 17
Posts: 7561
Joined: Wed Jun 17, 2009 8:20 pm

Re: blacklist.conf

Postby DrHu » Fri Nov 11, 2011 5:36 pm

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 ?

User avatar
5oak
Level 1
Level 1
Posts: 31
Joined: Fri Jan 25, 2008 4:39 pm

Re: blacklist.conf

Postby 5oak » Sun Nov 13, 2011 12:47 pm

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.


Return to “Archive”

Who is online

Users browsing this forum: No registered users and 12 guests