Re: Issues resuming from hibernation
Hi solitone,
You might want to consider, to not longer put the computer to
hibernation, but to use suspend. This way, you will not have to store
the memory state to harddisk, instead the RAM will stay on battery
power.
This state [I have a PC], is ACPI and the command to put the computer
sleeping is 'systemctl suspend'.
This way, you can make sure, if the loss of network connectivity has to
do with suspending RAM to harddisk, or not.
My laptop can stay suspended this way for several days. I would not be
surprised the problems you have, will go away this way. [I write this
because I am not surprised that most users can put their computer to
hibernate, and some don't] Suspending to RAM is safer bet, for a
computer to being able to restore everything.
Since systemctl is from systemd, I suspect that the command I just
wrote, will work for you.
For the Wi-fi adapter, I recommend, if you didn't have so already, to
use Gnome networkmanager [installer is named 'network-manager'] See;
https://boundarydevices.com/wp-content/uploads/2015/03/Screenshot-03032015-122125-PM2.png
If you really need to hibernate instead of suspending, I can't be of
much help. I have my reasons to prefer suspending over hibernation.
However, I would look in to 'pm-utils' which has;
/usr/sbin/pm-hibernate
/usr/sbin/pm-powersave
/usr/sbin/pm-suspend
/usr/sbin/pm-suspend-hybrid
If you already have 'pm-utils', which I'm not sure of, but for network
connections and suspending/ hibernating, different tools exist, so I
told this, to complete my answer to you issue.
Good luck.
--
Richard Waterbeek <richardwbb@versatel.nl>
solitone schreef op vr 23-12-2016 om 21:33 [+0100]:
> I've got a debian stretch installation on a MacBookPro 12,1 (Retina, Early
> 2015). When I resume the system from hibernation, the Wi-Fi adapter doesn't
> work any longer. I need to reboot the system to have it work again.
>
> Besides, performance in general is pretty bad after resume. The system is not
> responsive--e.g. windows in the desktop environment take tens of seconds to
> open.
>
> I've got a 7.5 GB swap partition (7812496 KiB), and 7.7 GiB of memory (8079104
> KiB)--actually I chose 8 GB for swap during disk partitioning, but I didn't
> get what I wanted, perhaps because of the giga vs. giga-binary thing.
>
> After a first installation attempt, where I had just 3 or something GB of swap,
> resume after hibernation didn't work at all. I got messages like the
> following:
>
> PM: Image loading progress: 0%
> PM: Image loading progress: 10%
> PM: Image loading progress: 20%
> PM: Image loading progress: 30%
> PM: Image loading progress: 40%
>
> and then a black screen.
>
> So I repartitioned the disk, increasing the swap partition, and reinstalled.
> Now the system does start from hibernation, but there are the issues I
> mentioned.
>
> I hope it's not related to a swap partition slightly falling short of RAM.
> Reinstallation is not an option now!
>
> Please let me know what information I should provide, so that you can tell me
> what I need to analyze.
>
> Thanks!
>
Reply to: