@asana,
have you read last messages of system journal after having this problem? (You can see it with "journalctl -b -1", meaning "select boot -1 from current".) I mean messages that have been logged after waking up from suspend. Are these present in journal at all? (You should be able to figure it out from messages' timestamps.)
Also, does "dmesg" work when you manage to log into tty after such event?
AFAIK, kernel produces at least couple of journal entries after every wake up. If these get saved to your disk before rebooting, there is no problem with disk encryption.
have you read last messages of system journal after having this problem? (You can see it with "journalctl -b -1", meaning "select boot -1 from current".) I mean messages that have been logged after waking up from suspend. Are these present in journal at all? (You should be able to figure it out from messages' timestamps.)
Also, does "dmesg" work when you manage to log into tty after such event?
AFAIK, kernel produces at least couple of journal entries after every wake up. If these get saved to your disk before rebooting, there is no problem with disk encryption.
Statistics: Posted by dashek — 2024-02-17 13:56