Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Why is it that when I shut down my system, it won't turn off automatically? It comes to a point it annouces "power down" but it remains on...
I'm using Vector Linux 5.0.1 SOHO (kernel 2.4.29) dual booted with Win XP. The boot loader is Lilo.
My config is as follows:
P4 2.4
Intel motherboard with chipset 850e
512mb Rimm
hd 60gb primary master
hd 80gb primary slave
cd writer secondary master
dvd writer secondary slave
ati 8500
sb audigy
Here's Lilo.conf:
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
default = linux
prompt
timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Partition 1 : DOS/Windows
other = /dev/hda1
label = windows
table = /dev/hda
# Partition 2: Linux GUI mode
image = /boot/vmlinuz
root = /dev/hda7
label = linux
append = ""
read-only
My boot/config apm/acpi section:
Code:
# CONFIG_OOM_KILLER is not set
CONFIG_PM=y
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
#
# ACPI Support
#
# CONFIG_ACPI is not set
I saw in VL forums that VL normally defaults with acpi and apm, and despite this no one else is having my problem.
As for the inittab shutdown section I have:
Code:
# What to do at the "Three Finger Salute".
#ca::ctrlaltdel:/sbin/ctrlaltdel
ca::ctrlaltdel:/sbin/shutdown -a -t3 -r now
(also already tryed using "-t1 -h now")
I have my bios fully acpi enabled, despite VL not having acpi neither apm enabled, but I need it for Win XP.
Finnaly, I'm a heavy KDE user, so I really wanted to keep it having auto started and also to always shutdown from it.
Any help really apreciated
Thanks
Last edited by chocobanana; 03-24-2005 at 08:40 AM.
A common reason for the computer not shutting down after showing "Power down." is that the apm module isn't loaded. Check this with lsmod - the resulting listing will show the loaded modules. If it isn't loaded, load it with the command modprobe apm . Then see if it powers off properly.
Since you use Vectorlinux, which is Slackware based, there might be an out-commented line in /etc/rc.d/rc.modules, which reads #/sbin/modprobe apm . Remove the "#" and the APM module will be loaded in future boots.
I'm unsure how ACPI and APM work together, or even if they should work together. I mean, I believe that if you use ACPI, it should take care of this by itself, end hence APM should be unnecessary. But, as I said, I'm not sure about this.
Considering you're running a P4, I would say you probably need to use ACPI, not APM. ACPI support can either be built into the kernel or not at all. There is no option to compile it as a module, only the ACPI features, button, thermal, etc... can be built as modules. To simply shut the system down you don't need any of those features, only ACPI. dmesg should show you if ACPI is enabled in the kernel.
Make sure that you don't use SMP-kernel if you have only one CPU. Your P4 might have ht-flag even though it doesn't have HyperThreading enabled. SMP+1 CPU does not shutdown properly.
You dmesg output says you don't have ACPI compiled in your kernel.
Two ways I've got it to actually turn off the box:
APM:
In the kernel
Code:
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y
#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=m
and in /etc/rc.d/rc.modules
Code:
#### 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 <- uncommented
and in /etc/lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="apm=power-off"
then issue # poweroff
to shut it down.
And recently, thanks to Tinkster, it works with
ACPI
In the kernel
Code:
# Power management options (ACPI, APM)
#
CONFIG_PM=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_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_VIDEO 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=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
# CONFIG_ACPI_CONTAINER is not set
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
Nothing in /etc/rc.d/rc.modules or /etc/lilo.conf like with APM.
And just issue # halt to shut it down.
NB: The APM option is with a 2.4.29 kernel; ACPI is 2.6.11.5
but Tink says ACPI is what he uses and on both 2.4.x and
2.6.x kernels
If you want me to check your system, post the output of the following
commands and I'll just give her a look see. And while you're at it, what
distribution is Vector Linux based on -- save me a Google search cause
I don't remember. ;-)
$ cat /etc/rc.d/rc.modules
$ cat /etc/lilo.conf
$ ls -alc /boot
$ dmesg | grep ACPI
How are you issuing the command to shut your computer down?
Vector Linux 5.01 SOHO is based on Slackware 10.0 or 10.1, I'm not sure which one.
Here's my rc.modules:
Code:
### Update module dependencies ###
RELEASE=`uname -r`
VERSION=`kernelversion`
# If /usr is mounted and we have 'find', we can try to take a shortcut:
if [ -x /usr/bin/find -a -e /lib/modules/$RELEASE/modules.dep \
-a /lib/modules/$RELEASE/modules.dep -nt /etc/modules.conf ]; then
NEWMODS="`/usr/bin/find /lib/modules/$RELEASE -type f -newer /lib/modules/$RELEASE/modules.dep`"
# Only rebuild dependencies if new module(s) are found:
if [ ! "" = "$NEWMODS" ]; then
echo "Updating module dependencies for Linux $RELEASE:"
/sbin/depmod -a
else
echo "Module dependencies up to date (no new kernel modules found)."
fi
else # we don't have find, or there is no existing modules.dep, or it is out of date.
echo "Updating module dependencies for Linux $RELEASE:"
/sbin/depmod -A
fi
### AGP (Accelerated Graphics Port) GART support
/sbin/modprobe agpgart
### Network device support
if [ -x /etc/rc.d/rc.netdevice ]; then
. /etc/rc.d/rc.netdevice
fi
## Kernel 2.4 base modules
if [ "$VERSION" = "2.4" ]; then
### load ide-scsi if specified on boot parameter
if grep -q "=ide-scsi " /proc/cmdline ; then
/sbin/modprobe ide-scsi
fi
# exit immediatelly, cut further processing
exit 0
### Kernel 2.6 based modules
elif [ "$VERSION" = "2.6" ]; then
# PS/2 mouse support
if grep -qe "MOUSETYPE.*=.*ps2" /etc/sysconfig/vector; then
modprobe psmouse proto=imps
fi
# exit immediatelly, cut further processing
exit 0
fi # end VERSION check
Here's my lilo.conf:
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
default = vector_linux
prompt
timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Partition 1 : DOS/Windows
other = /dev/hda1
label = windows
table = /dev/hda
# Partition 2: Vector_Linux
image = /boot/vmlinuz
root = /dev/hda7
label = vector_linux
append = ""
read-only
# Partition 3: Vida_Linux
image = /boot/vmlinuz
root = /dev/hda8
label = vida_linux
append = ""
read-only
I'm issuing the shutdown from KDE. I'd really like to continue doing it because I work mainly with programs with UI, so I admit I'm looking for a certain comodity. But I already tryed issuing from the command line "shutdown -t 1 -h now" both as a user and also as root, but without results.
Something is wrong with your ACPI configuration in the kernel,
perhaps, or maybe you don't have an ACPI motherboard? You
should have more than those 2 lines for ACPI.
Since it's really long, could you post your entire contents of
/boot/config-acpi-2.4.29 at http://pastebin.com/ and then
provide the link? Perhaps it's okay to post it in here, but I'd
really like to get a look at the entire power management
section, as well as how they might have structured their
kernel different from the sources at kernel.org -- if they did.
Specifically, is there no APM enabled in your config?
Could you also post the output of "lsmod" here?
And for shutdown you only need issue "halt" if it's working
correctly for ACPI to shut the computer down.
If you have the time, you might also search Google <Linux>
for "shutdown from KDE"
You've got APM as a module in the kernel, but it's not loading.
CONFIG_APM=m
Try to uncomment it in /etc/rc.d/rc.M if Vector has that, and see
what happens. That file should look like this:
Code:
# 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
You can first look to see if apmd is running by issuing "ps -aux"
and if it is, then comment (put a # before) it out of that file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.