Red Hat Bugzilla – Bug 495453
modprobe complains about dahdi and dahdi.blacklist
Last modified: 2009-09-11 19:22:45 EDT
Description of problem:
Every time modprobe loads a module, it complains that /etc/modprobe.d/dahdi.blacklist and /etc/modprobe.d/dahdi do not end in .conf. For example, the error is displayed during boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. reboot & watch the messages
WARNING: All config files need .conf: /etc/modprobe.d/dahdi, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/dahdi.blacklist, it will be ignored in a future release.
No error message.
They just need to be renamed dahdi.conf and dahdi.blacklist.conf to make modprobe happy.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Bug still exists in Rawhide
reported at upstream,
let me know if this version fix the problem
(In reply to comment #4)
> let me know if this version fix the problem
dahdi-tools-22.214.171.124-6.fc11 has been submitted as an update for Fedora 11.
dahdi-tools-126.96.36.199-6.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update dahdi-tools'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8769
dahdi-tools-188.8.131.52-6.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.