Fujitsu Siemens Lifebook E4010

[Marc Schiffbauer]

Binary package hint: acpi-support

Hi! Thanks for the great ACPI support....

Suspend-to-ram works for me! Please Whitelist!

I read
https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch
...
here is some additional Info:

Hotkeys
======
Hotkeys to be supported by the OS:
1 Mute (Fn+F3)
2 Volume-Down (Fn+F8)
3 Volume-Up (Fn+F9)

1 Mute (XLATE)
press: 0xe0 0x20
release: 0xe0 0xa0

2 Vol-Down (XLATE)
press: 0xe0 0x2e
release: 0xe0 0xae

3 Vol-Up (XLATE)
press: 0xe0 0x30
release: 0xe0 0xb0

Identifying your laptop
==============
system-manufacturer: "FUJITSU SIEMENS"
system-product-name: "LIFEBOOK E4010"
system-version: "" (empty line)

Need more/other Info?

Thanks for the support!

-Marc

[Marc Schiffbauer (mschiff)]

Hi again!

here is the updated Info for Edgy on my Laptop:

Fn+Mute / Fn+VolUp / Fn+VolDOwn now work out of the box now! Great!

But I think the following is still missing in "/usr/share/acpi-support/FUJITSU SIEMENS.config"

"LIFEBOOK E4010"*)
                ACPI_SLEEP=true
;;

Suspend-To-Ram: Does not work out of the Box anymore! :-(
But with the following settings in "/etc/default/acpi-support" it works like a charm:
(I think the important thing is to disable POST_VIDEO and SAVE_VIDEO_PCI_STATE)

ACPI_SLEEP=true
ACPI_SLEEP_MODE=mem
MODULES=""
MODULES_WHITELIST=""
SAVE_VBE_STATE=true
VBESTATE=/var/lib/acpi-support/vbestate
POST_VIDEO=false
SAVE_VIDEO_PCI_STATE=false
USE_DPMS=false

Cheers
-Marc

[Peter Whittaker (pwwnow)]

Marc, apologies for this lingering without comments for so long, sometimes reports fall through the cracks. There are standard debugging procedures for ACPI-related problems, hopefully we can address this problem with those.

First, please confirm that this is still a problem with a stock Edgy release.

Second, if you could test with Feisty and report back, that would be great. However, Feisty is development software, so testing with it on a production machine is not advised. If you can test with it, make sure you first back up important data.

If the problem persists, please provide the following information:

Update the report with the output of

uname -a

Attach to the report the output of the following commands, one attachment per command (please do not compress, please do not make one big attachment, and please do not include the information in-line):

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please be sure to use sudo, root privileges are required to get the information needed to make progress with this report.

Re which release to use when doing this: If you can test under Feisty and the problem persists there, use Feisty. If you cannot test under Feisty and the problem persists in Edgy, test under Edgy.

Of course, if the problem has disappeared, you can close the report or request that it be closed! Thanks!

[Marc Schiffbauer (mschiff)]

Hi Peter,

I still use the mentioned settings on my Laptop running Edgy.
I know that I needed to change settings to make it awake correctly after suspend-to-ram.

Since then I only installed all those security patches and such. I did not test with the original settings *now*, but my changed settings still work fine here.

As this is my production machine its not possible for me right now to test with feisty. Maybe I could upgrade to feisty prior to its release in the next couple of days as I did with edgy, especially if it would help you and especially if this would lead to better ACPI-support in feisty. Please let me know.

Here is the output you requested:

mschiff@bart:~$ uname -a
Linux bart 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux
mschiff@bart:~$

[Peter Whittaker (pwwnow)]

Mark as confirmed based on availability of requested logs and "workaround" (likely correct code change for this machine) supplied by user.

acpi-support seems to be the correct place for this report, since suspend-resume works when acpi-support variables are updated for this machine.

Devs, Once these have been changed, will a kernel config change be required to whitelist this box?

[Daniel Hahler (blueyed)]

This seems to be fixed in Hardy already. Please re-open, if I'm wrong here.
Thank you.