<div dir="ltr"><br><div class="gmail_quote"><div dir="ltr"><div><div><div>Thanks for that. So my problem has narrowed down a bit (it still happens but I can fix it by changing the input colour format using the buttons on the side of the screen). The screen switches to use YCbCr input format:<br><br></div>** When the computer is booted up<br>** When I log in using kdm <br>** When the screen switches off after a period of inactivity<br><br></div>I've used this screen for more than a year and it hasn't happened before. Is there any reason that the driver might set the input colour format to YCbCr, or is it possible for a Radeon card to set a hint for input colour format that could persist across a reboot?<br><br><br></div>I'll try with the 4.1 kernel and see if anything changes.<br></div><div class="gmail_extra"><span class=""><br clear="all"><div><div><div dir="ltr">Owen Riddy<br>Email: <a href="mailto:owen.riddy@gmail.com" target="_blank">owen.riddy@gmail.com</a><br>Mobile: 040 163 2663<br><br>--<br></div></div></div> <br></span><div><div class="h5"><div class="gmail_quote">On 19 May 2015 at 23:21, Alex Deucher <span dir="ltr"><<a href="mailto:alexdeucher@gmail.com" target="_blank">alexdeucher@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Mon, May 18, 2015 at 4:32 AM, Owen Riddy <<a href="mailto:owen.riddy@gmail.com" target="_blank">owen.riddy@gmail.com</a>> wrote:<br> > No worries.<br> ><br> > It turns out that the problem was the "Color Format" of my screen. Dunno<br> > what that is, but it was configuring poorly and the open source driver seems<br> > happier when it is set to RGB rather than YCbCr. Maybe Catalyst is a bit<br> > more forgiving or maybe there is some configuration issue here I don't<br> > understand.<br> ><br> > My problem is solved; there may still be a minor bug here in how the<br> > auto-configuration of the driver works.<br> <br> </span>The open source driver does not support YCbCr at the moment.<br> <span><font color="#888888"><br> Alex<br> </font></span><span><br> ><br> > Owen Riddy<br> > Email: <a href="mailto:owen.riddy@gmail.com" target="_blank">owen.riddy@gmail.com</a><br> > Mobile: 040 163 2663<br> ><br> > --<br> ><br> > On 18 May 2015 at 17:41, Michel Dänzer <<a href="mailto:michel@daenzer.net" target="_blank">michel@daenzer.net</a>> wrote:<br> >><br> >> On 18.05.2015 16:28, Owen Riddy wrote:<br> >> > I have not, but if I reboot the computer to an install of Jessie using<br> >> > fglrx the tinge is not present; and it appeared shortly after updating<br> >> > to Jessie + unstable. I'll try a few things with the cable & report back<br> >> > if any of them have an impact, but the fglrx test suggests this problem<br> >> > is 100% fixable in software.<br> >><br> >> I guess I misunderstood the comments about fglrx in your original<br> >> report. I agree it's probably a software bug then, though it's more<br> >> likely in the kernel driver than in the Xorg driver.<br> >><br> >><br> >> --<br> >> Earthling Michel Dänzer | <a href="http://www.amd.com" target="_blank">http://www.amd.com</a><br> >> Libre software enthusiast | Mesa and X developer<br> ><br> ><br> ><br> </span><div><div>> _______________________________________________<br> > xorg-driver-ati mailing list<br> > <a href="mailto:xorg-driver-ati@lists.x.org" target="_blank">xorg-driver-ati@lists.x.org</a><br> > <a href="http://lists.x.org/mailman/listinfo/xorg-driver-ati" target="_blank">http://lists.x.org/mailman/listinfo/xorg-driver-ati</a><br> ><br> </div></div></blockquote></div><br></div></div></div> </div><br></div>