[SOLVED] Hibernation does not work MGA9

[maluethy]

The power saving mode hibernation did not work on my PC with Mageia 8. Therefore I had written a forum post and applied the instructions from Errata. The hibernation mode worked after that.
https://forums.mageia.org/en/viewtopic.php?f=7&t=14683
https://wiki.mageia.org/en/Mageia_8_Errata#Hibernation

Now I have new installed Mageia 9 on the computer. Hibernation does not work after the new installation. In the Errata of Mageia 9 I do not find a corresponding entry. Can I use the instructions from the Errata of Mageia 8 also with Mageia 9? I tried it on a test installation. The hibernation worked afterwards also under Mageia 9.
https://wiki.mageia.org/en/Mageia_9_Errata

Thanks in advance for the information.

[morgano]

Many thanks for the feedback.

I have now entered a shortened fix, tested OK by two users in the bug.
https://wiki.mageia.org/en/Mageia_9_Errata#Hibernation

Please try and report back.

[isadora]

Thanks for the tests and the prompt feedback.

I have applied the longer version of the instructions according to the errata in Mageia 9. The standby and hibernation do not work despite applying the errata.

If I enter the first step again after applying the errata "cat /etc/dracut.conf.d/51-mageia-resume.conf", the output on the console is following:

Code: Select all

[root@localhost ~]# su -
[root@localhost ~]# cat /etc/dracut.conf.d/51-mageia-resume.conf
add_device+=" UUID=a176884a-4322-4e57-8f5a-bd79721a0fda "
add_dracutmodules+=" resume "
[root@localhost ~]#

When executing steps 2 and 3 of the errata, the console output shows, among other things, a message that something could not be mounted (a USB stick was inserted in the computer, otherwise no other media besides the internal SSD). However, a lot of lines appear relatively quickly, so I can only partially read them. For this, unfortunately, I can't scroll back or save the whole output on the console (I use the standard console of Plasma. Are there consoles that can keep the whole output or save the whole output?).

I have two identical computers. On computer A I had installed Mageia 9. I wanted to reinstall Mageia 9 again (The reinstallation of Mageia 9 Final Release was already some days ago. Before that, probably Mageia 9 RC1 was installed on the computer). Before the reinstallation, the Mageia_8_Errata#Hibernation came to my mind. I applied this to the Mageia 9 computer and hibernation worked after that (without customization, hibernation did not work. I don't remember the standby). So it surprises and irritates me that standby and hibernation do not work now with the application of the errata. - When reinstalling Mageia, I let the installation tool reformat the SSD and install Mageia 9 with the Plasma UI and minimal package selection.

I don't really know how to test the power management. So far I had activated the standby or hibernation mode and if the computer did not start afterwards, pressed the power button for a few seconds, waited and then restarted the computer. What do these crashes do to the Mageia operating system (risk of it not starting, not working, or data garbage accumulating)? Is there a test tool to test or read the power management? Is it better to reinstall the Mageia operating system at the end of the tests, so that it does not come to instabilities because of it?

[doktor5000]

For this, unfortunately, I can't scroll back or save the whole output on the console (I use the standard console of Plasma. Are there consoles that can keep the whole output or save the whole output?).

Why not ? The default scrollback in konsole is 1000 lines.
You can easily change this to unlimited. settings > edit current profile > scrolling > scrollback: unlimited.
You can also omit option -v when running dracut, that is verbose output and not necessary but generates a lot more output.

I don't really know how to test the power management. So far I had activated the standby or hibernation mode and if the computer did not start afterwards, pressed the power button for a few seconds, waited and then restarted the computer. What do these crashes do to the Mageia operating system (risk of it not starting, not working, or data garbage accumulating)? Is there a test tool to test or read the power management? Is it better to reinstall the Mageia operating system at the end of the tests, so that it does not come to instabilities because of it?

You can trigger either standby or hibernation with the following commands:

Code: Select all

systemctl suspend # (standby)

Code: Select all

systemctl suspend-then-hibernate #(this is a hybrid mode as the name says)

Code: Select all

systemctl hibernate #(hibernate)

If you simply reboot after either standby or reboot, no garbage data accumulates.
For standby, you loose everything that was in RAM at the time you triggered the standby.
When hibernated, you can't reboot as the box is already powered off when hibernated. Next time you start, it tries to resume that hibernated state which is saved on disk (you configure from which device in /etc/dracut.conf.d/51-mageia-resume.conf, this points to your swap partition/filesystem/LV) with the kernel option resume=UUID=a176884a-4322-4e57-8f5a-bd79721a0fda in your case.

[maluethy]

Today I received updates from Mageia on both computers (something like 6.4.9-desktop to 6.4.16-desktop). Following the forum reply above, I tried standby and hibernation mode again and both worked successfully (I made no changes to the system). I am very happy about that.

Thanks for the explanations about the console. I found the setting and was able to adjust it.

Thanks for the information on standby and hibernation mode. It helps me to assess the effects of the tests I have done.

Thanks for the commands to trigger standby or hibernation. Are there also commands to see the hardware support of ACPI? I tried to check with the tool Hardinfo (it's in the Mageia software database), but I didn't find any info about ACPI.
https://alternativeto.net/software/hardinfo/about/

Is it possible to read the ACPI support of hardware in Mageia? I found commands to do this on a website (acpi_available), but I can't successfully use them in Mageia. Is it not possible or do I understand something wrong?
https://www.geeksforgeeks.org/acpi_available-command-in-linux-with-examples

Is the problem described in the errata due to a missing entry or the lack of ACPI support? If it is due to a missing entry, does a query for ACPI support show the problem?

[doktor5000]

The entry in the errata is not related to ACPI support at all, maybe you're misunderstanding or there's some confusion.
If you want to check ACPI support, you can use the acpitool command (contained in the package of the same name) to query various parts of ACPI support.

For the errata entry, that is only ever relevant for hibernation, as if you'd be missing the resume support in initrd for some more exotic setups (if swap is on LVM or an encrypted partition e.g.).
It should also not be necessary anymore and should not be in the errata, see the comment on the quoted bug report: https://bugs.mageia.org/show_bug.cgi?id=28528#c25 and the later replies from Martin.

[morgano]

It should also not be necessary anymore and should not be in the errata, see the comment on the quoted bug report: https://bugs.mageia.org/show_bug.cgi?id=28528#c25 and the later replies from Martin.

In comment 41 & 42 two different users hit the problem and solve it by what is in errata 9.

[maluethy]

Doctor5000 thank you for the further explanations. Regarding the hibernation errata entry, I confused something with ACPI support.

Without the hibernation errata entry, hibernation probably wouldn't work on either of my computers (It certainly didn't on a previous fresh install with probably MGA 9 RC1. Hibernation only worked with the errata entry). - I install Mageia 9 with Plasma using UEFI without Secure Boot and the default formatting from the Classic installer ISO (no encryption of the SSD). - Why hibernation did not work during the last fresh install of Mageia 9 after applying the errata entry and now works after yesterday's update (6.4.9-desktop to 6.4.16-desktop), I cannot understand. I lack Linux knowledge and knowledge about these updates.

[doktor5000]

In comment 41 & 42 two different users hit the problem and solve it by what is in errata 9.

I don't think you read the comments thoroughly, see e.g. https://bugs.mageia.org/show_bug.cgi?id=28528#c36 and the followup comment - that user does not have the workaround (not fix) from the errata and hibernation still works.

Also check the previous comment: https://bugs.mageia.org/show_bug.cgi?id=28528#c35

"something something hibernation does not work" should NOT be munched all in the same bugreport as the causes in that bugreport are also quite different.

[morgano]

Yes maybe different causes.
Anyway the remedy now in Errata works for some users for the named symptom.

So let the description (symptom, remedy) in Errata stand, but omit the bug reference?

[doktor5000]

I don't know, AFAICT it simply hides another bug because the original one has been fixed by Martin before mga9 released.
Should probably be troubleshooted separately before people apply the workaround from the errata (where the only effective part is running dracut -f)

[morgano]

Closed that bug, updated errata.