User: Password:
Subscribe / Log in / New account



Posted May 4, 2006 6:24 UTC (Thu) by ncm (subscriber, #165)
Parent article: The Linux power management summit

This might be a good place to ask about interaction of ACPI and X.

I have laptops from two different manufacturers (Compaq, Toshiba)
with two different chipsets (ATI Rage Mobility, Intel 915M), that
lose one or another video attribute (XV_SATURATION, XV_CONTRAST)
that must be restored manually after a suspend-to-RAM/restore cycle.
Google reveals no indication that anybody else has noticed the problem,
never mind discussed what's going on.

Apparently X is depending on ACPI to save the parameters, and ACPI
assumes X will restore what it needs. Unfortunately xvattr does
not offer an option to save out the current settings in a form that
can be replayed, although it ought to be easy enough to add such a
feature. I hesitate, though: experience suggests that too much
setting of Xv attributes is a good way to crash X.

Any informed commentary offered here would multiply the amount of
information readily available on the net.

(Log in to post comments)


Posted May 25, 2006 7:03 UTC (Thu) by barrygould (guest, #4774) [Link]

FWIW, on my Dell D800, the solution to X not initializing the display after suspend-to-ram is to enable the system password in the BIOS... this cause the bios to reset the display and prompt for a password.

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds