Cat /proc/acpi/wakeup system suspend instant wake

I have read all the threads on this subject but i have an odd entry in my ❱cat /proc/acpi/wakeup that im not sure how to deal with?

inxi
❱inxi --admin --verbosity=7 --filter --no-host
System:
  Kernel: 6.4.16-5-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4-x86_64
    root=UUID=bf297078-1dd9-4d39-b246-b500233c73bb rw quiet splash
    resume=UUID=fb0af894-f621-4b37-b39c-7b067e2f8904 udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: Dell product: OptiPlex 7050 v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Dell model: 055H3G v: A01 serial: <superuser required> UEFI: Dell
    v: 1.26.0 date: 08/20/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.49 GiB used: 3.73 GiB (24.1%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: model: Intel Core i5-7500 bits: 64 type: MCP arch: Kaby Lake
    gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF4
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 900 min/max: 800/3800 scaling: driver: intel_pstate
    governor: powersave cores: 1: 900 2: 900 3: 900 4: 900 bogomips: 27208
  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 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
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, STIBP: disabled,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1
    empty: DP-1, DP-2, DP-3, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0
    chip-ID: 8086:5912 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :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: HDMI-A-1 mapped: HDMI-1 model: VA24D serial: <filter>
    built: 2022 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.1.9-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
    device-ID: 8086:5912 memory: 15.12 GiB unified: yes
  API: Vulkan v: 1.3.264 layers: 1 device: 0 type: integrated-gpu name: Intel
    HD Graphics 630 (KBL GT2) driver: mesa intel v: 23.1.9-manjaro1.1
    device-ID: 8086:5912 surfaces: xcb,xlib
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a2f0
    class-ID: 0403
  API: ALSA v: k6.4.16-5-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 0.3.81 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-4: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15e3 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd
    class-ID: 0280
  IF: wlp2s0 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 driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:4 chip-ID: 8087:0a2b
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 7c0104
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.84 TiB used: 47.03 GiB (2.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Toshiba model: KXG50ZNV1T02
    NVMe 1024GB size: 953.87 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: AADA4101
    temp: 41.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 944.77 GiB size: 928.86 GiB (98.32%)
    used: 47.03 GiB (5.1%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: bf297078-1dd9-4d39-b246-b500233c73bb
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: B79E-8ADE
  ID-3: /mnt/TRUENAS-cavern raw-size: N/A size: 5.79 TiB
    used: 242.42 GiB (4.1%) fs: cifs dev: /dev/cavern
  ID-4: /mnt/TRUENAS-home raw-size: N/A size: 5.58 TiB
    used: 24.79 GiB (0.4%) fs: cifs dev: /dev/home
  ID-5: /mnt/TRUENAS-manjaro-home raw-size: N/A size: 5.72 TiB
    used: 174.83 GiB (3.0%) fs: cifs dev: /dev/manjaro-home
  ID-6: /mnt/TRUENAS-media raw-size: N/A size: 5.88 TiB
    used: 330.67 GiB (5.5%) fs: cifs dev: /dev/media
  ID-7: /mnt/ssd raw-size: 931.51 GiB size: 915.82 GiB (98.31%)
    used: 2 MiB (0.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: secondary
    uuid: 8eb90896-961b-47fc-a8c5-4b5ce1d3db5f
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: fb0af894-f621-4b37-b39c-7b067e2f8904
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-3:2 info: SINO WEALTH USB KEYBOARD type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 258a:0135 class-ID: 0300
  Device-2: 1-7:3 info: Integrated Express HTX HID Device
    type: keyboard,mouse driver: hid-generic,hid-multitouch,usbhid interfaces: 2
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 048d:8911 class-ID: 0301 serial: <filter>
  Device-3: 1-9:4 info: Intel Bluetooth wireless interface type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 8087:0a2b class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 196 Uptime: 43m wakeups: 10 Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1375 libs: 399 tools: pamac,yay pm: flatpak
  pkgs: 0 Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: yakuake
  inxi: 3.3.30

My system is doing the “imidiate wake on suspend” thing. Iv been tinkering. I already have a script from another system i have that does somthing very simmalar.

The thing iv got a problem with is the ❱cat /proc/acpi/wakeup

⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ /home/greg ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼
❱cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
PEG0      S4    *disabled
PEGP      S4    *disabled
PEG1      S4    *disabled
PEGP      S4    *disabled
PEG2      S4    *disabled
PEGP      S4    *disabled
RP09      S4    *disabled
PXSX      S4    *disabled
RP10      S4    *disabled
PXSX      S4    *disabled
RP11      S4    *disabled
PXSX      S4    *disabled
RP12      S4    *disabled
PXSX      S4    *disabled
RP13      S4    *disabled
PXSX      S4    *disabled
RP01      S4    *disabled
PXSX      S4    *disabled
RP02      S4    *disabled
PXSX      S4    *disabled
RP03      S4    *disabled
PXSX      S4    *disabled
RP04      S4    *disabled
PXSX      S4    *disabled
RP05      S4    *disabled
PXSX      S4    *disabled
RP06      S4    *disabled
PXSX      S4    *disabled
RP07      S4    *disabled
PXSX      S4    *disabled
RP08      S4    *disabled  pci:0000:00:1c.0
PXSX      S4    *disabled  pci:0000:02:00.0
RP17      S4    *disabled  pci:0000:00:1b.0
PXSX      S4    *disabled  pci:0000:01:00.0
RP18      S4    *disabled
PXSX      S4    *disabled
RP19      S4    *disabled
PXSX      S4    *disabled
RP20      S4    *disabled
PXSX      S4    *disabled
RP21      S4    *disabled
PXSX      S4    *disabled
RP22      S4    *disabled
PXSX      S4    *disabled
RP23      S4    *disabled
PXSX      S4    *disabled
RP24      S4    *disabled
PXSX      S4    *disabled
RP14      S4    *disabled
PXSX      S4    *disabled
RP15      S4    *disabled
PXSX      S4    *disabled
RP16      S4    *disabled
PXSX      S4    *disabled
PS2K      S3    *disabled  pnp:00:02
                *enabled   serio:serio0
PS2M      S3    *disabled  pnp:00:03
GLAN      S4    *enabled   pci:0000:00:1f.6
XHC       S0    *enabled   pci:0000:00:14.0
XDCI      S4    *disabled
HDAS      S4    *disabled  pci:0000:00:1f.3

What is this "blank" "blank" *enabled serio:serio0 entry at the bottom that is *enabled?

How do disable it since it has no name? What is it?
The system start out after boot with this entry disabled but after a sleep cycle it is enabled again. Im not 100% sure it is the cause but iv disabled everything that i can and still be able to wake the system via keyboard. These are the last 3 things im left with.

❱cat /proc/acpi/wakeup | grep -i enabl
                *enabled   serio:serio0
GLAN      S4    *enabled   pci:0000:00:1f.6
XHC       S0    *enabled   pci:0000:00:14.0

It’s something to do with serial i/o. Do you have some kind of serial input device attached?

https://wiki.archlinux.org/title/Serial_input_device_to_kernel_input

Nop, all iv got is USB trackpad and KB. It has wifi & BT on an M.2. A M.2 NVME ssd & a SATA ssd

Cant think of anything else, Certainly nothing else plugged into it from the outside so to speak.

❱lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem
00:15.0 Signal processing controller: Intel Corporation 200 Series PCH Serial IO I2C Controller #0
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:16.3 Serial controller: Intel Corporation Device a2bd
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #8 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Q270)
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM
01:00.0 Non-Volatile memory controller: Toshiba Corporation XG5 NVMe SSD Controller
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)

❱lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 048d:8911 Integrated Technology Express, Inc. HTX HID Device
Bus 001 Device 002: ID 258a:0135 SINO WEALTH USB KEYBOARD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Try looking in other wakeup trigger interfaces - Power management/Wakeup triggers - ArchWiki

Maybe /sys/bus/serial/devices/ will contain a device with the power/wakeup file as described there.

/sys/bus/serial/devices/ is empty. I have tried to read the wiki but i dont understand.

⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ /sys/bus/serial/devices ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼
❱exa -aal --icons --group-directories-first --group --header -Um
Permissions Size User Group Date Modified Date Created Name
drwxr-xr-x     - root root  26 Oct 20:28  -             .
drwxr-xr-x     - root root  26 Oct 20:28  -             ..

⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ /sys/bus/serial/devices ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼
❱cd /sys/class/wakeup/

⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ /sys/class/wakeup ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼
❱exa -aal --icons --group-directories-first --group --header -Um
Permissions Size User Group Date Modified Date Created Name
drwxr-xr-x     - root root  26 Oct 20:28  -             .
drwxr-xr-x     - root root  26 Oct 20:28  -             ..
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup0 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/wakeup/wakeup0
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup1 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4c/wakeup/wakeup1
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup2 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:77/wakeup/wakeup2
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup3 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:7a/wakeup/wakeup3
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup4 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:6a/wakeup/wakeup4
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup5 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:32/wakeup/wakeup5
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup6 -> ../../devices/platform/i8042/serio0/wakeup/wakeup6
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup7 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:30/wakeup/wakeup7
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup9 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:48/wakeup/wakeup9
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup10 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/wakeup/wakeup10
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup11 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:69/wakeup/wakeup11
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup12 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4a/wakeup/wakeup12
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup13 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4b/wakeup/wakeup13
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup14 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:32/device:33/wakeup/wakeup14
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup15 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:30/device:31/wakeup/wakeup15
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup16 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/wakeup/wakeup16
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup17 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT3451:00/wakeup/wakeup17
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup18 -> ../../devices/LNXSYSTM:00/LNXPWRBN:00/wakeup/wakeup18
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup19 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/wakeup/wakeup19
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup20 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/wakeup/wakeup20
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup21 -> ../../devices/pnp0/00:06/wakeup/wakeup21
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup22 -> ../../devices/pnp0/00:06/rtc/rtc0/alarmtimer.0.auto/wakeup/wakeup22
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup23 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/INT33A1:00/wakeup/wakeup23
lrwxrwxrwx     - root root  26 Oct 20:28  -             wakeup24 -> ../../devices/pci0000:00/0000:00:14.0/wakeup/wakeup24
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup25 -> ../../devices/LNXSYSTM:00/PNP0C14:00/wakeup/wakeup25
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup26 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C14:01/wakeup/wakeup26
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup27 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C14:02/wakeup/wakeup27
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup29 -> ../../devices/pci0000:00/0000:00:1f.6/wakeup/wakeup29
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup30 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-3/wakeup/wakeup30
lrwxrwxrwx     - root root  27 Oct 10:01  -             wakeup31 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-7/wakeup/wakeup31

I just wanted to know how to disable that entry that has no name in the /proc/acpi/wakeup?

what is iv - if it is a self invented abbreviation - please don’t do that - it disturbs the meaning completely

A sincere effort to use modest and proper language and grammar is a sign of respect toward the community that will certainly be appreciated and is quite likely to elicit positive responses. Please refrain from using so-called “textspeak”, “netspeak”, “leetspeak” and all other forms of internet slang.
Forum Rules - Manjaro

ehh? iv , sorry dyslexic from birth, if it was not for the 3 spell-checkers i have running continually you would not be able to read anything i wrote.

is it supposed to be i’v ? your complaining because of a missed hyphen? (if thats what its called).

1 Like

How about NOT shaming people for a disability?

I also saw that and my IMMEDIATE reaction was internally giggling because I recognized it from doing exactly the same with my dyslexia.

There is a good motto to follow, even Ted Lasso used it.
“Don’t be judgmental, be curious and ask questions”.

1 Like

Where do you get that from?

Please read the comments in correct order …

@jackdinn
I asked because I didn’t understand the phrase - I am not native english speaking - but a native dane.

The correct language would be I have but when spoken it is often pronouced I’ve

And no I am not displeased - I have been around so long that I have seen a lot of self-invented abbreviations - most often called text speak - inherited from sms.

And I did see all the other times - there is not any need to quote them all - one is enough

1 Like

I was giggling because for some reason the first 2 or 3 times I wrote “iv” he didn’t mind, but the 4th time I used it, it offended him ^^
(I even spent the extra time to put the correct comma’s and capitals in this comment. Hope it pleases :slight_smile: )

Don’t worry about it, I am impossible to offend. I am also likely older than you and “text speak” is the absolute last thing id (opps sorry, I would) ever use because I hate it too. In this case, it’s just my bad spelling.

Device-2: 1-7:3 info: Integrated Express HTX HID Device
    type: keyboard,mouse driver: hid-generic,hid-multitouch,usbhid interfaces: 2
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 048d:8911 class-ID: 0301 serial: <filter>

What is this device? Some kind of touchpad? Does your problem go away if you unplug it?

It doesn’t have a sysfs id there for whatever reason so you can’t disable it through /proc/acpi/wakeup.

This seems to be the source of the serio wakeup;

wakeup6 -> ../../devices/platform/i8042/serio0/wakeup/wakeup6

so there should be a file /sys/devices/platform/i8042/serio0/power/wakeup. You can disable it using that file as described in the Arch Wiki article;

echo "disabled" > /sys/devices/platform/i8042/serio0/power/wakeup

Yea its a USB touchpad, it does not cure the problem when i unplug it.

However,
❱su -c 'echo "disabled" > /sys/devices/platform/i8042/serio0/power/wakeup'
works, the device is gone now.

❱cat /proc/acpi/wakeup | grep -i enabl
GLAN      S4    *enabled   pci:0000:00:1f.6
XHC       S0    *enabled   pci:0000:00:14.0

Also, I can probably disable the touchpad and just leave the keyboard via one of these

❱grep . /sys/bus/usb/devices/*/power/wakeup | grep enabled
/sys/bus/usb/devices/1-3/power/wakeup:enabled
/sys/bus/usb/devices/1-7/power/wakeup:enabled

It seems that it has now become an intermittent fault, sometimes it works others not, so it’ll take a little while to be sure. I should be able to figure it now though.

Thx all.

Is it a serial port that is missing a driver to be recognised as COM1 ?

00:16.3 Serial controller: Intel Corporation Device a2bd

Device can be found on many systems (288) using Vendor ID for Intel (8086) and Product ID (a2bd)
linux-hardware.org - pci:8086-a2bd - Device ‘Intel 200 Series Chipset Family KT Redirection’
None of the systems have a driver for a serial port

I suggest check motherboard BIOS settings to see if there is a serial port that can be disabled

I think that device might be something to do with Intel ME/AMT, but I’m not an Intel user so don’t know much about that stuff. KT means Keyboard and Text, so KT Redirection = something to do with remote management?

Hardware scan for Optiplex 7050 shows serial driver loaded for this device

https://linux-hardware.org/?probe=a35a9d7d8a&log=lspci_all

00:16.3 Serial controller [0700]: Intel Corporation Device [8086:a2bd] (prog-if 02 [16550])
Subsystem: Dell Device [1028:07a1]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin D routed to IRQ 20
Region 0: I/O ports at f0a0 [size=8]
Region 1: Memory at ef14d000 (32-bit, non-prefetchable) [size=4K]
Capabilities:
Kernel driver in use: serial

p38 of user manual shows that serial port is usually set to COM1 but can be disabled in BIOS
https://dl.dell.com/content/manual65979904-optiplex-7050-micro-owner-s-manual.pdf?language=en-us

1 Like

i had a look in the bios but the entry for serial port under system configuration does not exit. (This BIOS is fully updated)

No worries though as i believe i have disabled it when it suspends with su -c 'echo "disabled" > /sys/devices/platform/i8042/serio0/power/wakeup' added to my suspend script.

I am beginning to get the bigger picture now.

You are using a thin client as workstation.

Thin clients is usually parts of a larger corporate network and centrally managed by an IT department.

This requires some capabilities on firmware level.

Thus I would look at disabling wake-on-lan and network boot.

Also disable Intel ME if possible - although it is not possible for all systems - which has raised some concerns over the years - as it could be considered a backdoor into the system in question.

Yep, i am using a micro (thin client) as a workstation.

I have disabled all wake-on-lan and network boot settings already. I even disabled the wake-on-usb, although it still does wake on usb when on linux, not sure about windows.

I have looked into the MEBx briefly but did not want to touch anything as i did not know what i was doing. I assume this Intel ME is in there.

I shall leave it for now, though. As i say, i have been able to disable the entry that i originally was curious about.