Bug 2784

Summary: module-init-tools has to move/rename config files according to dmesg
Product: Mageia Reporter: Dick Gevers <dvgevers>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marcello.anni, palm_pre_stl, pietrotux88, shlomif, tmb
Version: CauldronKeywords: Junior_job, NEEDINFO
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: module-init-tools-3.16-1.mga2 CVE:
Status comment:

Description Dick Gevers 2011-09-19 20:10:17 CEST 
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 :)
Manuel Hiebel 2011-09-20 14:08:35 CEST

Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2011-09-20 15:15:22 CEST 
This is has nothing to do with systemd
Comment 2 Dick Gevers 2011-09-20 18:57:01 CEST 
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

Comment 3 Thomas Backlund 2011-09-21 15:09:02 CEST 
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

Comment 4 Dick Gevers 2011-09-21 20:48:46 CEST 
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.
Comment 5 Shlomi Fish 2011-10-06 18:34:38 CEST 
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

Thierry Vignaud 2011-10-06 18:39:16 CEST

Severity: normal => enhancement
Keywords: (none) => Junior_job

Comment 6 Manuel Hiebel 2011-10-08 18:49:04 CEST 
*** Bug 2988 has been marked as a duplicate of this bug. ***

CC: (none) => pietrotux88

Comment 7 Dick Gevers 2011-11-11 23:14:27 CET 
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

Comment 8 Manuel Hiebel 2011-11-21 19:54:27 CET 
Bug 3309 is fixed, I guess this one too ?
Comment 9 Dick Gevers 2011-11-23 21:33:24 CET 
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
Comment 10 Manuel Hiebel 2011-12-24 16:00:25 CET 
*** Bug 3878 has been marked as a duplicate of this bug. ***

CC: (none) => palm_pre_stl

Comment 11 Manuel Hiebel 2012-02-06 14:18:21 CET 
Is this bug still valid since we have migrate to kmod ?
Comment 12 Dick Gevers 2012-02-06 19:43:06 CET 
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.
Marcello Anni 2012-02-16 22:08:57 CET

CC: (none) => marcello.anni

Comment 13 Marja Van Waes 2012-05-26 13:05:57 CEST 
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

Shlomi Fish 2012-05-27 08:17:19 CEST

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

Comment 14 Shlomi Fish 2012-05-27 08:18:23 CEST 
shlomif@telaviv1:~$ rpm -qf /etc/modprobe.conf
kmod-7-6.mga2

Is this OK?
Comment 15 Manuel Hiebel 2012-05-27 14:07:27 CEST 
yes we use kmod now, so I guess this one is fixed, if not feel free to reopen

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 16 Dick Gevers 2012-05-28 11:28:22 CEST 
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.