Web lists-archives.com

Re: Fwd: terminal will not wak after hibernation

I wanted to know if this hibernation / waking issue can be solved by using more compatable motherboards, hardware, ect ... or is this issue prevelant regardless of the hardware and bios being used ?

On 7/5/18 12:27 PM, David Wright wrote:
On Thu 05 Jul 2018 at 11:11:19 (-0400), Cindy-Sue Causey wrote:
On 7/5/18, tomas@xxxxxxxxxx <tomas@xxxxxxxxxx> wrote:
Hash: SHA1

On Thu, Jul 05, 2018 at 09:18:38AM -0400, Dan Ritter wrote:
On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
after hibernation the terminal will not wake ( apparently, no signal )
the computer wakes, the keyboard lights up.
I just installed deb 9.4 amd / the bios was just updated.
By terminal, do you mean monitor?

If so:

1. ctrl-alt-F1
Note: since stretch things have... changed [1] (I have some dim
memory of not even getting a Linux console anymore on ctrl-alt-Fn
for *any* value of n < 10, but need to go back to double-check.
It's on a customer's machine.
Unfortunately "since" is ambiguous: do you mean *after* stretch. or
are you including stretch?

CTRL+ALT+Fn still works on my debootstrap'ed Stretch Stable. F7, not
F1, is the [default/primary] go-to when one's done playing in the
Still works here, but I don't understand the reference to F7. Perhaps
that might be because you run a DE? Here, I login to a VC and run
startx. X then runs as a user on VC1, not 7 as it did in the past.
I'm running stretch on a normal netinst installation.

That said, I have dim memories of reports that X behaves differently
when run on VC1 from any other VC, and this might have involved
hibernation. Because I don't hibernate this machine (I keep the lid
open when I can as the hinge is dicky), I didn't file them.
But it might be worth a try.

[…] Mine's got stock systemd.
Same here.