5 ms·

I find it curious that you care about boot-times. I use macbooks and just close and reopen the lid. Waking from this sleep takes less than a second usually. My

by cel1ne 10y ago

I find it curious that you care about boot-times. I use macbooks and just close and reopen the lid. Waking from this sleep takes less than a second usually. My average uptime is about 22 days until I reboot for an update or something. I used Linux for years, and I understood that in 2008 sleep/resume on notebooks didn't properly work, but now we have 2017 - 9 years later!

eltoozero 10y ago
Mac is my daily driver for this very reason, I'm a consultant and I need to frequently grab and go. I've had Linux on mobile for ages and have yet to have reliable sleep/wake behavior on a dozen machines over the years. Sleep on Linux works reliably if you run it inside a Mac VM though, FWIW! ;)
- karussell 10y ago
  Important difference: sleep usually works and is fast. What often does not work is hibernation (recover from disc)
  - pmontra 10y ago
    According to a comment in the post it fails when the swap partition is encrypted. However why enable swap with 16 GB of RAM? I've been running without swap for almost 3 years and never had any trouble. If I start approaching the limit I'll buy another 16 GB.
    - karussell 10y ago
      The comment also talks about suspend to disc.
      - pmontra 10y ago
        Exactly, the comment in your blog is "suspension to disk does not work if your swap partition is encrypted. This is due to how Ubuntu encrypts your home (ecryptfs) but not due to Linux itself." I was reporting that.
  - cel1ne 10y ago
    ...which is crucial since you don't want to lose your data when closing the lid. (Non-tech-term is on purpose here, since users shouldn't need to know about the difference. Also I believe OSX uses a hybrid approach).
    - karussell 10y ago
      You do not loose your data with both methods as power is used for suspend to RAM. BTW: OSX has not a "pure" suspend to disc anymore and the default method is suspend to RAM when closing the lid
      - cel1ne 10y ago
        Parent poster stated "What often does not work is hibernation (recover from disc)". Which means the user loses data.
        karussell 10y ago
        Parent poster was me and you do not loose data. Instead it just does not go into hibernation in my case :)
aiur3la 10y ago
I don't really care about boot times, but as a tech guy 23 seconds sounds like an error to me and I want to find it and fix it :) Also, old laptops with dieing batteries (or new ones with always-on sensors such as fingerprint readers) have some leakage during sleep so it may be better to turn them off if you are not going to use them for a few days. edit: resume/suspend in linux works just fine and has done so for many years (in response to eltoozero)
- karussell 10y ago
  I have disabled the UEFI Network Stack (updated the article to reflect this) and now the BIOS boot time is down to ~2seconds :) !
keithpeter 10y ago
I use whole drive encryption to protect data in the event I leave my old X220 (Fedora) on the bus. I don't mind boot times in the 20s range (X220/Fedora/cheapo SSD) too much, but I do need to close down/reboot a couple of times a day otherwise no point in encryption.
- blakeyrat 10y ago
  > but I do need to close down/reboot a couple of times a day otherwise no point in encryption. Given, I'm not a Linux user, but I don't understand this at all. On Windows, encrypted is encrypted-- the lock screen is exactly as secure as the login screen. Are you saying that in Linux the lock screen is easily-bypassed? So you have to keep your computer logged-out when you're in a place it might get stolen?
  - keithpeter 10y ago
    I believe that would be 'encrypt my home drive' on Linux, then you basically log out to protect files. Not sure though.
    - blakeyrat 10y ago
      What I'm not understanding is why logging out or rebooting is required to keep a computer with full disk encryption secure. That's certainly not the case on competing OSes like Windows.
      - tlikonen 10y ago
        Usually in Linux the system is installed on an encrypted filesystem (cryptsetup, LUKS). Only kernel and so called initrd image (early boot stuff) is outside the encryption. The disk is opened at very early stage in boot when just about the kernel is loaded. Thus, the encryption is open whenever the operating system is running. Everything is of course still transparently encrypted on disk but the "lock" is open. One must shut down the computer to close the filesystem's encryption.
      - 10y ago

by cel1ne 10y ago

eltoozero 10y ago

Mac is my daily driver for this very reason, I'm a consultant and I need to frequently grab and go. I've had Linux on mobile for ages and have yet to have reliable sleep/wake behavior on a dozen machines over the years. Sleep on Linux works reliably if you run it inside a Mac VM though, FWIW! ;)

karussell 10y ago
Important difference: sleep usually works and is fast. What often does not work is hibernation (recover from disc)
- pmontra 10y ago
  According to a comment in the post it fails when the swap partition is encrypted. However why enable swap with 16 GB of RAM? I've been running without swap for almost 3 years and never had any trouble. If I start approaching the limit I'll buy another 16 GB.
  - karussell 10y ago
    The comment also talks about suspend to disc.
    - pmontra 10y ago
      Exactly, the comment in your blog is "suspension to disk does not work if your swap partition is encrypted. This is due to how Ubuntu encrypts your home (ecryptfs) but not due to Linux itself." I was reporting that.
- cel1ne 10y ago
  ...which is crucial since you don't want to lose your data when closing the lid. (Non-tech-term is on purpose here, since users shouldn't need to know about the difference. Also I believe OSX uses a hybrid approach).
  - karussell 10y ago
    You do not loose your data with both methods as power is used for suspend to RAM. BTW: OSX has not a "pure" suspend to disc anymore and the default method is suspend to RAM when closing the lid
    - cel1ne 10y ago
      Parent poster stated "What often does not work is hibernation (recover from disc)". Which means the user loses data.
      - karussell 10y ago
        Parent poster was me and you do not loose data. Instead it just does not go into hibernation in my case :)

aiur3la 10y ago

I don't really care about boot times, but as a tech guy 23 seconds sounds like an error to me and I want to find it and fix it :) Also, old laptops with dieing batteries (or new ones with always-on sensors such as fingerprint readers) have some leakage during sleep so it may be better to turn them off if you are not going to use them for a few days. edit: resume/suspend in linux works just fine and has done so for many years (in response to eltoozero)

karussell 10y ago
I have disabled the UEFI Network Stack (updated the article to reflect this) and now the BIOS boot time is down to ~2seconds :) !

keithpeter 10y ago

I use whole drive encryption to protect data in the event I leave my old X220 (Fedora) on the bus. I don't mind boot times in the 20s range (X220/Fedora/cheapo SSD) too much, but I do need to close down/reboot a couple of times a day otherwise no point in encryption.

blakeyrat 10y ago
> but I do need to close down/reboot a couple of times a day otherwise no point in encryption. Given, I'm not a Linux user, but I don't understand this at all. On Windows, encrypted is encrypted-- the lock screen is exactly as secure as the login screen. Are you saying that in Linux the lock screen is easily-bypassed? So you have to keep your computer logged-out when you're in a place it might get stolen?
- keithpeter 10y ago
  I believe that would be 'encrypt my home drive' on Linux, then you basically log out to protect files. Not sure though.
  - blakeyrat 10y ago
    What I'm not understanding is why logging out or rebooting is required to keep a computer with full disk encryption secure. That's certainly not the case on competing OSes like Windows.
    - tlikonen 10y ago
      Usually in Linux the system is installed on an encrypted filesystem (cryptsetup, LUKS). Only kernel and so called initrd image (early boot stuff) is outside the encryption. The disk is opened at very early stage in boot when just about the kernel is loaded. Thus, the encryption is open whenever the operating system is running. Everything is of course still transparently encrypted on disk but the "lock" is open. One must shut down the computer to close the filesystem's encryption.
    - 10y ago