LinuxQuestions.org - system reboots when i shutdown -h now. any ideas why?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - system reboots when i shutdown -h now. any ideas why? (https://www.linuxquestions.org/questions/slackware-14/system-reboots-when-i-shutdown-h-now-any-ideas-why-437659/)

system reboots when i shutdown -h now. any ideas why?

hello everyone,
my first problem as a newbie in linux and thus my first thread.

the story is abit longer than stated in the title:
i installed recently slackware 10.2 with kernel version 2.4.31.
yesterday i decided to update the kernel in 2.6.16.9. seems like i did everything right and my system reboots nicely again etc. but i ended up not being able to shutdown the pc. so now when i shutdown -h now, i get the full (proper) halting process, but the pc never switches off, it really reboots!

searching through the forums here i tried the following:
1) if i type in bash 'apm' i get the response: no APM support in kernel - looks pretty obvious to me whats going on here.. however i felt i went thoroughly through the menuconfig steps, reading the help in almost all options available to me prior to choosing whether to install, or not, or make them modular.
2) it was suggested in the forums to do mobprobe apm but when i do that i get the response
FATAL : module apm not found
3) so i cd /etc/rc.d/rc.modules and i uncommented the apm support line '/sbin/modprobe apm'. i restarted but no luck.

so i need to know if it is i didn't enable some option in menuconfig. to make things a little easier i copy-pasted all of the power management section of .config here. hope this will help.
Thanks in advance everyone!
nass

:newbie:
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_SLEEP_PROC_SLEEP=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

Run halt and check if it works.

well it doesn't but i didnt expect it would..
i mean shutdown -h is really halt just in a more 'gentle' for the processes way... no?

haha this is hilarious
if i press the power button on the pc tower then i get a proper shutdown that also halts and powers off the pc completely on its own.
still however by trying "shutdown -h now" or "halt" i get a reboot!!!
please help.

in fact i went through all the process of recompiling all the kernel adding all the acpi and apm features i left out b4! but again, no luck.
:confused:

do u have other OS(windows xp or etc) in the same PC? If they managed to halt down completely, it could be your slackware probs. I had an experience where both my OSes were unable to shutdown completely. It turned out to be that nasty power supply :/.

it looks like you have both APM and ACPI configured for your kernel. i always just turn off APM completely. ACPI is preferred for newer hardware anyway. Try turning off APM and re-compile then see if that helps.

Check /bin/shutdown script:

Code:

#!/bin/sh

# Try to do the right thing for programs that rely on "/usr/bin/shutdown -r now"

# to shut down the machine.

prog=/sbin/shutdown

now=

for flag in $* ; do

        if test ${flag} = "-h" ; then

                prog=/usr/bin/halt

        elif test ${flag} = "-r" ; then

                prog=/usr/bin/reboot

        elif test ${flag} = "now" ; then

                now=$flag

        else

                args="$args $flag"

        fi

done

if [ -z "$args" -a $prog != /sbin/shutdown ] ; then

        exec $prog $args

else

        exec /sbin/shutdown $args $now

fi

slackamp, the fact is this pc is a PII running at 350MHz.. so no new machine at all. its also a fact that when i type 'apm' in bash i get the response "no apm in kernel".. so it seems only acpi is installed in kernel... yet again i did make sure i recompiled checking that all apm options are selected to make sure i have then in kernel... should i recompile -deselecting acpi support? i mean u ask me to recompile without apm i understand that but isnt it so i dont have apm even now?

the thing is with kernel 2.4.31 and the default tweaks (ie the ones inside the installation cd) the pc shutdown properly... so its not a hardware problem
the prob arose now..

another thing i just tried is to do a brutal halt -f -p and again it didnt do the poweroff but instead rebooted the system...
if u have any little details u want to elaborate on please do so, im up for tryig anything now with this system.

Alien_Hominid, i dont seem to have the specific script ur refering me to, but i did take a thorough look at the /etc/rc.d/rc.0 shutdown script.. the problem is the script seems to run fine... smth in the 'halt' process is not done properly..

thanks for ur help
nass

yes do that, recompile kernel with only apm selected (remove acpi). i just recompiled mine to use apm actually. also make sure you have "/sbin/modprobe apm" uncommented in the /etc/rc.d/rc.modules file. and make sure your apmd entries in /etc/rc.d/rc.M are NOT commented. oh and since you are using the latest kernel, make sure your udev is also installed and working properly. i suggest downloading the source for the udev in slacware-current and run the udev.Slackbuild.

FILE: /etc/rc.d/rc.modules
#### APM support ###
# APM is a BIOS specification for saving power using several different
# techniques. This is mostly useful for battery powered laptops.
/sbin/modprobe apm

FILE: /etc/rc.d/rc.M
# Start APM or ACPI daemon.
# If APM is enabled in the kernel, start apmd:
if [ -e /proc/apm ]; then
if [ -x /usr/sbin/apmd ]; then
echo "Starting APM daemon: /usr/sbin/apmd"
/usr/sbin/apmd
fi
elif [ -x /etc/rc.d/rc.acpid ]; then # otherwise, start acpid:
. /etc/rc.d/rc.acpid start
fi

well i recompiled without acpi support and it seems to work properly again.. but at boot up i get the following msg
FATAL: module apm not found.

and i ask you, why not?
the problem im asking is of course to get to understand this better, but also because i also get
FATAL: module agpgart not found
FATAL: module emu10k1 not found

and also later on

FATAL: module snd_pcm_oss not found
FATAL: module snd_mixer_oss not found

so im hoping that by understand the 1st ill get to solve these other probs as well..

Thanks alot for the help!

Have you compiled APM as module? it seems to me from your config that it is compiled built in. In that case you don't need to load the apm modules, they are already in the kernel

yep like koloth says, make sure you compile them as modules (M) not in the kernel (*). if you do, then don't try to modprobe them because you don't need to.

Here is my APM config

# Power management options (ACPI, APM)
# APM (Advanced Power Management) BIOS Support
CONFIG_APM=m
CONFIG_APM_IGNORE_USER_SUSPEND=y
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
CONFIG_APM_ALLOW_INTS=y
CONFIG_APM_REAL_MODE_POWER_OFF=y

You have CONFIG_APM=y.

I suggest compiling most things as a module, it will make your kernel smaller, less memory consumption. the only thing you really need to compile in the kernel is if you need them at boot time or use initrd.