06-17-2019 10:52 AM
Yes I see that issue on slackware live, I tested the iommu fix on Ubuntu and it did work on that distro. Is there a reason to be using slackware verses using one of the other Linux distros
06-18-2019 11:59 AM
I tested the live image of slackware adding the iommu=pt to the end of the cmdline and it did work for me the kfd loaded correctly. I tried putting it in the middle of the line and when I did a cat /proc/cmdline after booting it was not there so please verify it is really added to the cmdline
06-18-2019 12:18 PM
It's still not working for me.
I guess, if you say it is working for you, then it's just a matter of me trying a few more things.
I'll try different kernel branches or something ...
06-19-2019 03:50 AM
06-19-2019 03:32 PM
I just tried that
grep kfd dmesg-live.txt
[ 16.033740] kfd kfd: Initialized module
[ 16.351490] kfd kfd: Allocated 3969056 bytes on gart
[ 16.351633] kfd kfd: Failed to resume IOMMU for device 1002:15dd
[ 16.351802] kfd kfd: device 1002:15dd NOT added due to errors
device not added due to errors, but the modules load and it seems to work.
I've now replicated this setup on my main install. iommu had to be compiled as a module, not statically, and iommu=pt was need.
I guess I can live with any other issues, opencl is now working with rocm.