Quoting: XpanderLooks good. Now if it supported OpenGL also, we would have a tool that would work across all Linux Games.

Unlike Vulkan, OpenGL doesn't have layers concept, so it can't.

View this comment - View article - View full comments

That's a problem with Ubuntu, not with Mesa. No one is forcing you to use a distro with outdated graphics support. And if you are so inclined to use it instead of a distro which keeps such things up to date, you'll figure out how to work around such kind of issues.

Personally, I don't recommend Ubuntu for gaming.

View this comment - View article - View full comments

Quoting: Alm888

Quoting: ShmerlI don't see why it can't be developed at its own pace, and upstreamed at the same time, unless for some reason it can't be accepted back.

nVidia users do not use Mesa, so bundling the utility with it would mean needless drag in the system.

How much drag is there?

.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libVkLayer_MESA_overlay.so
/usr/lib/x86_64-linux-gnu/libvulkan_intel.so
/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so
/usr/share
/usr/share/bug
/usr/share/bug/mesa-vulkan-drivers
/usr/share/bug/mesa-vulkan-drivers/control
/usr/share/bug/mesa-vulkan-drivers/script
/usr/share/doc
/usr/share/doc/mesa-vulkan-drivers
/usr/share/doc/mesa-vulkan-drivers/changelog.Debian.gz
/usr/share/doc/mesa-vulkan-drivers/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/mesa-vulkan-drivers
/usr/share/vulkan
/usr/share/vulkan/explicit_layer.d
/usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json
/usr/share/vulkan/icd.d
/usr/share/vulkan/icd.d/intel_icd.x86_64.json
/usr/share/vulkan/icd.d/radeon_icd.x86_64.json

View this comment - View article - View full comments

I don't see why it can't be developed at its own pace, and upstreamed at the same time, unless for some reason it can't be accepted back.

View this comment - View article - View full comments

I'd prefer developers improving Mesa HUD instead of forking and then not upstreaming things.

Logging capabilities were taken straight from the Mesa HUD for the reference. It had it all along.

And Mesa HUD (i.e. Vulkan overlay) works for all Vulkan drivers as well, including Nvidia.

View this comment - View article - View full comments

Quoting: GuestYes but a bad situation for LTS distros which probably most users have due to the risk that rolling releases tend to break more easily (except of openSUSE Tumbleweed of course :-P). I'd wish it would be possible to install the AMDGPU driver also as a Kernel module to older Kernels with out backporting the actual driver from the latest kernles. :/

It is possible to use amdgpu via dkms.

See for example: https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/amd/dkms?h=amd-19.50 [External Link]

Not sure what exact kernels it supports, I've never used it.

The full list of releases is here: https://cgit.freedesktop.org/~agd5f/linux/refs [External Link]

Search for something like amd-xx.yy.

View this comment - View article - View full comments

Quoting: mrboeseKernel 5.3 that theoretically should support Navi 10.

I'm not surprised you are having issues - 5.3 has a ton of Navi related bugs, there is no reason to use it. Try kernel 5.5.

View this comment - View article - View full comments

Quoting: mrboeseI cannot understand why Navi cards still have those driver problems 6 months after launch.

What kernel are you using that still has Navi problems?

View this comment - View article - View full comments

Yep, just tested it by unsetting a field, works fine and says "you now have X unset fields". Thanks for the fix!

View this comment - View article - View full comments

Quoting: mrdeathjr*rdna is more or less gcn, no big changes - hopefully amd can offer some better with rdna 2

That's pretty wrong. There are a lot of big changes. And will be even more in RDNA2.

View this comment - View article - View full comments