Announcement

Collapse
No announcement yet.

AMDGPU Kernel Driver Is Working Out Well On Linux 5.0

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

  • AMDGPU Kernel Driver Is Working Out Well On Linux 5.0

    Phoronix: AMDGPU Kernel Driver Is Working Out Well On Linux 5.0

    While no measurable performance changes for either Polaris or Vega, the AMDGPU kernel driver in Linux 5.0 appears to be in largely good shape now mid-way through the cycle...

    http://www.phoronix.com/scan.php?pag...-AMDGPU-Stable

  • MasterCATZ
    replied
    I have R9 290's but can not get amdgpu to run with kernel 5.0 on Ubuntu 18.04 for me just keeps using radeon and if I black list I get nothing

    glxinfo | grep "OpenGL version"
    OpenGL version string: 3.0 Mesa 19.1.0-devel (git-9c46046 2019-04-07 bionic-oibaf-ppa)

    lspci -k | grep -EA3 'VGA|3D|Display'
    05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390]
    Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390]
    Kernel modules: radeon, amdgpu


    when I hit 4.19 radeon and amdgpu stopped working
    lspci -nnk | grep -i vga -A3 | grep 'in use'
    Kernel driver in use: i915


    I can roll back to kernels 4.17 ~ 4.18 and it works ?

    GRUB_CMDLINE_LINUX_DEFAULT="radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1"


    lspci -nnk | grep -i vga -A3 | grep 'in use'
    Kernel driver in use: i915
    Kernel driver in use: amdgpu
    Last edited by MasterCATZ; 04-07-2019, 06:28 AM.

    Leave a comment:


  • gedgon
    replied
    Originally posted by Venemo View Post
    With a single 4K 60Hz monitor there is no bug.
    I can confirm fixed SCLK clock on a RX 560 with a singe 4K @60Hz monitor without amdgpu.ppfeaturemask=0xffffffff kernel parameter.

    Leave a comment:


  • ernstp
    replied
    Originally posted by Brisse View Post
    Rebooted. Getting vrr_capable in xrandr, but I though there should be an vrr_enabled entry as well but there's not. Glxinfo is reporting Mesa 19.0-git as expected(
    The patch series went through quite a few iterations where properties came and went, I think that property was removed in the end and the Xorg.conf setting was added.

    Leave a comment:


  • Haxk20
    replied
    Originally posted by debianxfce View Post
    vrr_capable=0 means that it is not supported
    Missing the parameter with eDP means that there is no support in the driver or hardware. With RX570:
    Code:
    DisplayPort-0 connected 3840x2160+0+0
    vrr_capable: 1
    HDMI-A-0 disconnected
    vrr_capable: 0
    DVI-D-0 disconnected
    no vrr_capable variable available
    issue has been fixed. it was a bug. i know my VEGA 8 in ryzen 5 2500U supports it and rx560x does too so it must be supported on linux too. reported it and its fixed now.

    Leave a comment:


  • tuxd3v
    replied
    Originally posted by debianxfce View Post

    No changes in the idle governor. The CPU frequency governor slows down and is an optional feature of the Linux kernel so remove it. Using the Bios is a better way to control CPU power and fans. Power consumption depends of your other hardware too.
    Indeed, but what I was talking about is the Power draw for each power profile..
    In Linux is like crazy, on that mater..

    On Windows for example, there are better tunned profiles, and the AMD cards consume less power than in Linux, exactly because of the Power profiles..
    This for me should be one of the next key steps, for AMD,
    Because it doesn´t mater if your driver is more performant, if it his consuming tons of power, then the "Better Driver", is something difficult to classify..
    A 2 step way is needed like a loop, on each iteration
    1. Features
    2. Optimization

    Leave a comment:


  • dwagner
    replied
    I wish I could agree to the article's statement, but I cannot. It still only takes me minutes to reproduce the crash bug reported in https://bugs.freedesktop.org/show_bug.cgi?id=102322" on the latest git head version, a bug that has haunted amdgpu for about 18 months now.

    And as I already mentioned in another thread, there is a power usage regression in 5.0, again, with weird minimum clocks indicating that dynamic power management is still acting randomly:

    > cd /sys/class/drm/card0/device

    > xrandr --output HDMI-A-0 --mode 3840x2160 --rate 30
    > echo manual >power_dpm_force_performance_level
    > echo 0 >pp_dpm_mclk
    > echo 0 >pp_dpm_sclk
    > grep -H \\* pp_dpm_mclk pp_dpm_sclk
    pp_dpm_mclk:0: 300Mhz *
    pp_dpm_sclk:0: 214Mhz *

    > xrandr --output HDMI-A-0 --mode 3840x2160 --rate 50
    > echo manual >power_dpm_force_performance_level
    > echo 0 >pp_dpm_mclk
    > echo 0 >pp_dpm_sclk
    > grep -H \\* pp_dpm_mclk pp_dpm_sclk
    pp_dpm_mclk:1: 1750Mhz *
    pp_dpm_sclk:1: 481Mhz *

    > xrandr --output HDMI-A-0 --mode 3840x2160 --rate 60
    > echo manual >power_dpm_force_performance_level
    > echo 0 >pp_dpm_mclk
    > echo 0 >pp_dpm_sclk
    > grep -H \\* pp_dpm_mclk pp_dpm_sclk
    pp_dpm_mclk:0: 300Mhz *
    pp_dpm_sclk:6: 1180Mhz *

    Leave a comment:


  • Haxk20
    replied
    Originally posted by debianxfce View Post
    vrr_capable=0 means that it is not supported
    Missing the parameter with eDP means that there is no support in the driver or hardware. With RX570:
    Code:
    DisplayPort-0 connected 3840x2160+0+0
    vrr_capable: 1
    HDMI-A-0 disconnected
    vrr_capable: 0
    DVI-D-0 disconnected
    no vrr_capable variable available
    VEGA 8 has support for freesync as people got it working on this exact laptop on windows with little EDID edit which i will do on linux too.
    vrr_capable on HDMI is because there is nothing connected to it.
    Maybe its the initial implementation that doesnt have support for iGPU i guess.
    I hope i will get it working because freesync can help here a looot
    Last edited by Haxk20; 01-22-2019, 06:55 PM. Reason: added info

    Leave a comment:


  • Venemo
    replied
    Originally posted by aufkrawall View Post
    I just said that. Btw. it should suffice to enforce maximum VRAM pstate and not touching pstates for the GPU itself.
    That's not a real fix. Polaris already has this problem with 75Hz single display, while neither Vega nor other GPU vendors do.
    As a user, I don't care what the driver does, just that it shouldn't flicker my displays is all.

    Leave a comment:


  • Grogan
    replied
    That's good to hear, I got kernel shy with Linux 4.19... the amdgpu driver was failing on the ring buffer test while initializing DRM (R9 380/Volcanic Islands Tonga). I've been sticking with 4.18.20 since that and haven't revisited it (though I heard it's been fixed).

    Leave a comment:

Working...
X