Announcement

Collapse
No announcement yet.

Intel Rapid Start Being Toyed With For Linux

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Intel Rapid Start Being Toyed With For Linux

    Phoronix: Intel Rapid Start Being Toyed With For Linux

    UEFI Linux specialist Matthew Garrett is currently exploring the options for supporting Intel's Rapid Start Technology under Linux...

    http://www.phoronix.com/vr.php?view=MTQwMzU

  • #2
    Only works with ssd, however.

    Comment


    • #3
      Just let it die, like all the other intel proprietary crap that only works half the time.

      Comment


      • #4
        My SSD based laptop resumes as fast as I can open the lid, displaying the KDE lock screen. The OS is on a small 20gb SSD and the rest on a 500gb platter drive.

        Comment


        • #5
          I guess the mistake in the article is that it calls it 'suspend-resume' when it should be called hibernate (or suspend to disk vs suspend to ram).

          Suspend to ram is super fast, even on my 2004 old laptop. Hiberation, now that is slow, it first does a near full suspend, then writes the ram to swap. Booting takes longer, It has to start the bios as normal, load the kernel as normal and that then checks for the presence of the ram dump in swap and loads it.

          So speeding up hibernation can be quite interesting if that's accelerated, but only partial usefull. Suspend (to ram) is fast as it is, so 'who cares'.

          Comment


          • #6
            Originally posted by oliver View Post
            I guess the mistake in the article is that it calls it 'suspend-resume' when it should be called hibernate (or suspend to disk vs suspend to ram).
            Yeah, as far as I can tell, this is suspend-to-disk, but mostly implemented at a BIOS level instead of OS. So, like hibernate it's a complete power off rather than a sleep. But presumably the BIOS support speeds things up a lot - presumably skipping boot loaders and stuff...

            Comment


            • #7
              How would this work in a multi os set up where two systems are set to hibernat? Come to think of it what happens if you hibernate on linux installation and then try and hibernate another one.

              Comment


              • #8
                Originally posted by AJenbo View Post
                How would this work in a multi os set up where two systems are set to hibernat? Come to think of it what happens if you hibernate on linux installation and then try and hibernate another one.
                If you hibernate on linux, how would you boot to another OS?

                Comment


                • #9
                  Originally posted by dee. View Post
                  If you hibernate on linux, how would you boot to another OS?
                  I guess Rapid Start woudn't allow this as it is at the bios level, but with normal hibernation you still get the bootloader where you can pick what to boot in to. Having both a Windows and Linux installation hibernated works fine, but i think you might get some issues with two linux systems that share swap.

                  Comment


                  • #10
                    when you resume from suspend the only thing that takes a bit is the re-connection of the network.

                    Comment


                    • #11
                      I already resume from suspend in 2-3 seconds because of SSD.

                      Comment


                      • #12
                        This was a pretty poorly written article... Rapid Start is not about suspend, it's about hibernate (suspend-to-disk). Or, well, a hybrid of thereof, where suspend-to-RAM goes into hibernate after some time passes (or the battery becomes very low). So it's generally an interesting idea. And it's nice that it's already available on Linux (in a sense).

                        What's not nice is that it's all handled by the firmware. Firmware tends to be horrible as is, UEFI even more than usual. So I could see this going very wrong in many ways. There's also a need for a special partition, which is too bad, as swap is pretty much made for the same purpose.

                        Comment


                        • #13
                          Originally posted by dee. View Post
                          If you hibernate on linux, how would you boot to another OS?
                          Hibernate powers off the PC entirely. When you power it up, you get the bios, and then grub (or your bootloader of choice), where you can restart the hibernated OS, or start an other OS, or restart another hibernated OS.

                          I've done that in the past, but had many issues with the filesystem shared by the two OS, probably because the OS doesn't expect a filesystem to be changed while it hibernates (doesn't unmount, maybe even doesn't write all from cache, etc..).

                          Comment


                          • #14
                            I would like to point linux distros have a hybrid mode, you can usually invoke it from console with pm-suspend-hybrid

                            This command copies ram to disk, but instead of shutting down it goes suspend.

                            If power has not been lost (battery has not ran out), you can come back instantly. But if power has been lost, you did not lose anything and it performs the regular (albeit slower) power from hibernate situation (copy from disk back to ram).

                            This leaves Intel method unnecessary. Shouldn't hurt to just make your bios boot faster by skipping unnecessary stuff (ie. coreboot style).

                            Comment


                            • #15
                              Didn't Windows get hybrid style as well around Vista?

                              Also woudn't having this implemented at the bios generally make it slower for a normal boot (bloat)?

                              Comment

                              Working...
                              X