After installing the opencl plugin for pyrit, none of the pyrit commands work and just return "segmentation fault" However removing all plugins, I see: # pyrit benchmark Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com This code is distributed under the GNU General Public License v3+ Running benchmark (5090.8 PMKs/s)... | Computed 5090.82 PMKs/s total. #1: 'CPU-Core (SSE2)': 672.4 PMKs/s (RTT 2.9) #2: 'CPU-Core (SSE2)': 644.3 PMKs/s (RTT 2.9) #3: 'CPU-Core (SSE2)': 670.4 PMKs/s (RTT 3.0) #4: 'CPU-Core (SSE2)': 672.8 PMKs/s (RTT 2.9) #5: 'CPU-Core (SSE2)': 688.7 PMKs/s (RTT 2.9) #6: 'CPU-Core (SSE2)': 671.1 PMKs/s (RTT 3.0) #7: 'CPU-Core (SSE2)': 630.9 PMKs/s (RTT 3.1) #8: 'CPU-Core (SSE2)': 687.1 PMKs/s (RTT 3.0) Here is some additional info # fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: VESUVIUS (67B9) OpenGL version string: 4.4.12874 Compatibility Profile Context 14.10.1006.1001 Used AMD SDK 2.7 (previously tried 2.9 which didn't work either) Graphics Card: R9 295X2 If you would like me to run a debug command to collect more info, I would be glad to.
(In reply to tmrashed from comment #0) > # fglrxinfo > display: :0.0 screen: 0 > OpenGL vendor string: Advanced Micro Devices, Inc. > OpenGL renderer string: VESUVIUS (67B9) > OpenGL version string: 4.4.12874 Compatibility Profile Context > 14.10.1006.1001 > > Used AMD SDK 2.7 (previously tried 2.9 which didn't work either) That's not the open source driver. Please report your problem in a Catalyst bug tracker.
Thanks for your reply Michel. Can you provide the steps or instructions to install the open source driver? Also can you confirm that you are referring to the OpenGL driver? Thanks
For installing open source OpenCL support, see https://wiki.freedesktop.org/dri/GalliumCompute/#index3h3 . Note that you'll need to completely remove the Catalyst drivers first.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.