| What | Removed | Added |
|---|---|---|
| Component | Driver/AMDgpu | DRM/AMDgpu |
| Version | git | DRI git |
| Assignee | xorg-driver-ati@lists.x.org | dri-devel@lists.freedesktop.org |
| Product | xorg | DRI |
| QA Contact | xorg-team@lists.x.org |
Created attachment 118159 [details]<=
/span>
dmesg
Created attachment 118160 [det=
ails]
Xorg.0.log
Can you attach the output of xrandr --verbose? According to your xorg log, all the modes are found, e.g., [ 18.554] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 18.554] (II) AMDGPU(0): Modeline "3840x2160"x0.0 533.25 3840 3902 3950 4000 2160 2163 2168 2222 +hsync -vsync (133.3 kHz eP) [ 18.554] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync (67.5 kHz e) [ 18.554] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [ 18.554] (II) AMDGPU(0): Modeline "2560x1440"x0.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz e)
Created attachment 118167 [details]
xrandr
I too am experiencing this issue. I have two Dell P2715Q monitors connected to my Radeon Fury X and the highest resolution I can achieve is 1920x1080i. Looking through xrandr, it also confirms that the 3840x2160 resolution is not available on either monitor.
Alex: are you going to wait for the DAL to fix this or what wo= uld you guess?
Can you post your xorg config? Do you have a monitor section that has sync ranges that may be limiting what modes are added? I can't reproduce this. E.g., Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.0*+ 30.0 2560x1600 60.0 2560x1440 60.0 1920x1080 60.0 60.0 50.0 59.9 1920x1080i 60.1 50.0 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 59.9 1280x960 60.0 1152x864 75.0 1280x720 60.0 50.0 59.9 1440x576 50.0 1024x768 75.1 70.1 60.0 1440x480 60.0 59.9 832x624 74.6 800x600 72.2 75.0 60.3 56.2 720x576 50.0 720x480 60.0 59.9 640x480 75.0 72.8 66.7 60.0 59.9 720x400 70.1 DisplayPort-2 disconnected (normal left inverted right x axis y axis) HDMI-A-0 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 60.0*+ 1920x1080 60.0 59.9 1920x1080i 60.1 60.0 1600x1200 60.0 1280x1024 75.0 60.0 1152x864 75.0 1280x720 60.0 59.9 1024x768 75.1 60.0 800x600 75.0 60.3 720x576i 50.1 720x480 60.0 59.9 720x480i 60.1 60.1 640x480 75.0 60.0 59.9 720x400 70.1
Please attach a copy of your vbios. (as root) (use lspci to get the bus id) cd /sys/bus/pci/devices/<pci bus id> echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom
No monitor section. During this time i've actually bought a second 4k monitor of a different br= and. Attaching the xrandr with fglrx.
Created attachment 118780 =
[details]
xrandr fglrx
(In reply to Ernst Sj=C3=B6strand from comment #10) > No monitor section. > During this time i've actually bought a second 4k monitor of a differe= nt > brand. > Attaching the xrandr with fglrx. Does it work properly with amdgpu?
OK, the problem seems to be that amdgpu_connector_is_dp12_capa= ble returns false because adev->clock.default_dispclk is set to 50000.
[ 1.326627] [drm] initializing kernel modesetting (FIJI 0x1= 002:0x7300 0x174B:0xE329 0xCB). [ 1.326632] [drm] register mmio base: 0xFE600000 [ 1.326633] [drm] register mmio size: 262144 [ 1.326635] [drm] doorbell mmio base: 0xD0000000 [ 1.326635] [drm] doorbell mmio size: 2097152 [ 1.326647] amdgpu 0000:01:00.0: Invalid ROM contents [ 1.326659] ATOM BIOS: 113 [ 1.326664] ernst info_21.ulDefaultDispEngineClkFreq 50000
Created attachment 118827 [deta=
ils]
vbios.rom
Created attachment 118841 [details] [review] possible fix Does this patch fix the issue?
Works! There's another default value 54000 on line 676, but ma= ybe that's needed for "current_dispclk"?
| What | Removed | Added |
|---|---|---|
| Attachment #118841 is obsolete | 1 |
Created attachment 118844 = [details] [review] possible fix (In reply to Ernst Sj=C3=B6strand from comment #17) > Works! There's another default value 54000 on li= ne 676, but maybe that's > needed for "current_dispclk"? It shouldn't hurt anything, but lets just clean it up anyway.
Will this fix make it into the 4.3 RC kernels? or will this be published in 4.4?
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
It should go into 4.3: http://cgit.freedesktop.org/~agd5f/linux/log/?h=3Ddrm-fixes-4.3
| What | Removed | Added |
|---|---|---|
| Status | RESOLVED | CLOSED |
And the patch should even have a stable tag on it so it goes i= nto 4.2 as well. Anyway code is on it's way and I think we can close this ticket.