SlackwareThis 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.
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.
I put Slackware on Zareason's Alto and started playing with power options. Trying to make power button to hibernate or bring up menu, but it just ain't happening. Regardless of settings in KDE it seems to instantly run shutdown.
Kind of off-topic, but should I expect all of the Fn- things to work? Brightness and sound level, for example, work great, while sleep and wifi do nothing. Looks like may be half of them work.
I had a similar problem with my netbook. I set up the XFCE power manager to hibernate the netbook when the power-button is pressed. This worked, but when waking up the netbook it shutted of the system after the wake-up finished. This was caused by the settings in /etc/acpi, the power-button was set up to shut down the system there.
I don't know how you could edit /etc/acpi/acpi_handler.sh directly to do that, but you could just comment out everything in /etc/acpi/events/default, and have Xfce (or whatever GUI you use) manage the power button itself (that's what I did and it works just fine).
A while back, I was having trouble with X on my desktop: all mouse/keyboard input was ignored, so there was no way to exit X, not even Ctrl-Alt-F1 to switch to a text console. The only way out was the power button, but that incurred a power-cycle on every iteration of the bug-hunt.
The quick & dirty solution:
1. In /etc/acpi/acpi_handler.sh, change the "power" case to execute "/sbin/init 3".
2. "telinit 4" to launch X, powerbutton to kill X. No power cycle, plus it's just a whole lot faster.
I know that this is an old post, but this is an useful question since the /etc/acpi/acpi_handler.sh file is always replaced when Slackware is reinstalled or in new installations.
The best solution I've found here was to do what TommyC7 said, but replacing
Code:
power) /sbin/init 0
simply by
Code:
power)
In this way, when pressing the power button on the keyboard the logout screen appears (with the options to turn off, sleep, restart, etc...) instead of turn of the PC instantly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.