From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100871] radeon fails to initialize one DisplayPort monitor
Date: Mon, 08 Aug 2022 21:37:43 +0000 [thread overview]
Message-ID: <bug-100871-2300-LgNeiBgE6l@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-100871-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=100871
--- Comment #17 from Charles R. Anderson (cra@fea.st) ---
Still a problem on Fedora 36 / Linux kernel 5.18.16-200.fc36.x86_64. I'm now
using two newer monitors (DELL U3219Q) connected via DP instead of the previous
four monitors (2 DP, 2 DVI) and neither monitor turns on unless radeon.audio=0
is passed.
Maybe there needs to be a quirk added to the driver to keep audio turned off
for this card?
Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2460] (prog-if 00 [VGA
controller])
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-08-08 21:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 16:00 [Bug 100871] New: radeon fails to initialize one DisplayPort monitor bugzilla-daemon
2015-07-03 16:00 ` [Bug 100871] " bugzilla-daemon
2015-07-03 19:29 ` bugzilla-daemon
2015-07-04 21:19 ` bugzilla-daemon
2015-07-18 3:10 ` bugzilla-daemon
2015-10-20 22:48 ` bugzilla-daemon
2015-10-20 22:56 ` bugzilla-daemon
2015-10-20 22:57 ` bugzilla-daemon
2015-10-20 22:57 ` bugzilla-daemon
2015-10-20 22:58 ` bugzilla-daemon
2015-10-20 22:58 ` bugzilla-daemon
2016-08-08 15:23 ` bugzilla-daemon
2016-09-01 8:13 ` bugzilla-daemon
2016-09-01 8:19 ` bugzilla-daemon
2016-09-01 8:20 ` bugzilla-daemon
2016-09-06 10:28 ` bugzilla-daemon
2016-09-06 10:50 ` bugzilla-daemon
2016-09-06 18:13 ` bugzilla-daemon
2022-08-08 21:37 ` bugzilla-daemon [this message]
2022-08-08 21:48 ` 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-100871-2300-LgNeiBgE6l@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).