public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: carbonated beverage <ramune@net-ronin.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_ACPI_VIDEO on Thinkpad blanks display.
Date: Thu, 25 Sep 2008 12:09:30 -0700	[thread overview]
Message-ID: <20080925190930.GA17184@net-ronin.org> (raw)
In-Reply-To: <20080925100746.GA13185@srcf.ucam.org>

On Thu, Sep 25, 2008 at 11:07:46AM +0100, Matthew Garrett wrote:
> > Without CONFIG_ACPI_VIDEO, the above message don't appear.  From this point,
> > any pointers on figuring out why the ACPI features makes the screen go blank?
> 
> Yes. X assumed that any ACPI key press was a request to switch the video 
> output. Upgrade X.

Since CONFIG_ACPI_VIDEO wasn't required before 2.6.26.x to change the LCD
brightness, I'd rather the kernel go back to whatever it was doing for
2.6.25.x.  Upgrading X past what's currently packaged by the distribution
just to get a new kernel working is somewhat of a pain.

What change linked the brightness keys to CONFIG_ACPI_VIDEO?

-- DN
Daniel

  reply	other threads:[~2008-09-25 19:10 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 [this message]
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
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=20080925190930.GA17184@net-ronin.org \
    --to=ramune@net-ronin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox