Search Results for 'LID_SLEEP=true'

[Member iconoclast]

I followed the advice given in the discussion I referred to. The line “LID_SLEEP=true” is uncommented for me. I don’t have xfce-power-manager installed.

[Member iznit]

I used these tips

hmmm maybe should just use one OR the other (xfce-power-manager OR edit “#LID_SLEEP=true” line in /etc/default/acpi-support) maybe using both is causing a conflict? [[[ A “conflict” or a double trigger of the wake sleep toggle when the lidOPEN event is handled ]]]

[Member Xecure]

dknestaut wrote:

I gave it a try. Purging elogind and installing acpi-support had the same effect as my workaround.

Thanks for the feedback. If you then edit /etc/default/acpi-support
sudo geany /etc/default/acpi-support
and enable LID_SLEEP=true, and then reboot, does the issue appear again? If not, does the laptop sleep when the lid is closed or is this option completely ignored?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member slosion]

inxi -Fxz output:
System:
Host: vaio-antix Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64
compiler: gcc v: 8.3.0 Desktop: IceWM 2.0.1
Distro: antiX-19.3_x64-base Manolis Glezos 14 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: Sony product: VGNFW590FFT v: R5779802
serial: <filter>
Mobo: Sony model: VAIO serial: <filter> BIOS: American Megatrends
v: R4070Y0 date: 09/04/2009
Battery:
ID-1: BAT0 charge: 39.5 Wh condition: 41.1/41.1 Wh (100%)
model: Sony Corp. status: Charging
CPU:
Topology: Dual Core model: Intel Core2 Duo T9600 bits: 64 type: MCP
arch: Penryn rev: A L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11168
Speed: 1600 MHz min/max: 800/2801 MHz Core speeds (MHz): 1: 1600 2: 800
Graphics:
Device-1: AMD RV730/M96 [Mobility Radeon HD 4650/5165] vendor: Sony
driver: radeon v: kernel bus ID: 01:00.0
Display: server: X.Org 1.20.4 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920×1080~60Hz
Message: No advanced graphics data found on this system.
Audio:
Device-1: Intel 82801I HD Audio vendor: Sony driver: snd_hda_intel
v: kernel bus ID: 00:1b.0
Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series] vendor: Sony
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network:
Device-1: Intel WiFi Link 5100 driver: iwlwifi v: kernel port: d000
bus ID: 06:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Marvell 88E8055 PCI-E Gigabit Ethernet vendor: Sony driver: sky2
v: 1.30 port: 9000 bus ID: 08:00.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 6.71 GiB (1.4%)
ID-1: /dev/sda vendor: Hitachi model: HTS725050A9A360 size: 465.76 GiB
Partition:
ID-1: / size: 195.09 GiB used: 6.71 GiB (3.4%) fs: ext4 dev: /dev/sda4
Sensors:
System Temperatures: cpu: 58.0 C mobo: 58.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 156 Uptime: 1h 45m Memory: 5.80 GiB used: 951.6 MiB (16.0%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36

I installed antiX base from a live DVD.
I got the ISO from an official mirror given by the website.
I haven’t checked its integrity.

Suspending from the logout menu shuts down the laptop.
After that pressing keys makes it boot to the GRUB menu.

I scanned the linux partition and it didn’t return any errors.

I downloaded acpi-support from the repository, which created the acpi-support file.
After uncommenting LID_SLEEP=true, it still shuts down.
It probably is suspending, since as I said suspend just shuts it down.

It seems like these issues could stem from slim not starting.

[Member slosion]

inxi -Fxz output:
System:
Host: vaio-antix Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64
compiler: gcc v: 8.3.0 Desktop: IceWM 2.0.1
Distro: antiX-19.3_x64-base Manolis Glezos 14 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: Sony product: VGNFW590FFT v: R5779802
serial: <filter>
Mobo: Sony model: VAIO serial: <filter> BIOS: American Megatrends
v: R4070Y0 date: 09/04/2009
Battery:
ID-1: BAT0 charge: 39.5 Wh condition: 41.1/41.1 Wh (100%)
model: Sony Corp. status: Charging
CPU:
Topology: Dual Core model: Intel Core2 Duo T9600 bits: 64 type: MCP
arch: Penryn rev: A L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11168
Speed: 1600 MHz min/max: 800/2801 MHz Core speeds (MHz): 1: 1600 2: 800
Graphics:
Device-1: AMD RV730/M96 [Mobility Radeon HD 4650/5165] vendor: Sony
driver: radeon v: kernel bus ID: 01:00.0
Display: server: X.Org 1.20.4 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920×1080~60Hz
Message: No advanced graphics data found on this system.
Audio:
Device-1: Intel 82801I HD Audio vendor: Sony driver: snd_hda_intel
v: kernel bus ID: 00:1b.0
Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series] vendor: Sony
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network:
Device-1: Intel WiFi Link 5100 driver: iwlwifi v: kernel port: d000
bus ID: 06:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Marvell 88E8055 PCI-E Gigabit Ethernet vendor: Sony driver: sky2
v: 1.30 port: 9000 bus ID: 08:00.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 6.71 GiB (1.4%)
ID-1: /dev/sda vendor: Hitachi model: HTS725050A9A360 size: 465.76 GiB
Partition:
ID-1: / size: 195.09 GiB used: 6.71 GiB (3.4%) fs: ext4 dev: /dev/sda4
Sensors:
System Temperatures: cpu: 58.0 C mobo: 58.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 156 Uptime: 1h 45m Memory: 5.80 GiB used: 951.6 MiB (16.0%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36

I installed it from a live DVD of antiX base.
I got the ISO from an official mirror listed on the website.
I haven’t checked the integrity.

When pressing suspend from the logout menu it shuts down.
Pressing keys makes it start up to the GRUB menu.

I ran a scan of the linux partition and it didn’t find any errors.

The acpi-support file didn’t exist.
I installed acpi-support from the repository.
Doing this created the file.
After uncommenting LID_SLEEP=true, closing the lid still shuts it down.
This might mean it is suspending, since as I said suspend just shuts it down.

It started slim fine for the first few boots, but then it started requiring root to manually start it.
It seems like this could be the cause of all the other issues.

• This reply was modified 2 years, 3 months ago by slosion.
• This reply was modified 2 years, 3 months ago by slosion.

[Member Xecure]

Hello.

You first need to start giving us you system information. Just saying “I’m using a Sony laptop from 2009” doesn’t tell us anything about what is inside your computer, only that the sony put it all together and sold it. Please, launch a terminal and give us the output of
inxi -Fxz
This will first tell us what version of antiX you installed (if the newest 19.3 or an older one, if 32 or 64 bits, if the BASE edition or the FULL edition, which is important to know), the kernel version you are using, and also give us some more info related to your model and CPU, and also the GPU, which will help figure out why Xorg doesn’t start at boot.
Also, you should tell us if this is installed or running on Live USB. If installed, did you install using the whole disk, manual partitioning (and if so, did you reuse a home partition or is this only one / (root) partition).

You should also separate the issues. This time, I will do it for you.

1. Closing the lid shuts down the computer. What the user wants is to have the computer suspend when closing the lid (you mention hibernate, but that is not set up by default in antiX, so suspend will be what I recommend).
2. Pressing the power button shuts down the computer. The user wants it to suspend instead (I assume).
3. Slim (or Xorg) doesn’t start when the system boots up.

For 1 (close lid makes it so it suspends), there are two possibilities:
A. Suspend doesn’t work (for reasons to still be investigated), so when the system tries to suspend instead it shutsdown. Try using the Suspend option in the Exit Session menu and check if suspend/wake works.
B. Misconfiguration in acpi-support. If you are running antiX 19.3 base or full, then you can try configuring acpi-support and enable (if not already) LID_SLEEP.
sudo xdg-open /etc/default/acpi-support
Previously to antiX 19.3, the other 19.X base editions didn’t include acpi-support, so this needs to be installed on these cases. That is why it is important to give us more information, as some things may not be there (for space reasons, so the ISO was CD size).
More cases related to LID_SLEEP=true (https://www.antixforum.com/forums/search/LID_SLEEP=true/)

For 2 (Powerbutton shuts down the computer). May be related to option A from above or a acpi event not being recognized properly. We will need more information on your system to investigate the issue.

For 3 (Xorg not starting at boot), we will also need more information. Maybe there was a regression in Debian 10, and maybe this doesn’t happen with antiX 17. We may need to check how different the live experience was to the installed one.

EXTRA INFORMATION: Did you check the integrity of the ISO used or the live media? Did you install from CD or USB? Did you select a specific boot option (like Safe Video Mode or Failsafe mode)? Did you check the HD health?

With computers, there are so many different factors that are involved and may be responsible for something going wrong (including both software and hardware) that diagnosing may not be as strait forward as people think. It is similar to a medical issue. We may have some symptoms, but those can be related to many different causes (including physical and mental problems). That is why we go to physicians so, with different tests and observations, they try to discover the cause of our problems and, if it is possible, also a solution.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

drinkWine wrote:

Distro: antiX-19.2.1_x64-base

You need acpi-support package and activate lid sleep.

sudo apt update && sudo apt install acpi-support

Then edit the /etc/default/acpi-support file with root privileges. Example:
sudo geany /etc/default/acpi-support

And search for the line #LID_SLEEP=true and uncomment it. It should look like:
LID_SLEEP=true

You don’t even need to reboot to see this work. Close the lid.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

Unfortunately, it seems the logs are only for this session, and not for the one where you close the lid.

The ideal thing would be to make the “close lid behavior” work exactly the same as suspend/wake.

I won’t have much time to look into this this weak, so I will give you all my suggestions.

Add hook to suspend/resume
If you are going to use (Suspend) and then close the lid, you can always (with root privileges) create a file in /usr/lib/pm-utils/sleep.d/ with a name like 0000trackpad
and add this code:

#!/bin/sh
case "$1" in
	suspend|hibernate)
		modprobe -r psmouse
		;;
	resume|thaw)
		modprobe psmouse
		;;
esac

then make it executable
sudo chmod +x /usr/lib/pm-utils/sleep.d/0000trackpad

Updating the kernel
About updating the kernel, it can be done on a live system. I would first back up the entire system though.
The steps are the ones I follow whenever I update the kernel on my live-USB (there is a shorter way, but this is the one that always works for me.:
1. download and install the latest 4.19 kernel using antiX package installer, synaptic or cli-aptiX
2. Save persistent changes (I always like to do this) and reboot
3. Remaster your antiX live system. Reboot
4. Use the Live-USB Kernel Updater (can be found from the menu or from the control centre > Live).
4.1 Select the kernel you want to update (4.19). Follow the steps. The reboot.
5. If all goes well, your system will now boot with the new kernel. If it breaks, you can recover your system by accessing your live/boot-dev/antiX/ folder (from a different system I think) and renaming rootfs to rootfs.bac, rename linuxfs to linuxfs.bac, then restoring your linuxfs.old to linuxfs and rootfs.old to rootfs.
It may sound a bit complicated, but it is not that bad. Anyway, if it seems too complicated and you don’t want to risk your live system then ignore this and try it out some other time in the future.

Checking acpi-support
About suspending by closing the lid, you need to check the file /etc/default/acpi-support. There is a line there that should be uncommented. It needs to look like this:
LID_SLEEP=true
I would comment out the hibernate option just in case that is the problem when closing the lid. It should look like:
#ACPI_HYBERNATE=true

If you find you need help, I am sure someone else can comment here while I am away. You could also wait or test things out to see how everything works (make sure to backup before experiments).

Good luck!

• This reply was modified 2 years, 10 months ago by Xecure. Reason: correction
• This reply was modified 2 years, 10 months ago by Xecure. Reason: error in code

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator BobC]

anti,

The info wasp gave was from /etc/default/acpi-support

Here is what is in my stock file:

$ cat /etc/default/acpi-support
#
# Configuration file for the acpi-support package
#
#
# The acpi-support package is intended as "glue" to make special functions of
# laptops work. Specifically, it translates special function keys for some
# laptop models into actions or generic function key presses.
#

#
# Suspend/hibernate method
# ------------------------
#
# When gnome or kde power management daemons are running, acpi-support will
# translate the suspend and hibernate keys of laptops into special "suspend"
# and "hibernate" keys that these daemons handle.
#
# Only in situations where there is no power management daemon
# running, acpi-support needs to perform suspend/hibernate in some other way.
# Beginning with version 0.122-1 acpi-support solely uses pm-utils then.

# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true

# Comment the next line to disable suspend to disk
ACPI_HIBERNATE=true

# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true

# Comment this out to disable screen locking on resume
LOCK_SCREEN=true

# Uncomment this to enable ACPI sleep when the lid screen is closed.
#LID_SLEEP=true

# Uncomment this to shutdown the system if ACPI sleep has not been possible
# upon lid closure. Has no effect if LID_SLEEP is not set.
#LID_SHUTDOWN=true

# On some systems pressing the wireless button only results in an event that we
# handle, but not in some hardware enforced action. On these systems we are
# free to choose whether or not we cycle through "Both on, Both off, Wireless
# only, Bluetooth only" as we used to do, or if we just do "Both on, Both off"
# as the hardware kill switch does on most systems.
#
# For compatibility reasons with older version the larger cycle is the default.
# Enable this to to have both in switched on and off simultaniously. 
#WIRELESS_BLUETOOTH_SYNC=true

# Choose the method used to switch off/on the display. Available options are
# "xset", "xrandr" and "vbetool".
DISPLAY_DPMS=xset

# xrandr needs the output device to be named
XRANDR_OUTPUT=LVDS

# vbetool can switch off/on the display even if no user is logged in. However,
# there are systems that do not reset the display when coming out of suspend,
# so that the screen remains dark. Enable this option to switch off the display
# even if no one is logged in.
#DISPLAY_DPMS_NO_USER=true

• This reply was modified 3 years, 8 months ago by BobC.

[Forum Admin anticapitalista]

wasp wrote:

The bug of the non-blocking of the screen after the continuous suspension and of the characters not defined as in Antix 17.

# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true

# Comment the next line to disable suspend to disk
#ACPI_HIBERNATE=true

# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true

# Comment this out to disable screen locking on resume
LOCK_SCREEN=true

# Uncomment this to enable ACPI sleep when the lid screen is closed.
LID_SLEEP=true

If you let me know what file this refers to, I can make the change if others deem it necessary. BTW, is the above what is *should* be?

• This reply was modified 3 years, 8 months ago by anticapitalista.
• This reply was modified 3 years, 8 months ago by anticapitalista.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member wasp]

The bug of the non-blocking of the screen after the continuous suspension and of the characters not defined as in Antix 17.

# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true

# Comment the next line to disable suspend to disk
#ACPI_HIBERNATE=true

# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true

# Comment this out to disable screen locking on resume
LOCK_SCREEN=true

# Uncomment this to enable ACPI sleep when the lid screen is closed.
LID_SLEEP=true

What is the best way to have auto-suspend into antiX ?

dolphin_oracle wrote:
I think what you need is in /etc/default/acpi-support. Look for this line

Code: Select all
# Uncomment this to enable ACPI sleep when the lid screen is closed.
#LID_SLEEP=true

and try uncommenting the LID_SLEEP line.

I have seen this tip & trick, and that’s work for the lid screen.

But I also would like to have an auto-suspend mode at, for example, after 15 minutes inactivity, and I do not seen any available options for “power management” into the “Control Center”, and ether.

So what is the best practice for antiX ?
Maybe :linrunner , or an other sofware like that ?
https://linrunner.de/en/tlp/tlp.html

• This topic was modified 4 years ago by oops.

[Member wean_irdeh]

isminaki wrote:

I had the same question and found this:

https://antixlinux.com/forum-archive/laptop-suspend-solved-t5071.html

It works for me.

Ah thanks, editing /etc/default/acpi-support and removing hash (#) from #LID_SLEEP=true works for me! I can even disable lock screen by adding hash (#) in LOCK_SCREEN=true
Thanks a lot

And thanks to caprea for trying to help me