3 ms·
Why not for a Macbook? What are the issues?
by stavros 3y ago
Why not for a Macbook? What are the issues?
- petemir 3y agoProbably related to the different sleep states of the CPU, standby/resume, and battery use in general. Always a pain with Linux.
- lillecarl 3y agoThe Lenovo T14s with an AMD CPU and Intel WiFi sleeps perfectly every time, the CPU scheduler seems to behave right too since I have a full days battery life normally. I went into the BIOS and enabled S3 sleep though, since it's sold as a Windows machine and Microsoft is pushing the new hybrid sleep stuff really hard.
- mo_42 3y agoActually, I run it on my MacBook. Two things that might discourage most people: - CPU idle (they are trying to hack it into the their forked kernel but it will be a long way for proper support by Linux) - Sleep (not even Apple’s deep sleep) Not involved with the project. I read about this a couple of weeks ago. Could be outdated already.
- bakkoting 3y agoThey actually just today released an update [1] with fixes for sleep: "We now have a cpuidle driver, which significantly lowers idle power consumption by enabling deep CPU sleep. You should also get better battery runtime both idle and during sleep, especially on M1 Pro/Max machines. Thanks to the cpuidle driver, s2idle now works properly, which should fix timekeeping issues causing journald to crash." [1] https://social.treehouse.systems/@AsahiLinux/110497512340479064 https://social.treehouse.systems/@AsahiLinux/110497512340479...