All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202657] New: amdgpu.dc=0 coupled with amdgpu.audio=0 causes fullscreen flickering with dvi-d to vga monitor setup (Polaris)
Date: Sat, 23 Feb 2019 17:35:51 +0000	[thread overview]
Message-ID: <bug-202657-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=202657

            Bug ID: 202657
           Summary: amdgpu.dc=0 coupled with amdgpu.audio=0 causes
                    fullscreen flickering with dvi-d to vga monitor setup
                    (Polaris)
           Product: Drivers
           Version: 2.5
    Kernel Version: All
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: eutychios23@gmail.com
        Regression: No

Hello i discovered, that when using "amdgpu.dc=0 amdgpu.audio=0" krenel
parameters in a dvi-d to vga monitor setup i get screen flickering with full
screen video players and redshift.If i use only "amdgpu.dc=0" there is no
screen flickering but hdmi audio is enabled (which is useless in my setup)

gpu: RX 550

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-02-23 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 17:35 bugzilla-daemon [this message]
2019-02-23 21:58 ` [Bug 202657] amdgpu.dc=0 coupled with amdgpu.audio=0 causes fullscreen flickering with dvi-d to vga monitor setup (Polaris) bugzilla-daemon
2019-02-23 22:03 ` bugzilla-daemon
2019-02-23 23:28 ` bugzilla-daemon
2019-06-15  7:25 ` 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-202657-2300@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.