On 03/19/2016 06:20 PM, Aaron Digulla wrote:
Am 17.03.2016 um 13:04 schrieb Anton Aylward:
regular readers will recall that I've
I'm on 13.1 and few leading repositories, one of which is Kernel_Stable.
I'm on 13.2 and updated 4.5.0-2.2 and I'm not so happy with it.
With 4.4 and 4.5, suspend is broken in some odd way. The machine will
suspend once. When I suspend again, it will crash during resume.
That doesn't sound like "suspend to RAM" so much as "hibernate to
The power-management scripts use these terms:
suspend -- suspend to ram; some folks call this "sleep"
resume -- restart after suspend to ram; does not use grub
hibernate -- suspend to disk; includes power-off, looks like shutdown
thaw -- restart after suspend to disk; includes a trip through grub
might be because of a weird grub2 issue where grub will select the
second entry (advanced options) and then the second entry in that menu.
If GRUB is involved then its "hibernate-to-disk".
Perhaps the problem is that you're using hibernate when you ought to be
Which gets back to 'use case'. Is this just shutting the laptop lid
when going off to the bathroom or to get a coffee refill?
Or are you closing the laptop down for the night and expect to restart
exactly where you were again in the morning?
Well, I use KDE4 and I can run "shutdown -h -P now" and when I log in
the next morning KDE4 brings up exactly the same set of applications.
The downside is that if I had a LibreOffice document open its not open
again at the same place, if I had a ssh session its not open to the
remote machine again. But since 98% of the time its mail and browser
and file manager and a bunch of terminal sessions under Konsole, that's OK.
1% of the time its something like LibreOffice or some other editor where
I can "open last document" in a couple of clicks.
If, as you imply, this is a gaming laptop, and you want to continue
where you left off in the game then I really think you're talking about
"suspend to RAM". Or should be. In which case grub etc is irrelevant
and "you're doing it all wrong".
Which means I suspend with 4.5 and then Grub happily
boots into 4.4 ...
Now how did you get to that.
But it also fails when I manually select the first
option of the Grub2
menu. So there must be another issue somewhere.
Are you talking 'always'?
Then there's something wrong with that entry.
you'd have to give us details.
It may simply be that some file is missing or there is a typo.
A minor annoyance is that the computer doesn't
power down after suspend.
I have to flip the switch.
We're back to the 'suspend' vs 'hibernate' issue.
Have you tried this manually with and without the GUI running, that is
in each of:
# systemctl isolate graphical.target
# systemctl isolate multi-user.target
running from a VT as root
Recall that suspend stops operation of all applications and system state
is saved in RAM, the machine go into a low-power mode, in this state,
the system still requires power . Various triggers can resume the
machine, among them pressing a key or quickly pressing and releasing the
Recall that hibernate Moves the contents of memory into swap, tells the
bootloader to boot directly into the appropriate kernel, and shuts the
machine down, in this state, the system does not require power. You turn
on the machine by powering up, which causes the kernel to reload the
contents of memory from swap.
There is a reason I ask you to try this with and without the GUI.
Suspending and saving the contents of the graphical card is quite
another matter! The larger, the more powerful the card, the more
involved (aka complex, aka problem prone) it will be for both these
Q: Are you sure?
> A: Because it reverses the logical flow of conversation.
>> Q: Why is top posting frowned upon?
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org