Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DarkFoss
    replied
    Mabhatter Just follow the directions for installing and uninstalling from the Kernel/Mainline build page they work well enough. https://wiki.ubuntu.com/Kernel/MainlineBuilds
    I installed 17.10 under uefi and it's not uncommon to have to use sudo apt-get dist-upgrade after apt-get upgrade to get those signed kernels installed.

    Leave a comment:


  • randomsalad
    replied
    Originally posted by Mabhatter View Post
    Hi kids, I didn't do my homework. The new patches are great but now I can't run the normal Ubuntu 17.04 software updater. I know I saw a list of things to do... like uninstall the custom Kernel before running the standard update then reinstalling the custom stuff... can somebody point me to it. thanks in advance!
    Well, did you try the normal terminal method of
    Code:
    apt-get update
    followed by
    Code:
    apt-get upgrade
    ? Running a custom kernel shouldn't block you from package updates.

    On another note, it seems that the drm-next-4.15-dc branch was updated to work off of kernel 4.14-rc3 now.

    Leave a comment:


  • Mabhatter
    replied
    Hi kids, I didn't do my homework. The new patches are great but now I can't run the normal Ubuntu 17.04 software updater. I know I saw a list of things to do... like uninstall the custom Kernel before running the standard update then reinstalling the custom stuff... can somebody point me to it. thanks in advance!

    Leave a comment:


  • JordanL
    replied
    Originally posted by Brisse View Post

    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?

    Yeah, that's...odd. I'd guess one of two things. Either it's reporting that freesync is enabled when it isn't, or we screwed up and left it enabled We'll have a look.
    Last edited by JordanL; 09 October 2017, 01:49 AM.

    Leave a comment:


  • perpetually high
    replied
    Thanks for building these kernels, Michael. Running well for me so far (and fixed a resuming from sleep issue for me that was affecting all 4.13/4.14 kernel builds for me)

    I have an RX 480 and enabled DC with the kernel parameter (quiet splash amdgpu.dc=1 in my /etc/default/grub)

    1. HDMI/DP Audio working as intended

    2. Confirming that FreeSync does not work (as already mentioned not included in this pull request). Michael's previous Ubuntu kernel builds off that branch do have a working FreeSync if anyone needs.

    Code:
    $ cat /sys/module/amdgpu/parameters/dc
    1
    $ uname -a
    Linux ubuntu 4.13.0-rc5-phx-amdgpu-dc-2 #1 SMP Sat Oct 7 12:15:09 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
    $ DISPLAY=:0 xrandr --prop|grep freesync
    $

    Leave a comment:


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

    Leave a comment:


  • oleyska
    replied
    Originally posted by Brisse View Post
    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.
    [email protected]:~$ 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

    Leave a comment:


  • Brisse
    replied
    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.

    Leave a comment:


  • oleyska
    replied
    Originally posted by JordanL View Post

    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...

    Leave a comment:


  • Brisse
    replied
    Originally posted by JordanL View Post

    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?

    Leave a comment:

Working...
X