rocm-arch VS ROCm

I never could get rocm/hip to work on mint after going round and round several times over months. I finally switched distros and had it running in minutes under an arch based distro using https://github.com/rocm-arch/rocm-arch

I struggled for some time trying to make AMD's Rocm/HIP work in linux so I could use my GPU with blender. Never could get it to work across several distros (mint, ubuntu, fedora). I finally dropped it and just ran GPUless for months. I have since found myself on Manjaro and gave it another try after finding this github. Using this on manjaro I was able to install rocm/hip in NO time and am now using blender with my AMD GPU in linux.

To do this, you need to use the repository: https://github.com/rocm-arch/rocm-arch and checkout to commit 135aa026557d7c11d5f446d6c01521535e9e5747

To make it brief. Trying to install rocm-opencl-runtime and rocm-hip-runtime from rocm-arch on github.

rocm-arch README

Then why doesn't it work unless I have this installed?

Yeah, I had to install rocm using this method https://github.com/rocm-arch/rocm-arch. Afaik, it doesn't replace mesa, but provides OpenCL and HIP.

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