Announcement

Collapse
No announcement yet.

Mesa 19.2.4 Released As Emergency Update After 19.2.3 Broke All OpenGL Drivers

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

  • finalzone
    replied
    Originally posted by jrch2k8 View Post

    yeah, I did gave up on ROCm, is an impossible mess to sort through. For now i'm using amdgpu-pro opencl from AUR while i'm anxiously waiting for Clover over NIR project to reach CL 1.2 at least since at least part of HMM for AMDGPU already landed on the kernel.

    I think future wise this solution will be wayyyy better for 99% of the cases than ROCm.
    Interesting enough, rocm version is the only opencl working on Davinci Resolve.

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by abott View Post

    Go run every line of code in the driver and come back to report how easy it is to make sure that happens. In every combination of code, too.
    If we're speaking about corner cases, you're right. But this bug hits every driver in Mesa. It's not a case of every line of code and every combination of code.

    Leave a comment:


  • geearf
    replied
    Originally posted by abott View Post

    Go run every line of code in the driver and come back to report how easy it is to make sure that happens. In every combination of code, too.
    That's what testing is for, they should run tests, I'm sure Intel can afford it.

    Leave a comment:


  • DanL
    replied
    Originally posted by kpedersen View Post
    I am sure many Linux users would update to 19.2.3, even if the emergency update hadn't been replaced just because "its newer!
    Well, most Linux users have that automatically taken care of by their package manager. And the ones who do it manually are probably using mesa from git.

    Leave a comment:


  • ResponseWriter
    replied
    Hopefully fixes the bug where using Kate on Plasma Wayland session doesn't update the display, so I end up blindly typing and not seeing any change on screen. Turning off/on composition via keyboard shortcut seems to fix it.

    Leave a comment:


  • kpedersen
    replied
    I am sure many Linux users would update to 19.2.3, even if the emergency update hadn't been replaced just because "its newer!" XD

    Leave a comment:


  • jrch2k8
    replied
    Originally posted by ms178 View Post

    That is one reason why I started to read the gfx-related mailing lists years ago, for spotting hw bugs and workarounds. Even though I cannot judge their significance, it more or less makes an impact on the quality of the product. And especially with ROCm, some of these hardware issues left customers out in the cold (e.g Tonga). My 6770M laptop experience wasn't exactly great either, you cannot even use DX11 on Windows 10 anymore and if you don't disable the lowest power state, you get weird minute long delays in 2D desktop usage. Despite all of this, I really like AMD's products (running Ryzen + Vega 56 on my main rig), but I hope that with their improving financials AMD can improve their processes to avoid these long list of hardware and software issues in the future.
    yeah, I did gave up on ROCm, is an impossible mess to sort through. For now i'm using amdgpu-pro opencl from AUR while i'm anxiously waiting for Clover over NIR project to reach CL 1.2 at least since at least part of HMM for AMDGPU already landed on the kernel.

    I think future wise this solution will be wayyyy better for 99% of the cases than ROCm.

    Leave a comment:


  • ms178
    replied
    Originally posted by jrch2k8 View Post

    Ironically i use mesa-git daily(self compiled for the custom flagsness) and that didn't broke on RadeonSI for me(at least in the last 2 months).

    Also as an AMD only guy(for GPUs, i hate nVidia Blob), i can tell you that at least for Polaris, Tahiti, Cape Verde and Mullins Mesa rarely breaks for me, most of my issues with RadeonSI came from LLVM trunk breaking down.

    You maybe right tho because there are certain families of AMD GPU with serious bugs like Tonga, Hawaii and other that need lots of workarounds and the more workarounds the more chance something will break for those chips
    That is one reason why I started to read the gfx-related mailing lists years ago, for spotting hw bugs and workarounds. Even though I cannot judge their significance, it more or less makes an impact on the quality of the product. And especially with ROCm, some of these hardware issues left customers out in the cold (e.g Tonga). My 6770M laptop experience wasn't exactly great either, you cannot even use DX11 on Windows 10 anymore and if you don't disable the lowest power state, you get weird minute long delays in 2D desktop usage. Despite all of this, I really like AMD's products (running Ryzen + Vega 56 on my main rig), but I hope that with their improving financials AMD can improve their processes to avoid these long list of hardware and software issues in the future.

    Leave a comment:


  • jrch2k8
    replied
    Originally posted by Strunkenbold View Post
    They rely soly on automated tests. If a case like that didn't get test there, every gets boom.
    Especially RadeonSI is extremely error prone. Two devs simply can't handle it. And they can be lucky, that valve sponsors some talented people.
    In anyway they need too long to fix bugs. And they don't have control about performance. Performance regressions get in most cases not fixed at all.
    Ironically i use mesa-git daily(self compiled for the custom flagsness) and that didn't broke on RadeonSI for me(at least in the last 2 months).

    Also as an AMD only guy(for GPUs, i hate nVidia Blob), i can tell you that at least for Polaris, Tahiti, Cape Verde and Mullins Mesa rarely breaks for me, most of my issues with RadeonSI came from LLVM trunk breaking down.

    You maybe right tho because there are certain families of AMD GPU with serious bugs like Tonga, Hawaii and other that need lots of workarounds and the more workarounds the more chance something will break for those chips

    Leave a comment:


  • Britoid
    replied
    I was curious as to why Fedora hadn't updated yet.

    Leave a comment:

Working...
X