SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
APM broke on my Latitude D400, Slack 10. It was working and happened about the time I installed a new kernel - 2.4.28 from 2.4.26. Now, I have to force a power-off with the button.
modprobe apm:
Code:
/lib/modules/2.4.28/kernel/arch/i386/kernel/apm.o.gz: init_module: No such device
/lib/modules/2.4.28/kernel/arch/i386/kernel/apm.o.gz: 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
/lib/modules/2.4.28/kernel/arch/i386/kernel/apm.o.gz: insmod /lib/modules/2.4.28/kernel/arch/i386/kernel/apm.o.gz failed
/lib/modules/2.4.28/kernel/arch/i386/kernel/apm.o.gz: insmod apm failed
I'm running the same kernel on a C600 with no problems and, as I mentioned, APM worked on this one until yesterday. I'd like to avoid a 2.6 or ACPI change if possible.
Looks like you're trying to load APM as a module, but it was not compiled as a module with the new Kernel. If APM is showing up in your dmesg then it is possible that it was compiled into the kernel directly. Did youy compile the kernel yourself, or did you install a pre-compiled 2.4.28? If you compiled on your own, then I would look back through your .config and make sure you compiled APM correctly. Your last setup had APM as a module, so I would probably recompile 2.4.28 with that option.
I used the vanilla Slack 2.4.28 kernel, the same one that's on the working laptop. Here's the .config for it:
Code:
bash-3.00# grep APM /usr/src/linux-2.4.28/.config
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
Hmmm.....interesting. It sounds like slack is complaining that it can't load the APM module, yet you are getting an error message that APM can't locate BIOS. I'm stumped. I googled for 'apm: BIOS not found' and some hits with that same message came up, they might be helpful if you want to glance through them. My only thought is that someone submitted a patch for the APM module somewhere between the 2.4.26 and 2.4.28 kernels that broke compatibility with your specific BIOS. Any chance you flashed the BIOS before your kernel upgrade? Have you considered switching to APIC?
I'm using the same BIOS. I also searched quite a bit before posting and found a lot of suggestions (many of them were on LQ, by the way), but no solutions.
Most of the fixes relate to loading the APM module or uncommenting the APM line in rc.M. Neither of those applies in this case.
Thanks for your thoughts on it. If you have any others, I'm happy to hear them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.