HI!
I've read several threads similar to my problem...but no resolution.
When I hit Power-off computer...system halts...but computer does not shutdown. Have to turn off power manually. NO, it's not that hard to do.. but something's not working right and I want to fix it. It used to turn the computer off. I've apparently messed up something! All other OS turn off computer fine.

puppy linux 2.12

sh-3.00# fdisk -l

Disk /dev/hda: 30.6 GB, 30614814720 bytes
255 heads, 63 sectors/track, 3722 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2550 20482843+ c W95 FAT32 (LBA)
/dev/hda2 2551 3060 4096575 83 Linux
/dev/hda3 3061 3570 4096575 83 Linux
/dev/hda4 3571 3722 1220940 82 Linux swap / Solaris

Thanks

Does your board use APM or ACPI? Have you done any changes in the BIOS configuration lately?

Please post the output of:

ps aux | grep apm....nothing

5610 root 584 S grep acpi

Without you answering the questions that were asked that doesn't really tell us much. That said, you don't seem to be running either the APM or ACPI daemons, which is possibly the cause of your problem. If your board is APM, try loading the apm module:If it loads fine (check with lsmod), try shutting-down again.

If your board is ACPI, try manually starting acpid, which on most distros would go like:Then try shutting-down again.

Sorry I had trouble at first ...

sh-3.00# ps aux | grep apm
7045 root SW [kapmd]
7127 root 580 S grep apm
sh-3.00# ps aux | grep acpi
7143 root 580 S grep acpi
sh-3.00#

How about entering "poweroff" at the command line? May need su or sudo to get root privileges.

win32sux,
I followed your instructions and shutdown problems are no more!
Thank You!

That's great, but keep in mind that you'd still need to make adjustments to your startup scripts for the change to be permanent. Like, say that loading the apm module did the trick, you'd need to add said module to the list of modules to be loaded at startup. Or say that running the acpid init script did the trick, you'd need to figure-out why the script isn't getting run at startup in the first place.

your right...I'm still having trouble...when shutting down, I get the message..
shutting down / : recources busy or unavailable...and in the tmp file I get lots of missing mods txt files...any ideas?

I still have no clue which of the procedures allowed you box to shutdown properly. Additionally, it would be great if you could clarify whether or not the busy resources error appears only when you carry-out the procedure. I don't understand what you mean with "mods txt". Please try to be as verbose as possible when you post replies.

Sorry...I'm still new and half the time have no idea what I'm doing...must be a slow learner...but I do appreciate the time spent helping me...
lsmod produced :

rivafb 52672 0
vgastate 9904 1 rivafb
snd_via82xx 27720 0
gameport 14904 1 snd_via82xx
snd_ac97_codec 90448 1 snd_via82xx
snd_ac97_bus 2128 1 snd_ac97_codec
snd_pcm 77592 2 snd_via82xx,snd_ac97_codec
snd_timer 23540 1 snd_pcm
snd_page_alloc 10008 2 snd_via82xx,snd_pcm
snd_mpu401_uart 8112 1 snd_via82xx
snd_rawmidi 24064 1 snd_mpu401_uart
snd_seq_device 7996 1 snd_rawmidi
snd 51396 8 snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_devic e
soundcore 9408 1 snd
parport_pc 32100 1
parport 35080 2 lp,parport_pc
via_agp 9648 1
agpgart 34608 1 via_agp
uhci_hcd 23356 0
usbcore 126116 3 usb_storage,uhci_hcd
nls_iso8859_1 3984 0
nls_cp437 5648 0
sh-3.00#
*

sorry..this post was too long

file too long

Next time please use code tags when you decide to post stuff like this. It makes things easier for everybody. That said, the questions I asked you in my previous post are still up in the air.

After a quick look at your init script, it would seem you'd just need to add the appropriate line in /etc/rc.d/rc.modules in order for your apm module to be automatically loaded. That is, of course, if you are on an APM board (which we don't really know since it's one of the questions we've never received and answer for).

ok! found the problems!
puppy linux not shutting down...just halting system.
opened /boot/grub/menulst and
added..."PMEDIA=idehd acpi=force" to the end of kernel boot line..so it looked like this..
kernel /boot/vmlinuz root=/dev/hda2 ro vga=normal PMEDIA=idehd acpi=force
rebooted...shutdown problem fixed..
as for the missingmods.txt files...

SP212 - Unofficial Service Pack for Puppy 212

this fixes a minor bug ... files called missingmods*.txt are being created in /tmp
and are not being deleted
you can download the fix here:
http://www.murga-linux.com/puppy/viewtopic.php?&t=12907
Thanks for all the help...and advice on posting!