A New Ubuntu Kernel Build With The Very Latest AMDGPU DC Patches For 4.15

[oleyska]

does this provide freesync?

how would one "boot the kernel with amdgpu.dc=1"?

how would one turn on freesync for a game or would it be on by default all the time?

i presume you just install the two debs, does order matter?

try take my user name into account before mocking my lack of knowledge.

1.\ Freesync: worked out of the box on vega for me - so seems like Yes.
2.\ Boot the kernel with amdgpu, it's kernel parametres, see (Should apply to ubuntu too):

https://wiki.archlinux.org/index.php/Kernel_parameters

https://wiki.archlinux.org/index.php/AMDGPU

3.\ Freesync is enabled by default.
4.\ I have had no issues with order.

[Brisse]

1.\ Freesync: worked out of the box on vega for me - so seems like Yes.

Are you sure about that? From my previous testing, it's shown up as enabled by default but the monitor stays at a fixed refresh rate. Do you have an FPS counter or dynamic frequency counter in your monitors OSD where you can confirm you are actually getting dynamic refresh rate?

I've just installed this kernel and I'm trying to get it to work, but recently I run into a problem where Ubuntu 17.10 beta seem to have broken GNOME X-sessions for me, so I can only run Wayland right now. I can tell Freesync is definitely not working on my Wayland session though.

I'm on a Fury connected to an MG279Q, and enabled DC with the amdgpu.dc=1 kernel parameter.

[Brisse]

On the other hand, I have good news about my previous audio sample rate issue. 44.1khz music now plays fine over display port on this kernel.

[oleyska]

Are you sure about that? From my previous testing, it's shown up as enabled by default but the monitor stays at a fixed refresh rate. Do you have an FPS counter or dynamic frequency counter in your monitors OSD where you can confirm you are actually getting dynamic refresh rate?

I've just installed this kernel and I'm trying to get it to work, but recently I run into a problem where Ubuntu 17.10 beta seem to have broken GNOME X-sessions for me, so I can only run Wayland right now. I can tell Freesync is definitely not working on my Wayland session though.

I'm on a Fury connected to an MG279Q, and enabled DC with the amdgpu.dc=1 kernel parameter.

I am sure, previous kernel worked too.
Vega, DC2 kernel now, aoc 28" something (4K) and freesync is working 100% sure.
On the other hand... powerplay doesn't seem to be that happy

[JordanL]

I am sure, previous kernel worked too.
Vega, DC2 kernel now, aoc 28" something (4K) and freesync is working 100% sure.
On the other hand... powerplay doesn't seem to be that happy

Freesync shouldn't be working on the dc-next kernel sent in the pull request, as the existing implementation makes use of new ioctls that cannot and should not be pulled in upstream. We want to work with the community on developing an Adaptive Sync solution which can benefit the entirety of DRM.

[Brisse]

Freesync shouldn't be working on the dc-next kernel sent in the pull request, as the existing implementation makes use of new ioctls that cannot and should not be pulled in upstream. We want to work with the community on developing an Adaptive Sync solution which can benefit the entirety of DRM.

That makes sense I guess.

I just got my x session working again after purging and reinstalling gnome-session, and now when i check xrandr, my monitor doesn't even show up as Freesync compatible like it used to do with older versions of the kernel (not that it ever actually worked, it just pretended to).

Question is, why does oleyska claim it is working on his Vega?

[oleyska]

Freesync shouldn't be working on the dc-next kernel sent in the pull request, as the existing implementation makes use of new ioctls that cannot and should not be pulled in upstream. We want to work with the community on developing an Adaptive Sync solution which can benefit the entirety of DRM.

it shows freesync for the monitor, it doesn't have tear, all seems good here...

[Brisse]

oleyska Could you run 'DISPLAY=:0 xrandr --prop' and paste the output for us?

No tearing doesn't necessarily mean that Freesync is working. It might just be traditional fixed rate v-sync which is what I get.

[oleyska]

oleyska Could you run 'DISPLAY=:0 xrandr --prop' and paste the output for us?

No tearing doesn't necessarily mean that Freesync is working. It might just be traditional fixed rate v-sync which is what I get.

oleyska@oleyska-UbuntuG:~$ ISPLAY=:0 xrandr --prop
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
TearFree: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
TearFree: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
DisplayPort-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm
_MUTTER_PRESENTATION_OUTPUT: 0
EDID:
00ffffffffffff0005e37928c1010000
051b0104b53e22783b08a5a2574fa228
0f5054230800d1c0818081409500b300
81c0010101014dd000a0f0703e803020
35006d552100001a565e00a0a0a02950
302035006d552100001e000000fc0055
3238373947360a2020202020000000fd
00283e8c8c3c010a202020202020018c
020326f14b101f041303120211010514
23090707830100006d030c0020001978
2000600102034d6c80a070703e803020
3a006d552100001a011d007251d01e20
6e2855006d552100001e023a80d07238
2d40102c96806d55210000188c0ad08a
20e02d10103e96006d55210000180000
000000000000000000000000000000cb
TearFree: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
3840x2160 60.00*+ 30.00 25.00 24.00 29.97 23.98
1920x2160 59.99
2560x1440 59.95
1920x1200 60.00
1920x1080 60.00 60.00 50.00 50.00 59.94
1600x1200 60.00
1680x1050 59.95
1280x1024 60.02
1440x900 59.89
1280x960 60.00
1280x800 60.00
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32 56.25
720x576 50.00
720x480 60.00 59.94
640x480 60.00 59.94
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
TearFree: auto
supported: off, on, auto
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad

[Brisse]

oleyska It doesn't mention Freesync, so you are most likely just getting normal v-sync, just like me.