dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89198] Setting Refresh Rate on monitor causes flickering/artifacting
Date: Fri, 20 Feb 2015 01:09:26 +0000	[thread overview]
Message-ID: <bug-89198-502-iRdCsxiREG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89198-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1628 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=89198

--- Comment #17 from andre35822@yahoo.com ---
(In reply to Alex Deucher from comment #14)
> (In reply to andre35822 from comment #13)
> > Just thought I would post a little update, I am in the process of getting my
> > system to use the new kernel. Ive already compiled it with the patch and
> > stuff, i am just having a bit of trouble creating a ramdisk (I am followeing
> > the arch linux wiki) although I will figure it out. Will the fixes from
> > comment 19 and 20 be implemented into the next release of video-ati or does
> > it still need testing? I am asking this so that if I know it isn't I may as
> > well compile another kernel with the patches from 19 and 20. Thank you btw
> > for everything.
> 
> FWIW, using make install in your kernel tree will usually handle the ramdisk
> update, but I'm not that familiar with arch, so if you are comfortable with
> that, I'd stick with that.
> 
> As for the patches from 19 and 20, I'm pretty confident they will work, but
> it would be nice to get some confirmation.
Alright so I tried out the kernel I compiled with the patch from comment 15 on
the other bug report, and either I didn't install the patch correctly (or it
didnt install correctly) or the patch is not solving the problem. I am still
getting the flickering/artifacts. I have attached an xorg log and dmesg log and
added comment15_patch to each of their file names so they are easily
distinguishable. Should I be compiling another kernel with the patches from
comment 19 and 20?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2800 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-02-20  1:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89198-502@http.bugs.freedesktop.org/>
2015-02-18  5:18 ` [Bug 89198] Setting Refresh Rate on monitor causes flickering/artifacting bugzilla-daemon
2015-02-18  5:33 ` bugzilla-daemon
2015-02-18  5:35 ` bugzilla-daemon
2015-02-18  5:35 ` bugzilla-daemon
2015-02-18  5:44 ` bugzilla-daemon
2015-02-18 13:22 ` bugzilla-daemon
2015-02-18 13:22 ` bugzilla-daemon
2015-02-18 14:06 ` bugzilla-daemon
2015-02-18 15:17 ` bugzilla-daemon
2015-02-18 15:22 ` bugzilla-daemon
2015-02-18 19:26 ` bugzilla-daemon
2015-02-18 20:56 ` bugzilla-daemon
2015-02-19 20:34 ` bugzilla-daemon
2015-02-19 20:41 ` bugzilla-daemon
2015-02-20  1:07 ` bugzilla-daemon
2015-02-20  1:07 ` bugzilla-daemon
2015-02-20  1:09 ` bugzilla-daemon [this message]
2015-02-20  1:12 ` bugzilla-daemon
2015-02-20  2:15 ` bugzilla-daemon
2015-02-20  3:21 ` bugzilla-daemon
2015-02-20  3:56 ` bugzilla-daemon

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-89198-502-iRdCsxiREG@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox