Kmod: how to configure?

.:B:. · 2012-01-06 15:19:25

Well hi there fellas.

I had module-init-tools replaced by kmod last night but it does not seem to work with the old modprobe.conf files. Now I see pcspkr is loaded. So far, I haven't done anything to upset my computer, but I'm sure it will get vocal again once I start pushing the wrong buttons. So how do I blacklist (or pass options to) modules with kmod?

Thank you

the.ridikulus.rat · 2012-01-06 15:24:28

I think the /etc/modprobe.d/*.conf problem was corrected by testing/kmod 3-4 (https://bugs.archlinux.org/task/27846).

Last edited by the.ridikulus.rat (2012-01-06 15:44:06)

.:B:. · 2012-01-06 15:40:38

Funky, and quick. Thanks .

fredbezies · 2012-01-08 10:19:25

But kmod breaks 75% of my laptop boot. Downgrading to modules-init-tools and blocking upgrade => 100% successful boot on my laptop.

Army · 2012-01-08 12:02:58

kmod works better here than modules-init-tools did. Everything still works, but in addition I don't get this error message about a module (padlock-sha) not being able to be loaded. Very nice indeed!

karol · 2012-01-13 02:14:42

/etc/modprobe.d/modprobe.conf is not provided by kmod so you need to edit your /etc/mkinitcpio.conf and comment out the

FILES="/etc/modprobe.d/modprobe.conf"

line or change it to

FILES="/lib/modprobe.d/modprobe.conf"

I guess (and move modprobe.conf there).

Last edited by karol (2012-01-13 02:15:09)

Jristz · 2012-01-13 02:20:47

karol wrote:

/etc/modprobe.d/modprobe.conf is not provided by kmod so you need to edit your /etc/mkinitcpio.conf and comment out the
FILES="/etc/modprobe.d/modprobe.conf"
line or change it to
FILES="/lib/modprobe.d/modprobe.conf"
I guess (and move modprobe.conf there).

and making a simlink to there can work, for prevent redundant files
work?

karol · 2012-01-13 02:25:10

I don't get it, you either have
* /lib/modprobe.d/modprobe.conf - one file
* /etc/modprobe.d/modprobe.conf + a symlink - two files.

I think that just moving the file is simpler. I'm not sure what you mean by 'redundant' here.

Jristz · 2012-01-13 02:31:16

karol wrote:

I don't get it, you either have
* /lib/modprobe.d/modprobe.conf - one file
* /etc/modprobe.d/modprobe.conf + a symlink - two files.
I think that just moving the file is simpler. I'm not sure what you mean by 'redundant' here.

sorry I undertsçand incorrecltly
I think:
/lib/modprobe.d/ <- origial
/etc/modprobe/ <- not exist
and aI thiks tah you say : copy (literaly (cp) from one to other

I thik /etc/modprobe.d/ <- original for compatibility for kernel26-lts nd oters
/lib/modprobe.d/ <- symlñinked from /etc/modprobe.d/

karol · 2012-01-13 02:36:03

After the update /etc/modprobe.d/modprobe.conf has been automatically renamed to /etc/modprobe.d/modprobe.conf.pacsave.
I'm not sure about this kernel26-lts compatibility stuff, this is the mkinitcpio config file so I'm not sure what does it have to do with the kernel.
kernel26-lts 2.6.32.53-1 is in testing so it should work with kmod, right?

falconindy · 2012-01-13 02:39:32

kmod does not ship /etc/modprobe.d/modprobe.conf. It's silly to ship an empty config file. This is the only reason modprobe.conf was pacsaved.

kmod follows the exact same rules for config as module-init-tools:

- /lib/modprobe.d and /lib/depmod.d are intended for usage by distros to ship configuration files that are read only. That is, users should not touch them.
- /etc/modprobe.d and /lib/depmod.d are intended for usage by administrators to tune their systems accordingly. If you have specific softdep, aliasing, install, ordering, override, or blacklisting rules that you need, put them in a .conf file in the appropriate dir in /etc.

Symlinking between these directories is foolish and accomplishes nothing. The original post stemmed from a bug in the intial packaging of kmod and is no longer valid.

karol · 2012-01-13 02:47:19

Not sure who do you mean by 'administrators'. Where do average Joe User can put his configs? Is he allowed only in /etc/modprobe.d ?
Or maybe you have a typo there.

Either way, I'm using kmod 3-6 and all is fi-

bzzzzzzt

[Broadcast terminated]

Last edited by karol (2012-01-13 03:05:24)

falconindy · 2012-01-13 03:06:57

The "average Joe" still needs root (administrator) privileges to write to _any_ of these directories. Once assuming said privileges, they can direct their random keypress to the /etc flavored dumping grounds.

karol · 2012-01-13 03:25:31

I somehow missed http://mailman.archlinux.org/pipermail/ … 22330.html that explains it all. The previous message said "The only place that works here is /lib/modprobe.d/foo.conf" and that's why I wanted to keep my stuff there.

cfr · 2012-01-21 03:38:50

Glad I found this. It seems a bit odd that pacman moved /etc/modprobe.d/modprobe.conf to modprobe.conf.pacsave. I expect it to leave the custom version in place and install the new version as a .pacsave. Obviously there is no new version in this case. So if kmod works with the file in the same way as module-init-tools, why move the customised config file to .pacsave? If anything, there seems a stronger case for the standard behaviour here than usual since there is nothing new in the new default which needs integration.

Maybe I just don't understand the policy properly, though? I'm not really used to how pacman works yet...

All I've now done is moved modprobe.conf.pacsave back to modprobe.conf. Can that really be right? Surely I'm meant to do more than just undo what pacman did?

Am I right that the only significant change to rc.conf is the deletion of the UDEV_TIMEOUT line? I didn't have a default copy of the old rc.conf to compare because mine was edited during installation. I couldn't see anything else that looked different other than comments and customisations.

falconindy · 2012-01-21 04:11:34

crossposting myself: https://bbs.archlinux.org/viewtopic.php … 3#p1044733

karol · 2012-01-21 11:26:40

cfr wrote:

Glad I found this. It seems a bit odd that pacman moved /etc/modprobe.d/modprobe.conf to modprobe.conf.pacsave. I expect it to leave the custom version in place and install the new version as a .pacsave.

No, please read pacman's man page, the 'HANDLING CONFIG FILES' section.
If you remove a package, the modified config gets a .pacsave and that's what happened.

cfr wrote:

I didn't have a default copy of the old rc.conf to compare because mine was edited during installation.

Check the stock rc.conf here: http://projects.archlinux.org/initscrip … ee/rc.conf if you like.

Arch Linux

#1 2012-01-06 15:19:25

Kmod: how to configure?

#2 2012-01-06 15:24:28

Re: Kmod: how to configure?

#3 2012-01-06 15:40:38

Re: Kmod: how to configure?

#4 2012-01-08 10:19:25

Re: Kmod: how to configure?

#5 2012-01-08 12:02:58

Re: Kmod: how to configure?

#6 2012-01-13 02:14:42

Re: Kmod: how to configure?

#7 2012-01-13 02:20:47

Re: Kmod: how to configure?

#8 2012-01-13 02:25:10

Re: Kmod: how to configure?

#9 2012-01-13 02:31:16

Re: Kmod: how to configure?

#10 2012-01-13 02:36:03

Re: Kmod: how to configure?

#11 2012-01-13 02:39:32

Re: Kmod: how to configure?

#12 2012-01-13 02:47:19

Re: Kmod: how to configure?

#13 2012-01-13 03:06:57

Re: Kmod: how to configure?

#14 2012-01-13 03:25:31

Re: Kmod: how to configure?

#15 2012-01-21 03:38:50

Re: Kmod: how to configure?

#16 2012-01-21 04:11:34

Re: Kmod: how to configure?

#17 2012-01-21 11:26:40

Re: Kmod: how to configure?

Board footer