mesa-dist-win VS ROCm

Go to the website https://github.com/pal1000/mesa-dist-win/releases and download mesa3d-23.3.0-release-msvc.7z, or whatever the latest version is. Just make sure it’s the release version. I assume either the MinGW version or the MSVC version will work, but I’ve only tried the MSVC version (and it's a smaller download).

The thing is, I'm only a little more smart than most normies and the instructions provided in the website aren't clear enough for me, so I figured out I could use a precompiled version of Mesa3D (if it even exists) for Windows for convenience sake. In my searches, I have found two Github repositories of pre-built Mesa3D drivers but I don't know if they're safe. (https://github.com/pal1000/mesa-dist-win) (https://github.com/mmozeiko/build-mesa)

all you need to do is download and run this thing called the "Mesa Injector"

The default WDDM driver provided by Microsoft for that GPU is a stripped down version of Intel's reference drivers without the control panel applet and the OpenGL dlls. The older Windows 7 driver will not install on anything newer because it is hardcoded to expect NT version 6.x. There were some patches released about a decade ago to fix this but you're better off running Mesa3D which re-implements OpenGL 3.3 in software https://github.com/pal1000/mesa-dist-win

I've managed to run Windows game (Homeworld Remastered) that uses modern OpenGL (3.3) on Crossover using Mesa Zink (OpenGL implementation over Vulkan) build for Windows that you can find here: mesa-dist-win. So if you check Homeworld Remastered or any other modern OpenGL game status on Crossover you will notice that it doesn't work. The issue is that Crossover OpenGL support is limited to 2.1 even if macOS itself supports up to 4.1. I'm not sure why but that means no modern OpenGL Windows games for us. This is where Mesa Zink comes to shine. Zink is Mesa (open source OpenGL/Vulkan/etc. and drivers implementations that are used by Linux and some other operating systems) driver that implements OpenGL on top of Vulkan. There is no native Vulkan on macOS but there is MoltenVK. I was curious if MoltenVK is good enough to run Zink and some big game and turns out it is. Homeworld is working fine and performance is good. I didn't play whole campaign so I can't promise it will work without any issues but I tested it in tutorials and Player vs CPU mode and it seems to work fine with only two minor issues - game will crash if anti aliasing is enabled and there is some minor graphical glitches with invisible ships.

If it's OpenGL-based, have you tried Zink? It was originally meant for Wine/Linux environments, but it should be in there as a normal DLL. It will redirect OpenGL calls to its own Vulkan-based compatibility layer.

i do wonder if you can use https://github.com/pal1000/mesa-dist-win to solve your opengl errors, ive only ever tried it in a vm though

Just gonna leave this here.

instead of 46 & 460 with my Windows drivers. So I think there is still something preventing your system from working. I would recommend you submit an issue and see if pal1000 or someone else can help troubleshoot the issue: https://github.com/pal1000/mesa-dist-win/issues

Try this like the Hiacenty did but for win https://github.com/pal1000/mesa-dist-win/issues/63

Yep, did exactly that. IMO he threw a fit, even though AMD was working with him squashing bugs. https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...

Ok, I wonder what's wrong. maybe it's this? https://stackoverflow.com/questions/4959621/error-1001-in-cl...

Nope. Anything about this on the arch wiki? Nope

This bug report[2] from 2021? Maybe I need to update my groups.

[2]: https://github.com/RadeonOpenCompute/ROCm/issues/1411

    $ ls -la /dev/kfd

HMM is, I believe, a Linux feature.

AMD added HMM support in ROCm 5.0 according to this: https://github.com/RadeonOpenCompute/ROCm/blob/develop/CHANG...

Woot AMD now supports APU? I sold my notebook as i hit a wall when trying rocm [1] Is there a list oft Wirkung apu's ?

[1] https://github.com/RadeonOpenCompute/ROCm/issues/1587

Last I heard he's abandoned working with AMD products.

https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...

They're talking about the meltdown he had on stream [1] (in front of the mentioned pirate flag), that ended with him saying he'd stop using AMD hardware [2]. He recanted this two weeks after talking with AMD [3].

Maybe he'll succeed, but this definitely doesn't scream stability to me. I'd be wary of investing money into his ventures (but then I'm not a VC, so what do I know).

[1] https://www.youtube.com/watch?v=Mr0rWJhv9jU

[2] https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...

[3] https://twitter.com/realGeorgeHotz/status/166980346408248934...

As for rocm support on consumer devices, AMD wont even clarify what devices are supported. https://github.com/RadeonOpenCompute/ROCm/pull/1738

He flamed out, then is back after Lisa Su called him (lmao)

https://geohot.github.io/blog/jekyll/update/2023/05/24/the-t...

https://www.youtube.com/watch?v=Mr0rWJhv9jU

https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...

https://geohot.github.io/blog/jekyll/update/2023/06/07/a-div...

On a personal level that youtube doesn't make him come off looking that good... like people are trying to get patches to him and generally soothe him/damage control and he's just being a bit of a manchild. And it sounds like that's the general course of events around a lot of his "efforts".

On the other hand he's not wrong either, having this private build inside AMD and not even validating official, supported configurations for the officially supported non-private builds they show to the world isn't a good look, and that's just the very start of the problems around ROCm. AMD's OpenCL runtime was never stable or good either and every experience I've heard with it was "we spent so much time fighting AMD-specific runtime bugs and specs jank that what we ended up with was essentially vendor-proprietary anyway".

On the other other hand, it sounds like AMD know this is a mess and has some big stability/maturity improvements in the pipeline. It seems clear from some of the smoke coming out of the building that they're cooking on more general ROCm support for RDNA cards, and generally working to patch the maturity and stability issues he's talking about. I hate the "wait for drivers/new software release bro it's gonna fix everything" that surrounds AMD products but in this case I'm at least hopeful they seem to understand the problem, even if it's completely absurdly late.

Some of what he was viewing as "the process happening in secret" was likely people doing rush patches on the latest build to accommodate him, and he comes off as berating them over it. Again, like, that stream just comes off as "mercurial manchild" not coding genius. And everyone knew the driver situation is bad, that's why there's notionally alpha for him to realize here in the first place. He's bumping into moneymakers, and getting mad about it.

I tried to train another model using InceptionResNetV2 and the same issues happens. Also, this happens even using the model.predict() method if using the GPU. Probably this is an issue related to the AMD Radeon RX 6700 XT or some mine misconfiguration. System Inormation: ArchLinux 6.1.32-1-lts - AMD Radeon RX 6700 XT - gfx1031 Opened issues: - https://github.com/RadeonOpenCompute/ROCm/issues/2250 - https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/issues/2125