public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Pavel Machek <pavel@suse.cz>,
	carbonated beverage <ramune@net-ronin.org>,
	linux-kernel@vger.kernel.org,
	"Bryan O'Sullivan" <bos@serpentine.com>,
	Karl Czajkowski <karlcz@bbswl.com>
Subject: Re: Thinkpad brightness keys kill X on 2.6.26.5
Date: Wed, 01 Oct 2008 11:55:30 -0700	[thread overview]
Message-ID: <48E3C7A2.6010901@goop.org> (raw)
In-Reply-To: <20081001183350.GA3240@srcf.ucam.org>

Matthew Garrett wrote:
> On Wed, Oct 01, 2008 at 11:28:34AM -0700, Jeremy Fitzhardinge wrote:
>
>   
>> I'm also using the vesa X server; I haven't tried using the intel one yet.
>>     
>
> Ah. In that case, I suspect the DRM module is never binding and may not 
> do its thing.
>   

OK, great.  Simply loading the i915 module makes the backlight come back 
after resume, even using the vesa X server.

Thanks,
    J

  reply	other threads:[~2008-10-01 18:55 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
2008-10-01 18:28       ` Jeremy Fitzhardinge
2008-10-01 18:33         ` Matthew Garrett
2008-10-01 18:55           ` Jeremy Fitzhardinge [this message]
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=48E3C7A2.6010901@goop.org \
    --to=jeremy@goop.org \
    --cc=bos@serpentine.com \
    --cc=karlcz@bbswl.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox