| 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 <=
a href=3D"attachment.cgi?id=3D136779&action=3Dedit" title=3D"dmesg with=
error">[details]
dmesg with error
R9 285 Tonga, I see in agd5f 4.17-wip there are commits to do with DVI dual
link.=20
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
Created atta=
chment 136780 [details]
xrandr with missing > 60Hz modes
Created attachment 1= 36782 [details] [review] Fix for dual-link DVI modes The error is unrelated. This patch should fix your dual-link DVI modes. It's hitting the mailing list soon, just took a bit longer than the rest of the = DVI patches. Note that we also see issues with non-native modes on one display = with this patch, but that's likely a monitor-specific issue.
Thanks, that works.
This is the same with non dc, but is there a reason they are a bit low?
1920x1080 (0x5b) 285.500MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 137.2=
6KHz
v: height 1080 start 1083 end 1088 total 1144 clock 119.9=
8Hz
1920x1080 (0x5c) 260.250MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 125.1=
2KHz
v: height 1080 start 1083 end 1088 total 1138 clock 109.9=
5Hz
1920x1080 (0x5d) 235.500MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 113.2=
2KHz
v: height 1080 start 1083 end 1088 total 1133 clock 99.9=
3Hz
I was hoping DC would differ from the old driver in giving exact Hz for the=
se.
(In reply to Andy Furniss from comment #3) > Thanks, that works. >=20 > This is the same with non dc, but is there a reason they are a bit low? >=20 > 1920x1080 (0x5b) 285.500MHz +HSync -VSync > h: width 1920 start 1968 end 2000 total 2080 skew 0 clock > 137.26KHz > v: height 1080 start 1083 end 1088 total 1144 clock > 119.98Hz >=20 > 1920x1080 (0x5c) 260.250MHz +HSync -VSync > h: width 1920 start 1968 end 2000 total 2080 skew 0 clock > 125.12KHz > v: height 1080 start 1083 end 1088 total 1138 clock > 109.95Hz >=20 > 1920x1080 (0x5d) 235.500MHz +HSync -VSync > h: width 1920 start 1968 end 2000 total 2080 skew 0 clock > 113.22KHz > v: height 1080 start 1083 end 1088 total 1133 clock= =20 > 99.93Hz >=20 > I was hoping DC would differ from the old driver in giving exact Hz for > these. Those are the modes from the EDID from your monitor: CEA extension block Extension version: 1 0 8-byte timing descriptors Detailed mode: Clock 235.500 MHz, 521 mm x 293 mm 1920 1968 2000 2080 hborder 0 1080 1083 1088 1133 vborder 0 +hsync -vsync=20 Detailed mode: Clock 260.250 MHz, 521 mm x 293 mm 1920 1968 2000 2080 hborder 0 1080 1083 1088 1138 vborder 0 +hsync -vsync=20 Detailed mode: Clock 285.500 MHz, 521 mm x 293 mm 1920 1968 2000 2080 hborder 0 1080 1083 1088 1144 vborder 0 +hsync -vsync
Thanks, stupid monitor rather than some rounding then :-)
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |