Moin,
wenn ich den PC in den Standby setzen will geht er direkt wieder an. Das Netzteil schaltet aus und direkt wieder an.
Hat jemand eine Ahnung woran das liegen könnte?
M$ oder Apple?
Linux?
Garuda?
Poste doch bitte das vom Template geforderte garuda-inxi.
Falls du noch KDE benutzt, kann ich dir mitteilen, dass es hier wunderbar funktioniert, zumindest wenn ich den Notebookdeckel schließe.
Wie machst du es?
System:
Kernel: 6.10.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=838024dc-651f-4cf8-87bb-7e39cd372180 rw rootflags=subvol=@
quiet loglevel=3 splash ibt=off
Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.5.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B550 AORUS PRO
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: F17 date: 03/22/2024
CPU:
Info: model: AMD Ryzen 5 5600 bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3564 high: 3638 min/max: 2200/4467 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3500 2: 3500
3: 3593 4: 3500 5: 3500 6: 3586 7: 3638 8: 3592 9: 3593 10: 3592 11: 3592
12: 3593 bogomips: 83843
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-2 empty: DP-1, HDMI-A-1, HDMI-A-2, Writeback-1
bus-ID: 09:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: DP-2 res: 2048x1152 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 18.1.8 DRM 3.57 6.10.6-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.1.6-arch1.1
device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.1.6-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.10.6-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.2.3 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: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10.2:7 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 1.36 TiB used: 558.16 GiB (39.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:6 vendor: Gigabyte model: AG450E1TB-G
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: ELFMB0.5 temp: 32.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Kingston model: SNV2S500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: SBI02105 temp: 25.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 215.05 GiB size: 215.05 GiB (100.00%)
used: 33.29 GiB (15.5%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 19 MiB (6.3%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
ID-3: /home raw-size: 215.05 GiB size: 215.05 GiB (100.00%)
used: 33.29 GiB (15.5%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:5
ID-4: /var/log raw-size: 215.05 GiB size: 215.05 GiB (100.00%)
used: 33.29 GiB (15.5%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 215.05 GiB size: 215.05 GiB (100.00%)
used: 33.29 GiB (15.5%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.36 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p4 maj-min: 259:4
Sensors:
System Temperatures: cpu: 33.2 C mobo: N/A gpu: amdgpu temp: 39.0 C
mem: 32.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 4.18 GiB (13.4%)
Processes: 405 Power: uptime: 4m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.48 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 1889 pm: pacman pkgs: 1877 libs: 573 tools: octopi,pamac,paru
pm: flatpak pkgs: 12 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi
default: fish v: 3.7.1 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date: 2024-08-20
Last full system update: 2024-08-27
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
Es funktioniert soweit auch alles 
- Formatieren Sie alle Terminalausgaben (einschließlich
garuda-inxi) als Code-Block, indem Sie auf die Schaltfläche für vorformatierten Text, </>, klicken, oder setzen Sie drei Tilde (~) über und unter den Text.
Antwort? 
Versuch es vom Terminal aus
systemctl suspend
Ich hab es über den Anwendungsstarter gemacht und auch per Terminal. Gleiches Ergebnis. Netzteil schaltet aus und direkt wieder an. Hatte schon die Vermutung im Bios passt was nicht, konnte aber nichts finden…
ich nutze Garuda.
Das hatte ich auch mal, jetzt wo du es sagst.
Ich musste WOL abschalten.
Wake-up after shutdown
It is known that some motherboards are affected by a bug that can cause immediate or random wake-up after a shutdown whenever the BIOS WoL feature is enabled (as discussed in this thread for example).
Fix using BIOS Settings
The following actions in the BIOS preferences can solve this issue with some motherboards:
Disable all references to xHCI in the USB settings (note this will also disable USB 3.0 at boot time)
Disable EuP 2013 if it is explicitly an option
Optionally enable wake-up on keyboard actions
Note: There are mixed opinions as to the value of #3 above and it may be motherboard dependent.
Fix by Kernel quirks
The issue can also be solved by adding the following kernel boot parameter: xhci_hcd.quirks=270336 This activates the following quirks:
XHCI_SPURIOUS_REBOOT
XHCI_SPURIOUS_WAKEUP
Viel Glück.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.