/etc/modprobe.d folder is empty

hadrons123 · 2012-01-23 03:15:51

My modprobe.d folder is empty.I don't have a modprobe.conf file in it.

Pacman did not seem to have altered any files in this folder,when I upgraded.

[2012-01-20 22:47] Running 'pacman -Syu'
[2012-01-20 22:47] synchronizing package lists
[2012-01-20 22:47] starting full system upgrade
[2012-01-20 22:48] upgraded gnome-shell (3.2.2-2 -> 3.2.2.1-1)
[2012-01-21 09:11] Running 'pacman -Sy'
[2012-01-21 09:11] synchronizing package lists
[2012-01-21 09:12] starting full system upgrade
[2012-01-21 09:13] Running 'pacman -S -u'
[2012-01-21 09:13] starting full system upgrade
[2012-01-21 09:15] removed module-init-tools (3.16-3)
[2012-01-21 09:15] upgraded gnutls (3.0.11-1 -> 3.0.12-1)
[2012-01-21 09:15] installed kmod (4-1)
[2012-01-21 09:15] upgraded udev (175-1 -> 177-3)
[2012-01-21 09:15] warning: /etc/rc.conf installed as /etc/rc.conf.pacnew
[2012-01-21 09:15] upgraded initscripts (2012.01.2-1 -> 2012.01.3-1)
[2012-01-21 09:15] upgraded mkinitcpio (0.8.0-3 -> 0.8.2-1)
[2012-01-21 09:15] upgraded xkeyboard-config (2.4.1-3 -> 2.5-1)

My system reboots and works fine.What did I miss?

Last edited by hadrons123 (2012-01-23 03:18:25)

Trilby · 2012-01-23 03:20:29

pacman wrote:

[2012-01-21 09:15] removed module-init-tools (3.16-3)
...
[2012-01-21 09:15] installed kmod (4-1)

modprobe.conf was part of module-init-tools. Kmod did not come with a similar file.

hadrons123 · 2012-01-23 04:31:18

thanks trilby.Reading docmentation on Kmod...

.:B:. · 2012-01-23 07:31:07

It's a drop-in replacement, so you can just use modprobe's configuration file as if you were still using module-init-tools.

hadrons123 · 2012-01-23 07:53:39

i read some documentation on modprobe.conf now,at http://linux.die.net/man/5/modprobe.conf
I 've a question, why isn't there a modprobe.conf file in /etc/modprobe.d/ folder?

Last edited by hadrons123 (2012-01-23 07:55:22)

.:B:. · 2012-01-23 08:55:48

That's because kmod doesn't come with any, and pacman procedure is to back up the config files before removal of a package (which, for 99% of the people, pacman seems to do in case of module-init-tools - it went like this here).

PReP · 2012-01-23 11:06:55

I had modprobe.conf on one of my arch systems, and none on another.
The one having one, had "blacklist soundcore", which was probably placed there when installing OSS.

I figure, that only systems that have blacklisted modules, in that file (before the xx-blacklist_something.conf files started to be used) has those.

So if there is none, there won't be a modprobe.conf.pacsave, and you probably did not need one either.

This my guess atleast

hadrons123 · 2012-01-23 11:10:59

I have a fedora installation too.It has blacklisted too many items on the same laptop.But arch didnt do any blacklisting and everything works fine on both systems.I wonder why?

Trilby · 2012-01-23 12:42:00

hadrons123 wrote:

But arch didnt do any blacklisting

I've never used fedora, but arch will not ever do any blacklisting - it doesn't do our thinking for us. Some arch users need to blacklist some modules.

If everything is working for you, then it sounds like you are set. You can add .conf files to that directory and they will be used by kmod the same as they would have been by modprobe.

As for the differences, if some modules were blacklisted for you by a fedora install or some other automatic process, perhaps it was to liberal and it listed some that wouldn't bother your system. If you're curious you could try removing some to see if everything still works.

But as they say, if it aint broke ...

Arch Linux

#1 2012-01-23 03:15:51

/etc/modprobe.d folder is empty

#2 2012-01-23 03:20:29

Re: /etc/modprobe.d folder is empty

#3 2012-01-23 04:31:18

Re: /etc/modprobe.d folder is empty

#4 2012-01-23 07:31:07

Re: /etc/modprobe.d folder is empty

#5 2012-01-23 07:53:39

Re: /etc/modprobe.d folder is empty

#6 2012-01-23 08:55:48

Re: /etc/modprobe.d folder is empty

#7 2012-01-23 11:06:55

Re: /etc/modprobe.d folder is empty

#8 2012-01-23 11:10:59

Re: /etc/modprobe.d folder is empty

#9 2012-01-23 12:42:00

Re: /etc/modprobe.d folder is empty

Board footer