Problem Shutting down or rebooting

Paul Nedlands pauln at mantatest.com
Thu Apr 15 16:58:06 UTC 2004


Thank you for the suggestions Eric.

Indeed your suspicions were correct.
There were no S* entries at all in rc0.d
I added the links:
S00killall -> /etc/rc.d/init.d/killall
and
S01halt -> /etc/rc.d/init.d/halt

This fixed the shutdown problem.
For the reboot problem there was no reboot entry in /etc/rc/d/init.d
Looking at the halt script there, it looks at its name (halt or reboot)
to decide what to do, so I copied the script and renamed it reboot.
I then added the following links in rc6.d
S00killal -> /etc/rc.d/init.d/killall
and
S01reboot -> /etc/rc.d/init.d/reboot

This fixed the reboot problem.
Also regarding APM you were right. The machine uses ACPI.

Things are now working properly.

Many thanks,

Paul

-----Original Message-----
From: Network Administrator [mailto:administrator at mantatest.com]
Sent: Thursday, April 15, 2004 9:28 AM
To: pauln at mantatest.com
Subject: RE: Problem Shutting down or rebooting


>I am running Fedora Core on a Dell Inspiron 8100 laptop and am having
>trouble with shutdown/reboot.
>Many aspects of it work correctly. In particular it runs the INIT script,
>stops processes, shuts things down, and then hangs forever after the
>message: INIT: no more processes left in this runlevel

The init process message is OK.  It means that you have no processes for
init to work on (either to kill or to start).
Look in /etc/rc.d/rc.0 for a "shutdown" process.  It will be something like
"SXXshutdown" in this directory, and will be an executable symbolic link.
"XX" will be some numbers.

The S means that this process gets started in runlevel 0, which is the one
that shuts the system down.  So every process running gets killed by init
(those are the K's) and then this one takes you down. But at this point, the
power management system needs to come in and turn the system off.

I'm assuming that after you directly power off with the button, that the
system goes down.  And then, upon reboot, the system reports that the
disk(s) are dirty or that "repair is needed" in among all the bootup
messages.  Is my guess correct?.

If this is so, then your runlevel 0 (zero) is probably awry.  Otherwise, I'd
suspect a power-management problem.

>At this point the machine needs to be directly powered off or powered off
>and on again for another boot. In the hope that this was related to the Red
>Hat 9 SMP problem, I added apm=power-off to the grub kernel boot line, but
>no joy.

Are you certain that you have an APM machine?  Might you have an ACPI system
instead?  I had this problem with my ACPI laptop (an Inspiron 1100) until I
changed the boot parameters in GRUB to enable ACPI.  If in your boot log you
see a message that says something like "APM BIOS not found", you actually
don't have APM.

>Help,

>Paul

Hope this helps.  Come back with more detail and perhaps I can be of more
help.   Erik


--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list





More information about the fedora-list mailing list