Power management under TTY

Message

PeGa! · Post by **PeGa!** » Thu Jun 06, 2019 2:37 am

Hello,

I'm doing a long waited system upgrade in my laptop, and as it only has 4GB of RAM, I decided to stop X entirely and work only in TTY.

Now, the problem is, when I close the lid, my system (i5 5200u based generic laptop) goes to sleep.

How could I control that behavior? In X (I use Plasma Desktop) it's just a couple of clicks, but what about TTY? I tried vbetool to no avail, and a couple of searches around the forums pointed me to look into /etc/acpi (there's no such directory in my system, and after a quick eix I noticed I don't have any acpi packages installed either) and to look into /proc. However, in /proc I only found the lid state and /sys wasn't helpful either.

Any hints will be appreciated.

Thanks in advance.

fturco · Post by **fturco** » Thu Jun 06, 2019 9:46 am

If you use systemd you can set HandleLidSwitch=ignore in /etc/systemd/logind.conf and restart systemd-logind.service (be warned that this will terminate all login sessions that might still be open). Unfortunately I don't know how to accomplish the same thing with OpenRC or other init systems...

PeGa! · Post by **PeGa!** » Thu Jun 06, 2019 1:22 pm

Hi fturco,

I forgot to specify; I'm using OpenRC.

Thanks anyway.

cboldt · Post by **cboldt** » Thu Jun 06, 2019 2:34 pm

Likely the kernel is doing this all on its own, that is, no need for any userspace ACPI package.

There is a file in the kernel source code tree, Documentation/acpi/acpi-lid.txt that advises of a few kernel boot parameters that affect how the lid switch is handled. I suppose there are some kernel build settings that could accomplish a similar "ignore" effect.

eccerr0r · Post by **eccerr0r** » Thu Jun 06, 2019 2:41 pm

It's doing some firmware based suspend. Acpid should intercept all the acpi events, of which lid switch is one of them. You can try emerging acpid and see if it will intercept the suspend like what GUI normally does to handle the suspend event.

(vbetool only handles your display, not cpu)

BTW, you probably can get away with running the GUI on 2GB 32-bit and ~3GB 64-bit machines, less than that is dicey, but you need swap space. I set up swap on all my machines including SSD based machines for the overflow.

cboldt · Post by **cboldt** » Thu Jun 06, 2019 3:16 pm

Tried this, worked for me ...

"To toggle their state you have to echo the device name to the file as root."

Code: Select all

# echo LID > /proc/acpi/wakeup

I did a `cat proc/acpi/wakeup` and the contents include an entry called "LID"