I am currently using Fedora 44 on my 2014 MacBook Pro and anytime my laptop suspends itself, it gets into a unusable state where it is stuck on a black screen and the only way to get out of it is by hard resetting the computer and turning it back on.
I’ve seen that this is a known issue and that people have had different fixes, but none of the fixes that I have tried have seemed to fix the problem.
Below I have linked the two threads that I followed that have given zero results. I have tried both disabling the Thunderbolt service, and disabling the Thunderbolt controller, but both of these have not solved the problem.
I also read in another Fedora discussion thread linked below that apparently it could be an issue with the power profile daemon, but I know recently Fedora switched to tuned, and unless anyone has gotten the problem fixed on their end, I’m not willing to try out that solution, especially considering it’s running off of an outdated version of Fedora, which uses a different power daemon.
I’m hoping to see if there has been any work done to combat this problem or if there are any new fixes for this problem people have figured out.
You should try to get the latest Apple firmware that your system supports as that is what Linux developers are likely to have used.
Old batteries can cause problems with power management.
There is a good chance that your issue is affecting multiple linux distros. If you can find relevant errors in the journals a search may find useful posts from other distros.
Thank you for your reply. I looked over your message and I want to add a few bits of extra information.
1. To my knowledge, I am using the latest version of Apple firmware. I did previously use macOS on it, and it was completely up to date, so I don’t think firmware is the problem.
2. I don’t think it is an issue with my battery, considering on macOS battery life is just fine and on Linux battery life continues to be just fine. Now I don’t have the greatest battery, it is around 80%, but that shouldn’t cause major power management issues.
3. Unfortunately, with information that I’ve looked at and by personal experience, this suspend problem seems to be an issue that is exclusively on Fedora. When I used Debian and Ubuntu, this problem simply didn’t exist. And there are multiple accounts that confirm that this seems to be a Fedora-specific problem.
If it helps, below I linked the logs to my system. Some information may be redacted but all the relevant pieces should be left intact.
Aug 24 17:42:57 HOSTNAME systemd-logind[853]: Lid closed.
Aug 24 17:42:57 HOSTNAME systemd-logind[853]: Suspending…
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: sleep requested
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: state now DISABLED (ASLEEP)
Aug 24 17:42:57 HOSTNAME ModemManager[920]: system is about to suspend
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: device (wlp3s0): activated → deactivating (sleeping)
Aug 24 17:42:57 HOSTNAME ModemManager[920]: ready to sleep; dropping inhibitor
Aug 24 17:42:57 HOSTNAME systemd[1]: Starting NetworkManager-dispatcher.service
Aug 24 17:42:57 HOSTNAME warp-svc[789]: New power state Suspend
Aug 24 17:42:57 HOSTNAME warp-svc[789]: System going to sleep, blocking deployment initiation
Aug 24 17:42:57 HOSTNAME warp-svc[789]: PowerStatusChanged handled
Aug 24 17:42:57 HOSTNAME systemd[1]: Started NetworkManager-dispatcher.service
Aug 24 17:42:57 HOSTNAME audit[1]: SERVICE_START unit=NetworkManager-dispatcher
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: send_event_marker failed
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: CTRL-EVENT-DISCONNECTED bssid=MAC_REDACTED reason=3
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: CTRL-EVENT-DSCP-POLICY clear_all
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: unexpected disconnect event
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: REGDOM-CHANGE WORLD
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: REGDOM-CHANGE COUNTRY US
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: supplicant completed → disconnected
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: deactivating → disconnected (sleeping)
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Withdrawing address IPV6_GLOBAL_REDACTED
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Withdrawing address IPV6_GLOBAL_REDACTED
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Leaving mDNS group IPV6_GLOBAL_REDACTED
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Joining mDNS group IPV6_LL_REDACTED
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: dhcp4 canceled
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Registering IPV6_LL_REDACTED
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: dhcp4 starting transaction
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Withdrawing IPV6_LL_REDACTED
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: dhcp4 no lease
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Leaving mDNS group IPV6_LL_REDACTED
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: dhcp6 canceled
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Interface IPv6 no longer relevant
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: dhcp6 starting transaction
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: dhcp6 no lease
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Withdrawing IPV4_LOCAL_REDACTED
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Leaving mDNS group IPV4_LOCAL_REDACTED
Aug 24 17:42:57 HOSTNAME avahi-daemon[689]: Interface IPv4 no longer relevant
Aug 24 17:42:57 HOSTNAME chronyd[743]: Source IPV4_EXTERNAL_REDACTED offline
Aug 24 17:42:57 HOSTNAME chronyd[743]: Source IPV4_EXTERNAL_REDACTED offline
Aug 24 17:42:57 HOSTNAME chronyd[743]: Source IPV4_EXTERNAL_REDACTED offline
Aug 24 17:42:57 HOSTNAME chronyd[743]: Can’t synchronise: no selectable sources
Aug 24 17:42:57 HOSTNAME chronyd[743]: Source IPV4_EXTERNAL_REDACTED offline
Aug 24 17:42:57 HOSTNAME audit: BPF prog-id=75 op=UNLOAD
Aug 24 17:42:57 HOSTNAME systemd-resolved[524]: reset search domain list
Aug 24 17:42:57 HOSTNAME systemd-resolved[524]: default route setting: no
Aug 24 17:42:57 HOSTNAME systemd-resolved[524]: reset DNS server list
Aug 24 17:42:57 HOSTNAME NetworkManager[949]: disconnected → unmanaged
Aug 24 17:42:57 HOSTNAME geoclue[1894]: WiFi scan failed
Aug 24 17:42:57 HOSTNAME warp-svc[789]: PowerStatusChanged handled
Aug 24 17:42:57 HOSTNAME warp-svc[789]: dex_tests updated
Aug 24 17:42:57 HOSTNAME warp-svc[789]: device_state updated
Aug 24 17:42:57 HOSTNAME warp-svc[789]: emergency_disconnect updated
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: DSCP-POLICY clear_all
Aug 24 17:42:57 HOSTNAME warp-svc[789]: update_power_status
Aug 24 17:42:57 HOSTNAME warp-svc[789]: emergency_disconnect handler
Aug 24 17:42:57 HOSTNAME warp-svc[789]: configuration handler
Aug 24 17:42:57 HOSTNAME wpa_supplicant[964]: deinit ifname=wlp3s0
Aug 24 17:42:57 HOSTNAME warp-svc[789]: Routes changed (all IPs redacted)
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute IPV6_GLOBAL_REDACTED
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute IPV6_GLOBAL_REDACTED
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute IPV6_LL_REDACTED
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute ff00::/8
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelNeighbour (all IPs redacted)
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute IPV4_LOCAL_REDACTED
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute IPV4_LOCAL_REDACTED
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelRoute 192.168.1.0/24 (local subnet redacted)
Aug 24 17:42:57 HOSTNAME warp-svc[789]: DelNeighbour (local IPs redacted)
Aug 24 17:42:57 HOSTNAME audit[703]: NETFILTER_CFG firewalld rule unregister
Aug 24 17:42:57 HOSTNAME warp-svc[789]: main loop handling Suspend
Aug 24 17:42:57 HOSTNAME warp-svc[789]: update_network_info
Aug 24 17:42:57 HOSTNAME warp-svc[789]: NetworkInfoChanged processed
Aug 24 17:42:57 HOSTNAME warp-svc[789]: Firewall unloaded
Aug 24 17:42:57 HOSTNAME warp-svc[789]: alternate_network updated
Aug 24 17:42:57 HOSTNAME warp-svc[789]: Determining power_state=Suspend
Aug 24 17:42:57 HOSTNAME warp-svc[789]: StatusChanged Unable(NoNetwork)
Aug 24 17:42:57 HOSTNAME warp-svc[789]: Ipc Broadcast Unable(NoNetwork)
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: Ignoring excess values in shadow definition
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: Ignoring excess values in shadow definition
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: Ignoring excess values in shadow definition
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: Ignoring excess values in shadow definition
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: Ignoring excess values in shadow definition
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: Ignoring excess values in shadow definition
Aug 24 17:42:57 HOSTNAME gnome-shell[2380]: AccountsService.User::password-mode mismatch
Aug 24 17:42:58 HOSTNAME gnome-shell[2380]: Object disposed in extension cupertino-dock-lite (paths redacted)
Aug 24 17:42:58 HOSTNAME gnome-shell[2380]: Object disposed in extension cupertino-dock-lite (paths redacted)
Aug 24 17:42:58 HOSTNAME gnome-shell[2380]: Object disposed in extension cupertino-dock-lite (paths redacted)
Aug 24 17:42:58 HOSTNAME gnome-shell[2380]: Object disposed in extension cupertino-dock-lite (paths redacted)
Fedora has historically been one of the first distros to release new kernels, so issues encountered using Fedora get fixed by the time other distros release new kernels. I think the current AI driven threat environment is forcing distros to up their release cadence and also leading to problems with hardware-specific support when existing mechanisms have security problems. Have you tried a pre-release Fedora 45 “Live” iso to see if the issue is present there?
Previously, I updated the computer to the latest supported version, which was macOS Big Sur, and then used open core legacy patcher to upgrade it to macOS Sonoma. I used MacOS Sonoma for about two months before switching back to Linux.
The firmware changes may come with the more recent MacOS installed using OCLP. It is safest to follow the instructions to restore the last supported macOS version when moving off OCLP.