As long as when lid is open, still allow keyboard signals.
Also, what will happen if I have the OS (Linux specifically) to not suspend on lid close? Will it suspend regardless with this change?
This is just the action of keyboard during sleep or lid close he’s talking about. It wouldn’t affect setting Linux to not suspend on lid close.
Gotcha. Ok, great.
Would this be a QMK firmware update? I assume there has to be some OS-side software as well to send the lid-closed signal?
Looks like Kieran and Mario are working through some ideas. We’ll know more as this evolves.
1 Like
I also confirm that the Framework 16 is, so far, unreliable when it comes to suspend:
- s2idle feels like a technological regression compared to S3. I understand Framework is not to blame for this first point though.
- I have seen it failing to suspend, with at least one stacktrace related to the amdgpu driver.
- I have seen it suspending then waking too early while transported in a backpack.
- I have just seen it not waking at all (possibly freezing?) after suspend (I had to long-press the power button to shut it down).
That being said, I cannot complain too much for I do not use an officially supported kernel (I use Debian Sid and its 6.7.9 packaged kernel instead of Ubuntu 22.04).
The elements above were harvested as part of my normal, regular use of the laptop, but I will try to experiment in a more rational way with better logging and tooling, as suggested by Mario.
4 Likes
I have experienced a 2nd instance of freezing on resuming.
Details:
- the laptop was suspended through “systemctl suspend” while its lid was closed, its main screen disabled and various other devices connected through a dock, including 2 DisplayPort monitors.
- I pressed a key and noticed no reaction
- I opened the lid: the screen was still disabled and I noticed the keyboard was not responding to the hotkeys (e.g. Fn+space to increase backlight); same for the numpad.
At this stage, I consider the laptop is frozen and can only long-press the power button to shut it down.
Like the 1st time it happened, regular system logs do not help. The last log entry before the next boot is simply “kernel: PM: suspend entry (s2idle)”.
1 Like
More than a week has passed since my previous post and… I did not get any suspend-related troubles in the meantime. Presumably, I have been subconsciously avoiding a situation that used to trigger those issues, but I cannot pinpoint what exactly.
Note : I have not switched to the 3.3 BIOS yet.
The lid on the 16 flexes a lot - enough to be able to click the trackpad / keyboard
I also noticed a series of ‘k’ characters appeared in a text editor after I dusted the laptop with the lid closed, but I cannot reproduce it at will.
I’m on Ubuntu 24.04 beta with kernel 6.8.0-22-generic #22-Ubuntu and suspend works perfectly for me. I had problems with suspend until I updated the kernel from 6.8.0-11 to 6.8.0-20.
I was having issues on 22.04 LTS (with OEM kernel) that would result in it going to sleep properly, but I opened the laptop again within like 30 seconds the screen would completely glitch out and either just look broken (graphical), or wouldn’t turn on the screen at all. And I had the same issue with 23.10 with the latest mainline kernels.
Since switching to 24.04 Beta with the latest kernel that comes with it, everything has worked absolutely perfectly 100% of the time when it comes to the display and sleep so far.
Glad to hear it’s doing better on Ubuntu, but I just had the issue happen tonight again - put my laptop in the bag and it woke up & drained the battery again. This is on a newly updated archlinux, kernel 6.8.7
If it’s 13 add platform/x86/amd/pmc: Extend Framework 13 quirk to more BIOSes · torvalds/linux@f609e7b · GitHub to your kernel.
If it’s 16, it’s probably it’s from the lid pressing the keyboard or trackpad.
1 Like
Yeah this needs to get fixed. The thing work up in my bag. When I pulled it out the thing was almost too hot to touch. Now I have to wonder if that may have damaged the system. I had this issue with a MBP I had back in 2006. Sensor was screwed up overheated in the bag and then I spent 8 months back and forth with Apple as the system would crash randomly after that until they finally replaced the motherboard.
FW 16 with GPU on Fedora 39. Used the guide to set it up.
1 Like
I completely agree. This needs to be top of the list of potentially damaging issues that need to be fixed. A laptop should properly sleep of all things. It can’t be that hard. Other brands of laptops I use all do it just fine.
Very frustrating that I have to power it all the way down before putting it in my bag or I run the risk of pulling it out on fire the next time.
3 Likes
That’s definitely something that’ll be on my list, although I don’t do suspend that often myself.
Yeah this happens to me a lot while riding my bike, too.
I can tell it woke up, as the laptop steals my airpods and I had to connect again on my phone.
It also suspends very quickly afterwards though, within ~10 seconds.
I’m running arch linux, keeping my stuff on the latest.
1 Like
I really hope this is high on the priority list… I had a critical moment where I needed my laptop yesterday fast and found it in my bag on the login screen at 5% battery and extremely hot to the touch.
1 Like
For now If you upgrade to 6.8.8 the kernel workaround is there. If you’re on something older you can use the udev rule workaround.
1 Like
We are planning to address this in our next BIOS/firmware update for this platform by disabling keyboard input when the lid is closed.
11 Likes
Any estimated timeframe on this? A “hopefully by X month” would be nice, and I promise I won’t hold you to it 