From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105051] Radeon sets max_brightness to -1, breaking GNOME backlight control on Macbook Pro mid-2015 11,5
Date: Thu, 15 Oct 2015 04:47:13 +0000 [thread overview]
Message-ID: <bug-105051-2300-T8kzxpdTsh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-105051-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=105051
Felipe Ortiz <fortizc@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fortizc@gmail.com
--- Comment #14 from Felipe Ortiz <fortizc@gmail.com> ---
I can confirm the problem with 4eebd5a4e72697aac25a8a57d3f888a9d5f80370. I have
a MPB 11,5 with AMD/Intel graphics. I recompile the module (a previous version
of 4eebd5a4e72697aac25a8a57d3f888a9d5f80370) and brightness adjusts is working
again.
I see two problems:
1) If someone uses gpu-switch (https://github.com/0xbb/gpu-switch) with this
bug screen seem not work, after severals reboots (with different kernels) I can
access a terminal and execute gpu-switch -d and then screen seems work again.
2) If you use a Intel card (swiched with gpu-switch) the OSD (activated with
functions keys) is so slow and chromium have the same problem (temporary fix is
deactivate chromium hw acceleration) is this a intel driver bug?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-15 4:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 21:01 [Bug 105051] New: Radeon sets max_brightness to -1, breaking GNOME backlight control on Macbook Pro mid-2015 11,5 bugzilla-daemon
2015-09-28 15:07 ` [Bug 105051] " bugzilla-daemon
2015-09-28 15:53 ` bugzilla-daemon
2015-09-28 22:32 ` bugzilla-daemon
2015-09-29 1:15 ` bugzilla-daemon
2015-09-29 1:17 ` bugzilla-daemon
2015-09-29 10:42 ` bugzilla-daemon
2015-09-29 15:52 ` bugzilla-daemon
2015-09-30 2:57 ` bugzilla-daemon
2015-09-30 19:56 ` bugzilla-daemon
2015-10-01 7:42 ` bugzilla-daemon
2015-10-01 21:04 ` bugzilla-daemon
2015-10-01 21:13 ` bugzilla-daemon
2015-10-08 14:46 ` bugzilla-daemon
2015-10-08 15:14 ` bugzilla-daemon
2015-10-15 4:47 ` bugzilla-daemon [this message]
2015-10-22 9:37 ` bugzilla-daemon
2015-10-22 9:39 ` bugzilla-daemon
[not found] <bug-105051-5380@https.bugzilla.kernel.org/>
[not found] ` <bug-105051-5380-RlJ9dZd1ch@https.bugzilla.kernel.org/>
2015-10-22 9:36 ` Darren Hart
2015-10-25 16:58 ` Bruno Prémont
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=bug-105051-2300-T8kzxpdTsh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.