Hibernate doesn't wake-up properly

Occasionally, a very modern BIOS has a setting as follows:

  • “BIOS Boot Setting: Windows UEFI/Other OS”

AFAICS, “Other OS” doesn’t mean “EFI without MS Windows” – it means “Support for legacy operating systems, such as Windows 7” – IOW: no EFI

  • The EFI we’re using has been “accepted” by Redmond …

The openSUSE Leap 15.2 Kernel initialises LSM:


 > cat /sys/kernel/security/lsm 
lockdown,capability,apparmor > 

“lockdown” is output in the string – therefore the lockdown mode is being enforced …
[HR][/HR]Bottom line:

  • The systemd Journal doesn’t tell lies – when “kernel: Kernel is locked down from EFI Secure Boot mode” appears in the system Journal, guess what:
    [LIST]
  • The Kernel is locked down …

[/LIST]

I have the same output, I’ll consider kernel lockdown is enable, even if I can’t see it in the log file.
Now, how can I boot with lockdown disable?

If the systemd Journal is not indicating that, the Kernel is locked down, guess what – it ain’t locked down …

  • Despite that fact that, it could be locked down if, and only if, the EFI prerequisites were being met.
  • ‘/sys/kernel/security/lsm’ is only indicating that, LSM has been correctly initialised …

There’s no need for you to force anything – it seems that, your system doesn’t support a locked down Kernel …
[HR][/HR] You need to execute “lsblk --fs” to work out which device has the swap partition on it.
Then you need to execute “fdisk -l /dev/sd??” on the swap device to see how large the swap partition is.
Alternatively, “swapon --show” and “cat /proc/swaps” will in addition indicate if swapping is enabled and, how much swap space is being used.
“inxi --memory” indicates how much physical memory is present on the machine – if it’s being executed by the user “root” …

  • If the size of the swap partition is less than the amount of physical memory on the machine, you can not resume from hibernation …

That’s often called “CSM” (or “compatibility support module”).

You can turn it off with

mokutil --disable-validation

No, there are two different settings…

The UEFI setup:

There is just after that a button to set keys; PK, KEK, db, dbx
I didn’t set that because I don’t have any clue what it is.

> mokutil --sb-state
SecureBoot disabled
Platform is in Setup Mode
> mokutil --list-enrolled
MokListRT is empty

Obviously secure-boot is not enabled.

mokutil --disable-validation
password length: 8~16
input password: 

I’d guess this is a new password asked here. I don’t want to set a password I will forget as I never use this parameter

Short summing-up:

  • SecureBoot is disabled
  • Kernel lockdown is disabled
  • Hibernation can’t wakeup properly

I am lost, could you help me to get hibernation working, I don’t care about other setting, maybe the motherboard is too old.

The password requested is a one-time password. You will need it at the next boot, but never again after that. So no worries about forgetting.

However, you have secure-boot disabled, so there isn’t any point to doing that anyway.

After some experiments:
In the UEFI, only - Opensuse-secureboot works with or without Secure Boot: - Enabled. In both cases hibernation fail to wakeup properly.

It looks like I can’t get secure-boot enable, I don’t know why.

As I don’t know what to do now, I’ll leave as it is and never use hibernation. I hope there will be announcement in case this issue is fixed.

Thanks for your help

You originally indicated that, “free” is reporting that your system has 8 GiB memory and, 8 GiB swap allocation on disk.

  • But, “free” is only reporting the amount of RAM available for system use, which isn’t the same as the amount of physical memory on the system.
  • “inxi -a -m” – when executed by the user “root” – also reports the amount of physical memory on the system.
  • Linux uses some of the physical memory to cache the Kernel – which means that, the amount of RAM being reported by “free”, is often less than the amount of memory which will be written to the Swap space when the system hibernates …
inxi -am

and

inxi

works Ok without root permissions - I can see amount of RAM.

Linux can hibernate if used amount of RAM is smaller than swap file.


 > inxi -am
Memory:    RAM: total: 13.56 GiB used: 2.88 GiB (21.2%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
 > 


 # inxi -am
Memory:    RAM: total: 13.56 GiB used: 2.89 GiB (21.3%) 
           Array-1: capacity: 128 GiB slots: 4 EC: None max module size: 32 GiB note: est. 
           Device-1: DIMM_A1 size: No Module Installed 
           Device-2: DIMM_A2 size: 8 GiB speed: 2933 MT/s type: DDR4 detail: synchronous unbuffered (unregistered) 
           bus width: 64 bits total: 64 bits manufacturer: G-Skill part-no: F4-3200C16-8GIS serial: N/A 
           Device-3: DIMM_B1 size: No Module Installed 
           Device-4: DIMM_B2 size: 8 GiB speed: 2933 MT/s type: DDR4 detail: synchronous unbuffered (unregistered) 
           bus width: 64 bits total: 64 bits manufacturer: G-Skill part-no: F4-3200C16-8GIS serial: N/A 
 # 

The machine has two 8 GiB modules installed – 16 GiB.

  • But, “only” 13.56 GiB RAM is available for executable code …
  • The rest is being used by the Kernel for a RAM disk …
systemd[1]: Running in initial RAM disk.

Some of the memory goes to graphics

> sudo inxi -am
Memory:    RAM: total: 7.72 GiB used: 1.55 GiB (20.1%) 
           Array-1: capacity: 32 GiB slots: 4 EC: None max module size: 8 GiB note: est. 
           Device-1: A1_DIMM0 size: No Module Installed 
           Device-2: A1_DIMM1 size: 4 GiB speed: 1600 MT/s type: DDR3 detail: synchronous unbuffered (unregistered) 
           bus width: 64 bits total: 64 bits manufacturer: Corsair part-no: CMZ8GX3M2A1600C9 serial: N/A 
           Device-3: A1_DIMM2 size: No Module Installed 
           Device-4: A1_DIMM3 size: 4 GiB speed: 1600 MT/s type: DDR3 detail: synchronous unbuffered (unregistered) 
           bus width: 64 bits total: 64 bits manufacturer: Corsair part-no: CMZ8GX3M2A1600C9 serial: N/A 

> sudo swapon -s
Filename                Type        Size    Used    Priority
/dev/sda3               partition    8398844    0    -2

I’d guess this is not the issue.