Lenovo Ideapad 720S can't resume from suspend on 18.04 [duplicate]
up vote
0
down vote
favorite
This question already has an answer here:
How can I figure out why Suspend sometimes fails?
2 answers
My PC is a Lenovo Ideapad 720S with Windows 10 and Ubuntu 18.04 installed. This PC can't resume from suspend.
How can I fix this?
18.04 suspend
edited Nov 28 at 16:49
Zanna
49.3k13127236
asked Nov 27 at 15:03
kgyk
11
marked as duplicate by abu_bua, Fabby, RoVo, Eric Carvalho, Thomas Dec 1 at 9:31
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
0
down vote
favorite
This question already has an answer here:
How can I figure out why Suspend sometimes fails?
2 answers
My PC is a Lenovo Ideapad 720S with Windows 10 and Ubuntu 18.04 installed. This PC can't resume from suspend.
How can I fix this?
18.04 suspend
edited Nov 28 at 16:49
Zanna
49.3k13127236
asked Nov 27 at 15:03
kgyk
11
marked as duplicate by abu_bua, Fabby, RoVo, Eric Carvalho, Thomas Dec 1 at 9:31
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
1
Edit your question to include the output offree -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resume. Use the{}to pretty-fy the text. Report back to @heynnema
– heynnema
Nov 27 at 15:26
Not sure about closing this as there might be a specific reason for the hardware, but the suggested target is nowhere near as good as How to debug suspend? if anyone wants to add it
– Zanna
Nov 28 at 16:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This question already has an answer here:
How can I figure out why Suspend sometimes fails?
2 answers
My PC is a Lenovo Ideapad 720S with Windows 10 and Ubuntu 18.04 installed. This PC can't resume from suspend.
How can I fix this?
18.04 suspend
edited Nov 28 at 16:49
Zanna
49.3k13127236
asked Nov 27 at 15:03
kgyk
11
This question already has an answer here:
How can I figure out why Suspend sometimes fails?
2 answers
My PC is a Lenovo Ideapad 720S with Windows 10 and Ubuntu 18.04 installed. This PC can't resume from suspend.
How can I fix this?
This question already has an answer here:
How can I figure out why Suspend sometimes fails?
2 answers
18.04 suspend
18.04 suspend
edited Nov 28 at 16:49
Zanna
49.3k13127236
asked Nov 27 at 15:03
kgyk
11
edited Nov 28 at 16:49
Zanna
49.3k13127236
asked Nov 27 at 15:03
kgyk
11
edited Nov 28 at 16:49
Zanna
49.3k13127236
edited Nov 28 at 16:49
Zanna
49.3k13127236
edited Nov 28 at 16:49
Zanna
49.3k13127236
49.3k13127236
asked Nov 27 at 15:03
kgyk
11
asked Nov 27 at 15:03
kgyk
11
asked Nov 27 at 15:03
kgyk
11
11
marked as duplicate by abu_bua, Fabby, RoVo, Eric Carvalho, Thomas Dec 1 at 9:31
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by abu_bua, Fabby, RoVo, Eric Carvalho, Thomas Dec 1 at 9:31
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
1
Edit your question to include the output offree -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resume. Use the{}to pretty-fy the text. Report back to @heynnema
– heynnema
Nov 27 at 15:26
Not sure about closing this as there might be a specific reason for the hardware, but the suggested target is nowhere near as good as How to debug suspend? if anyone wants to add it
– Zanna
Nov 28 at 16:51
add a comment |
1
Edit your question to include the output offree -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resume. Use the{}to pretty-fy the text. Report back to @heynnema
– heynnema
Nov 27 at 15:26
Not sure about closing this as there might be a specific reason for the hardware, but the suggested target is nowhere near as good as How to debug suspend? if anyone wants to add it
– Zanna
Nov 28 at 16:51
1
1
Edit your question to include the output of
free -h and sudo blkid and cat /etc/fstab and cat /etc/initramfs-tools/conf.d/resume. Use the {} to pretty-fy the text. Report back to @heynnema– heynnema
Nov 27 at 15:26
Edit your question to include the output of
free -h and sudo blkid and cat /etc/fstab and cat /etc/initramfs-tools/conf.d/resume. Use the {} to pretty-fy the text. Report back to @heynnema– heynnema
Nov 27 at 15:26
Not sure about closing this as there might be a specific reason for the hardware, but the suggested target is nowhere near as good as How to debug suspend? if anyone wants to add it
– Zanna
Nov 28 at 16:51
Not sure about closing this as there might be a specific reason for the hardware, but the suggested target is nowhere near as good as How to debug suspend? if anyone wants to add it
– Zanna
Nov 28 at 16:51
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You may be resumed but have black screen video failure. System is running, you cannot see. That has been happening to me lately.
Avoid using power button restart. Drive may get corrupted if it is running and you kill with button.
I get another computer and SSH into the one that seems dead. Then trigger restart with
sudo /sbin/shutdown -r now
This assumes you know IP number of frozen computer.
edited Nov 28 at 16:49
Zanna
49.3k13127236
answered Nov 28 at 4:22
pauljohn32
2,199822
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You may be resumed but have black screen video failure. System is running, you cannot see. That has been happening to me lately.
Avoid using power button restart. Drive may get corrupted if it is running and you kill with button.
I get another computer and SSH into the one that seems dead. Then trigger restart with
sudo /sbin/shutdown -r now
This assumes you know IP number of frozen computer.
edited Nov 28 at 16:49
Zanna
49.3k13127236
answered Nov 28 at 4:22
pauljohn32
2,199822
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
add a comment |
up vote
0
down vote
You may be resumed but have black screen video failure. System is running, you cannot see. That has been happening to me lately.
Avoid using power button restart. Drive may get corrupted if it is running and you kill with button.
I get another computer and SSH into the one that seems dead. Then trigger restart with
sudo /sbin/shutdown -r now
This assumes you know IP number of frozen computer.
edited Nov 28 at 16:49
Zanna
49.3k13127236
answered Nov 28 at 4:22
pauljohn32
2,199822
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
add a comment |
up vote
0
down vote
up vote
0
down vote
You may be resumed but have black screen video failure. System is running, you cannot see. That has been happening to me lately.
Avoid using power button restart. Drive may get corrupted if it is running and you kill with button.
I get another computer and SSH into the one that seems dead. Then trigger restart with
sudo /sbin/shutdown -r now
This assumes you know IP number of frozen computer.
edited Nov 28 at 16:49
Zanna
49.3k13127236
answered Nov 28 at 4:22
pauljohn32
2,199822
You may be resumed but have black screen video failure. System is running, you cannot see. That has been happening to me lately.
Avoid using power button restart. Drive may get corrupted if it is running and you kill with button.
I get another computer and SSH into the one that seems dead. Then trigger restart with
sudo /sbin/shutdown -r now
This assumes you know IP number of frozen computer.
edited Nov 28 at 16:49
Zanna
49.3k13127236
answered Nov 28 at 4:22
pauljohn32
2,199822
edited Nov 28 at 16:49
Zanna
49.3k13127236
edited Nov 28 at 16:49
Zanna
49.3k13127236
edited Nov 28 at 16:49
Zanna
49.3k13127236
49.3k13127236
answered Nov 28 at 4:22
pauljohn32
2,199822
answered Nov 28 at 4:22
pauljohn32
2,199822
answered Nov 28 at 4:22
pauljohn32
2,199822
2,199822
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
add a comment |
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
Thank you for your help. I tried many things. Although I didn't find the reason of this problem, finally it was solved by change kernel version to 4.19.4 using UKUU.
– kgyk
Dec 5 at 7:43
add a comment |
1
Edit your question to include the output of
free -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resume. Use the{}to pretty-fy the text. Report back to @heynnema– heynnema
Nov 27 at 15:26
Not sure about closing this as there might be a specific reason for the hardware, but the suggested target is nowhere near as good as How to debug suspend? if anyone wants to add it
– Zanna
Nov 28 at 16:51