X and Fluxbox :: APM Error message when X starts

Hello everyone,

I've just brought an old Toshiba Libretto 100ct back to life with Damn Small Linux... I've done a hard drive install, got everything set up just about perfect. The only thing that is bothering me is whenever I start X, I get the following error messages:

Code Sample

apm: overridden by ACPI.
insmod: /lib/modules/2.4.26/kernel/arch/i386/kernel/apm.o: init_module: No such device
insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.26/kernel/arch/i386/kernel/apm.o: insmod char-major-10-134 failed

Everything seems to work fine; ACPI works and correctly reports the battery state, CPU speed, etc., so I don't think the errors are causing me any problems. I would just like to find out where the apm / insmod stuff is coming from, so I can make it stop. (syslog is empty and dmesg doesn't have any additional info, so the hints in the error message weren't much help.)

I've narrowed it down somewhat, I know that the errors happen when startx issues the xinit command, and from there I've narrowed it right down to /usr/bin/X11/Xfbdev - if I don't use startx, and just run Xfbdev directly, I get those error messages. I can't figure out though if Xfbdev is hardcoded to insmod apm.o or if it's got a configuration script somewhere with that stuff in it.

Any suggestions or pointers would be most appreciated!

Thanks!

Edited to add: I have tried the noapm boot option, and I have also tried Xvesa instead of Xfbdev. The noapm option had no effect, and I get the same exact error messages with Xvesa, so I think it's an X server issue that's not unique to Xfbdev.

I could guess you could safely ignore those messages - since ACPI overrides apm. Though I suppose apm dependent operations should not continue, it can't load anyways. If you really want to get rid of it, I suppose you could remove the apm.o manually (and optionally update the module lists via depmod).

You could also try "apm=off" in the boot combinations..

I'm guessing this is for a traditional hd-install?

I did some more digging and noticed that the errors that Xfbdev was producing were exactly the same as I got if I did a modprobe apm so I looked into that, and found a solution.

First I added the following lines to /etc/modutils/aliases
alias char-major-10-134 off
alias apm off
alias apm-bios off

Then I did a sudo update-modules

Since then, no more apm error messages, and everything else is working properly. I'm sure you're right, the error messages didn't cause or indicate any real problem. I just wanted to get rid of them before I showed-off DSL to anyone, so I wouldn't have to answer questions about error messages.

-Stephanie

original here.