• 9 Posts
  • 15 Comments
Joined 9 months ago
cake
Cake day: July 15th, 2024

help-circle

  • So when lid is closed, OS doesnt suspend or takes long to suspend? The best way is to use journalctl. Close the lid, wait 2 - 5 mins, then open it up and check most recent journalctl messages. Hopefully that gives you some clues.

    Now, are you dual booting Windows? Try to check Bios if your laptop has any funny settings for power. On Lenovo, there used to be something like “Power scheme for both Linux and Window” button…

    Lastly, xfce4-power-manager app really is just a GUI for your core systemd services. So… as a test, can you not autostart it? Xfce has a setting for that. Or just remove it, you can easily install it back later.
    Once youre done, reboot back and check:

    1. Does closing the lid make the laptop to go into suspend mode? If yes, great. Test again to see if behavior is erratic, i.e. sometimes it takes 5 sec to suspend, sometimes it does not suspend at all…etc.

    2. If above fail, try to run “systemctl suspend” to check if suspend really works on your system.

    3. if 1) and 2) fail, you can play around with /etc/systemd/sleep.conf script. Maybe uncomment “AllowSuspend” or something similar…










  • Well thanks everyone. I finally managed to get it to work on Arch. System has separate encrypted root and swap in LVM, and a separate encrypted home. It can suspend and hibernate. Below are my steps

    DISK PREP

    to create a LUKS container that is encrypted with: a keyfile and a password. Test both to make sure you can open the locked drive. Format and mount it at /mnt/home or where you want the /home to be.

    • Pacstrap and then genfstab.
      Important: Make sure to copy the keyfile from your archiso environment to your chroot environment aka your system. Otherwise, when reboot, the keyfile is gone. I put it in /root and set permission so only root can read.

    AUTOMATIC UNLOCK

    • First, fstab. When you do genfstab, things should be fine. But just double check the UUID is correct for /home. Note in fstab, the UUID is the unlocked one: so the one with /dev/mapper/home. Change to noatime if you desire.

    • Second, crypttab. Assume you decrypt your LUKS home as “home”. Add this:

    home uuid of the unencrypted home drive location of the keyfile luks

    The link above said to just use /dev/sda, but imo UUID is safer if you have a removable drive.

    • Third, grub. Edit your /etc/default/grub and append the following to GRUB_CMD_LINUX:

    “rd.luks.uuid=UUID of the locked luks home drive”

    FOR HIBERNATION

    For some reasons, hibernation doesnt work out of the box. It works when I have everything in 1 drive, i.e 1 boot, 1 efi, 1 lvm on luks for /home, swap and /. The fix is simple:

    • add “resume” to /etc/mkinitcpio.conf. Add before “filesystems” . Rebuild your initramfs with mkinitcpio -P.

    • add to /etc/default/grub: “resume= uuid of the unlocked swap partition”. Or if you do LVM, just use “resume=/dev/vg/swap”.

    Special thanks to bodaciousFern@lemmy.dbzer0.com and Lemmchen@feddit.org for giving me correct ideas about “rd.luks.uuid” and that LUKS can do both pass and keyfile.





  • I have Fedora on my work laptop and vanilla Arch on my tinkering laptop.

    I think instead of thinking about “set it and forget it”, you might want to think about “if shit happens, how fast can I fix it?”. That is because stuff break or there are bugs . If you use a very old and LTS distro, you might be comfortable but there might be bugs that do not get fixed until much later. Eg: Debian’s kernel used to be able to suspend-then-hibernate, then they jump to one that cannot. So if you want that feature back, you need to wait… until Debian catches up with mainline’s fixes.

    So if you only use your computer for web, email, movie. Then any distro will work.

    Now, imo there are 2 types of problems in Linux:

    1. Boot/GRUB/partition problems: this can happen if you’re dual boot, or a config goes wrong. To fix, usually you need to boot a live cd.

    Pop OS would be #1 choice just because it has a “Recovery Partition” with live environment. You can reinstall the entire OS while you’re on the plane, without wifi or any USB.

    Arch would be #2 here, just because the arch iso is so good. It is minimal and has all the tools you need to fix stuff: partitions, wifi…etc. Plus, it boots in tty so it is faster for fixing.

    1. Problems with library mismatch: for this you want one with good snapshots built in. So OpenSUSE or if you know how to configure btrfs, maybe Fedora. I would still go Pop OS here, so you can configure btrfs AND get the recovery from point 1) above. Linux Mint would be #2 choice because they have timeshift built in.

    So the TLDR for you is: pick Pop OS for the recovery partition. Also, use btrfs. Lastly, configure your disk nicely, i.e. dont do any crazy LVM encryption, just use standard layout so when comes the time to fix, it is easier.