Hello everyone, the last weekend I was away and - for the first time after receiving my laptop - I didn’t use it for few days. Before leaving I powered it off (I’m using debian) and this morning when I tried to power it on it was not responding.
I plugged the usb-c cable to the monitor I usually use while at home and the charging led turned orange. I waited a minute or so and then I pushed the power button, the led lit immediately but the startup of the laptop (as in displaying the framework logo, so possibly the POST?) was slower than usual.
The OS detected the battery at 0%, so from the look of it the battery emptied itself over a weekend while powered off (I keep the maximum charge at 80% from the BIOS), this is a higher battery drain than the s0 suspension, so I guess there must be something very wrong somewhere.
This is the output of journalctl -b -1, so from the OS point of view the shutdown state was properly reached:
feb 23 06:05:18 ferox systemd[1]: lvm2-monitor.service: Deactivated successfully.
feb 23 06:05:18 ferox systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
feb 23 06:05:18 ferox systemd[1]: Reached target shutdown.target - System Shutdown.
feb 23 06:05:18 ferox systemd[1]: Reached target final.target - Late Shutdown Services.
feb 23 06:05:18 ferox systemd[1]: systemd-poweroff.service: Deactivated successfully.
feb 23 06:05:18 ferox systemd[1]: Finished systemd-poweroff.service - System Power Off.
feb 23 06:05:18 ferox systemd[1]: Reached target poweroff.target - System Power Off.
feb 23 06:05:18 ferox systemd[1]: Shutting down.
feb 23 06:05:18 ferox systemd-shutdown[1]: Syncing filesystems and block devices.
feb 23 06:05:18 ferox systemd-shutdown[1]: Sending SIGTERM to remaining processes...
feb 23 06:05:18 ferox systemd-journald[749]: Received SIGTERM from PID 1 (systemd-shutdow).
feb 23 06:05:18 ferox systemd-journald[749]: Journal stopped
Edit: information about the laptop model and connected expansion ports (no hardware was attached to the ports when powering off)
I’m using: a single usb-c expansion port (up left also towards the screen) and one usb-A in (lower-right also towards me).
I can confirm this ! I had the same behavior on FW13 AMD 7840U with Fedora 39 all updated.
All USB C, but only the front left one is USB A. The laptop was not connected to anything.
Ahh ok, I’m not familiar with the AMD platform as that is an entirely different chipset, etc.
I would suggest speaking with Framework customer support. The USB re-timers and all are very tricky things and the mainboards are immensely complicated things. My guess, for what it is worth, is that a USB port is staying hot (current being sent to it) despite being off. You can test this by turning it off and plugging in a USB mouse. If it lights up, there is a vampiric loss as a result of a USB port.
Hard to say if this is Framework or Linux’s issue. I have not seen any reports of this on Windows 11 with the AMD platform.
I opened a support ticket.
FYI last night I kept the laptop powered off for 11 hours without external adapters and it lost 5% of battery. This does not seem normal to me.
I have no idea what could have happened but tonight the battery went from 80% to 0% in just a few hours with the laptop powered off!
Last entry of journalctl -b -1 -k was written at 19:13:11 and this morning at 8:55 when pushing the power button it started blinking and the laptop shut itself off as soon as it reached the luks passphrase input stage. I then connected the power adapter and could boot and the OS detected the battery as empty.
I’m running bios 3.05. Last boot was with debian kernel 6.9.7 and linux-firmware @ e94a2a3bc8bdfc6a4a7b05eed7803b64a409c9f5, I am now running debian kernel 6.9.8 (getting on the new kernel was the reason of the power off).
Not sure if that also happens when the laptop is powered off.
Another related problem: When it’s sleeping it can be waked up unintentionally by pressing the touchpad - this can also happen when the lid is closed and you carry the device around or it’s in a bag or similar, when the lid/display presses on the touchpad.
That can be prevented by disabling wakeup by touchpad. On Linux that can be done by running the following in a script after each boot (as root):
If you’re wondering where that path comes from: $ sudo libinput list-devices
lists, among other things: Device: PIXA3854:00 093A:0274 Touchpad
The nodes in /sys/ for configuring if a device can wake the system are always like /sys/*/power/wakeup
So I ran $ find /sys/ -wholename "*/power/wakeup" | grep PIXA3854:00
and it gave me the path used above.
I’m honestly not sure what in my message led you to believe that the laptop was suspended rather than fully turned off. As English is not my first language, I’d be grateful if you could point out the source of this misinterpretation so that I can improve my communication in this language.
Depending on expansion cards, bios/firmware version and other settings going from full to empty in 3 days suspended is very possible (and kind of an ongoing issue here which is probably why it was suggested).