Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #197209 > unrolled thread

Fwd: terminal will not wak after hibernation

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Fwd: terminal will not wak after hibernation Dave <debiantechquestions@gmx.com> - 2018-07-05 01:40 +0200
    Re: Fwd: terminal will not wak after hibernation Dan Ritter <dsr@randomstring.org> - 2018-07-05 15:20 +0200
      Re: Fwd: terminal will not wak after hibernation Dave <debiantechquestions@gmx.com> - 2018-07-05 15:40 +0200
        Re: Fwd: terminal will not wak after hibernation Dan Ritter <dsr@randomstring.org> - 2018-07-05 16:30 +0200
          Re: Fwd: terminal will not wak after hibernation Dave <debiantechquestions@gmx.com> - 2018-07-05 16:40 +0200
            Re: Fwd: terminal will not wak after hibernation Dan Ritter <dsr@randomstring.org> - 2018-07-05 17:10 +0200
        Re: Fwd: terminal will not wak after hibernation Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-07-05 18:40 +0200
      Re: Fwd: terminal will not wak after hibernation <tomas@tuxteam.de> - 2018-07-05 16:30 +0200
        Re: Fwd: terminal will not wak after hibernation Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-07-05 17:20 +0200
          Re: Fwd: terminal will not wak after hibernation David Wright <deblis@lionunicorn.co.uk> - 2018-07-05 18:30 +0200
            Re: Fwd: terminal will not wak after hibernation <tomas@tuxteam.de> - 2018-07-06 07:20 +0200
            Re: Fwd: terminal will not wak after hibernation Dave <debiantechquestions@gmx.com> - 2018-07-07 15:50 +0200
              Re: Fwd: terminal will not wak after hibernation Dan Ritter <dsr@randomstring.org> - 2018-07-07 17:30 +0200
                Re: terminal will not wak after hibernation Joe <joe@jretrading.com> - 2018-07-07 21:40 +0200
                  Re: terminal will not wak after hibernation Celejar <celejar@gmail.com> - 2018-07-10 01:50 +0200
                    Re: terminal will not wak after hibernation Zenaan Harkness <zenaan@freedbms.net> - 2018-07-10 06:20 +0200
                      Re: terminal will not wak after hibernation Joe <joe@jretrading.com> - 2018-07-10 12:20 +0200
                Re: Fwd: terminal will not wak after hibernation Dave <debiantechquestions@gmx.com> - 2018-07-07 22:20 +0200
                  Re: Fwd: terminal will not wak after hibernation Dan Ritter <dsr@randomstring.org> - 2018-07-08 13:50 +0200
              Re: Fwd: terminal will not wak after hibernation John Darrah <xyllyx@gmail.com> - 2018-07-08 18:30 +0200
                Re: Fwd: terminal will not wak after hibernation Dave <debiantechquestions@gmx.com> - 2018-07-08 19:30 +0200

Page 1 of 2  [1] 2  Next page →

#197209 — Fwd: terminal will not wak after hibernation

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.

[toc] | [next] | [standalone]

#197225

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
2. if that doesn't work, ctrl-alt-F2
3. if that doesn't work, can you ssh in from another machine?

The most likely issue is that your video card did not wake up
from hibernation properly.

There are various workarounds or fixes, depending on what kind
of video card.

-dsr-

[toc] | [prev] | [next] | [standalone]

#197226

On 7/5/18 9:18 AM, 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
> 2. if that doesn't work, ctrl-alt-F2
> 3. if that doesn't work, can you ssh in from another machine?
>
> The most likely issue is that your video card did not wake up
> from hibernation properly.
>
> There are various workarounds or fixes, depending on what kind
> of video card.
>
> -dsr-
>
>
Hello

I mean display, screen, monitor,
the Ctrl Alt F1 F2 does not seem to work.
I have the Radeon HD 6850

please advise.

[toc] | [prev] | [next] | [standalone]

#197227

On Thu, Jul 05, 2018 at 09:34:48AM -0400, Dave wrote:
> 
> On 7/5/18 9:18 AM, 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
> > 2. if that doesn't work, ctrl-alt-F2
> > 3. if that doesn't work, can you ssh in from another machine?
> > 
> > The most likely issue is that your video card did not wake up
> > from hibernation properly.
> > 
> > There are various workarounds or fixes, depending on what kind
> > of video card.
> > 
> > -dsr-
> > 
> > 
> Hello
> 
> I mean display, screen, monitor,
> the Ctrl Alt F1 F2 does not seem to work.
> I have the Radeon HD 6850

Can you SSH in from another machine?

If so, stopping and restarting the window manager (or the login
manager) might reset things.

This sort of thing has been fairly common over the years, and
the usual workaround is to add

chvt 2

to the hibernation script, which switches the video card out of
graphics mode and into text mode, after which the hibernation
continues and then when it resumes, you tap ctrl-alt-F1 or
similar to get back to your X11 session.

-dsr-

[toc] | [prev] | [next] | [standalone]

#197229

On 7/5/18 10:23 AM, Dan Ritter wrote:
> On Thu, Jul 05, 2018 at 09:34:48AM -0400, Dave wrote:
>> On 7/5/18 9:18 AM, 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
>>> 2. if that doesn't work, ctrl-alt-F2
>>> 3. if that doesn't work, can you ssh in from another machine?
>>>
>>> The most likely issue is that your video card did not wake up
>>> from hibernation properly.
>>>
>>> There are various workarounds or fixes, depending on what kind
>>> of video card.
>>>
>>> -dsr-
>>>
>>>
>> Hello
>>
>> I mean display, screen, monitor,
>> the Ctrl Alt F1 F2 does not seem to work.
>> I have the Radeon HD 6850
> Can you SSH in from another machine?
>
> If so, stopping and restarting the window manager (or the login
> manager) might reset things.
>
> This sort of thing has been fairly common over the years, and
> the usual workaround is to add
>
> chvt 2
>
> to the hibernation script, which switches the video card out of
> graphics mode and into text mode, after which the hibernation
> continues and then when it resumes, you tap ctrl-alt-F1 or
> similar to get back to your X11 session.
>
> -dsr-
>
I cannot SSH in to this sytem.

I have tried Ctrl Alt F1 or F2 does not work.

[toc] | [prev] | [next] | [standalone]

#197231

On Thu, Jul 05, 2018 at 10:33:52AM -0400, Dave wrote:
> 
> 
> I cannot SSH in to this sytem.
> 
> I have tried Ctrl Alt F1 or F2 does not work.


You'll need to reboot. Ctrl-Alt-Del should work.

-dsr-

[toc] | [prev] | [next] | [standalone]

#197235

On 7/5/18, Dave <debiantechquestions@gmx.com> wrote:
>
> On 7/5/18 9:18 AM, 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
>> 2. if that doesn't work, ctrl-alt-F2
>> 3. if that doesn't work, can you ssh in from another machine?
>>
>> The most likely issue is that your video card did not wake up
>> from hibernation properly.
>>
>> There are various workarounds or fixes, depending on what kind
>> of video card.
>>
>> -dsr-
>>
>>
> Hello
>
> I mean display, screen, monitor,
> the Ctrl Alt F1 F2 does not seem to work.
> I have the Radeon HD 6850
>
> please advise.


Sorry, still no advice, just empathy. I was re-reading the thread one
more time before deleting, and saw this. My video players, primarily
MPV and SMPlayer, started kicking mine into most likely hibernation at
the end of videos.

A week or so of that fail, and now at least SMPlayer does the same 5
minutes or so into a maybe 2 hour long video. Those have been
Hollywood type videos playing in the DVD drawer. In considering
causatives, I do acknowledge that overheating or similar may play a
rational part, by the way.

Anyway, in those cases, CTRL+ALT+Fn does NOT work for me, either. Only
a cold, hard reboot via the on/off hardware button on the PC computer
case puts things back into operation.

That's why I just did the latest debootstrap. Refresh, start over with
the hope that might instantly fix things. K/t current #Life
circumstances just outside my front door (plus degenerative memory
issues), I don't have time right now to fight it while trying to
diagnose.

Unfortunately haven't been able to test the new debootstrap theory
because there's a whole 'nother thread of a fail going on there, too.
It's not recognizing the correctly defined UUID at boot. *sighhhh,
grinnn* :)

For what it's worth in the possibility that our video cards play a
sizable part in this thread's issue, I just pulled this from lspci:

VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1)

Its fan... um.. "works", but the dogs have hit the case (hard) a few
times so things aren't running as optimal as they used to/should be.
Ahhh, #FurBabies. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#197228

-----BEGIN PGP SIGNED MESSAGE-----
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.

Needless to say that I am not amused ("my" Debian installation has
sane defaults: it seems that keeping systemd away also helps on
those other things ;-)

Cheers
[1] https://www.reddit.com/r/debian/comments/6jdyzy/cant_open_text_terminal_with_ctrlaltf1_any_longer/
    I'd be thankful to anyone providing a linkable Debian resource
    on that, preferably with some rationale.

- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAls+Km4ACgkQBcgs9XrR2kZt/ACdFL7FbkuNp6295SSa4gJnKl/x
veIAnAmrY0aeq2yo16E6uQw48Frr6uXw
=rS7K
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#197232

On 7/5/18, tomas@tuxteam.de <tomas@tuxteam.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> 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.


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
others.

The debootstrap disclaimer is necessary because, at some point, the
chatter was about only being able to reboot as root via [terminal]
command line. As of about two debootstraps back, I still had to sudo
to reboot while others were saying they don't have to with some of the
more hefty installs.


> Needless to say that I am not amused ("my" Debian installation has
> sane defaults: it seems that keeping systemd away also helps on
> those other things ;-)
>
> Cheers
> [1]
> https://www.reddit.com/r/debian/comments/6jdyzy/cant_open_text_terminal_with_ctrlaltf1_any_longer/
>     I'd be thankful to anyone providing a linkable Debian resource
>     on that, preferably with some rationale.


It just occurred to me because I debootstrap'ed again a couple days
(so things are fresh in my mind). Would a quiet change in keyboard
layout configuration or compatibility prevent that combination from
working, maybe?

OR NOT. :)

Secondary disclaimer: Mine's got stock systemd.

$ systemd --version
systemd 232
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD +IDN

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#197234

On Thu 05 Jul 2018 at 11:11:19 (-0400), Cindy-Sue Causey wrote:
> On 7/5/18, tomas@tuxteam.de <tomas@tuxteam.de> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > 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
> others.

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.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#197259

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jul 05, 2018 at 11:27:31AM -0500, David Wright wrote:
> On Thu 05 Jul 2018 at 11:11:19 (-0400), Cindy-Sue Causey wrote:
> > On 7/5/18, tomas@tuxteam.de <tomas@tuxteam.de> wrote:

[...]

> > >> 1. ctrl-alt-F1
> > >
> > > Note: since stretch things have... changed [...]

> Unfortunately "since" is ambiguous: do you mean *after* stretch. or
> are you including stretch?

Yes, sorry. I meant "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
> > others.
> 
> 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.

Hm. Interesting. I'll have to double-check when I'm back. The machine
I'm referring to (and I don't have access to) seems to allocate VC1
for the display manager and put X on VC2 or something. But that's from
memory. Next week I'll be wiser.

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAls++ZwACgkQBcgs9XrR2kYUFwCeKgH60WBxAVbwIMgnfZpDa+W+
lDYAniifrctRyw+y4+CB/ziku+3hEcFA
=fK20
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#197318

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@tuxteam.de <tomas@tuxteam.de> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> 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
>> others.
> 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.
>
> Cheers,
> David.
>
>

[toc] | [prev] | [next] | [standalone]

#197320

On Sat, Jul 07, 2018 at 09:45:25AM -0400, Dave wrote:
> 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 ?

It's a specific combination of motherboard, motherboard BIOS,
video card, and video driver.

Unfortunately there are several such combinations, and new ones
occasionally appear.

The majority of machines can do suspend-to-RAM and/or
suspend-to-disk and wake up smoothly afterwards.

-dsr-

[toc] | [prev] | [next] | [standalone]

#197324

On Sat, 7 Jul 2018 11:24:59 -0400
Dan Ritter <dsr@randomstring.org> wrote:

> On Sat, Jul 07, 2018 at 09:45:25AM -0400, Dave wrote:
> > 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 ?  
> 
> It's a specific combination of motherboard, motherboard BIOS,
> video card, and video driver.
> 
> Unfortunately there are several such combinations, and new ones
> occasionally appear.
> 
> The majority of machines can do suspend-to-RAM and/or
> suspend-to-disk and wake up smoothly afterwards.
> 

I'll take your word for it. I've never seen such a combination. I give
suspend a try on my Gigabyte/AMD sid machine now and then, but it seems
to work for no more than two weeks in any year. Currently it is
leaving orphaned inodes, so I'm not experimenting too much.

Years ago, I used to spend time fixing it, but after a while I realised
it would only break again a month later, so I've stopped bothering.
I've yet to see a laptop/netbook screen backlight come on again after
suspend...

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#197421

On Sat, 7 Jul 2018 20:32:03 +0100
Joe <joe@jretrading.com> wrote:

> On Sat, 7 Jul 2018 11:24:59 -0400
> Dan Ritter <dsr@randomstring.org> wrote:

...

> > The majority of machines can do suspend-to-RAM and/or
> > suspend-to-disk and wake up smoothly afterwards.
> > 
> 
> I'll take your word for it. I've never seen such a combination. I give
> suspend a try on my Gigabyte/AMD sid machine now and then, but it seems
> to work for no more than two weeks in any year. Currently it is
> leaving orphaned inodes, so I'm not experimenting too much.
> 
> Years ago, I used to spend time fixing it, but after a while I realised
> it would only break again a month later, so I've stopped bothering.
> I've yet to see a laptop/netbook screen backlight come on again after
> suspend...

?! Many people have suspend working fine (although many certainly
don't); suspend-to-ram has been working flawlessly (AFAICT) out of the
box on my Lenovo ThinkPad W550s.

Celejar

[toc] | [prev] | [next] | [standalone]

#197425

On Mon, Jul 09, 2018 at 05:27:44PM -0400, Celejar wrote:
> On Sat, 7 Jul 2018 20:32:03 +0100
> Joe <joe@jretrading.com> wrote:
> 
> > On Sat, 7 Jul 2018 11:24:59 -0400
> > Dan Ritter <dsr@randomstring.org> wrote:
> 
> ...
> 
> > > The majority of machines can do suspend-to-RAM and/or
> > > suspend-to-disk and wake up smoothly afterwards.
> > > 
> > 
> > I'll take your word for it. I've never seen such a combination. I give
> > suspend a try on my Gigabyte/AMD sid machine now and then, but it seems
> > to work for no more than two weeks in any year. Currently it is
> > leaving orphaned inodes, so I'm not experimenting too much.
> > 
> > Years ago, I used to spend time fixing it, but after a while I realised
> > it would only break again a month later, so I've stopped bothering.
> > I've yet to see a laptop/netbook screen backlight come on again after
> > suspend...
> 
> ?! Many people have suspend working fine (although many certainly
> don't); suspend-to-ram has been working flawlessly (AFAICT) out of the
> box on my Lenovo ThinkPad W550s.

In the APM days, Debian/Linux suspend was flawless for years.

Then ACPI came along and things have been iffy for a decade.

However, suspend-to-RAM (suspend, as opposed to hibernate) has worked
very well here (Lenovo X220) for the last few years.

Possibly OP/Joe has some customization he regularly implements,
causing his problem? IDK of course...

Good luck,

[toc] | [prev] | [next] | [standalone]

#197427

On Tue, 10 Jul 2018 14:14:11 +1000
Zenaan Harkness <zenaan@freedbms.net> wrote:

> On Mon, Jul 09, 2018 at 05:27:44PM -0400, Celejar wrote:
> > On Sat, 7 Jul 2018 20:32:03 +0100
> > Joe <joe@jretrading.com> wrote:
> >   
> > > On Sat, 7 Jul 2018 11:24:59 -0400
> > > Dan Ritter <dsr@randomstring.org> wrote:  
> > 
> > ...
> >   
> > > > The majority of machines can do suspend-to-RAM and/or
> > > > suspend-to-disk and wake up smoothly afterwards.
> > > >   
> > > 
> > > I'll take your word for it. I've never seen such a combination. I
> > > give suspend a try on my Gigabyte/AMD sid machine now and then,
> > > but it seems to work for no more than two weeks in any year.
> > > Currently it is leaving orphaned inodes, so I'm not experimenting
> > > too much.
> > > 
> > > Years ago, I used to spend time fixing it, but after a while I
> > > realised it would only break again a month later, so I've stopped
> > > bothering. I've yet to see a laptop/netbook screen backlight come
> > > on again after suspend...  
> > 
> > ?! Many people have suspend working fine (although many certainly
> > don't); suspend-to-ram has been working flawlessly (AFAICT) out of
> > the box on my Lenovo ThinkPad W550s.  
> 
> In the APM days, Debian/Linux suspend was flawless for years.
> 
> Then ACPI came along and things have been iffy for a decade.
> 
> However, suspend-to-RAM (suspend, as opposed to hibernate) has worked
> very well here (Lenovo X220) for the last few years.
> 
> Possibly OP/Joe has some customization he regularly implements,
> causing his problem? IDK of course...
> 

Not that I know of. But I'm not an IT professional, dealing with
hundreds of machines. I've had a couple of laptops and an Acer netbook,
fairly mainstream, and a few desktops. 

For example, the netbook has a fairly recent Stretch installation. If I
manually select 'Suspend', that works and appears to come back up
normally. If I close the lid, when I open it again, the display stays
black. From keyboard and mouse action, it looks as if it is awake
normally, there's just no display. It's not really of any use in that
state, and needs to be killed with the four-second power button thing.

As I've posted, I have a moderately old desktop Gigabyte MB, with a
fairly old sid installation, on which suspend to RAM has occasionally
worked. At the moment, the only way to resume is to poke the power
button, it no longer wakes up on keyboard or mouse action, when it
wakes it sits for fifteen seconds then reboots. Yes, I know about swap
naming, I've been through all that and in any case, swap isn't involved
in suspend to RAM. It has worked reliably within the last year, but not
for more than a couple of weeks.

I can't recall any machine on which I've run Linux working properly as
regards suspend. OK, it's only half a dozen or so computers, but zero
out of six isn't an impressive performance.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#197326

On 7/7/18 11:24 AM, Dan Ritter wrote:
> On Sat, Jul 07, 2018 at 09:45:25AM -0400, Dave wrote:
>> 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 ?
> It's a specific combination of motherboard, motherboard BIOS,
> video card, and video driver.
>
> Unfortunately there are several such combinations, and new ones
> occasionally appear.
>
> The majority of machines can do suspend-to-RAM and/or
> suspend-to-disk and wake up smoothly afterwards.
>
> -dsr-
>

Would one of the newer Dell Power Spec Servers Work with Debian Linux 
Solving this "Non Wake display issue" ?  the Dells start at 1600.00 and 
go up from there.
I have been Asking Debian-User list if there is a cheaper, easier or 
simpler fix , but no one has any definitive answers about this issue, 
I'm at the point of just buying a powerspec.

please advise

Dave

[toc] | [prev] | [next] | [standalone]

#197343

On Sat, Jul 07, 2018 at 04:16:19PM -0400, Dave wrote:
> 
> 
> On 7/7/18 11:24 AM, Dan Ritter wrote:
> > On Sat, Jul 07, 2018 at 09:45:25AM -0400, Dave wrote:
> > > 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 ?
> > It's a specific combination of motherboard, motherboard BIOS,
> > video card, and video driver.
> > 
> > Unfortunately there are several such combinations, and new ones
> > occasionally appear.
> > 
> > The majority of machines can do suspend-to-RAM and/or
> > suspend-to-disk and wake up smoothly afterwards.
> > 
> > -dsr-
> > 
> 
> Would one of the newer Dell Power Spec Servers Work with Debian Linux
> Solving this "Non Wake display issue" ?  the Dells start at 1600.00 and go
> up from there.
> I have been Asking Debian-User list if there is a cheaper, easier or simpler
> fix , but no one has any definitive answers about this issue, I'm at the
> point of just buying a powerspec.

I guess my first question would be, why are you hibernating a
server?

All I can testify to is my own experience. I've seen Intel
CPU/GPU combinations fail to wake the display, but not since
Stretch started and possibly not for several years before that.
My wife's AMD cpu with an NVidia 1030 wakes properly. 

-dsr-

[toc] | [prev] | [next] | [standalone]

#197354

On 7/7/2018 6:51 AM, Dave wrote:
> 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 ?
>

Hibernation issues are almost always an issue with the BIOS/Motherbord 
firmware... make sure your BIOS is up to date.

-- john

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web