public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <sonne@debian.org>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
	dri-devel@lists.sourceforge.net,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: enabling kms for i915 disables brightness control and xrandr
Date: Sun, 29 Mar 2009 15:22:37 +0200	[thread overview]
Message-ID: <1238332957.4185.74.camel@localhost> (raw)
In-Reply-To: <20090329130702.GA23660@sucs.org>

On Sun, 2009-03-29 at 14:07 +0100, Sitsofe Wheeler wrote:
> (CC'ing dri-devel, Eric Anholt and Jesse Barnes)
> 
> On Sun, Mar 29, 2009 at 12:34:01PM +0200, Soeren Sonnenburg wrote:
> > Dear all,
> > 
> > I am not sure if this is just a user error/ too old userspace problem,
> 
> [User stated that 2.6.3 intel driver is being used in another email]

Just to not cause any (further?) confusion, I was using 2.6.1 when I
wrote that email and after compiling/upgrading to 2.6.3 a number of
problems vanished (like Xv works, screen resolution is correct, things
are *a lot* faster with UXA). However, brightness still only works via
setpci and xrandr only shows the 1024x600 modeline.

> > but I recognized that when I enable kernel based modesetting on a intel
> > 945 based samsung nc 10 netbook, I loose brightness control from within
> > X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and
> > xrandr does no longer have the all the modelines ranging from 1024x600
> > to 640x350... Trying to change resolutions / setting the brightness via
> > xrandr results in error messages being printed. 
> > 
> > Furthermore, this same flag disables Xv support..
> > 
> > However, screen switches between terminal and X are quite fast now
> > (without any flicker) and suspend and everything works stably.
> > 
> > I recognized that I can set the brightness via
> > 
> > setpci -s 00:02.1 F4.B=XX
> > 
> > (XX ranging from 00 to FF) just fine...

Soeren.
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962

  reply	other threads:[~2009-03-29 13:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 10:34 enabling kms for i915 disables brightness control and xrandr Soeren Sonnenburg
2009-03-29 11:01 ` Sitsofe Wheeler
2009-03-29 12:00   ` Soeren Sonnenburg
2009-03-31 21:58     ` Eric Anholt
2009-03-29 13:07 ` Sitsofe Wheeler
2009-03-29 13:22   ` Soeren Sonnenburg [this message]
2009-03-30 13:37     ` Soeren Sonnenburg
2009-03-30 21:34       ` Jesse Barnes
2009-03-30 22:57         ` Soeren Sonnenburg
2009-03-30 23:00           ` Jesse Barnes

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=1238332957.4185.74.camel@localhost \
    --to=sonne@debian.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=eric@anholt.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sitsofe@yahoo.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