Description of problem:
the module asus_acpi is always loaded even I don't have a computer build by
Asus. Machine is a IBM Thinkpad R52.
Version-Release number of selected component (if applicable):
Fedora 7 Test 2, Kernel 2.6.20-1.2949
Steps to Reproduce:
1. install Fedora on a non-Asus-machine
asus_acpi is (unecessary?) loaded
asus_acpi should not be needed by non Asus-machines
I have this bug since Fedora Core 6 and on two different computers (IBM Thinkpad
and a custom build Desktop PC). Both machines doesn't contain ANY parts made or
build by Asus. So why this module is loading? It is quite annoying and I hope
there is a good reason for this.
Bulk message: Fedora 7 test bugs should be filed against "devel", not against
test1/2/3. This isn't obvious, I know. Moving this report so it isn't lost.
Thats actually more of a kernel question/bug, so reassigning it to proper component.
Read ya, Phil
asus_acpi is always loaded because of this piece of /etc/rc.d/rc.sysinit:
# Initialize ACPI bits
if [ -d /proc/acpi ]; then
for module in /lib/modules/$unamer/kernel/drivers/acpi/* ; do
modprobe $module >/dev/null 2>&1
rc.sysinit is from the package "filesystem", owned by pknirsch
Is there a way to exclude a single kernel module like asus_acpi? Blacklisting
the module via modprobe.conf does not work.
Actually, rc.sysinit is owned by initscripts, moving there.
Read ya, Phil
This will be removed when the modules support proper dmi-based aliases - this is
going upstream soon.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Having freshly installed Fedora 8 on a secondary computer it seems that this
bug is fixed now. No module asus_acpi is shown via lsmod.
That's like it should be.
Thanks for your update
Okay to close this bug?
Sure, you can close this one. Didn't know if I can do this on my own.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here: