Suspend/resume issue (I think) on FreeBSD

[mogabi]

I am new to FreeBSD. My first installation was on a ThinkPad T480 two months ago. So far, so good. But...

When I close the laptop lid, leave it closed for a short or long bit, then typically either:

More often...

(1)

the screen comes back exactly as I left it, I can move the pointer with the track pad, but otherwise clicking anywhere or pressing any button on the keyboard does absolutely nothing.

When this happens, I push the power button to force it to power off, then boot back up and things work normally. This happens almost every time when I leave the lid closed for a brief period (which I try to avoid now). It also happens sometimes when I leave the lid closed for a long time.

Or, less often...

(2)

when I open the lid, it goes to the screen where I have to type in my password (like when I leave it untouched for a while and the screen goes goes black), I type in the password, then everything works. This never seems to happen when the lid is closed briefly. But it doesn't happen every time when the lid is closed for a long time (hours, or overnight, etc).

Any thoughts on what might be happening and how to fix it?

 

[fahrenheit]

Well, FreeBSD only supports S3 suspend which most recent CPUs do not support (only S0ix), did you check if your cpu does support S3 (instructions on the handbook).
Assuming it supports S3, then you have to check if the rest of the devices also support it (network cards and gpus may be an issue).
Afterwards you have to enable support on the software side, DEs usually have some place to configure it, the handbook also helps.

 

[T-Aoki]

In my experience, the last time I've successfully suspended/resumed was before FreeBSD switched from APM to ACPI, using PAO code available at the era. Note that tried only on several ThinkPads.
So it was quite a huge surprize for me when I found PR 285803.

Anyway, succeed or fail on suspend/resume depends not only on CPU features, but also BIOS/firmware/additional hardwares used.

 

[mogabi]

Well, FreeBSD only supports S3 suspend which most recent CPUs do not support (only S0ix), did you check if your cpu does support S3 (instructions on the handbook).
Assuming it supports S3, then you have to check if the rest of the devices also support it (network cards and gpus may be an issue).
Afterwards you have to enable support on the software side, DEs usually have some place to configure it, the handbook also helps.

My CPU, network card, and GPU all support S3.

Thanks for the reply.

 

[blackbird9]

I have suspend/resume working reliably on my thinkpad X220, however that is a generation or two older than your T480. I had to write a couple of scripts to get it to work properly, I can dig out the details if you want to try doing the same thing. I don't know if what I have done will work on the T480 though.

 

[blackbird9]

It seems I already posted what I did a few years ago.

Post in thread 'How to make the laptop sleep when lid is closed'

Oct 30, 2023

At the risk of repeating what other's have said...

The following works with freebsd 13.2 on my thinkpad X201. I run the system using the windowmaker window manager.

For suspend on lid close, add the following line to /etc/sysctl.conf:-

hw.acpi.lid_switch_state=S3

As a bonus, I found Fn+F4 correctly suspends the system from the keyboard. So nice to see old(er) thinkpads well supported in freebsd, whoever wrote the code needs some recognition for doing a good job.

Basic resume then works on lid open with no other changes.

To maintain security after a resume on lid open (or, by...

• blackbird9

Post in thread 'Execute command after ACPI resume'

Mar 24, 2023

Another way to achieve this is to use xidle to run the lock program. Taking 'slock' as an example, launch it using xidle as follows:-

xidle -se -program "/usr/local/bin/slock" -timeout 300 &

Which can be run from your desktop's autostart script, or .xinitrc.
Using wmaker I added the xidle command to ~/GNUstep/Library/Windowmaker/autostart .

To lock the screen on resume, add the line

pkill -USR1 xidle

to /etc/rc.resume, I added it after the filesystem sync as follows:-

/usr/bin/logger -t $subsystem resumed at `/bin/date +'%Y%m%d %H:%M:%S'`
/bin/sync && /bin/sync && /bin/sync
pkill...

• blackbird9

That gives you a starting point, anyway. Now, that may or may not work with your particular desktop environment, you will have to investigate that yourself. I developed that solution to work with windowmaker and fvwm. I seem to remember there was one remaining race condition when I made those posts, which I have since fixed, I can dig out the details if that helps.