SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Sounds like an ACPI problem. Without it, the system will just come to a halt but it won't actually power down your hardware. Weird, this should be enabled by default. Did you uncheck certain items when you installed?
I suggest you go to System > Administration > yast and check whether there are any ACPI packages to install.
I got this after typing the command, which one should i choose?
linux-tuvz:/home/jerry # shutdown --poweroff now
shutdown: invalid option -- -
Usage: shutdown [-akrhHPfnc] [-t secs] time [warning message]
-a: use /etc/shutdown.allow
-k: don't really shutdown, only warn.
-r: reboot after shutdown.
-h: halt after shutdown.
-P: halt action is to turn off power.
-H: halt action is to just halt.
-f: do a 'fast' reboot (skip fsck).
-F: Force fsck on reboot.
-n: do not go through "init" but go down real fast.
-z: shutdown using software suspend.
-c: cancel a running shutdown.
-t secs: delay between warning and kill signal.
** the "time" argument is mandatory! (try "now") **
This will scan for any error messages and print them to an "error" file in your home directory. If you post that file, we may find out what is going wrong.
btw, you may also want to check your BIOS and make sure that ACPI is enabled. Of course, if you were running something else before SLED and powering down was no problem, then obviously this is not the problem.
Huh, so Suse hasn't got /var/log/dmesg now? OK, if the sytem says so, that must be correct. I would suggest that - providing you haven't done so yet - you check whether there are any updates to be made. It's quiet often that a system has some bugs which are resolved only by an update.
Give it a try and post back. I'll get back to you as soon as possible (some other business to attend to right now).
I have installed updates, but it hasn't fixed the problem.
BenQ Joybook S73G
1.66 GHz Core Duo
ATI Mobility Radeon x1600 512mb
80 GB hard drive
OS: Windows XP home edition and SLED 10