From: Stefan Seyfried <seife@suse.de>
To: Miroslav Ruda <ruda@ics.muni.cz>
Cc: suspend-devel List <suspend-devel@lists.sourceforge.net>,
linux-acpi@vger.kernel.org
Subject: Re: suspend to RAM on lifebook 7110
Date: Mon, 18 Dec 2006 07:38:16 +0100 [thread overview]
Message-ID: <20061218063816.GE26170@suse.de> (raw)
In-Reply-To: <20061207221831.GA31419@erebor.ics.muni.cz>
Hi Miroslav,
i'm taking suspend-devel into cc:, maybe somebody there has an idea about
this, too.
On Thu, Dec 07, 2006 at 11:18:31PM +0100, Miroslav Ruda wrote:
> Hi,
>
> I'm installing opensuse 10.2 on Fujitsu Siemens Lifebook 7110 (intel
> dual core, intel 965 chipset, intel 945 graphics chipset ...).
> Most of hardware works fine, but I have some problems with suspend to
> ram - suspend/resume using s2ram works fine, but display remains nearly
> black. I can see very hardly what's on display, but machine including
> network works fine.
So the graphics card is back up, it is really just the backlight that stays
off.
> I have tested s2ram on Suse 2.6.18.2-23-default or vanila 2.6.19+swsusp2
> with the same problems.
>
> s2ram -i returns
> This machine can be identified by:
> sys_vendor = "FUJITSU SIEMENS"
> sys_product = "LIFEBOOK S7110"
> sys_version = " "
> bios_version = "Version 1.18 "
>
> s2ram -f -a[0123] gives the same result, -s -p combinations doesn't work
> too. Switching back to text console doesn't help. Using xset dpms force
> off doesn't help too. The same problem I have both on text console and
> using Xserver.
Does this machine have fn-keycombos for adjusting the screen brightness?
Try those. I have seen a FSC Q-series (?) that needed just one touch of
the brightness-up key to turn back on the light.
Once we realized this, we could also poke it via the ACPI video module
(just increase the brightness by one level, then decrease it again) and
this also switched the light back on.
Maybe also playing with the "switch internal/external display" key combo
might do something.
I am of course not sure that this also helps on your machine, but it might :-)
Good luck,
Stefan
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-18 6:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 22:18 suspend to RAM on lifebook 7110 Miroslav Ruda
2006-12-18 6:38 ` Stefan Seyfried [this message]
2006-12-18 9:30 ` Frank Ursel
2006-12-18 16:53 ` Miroslav Ruda
-- strict thread matches above, loose matches on Subject: below --
2006-12-08 12:33 Frank Ursel
2006-12-08 21:13 ` Miroslav Ruda
2006-12-18 6:51 ` Stefan Seyfried
2006-12-18 11:11 ` Matthew Garrett
2006-12-18 11:29 ` Stefan Seyfried
2006-12-18 12:05 ` Matthew Garrett
2006-12-18 17:48 ` Stefan Seyfried
2006-12-18 20:00 ` Rafael J. Wysocki
2006-12-18 12:16 ` Pavel Machek
2006-12-18 15:55 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061218063816.GE26170@suse.de \
--to=seife@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=ruda@ics.muni.cz \
--cc=suspend-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox