Yannick wrote:
> Hello!
> I made those change on a fresh Kubuntu gutsy, and it does'nt do anything: when the screen goes on, the image is garbage: block spot behind the menu, the writing in firefox don't show up, etc...
> Any other idea?
I've attached my acpi-support file, maybe there are some other
differences that may be relevant?
Otherwise, I'm not sure. I myself still experience the occasional lockup
at resume. It happens more often after suspend, and less after
hibernate, but I have not been able to find a definite pattern there...
As an aside, network often fails to come up properly at resume as well
(with 'sudo killall NetworkManager && sudo Networkmanager' as an easy
but inappropriate workaround...). I don't suppose this is related, but
mention it just in case (please do redirect nm related stuff to the
appropriate bug/thread!).
--
Groetjes,
Anton
_____________ _______________________________________________________
| | |
| _ _ ___,| K. Anton Feenstra |
| / \ / \'| | | IBIVU/Bioinformatics - Free University Amsterdam |
|( | )| | | De Boelelaan 1083A - 1081 HV Amsterdam - Netherlands |
| \_/ \_/ | | | Tel +31 20 59 87783 - Fax +31 20 59 87653 - Room P136 |
| | <email address hidden> - www.few.vu.nl/~feenstra/ |
| | "A Lady Shaves Her Legs" (C. Meijering) |
|_____________|_______________________________________________________|
# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true
# Comment the next line to disable suspend to disk
ACPI_HIBERNATE=true
# Change the following to "standby" to use ACPI S1 sleep, rather than S3.
# This will save less power, but may work on more machines
ACPI_SLEEP_MODE=mem
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="ipw3945"
# MODULES=""
# Add modules to this list to leave them in the kernel over suspend/resume
MODULES_WHITELIST=""
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
# SAVE_VBE_STATE=true
# The file that we use to save the vbestate
VBESTATE=/var/lib/acpi-support/vbestate
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
#POST_VIDEO=true
# Save and restore video state?
SAVE_VIDEO_PCI_STATE=false
# SAVE_VIDEO_PCI_STATE=true
# Should we switch the screen off with DPMS on suspend?
USE_DPMS=true
# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true
# Uncomment the next line to switch away from X and back again after resume.
# This is needed for some hardware, but should be unnecessary on most.
DOUBLE_CONSOLE_SWITCH=true
# DOUBLE_CONSOLE_SWITCH=true
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=shutdown
# Comment this out to disable screen locking on resume
# LOCK_SCREEN=true
# Uncomment this line to have DMA disabled before suspend and reenabled
# afterwards
# DISABLE_DMA=true
# Uncomment this line to attempt to reset the drive on resume. This seems
# to be needed for some Sonys
# RESET_DRIVE=true
# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="network bluetooth"
# STOP_SERVICES=""
# Restart Infra Red services on resume - off by default as it crashes some
# machines
RESTART_IRDA=false
# Switch to laptop-mode on battery power - off by default as it causes odd
# hangs on some machines
ENABLE_LAPTOP_MODE=false
Yannick wrote:
> Hello!
> I made those change on a fresh Kubuntu gutsy, and it does'nt do anything: when the screen goes on, the image is garbage: block spot behind the menu, the writing in firefox don't show up, etc...
> Any other idea?
I've attached my acpi-support file, maybe there are some other
differences that may be relevant?
Otherwise, I'm not sure. I myself still experience the occasional lockup
at resume. It happens more often after suspend, and less after
hibernate, but I have not been able to find a definite pattern there...
As an aside, network often fails to come up properly at resume as well
(with 'sudo killall NetworkManager && sudo Networkmanager' as an easy
but inappropriate workaround...). I don't suppose this is related, but
mention it just in case (please do redirect nm related stuff to the
appropriate bug/thread!).
--
Groetjes,
Anton _______ _______ _______ _______ _______ _______ ______ atics - Free University Amsterdam | vu.nl/~ feenstra/ | _______ |______ _______ _______ _______ _______ _______ _______ _______ |
_____________ _______
| | |
| _ _ ___,| K. Anton Feenstra |
| / \ / \'| | | IBIVU/Bioinform
|( | )| | | De Boelelaan 1083A - 1081 HV Amsterdam - Netherlands |
| \_/ \_/ | | | Tel +31 20 59 87783 - Fax +31 20 59 87653 - Room P136 |
| | <email address hidden> - www.few.
| | "A Lady Shaves Her Legs" (C. Meijering) |
|______
# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true
# Comment the next line to disable suspend to disk
ACPI_HIBERNATE=true
# Change the following to "standby" to use ACPI S1 sleep, rather than S3.
# This will save less power, but may work on more machines
ACPI_SLEEP_MODE=mem
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="ipw3945"
# MODULES=""
# Add modules to this list to leave them in the kernel over suspend/resume WHITELIST= ""
MODULES_
# Should we save and restore state using the VESA BIOS Extensions? STATE=false
SAVE_VBE_
# SAVE_VBE_STATE=true
# The file that we use to save the vbestate /var/lib/ acpi-support/ vbestate
VBESTATE=
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
#POST_VIDEO=true
# Save and restore video state? PCI_STATE= false PCI_STATE= true
SAVE_VIDEO_
# SAVE_VIDEO_
# Should we switch the screen off with DPMS on suspend?
USE_DPMS=true
# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true
# Uncomment the next line to switch away from X and back again after resume. CONSOLE_ SWITCH= true CONSOLE_ SWITCH= true
# This is needed for some hardware, but should be unnecessary on most.
DOUBLE_
# DOUBLE_
# Set the following to "platform" if you want to use ACPI to shut down MODE=shutdown
# your machine on hibernation
HIBERNATE_
# Comment this out to disable screen locking on resume
# LOCK_SCREEN=true
# Uncomment this line to have DMA disabled before suspend and reenabled
# afterwards
# DISABLE_DMA=true
# Uncomment this line to attempt to reset the drive on resume. This seems
# to be needed for some Sonys
# RESET_DRIVE=true
# Add services to this list to stop them before suspend and restart them in "network bluetooth"
# the resume process.
STOP_SERVICES=
# STOP_SERVICES=""
# Restart Infra Red services on resume - off by default as it crashes some
# machines
RESTART_IRDA=false
# Switch to laptop-mode on battery power - off by default as it causes odd LAPTOP_ MODE=false
# hangs on some machines
ENABLE_
# Spindown time on battery
SPINDOWN_TIME=12