- This topic has 11 replies, 5 voices, and was last updated Oct 9-4:46 pm by magnet helper.
-
Posts
-
magnet helper
when i tell the machine to suspend, either from terminal or the exit session gui button, it appears to go to sleep but will not wake back up. mouse or keyboard inputs don’t do anything. pressing the power button seems to make the CPU fan come back on, and the USB keyboard’s caps lock/num lock buttons respond, but no other signs of life. i end up having to hold the power button and force shutdown.
pm-is-supported –suspend && echo $? returns 0output of inxi -Faz
sorry if this is overlongSystem: Kernel: 6.1.105-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.105-antix.1-amd64-smp root=UUID=d4a25448-945d-4a8a-9ec1-72775d63f150 ro quiet selinux=0 Desktop: IceWM v: 3.9.0 tools: avail: slock,xlock dm: slimski v: 1.5.0 Distro: antiX-23.2-runit_x64-full Arditi del Popolo 5 October 2024 base: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop System: Apple product: iMac11,2 v: 1.0 serial: <superuser required> Chassis: type: 13 v: Mac-F2238AC8 serial: <superuser required> Mobo: Apple model: Mac-F2238AC8 serial: <superuser required> uuid: <superuser required> UEFI: Apple v: 99.0.0.0.0 date: 06/13/2019 CPU: Info: model: Intel Core i3 540 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 5 microcode: 0x7 Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB Speed (MHz): avg: 1197 min/max: 1197/3059 scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1197 2: 1197 3: 1197 4: 1197 bogomips: 24473 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: reg_file_data_sampling status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] vendor: Apple driver: radeon v: kernel alternate: amdgpu arch: TeraScale code: R6xx/RV6xx/RV7xx process: TSMC 55-65nm built: 2005-13 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:9488 class-ID: 0300 Device-2: Apple Built-in iSight driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.1:3 chip-ID: 05ac:8502 class-ID: 0e02 serial: <filter> Display: server: X.Org v: 1.21.1.7 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: eDP-1 mapped: eDP model: Apple Color LCD built: 2010 res: 1920x1080 hz: 60 dpi: 103 gamma: 1.2 size: 475x267mm (18.7x10.51") diag: 545mm (21.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480 API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1 drv: swrast gbm: egl: 1.4 drv: kms_swrast surfaceless: drv: r600 x11: drv: r600 inactive: wayland API: OpenGL v: 3.3 compat-v: 3.0 vendor: x.org mesa v: 22.3.6 glx-v: 1.4 es-v: 3.0 direct-render: yes renderer: AMD RV730 (DRM 2.50.0 / 6.1.105-antix.1-amd64-smp LLVM 15.0.6) device-ID: 1002:9488 memory: 250 MiB unified: no Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403 Device-2: Advanced Micro Devices [AMD/ATI] RV710/730 HDMI Audio [Radeon HD 4000 series] vendor: Apple driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aa38 class-ID: 0403 API: ALSA v: k6.1.105-antix.1-amd64-smp status: kernel-api with: apulse type: pulse-emulator tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Broadcom NetXtreme BCM5764M Gigabit Ethernet PCIe driver: tg3 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 14e4:1684 class-ID: 0200 IF: eth0 state: down mac: <filter> Device-2: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Apple AirPort Extreme driver: ath9k v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 168c:002a class-ID: 0280 IF: wlan0 state: up mac: <filter> Info: services: mld,wpa_supplicant Bluetooth: Device-1: Apple Built-in Bluetooth 2.0+EDR HCI driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.1.1:6 chip-ID: 05ac:8215 class-ID: fe01 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: warning rfk-block: hardware: no software: no address: <filter> Info: acl-mtu: 1021:5 sco-mtu: 64:1 link-policy: rswitch hold sniff park link-mode: peripheral accept Drives: Local Storage: total: 931.51 GiB used: 42.54 GiB (4.6%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s tech: SSD serial: <filter> fw-rev: 033 scheme: GPT Partition: ID-1: / raw-size: 46.56 GiB size: 45.53 GiB (97.78%) used: 5.77 GiB (12.7%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 ID-3: /home raw-size: 860.7 GiB size: 846.11 GiB (98.31%) used: 36.78 GiB (4.3%) fs: ext4 dev: /dev/sda3 maj-min: 8:3 Swap: Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100) zswap: no ID-1: swap-1 type: partition size: 24 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4 maj-min: 8:4 Sensors: System Temperatures: cpu: 21.0 C mobo: N/A Fan Speeds (rpm): cpu: 1198 Info: Memory: total: 16 GiB available: 15.61 GiB used: 547.5 MiB (3.4%) Processes: 157 Power: uptime: 1m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.22 GiB Init: runit v: N/A runlevel: 2 tool: service Packages: pm: dpkg pkgs: 1835 libs: 891 tools: apt,apt-get,aptitude,synaptic Compilers: gcc: 12.2.0 Shell: Bash v: 5.2.15 running-in: roxterm inxi: 3.3.36thanks, all
Robin
Smells like a Graphics driver issue with wakeup. I’ve seen this on old proprietary nvidia drivers also (in antiX 17 long ago), and it was finally fixed by the recent open source Nouveau replacement for these.
Since, according to your inxi report, your Apple driver is actually for AMD, maybe this could help to check for the reasons:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.pyRunning this AMD script should perform an in-depth diagnosis and inspection of all what is needed for successfully suspend and resume on machines with AMD graphics, and tell you what’s wrong.
Windows is like a submarine. Open a window and serious problems will start.
that didn’t work.
$ pipx run amd-s2idle Fatal error from pip prevented installation. Full pip output in file: /home/mgnthlpr/.local/pipx/logs/cmd_2025-10-05_19.59.43_pip_errors.log Some possibly relevant errors from pip install: ERROR: Could not find a version that satisfies the requirement amd-s2idle (from versions: none) ERROR: No matching distribution found for amd-s2idle Error installing amd-s2idle.contents of error .log file:
PIP STDOUT ---------- PIP STDERR ---------- ERROR: Could not find a version that satisfies the requirement amd-s2idle (from versions: none) ERROR: No matching distribution found for amd-s2idle- This reply was modified 11 months, 3 weeks ago by magnet helper.
did i use that script incorrectly? does anyone have other suggestions? the boot time is very fast but i would still like to be able to suspend the machine.
Sorry, I’m not sure what this pipx you have used is about, in antiX python scripts are usually called simply by preceding the scriptname by “python3” in the command line. But the diagnostic script itself contains a reference to “pipx”, so you most likely did everything fine. Merely looks like this “pipx” doesn’t know anything about antiX…
Best advice I can give you is: Create an issue to the authors of this script (which is AMD itself, it’s part of their debug tools set) :
https://gitlab.freedesktop.org/drm/amd/-/issuesAsk them how to run their script for diagnostics on your device.
———————
Additionally, if needed: Full amd debug tool set, at kernel.org: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/amd-debug-tools.git/Windows is like a submarine. Open a window and serious problems will start.
i tried it again and must have done something differently. i was able to enter amd-s2idle test in the command line and this was the output:
💻 Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz (family 6 model 25) 💻 Apple Inc. iMac11,2 (iMac) 🐧 Debian GNU/Linux 12 (bookworm) 🐧 Kernel 6.6.87-antix.1-amd64-smp ❌ ACPI FADT doesn't support Low-power S0 idle 🚦 Logs are provided via dmesg, timestamps may not be accurate over multiple cycles ✅ LPS0 _DSM enabled ✅ WLAN driver <code>ath9k</code> bound to 0000:03:00.0 🚫 Your system does not meet s2idle prerequisites! 🗣️ Explanations for your system 🚦 The kernel didn't emit a message that low power idle was supported Low power idle is a bit documented in the FADT to indicate that low power idle is supported. Only newer kernels support emitting this message, so if you run on an older kernel you may get a false negative. When launched as root this script will try to directly introspect the ACPI tables to confirm this. Report written to amd-s2idle-report-2025-10-08.html To display report automatically in browser launch tool with '-E' argument (Example: sudo -E /home/riley/.local/bin/amd-s2idle)where should i go from here? is there a setting i can change?
edit: tried to attach report, but it wouldn’t let me upload an html. will try a .txt next
- This reply was modified 11 months, 3 weeks ago by magnet helper.
- This reply was modified 11 months, 3 weeks ago by magnet helper.
okay, attached the log. will also paste in code tags:
s2idle report created on 2025-10-08 22:18:00.456693 using amd-s2idle 0.2.8 ⚓ Prerequisite checks Measured 2025-10-08 22:18:00. 💻 Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz (family 6 model 25) 💻 Apple Inc. iMac11,2 (iMac) 🐧 Debian GNU/Linux 12 (bookworm) 🐧 Kernel 6.6.87-antix.1-amd64-smp ❌ ACPI FADT doesn't support Low-power S0 idle 🚦 Logs are provided via dmesg, timestamps may not be accurate over multiple cycles ✅ LPS0 _DSM enabled ✅ WLAN driver <code>ath9k</code> bound to 0000:03:00.0 🚫 Your system does not meet s2idle prerequisites! 🦟 Debug Data DMI|value bios_date| 06/13/2019 bios_release| 0.1 bios_vendor| Apple Inc. bios_version| 99.0.0.0.0 board_name| Mac-F2238AC8 board_vendor| Apple Inc. board_version| chassis_type| 13 chassis_vendor| Apple Inc. chassis_version| Mac-F2238AC8 product_sku| product_version| 1.0 PCI Slot | Vendor | Class | ID | ACPI path │ 0000:00:00.0 | Intel Corporation | Host bridge | 8086:0040 | \_SB_.PCI0.MCHC │ 0000:00:01.0 | Intel Corporation | PCI bridge | 8086:0041 | \_SB_.PCI0.P0P2 ├─ 0000:01:00.0 | Advanced Micro Devices, Inc. [AMD/ATI] | VGA compatible controller | 1002:9488 | \_SB_.PCI0.P0P2.GFX0 ├─ 0000:01:00.1 | Advanced Micro Devices, Inc. [AMD/ATI] | Audio device | 1002:aa38 | \_SB_.PCI0.P0P2.HDAU │ 0000:00:1a.0 | Intel Corporation | USB controller | 8086:3b3b | \_SB_.PCI0.UHC5 │ 0000:00:1a.7 | Intel Corporation | USB controller | 8086:3b3c | \_SB_.PCI0.EHC2 │ 0000:00:1b.0 | Intel Corporation | Audio device | 8086:3b56 | \_SB_.PCI0.HDEF │ 0000:00:1c.0 | Intel Corporation | PCI bridge | 8086:3b42 | \_SB_.PCI0.RP01 ├─ 0000:02:00.0 | Broadcom Inc. and subsidiaries | Ethernet controller | 14e4:1684 | \_SB_.PCI0.RP01.GIGE │ 0000:00:1c.1 | Intel Corporation | PCI bridge | 8086:3b44 | \_SB_.PCI0.RP02 ├─ 0000:03:00.0 | Qualcomm Atheros | Network controller | 168c:002a | \_SB_.PCI0.RP02.ARPT │ 0000:00:1c.2 | Intel Corporation | PCI bridge | 8086:3b46 | \_SB_.PCI0.RP03 ├─ 0000:04:00.0 | Texas Instruments | PCI bridge | 104c:823e | \_SB_.PCI0.RP03.FWBR ├─ 0000:05:00.0 | Texas Instruments | FireWire (IEEE 1394) | 104c:823f | \_SB_.PCI0.RP03.FWBR.FRWR │ 0000:00:1d.0 | Intel Corporation | USB controller | 8086:3b36 | \_SB_.PCI0.UHC1 │ 0000:00:1d.7 | Intel Corporation | USB controller | 8086:3b34 | \_SB_.PCI0.EHC1 │ 0000:00:1e.0 | Intel Corporation | PCI bridge | 8086:244e | │ 0000:00:1f.0 | Intel Corporation | ISA bridge | 8086:3b02 | \_SB_.PCI0.LPCB │ 0000:00:1f.2 | Intel Corporation | SATA controller | 8086:3b22 | \_SB_.PCI0.SATA │ 0000:00:1f.3 | Intel Corporation | SMBus | 8086:3b30 | \_SB_.PCI0.SBUS │ 0000:00:1f.6 | Intel Corporation | Signal processing controller | 8086:3b32 | │ 0000:ff:00.0 | Intel Corporation | Host bridge | 8086:2c61 | │ 0000:ff:00.1 | Intel Corporation | Host bridge | 8086:2d01 | \_SB_.CPBG.IMCH │ 0000:ff:02.0 | Intel Corporation | Host bridge | 8086:2d10 | │ 0000:ff:02.1 | Intel Corporation | Host bridge | 8086:2d11 | │ 0000:ff:02.2 | Intel Corporation | Host bridge | 8086:2d12 | └─0000:ff:02.3 | Intel Corporation | Host bridge | 8086:2d13 | EDID for card0-eDP-1: │ Block 0, Base EDID: │ EDID Structure Version & Revision: 1.4 │ Vendor & Product Identification: │ Manufacturer: APP │ Model: 40157 │ Made in: week 10 of 2010 │ Basic Display Parameters & Features: │ Digital display │ Bits per primary color channel: 8 │ DisplayPort interface │ Maximum image size: 48 cm x 27 cm │ Gamma: 2.20 │ DPMS levels: Off │ Supported color formats: RGB 4:4:4 │ First detailed timing includes the native pixel format and preferred refresh rate │ Color Characteristics: │ Red : 0.6533, 0.3339 │ Green: 0.2998, 0.6201 │ Blue : 0.1464, 0.0498 │ White: 0.3125, 0.3291 │ Established Timings I & II: none │ Standard Timings: none │ Detailed Timing Descriptors: │ DTD 1: 1920x1080 59.933878 Hz 16:9 66.587 kHz 138.500000 MHz (475 mm x 267 mm) │ Hfront 48 Hsync 32 Hback 80 Hpol P │ Vfront 3 Vsync 5 Vback 23 Vpol N │ Display Product Name: 'Color LCD' │ Checksum: 0x55 │ ---------------- └─ EDID conformity: PASS ACPI C-state information │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/s2idle/time: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/s2idle/usage: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/disable: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/above: 524625 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/time: 1195105215 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/rejected: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/power: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/residency: 80 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/latency: 20 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/usage: 2647796 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/desc: MWAIT 0x10 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/below: 641502 │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/default_status: enabled │ /sys/bus/cpu/devices/cpu0/cpuidle/state3/name: C3 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/s2idle/time: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/s2idle/usage: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/disable: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/above: 139417 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/time: 49095243 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/rejected: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/power: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/residency: 6 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/latency: 3 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/usage: 957981 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/desc: MWAIT 0x00 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/below: 337506 │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/default_status: enabled │ /sys/bus/cpu/devices/cpu0/cpuidle/state1/name: C1 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/s2idle/time: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/s2idle/usage: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/disable: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/above: 3924631 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/time: 11084342254 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/rejected: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/power: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/residency: 800 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/latency: 200 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/usage: 7161917 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/desc: MWAIT 0x20 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/below: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/default_status: enabled │ /sys/bus/cpu/devices/cpu0/cpuidle/state4/name: C6 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/s2idle/time: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/s2idle/usage: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/disable: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/above: 173088 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/time: 201290732 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/rejected: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/power: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/residency: 20 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/latency: 10 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/usage: 2560789 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/desc: MWAIT 0x01 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/below: 316731 │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/default_status: enabled │ /sys/bus/cpu/devices/cpu0/cpuidle/state2/name: C1E │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/disable: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/above: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/time: 5392570 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/rejected: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/power: 4294967295 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/residency: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/latency: 0 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/usage: 782428 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/desc: CPUIDLE CORE POLL IDLE │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/below: 240326 │ /sys/bus/cpu/devices/cpu0/cpuidle/state0/default_status: enabled └─/sys/bus/cpu/devices/cpu0/cpuidle/state0/name: POLL Fetching low power idle bit directly from FADT ACPI name | ACPI path | Kernel driver LNXSYSTM:00 | \ | None LNXCPU:00 | \_PR_.CPU0 | processor LNXCPU:01 | \_PR_.CPU1 | processor LNXCPU:02 | \_PR_.CPU2 | processor LNXCPU:03 | \_PR_.CPU3 | processor LNXCPU:04 | \_PR_.CPU4 | None LNXCPU:05 | \_PR_.CPU5 | None LNXCPU:06 | \_PR_.CPU6 | None LNXCPU:07 | \_PR_.CPU7 | None LNXSYBUS:00 | \_SB_ | None APP0002:00 | \_SB_.PNLF | None PNP0A03:00 | \_SB_.CPBG | None device:2c | \_SB_.CPBG.IMCH | None PNP0A08:00 | \_SB_.PCI0 | None PNP0C02:02 | \_SB_.PCI0.PDRC | system device:00 | \_SB_.PCI0.MCHC | None device:01 | \_SB_.PCI0.P0P2 | pcieport LNXVIDEO:00 | \_SB_.PCI0.P0P2.GFX0 | radeon device:02 | \_SB_.PCI0.P0P2.GFX0.LCD_ | None device:03 | \_SB_.PCI0.P0P2.HDAU | snd_hda_intel device:04 | \_SB_.PCI0.SATA | ahci device:05 | \_SB_.PCI0.SATA.PRT0 | None device:06 | \_SB_.PCI0.SATA.PRT1 | None device:07 | \_SB_.PCI0.SBUS | i801_smbus SMBUS:00 | \_SB_.PCI0.SBUS.BUS0 | None MIKEY:00 | \_SB_.PCI0.SBUS.BUS0.MKY0 | None SMBUS:01 | \_SB_.PCI0.SBUS.BUS1 | None device:08 | \_SB_.PCI0.LPCB | lpc_ich APP0001:00 | \_SB_.PCI0.LPCB.SMC_ | None INT0800:00 | \_SB_.PCI0.LPCB.FWHD | None PNP0000:00 | \_SB_.PCI0.LPCB.IPIC | None PNP0100:00 | \_SB_.PCI0.LPCB.TIMR | None PNP0103:00 | \_SB_.PCI0.LPCB.HPET | system PNP0200:00 | \_SB_.PCI0.LPCB.DMAC | None PNP0B00:00 | \_SB_.PCI0.LPCB.RTC_ | rtc_cmos PNP0C02:00 | \_SB_.PCI0.LPCB.LDRC | system PNP0C02:01 | \_SB_.PCI0.LPCB.CDRC | system PNP0C04:00 | \_SB_.PCI0.LPCB.MATH | None PNP0C09:00 | \_SB_.PCI0.LPCB.EC__ | None device:09 | \_SB_.PCI0.HDEF | snd_hda_intel device:0a | \_SB_.PCI0.RP01 | pcieport device:0b | \_SB_.PCI0.RP01.GIGE | tg3 device:0c | \_SB_.PCI0.RP02 | pcieport device:0d | \_SB_.PCI0.RP02.ARPT | ath9k device:0e | \_SB_.PCI0.RP03 | pcieport device:0f | \_SB_.PCI0.RP03.FWBR | None device:10 | \_SB_.PCI0.RP03.FWBR.FRWR | firewire_ohci device:11 | \_SB_.PCI0.RP04 | None device:12 | \_SB_.PCI0.RP04.EXCD | None device:13 | \_SB_.PCI0.IO10 | None device:14 | \_SB_.PCI0.IO1X | None device:15 | \_SB_.PCI0.IIO0 | None device:16 | \_SB_.PCI0.IIOX | None device:17 | \_SB_.PCI0.UHC1 | None device:18 | \_SB_.PCI0.UHC2 | None device:19 | \_SB_.PCI0.UHC3 | None device:1a | \_SB_.PCI0.UHC4 | None device:1b | \_SB_.PCI0.UHC5 | None device:1c | \_SB_.PCI0.UHC6 | None device:1d | \_SB_.PCI0.UHC7 | None device:1e | \_SB_.PCI0.EHC1 | ehci-pci device:1f | \_SB_.PCI0.EHC1.HUBN | usb device:20 | \_SB_.PCI0.EHC1.HUBN.PRTN | None device:21 | \_SB_.PCI0.EHC1.HUBN.PRTN.PRT1 | None device:22 | \_SB_.PCI0.EHC1.HUBN.PRTN.PRT2 | None device:23 | \_SB_.PCI0.EHC1.HUBN.PRTN.PRT3 | None device:24 | \_SB_.PCI0.EHC1.HUBN.PRTN.PRT4 | None device:25 | \_SB_.PCI0.EHC2 | ehci-pci device:26 | \_SB_.PCI0.EHC2.HUBN | usb device:27 | \_SB_.PCI0.EHC2.HUBN.PRTN | None device:28 | \_SB_.PCI0.EHC2.HUBN.PRTN.PRT1 | None device:29 | \_SB_.PCI0.EHC2.HUBN.PRTN.PRT2 | None device:2a | \_SB_.PCI0.EHC2.HUBN.PRTN.PRT3 | None device:2b | \_SB_.PCI0.EHC2.HUBN.PRTN.PRT4 | None PNP0C0C:00 | \_SB_.PWRB | None PNP0C0E:00 | \_SB_.SLPB | None PNP0C0F:00 | \_SB_.LNKA | None PNP0C0F:01 | \_SB_.LNKB | None PNP0C0F:02 | \_SB_.LNKC | None PNP0C0F:03 | \_SB_.LNKD | None PNP0C0F:04 | \_SB_.LNKE | None PNP0C0F:05 | \_SB_.LNKF | None PNP0C0F:06 | \_SB_.LNKG | None PNP0C0F:07 | \_SB_.LNKH | None LNXSYBUS:01 | \_TZ_ | None Device firmware checks unavailable without gobject introspection Summary No sleep cycles found in the database.
sybok
You can try newer kernels (newer/different drivers); either those of antiX (there’s newer kernel in the 6.1 series, then there’s 6.6) or Debian.
Summary
No sleep cycles found in the database.Seems like the tests have not run through completely and this causes possibly a false result:
Device firmware checks unavailable without gobject introspection
Have you tried to add this “gobject introspection” to your system to complete the test?
$ apt-cache policy gobject-introspection python3-gi-dbgMaybe installing one of these or both (or even some additional stuff) is needed or expected here.
On the other hand, from the Archwiki:
If your hardware does not advertise the deep sleep status, check first if your UEFI advertises some settings for it, generally under Power or Sleep state or similar wording, with options named Windows 10, Windows and Linux or S3/Modern standby support for S0ix, and Legacy, Linux, Linux S3 or S3 enabled for S3 sleep. Failing that, you can keep using s2idle, consider using hibernation or try to patch the DSDT tables (or find a patched version online).
Note
This last solution is likely going to cause issues. Manufacturers have stopped fixing bugs with the ACPI S3 state since systems shipping with Windows are encouraged to use “Modern standby” by default; if they have voluntarily not advertised it, it is probably broken in some way.Confirm that your hardware does not exhibit issues with S3 sleep by testing a few sleep cycles after changing the sleep method:
# echo deep > /sys/power/mem_sleep
Even when they explicitly mention Windows, something similar might be true for Apple devices… In this case: for modern hardware where S3 is problematic or absent, S0ix (s2idle) is the intended and often the only viable “deep” suspend state you can have.
In this case you can try to change the default:
First, check whether S0ix method is supported by your current kernel:
$ cat /sys/power/mem_sleep s2idle shallow [deep](in the example output from my device it is supported by the kernel, but not set as the default, since my device has proper S3 support)
If you see s2idle being supported, actually change the value:
$ echo s2idle | sudo tee /sys/power/mem_sleepCheck again, the brackets must have moved to s2idle:
$ cat /sys/power/mem_sleep [s2idle] shallow deepThen you can try suspending to this “modern” mode:
$ echo s2idle > /sys/power/stateBut first try to complete the amd debugging procedure, which was aborted when inspecting the firmware, so you have no clean result still.
And then you might want to check your dmesg for any messages related to ACPI, suspend, and resume failures.
Please note:
“s2idle” is not the same as “S0ix”, still it is the way this mode is initialised in Linux. S2idle generally is a generic, software-driven, poor suspend variant in Linux, causing the battery in mobile devices to drain fast due to relatively high power consumption compared with true hardware S3 or s0ix suspend. Still, the kernel may use s2idle as a placeholder for S0ix if the hardware supports it (which has no separate way to command it), and it can also be a shallow suspend if the firmware or drivers don’t fully implement S0ix. On systems where S0ix is truly supported, the kernel places the CPU into deeper idle states during s2idle than on the ones where hardware support is broken. You can only know by analysing the results. See https://docs.anduinos.com/Skills/System-Management/Diagnose-Sleep.html#5-what-if-it-only-shows-s2idle for further details, but please keep in mind that all what is written there about systemd specific methods doesn’t apply to antiX.So additionally try:
$ sudo dmesg | grep -i -E 'acpi|pm|s2idle'
If you see something like “kernel: Low-power S0 idle used by default for system suspend” you actually do use S0ix, while when it reads something like “PM: suspend entry (s2idle)” this points to the software driven suspend.At least, you are not alone with your suspend issues. Some hardware manufacturers have simply neglected supporting Linux : https://unix.stackexchange.com/questions/784449/getting-into-deep-s0ix-modern-standby »So, no sleep on current CPU?« Yes, in these cases you can’t have proper low-power suspend at all in Linux by manufacturers’ decision. In this case: Single chance is complaining on them, nagging them until they change their behaviour on the long run.
Windows is like a submarine. Open a window and serious problems will start.
BobC
Search everywhere for your machine and Linux suspend resume. See if you can find anyone where its working and what kernel they are running or what they did to make it work.
Yes, try different kernel versions.
If no luck there, search around and see if you can find out where the system and suspend/resume log files are and look at them. If there aren’t sufficient clues there, you might also see if there is a way to increase the logging level.
If you have another computer where suspend and resume work, compare the logs from the two machines to find out what step the one that doesn’t work never got to.
Sorry, I don’t have (and won’t buy) any Apple hardware, so can’t do anything to help.
Here is the link to SEARCH THE FORUM >> http://www.antixforum.com/search-forums
abc-nix
Debian kernels and antiX kernels have some differences. The Debian kernel (be it 6.1 from bookworm or 6.12 from bookworm-backports) may have the needed modules for your machine to suspend.
I haven’t tried to help in this topic because I am also having issues with suspending my laptop (completely different hardware, and different kernels don’t help). It would be hypocritical. 😅
I ended up adding a swap partition and I now hibernate the machine when I don’t want to lose my session and progress I have. It isn’t perfect, and takes longer to power down and wake up, but this is the workaround I found. Sorry for the off-topic.
Corruption has two hands: the Right and the Left. Don't let them squeeze you.
i should have noted that after the first post i updated the kernel trying to troubleshoot a separate issue. the subsequent posts reflect this (currently running 6.6.87-antix.1-amd64-smp )
tried adding the gobject-introspection and python3-gi-dbg packages, but the log still ends with “Device firmware checks unavailable without gobject introspection”
cat /sys/power/mem_sleep shows only two options: s2idle and deep (with the latter selected). i did try setting it to s2idle and running the test just in case, but no luck there either.
unless i’m reading it wrong, it sounds like the hardware support is a more modern issue? i’m pretty sure this hardware is at least 13 years old.
i do have a swap partition large enough to properly handle hibernate mode, but the boot time is already so snappy that i don’t think it’s worth pursuing. a lighter sleep mode would be more convenient than a full power down/up, though.
- You must be logged in to reply to this topic.