Bryan SteeleHeads up: The machdep.lidsuspend compat sysctl is going away. Use machdep.lidaction in sysctl.conf (0:disable/1:suspend/2:hibernate) #OpenBSD
nakal 👨👩👦👦 ⌨️@canadianbryan
0: you'll be fine
1: fsck on next reboot
2: reinstall system on next reboot
😏
@nakal Hmm? I've never seen any such issues with suspend/resume. If it works, it works. It's even the default lid action. No idea what are you on about regarding hibernate..
@canadianbryan Hinernate sometimes does not unhibernate successfully and boots up fresh, fscks follow which is scary. Happened to me twice then I disabled it. Normal sleep is a lot more stable. I think the only issue is that sometimes VGA is not reset to Xorg, but stays on text terminal after wakeup.
@nakal Unhibernate relies on the disk and kernel staying the same, you definitely want it to start fresh if it detects this case. Suspend/resume needs graphics drivers, otherwise it can't reinit hw, for example efifb(4) is lost.
@canadianbryan So if I update with syspatch, it may be that I get the problem I described? I haven't paid attention if I patched the system, I have to admit. It makes sense. Thank you.
Suspend/resume just sometimes doesn't do tty switch back to X. This is only cosmetic problem, because I can press Ctrl+Alt+F5.
@nakal Correct, if you replace the kernel and then hibernate, there will be a new kernel loaded which is incompatible with the hibernate image. Special care was added to the bootloader for KARL for this, for example: http://marc.info/?l=openbsd-cvs&m=149791265512541&w=2