From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91302] radeon.audio=1 causes weird issues with 7950
Date: Sat, 11 Jul 2015 01:06:43 +0000 [thread overview]
Message-ID: <bug-91302-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91302
Bug ID: 91302
Summary: radeon.audio=1 causes weird issues with 7950
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: contrib@kliznoe.com
When I have radeon.audio set to 1, My displayport audio output is deeper then
normal and my hdmi screen becomes blurry and has a pink line to the left of it.
This doesn't happen when radeon.audio is set to 0 or in Windows.
OS : Arch Linux with Gnome3 and xf86-video-ati-git from the AUR
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2053 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
next reply other threads:[~2015-07-11 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 1:06 bugzilla-daemon [this message]
2015-07-11 20:41 ` [Bug 91302] radeon.audio=1 causes weird issues with 7950 bugzilla-daemon
2015-07-16 19:26 ` [Bug 91302] radeon.audio=1 causes " bugzilla-daemon
2015-07-26 19:49 ` bugzilla-daemon
2015-07-27 7:23 ` bugzilla-daemon
2015-07-27 13:17 ` bugzilla-daemon
2015-08-05 21:54 ` bugzilla-daemon
2015-08-05 21:55 ` bugzilla-daemon
2015-08-05 21:55 ` bugzilla-daemon
2015-08-06 20:01 ` 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-91302-502@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 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.