Dell Inspiron 5150 - Suspend to RAM not working... still (part one)
woyciesjes at sbcglobal.net
Fri Feb 12 19:30:24 UTC 2010
Dave Woyciesjes wrote:
> I've had this laptop, upgraded from 8.10 to 9.04, and now to 9.10.
> Suspend hasn't worked, oh, since 8.04. Finally getting 'round to fixing
> it. Right now, it goes into suspend (from the menu, keyboard combo
> doesn't work), but when I hit the power button to resume, I get:
> [ 109.218040] pm-op() pci_pm_resume+0x0/0x90 returns -16
> [ 109.218044] PM: Device 0000:00:00.0 failed to resume: error -16
> Then a blank screen. Have to power off to get going again. Tried
> suggestions from here (tweaking /etc/default/acpi-support):
> I also found these, but haven't had a moment to try yet:
> Another thing I may try, since I have an extra HDD, is doing a test
> with a fresh 9.10 install, since the current likely has leftovers from
> the previous versions.
> Anybody else with a Dell laptop & nVidia chipset get suspend working?
> (jump to end for my lspci, xorg.conf and acpi-support files)
Here's what I have for notes so far, a summary of changes I'll try.
Comments, thoughts, insight?
(from Ubuntu Forums thread):
Try turning off wireless, then suspend & resume, as a test.
Add under the “Device” section:
Option “NvAGP” “1"
---(Ubuntu Forums post also added):
----(dreamhosters site suggests this for acpi-support file:
# Save and restore video state?
#SAVE_VIDEO_PCI_STATE=true (will try this later...)
"...Finally if you’re using compiz (desktop-effects) in conjunction with
NVIDIA binary drivers, make sure your “Sync to VBLANK” option in
“Advanced Desktop Effects Settings > General > Display settings” is
*disabled*. You can set this option to false by running:
gconftool –set /apps/compiz/general/screen0/options/sync_to_vblank 0
(from one source, taksuyama.com)
SUSPEND_MODULES=ath_pci (or whatever the wireless driver is)
(from two other sources, dreamhosters.com & Ubuntu Forum):
/etc/acpi/wireless.sh - because of Intel Pro Wireless 2200bg [ipw2200] wifi:
< echo -n 2 > $DEVICE/device/power/state;
> echo -n 3 > $DEVICE/device/power/state;
(this means replace "echo -n 2" with "echo -n 3")
> Here are some files & output that is probably relevant:
> (I'll send dmesg in a following message)
> Section "Screen"
> Identifier "Configured Screen Device"
> DefaultDepth 24
> Section "Device"
> Identifier "Configured Video Device"
> Driver "nvidia"
> lspci output:
> 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV
> Processor to I/O Controller (rev 02)
> 00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV
> Processor to I/O Controller (rev 02)
> 00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV
> Processor to I/O Controller (rev 02)
> 00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV
> Processor to AGP Controller (rev 02)
> 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
> 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
> 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
> 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2
> EHCI Controller (rev 01)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
> 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface
> Bridge (rev 01)
> 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE
> Controller (rev 01)
> 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
> 01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX
> Go5200 64M] (rev a1)
> 02:01.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
> 02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG
> [Calexico2] Network Connection (rev 05)
> 02:04.0 CardBus bridge: Texas Instruments PCI4510 PC card Cardbus
> Controller (rev 02)
> 02:04.1 FireWire (IEEE 1394): Texas Instruments PCI4510 IEEE-1394 Controller
> # Configuration file for the acpi-support package
> # The acpi-support package is intended as "glue" to make special
> functions of
> # laptops work. Specifically, it translates special function keys for some
> # laptop models into actions or generic function key presses.
> # Suspend/hibernate method
> # ------------------------
> # When gnome-power-manager or klaptopdaemon are running, acpi-support will
> # translate the suspend and hibernate keys of laptops into special "suspend"
> # and "hibernate" keys that these daemons handle.
> # Only in situations where there is no gnome-power-manager or klaptopdaemon
> # running, acpi-support needs to perform suspend/hibernate in some other
> # There are several options for this. The options are:
> # dbus-pm:
> # Perform suspend and hibernate actions via a DBUS request to the power
> # management daemon. This works for power management daemons that we
> # know of. (For gnome-power-manager and klaptopdaemon this will do
> # since those will be detected when they are running, and triggered using
> # a virtual keypress.)
> # dbus-hal:
> # Perform suspend and hibernate actions via a DBUS request directly
> to HAL,
> # bypassing any running power management daemons.
> # pm-utils:
> # Use pm-suspend and pm-hibernate to suspend and hibernate. (The dbus
> # normally results in this as well, but calls through dbus. Use this
> # only if you don't have dbus installed.)
> # hibernate:
> # Use the hibernate package to suspend and hibernate.
> # acpi-support:
> # Use the legacy built-in suspend/hibernate support. (DEPRECATED)
> # none:
> # Do not attempt to suspend/hibernate. Set SUSPEND_METHODS="none" to
> # disable suspend/hibernate handling in acpi-support.
> # If you specify dbus or pm-utils, the result will normally be the same
> as when
> # you suspend from your desktop environment. If you specify "hibernate" or
> # "acpi-support", be aware that this probably does not match what your
> # environment would do (unless you have managed to configure something
> so that
> # the DBUS power management interfaces call the hibernate package).
> # Please specify a space separated list of options. The recommended value is
> # "dbus pm-utils"
> SUSPEND_METHODS="acpi-support dbus-pm dbus-hal pm-utils"
> # LEGACY BUILT IN SUSPEND SUPPORT (DEPRECATED)
> # --------------------------------------------
> # These options only work for the "acpi-support" suspend method. This is NOT
> # recommended, but is retained for backward compatibility reasons.
> # Comment the next line to disable ACPI suspend to RAM
> # Comment the next line to disable suspend to disk
> # Change the following to "standby" to use ACPI S1 sleep, rather than S3.
> # This will save less power, but may work on more machines
> # 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
> # Add modules to this list to leave them in the kernel over suspend/resume
> # Should we save and restore state using the VESA BIOS Extensions?
> # The file that we use to save the vbestate
> # Should we attempt to warm-boot the video hardware on resume?
> # Save and restore video state?
> # SAVE_VIDEO_PCI_STATE=true
> # Should we switch the screen off with DPMS on suspend?
> # Use Radeontool to switch the screen off? Seems to be needed on some
> # 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
> # Set the following to "platform" if you want to use ACPI to shut down
> # your machine on hibernation
> # Comment this out to disable screen locking on resume
> # 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.
> # Restart Infra Red services on resume - off by default as it crashes some
> # machines
> # Switch to laptop-mode on battery power - off by default as it causes odd
> # hangs on some machines. (Note: This is reported to cause breakage in
> # Debian - see deb bug #425800. Leaving enabled for Ubuntu for now
> # since presumably it's still valid here.)
> # Add to this list network interfaces that you don't want to be stopped
> # during suspend (in fact any network interface whose name starts with
> # a prefix given in this list is skipped)
> SKIP_INTERFACES="dummy qemu"
> # Note: to enable "laptop mode" (to spin down your hard drive for longer
> # periods of time), install the laptop-mode-tools package and configure
> # it in /etc/laptop-mode/laptop-mode.conf.
More information about the ubuntu-users