From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104660] DC R9 285 dual link DVI modes not shown.
Date: Tue, 16 Jan 2018 18:18:19 +0000 [thread overview]
Message-ID: <bug-104660-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104660
Bug ID: 104660
Summary: DC R9 285 dual link DVI modes not shown.
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
Created attachment 136779
--> https://bugs.freedesktop.org/attachment.cgi?id=136779&action=edit
dmesg with error
R9 285 Tonga, I see in agd5f 4.17-wip there are commits to do with DVI dual
link.
I was hoping "Don't block dual-link DVI modes" would enable 120Hz my monitor
supports, which has always worked with without dc.
There is an error in dmesg - don't know if it's related. dmesg and xrandr
attached.
[drm:dal_bios_parser_init_cmd_tbl [amdgpu]] *ERROR* Don't have set_dce_clock
for v0
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2473 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 reply other threads:[~2018-01-16 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 18:18 bugzilla-daemon [this message]
2018-01-16 18:19 ` [Bug 104660] DC R9 285 dual link DVI modes not shown bugzilla-daemon
2018-01-16 18:54 ` bugzilla-daemon
2018-01-16 19:27 ` bugzilla-daemon
2018-01-16 19:31 ` bugzilla-daemon
2018-01-16 19:38 ` bugzilla-daemon
2018-01-29 23:46 ` 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-104660-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox