On Wed, 2009-07-01 at 19:05 -0500, Aaron Griffin wrote:

On Wed, Jul 1, 2009 at 6:43 PM, Baho Utot wrote:

...

I am getting a message on boot that I need to change the modules line in rc.conf to the "new way" which is to put the conf file into modprobe.d.

Is there any info on this?

I have some modules I want to blacklist and some to load.

Is the format the same as modprobe.conf? ( I presume )

I take it I can just add a file like this

net-pf-10.conf that contains

blacklist net-pf-10

I think you're mistaken. Our modprobe doesn't have any message of the sort, relating to Arch. The error you are seeing is due to a change in the way modprobe parses config files. It used to read /etc/modprobe.conf and/or /etc/modprobe.d/* - now it only reads /etc/modprobe.d/*.conf

The message is modprobe telling you something is wrong with the config files. Most likely you just have a .pacsav file in /etc/modprobe.d/

Yes I do have a .pacsav file in /etc/modprobe.conf Any way I tried adding the filename.conf to modules I wanted blacklisted or installed and it worked as well.

2009/7/2 Thomas Bächler :

Aaron Griffin schrieb:

...

I think you're mistaken. Our modprobe doesn't have any message of the sort, relating to Arch. The error you are seeing is due to a change in the way modprobe parses config files. It used to read /etc/modprobe.conf and/or /etc/modprobe.d/* - now it only reads /etc/modprobe.d/*.conf

The message is modprobe telling you something is wrong with the config files. Most likely you just have a .pacsav file in /etc/modprobe.d/

This is annoying, I thought it would simply ignore those files. Now it seems that it reads them, but prints that warning. Do you think we should patch it to at least ignore .pacsave files until they remove this warning and backward-compatibility?

I've noticed an issue regarding mkinitcpio and the new modprobe changes that requires a symlink from /etc/modprobe.conf to /etc/modprobe.d/modprobe.conf in order for options for any modules you load in the initramfs to be applied, just incase this hasn't been reported yet. Damien

2009/7/2 Thomas Bächler :

Damien Churchill schrieb:

...

I've noticed an issue regarding mkinitcpio and the new modprobe changes that requires a symlink from /etc/modprobe.conf to /etc/modprobe.d/modprobe.conf in order for options for any modules you load in the initramfs to be applied, just incase this hasn't been reported yet.

/etc/modprobe.conf is not used in the real system or initramfs anymore. Your mkinitcpio configuration is simply wrong.

Touché, I blindly overlooked the FILES var. Apologies.