From: Pavel Machek <pavel@ucw.cz>
To: daniel.vetter@intel.com, jani.nikula@linux.intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 4.7-rc0: redshift stopped working on intel display
Date: Sat, 28 May 2016 20:15:58 +0200 [thread overview]
Message-ID: <20160528181558.GA16247@amd> (raw)
In-Reply-To: <20160528101206.GA1870@amd>
On Sat 2016-05-28 12:12:06, Pavel Machek wrote:
> Hi!
>
> It looks like redshift stopped working. Even pretty crazy settings
> have no visible effect:
>
> pavel@amd:~$ redshift -O 1500 -g 6.6:6.6:6.6
> Using method `randr'.
> pavel@amd:~$ redshift -x
> Using method `randr'.
> pavel@amd:~$ uname -a
> Linux amd 4.6.0 #47 SMP Fri May 27 12:07:10 CEST 2016 x86_64 GNU/Linux
> pavel@amd:~$ redshift -O 5500 -g 6.6:6.6:6.6
> Using method `randr'.
> pavel@amd:~$ redshift -O 5500 -g 6.6:6.6:6.6 -b .3
> Using method `randr'.
> pavel@amd:~$
> pavel@amd:~$ lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller (rev 03)
> pavel@amd:~$
suspend-to-ram + resume cycle updates the display to match the
settings. Not convenient, but...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-28 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 10:12 4.7-rc0: redshift stopped working on intel display Pavel Machek
2016-05-28 18:15 ` Pavel Machek [this message]
2016-05-29 9:08 ` Matthew Auld
2016-06-08 13:06 ` [Intel-gfx] " 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=20160528181558.GA16247@amd \
--to=pavel@ucw.cz \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.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