Bug 109940 - ACPI modules loaded using insmod instead of modprobe
ACPI modules loaded using insmod instead of modprobe
Status: CLOSED DUPLICATE of bug 107199
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-11-13 00:43 EST by Bojan Smojver
Modified: 2014-03-16 22:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:59:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bojan Smojver 2003-11-13 00:43:20 EST
/etc/rc.d/rc.sysinit script, line 175 in FC1, goes like this:

insmod $module

The module here is a full path to the ACPI module in question. If
hardware doesn't support certain module (e.g. toshiba_acpi) this
causes ugly error messages being spewed out to the console. One can
turn such modules off in /etc/modules.conf, but error messages
persist. This can be solved by changing the above line to:

modprobe `basename $module .o`
Comment 1 Sergey V. Udaltsov 2003-11-13 04:49:33 EST
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107199 -
virtually same bug
Comment 2 Bastien Nocera 2003-12-19 20:40:36 EST

*** This bug has been marked as a duplicate of 107199 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:59:58 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.