[SOLVED]Forgot swap partition when I did the install, suspend/resume not working

Forum Forums General Software [SOLVED]Forgot swap partition when I did the install, suspend/resume not working

  • This topic has 6 replies, 4 voices, and was last updated May 27-10:24 am by BobC.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #22073
    Moderator
    BobC

      I can create a swap partition with gparted, but how do I get the system to use it to suspend and resume? I am running 17.4.1 Full 64 bit on this machine.

      Thanks for any help…

      • This topic was modified 3 years, 11 months ago by BobC.
      #22080
      Moderator
      caprea
        Helpful
        Up
        0
        ::

        Hi BobC, did you create an entry in /etc/fstab for the newly created swap-partition?

        eg. part of my /etc/fstab

        # Pluggable devices are handled by uDev, they are not in fstab
        UUID=41fff33b-ef6d-48b4-bfd1-8435c76f3c5a / ext4 defaults,noatime 1 1
        UUID=576eb5a9-c73e-4846-9d66-bc4547026eae swap swap defaults 0 0 
        #-> /dev/sda1  label=rootantiX17.2
        UUID=55ad088c-da3f-48ef-8cc0-2388762cb664  /media/rootantiX17.2                        ext4       noauto,exec,users               0 0
        #-> /dev/sda2  label=rootMX18.1
        UUID=3e980b39-be42-461a-b500-760a6c111eb5  /media/rootMX18.1                           ext4       noauto,exec,users               0 0

        You can look for the UUID of your swap with

        sudo blkid /dev/sdaX

        where X is your swap-partition.

        #22083
        Member
        fatmac
          Helpful
          Up
          0
          ::

          Remember to make it equal or greater than the amount of your ram. 😉

          Linux (& BSD) since 1999

          #22094
          Forum Admin
          dolphin_oracle
            Helpful
            Up
            0
            ::

            once the swap partition is created, you can use

            make-fstab -s

            to add swap entry to your fstab automatically.

            then you will need to update the initramfs to tell the system where the resume partition is.

            sudo update-initramfs -u -k all

            should do the trick.

            If that doesn’t work, you will want to add a “resume=path_to_swap” boot code to your /etc/default/grub and then do a

            sudo update-grub

            to apply that change.

            • This reply was modified 3 years, 11 months ago by dolphin_oracle.
            #22096
            Moderator
            BobC
              Helpful
              Up
              0
              ::

              I have tried everything last night, except the -k all parameters that DO suggested, which I will try now. Thanks for all the replies everyone. Here is a pic showing all the current settings.

              Attachments:
              #22104
              Moderator
              BobC
                Helpful
                Up
                0
                ::

                FYI, my old HP laptop from 2006/2007 died recently, which is why I moved to the now 3 year old ridiculously fast Dell Inspiron I7-7559. Well why wasn’t I using it all along? Because I LOATHE Windoze 10, and because Linux has always had problems on the Dell since the day it was new. I read today that its a firmware issue with many of the newer machines with acpi.

                As I recall, Back when it was new, I spent weeks trying about 10 different kernels to eventually find one that worked with weird boot command line tweaks to be able to run the silly 4k Optimus video and suspend and resume and not be locking up all the time, all at the same time. I guess even with the newer BIOS and newer kernels the problem was never resolved. Anyway, I’m able to run and suspend now, but resuming is hopeless. I guess I will try all the kernels and tweaks that I can find again.

                #22108
                Moderator
                BobC
                  Helpful
                  Up
                  0
                  ::

                  Yup, that fixed it on the first try. Luckily I remembered that the kernel that worked once upon a time was 4.9.0-5.

                  Thanks everyone for pitching in and sorry for causing my own problems by not investigating better before I bought the machine…

                  PS: I just tried Anti’s new 5.1.5 kernel, and its working just fine with my 4.9.0-5 boot codes, and I’m able to suspend, suspend-hybrid, hibernate, and resume now, without any problems.

                  THANKS!

                  • This reply was modified 3 years, 11 months ago by BobC.
                Viewing 7 posts - 1 through 7 (of 7 total)
                • You must be logged in to reply to this topic.