From: Peter Stuge <peter@stuge.se>
To: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
Cc: linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
mjg@redhat.com, eric@anholt.net
Subject: Re: no video output after suspend after "drm/i915: force mode set at lid open time"
Date: Mon, 26 Oct 2009 02:52:30 +0100 [thread overview]
Message-ID: <20091026015230.6438.qmail@stuge.se> (raw)
In-Reply-To: <4AE4BBBC.2070809@gmail.com>
Hi,
Riccardo Magliocchetti wrote:
> i lost video output, screen stays black, after suspend after commit
> c1c7af60892070e4b82ad63bbfb95ae745056de0 "drm/i915: force mode set at lid
> open time".
I also experience this symptom.
I have an IBM ThinkPad X40, chipset with integrated 855GM graphics.
The last release kernel I used was 2.6.30, with DRI enabled but no fb.
Gentoo xorg-server-1.6.1.092 with xf86-video-intel-2.7.1. All vanilla
kernels. With that kernel I would get the mode back on restore, but
the panel backlight would not come on, so it would be very difficult
to see the screen contents, especially in dim environments.
thinkwiki.org documents this symptom on X40 and many other models.
One suggested workaround is to chvt 1 and save a copy of the VGA
device PCI config space right before echo mem > /sys/power/state,
and write it back and run vbetool post immediately after resume,
followed by chvt 7 (or wherever X is). This workaround functioned
fairly well for me, but not always reliably, and of course it's a
bit of a hack. :)
I am now running drm-intel.git a83a44 from Oct 14 with KMS enabled
and xf86-video-intel 1556c62 from Oct 8, and the workaround
(understandably) does not function anymore. I've tried permutations
with only saving PCI config space and only running vbetool but no go.
(Before this I tried 2.6.31.1 with KMS, but it didn't do Xv.)
(Oh, and Xv performance with a83a44+1556c6 is lower than 2.6.30 nofb,
but that's somewhat secondary. MPlayer performs worse than VLC, but
both are worse than MPlayer with 2.6.30+2.7.1.)
Can I help solve this somehow?
//Peter
next prev parent reply other threads:[~2009-10-26 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 20:57 Riccardo Magliocchetti
2009-10-26 1:52 ` Peter Stuge [this message]
2009-10-26 16:02 ` Jesse Barnes
2009-10-26 19:28 ` Peter Stuge
2009-10-26 19:39 ` Rafael J. Wysocki
2009-10-26 19:42 ` Peter Stuge
2009-10-26 20:00 ` Rafael J. Wysocki
2009-10-26 16:05 ` Jesse Barnes
2009-10-27 21:21 ` Riccardo Magliocchetti
2009-10-27 21:26 ` Jesse Barnes
2009-10-31 13:42 ` Riccardo Magliocchetti
2009-10-31 13:46 ` Riccardo Magliocchetti
2009-11-04 19:19 ` Jesse Barnes
2009-11-04 20:16 ` Riccardo Magliocchetti
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=20091026015230.6438.qmail@stuge.se \
--to=peter@stuge.se \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=riccardo.magliocchetti@gmail.com \
/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
all inboxes | Powered by JetHome®