Arch Linux

Llama

Member

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,199

The art of blacklisting

Hi, everybody,

I gather that "Load UDev Events" stage of the boot process is responsible for dynamically detecting hardware, loading drivers and creating device interfaces. Blacklisting has been invented to block certain parts of this process. Is it correct (I am not sure)? How can I see what's been detected, loaded and created? There doesn't seem to be a special log for it. To blacklist precisely the right thing you have to see the whole thing first, haven't you?

dyscoria

Member

Registered: 2008-01-10

Posts: 1,007

Re: The art of blacklisting

To view the modules that are currently loaded:

lsmod

To view info on the module:

modinfo $module_name

Last edited by dyscoria (2008-06-05 08:51:48)

---

flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)

chimeric

Member

From: Munich, Germany

Registered: 2007-10-07

Posts: 254

Website

Re: The art of blacklisting

Blacklisting can be used to prevent udev from loading certain kernel modules (drivers). You can use lsmod to get a list of currently loaded modules. Note that some modules are loaded dynamically when you for example attach a device to your computer while it's running (bluetooth and the like).

Edit: Not fast enough

Last edited by chimeric (2008-06-05 08:55:59)

_Marco_

Member

Registered: 2008-04-21

Posts: 242

Re: The art of blacklisting

well... if you want to know what modules are loaded by udev you can:
hwdetect --modules (so you see every loaded module)
comparing with the rc.conf MODULES line you have the autodetected one

I tried to get the output of "hwdetect --modules" put it in /etc/rc.conf 's MODULE=() and setting the MODULE_AUTOLOAD="no" but it doesn't help the boot time (simply a note, I know it's not what you asked )

AFAIK modules blacklisting is deprecated (see if you have a /etc/rc.conf.pacnew to see the dev's comment)
bye

edit: not fast enough too   (:P)

Last edited by _Marco_ (2008-06-05 08:57:20)

Llama

Member

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,199

Re: The art of blacklisting

Thanks!

AFAIK modules blacklisting is deprecated (see if you have a /etc/rc.conf.pacnew to see the dev's comment)
bye

What's the replacement?

dyscoria

Member

Registered: 2008-01-10

Posts: 1,007

Re: The art of blacklisting

You just put a '!' in front of the module you want blacklisted in the MODULES array.

Last edited by dyscoria (2008-06-05 09:11:50)

---

flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)

Llama

Member

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,199

Re: The art of blacklisting

Another question: why while MOD_AUTOLOAD="yes" the MODULES list isn't kept empty?

dyscoria

Member

Registered: 2008-01-10

Posts: 1,007

Re: The art of blacklisting

See: http://wiki.archlinux.org/index.php/Rc.conf#Hardware

---

flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)

_Marco_

Member

Registered: 2008-04-21

Posts: 242

Re: The art of blacklisting

dyscoria I don't understand (it's not your problem if I am stupid but..)
(question are for everyone, not only for dyscoria )
what exactly change using udev/modules=()/modprobe?
ah and there is another thing..
"Prepending a module with a bang ('!') will not load the module during bootup (this is not the same as MOD_BLACKLIST!)"
so why MOD_BLACKLIST is deprecated if it still be useful?

dyscoria

Member

Registered: 2008-01-10

Posts: 1,007

Re: The art of blacklisting

"Prepending a module with a bang ('!') will not load the module during bootup (this is not the same as MOD_BLACKLIST!)"
so why MOD_BLACKLIST is deprecated if it still be useful?

Hmm a discrepancy here it seems. Udev wiki page says different: http://wiki.archlinux.org/index.php/Ude … ng_Modules

Last edited by dyscoria (2008-06-05 09:51:23)

---

flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)

_Marco_

Member

Registered: 2008-04-21

Posts: 242

Re: The art of blacklisting

ah.. it seems to me more "correct" the second one (the first article you linked is out to date just seen this)
for the first question what I don't understand is the
"bind them to a hardware device as in the modprobe.conf"
(I have modprobe.conf empty so I can't figure out the point...)
Thanks for the patience ^^

dyscoria

Member

Registered: 2008-01-10

Posts: 1,007

Re: The art of blacklisting

I think its just talking about putting module specific options for your modules in modprobe.conf (such as setting up audio devices for OSS).

---

flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)

_Marco_

Member

Registered: 2008-04-21

Posts: 242

Re: The art of blacklisting

aah ok, I thought it was regard some "very obscure hardcore geeky thing"
thanks for the hint