vejeta.

in chuleta · debian

Suspending and hibernating a Macbook pro with Debian Buster

Published EN

I have a Macbook pro with Debian GNU/Linux on which I was having problems when hibernating and suspending it.

The network interface it has is:

03:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03)

I have fiddled quite a lot with this laptop, repartitioning its hard disk, so it is likely that this has influenced the identifiers of the swap partitions used when hibernating.

When hibernating it:

Booting the computer again was the same as if it had not been hibernated before.

The solution was in modifying the file /etc/initramfs-tools/conf.d/resume
and correctly specifying the UUID identifier of the swap partition to use.

The identifiers can be checked in the directory:

/dev/disk/by-uuid/

Example:

  1. Check where the swap space partition is

    $ sudo fdisk -l
    .
    /dev/sda3 131602432 165154815 33552384 16G Linux swap
    .

  2. Check which is the UUID of that partition.

    $ ls -l /dev/disk/by-uuid/
    .
    lrwxrwxrwx 1 root root 10 Nov 25 14:39 db4290b0-56c2-499c-aa4a-8a4e932e9b23 -> ../../sda3
    .

  3.  Update /etc/initramfs-tools/conf.d/resume with the correct UUID.

    RESUME=UUID=db4290b0-56c2-499c-aa4a-8a4e932e9b23

 

Source: https://lists.debian.org/debian-user/2017/07/msg01074.html

When suspending it:

In this case, the main drawback I was having was that when coming back from suspension I lost the network connections, whether by ethernet cable or wirelessly over wifi.
This was forcing me to restart network-manager, and often several times in a row after coming back from a suspension.

After playing with power settings in the control panels, the interfaces files, systemd, etc…

In the end, the solution was to avoid conflicts between several network managers. In my case I chose to remove the wicd-daemon package and let network-manager take care of the connections.