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
what shuld i now do? go where and uncomment what? am i right?

looks like you have APM as module in your kernel. where is your ACPI output ? as sl4ckw4re asked before, try running the command again using ACPI instead of APM, I still belive you'll need ACPI, so run this and post back

marto@marto:~$ grep ACPI /usr/src/linux/.config
# ACPI Support
# CONFIG_ACPI is not set
marto@marto:~$

I, for one, would suggest you compile your kernel and add ACPI as module.

you can use this thread http://www.linuxquestions.org/questi...threadid=49035 if you don't have experience and don't know how to compile it. follow this tutorial, check ACPI as module and make sure you have the button module enabled too.

oh, I do not for now dare compile my kernel. I believe there is some simpler way of achieving shutdown. Since people using the same kernel can do that with apm, why can't I do that too?

however, if it turns out that there is no other way to enable power off on my PC, I will have to compile it. i have the slackbook and i have read it thorougly. I hope a scrutiny of the section about compiling kernels will be helpful. stil, I hope there will be some simpler suggestions. if there be no other alternative, i will compile it

Can you think of any other solution to my problem, other than compiling the kernel? Is compiling the kernel the only alternative?

I cannot think of anything else, and I know that for me ACPI worked (and really, from what I know, for desktop computers you need ACPI - at least that's how it goes on 2.6 kernels). You can just sit back and wait for more experienced users to reply and see their opinion, I might be wrong and I really don't want to 'help you mess things up' . So it's best to wait until someone else says something too.

maybe he should try installing the "testing 2.6.13 kernel" and that may fix up his issue?

or maybe he needs to reinstall if that don't work?

I would be very glad if there is some solution different from compiling the kernel. There are people with the same kernel who can shutdown their desktop PCs. Why can't I do that too?

tramni i use 2.4.31 kernel on one computer, and can use the apm no problem. in fact every computer I ever put slackware on, I always used the 2.4.31 kernel and using apm never failed for me ever. I truly believe that your modules did not load in correctly for some reason.

I really think the best way to do this is to play it safe and just reinstall for the fact that you may get the apm working, but who knows, maybe some other issue will pop up along the way.

On my slowest computer a p66 it only takes slakcware 40 minutes to reinstall off a cd, and 20 if I use a network install. It may prove better for you in the long run. I don't know that I'd want to have module issues on my pc to be honest.

Sorry it's not a quick fix, but it's a fix none the less.

Do you think it is a good idea to try the "bareacpi.i" kernel? It is the same as bare.i, but has acpi support, they say. Ok, I will reinstall the system, but what if it again does not wish to load the apm module? maybe i should try it with the acpi? have you got an idea what to do so that my PC shut down using the acpi? where and what should I have to uncomment?

HERE IS THE OUTPUT OF THE KERNEL MESSAGES AT START UP:


Jul 25 17:14:03 marto cardmgr[83]: no pcmcia driver in /proc/devices
Jul 25 17:14:04 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:04 marto kernel: hw_random: misc device register failed
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:04 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:05 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:05 marto kernel: hw_random: misc device register failed
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:05 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:06 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:06 marto kernel: hw_random: misc device register failed
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:06 marto kernel: usb.c: USB device 2 (vend/prod 0x46d/0x8f0) is not claimed by any active driver.
Jul 25 17:14:06 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:06 marto kernel: hw_random: misc device register failed
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:06 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:07 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:07 marto kernel: hw_random: misc device register failed
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:07 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:07 marto kernel: hw_random: misc device register failed
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:07 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:08 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:08 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:08 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:08 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:08 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:08 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:08 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:09 marto kernel: hw_random: misc device register failed
Jul 25 17:14:09 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:09 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:09 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:13 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:13 marto kernel: hw_random: misc device register failed
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:13 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:13 marto kernel: hw_random: misc device register failed
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:13 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:14 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:14 marto kernel: hw_random: misc device register failed
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:14 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:14 marto kernel: hw_random: misc device register failed
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:14 marto kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.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
Jul 25 17:14:14 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
Jul 25 17:14:15 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Jul 25 17:14:15 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.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
Jul 25 17:14:15 marto insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Jul 25 17:14:15 marto kernel: hw_random: misc device register failed
Jul 25 17:14:15 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: Device or resource busy
Jul 25 17:14:15 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.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
Jul 25 17:14:15 marto insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Jul 25 17:14:42 marto dnsmasq: failed to bind listening socket for 62.204.149.45: Address already in use
Jul 25 17:14:42 marto dnsmasq: FAILED to start up
AS YOU SEE THERE IS A PROBLEM WITH LOADING SOME MODULES. DO YOU THINK IT IS THE REASON WHY I CANNOT USE APM? ANY REMEDY?

Chances are, even if your motherboard supports ACPI it will work with APM. ACPI from what I read, is still new in gnu/linux. Many linux distributions up until recently disable ACPI support as their default installation method so as to "play it safe". Even slackware by default choses a kernel that is configured for APM and not ACPI as it's default.

I would think that your issue is probably an installation error. You really should be able to use the bare.i kernel whether you have ACPI or not. Just use the "full" "noobie" install to play it safe and Pat defaults the installer to put everything in their for you that you need for a clean good working system.

After you reinstall, just reboot as slakware tells you to, and then after the pc comes back up, log in as root, then edit the /etc/rc.d/rc.modules file so that the /sbin/modprobe/apm is un-commented (without a #).

In console to do that you just:

arrow key down to the line for the /sbin/modprobe/apm and un-comment it.

then to exit the pico program.

now at this point you only told slackware to load the APM at start-up.

now you can tell it to load the APM now with

""

your cursor should quickly return to another root prompt. that is a good sign.

now type in "" and you should see a bunch of text scroll on the screen and you should see that "apm" is listed there.

now to test it, type "" and your computer should shutdown for you.