After a couple of latest updates system refuses to go to sleep and immediately wakes up. Turning on airplane mode fixes issue, but it worked fine before without it. Tried clean install and suspend worked as expected, but after upgrade to latest image and kernel problem returned. How to fix this? Maybe it’s a kernel problem or network-manager?
I looked at the logs and found this message:
NetworkManager: [1679234061.3831] manager: sleep: wake requested (sleeping: yes enabled: yes)
It happens on both: latest f37 and f38.
I’m using silverblue.
I wonder if the solution here may be related to your issue, which seems triggered by NetworkManager
Hi all, I just installed
Portmaster recently and was monitoring my network traffic.
Noticed that NetworkManager from /usr/sbin/NetworkManager makes regular unencrypted requests to fedoraproject.org
Assuming that NetworkManager is https://fedoraproject.org/wiki/Tools/NetworkManager. It does not appear to do any critical functions. I’m on a desktop with a stable connection, so “automatic network detection and configuration” are not needed. Also poked around to see if I could configure it but had…
I tried this now, it didn’t help. Only stopping NetworkManager.service helps or turning on aiplane mode.
I found the ostree commit that caused the issue:
Changes between commits:
amd-gpu-firmware 20230210-147.fc37 → 20230310-148.fc37
intel-gpu-firmware 20230210-147.fc37 → 20230310-148.fc37
iwl100-firmware 220.127.116.11-147.fc37 → 18.104.22.168-148.fc37
iwl1000-firmware 1:22.214.171.124-147.fc37 → 1:126.96.36.199-148.fc37
iwl105-firmware 188.8.131.52-147.fc37 → 184.108.40.206-148.fc37
iwl135-firmware 220.127.116.11-147.fc37 → 18.104.22.168-148.fc37
iwl2000-firmware 22.214.171.124-147.fc37 → 126.96.36.199-148.fc37
iwl2030-firmware 188.8.131.52-147.fc37 → 184.108.40.206-148.fc37
iwl3160-firmware 1:220.127.116.11-147.fc37 → 1:18.104.22.168-148.fc37
iwl3945-firmware 22.214.171.124-147.fc37 → 126.96.36.199-148.fc37
iwl4965-firmware 188.8.131.52-147.fc37 → 184.108.40.206-148.fc37
iwl5000-firmware 220.127.116.11_1-147.fc37 → 18.104.22.168_1-148.fc37
iwl5150-firmware 22.214.171.124-147.fc37 → 126.96.36.199-148.fc37
iwl6000-firmware 188.8.131.52-147.fc37 → 184.108.40.206-148.fc37
iwl6000g2a-firmware 220.127.116.11-147.fc37 → 18.104.22.168-148.fc37
iwl6000g2b-firmware 22.214.171.124-147.fc37 → 126.96.36.199-148.fc37
iwl6050-firmware 188.8.131.52-147.fc37 → 184.108.40.206-148.fc37
iwl7260-firmware 1:220.127.116.11-147.fc37 → 1:18.104.22.168-148.fc37
iwlax2xx-firmware 20230210-147.fc37 → 20230310-148.fc37
libertas-usb8388-firmware 2:20230210-147.fc37 → 2:20230310-148.fc37
linux-firmware 20230210-147.fc37 → 20230310-148.fc37
linux-firmware-whence 20230210-147.fc37 → 20230310-148.fc37
nvidia-gpu-firmware 20230210-147.fc37 → 20230310-148.fc37
webp-pixbuf-loader 0.2.1-1.fc37 → 0.2.2-1.fc37
Similar problem here. Suspend only works in Airplane mode. F38.
It’s a bug with wifi driver. I’ve reported it upstream. Must be fixed in next linux-firmware update.
Exactly same issue here，suspend only works properly when airplane mode is on
The simplest workaround until bug is fixed is to create systemd service that disabling module on suspend and enabling it on wakeup.
Create file /etc/systemd/system/root-suspend-fix.service:
Description=Suspend fix for ath11k_pci
ExecStart=-modprobe -r ath11k_pci
sudo systemctl enable --now root-suspend-fix.service