Hello,
on my just installed ( days ago) leap, I wanted to test hibernation.
so on this morning, I clicked "hibernate" after a great while (went to coffe), the computer was still running, but the screen was back. I had to switch it off to regain control and, now, each time I try to launch leap I get this black screen again and again.
Here I'm writing from my good old (same computer) :-)
Leap is on a ssd, 8Gb swap
what can I do to recover? I don't find anything relevant on google
thanks jdd
Try to turn it off, remove battery and leave it for some time.
On Fri, Dec 25, 2015 at 4:32 PM, jdd jdd@dodin.org wrote:
Hello,
on my just installed ( days ago) leap, I wanted to test hibernation.
so on this morning, I clicked "hibernate" after a great while (went to coffe), the computer was still running, but the screen was back. I had to switch it off to regain control and, now, each time I try to launch leap I get this black screen again and again.
Here I'm writing from my good old (same computer) :-)
Leap is on a ssd, 8Gb swap
what can I do to recover? I don't find anything relevant on google
thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
25.12.2015 18:19, jdd пишет:
Le 25/12/2015 14:56, Andrei Borzenkov a écrit :
Try to turn it off, remove battery and leave it for some time.
it's a desktop, no battery :-(
In this case try removing coin battery to clear NVRAM; may be your motherboard has some other means (DIP switches, jumper).
Le 25/12/2015 16:45, Andrei Borzenkov a écrit :
25.12.2015 18:19, jdd пишет:
Le 25/12/2015 14:56, Andrei Borzenkov a écrit :
Try to turn it off, remove battery and leave it for some time.
it's a desktop, no battery :-(
In this case try removing coin battery to clear NVRAM; may be your motherboard has some other means (DIP switches, jumper).
that would remove all setup, I would try to avoid this.
thanks jdd
Le 25/12/2015 14:32, jdd a écrit :
what can I do to recover? I don't find anything relevant on google
I could solve the problem myself and I'm back with leap. That is I could recover Leap, I wont even try again to hibernate!
the solution is: access your /etc/fstab by any mean...
add a # in front of any swap line
reboot, you should be ok. Then reactivate swap and stop normally.
Doing this I noticed some very curious things.
I had *three* swap files. in se this is not surprising, I have three disks and so three swap partitions. That said I created one on my ssd at install time and expected it to be used alone. May be I have to look better at the install report Yast do just before installing :-(.
But this is only the normal thing.
The third swap line is to an uuid.. of what? it's *not* the uuid of my swap partition (I get with blkid), and findfs do not return any disk ID/device, it only return the uuid given as argument.
ls /dev/disk/by-uuid/
do not show any partition with this uuid.
So what can I guess? may be the hibernate process gives a transient uuid to the swap space chosen for hibernation? does it *change* the uuid? In my fstab I had not as swap my last created one (the one on the new sssd).
is so where does the hibernate system store the initial uuid (I guess it's restored if all goes well)
thanks jdd
-
Andrei Borzenkov -
jdd