Whitelist Asus A5Ec laptop for working suspend.

Bug #37303 reported by dhalgren
12
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

On Asus A5Ec laptop Fn+F1 is supposed to activate sleep mode. This does not work in breezy or in Dapper

Related branches

Revision history for this message
Matthew Garrett (mjg59) wrote :

If you press the key, does anything appear in /var/log/acpid ?

Revision history for this message
dhalgren (muirhead) wrote : Re: [Bug 37303] Fn+F1 does not work

thanks for asking the question! I didn't know where to look for error
messages.

On Thu, 2006-03-30 at 10:38 +0000, Matthew Garrett wrote:

> Public bug report changed:
> https://launchpad.net/malone/bugs/37303
>
> Comment:
> If you press the key, does anything appear in /var/log/acpid ?
>

Yes. I think all of the message below refers to Fn+F1. launchpad is
closed for maintenance at the moment, and I will put it there later.

[Thu Mar 30 20:57:31 2006] received event "button/sleep SLPB 00000080
00000001"
[Thu Mar 30 20:57:31 2006] notifying client 4038[111:111]
[Thu Mar 30 20:57:31 2006] executing action "/etc/acpi/sleep.sh"
[Thu Mar 30 20:57:31 2006] BEGIN HANDLER MESSAGES
+ . /etc/default/acpi-support
++ ACPI_HIBERNATE=true
++ ACPI_SLEEP_MODE=mem
++ MODULES=
++ MODULES_WHITELIST=
++ SAVE_VBE_STATE=true
++ VBESTATE=/var/lib/acpi-support/vbestate
++ POST_VIDEO=true
++ USE_DPMS=true
++ HIBERNATE_MODE=shutdown
++ LOCK_SCREEN=true
++ STOP_SERVICES='mysql '
++ RESTART_IRDA=false
++ ENABLE_LAPTOP_MODE=true
+ . /usr/share/acpi-support/power-funcs
++ umask 022
++ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/bin/X11
++ POWERSTATE=/var/lib/acpi-support/powerstate
++ LAPTOP_MODE=/usr/sbin/laptop_mode
++ HDPARM='/sbin/hdparm -q'
++ LIDSTATE=/var/lib/acpi-support/lidstate
+ . /usr/share/acpi-support/device-funcs
+ . /usr/share/acpi-support/policy-funcs
+ DeviceConfig
++ dmidecode --string system-manufacturer
++ sed -e 's/ *$//'
+ manufacturer='ASUSTeK Computer Inc.'
++ dmidecode --string system-product-name
++ sed -e 's/ *$//'
+ model=A5E
++ dmidecode --string system-version
++ sed -e 's/ *$//'
+ version=1.0
+ '[' -f '/usr/share/acpi-support/ASUSTeK Computer Inc..config' ']'
+ . '/usr/share/acpi-support/ASUSTeK Computer Inc..config'
++ case "$model" in
+ '[' x '!=' xtrue ']'
+ '[' x '!=' xforce ']'
+ exit
[Thu Mar 30 20:57:31 2006] END HANDLER MESSAGES
[Thu Mar 30 20:57:31 2006] action exited with status 0
[Thu Mar 30 20:57:31 2006] completed event "button/sleep SLPB 00000080
00000001"bruce@inana:~$

Revision history for this message
Matthew Garrett (mjg59) wrote : Re: Fn+F1 does not work

Ok. Sleep may need to be enabled in whichever desktop you're using, or alternatively edit /etc/default/acpi-support and uncomment the SLEEP= line.

Changed in hotkey-setup:
status: Unconfirmed → Rejected
Revision history for this message
Paul Sladen (sladen) wrote :

If you enable SLEEP= suspend (it doesn't work on all laptop so it is only enabled by default on laptops which we definately know work), does the machine suspend and unsuspend quite happily.

If it does, can you paste your dmidecode data, so that it can be whitelisted?

Revision history for this message
dhalgren (muirhead) wrote :
Download full text (5.0 KiB)

I edited << /etc/default/acpi-support >> and then used system>preferences>power management to enable suspend with the result that the laptop suspended and unsuspended quite happily. It was a bit slow and I received a black screen with varoius messages, but it did work.
 I am including < /var/log/acpid >> in the event taht these messages and black screen should not have happened.

[Tue Apr 4 08:30:11 2006] received event "button/sleep SLPB 00000080 00000001"
[Tue Apr 4 08:30:11 2006] notifying client 4069[119:119]
[Tue Apr 4 08:30:11 2006] executing action "/etc/acpi/sleep.sh"
[Tue Apr 4 08:30:11 2006] BEGIN HANDLER MESSAGES
+ . /etc/default/acpi-support
++ ACPI_SLEEP=true
++ ACPI_HIBERNATE=true
++ ACPI_SLEEP_MODE=mem
++ MODULES=
++ MODULES_WHITELIST=
++ SAVE_VBE_STATE=true
++ VBESTATE=/var/lib/acpi-support/vbestate
++ POST_VIDEO=true
++ USE_DPMS=true
++ HIBERNATE_MODE=shutdown
++ LOCK_SCREEN=true
++ STOP_SERVICES='mysql '
++ RESTART_IRDA=false
++ ENABLE_LAPTOP_MODE=true
+ . /usr/share/acpi-support/power-funcs
++ umask 022
++ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/bin/X11
++ POWERSTATE=/var/lib/acpi-support/powerstate
++ LAPTOP_MODE=/usr/sbin/laptop_mode
++ HDPARM='/sbin/hdparm -q'
++ LIDSTATE=/var/lib/acpi-support/lidstate
+ . /usr/share/acpi-support/device-funcs
+ . /usr/share/acpi-support/policy-funcs
+ DeviceConfig
++ cat /var/lib/acpi-support/system-manufacturer
+ manufacturer='ASUSTeK Computer Inc.'
++ cat /var/lib/acpi-support/system-product-name
+ model=A5E
++ cat /var/lib/acpi-support/system-version
+ version=1.0
+ '[' -f '/usr/share/acpi-support/ASUSTeK Computer Inc..config' ']'
+ . '/usr/share/acpi-support/ASUSTeK Computer Inc..config'
++ case "$model" in
+ '[' xtrue '!=' xtrue ']'
++ CheckPolicy
+++ pidof gnome-power-manager
+++ pidof kpowersave
+++ '[' -x /usr/bin/dcop ']'
++ '[' 5349 -o '' -o x '!=' x ']'
++ echo 0
+ '[' 0 = 0 ']'
+ '[' x '!=' xforce ']'
+ '[' x '!=' xsleep ']'
+ exit
[Tue Apr 4 08:30:11 2006] END HANDLER MESSAGES
[Tue Apr 4 08:30:11 2006] action exited with status 0
[Tue Apr 4 08:30:11 2006] completed event "button/sleep SLPB 00000080 00000001"
[Tue Apr 4 08:45:40 2006] received event "button/power PWRF 00000080 00000001"
[Tue Apr 4 08:45:40 2006] notifying client 4069[119:119]
[Tue Apr 4 08:45:40 2006] executing action "/etc/acpi/powerbtn.sh"
[Tue Apr 4 08:45:40 2006] BEGIN HANDLER MESSAGES
[Tue Apr 4 08:45:41 2006] END HANDLER MESSAGES
[Tue Apr 4 08:45:41 2006] action exited with status 0
[Tue Apr 4 08:45:41 2006] completed event "button/power PWRF 00000080 00000001"
[Tue Apr 4 08:45:56 2006] received event "processor CPU1 00000081 00000000"
[Tue Apr 4 08:45:56 2006] notifying client 4069[119:119]
[Tue Apr 4 08:45:56 2006] completed event "processor CPU1 00000081 00000000"

When the power management is used to anable hibernate the result is that the machine powers up with a fault, reboots itself and does not restore the desktop as it was. The log entry for this follows. (If this has happened because I have done something wrong, my apologies.) please advise any other information you may want/need.

[Tue Apr 4 08:13:59...

Read more...

Revision history for this message
dhalgren (muirhead) wrote : Re: [Bug 37303] Re: Fn+F1 does not work

Done. results on bug page. sorry ti took a while to get around to it. I
have managed to become ill over the past week.

cheers

bruce muirhead

On Mon, 2006-04-03 at 11:55 +0000, Paul Sladen wrote:

> If you enable SLEEP= suspend (it doesn't work on all laptop so it is only enabled by default on laptops which we definately know work), does the machine suspend and unsuspend quite happily.
>
> If it does, can you paste your dmidecode data, so that it can be whitelisted?

Revision history for this message
Paul Sladen (sladen) wrote : Re: Fn+F1 does not work

Hi Bruce,

I can't find your DMI decode data in order to whitelist this laptop. You mentioned it's "on the bug page", but I can't see it attached anywhere.

Can you upload the output of:

  $ sudo dmidecode --type system

please

Changed in hotkey-setup:
status: Rejected → Needs Info
Revision history for this message
Paul Sladen (sladen) wrote :

Hi Bruce,

I can't find your DMI decode data in order to whitelist this laptop. You mentioned it's "on the bug page", but I can't see it attached anywhere.

Can you upload the output of:

  $ sudo dmidecode --type system

please.

Revision history for this message
dhalgren (muirhead) wrote : bug 37303

Sorry folks, here is the data required:

# dmidecode 2.7
SMBIOS 2.3 present.

Handle 0x0001, DMI type 1, 25 bytes.
System Information
        Manufacturer: ASUSTeK Computer Inc.
        Product Name: A5E
        Version: 1.0
        Serial Number: SSN12345678901234567
        UUID: 20010000-1600-0080-BF5A-C0C000510110
        Wake-up Type: Power Switch

Handle 0x0023, DMI type 32, 20 bytes.
System Boot Information
        Status: No errors detected

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Marking as confirmed based on requested info having been supplied (this one fell though the triage cracks big time). Assigning to Paul Sladen for quick action (what with this having lingered so long).

Changed in acpi-support:
assignee: nobody → sladen
status: Needs Info → Confirmed
Paul Sladen (sladen)
Changed in acpi-support:
assignee: sladen → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package acpi-support - 0.120

---------------
acpi-support (0.120) jaunty; urgency=low

  [ Alexander Solodukhin ]
  * Correct suspend.d/55-down-interfaces.sh to point to
    /var/run/network/ifstate rather than /etc/network/run/ifstate.
    LP: #295544.

  [ Martin Pitt ]
  * Drop lib/*.config: I committed all sleep quirks to hal-info now
    (upstream, and in Jaunty). The ACPI_SLEEP whitelisting, as well as
    acpi-support's suspend/resume handling itself is not used by
    default any more, and almost all laptops support suspend/resume
    nowadays, so keeping a whitelist is the wrong approach.
    LP: #37303, #44781.
  * lib/device-funcs: Drop reading of .config files.
  * Drop vbesave, resume.d/17-video-restore.sh, suspend.d/
    80-video-pci-state.sh, suspend.d/80-video-vesa-state.sh:
    pm-utils and hal-info handle VBE/PCI status quirks.

  [ Scott James Remnant ]
  * suspend.d/88-time.sh, resume.d/50-time.sh: Remove since the kernel
    keeps the system clock in sync with the hardware clock over a
    suspend/resume cycle. LP: #312486, #218120, #158358, #157936.
  * debian/preinst: Remove on upgrade.
  * Remove the toshiba_acpi.modprobe file; this sets a kernel option that's
    been the default for ages.

 -- Scott James Remnant <email address hidden> Tue, 03 Mar 2009 17:29:01 +0000

Changed in acpi-support:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.