From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106191] FirePro v8800 Failure to recognize DisplayPort signal
Date: Wed, 25 Apr 2018 01:26:32 +0000 [thread overview]
Message-ID: <bug-106191-502-hyyExxCp5n@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106191-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1534 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106191
--- Comment #11 from François Jacques <francois.jacques@gmail.com> ---
The bug is caused by having both the audio signal and image simultaneously, it
seems.
After I added "radeon.audio=0" to the kernel argument list and rebooted, the
video interface and the monitor concluded their signal handshake successfully
(!) and I could switch the monitor to full res and, lo' behol', a 1440p image
(!!).
For future reference, should anyone have issues, try radeon.audio=0. If you
were relying on the radeon for audio, look for an alternative, or use a
DP-to-HDMI adapter and tolerate the lower resolution until the bug is fixed.
----
Googling on this specific symptom revealed multiple regressions on this matter
before, it could be a new one or it's been lurking for a while. Which means
either:
- tons of dupes in the DRM bugs list wrt radeon and DP /w audio enabled and
users don't know how to disable it.
- all radeon users having switched their audio off
- most radeon users gave up on their DisplayPort or their radeon-based card
altogether (perhaps switching brand in the process, frustration kicking in)
- it's a recent regression and I've been lucky to catch it before the kernel
goes mainstream in major distros.
I'll still provide a dmesg dump, this time with drm.debug=0x06 (0x06 any good?
any prefered value?) by rebooting with audio back on and image gone.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2348 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-25 1:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 13:23 [Bug 106191] Failure to recognize DisplayPort signal bugzilla-daemon
2018-04-23 13:24 ` bugzilla-daemon
2018-04-23 13:25 ` bugzilla-daemon
2018-04-23 13:27 ` bugzilla-daemon
2018-04-23 13:29 ` bugzilla-daemon
2018-04-23 13:34 ` bugzilla-daemon
2018-04-23 13:36 ` bugzilla-daemon
2018-04-23 13:42 ` [Bug 106191] FirePro v8800 " bugzilla-daemon
2018-04-23 14:43 ` bugzilla-daemon
2018-04-23 16:44 ` bugzilla-daemon
2018-04-23 16:48 ` bugzilla-daemon
2018-04-23 17:14 ` bugzilla-daemon
2018-04-24 11:10 ` bugzilla-daemon
2018-04-25 1:26 ` bugzilla-daemon [this message]
2018-04-25 2:14 ` bugzilla-daemon
2018-04-25 2:24 ` bugzilla-daemon
2019-11-19 9:33 ` 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-106191-502-hyyExxCp5n@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