I have the framework 13, 11th Gen Intel® Core™ and I am running linux kernel 6.16.7 on fedora 42 WE
I have the old 3.07 bios currently installed and would like to update to the latest one. To my shock I saw that it is now 3.24 xD Yikes, long time since I did last update
@Erik_Wilhelm_Gren Depending how you use your laptop, I would recommend you only update to BIOS 3.17. They have introduced a bug from BIOS 3.19 on that might prevent your laptop from going into proper suspend mode. That means it will eat through your battery even during sleep. This is as far as I know not fixed. The only way for your laptop to go through a night is by using hibernate, but that requires special setup during installation of your distro. Somebody even created a gnome extension to circumvent all this mess. I used it for a while but stopped caring at some point.
Note that you cannot go back once you went to 3.19. There is no downgrade path.
They claimed that Intel CPUs never supported these modes on Linux in the first place, although everything was working fine before. For me this made the Framework unusable as a travel laptop and I went back to a Macbook.
There are threads in the forum with a lot more explanation.
If you use the Framework as a stationary computer, you might not care. So you need to decide for yourself.
I just updated to 3.24 and can confirm that I can enable “deep” sleep again without entering my death-cycle described here:
So, at least for me and with BIOS 3.24, my Framework 11th gen batch 8 is waking up from deep sleep again. It is currently running a standard encrypted installation of Fedora 43.
I need to check how the battery drains in this mode. It looks like my previous post contains outdated information now
Yes, the default Fedora installation is using s2idle. You can find out what your system is using by issuing
$ cat /sys/power/mem_sleep
I enabled the “deep” mode, by adding the CMDLINE argument to my grub config.
To enable deep sleep in Fedora, you need to add the kernel parameter mem_sleep_default=deep to your GRUB configuration. You can do this by editing the /etc/default/grub file and then running grub2-mkconfig -o /etc/grub2.cfg to apply the changes.
But for testing I recommend to add this parameter in grub by hand first, to see if your system is returning from deep sleep without issue. After that you can apply it permanently to the configuration.