<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [DC] "Out of range" on a display connected to a DVI-D output of RX460 card via DVI-D<=>HDMI-A cable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100919#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [DC] "Out of range" on a display connected to a DVI-D output of RX460 card via DVI-D<=>HDMI-A cable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100919">bug 100919</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop-bugs@digital-trauma.de" title="Thomas R. <freedesktop-bugs@digital-trauma.de>"> <span class="fn">Thomas R.</span></a>
</span></b>
<pre>Harry, I tried amd-staging-drm-next and there is no corruption on the primary,
but my second monitor is dead. It may be something like <a class="bz_bug_link
bz_status_NEW "
title="NEW - Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors"
href="show_bug.cgi?id=91202">bug #91202</a> or something
else entirely, the dmesg output is very sparse (egrep drm|amd below).
What can I do now?
[ 0.583791] [drm] amdgpu kernel modesetting enabled.
[ 0.583968] [drm] initializing kernel modesetting (TONGA 0x1002:0x6939
0x1043:0x0486 0x00).
[ 0.584028] [drm] register mmio base: 0xFE980000
[ 0.584071] [drm] register mmio size: 262144
[ 0.584109] [drm] add ip block number 0 <vi_common>
[ 0.584140] [drm] add ip block number 1 <gmc_v8_0>
[ 0.584172] [drm] add ip block number 2 <tonga_ih>
[ 0.584207] [drm] add ip block number 3 <amdgpu_powerplay>
[ 0.584239] [drm] add ip block number 4 <dm>
[ 0.584271] [drm] add ip block number 5 <gfx_v8_0>
[ 0.584303] [drm] add ip block number 6 <sdma_v3_0>
[ 0.584334] [drm] add ip block number 7 <uvd_v5_0>
[ 0.584367] [drm] add ip block number 8 <vce_v3_0>
[ 0.584402] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[ 0.584434] [drm] probing mlw for device 1002:5a16 = 31cd02
[ 0.584472] [drm] VCE enabled in physical mode
[ 0.584775] amdgpu 0000:05:00.0: Invalid PCI ROM header signature: expecting
0xaa55, got 0xb60f
[ 0.585447] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment
size is 9-bit
[ 0.585490] amdgpu 0000:05:00.0: VRAM: 2048M 0x000000F400000000 -
0x000000F47FFFFFFF (2048M used)
[ 0.585526] amdgpu 0000:05:00.0: GTT: 1024M 0x0000000000000000 -
0x000000003FFFFFFF
[ 0.585563] [drm] Detected VRAM RAM=2048M, BAR=256M
[ 0.585594] [drm] RAM width 256bits GDDR5
[ 0.585843] [drm] amdgpu: 2048M of VRAM memory ready
[ 0.585874] [drm] amdgpu: 3072M of GTT memory ready.
[ 0.585907] [drm] GART: num cpu pages 262144, num gpu pages 262144
[ 0.586405] [drm] PCIE GART of 1024M enabled (table at 0x000000F400040000).
[ 0.587618] [drm] Found UVD firmware Version: 1.65 Family ID: 10
[ 0.588927] [drm] Found VCE firmware Version: 52.8 Binary ID: 3
[ 0.638265] [drm] Display Core initialized with v3.1.34!
[ 0.651084] [drm] SADs count is: -2, don't need to read it
[ 0.663759] [drm] SADs count is: -2, don't need to read it
[ 0.663823] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.663879] [drm] Driver supports precise vblank timestamp query.
[ 0.712563] [drm] UVD initialized successfully.
[ 0.921688] [drm] VCE initialized successfully.
[ 0.925673] [drm] fb mappable at 0xD0566000
[ 0.925738] [drm] vram apper at 0xD0000000
[ 0.925798] [drm] size 8294400
[ 0.925857] [drm] fb depth is 24
[ 0.925909] [drm] pitch is 7680
[ 0.926025] fbcon: amdgpudrmfb (fb0) is primary device
[ 1.123458] amdgpu 0000:05:00.0: fb0: amdgpudrmfb frame buffer device
[ 1.131506] [drm] Initialized amdgpu 3.25.0 20150101 for 0000:05:00.0 on
minor 0</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>