Bug 555 - S3 power saving mode "SuspendTime" not supported
S3 power saving mode "SuspendTime" not supported
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1998-12-21 16:08 EST by dnelson
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1998-12-30 17:14:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description dnelson 1998-12-21 16:08:55 EST
If the SuspendTime option is enabled, X will fail to start
indicating that it can not process the option.  The other
power saving options (StandbyTime and OffTime) appear to
work.  The README.S3 documents the SuspendTime option.
Comment 1 David Lawrence 1998-12-21 16:50:59 EST
I am unable to find any reference to SuspendTime option in the
/usr/X11R6/lib/X11/doc/README.S3 file that is included in
XFree86-3.3.2 or XFree86-3.3.2.
Comment 2 dnelson 1998-12-22 00:06:59 EST
Ooops, my mistake.  The *Time options are documented in the man page
for XF86Config(5).  The man page XF86_S3(1) refers to having to
specify the "power_saver" option in order to use the *Time options.

In addition, this used to work flawlessly in RHL 4.1 for i386.
Comment 3 David Lawrence 1998-12-22 13:51:59 EST
What exact type of S3 chipset are you using? It also says in the
XF86-S3 man page:

The  suspend  level  is currently  only  supported  for the Mach64 and
for the 732, 764, 864, 868, 964, 968 S3 chips.

It also states that it is considered experimental so it could be
possible that your card is not yet fully stable.
Comment 4 David Lawrence 1998-12-30 17:14:59 EST
Please feel free to reopen this bug once you have obtained the
necessary information requested.

Note You need to log in before you can comment on or make changes to this bug.