SlackwareThis Forum is for the discussion of Slackware 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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
I've a "small" problem with my laptop, a Dell Inspiron 15 7537. The pc mounts Slackware64 14.1 with kernel 3.10.17 (KDE) but I've been forced to add Fedora 20 (KDE) in dual boot because Slackware doesn't want to turn off. The machine seems to turn off, but after few seconds it restarts.
I've tried to append "acpi=force" in /etc/lilo.conf, but nothing changes.
The only way to turn off the pc is to give one of these commands from command line:
But this way is a bit "dirty", IMHO. If I try poweroff, shutdown -h now or halt commands without any additional option, the machine restarts.
Besides, I've noticed that I can't suspend the pc through the KDE menu, but only giving this command via command line (found here on LQ):
Distribution: Gentoo, Gentoo ~amd64, Linux Mint 17
...that's because nobody can _kill_ Slackware... ;-p just trying to be punny!
Interesting problem. That's why have subscribed to this thread although I may not be able to help.
It looks like it's not hardware issue as you have installed Fedora and not complaining about it. May not be problem with KDE also as you have specifically mentioned that you are using KDE with Fedora and Slackware ships vanilla KDE.
Did problem start recently or was present since installation? Do you remember doing anything different in either case? Are you using huge kernel or generic. If you are using one can you try using other to see if problem persists?
I think there was a bug or something for 'shutdown' command and the proper options now includes 'P' for poweroff.
shutdown -hP now
Last edited by saivinoba; 12-31-2013 at 08:50 PM.
Reason: to correct spelling
Ahahah! Yes, Slackware is invincible ;-)
The problem persists from the first installation (the pc is new). I'm still using the default kernel. In /etc/lilo.conf I can see the line image = /boot/vmlinuz, although in /boot there are also vmlinuz-huge-3.10.17 and vmlinuz-generic-3.10.17. Should I create an initrd as explained in the README.initrd in order to use the generic, right? But then I've to modify the grub because, once I've installed Fedora, the master boot record has been overwritten.
I've tried to launch the command shutdown -hP now as root, but the pc restarts. It seems it turns off for a few seconds but then restarts.
No, no sorry, maybe I've explained badly. With both, root and user, it doesn't work. The /etc/rc.d/rc.0 script is called correctly but inexplicably the machine restarts.
Yes, I've already added the user to the power group in /etc/group.
I've tried the generic kernel creating an initrd but the problem still persists...
Since I've not much time to spend in tests, I've decided to install Fedora on the whole disk and to keep Slackware64 in vm with Virtual Box for now.
I think it is a bit unlikely since nobody can access the pc except me
Sorry, I haven't tried it on the Dell, but on my old laptop this combination turns off the pc immediately.
However I think it isn't the right way to turn off the pc correctly. In my initial post I've written I can turn off the pc using halt -fihp or poweroff -fihp, but it is not the right way. The man halt command said:
-f Force halt or reboot, don't call shutdown(8).
-i Shut down all network interfaces just before halt or reboot.
-h Put all hard drives on the system in stand-by mode just before halt or power-off.
-p When halting the system, switch off the power. This is the default when halt is called as poweroff.
Thanks to all for your help. At this point I hope I can try successfully the next Slackware version...
Thank you for reporting!
Now my pc mounts Fedora (Slackware64 in vm), but if I remember correctly, I once tried to disable nouveau driver and restart the machine (not in init 4, but in init 3) but the problem persisted. Anyhow, in order to be sure, I'll retry when I'll do some tests with Slackware.
I purchased this laptop less than 2 weeks ago and am experiencing something similar to this when trying to run Ubuntu 13.10 from a USB startup disk.
At it's worst, it would restart after every second shut down.
In my case though I thought the problem was in the hardware as I've used this startup disk many times and never had this problem.
Plus it only restarted when powered by the AC adapter, on battery only it didn't happen.
Anyway, my laptop is to be returned this week because of it.
Rather than post a lengthy description of what I have done to analyse the problem, I will just add a link in the next post as I can't do it here as a newbie.
Last edited by OlderNWiser; 01-19-2014 at 05:57 PM.
Reason: Change comments
Incidentally, I had Windows 8 restart once or twice which was why I thought it might be a hardware problem.
In addition, the restarts from the Ubuntu USB only seemed to occur when using the ports closest to the AC adapter.
If I used the USB port on the right hand side, the restarts did not occur (at least not in the 20 shut downs I tried).
Anyway, this is the link to the Dell forum where I have posted all the details and it may help someone.