From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: hibernation
Date: Sat, 06 Dec 2014 08:41:18 +0100 [thread overview]
Message-ID: <16517980.BFzQ2mVHeL@andromeda> (raw)
In-Reply-To: <loom.20141205T160052-420@post.gmane.org>
On Friday, December 05, 2014 03:08:25 PM James wrote:
> Marc Stürmer <mail <at> marc-stuermer.de> writes:
> > The sad thing about hibernation is, that it has always kinda been some
> > kind of lackluster in the kernel and quite disappointing. It is a kind
> > of area which does not get much love in the kernel for at least over one
> > decade.
> >
> > So if you want to get this working reliable, good luck. You'll need it.
>
> Hibernation depends on a myriad of CPU variants, setting and the matching
> memory issues. (U)efi is a good place to start your long, arduous journey
> of research [1] ; see S4.
Not my experience, suspend-to-disk works quite well. The biggest issue was
with certain drivers not being able to re-initialize certain hardware. (Yes, I
am talking about the likes of Nvidia)
With current kernels, it does work though.
> I would research the problem and fix it with winblows as the operating
> system, if possible; then hope that those setting are not changed
> by booting linux. Often you can copy the bios setting from the laptop
> and find tools to at least view the contents legibly. It does depend
> on the bios. Maybe you need a vendor supplied bios update/downgrade.
>
> Maybe Coreboot, has some old work laying around that is relevant to
> your needs [2]. It is mostly a research journey, that may lead
> to success or failure. Hard to say, as sometimes the same make and
> model of a laptop, has diffent internal components (like firmware, bios
> and chips)...
For suspend-to-ram, I agree.
Suspend-to-disk can be handled by the OS.
--
Joost
next prev parent reply other threads:[~2014-12-06 7:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 10:32 [gentoo-user] hibernation Michael Vetter
2014-12-03 10:39 ` Randolph Maaßen
2014-12-03 12:43 ` J. Roeleveld
2014-12-03 12:50 ` Marc Stürmer
2014-12-04 16:30 ` Michael Vetter
2014-12-04 16:40 ` J. Roeleveld
2014-12-04 16:58 ` Michael Vetter
2014-12-04 17:10 ` Randolph Maaßen
2014-12-04 17:32 ` Michael Vetter
2014-12-04 18:52 ` J. Roeleveld
2014-12-06 7:38 ` J. Roeleveld
2014-12-04 21:22 ` Marc Stürmer
2014-12-05 15:08 ` [gentoo-user] hibernation James
2014-12-06 7:41 ` J. Roeleveld [this message]
2014-12-06 11:15 ` Mick
2014-12-06 13:59 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16517980.BFzQ2mVHeL@andromeda \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox