No option to "hybrid sleep" on reaching critical battery level

Support
1

I wish to put the computer to hybrid sleep automatically when it reaches critical battery level. I do not find such an option.

Here’s where I checked:

System Settings > Power Management > Advanced Power Settings > Battery Levels > At critical level:

image
image2690×1569 357 KB

Only the following options are available:

  • Do nothing
  • Sleep
  • Hibernate
  • Shutdown

Thoughts?

inxi --full --verbosity=7 --filter --no-host 
System:
  Kernel: 5.19.7-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    Desktop: KDE Plasma v: 5.25.5 tk: Qt v: 5.15.5 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Convertible System: LENOVO product: 20JES01U2C v: ThinkPad X1 Yoga
    2nd serial: <superuser required> Chassis: type: 31
    serial: <superuser required>
  Mobo: LENOVO model: 20JES01U2C v: SDK0J40697 WIN
    serial: <superuser required> UEFI: LENOVO v: N1NET54W (1.41 )
    date: 08/17/2021
Battery:
  ID-1: BAT0 charge: 16.7 Wh (33.7%) condition: 49.5/56.0 Wh (88.4%)
    volts: 14.9 min: 15.3 model: SMP 01AV441 type: Li-poly serial: <filter>
    status: discharging cycles: 516
  Device-1: wacom_battery_0 model: Wacom Pen and multitouch sensor
    serial: N/A charge: 0% rechargeable: yes status: N/A
Memory:
  RAM: total: 15.37 GiB used: 5.41 GiB (35.2%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: dual core model: Intel Core i7-7600U bits: 64 type: MT MCP
    smt: enabled arch: Amber/Kaby Lake note: check level: v3 rev: 9 cache:
    L1: 128 KiB L2: 512 KiB L3: 4 MiB
  Speed (MHz): avg: 892 high: 900 min/max: 400/3900 cores: 1: 900 2: 869
    3: 900 4: 900 bogomips: 23209
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
    rep_good sdbg sep sgx smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3
    stibp syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx
    vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-8:3 chip-ID: 04f2:b5ce class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.4 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: eDP-1 model: Lenovo 0x4140 res: 2560x1440 hz: 60 dpi: 210
    size: 310x175mm (12.2x6.89") diag: 356mm (14") modes: 2560x1440
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.1.7
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
    class-ID: 0403
  Sound Server-1: ALSA v: k5.19.7-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.57 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d7 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:2 chip-ID: 8087:0a2b class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 8 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 953.87 GiB used: 94.14 GiB (9.9%)
  ID-1: /dev/sda vendor: SanDisk model: SD9SN8W-1T00-1006 size: 953.87 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4006 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / size: 920.87 GiB used: 88.69 GiB (9.6%) fs: ext4 dev: /dev/sda2
    label: N/A uuid: 2c6dd6cd-0652-407b-a5ad-bca998619889
  ID-2: /boot/efi size: 299.4 MiB used: 300 KiB (0.1%) fs: vfat
    dev: /dev/sda1 label: NO_LABEL uuid: D685-454B
Swap:
  ID-1: swap-1 type: partition size: 16.92 GiB used: 5.45 GiB (32.2%)
    priority: -2 dev: /dev/sda3 label: swap
    uuid: 9bf47d72-3a49-42a5-b9b2-f3d0841ee34e
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-7:2 info: Intel Bluetooth wireless interface type: Bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 8087:0a2b class-ID: e001
  Device-2: 1-8:3 info: Chicony Integrated Camera type: Video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 04f2:b5ce class-ID: 0e02
  Device-3: 1-9:11 info: Validity Sensors type: <vendor specific>
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 138a:0097 class-ID: ff00 serial: <filter>
  Device-4: 1-10:5 info: Wacom Pen and multitouch sensor type: HID
    driver: usbhid,wacom interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 400mA
    chip-ID: 056a:5087 class-ID: 0300
  Hub-2: 2-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 43.0 C pch: 40.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 65535 fan-1: 0
Info:
  Processes: 212 Uptime: 3d 21h 6m wakeups: 11 Init: systemd v: 251
  default: graphical Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 1551
  pm: pacman pkgs: 1535 pm: flatpak pkgs: 9 pm: snap pkgs: 7 Shell: Zsh
  v: 5.9 default: Bash v: 5.1.16 running-in: yakuake inxi: 3.3.21
2

hybrid sleep is a variation where the system is put to sleep then after a period it is hibernated.

On critical level you don’t want to hybrid - you want to hibernate or shutdown.

And it requires swapspace the size of your system RAM + GPU RAM if applicable.

3

Apparently not. Quoting from ArchWiki:

[Hybrid suspend] saves the machine’s state into swap space, but does not power off the machine. Instead, it invokes usual suspend to RAM. Therefore, if the battery is not depleted, the system can resume from RAM.

Well if the option to sleep is available on critical level, then I don’t see why the option to hybrid sleep shouldn’t.

Sure, and I must have it because I do have the option to hybrid sleep or to hibernate under the usual power settings. In the critical level setting though, hybrid sleep alone is missing, and that’s my concern.

4

Choice of words - then end result the same - fast resume if not hibernated.

One can ponder over many things and wonder why it is not done the way one expect.

In the endless possibilites in system components and system configuration yours may be the one which may not have the exact specification to make it possible - who know?

I know the perfect power save option is summarized in these two words entered in a terminal

systemctl poweroff
5

Sure, that is a possibility, and of course — like some Linux enthusiasts — I’m just curious what that component/spec might be. Hence the post.

But then, when you’d said,

On critical level you don’t want to hybrid - you want to hibernate or shutdown.

to me it sounded like you went too far in assuming what a user would want. A user can certainly want to hybrid sleep on critical battery level. :smiley:

Now I get it. When you’d said,

hybrid sleep is a variation where the system is put to sleep then after a period it is hibernated.

I assumed that you meant “it is hibernated automatically.” My bad.