From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Pavel Machek <pavel@suse.cz>,
carbonated beverage <ramune@net-ronin.org>,
linux-kernel@vger.kernel.org
Subject: Re: Thinkpad brightness keys kill X on 2.6.26.5
Date: Wed, 1 Oct 2008 10:53:22 +0100 [thread overview]
Message-ID: <20081001095322.GA27987@srcf.ucam.org> (raw)
In-Reply-To: <48E2CB5A.1050809@goop.org>
On Tue, Sep 30, 2008 at 05:59:06PM -0700, Jeremy Fitzhardinge wrote:
> On my shiny new X200 running Fedora Rawhide, I'm finding that the
> brightness control keys work OK, but the backlight remains stuck off
> after a resume. The machine is working fine but the backlight is just
> off; I can see the display under a bright light. Switching consoles and
> poking about in /sys/class/backlight/acpi_video?/ didn't help.
Intel graphics, right? The DRM layer should handle full resume on modern
Intel hardware, but there's the potential for bugs. This is entirely
unrelated to ACPI, though.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-10-01 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 6:02 Thinkpad brightness keys kill X on 2.6.26.5 carbonated beverage
2008-09-25 7:07 ` CONFIG_ACPI_VIDEO on Thinkpad blanks display carbonated beverage
2008-09-25 10:07 ` Matthew Garrett
2008-09-25 19:09 ` carbonated beverage
2008-09-25 19:58 ` Henrique de Moraes Holschuh
2008-09-25 20:16 ` carbonated beverage
2008-09-30 23:19 ` Thinkpad brightness keys kill X on 2.6.26.5 Pavel Machek
2008-10-01 0:59 ` Jeremy Fitzhardinge
2008-10-01 9:40 ` Pavel Machek
2008-10-01 9:54 ` Matthew Garrett
2008-10-01 9:53 ` Matthew Garrett [this message]
2008-10-01 18:28 ` Jeremy Fitzhardinge
2008-10-01 18:33 ` Matthew Garrett
2008-10-01 18:55 ` Jeremy Fitzhardinge
2008-10-01 20:33 ` Pavel Machek
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=20081001095322.GA27987@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=ramune@net-ronin.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.