Slackware This Forum is for the discussion of Slackware 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
05-08-2008, 08:27 PM
|
#1
|
|
LQ Newbie
Registered: Aug 2004
Posts: 15
Rep:
|
Slackware 12.1 - halt problem
I am facing a strange problem since upgrading to 12.1 from 12.0 . Earlier when I would do a halt, it would power off the PC. But after I upgraded, it has stopped doing that. It simply stops at 'System had been halted' . So far I have tried 'modprobe apm' ( and verified using lsmod that it is actually loaded ) , shutdown -h and poweroff - but nothing has worked for me so far
Any clues as to what I might be missing ? - thanks
|
|
|
|
05-08-2008, 10:17 PM
|
#2
|
|
LQ Newbie
Registered: Apr 2008
Posts: 14
Rep:
|
yes, i'm having the same problem. being a newbie i',m sorry i can't help.
|
|
|
|
05-08-2008, 10:34 PM
|
#3
|
|
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,358
Rep: 
|
Perhaps this applies to you:
From Changes and Hints.txt:
Quote:
If you have an older machine (with a BIOS released prior to 2001) and it will not power off on shutdown, try adding this to your kernel's lilo stanza:
append = "acpi=force"
|
Brian
|
|
|
|
05-08-2008, 11:22 PM
|
#4
|
|
LQ Newbie
Registered: Aug 2004
Posts: 15
Original Poster
Rep:
|
Quote:
Originally Posted by BCarey
Perhaps this applies to you:
From Changes and Hints.txt:
Brian
|
Tried this from the boot prompt first - and it works like a charm. Will put it in lilo.conf now - THANK YOU very much Brian, for the tip.
-Rohit
|
|
|
|
05-09-2008, 06:06 AM
|
#5
|
|
LQ Newbie
Registered: Apr 2008
Posts: 14
Rep:
|
yes, i had read the changes and hints text previously,but somehow i'm not placing the acpi addition in the right place or in the right format. maybe
my bios is just a little to old. thanks
|
|
|
|
05-09-2008, 08:02 AM
|
#6
|
|
Member
Registered: Jan 2007
Location: Germany
Distribution: Slackware 13.37
Posts: 384
Rep:
|
Try it here:
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0 acpi=force"
boot = /dev/hda
lba32
# Boot BMP Image.
*snip*
|
|
|
|
05-09-2008, 09:57 AM
|
#7
|
|
LQ Newbie
Registered: Apr 2008
Posts: 14
Rep:
|
thanks general failure, but it still will not work in this format. i'll can learn to live with it, thanks.
Last edited by rwright; 05-09-2008 at 09:58 AM.
Reason: delete
|
|
|
|
05-09-2008, 09:57 AM
|
#8
|
|
LQ Newbie
Registered: Apr 2008
Posts: 14
Rep:
|
thanks general failure, but it still will not work in this format. i can learn to live with it, thanks.
|
|
|
|
05-09-2008, 10:01 AM
|
#9
|
|
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 3,655
|
Quote:
Originally Posted by rwright
thanks general failure, but it still will not work in this format. i can learn to live with it, thanks.
|
That format works for me on my ancient Plll 667 MHz IBM. Did you update lilo after editing lilo.conf?
|
|
|
|
05-09-2008, 10:12 AM
|
#10
|
|
LQ Newbie
Registered: Apr 2008
Posts: 14
Rep:
|
hitest, that was the problem. sorry, i forgot to run lilo. thanks everyone.
|
|
|
|
05-09-2008, 01:40 PM
|
#11
|
|
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 3,655
|
Quote:
Originally Posted by rwright
hitest, that was the problem. sorry, i forgot to run lilo. thanks everyone.
|
No need to apologize:-) I'm glad you got it working:-)
|
|
|
|
05-10-2008, 03:31 AM
|
#12
|
|
Member
Registered: Dec 2005
Distribution: Slackware
Posts: 250
Rep:
|
I have the same Problem, but my Bios is only from 2007 ? I have a asrock Mainboard with a crossfire chipset socket AM2 , so I think this fix shouldn't apply on my pc...
Anyway, I will try it later and then report back
|
|
|
|
06-13-2008, 11:26 PM
|
#13
|
|
Member
Registered: Jan 2005
Posts: 183
Rep:
|
Thanks! I had the same problem and the lilo trick fixed it for me as well.
I don't know why someone thought this only affects pre-2001 bioses. Mine is nowhere near that old. But come to think of it 2001 was probably the last time I saw a Windows box have this problem 
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:38 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|