Ubuntu 18.04 / Mint 19.1: Resume from hibernate not working. How to troubleshoot? [on hold]
(1) I know - frequently asked and many times answered. But the answeres I found so far do not work for me ;-(
(2) The computer(s): Thinkpad R60, Thinkpad T43, Medion-Laptop from2005 (based on MSI-250-Barebone, similar Arch to T43 (Pentium-M)) - all the same behavior:
(3) installed initially Lubuntu 18.04 32bit, but then changed to Mint 19.1 (XFCE, also 32bit). For the issue (power management, kernel) I post here I consider the system Xubuntu 18.04-equivalent. On all machines:
Mint on logical root partition (ext4), swap partition with about 150% of installed RAM, dual boot with Windows 10
Hibernate (sudo systemctl hibernate) does work: screen turns black, possibly (T43, R60) displays error concerning TPM, 10 sec HDD activity,then turns off.
Resume ends up in HDD activity, after about 20 sec.new rebott, then normal booting Linux...
on all machines: grub-commandline with added resume=UUID=.... and removed resume-file under initramfs-tools/conf.d/
(4) The question:
- what else can be wrong? How do I troubleshoot the log-files (or elsewhere)? (I am a Linux beginner I would say: basic understanding of some things, but no detailed knowledge especially on how to work with systemd etc...)
Torsten
18.04 hibernate resume
New contributor
put on hold as off-topic by Charles Green, pomsky, Organic Marble, heynnema, N0rbert 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – Charles Green, pomsky, Organic Marble, heynnema, N0rbert
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
(1) I know - frequently asked and many times answered. But the answeres I found so far do not work for me ;-(
(2) The computer(s): Thinkpad R60, Thinkpad T43, Medion-Laptop from2005 (based on MSI-250-Barebone, similar Arch to T43 (Pentium-M)) - all the same behavior:
(3) installed initially Lubuntu 18.04 32bit, but then changed to Mint 19.1 (XFCE, also 32bit). For the issue (power management, kernel) I post here I consider the system Xubuntu 18.04-equivalent. On all machines:
Mint on logical root partition (ext4), swap partition with about 150% of installed RAM, dual boot with Windows 10
Hibernate (sudo systemctl hibernate) does work: screen turns black, possibly (T43, R60) displays error concerning TPM, 10 sec HDD activity,then turns off.
Resume ends up in HDD activity, after about 20 sec.new rebott, then normal booting Linux...
on all machines: grub-commandline with added resume=UUID=.... and removed resume-file under initramfs-tools/conf.d/
(4) The question:
- what else can be wrong? How do I troubleshoot the log-files (or elsewhere)? (I am a Linux beginner I would say: basic understanding of some things, but no detailed knowledge especially on how to work with systemd etc...)
Torsten
18.04 hibernate resume
New contributor
put on hold as off-topic by Charles Green, pomsky, Organic Marble, heynnema, N0rbert 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – Charles Green, pomsky, Organic Marble, heynnema, N0rbert
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Welcome to AskUbuntu - this question will be marked as off-topic because of Mint, but.... check out https://askubuntu.com/a/821122/283721 - you may need to add a line to Grub so that Grub can find the hibernated data at boot time.
– Charles Green
2 days ago
To be slightly clearer, although you have specified the resume disk by uuid, you probably also need to specifyresume_offset=n
which locates the swapfile on the resume device.
– Charles Green
2 days ago
to Charles Green (Answer 1): I have a swap PARTITION, not file. no offset. The other parameter (telling swap partition-UUID is there. ---- to all: Yes, current install is NOT Ubuntu. But (a) the same base and (b) before the shift to Mint for other reasons I had the exact same picture on Lubuntu 18.04 (is the "L" already a problem? and (c) I hate the general habit to tell "oh that is off-topic" for minor reasons. The Linux/Debian/Ubuntu/Mint community is already scattered enough!
– Torsten
yesterday
Sadly, the 'M' is a problem, but Lubuntu is fine - I don't make the rules though, and don't know who does. But many of the same people at this site are also at Unix&Linux and there, Mint is fine.
– Charles Green
yesterday
add a comment |
(1) I know - frequently asked and many times answered. But the answeres I found so far do not work for me ;-(
(2) The computer(s): Thinkpad R60, Thinkpad T43, Medion-Laptop from2005 (based on MSI-250-Barebone, similar Arch to T43 (Pentium-M)) - all the same behavior:
(3) installed initially Lubuntu 18.04 32bit, but then changed to Mint 19.1 (XFCE, also 32bit). For the issue (power management, kernel) I post here I consider the system Xubuntu 18.04-equivalent. On all machines:
Mint on logical root partition (ext4), swap partition with about 150% of installed RAM, dual boot with Windows 10
Hibernate (sudo systemctl hibernate) does work: screen turns black, possibly (T43, R60) displays error concerning TPM, 10 sec HDD activity,then turns off.
Resume ends up in HDD activity, after about 20 sec.new rebott, then normal booting Linux...
on all machines: grub-commandline with added resume=UUID=.... and removed resume-file under initramfs-tools/conf.d/
(4) The question:
- what else can be wrong? How do I troubleshoot the log-files (or elsewhere)? (I am a Linux beginner I would say: basic understanding of some things, but no detailed knowledge especially on how to work with systemd etc...)
Torsten
18.04 hibernate resume
New contributor
(1) I know - frequently asked and many times answered. But the answeres I found so far do not work for me ;-(
(2) The computer(s): Thinkpad R60, Thinkpad T43, Medion-Laptop from2005 (based on MSI-250-Barebone, similar Arch to T43 (Pentium-M)) - all the same behavior:
(3) installed initially Lubuntu 18.04 32bit, but then changed to Mint 19.1 (XFCE, also 32bit). For the issue (power management, kernel) I post here I consider the system Xubuntu 18.04-equivalent. On all machines:
Mint on logical root partition (ext4), swap partition with about 150% of installed RAM, dual boot with Windows 10
Hibernate (sudo systemctl hibernate) does work: screen turns black, possibly (T43, R60) displays error concerning TPM, 10 sec HDD activity,then turns off.
Resume ends up in HDD activity, after about 20 sec.new rebott, then normal booting Linux...
on all machines: grub-commandline with added resume=UUID=.... and removed resume-file under initramfs-tools/conf.d/
(4) The question:
- what else can be wrong? How do I troubleshoot the log-files (or elsewhere)? (I am a Linux beginner I would say: basic understanding of some things, but no detailed knowledge especially on how to work with systemd etc...)
Torsten
18.04 hibernate resume
18.04 hibernate resume
New contributor
New contributor
edited yesterday
Torsten
New contributor
asked 2 days ago
TorstenTorsten
11
11
New contributor
New contributor
put on hold as off-topic by Charles Green, pomsky, Organic Marble, heynnema, N0rbert 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – Charles Green, pomsky, Organic Marble, heynnema, N0rbert
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by Charles Green, pomsky, Organic Marble, heynnema, N0rbert 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – Charles Green, pomsky, Organic Marble, heynnema, N0rbert
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Welcome to AskUbuntu - this question will be marked as off-topic because of Mint, but.... check out https://askubuntu.com/a/821122/283721 - you may need to add a line to Grub so that Grub can find the hibernated data at boot time.
– Charles Green
2 days ago
To be slightly clearer, although you have specified the resume disk by uuid, you probably also need to specifyresume_offset=n
which locates the swapfile on the resume device.
– Charles Green
2 days ago
to Charles Green (Answer 1): I have a swap PARTITION, not file. no offset. The other parameter (telling swap partition-UUID is there. ---- to all: Yes, current install is NOT Ubuntu. But (a) the same base and (b) before the shift to Mint for other reasons I had the exact same picture on Lubuntu 18.04 (is the "L" already a problem? and (c) I hate the general habit to tell "oh that is off-topic" for minor reasons. The Linux/Debian/Ubuntu/Mint community is already scattered enough!
– Torsten
yesterday
Sadly, the 'M' is a problem, but Lubuntu is fine - I don't make the rules though, and don't know who does. But many of the same people at this site are also at Unix&Linux and there, Mint is fine.
– Charles Green
yesterday
add a comment |
1
Welcome to AskUbuntu - this question will be marked as off-topic because of Mint, but.... check out https://askubuntu.com/a/821122/283721 - you may need to add a line to Grub so that Grub can find the hibernated data at boot time.
– Charles Green
2 days ago
To be slightly clearer, although you have specified the resume disk by uuid, you probably also need to specifyresume_offset=n
which locates the swapfile on the resume device.
– Charles Green
2 days ago
to Charles Green (Answer 1): I have a swap PARTITION, not file. no offset. The other parameter (telling swap partition-UUID is there. ---- to all: Yes, current install is NOT Ubuntu. But (a) the same base and (b) before the shift to Mint for other reasons I had the exact same picture on Lubuntu 18.04 (is the "L" already a problem? and (c) I hate the general habit to tell "oh that is off-topic" for minor reasons. The Linux/Debian/Ubuntu/Mint community is already scattered enough!
– Torsten
yesterday
Sadly, the 'M' is a problem, but Lubuntu is fine - I don't make the rules though, and don't know who does. But many of the same people at this site are also at Unix&Linux and there, Mint is fine.
– Charles Green
yesterday
1
1
Welcome to AskUbuntu - this question will be marked as off-topic because of Mint, but.... check out https://askubuntu.com/a/821122/283721 - you may need to add a line to Grub so that Grub can find the hibernated data at boot time.
– Charles Green
2 days ago
Welcome to AskUbuntu - this question will be marked as off-topic because of Mint, but.... check out https://askubuntu.com/a/821122/283721 - you may need to add a line to Grub so that Grub can find the hibernated data at boot time.
– Charles Green
2 days ago
To be slightly clearer, although you have specified the resume disk by uuid, you probably also need to specify
resume_offset=n
which locates the swapfile on the resume device.– Charles Green
2 days ago
To be slightly clearer, although you have specified the resume disk by uuid, you probably also need to specify
resume_offset=n
which locates the swapfile on the resume device.– Charles Green
2 days ago
to Charles Green (Answer 1): I have a swap PARTITION, not file. no offset. The other parameter (telling swap partition-UUID is there. ---- to all: Yes, current install is NOT Ubuntu. But (a) the same base and (b) before the shift to Mint for other reasons I had the exact same picture on Lubuntu 18.04 (is the "L" already a problem? and (c) I hate the general habit to tell "oh that is off-topic" for minor reasons. The Linux/Debian/Ubuntu/Mint community is already scattered enough!
– Torsten
yesterday
to Charles Green (Answer 1): I have a swap PARTITION, not file. no offset. The other parameter (telling swap partition-UUID is there. ---- to all: Yes, current install is NOT Ubuntu. But (a) the same base and (b) before the shift to Mint for other reasons I had the exact same picture on Lubuntu 18.04 (is the "L" already a problem? and (c) I hate the general habit to tell "oh that is off-topic" for minor reasons. The Linux/Debian/Ubuntu/Mint community is already scattered enough!
– Torsten
yesterday
Sadly, the 'M' is a problem, but Lubuntu is fine - I don't make the rules though, and don't know who does. But many of the same people at this site are also at Unix&Linux and there, Mint is fine.
– Charles Green
yesterday
Sadly, the 'M' is a problem, but Lubuntu is fine - I don't make the rules though, and don't know who does. But many of the same people at this site are also at Unix&Linux and there, Mint is fine.
– Charles Green
yesterday
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Welcome to AskUbuntu - this question will be marked as off-topic because of Mint, but.... check out https://askubuntu.com/a/821122/283721 - you may need to add a line to Grub so that Grub can find the hibernated data at boot time.
– Charles Green
2 days ago
To be slightly clearer, although you have specified the resume disk by uuid, you probably also need to specify
resume_offset=n
which locates the swapfile on the resume device.– Charles Green
2 days ago
to Charles Green (Answer 1): I have a swap PARTITION, not file. no offset. The other parameter (telling swap partition-UUID is there. ---- to all: Yes, current install is NOT Ubuntu. But (a) the same base and (b) before the shift to Mint for other reasons I had the exact same picture on Lubuntu 18.04 (is the "L" already a problem? and (c) I hate the general habit to tell "oh that is off-topic" for minor reasons. The Linux/Debian/Ubuntu/Mint community is already scattered enough!
– Torsten
yesterday
Sadly, the 'M' is a problem, but Lubuntu is fine - I don't make the rules though, and don't know who does. But many of the same people at this site are also at Unix&Linux and there, Mint is fine.
– Charles Green
yesterday