Fujitsu-Siemens C1110 enable suspend patch

Bug #52970 reported by Jörg Höhle
4
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Hi,
here's a patch to enable suspend/hibernate on my Fujitsu Siemens C1110 laptop (hibernate & sleep have been working since Hoary).

BTW, how were the acpi *.config created? Didn't I submit an entry to the hardware database? Can it be viewed online?

BTW2, I thought Debian+Ubuntu's packaging system would detect modified files and warn me or error out? I had applied this patch to the original Dapper distribution, but when I updated to 0.85, my patched file got overwritten by 0.85. How comes?
(I've already had cases where the packaging system showed me diffs and asked what to do; why not this time?)

--- FUJITSU SIEMENS.config.jch 2006-05-23 17:40:45.000000000 +0200
+++ /usr/share/acpi-support/FUJITSU SIEMENS.config 2006-07-07 12:53:43.000000000 +0200
@@ -11,6 +11,9 @@
  "LIFEBOOK S6120"*)
   ACPI_SLEEP=true
  ;;
+ "LIFEBOOK C1110"*)
+ ACPI_SLEEP=true
+ ;;
  "LIFEBOOK P7010"*)
   ACPI_SLEEP=true
  ;;

Regards,
 Jörg Höhle

Related branches

Revision history for this message
Jörg Höhle (joerg-cyril-hoehle) wrote :
Revision history for this message
Matthew Garrett (mjg59) wrote : Re: [Bug 52970] Re: Fujitsu-Siemens C1110 enable suspend patch

You weren't prompted because the file you edited isn't a configuration
file. The correct location for local changes there is
/etc/default/acpi-support

Revision history for this message
Paul Sladen (sladen) wrote :

Hi Jörg, thanks for that.

Config files are those in '/etc/'. This file is in '/usr/share/acpi-support/' as is part of the package normally - meaning that it will be replaced on package update.

Changed in acpi-support:
importance: Untriaged → Low
status: Unconfirmed → Confirmed
Daniel Hahler (blueyed)
Changed in acpi-support:
assignee: nobody → blueyed
status: Confirmed → In Progress
Revision history for this message
Daniel Hahler (blueyed) wrote :

The patch/fix has been included in the debdiff at bug 193842, and is waiting for sponsorship.
A test package is available from my PPA, if you want to test it (https://launchpad.net/~blueyed/+archive).

Changed in acpi-support:
assignee: blueyed → nobody
status: In Progress → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
acpi-support (0.106) hardy; urgency=low

  * Cherrypicked bugfix patches from Launchpad (LP: #193842)
  * lib/state-funcs: make wireless led work with asus-laptop (the new module);
    patch from Nicolò Chieffo (LP: #189889)
  * Add events/asus-video to support asus switch video hotkey; patch from
    Nicolò Chieffo (LP: #138228)
  * events/asus-wireless-2, asus-wireless-2.sh:
    Support Fn+F2 on Asus A8Js; patch from Matteo Collina (LP: #105929)
  * Fix the value range in sonybright.sh (0-7 instead of 1-8); patch from unggnu
    (LP: #136380)
  * "lib/FUJITSU SIEMENS.config":
    - Enable suspend for Fujitsu-Siemens C1110 (LP: #52970)
    - Enable STR for Fujitsu-Siemens Lifebook S7020, S7110
  * resume.d/50-time.sh, suspend.d/88-time.sh:
    Fix handling of hardware clock before/after suspend; patch from Rodrigo
    Novo (LP: #36815)
  * events/asus-*: Fix event key names for ASUS (HOTK); patch from
    Jeroen van der Vegt (LP: #25784)
  * Fix names in comments for events/panasonic-{mute,volume-down,volume-up}
  * debian/rules, README.toshiba: Drop toshiba_acpi.modprobe, which only
    contained an invalid/obsolete option "hotkeys_over_acpi" (LP: #180678)
  * debian/control: Standards-Version 3.7.3
  * Drop thinkpad_acpi.modprobe: the workarounds therein are not needed for
    thinkpad_acpi in Hardy anymore; investigations by Jerone Young (LP: #194679)
  * Add events/lenovo-eject to handle the Thinkpad eject button (Fn+F9); patch
    from Jerone Young (LP: #194609)

 -- Daniel Hahler <email address hidden> Thu, 06 Mar 2008 02:15:54 +0100

Changed in acpi-support:
status: Triaged → 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.