Laptop exits sleep without me opening the lid

Which Linux distro are you using?

Ubuntu

Which release version?

24.04.2 LTS

Which kernel are you using?

6.8.0-60-generic

Which BIOS version are you using?

3.09

Which Framework Laptop 13 model are you using?

AMD Ryzen™ 7040 Series


Hi all,

I am trying to understand I weird behavior I have noticed on my AMD 7040 board (which I upgraded to from an 11th gen Intel board).

In a nutshell, the laptop seems to exit its s2idle sleep unexpectedly.
Sometimes, I notice the event because, while walking with the laptop in my backpack, my Bluetooth headphones connect to the laptop, then disconnect again.
Other times, I pull the laptop out of my bag, and I start hearing notification noises before I even try to open the lid.

I have used journalctl in the past, in an effort to figure out the odd sleep behavior of the 11th gen board. But I must be missing some key knowledge, because I cannot for the life of me figure out what is triggering the suspen exit event.

If I didn’t know any better, I would blame a faulty lid sensor. But it’s in my nature to think of a hardware failure first, and maybe the issue here is on the software side of things.
Any tips are appreciated.

Cheers,

My suggestion is to make sure you are using s2idle (deep). Framework’s official guides talk about this as well.

That or configure hibernation. On an NVME and depending on how much system RAM you have it really is not the big of a time synch anymore. And you have peace of mind knowing your system is completely off.

Hi, thanks for chiming in @2disbetter

This is what we are doing on our older intel boards. It should not be something needed for the AMD boards. On top of it, /sys/power/mem_sleep only lists s2idle as an option.

Besides, I’d still want to understand what the trigger is. What if it really is a problem with the lid sensor?

If I was to guess here it’s your touchpad being pressed “through” the lid.

What you can try to do is use Client Challenge to reproduce it.

Basically install the wheel and then install it’s systemd hook. Then suspend just like normal.

When the issue reproduces generate a report using “amd-s2idle report” and then share that somewhere to make sense of.

2 Likes

Thanks @Mario_Limonciello, I’ll try to give it a go.

This seems to be a common problem with FW laptops.
On my FW16, I just disable all wakeup sources except the power button.
So, I disable wakeup on:

  1. Keyboard
  2. Touchpad
  3. Lid open / close
    To find out how, search these threads for “sleep” or “wakeup” problems. There will be a script you can use to disable wakeups.

Then when I open the lid, I can see it still in suspend, and just press the power button to wake it up.

A long time ago, someone from FW said they were going to fix it in a BIOS update, but the BIOS update fix never arrived.

If this doesn’t solve your issue, I’d recommend filing a ticket so the Support team can take a closer look at what’s going on.

Hi all,

Thanks for the input, and apologies for the silence. After some very scientific tests (i.e. bending the chassis while the laptop is sleeping) I can confirm that the issue seems to be mechanical in nature.

I’ll see if I have the grit to figure out which component is triggering the wakeup. Or I will reach out to support. Let’s see.

Thanks a lot for the help!

Might be worth completely disconnecting/removing the audio board and see if that helps. If the defect is on the mainboard that’d be a bigger issue.

1 Like

Can I ask how the audio board comes into play?

It’s where the lid sensor is.

The sensor is hall sensor based. It works based on magnets in the lid. As such magnets near audio jack can possible trigger it, causing your laptop to suspend.

Is it possible you have a magnet or anything like this often around your FW 13?

He did say bending the laptop can make it happen so it could also be a broken trace or loose solder joint somewhere causing the signal from the hall sensor to get interrupted causing the wakeup. If it does happen with the audio board disconnected it can’t be stray magnets or a defect on the audio-board. if it doesn’t happen with the audio-board disconnected the fault is entirely somewhere else.

To clarify: the Super Scientific Bend Test was done with the lid open, not closed. So, whatever triggers the wake-up, I am tempted to rule out anything magnet/related. I’ll tinker a bit more, and see what I can find.

How so?

Well, with the screen open all the way, its magnet is too far to have any effect on the sensor. With no other magnet in sight, I don’t see how it could be related to a magnetic field interfering with the sensor on the board.

That is kind of an important detail left out XD.

So it could still be an issue with the sensor or connections to the sensor, unplugging the audio-board would narrow it down a bit.

In my defense, I did say the lid was open. And I don’t know about you, but I don’t walk around with magnets hanging from my neck. :squinting_face_with_tongue:

I’ll give it a shot.

You’d be surprised where you can find magnets these days.

1 Like

Such as a magnetic watch band …