Description of problem: Using systemd this is seen when booting up (from dmesg) rc.sysinit[96]: WARNING: "include /lib/module-init-tools/modprobe.compat" is deprecated, please use /etc/modprobe.d rc.sysinit[96]: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. rc.sysinit[96]: WARNING: All config files need .conf: /etc/modprobe.d/snd-oss, it will be ignored in a future release. rc.sysinit[96]: WARNING: All config files need .conf: /etc/modprobe.d/blacklist-compat, it will be ignored in a future release. rc.sysinit[96]: WARNING: All config files need .conf: /etc/modprobe.d/blacklist-mga, it will be ignored in a future release. The above states clearly what is expected :)
Assignee: bugsquad => thierry.vignaud
This is has nothing to do with systemd
Fine, but I didn't see it before.
Summary: For systemd module-unit-tools has to move/rename config files => module-unit-tools has to move/rename config files according to dmesg
Files: /etc/modprobe.d/blacklist-compat /etc/modprobe.d/blacklist-mga /etc/modprobe.d/snd-oss renamed so they end with .conf Question is... should we move /lib/module-init-tools/modprobe.compat to /etc/modprobe.d/modprobe.compat.conf ? And I'm not sure what to do with /etc/modprobe.conf... I guess there is some stuff still that expects to find /etc/modprobe.conf, (including the installer), so maybe just silence the warning about that one... or fix the installer, and move the file to /etc/modpbrobe.d/ and wait for bugreports...
CC: (none) => tmb
For info: I renamed the first 3 mentioned, moved /etc/modprobe.conf to inside /etc/modprobe.d and all relative warnings are gone when rebooting. For the /lib......compat file I created a symlink with name module.compat.conf to the /lib....compat file in /etc/modprobe.d but the warning remained. All seems to work well on this i7 970 with a few usb connections. No new errors seen. But obviously I did not use the installer.
I can reproduce it here on a Core i3 machine without systemd. All this should be fixed at the package source: [root@localhost ~]# modprobe e1000e WARNING: "include /lib/module-init-tools/modprobe.compat" is deprecated, please use /etc/modprobe.d WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/lockd.drakx, it will be ignored in a future release. [root@localhost ~]#
CC: (none) => shlomif
Severity: normal => enhancementKeywords: (none) => Junior_job
*** Bug 2988 has been marked as a duplicate of this bug. ***
CC: (none) => pietrotux88
I beg to differ that this is an 'enhancement', for the simple reason that the bug is a severe nuisance itself (though harmless): it spams the console every Cauldron day or more and some logs as well. If this is within the definition of enhancement then the enhancement definition needs serious reconsideration. Anticipant a ta chère cooperation de se fixer à ta meilleure convenance, Thierry, je t'achète une biere (ou deux) à notre prochaine recontre! :)
Severity: enhancement => normal
Bug 3309 is fixed, I guess this one too ?
Seemingly, but not quite: # stat /etc/modprobe.conf File: `/etc/modprobe.conf' Size: 0 Blocks: 0 IO Block: 4096 regular empty file ... # rpm -qf /etc/modprobe.conf module-init-tools-3.16-9.mga2
*** Bug 3878 has been marked as a duplicate of this bug. ***
CC: (none) => palm_pre_stl
Is this bug still valid since we have migrate to kmod ?
Perhaps the warnings are all suppressed or not even called up, but still: # rpm -qf /etc/modprobe.conf module-init-tools-3.16-15.mga2 which I think should not apply anymore.
CC: (none) => marcello.anni
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Summary: module-unit-tools has to move/rename config files according to dmesg => module-init-tools has to move/rename config files according to dmesg
shlomif@telaviv1:~$ rpm -qf /etc/modprobe.conf kmod-7-6.mga2 Is this OK?
yes we use kmod now, so I guess this one is fixed, if not feel free to reopen
Status: NEW => RESOLVEDResolution: (none) => OLD
The warnings are suppressed, but the file is still there, even if via another package. IMHO this is a workaround rather than a fix, but perhaps not important enough to keep the bug.