Package: acpid
Version: 1.0.6-9
Severity: minor
In /var/log/boot:
Loading ACPI modules...Unable to load module: asus_acpi
Unable to load module: bay
Unable to load module: toshiba_acpi
Well that makes sense, as my computer is not those brands, or has a
bay, I guess. But wait, why is it attempting to load them in the first
place?
# tail -n 1 /etc/default/acpid
MODULES="all"
Oh, I see, I must adjust this file for each of my machines. Ugh... why
can't it auto detect and not attempt the wrong actions... OK, I
suppose that's what it's doing in a way, but it sure looks bad upon
boot. But then you might say to turn VERBOSE off, which brings us to
/etc/init.d/acpid:
(By the way how do I find out what kprint does?
$ cd /usr/share/doc/linux-doc-2.6.25/" -*-
$ find . -type f -print0 | xargs -0 -e zgrep -nH -e kprint
$)
(Also instead of
if [ -d "$LOC" ]; then
if [ -d "$LOC2" ]; then
just do for dirs in /lib/modules/$(uname -r)/kernel/*/acpi ...
or use .../{d1,d2}/acpi (oops, bashism) or even just
find /lib/modules/$(uname -r)/kernel/*/acpi/*.ko ...)
Anyway, mainly you need to first let better messages get through:
The original message looks like
FATAL: Error inserting bay
(/lib/modules/2.6.25-2-686/kernel/drivers/acpi/bay.ko): No such device
so maybe print that instead of just "failed..."
Then some time later figure out a way to test before attempting to insert...
P.S., no asus_acpi even on Asus (Duron desktop.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
