You are not logged in.

#1 2012-08-23 11:56:49

zenlord
Member
From: Belgium
Registered: 2006-05-24
Posts: 1,221
Website

[SOLVED] systemd and blacklisting modules

Hi,

I recently found out about the 'systemctl status foo.service'-cmd and I was finally able to see why the systemd-modules-load-service was failing on my laptop.

It complains it cannot find service-files for 'blacklist nouveau' and other modules I have blacklisted. The wiki mentions blacklisting is done the same for systemd as for sysV-init, i.e. through a simple 'blacklist <modulename>' inside a .conf-file residing in either:
/etc/modprobe.d/ or
/etc/modules-load.d/

What am I doing wrong?

Last edited by zenlord (2012-08-24 19:38:38)

Offline

#2 2012-08-23 13:27:22

tomegun
Developer
From: France
Registered: 2010-05-28
Posts: 661

Re: [SOLVED] systemd and blacklisting modules

The .conf file must be in /etc/modprobe.d and not in /etc/modules-load.d.

If that is not the problem, then please past the exact error message, the contents of the relevant .conf file, and its full path.

Offline

#3 2012-08-23 13:32:17

Pres
Member
Registered: 2011-09-12
Posts: 423

Re: [SOLVED] systemd and blacklisting modules

See `man modprobe.d` and `man modules-load.d` for more information on what each of these directories are for.

Offline

#4 2012-08-24 19:37:57

zenlord
Member
From: Belgium
Registered: 2006-05-24
Posts: 1,221
Website

Re: [SOLVED] systemd and blacklisting modules

tomegun wrote:

The .conf file must be in /etc/modprobe.d and not in /etc/modules-load.d.

OK, that's the one. I was mistaken to think that both directories had the same functionality.

THX!

Marking as solved.

Last edited by zenlord (2012-08-24 19:38:11)

Offline

Board footer

Powered by FluxBB