From: Andrea Arcangeli <aarcange@redhat.com>
To: Dan Carpenter <error27@gmail.com>,
chris@chris-wilson.co.uk, mjg@redhat.com, rpurdie@rpsys.net,
kernelorg@bof.de, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: back light conflict i915 vs dell-laptop
Date: Thu, 25 Nov 2010 15:41:57 +0100 [thread overview]
Message-ID: <20101125144157.GN6118@random.random> (raw)
In-Reply-To: <20101125093301.GT1522@bicker>
On Thu, Nov 25, 2010 at 12:33:01PM +0300, Dan Carpenter wrote:
> Patrick Schaaf has reported that the i915 driver is setting his
> backlight very dim when he starts GDM.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=23472
>
> It should be the dell-laptop platform driver controlling his backlight.
>
> Gnome tries to restore the backlight settings through the dell_laptop
> interface in sysfs but it fails. (Because the platform hardware refuses
> to set the settings to what it thinks they already are).
I think I run into the same problem, xset dpms force standby is enough
to trigger it, after that the backlight will never come up again. I
need to suspend to ram to be able to see my screen again. The screen
is on, just the backlight is off. Not dimmed to low level: completely
off.
Ironically xset dpms force off will come up right... but all screen
powermanagement will start with standby, so I'm stuck for the last few
weeks in presentation mode to be able to work on 37-rc1... It was fine
in .36 and it broke in 37-rc1.
I reported it to chris@chris-wilson.co.uk on 8 Nov but got no reply.
If you need me to test something let me know. It's super annoying when
I unplug the laptop and it exits presentation mode...
CONFIG_DRM_I915=y
CONFIG_DRM_I915_KMS=y
Thanks,
Andrea
next prev parent reply other threads:[~2010-11-25 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 9:33 back light conflict i915 vs dell-laptop Dan Carpenter
2010-11-25 14:41 ` Andrea Arcangeli [this message]
2010-11-28 18:05 ` Patrick Schaaf
2010-11-28 19:36 ` Dan Carpenter
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=20101125144157.GN6118@random.random \
--to=aarcange@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=error27@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernelorg@bof.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rpurdie@rpsys.net \
/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