Just upgraded to Trixie (Debian 13), and BIOS from 3.04 to 3.18.
Battery on 80% charge, and it a few years old so down to 80% charge anyway. So 64% of fully charged. Made laptop suspend, put in bag, watched movie in cinema (Lost In Translation - lovely). Came out about two hours later - bag is hot, laptop is dead, out of battery. TF?
If laptop is hot, then it was not asleep, simple as that.
Debian is stable but it often not compatible to the latest hardware(or BIOS)
This topic is still live for me: my 13 is supposedly on suspend after 15 minutes, battert or mains power…and the machine just drains the battery right down in a matter of hours. I think it even does it if I manually suspend (Ubuntu 24.04.3 LTS 11th Gen Intel® Core™ i7-1165G7 × 8 Linux 6.14.0-37-generic firmware 03.24)
You have to manually configure the deep sleep state for the laptop. The default state is “s2idle” which is basically not a sleep at all, and there is a better state “deep”, which you need to manually set. I can’t remember how to set it permanently, but you can see what you have now with “cat /sys/power/mem_sleep”. The value in square brackets is the currently selected value. I get this “s2idle [deep]”. This is a critical fix.
The next issue, which I’m not wholly sure about, is that it may be the USB-A adapters draw significant power, each. I’ve removed all mine. I have tested a bit, powertop and switching one USB-A in/out and I’ve not seen a significant difference. In any event, USB-C is better because it’s rated for a lot more current/electricity.
Note that quite a bit of power config seems non-optimal by default, in that “powertop --auto-tune” changes quite a bit of config. Powertop is your friend - use it and learn how to use it. The list of config and whether it’s good or bad is important. Look at what’s draining power on your system and fix things up - it’s very easy to have a lot of power draw. I get down to about 4 watts, when I turn off the stuff I don’t really need.
Finally, note that a USB mouse draws about 3 watts. If you want to conserve power, you can’t use a mouse.
Separate matter - I received an email notification about the post from Andrew, and that email says “you can reply to this email to post”. This does not work. I used the same email address I log in as, but my email was rejected with “Email replies require that you use the same email address when replying.”.
As such, I followed the “view topic” link in the email, and logged in. Logging in - takes you away from the topic and to the forum home page. So you then return to the “view topic” link and follow it again.
Known issue for a very long time.
Official (non-)solution from FW is:
“Just shut it down”.
Which FW13 model do you have?
There are cases reported of the laptop waking up if pressure is put on it while its lid is closed. Pressure enough to make it think a key has been pressed or the trackpad touched.
Their have been efforts recently, a new BIOS update, and firmware update for the keyboard, that will help reduce the likelihood of the wakeup happening while the lid is closed.
A work-around that I use for this, on my FW16, is I disable all wake-up sources except the power button.
So, it goes to sleep, but I have to open the lid, and press the power button for it to wake.
This seems to work for me.
You can use the “amd_s2idle.py” program to test the suspend, and what is waking it up.
Another simple work around, as mention by others, is to power off the laptop, instead of suspend it.
Why should one have to use workarounds or use the laptop in an unexpected way in order to have a normal computing experience?
Why don’t Framework address these issues directly instead of basically telling us to deal with it then ignoring any subsequent mention of it?
Well, there has been a BIOS update that should fix it, thus why I was asking which FW13 model you have and which BIOS version you currently have.