[gentoo-user] Deprecated config file /etc/modprobe.conf

[gentoo-user] Deprecated config file /etc/modprobe.conf

[Jacob Todd]

I'm getting the following warnings when I boot/come back from
hibernation:

WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will
be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/alsa, it will be
ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/pnp-aliases, it
will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it
will be ignored in a future release.

I just noticed these yesterday because I had to reboot my machine. When
did this change in config files happen? Should I just rename the config
file in /etc/modprobe.d/ so that they all have .conf at the end, or is
there another process I need to do when upgrading? I'm using ~x86.

-- 
Jake Todd

Re: [gentoo-user] Deprecated config file /etc/modprobe.conf

[Alan McKinnon]

On Wednesday 27 May 2009 21:42:23 Jacob Todd wrote:
> I'm getting the following warnings when I boot/come back from
> hibernation:
>
> WARNING: Deprecated config file /etc/modprobe.conf, all config files
> belong into /etc/modprobe.d/.
> WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will
> be ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/alsa, it will be
> ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/pnp-aliases, it
> will be ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it
> will be ignored in a future release.
>
> I just noticed these yesterday because I had to reboot my machine. When
> did this change in config files happen? 

> Should I just rename the config
> file in /etc/modprobe.d/ so that they all have .conf at the end, or is
> there another process I need to do when upgrading? 

The former.

When you've done this, run update-modules manually. You might find you have 
stuff in /etc/modules.d/ that also needs to be similarly renamed.
 
> I'm using ~x86.

-- 
alan dot mckinnon at gmail dot com