Computers and the internet gave you freedom. Trusted Computing would take your freedom.
Learn why: https://vimeo.com/5168045

  • 0 Posts
  • 125 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle













  • logs are mostly at 2 places.

    kernel logs are read with the dmesg command. use the --follow parameter if you want it to keep printing new messages.
    dmesg does not save logs to disk.

    broader system logs are read with journalctl. use -f for it to keep printing. the journal records kernel messages, but it only shows them when you specifically request it. you can find the param for that in man journalctl.
    the journalctl (journald actually) saves logs to disk. but if you don’t/can’t shut down the system properly, the last few messages will not be there.

    some system programs log to files in /var/log/, but that’s not relevant for now.


    if you switch to a VT as the other user described, you should see a terminal prompt on aback background. log in and run dmesg --follow > some_file, some_file should not be something important that already exists in the current directory. switch to another VT, log in, and run sleep. try to wake up. see if you could have waken up, and if not check the logs you piped to the file, maybe post it here for others to see.

    also, what did you do after setting the deep sleep kernel param? did you rebuild the grub config, and reboot before trying to sleep with it? that change only gets applied if you do those in that order.
    there’s an easier way to test different sleep modes temporarily, let me know if it would be useful