R
Robbie Hatley
"someone watching" wrote:
> I think the 'sleep' issue you brought up is an age long one
> and I've never seen 'one specific' cause!
I just stumbled across something that gave me an idea,
though:
http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface
S1: All processor caches are flushed, and the CPU(s) stop
executing instructions. Power to the CPU(s) and RAM
is maintained devices that do not indicate they must
remain on may be powered down.
S2: CPU powered off
S3: Commonly referred to as Standby, Sleep, or Suspend to RAM.
RAM remains powered
S4: Hibernation or Suspend to disk. All content of main memory
is saved to non-volatile memory such as a hard drive, and
is powered down.
My BIOS has two options for "Suspend To": "S1" and "S3".
Up until now, I had it set to "S3", because I had no idea
what either option really meant. But now that I see that
S3 powers down the CPU, while S1 doesn't, I'll set it to
S1. That should make "waking up" easier, since the
computer will be less deeply asleep.
> For both issues the typical, 'do you have a driver conflict',
> comes to mind! ...
Maybe. But I've installed / uninstalled / changed various
peripherals a lot over the years, and yet these two nagging
problems have remained about the same.
> ... event logs ...
The last recorded events are immediately prior to shut-down,
and if "wake" fails, no events at all are recorded at the
time of the failed "wake" attempt. Video remains black,
system doesn't respond to keyboard or mouse, and Num-Lock and
Cap-Lock LEDs do not react to Num-Lock and Cap-Lock keys.
> ... hibernating ...
I've never been able to get that to work. Possibly whatever
is screwing up "Standby" is also screwing up "hibernate".
But I'll see what happens with "suspend to" set to S1.
Hopefully that will make Standby more reliable.
--
Cheers,
Robbie Hatley
lonewolf at well dot com
www dot well dot com slant tilde lonewolf slant
> I think the 'sleep' issue you brought up is an age long one
> and I've never seen 'one specific' cause!
I just stumbled across something that gave me an idea,
though:
http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface
S1: All processor caches are flushed, and the CPU(s) stop
executing instructions. Power to the CPU(s) and RAM
is maintained devices that do not indicate they must
remain on may be powered down.
S2: CPU powered off
S3: Commonly referred to as Standby, Sleep, or Suspend to RAM.
RAM remains powered
S4: Hibernation or Suspend to disk. All content of main memory
is saved to non-volatile memory such as a hard drive, and
is powered down.
My BIOS has two options for "Suspend To": "S1" and "S3".
Up until now, I had it set to "S3", because I had no idea
what either option really meant. But now that I see that
S3 powers down the CPU, while S1 doesn't, I'll set it to
S1. That should make "waking up" easier, since the
computer will be less deeply asleep.
> For both issues the typical, 'do you have a driver conflict',
> comes to mind! ...
Maybe. But I've installed / uninstalled / changed various
peripherals a lot over the years, and yet these two nagging
problems have remained about the same.
> ... event logs ...
The last recorded events are immediately prior to shut-down,
and if "wake" fails, no events at all are recorded at the
time of the failed "wake" attempt. Video remains black,
system doesn't respond to keyboard or mouse, and Num-Lock and
Cap-Lock LEDs do not react to Num-Lock and Cap-Lock keys.
> ... hibernating ...
I've never been able to get that to work. Possibly whatever
is screwing up "Standby" is also screwing up "hibernate".
But I'll see what happens with "suspend to" set to S1.
Hopefully that will make Standby more reliable.
--
Cheers,
Robbie Hatley
lonewolf at well dot com
www dot well dot com slant tilde lonewolf slant