Yes, that is correct. It is what keeps Darktable from having openCL support with AMD when using Mesa. AMDs packages for ROCM still don't support RH8 and I suspect will never support Fedora. I will eat a gun before I will use Ubuntu, how that became AMDs reference platform is a serious mystery.
Announcement
Collapse
No announcement yet.
Gallium3D's LLVMpipe Lands NIR Support Plus Radeon R600g NIR Support Is Forthcoming
Collapse
X
-
Originally posted by MadeUpName View PostAMDs packages for ROCM still don't support RH8 and I suspect will never support Fedora. I will eat a gun before I will use Ubuntu, how that became AMDs reference platform is a serious mystery.
I haven't tried installing the RHEL userspace packages on latest Fedora myself (vacation is coming so will try then) but my impression was that it should pretty much work, with most of the problems seeming to come from other OpenCL packages that were still there and getting in the way.
There is background work going on to improve the Fedora situation, including scripts to install ROCm on Fedora, but we need to do more general cleanup of the build environment before we can get to the point where it's packaged with Fedora. The scripts aren't being regularly updated yet - my impression is that they tend to move forward when developers are on vacation and can work on their own priorities:
Experimental and Intriguing Tools for ROCm. Contribute to ROCm/Experimental_ROC development by creating an account on GitHub.
Ubuntu LTS ended up as our reference platform simply because it was what most of our OEM and embedded customers were requesting. That is more for graphics than compute but it's pretty much the same driver stack and same developers.
The developers tend to move back and forth between Ubuntu and Fedora depending on which distro last did something annoying to them.
Most of our focus has been on enterprise distros, primarily RHEL/CentOS although as new customers come on stream we are getting demand for SLES and Debian as well.Last edited by bridgman; 29 November 2019, 12:11 AM.Test signature
- Likes 3
Comment
-
Originally posted by Michael View PostYes it does. (Though presumably he was probably meaning for Mesa OpenCL as opposed to 'proprietary' drivers. Just like Intel's OpenCL NEO has images + CL 2.0/2.1, etc)Last edited by bridgman; 29 November 2019, 12:10 AM.Test signature
- Likes 4
Comment
-
Originally posted by bridgman View Post
It's a sad day when open source out of tree drivers get described as "proprietary" just because they are not upstream
ROCM very much is up stream what is missing is down stream. What I remember from about 6-9 months ago was some one posting that the code for thunk wasn't fit for purpose because of all of the links in it pointing to the wrong places. Going through and changing those every time AMD patched would be too painful for a packager and a solution needed to be found. Who ever posted that proposed helping the AMD coders understand how the GNU tool set could help with that and offered to help. To the best of my knowledge that wasn't followed up on. ROCM may be open source but it certainly isn't an open source project. If people started submitting patches to modify it to work with the GNU tool set would AMD accept those patches? If not then whiie there may be an upstream implementation it may never be usable again by any one not running Ubuntu. So if you use some thing other than Ubuntu does a ROCM driver actually exist?
Don't get me wrong I like AMD and have stuck with them for both my CPU and graphics needs even when they flat out sucked next to the competition. I am happy to see them with some strut in their step again after all these years. But OpenCL is a real thing now and if you want to get work done you need it. Having to reinstall the OS every time I patch because I am stuck with AMDGPU isn't a functional solution. If NVidia gives me what I need and AMD doesn't then I am going to have to switch. I hate NVidia and yes their drivers are proprietary. But they also work with every thing I need and give me functionality I can't get from AMD. I wish that wasn't the case.
Comment
-
Originally posted by MadeUpName View PostI take your point. But your kind of stretching that beyond what I actually mean.
Originally posted by MadeUpName View PostROCM stopped working for every one running DR after ROCM 1.2 and people that can't stick with RH7 can't use it. My graphics card shouldn't be deciding which OS and which software I will use.
Originally posted by MadeUpName View PostROCM very much is up stream what is missing is down stream. What I remember from about 6-9 months ago was some one posting that the code for thunk wasn't fit for purpose because of all of the links in it pointing to the wrong places. Going through and changing those every time AMD patched would be too painful for a packager and a solution needed to be found. Who ever posted that proposed helping the AMD coders understand how the GNU tool set could help with that and offered to help. To the best of my knowledge that wasn't followed up on.
ROCM may be open source but it certainly isn't an open source project. If people started submitting patches to modify it to work with the GNU tool set would AMD accept those patches? If not then whiie there may be an upstream implementation it may never be usable again by any one not running Ubuntu. So if you use some thing other than Ubuntu does a ROCM driver actually exist?
One last thing - my understanding is that you don't actually need to build everything from source to get it running on Fedora... the existing packages have at least worked in the past (don't know if anyone has tested recently). I'll be setting up a new system over the holidays so will try to get it running with Fedora and ROCm stack. Worst case it will make me as unhappy as youLast edited by bridgman; 29 November 2019, 02:51 PM.Test signature
- Likes 2
Comment
Comment