OK, there is more. Finally, Linux user have libOpenCL.so shipped with the Catalyst driver. So there is no more need to install the SDK.
Unfortunally, if you have it already installed, you have to uninstall it now. The best way to avoid problems is to completly remove the SDK directory.
With SDK 2.4 just remove it. But try to remember, you may have added some LD_LIBRARY_PATH exports in your configs. Remove them.
With SDK 2.5 the installer installs some files in /etc/ld.so.conf.d. Make sure you remove them too and run ldconfig afterwards. It also adds some lines at the end of /etc/profile. You also need to clear them. You may now to reboot now.
After i did that, the same original 100% CPU bug came back. Multiple threads using lots of CPU power as if there was no change at all. Well, at least we do not need the SDK any longer.
One more thing to mention is that the libOpenCL.so.1 required an symlink so that oclHashcat-lite64.bin find it on startup:
Unfortunally, if you have it already installed, you have to uninstall it now. The best way to avoid problems is to completly remove the SDK directory.
With SDK 2.4 just remove it. But try to remember, you may have added some LD_LIBRARY_PATH exports in your configs. Remove them.
With SDK 2.5 the installer installs some files in /etc/ld.so.conf.d. Make sure you remove them too and run ldconfig afterwards. It also adds some lines at the end of /etc/profile. You also need to clear them. You may now to reboot now.
After i did that, the same original 100% CPU bug came back. Multiple threads using lots of CPU power as if there was no change at all. Well, at least we do not need the SDK any longer.
One more thing to mention is that the libOpenCL.so.1 required an symlink so that oclHashcat-lite64.bin find it on startup:
Quote:$ cd /usr/lib
$ ln -s libOpenCL.so.1 libOpenCL.so
$ cd /usr/lib32
$ ln -s libOpenCL.so.1 libOpenCL.so