I assume that it will all be open source, so there would be nothing preventing anyone from porting it to a different distro.
True, but if I understand it correctly it is essentially a GNOME Extension right now and it requires BTRFS. So it only makes sense for new installs. So it is in its current form not a generic solution for all Linux systems/distributions. Others will have to fiddle and do it by hand.
And suspend is still broken for my systemâŚ
Well, they only officially support Fedora and Ubuntu, so thatâs nothing new. And if it requires a particular partition setup then the logical time to do it is on initial install.
Setting up hibernate is not that difficult. It takes a bit of effort, but itâs worth it. I have been very happy with suspend-then-hibernate on my systems.
Maybe we should take it to a different thread, but what is broken with suspend on your system, and what distro are you running?
I am in the same club as these fine people over here:
As this thread is focused on BIOS 3.20, if you have issues with suspend and would like help with that, please move to another thread or open a new one.
1 Like
Well, my issue with suspend was introduced after updating my from BIOS 3.17 to 3.20. Which soft-bricked my computer until I switched suspend mode from âdeepâ to âs2idleâ
Deep suspend was working perfectly fine before and the battery drain was tolerable. Now it is not anymore as most of the time the laptop doesnât really go to sleep - it just pretends it does by flashing the powerbutton. But if you listen closely you can still hear the fan spinning. Which tells me it is not sleeping at all. In that state it lasts maybe a few of hours instead of days.
Using hibernation is fine by me - but it isnât fixing the underlying problem. It is just covering things up.
But fine, I will watch how this goes and if framework is providing a proper solution for this with the next BIOS version and then I decide if it is worth spending more money.
@lvdd deep sleep wonât be fixed anymore.
I was in contact with support and since 3.20 deep sleep is not supported anymore:
âSpoke with engineering for clarification on deep sleep not working. Yes, you will be using s2idle as we have found that the later BIOS are not supporting deep.â
Thatâs a pity for everyone with this issue, especially since there was no mention anywhere. At the least they added it now to the âKnown Issuesâ for bios 3.20.
1 Like
Well, thatâs a pity for them as they wonât see any more money from me, if that turns out to be true.
They remove an essential functionality and then afterwards tell me âsorry, bad luckâ? That for me is a trust problem which they are not going to recover from in my book.
My laptop is still working and I can use it with the hibernate workaround to circumvent the battery drain issues. But the fiddling required to just get the most fundamental thing to work on this hardware is a waste of lifetime for me at this point.
Maybe I am just going to print a case and use the board as a homelab server (that doesnât require any sleep functionality) or hand this thing to my wife replacing her x230 as a âcouch surfingâ machine thatâs connected to power most of the time anyway and go back to my MacBook.
As much as I love the framework idea, I hate being kicked in the nuts after 3 years being left with less than before. Good luck to everyone - updating BIOS can leave you with a handicapped laptop with no way back - good work framework⌠
1 Like
Which of the Windows states s0, (. . . . s3 s4 etc.) do you consider âdeepâ
I use hibernate but have just enabled s3 to see what happens.
It uses about 1w
@lvdd Did you try to use nvme.noacpi=1 as boot parameter? It drastically reduced the battery drain in s2idle for me to a similar level as deep (~ 0.5%/h).
Which of the Windows states s0, (. . . . s3 s4 etc.) do you consider âdeepâ
I donât know the Windows states, but it should be s3.
1 Like
0.5% of what per hour?
0.5% of battery charge level on a 55Wh battery would give 54/48 or just over 1.125 W/h
So my s3 is the same roughly at 1W/h
As for the Win states; Quoted July 2024
Iâm stubborn and still trying to figure out why both of my 11th gen systems suspend and resume with no issues. Poor @lvdd ran through about eleventybillion different scenarios and didnât get anywhere with determining why his system does not come back. It feels like a driver not reloading properly, but I am way out over my skis on this. I am just a dumb end user, tinkering and plinking away on the machine. I would love it if we could get an engineer (not Support - nothing against Support, but this is out of their realm as well) that would work with us to test working and non-working systems to try to narrow things down.
3 Likes
Damn, so much friction just to even âattemptâ to get it to sleep (and wake) right. (successfully or not).
@lvdd what distribution/kernel are you using? And anything else you can comment about your setup/software configuration/kernel parameters?
1 Like
Hi Kieran,
thanks for chiming in.
There are a couple of links I posted with information about my system and the systemd journal during the death-loop. Also there is a description there how to reproduce it - at least on my laptop. The distribution doesnât matter as I can easily reproduce it with Fedora 40, Debian stable and Archlinux.
The process for me is always the same:
Install a base system with Gnome (for convenience)
Add mem_sleep_default=deep via grub to the commandline
put the laptop to sleep via powerbutton
It goes to sleep but is not waking up anymore with the effect I have outlined here: Sleep issues after 3.19 BIOS update - 11th Gen Intel Framework 13 - #28 by lvdd
The point here is that this happened after I upgraded the BIOS from 3.17 to 3.20. All of the above was working fine before. Which lets me believe that this is not an issue with Linux Kernel changes but something being introduced with the BIOS.
If I could somehow go back to 3.17 I would do that and never touch BIOS again.
@lvdd for the bios update to 3.20 we updated the core bios kernel from Insyde, and CSME, and I suspect a change in there may have broken this somehow. Your support request got to me, and I was the one who gave the statement that S3 sleep is not supported.
This is actually the official stance of Intel supported sleep states from Intel. So even though it previously did work is was not an officially supported configuration.
I am not sure exactly where this got broken, but other vendors have documented similar issues with removed/missing S3 sleep, and the requirement for CSME to support S0ix sleep. Eg https://www.reddit.com/r/System76/comments/k7xrtz/comment/gev9mkp/?utm_source=reddit&utm_medium=web2x&context=3
We can do a quick pass to see if there was something that changed which caused this to be removed, however this may be something in CSME or other components which is not fixable by us. So no guarantees if this can be fixed, and no set timeline. (I would continue to operate under the assumption that this is not going to be fixed for now).
I would have to go back and measure again for this release, but we have generally found that Linux does a much better job with S0ix sleep power drain than windows. Eg on older intel platforms I think we were ball-parking around 300mW for Windows, and around 260mW for Linux.
3 Likes
Regarding that may be true the s3 doesnât actually work as a quick wake up, itâs slower than hibernate and logs me out, so Iâm back to s0, which works fine but does use watts of power.
Yes, I can attest to this.
I can tell you that S0 is definitely not better on my system. When I put the laptop into suspend with s2idle in the evening with 10-15% battery left, it is dead the next morning with the battery fully drained, which was not the case with S3. I quite often have the situation that the system pretends to go into suspend - turning display off and powerbutton flashing but the fan keeps actually running and the system stays warm to the touch. I got into the habit of listening on the backside of the laptop to make sure it really has gone to sleep. That has always been the case since I got it and I was happy when S3 was working after a while.
Ok, that means I have a laptop with a crappy CPU that got actively crippled by some moronic Intel decision? I didnât know that and I am not sure I should be required to dig that deep into CPU design to learn about these traps upfront. That means I now have to get hibernate running as this is the only way to keep this laptop useful for me.
All of that is deeply disappointing and already shaped my decision making for the future.
BTW: It would really be beneficial to have a sleep indicator on the side of the laptop and not just with the powerbutton, as it is impossible to see with the screen closed.
1 Like
One last thing. It seems other manufacturers have found a solution for their systems with this crippled CPU: