Ati Driver | Stream sdk 2.2 (Opencl 1.1) | CAL++ | cpyrit_calpp |

cd
apt-get install libboost-dev cmake
tar xvfz calpp-*.tar.gz
cd calpp-*
cmake .
make
make install

Im stuck at this part. I get to the cd calpp-*( I take it i enter my version i have) then i go to do cmaek . and i get this:root@bt:~/calpp-0.90# cmake .
-- ================================================== =========
-- ATI CAL include directory LIB_ATICAL_INCLUDE-NOTFOUND
-- ATI CAL cl library directory /usr/lib
-- ATI CAL rt library directory /usr/lib
-- Boost version 1_34_1
-- ================================================== =========
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
LIB_ATICAL_INCLUDE
used as include directory in directory /root/calpp-0.90
used as include directory in directory /root/calpp-0.90/examples
used as include directory in directory /root/calpp-0.90/regression

-- Configuring done
and when i try to do make it says not targets specified and no make fille

Followed the guide up to pyrit install:

Code:

---

root@bt:~/pyrit_svn/pyrit# ./setup.py build
running build
running build_py
creating build
creating build/lib.linux-i686-2.5
copying pyrit_cli.py -> build/lib.linux-i686-2.5
creating build/lib.linux-i686-2.5/cpyrit
copying cpyrit/__init__.py -> build/lib.linux-i686-2.5/cpyrit
copying cpyrit/cpyrit.py -> build/lib.linux-i686-2.5/cpyrit
copying cpyrit/util.py -> build/lib.linux-i686-2.5/cpyrit
copying cpyrit/pckttools.py -> build/lib.linux-i686-2.5/cpyrit
copying cpyrit/config.py -> build/lib.linux-i686-2.5/cpyrit
copying cpyrit/network.py -> build/lib.linux-i686-2.5/cpyrit
copying cpyrit/storage.py -> build/lib.linux-i686-2.5/cpyrit
running build_ext
building 'cpyrit._cpyrit_cpu' extension
creating build/temp.linux-i686-2.5
creating build/temp.linux-i686-2.5/cpyrit
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c cpyrit/_cpyrit_cpu.c -o build/temp.linux-i686-2.5/cpyrit/_cpyrit_cpu.o -Wall -fno-strict-aliasing -DVERSION="0.4.1-dev (svn r304)" -maes -mpclmul
cc1: error: unrecognized command line option "-maes"
cpyrit/_cpyrit_cpu.c:1: error: pc0 is not valid precision setting (32, 64 or 80)
error: command 'gcc' failed with exit status 1

---

Any hints?

Checked out revision 304.

Quote:

---

Originally Posted by azboy

yay, finally figured out how to run my HD 5970 above 70,000 PMK/s! Problem was crossfire being enabled. I was mislead at first because "aticonfig --lsch" says crossfire was disabled. But if you run the command "aticonfig --lscs" it showed enabled, wtf?!

So to disable crossfire I had to do the following:
1. aticonfig --adapter=all --initial (this reconfigures /etc/X11/xorg.conf and also makes a copy of the original as xorg.conf.fglrx-1)
2. restart x server by press control+alt+backspace
3. type startx once at the command prompt
4. run "aticonfig --lscs" to ensure it says disabled. If not, run "aticonfig --adapter=all --cf=off" and restart X again from step 2
5. if you do "pyrit list_cores" it should only list one GPU, don't worry just need a simple command to access the other gpu.
6. type "export DISPLAY=:0" to access the other GPU.
7. Run pyrit list_cores again and should get both GPUs now.
8. Run pyrit benchmark and you should be getting PMK/s in the 100,000 range. I get around 145,000 PMK/s :)

---

tnx for post. now im getting 100,000 pmk/s :) but.. i would like more :P what else need to be done? what spec is ur pc?

root@bt:~/cpyrit_calpp# pyrit list_cores
/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py:63: UserWarning: WARNING: Version mismatch between <module 'cpyrit._cpyrit_cpu' from '/usr/lib/python2.5/site-packages/cpyrit/_cpyrit_cpu.so'> ('0.4.0') and <module 'cpyrit._cpyrit_calpp' from '/usr/lib/python2.5/site-packages/cpyrit/_cpyrit_calpp.so'> ('0.4.0-dev (svn r304)')

"('%s')\n" % (_cpyrit_cpu, _cpyrit_cpu.VERSION, mod, ver))
Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

The following cores seem available...
#1: 'CAL++ Device #1 'AMD REDWOOD''
#2: 'CPU-Core (SSE2)'
#3: 'CPU-Core (SSE2)'
#4: 'CPU-Core (SSE2)'

Please help me to resolve this recurring problem with me:confused:

thx .:D

This is just a warning and should not affect performance. For more information refer to ---> http://code.google.com/p/pyrit/issues/detail?id=265 and ---> http://code.google.com/p/pyrit/issues/detail?id=275

ok thx he is working now

Quote:

---

Originally Posted by dfghjkl

tnx for post. now im getting 100,000 pmk/s :) but.. i would like more :P what else need to be done? what spec is ur pc?

---

try editing /usr/lib/python2.5/site-packages/cpyrit/cpyrit.py and change "ncpu=1" to equal the number of cpu cores on you system.

I overclocked the GPU to 850 Mhz which gets about 150,000 PMK/s but really it's not a huge different in actual speed given the amount of power consumption and heat.

my setup is a powercolor hd 5970, i7 980x, GIGABYTE GA-X58A-UD9 motorboard, 24GB RAM. now running Ubuntu 64bit to make better use of RAM and CPU cores.

Hey peops thought I'd come here to ask are any of you lot using your gpu rigs to mine bitcoins ?? I was thinking of setting up a little rig and having a go (at bitcoin mining that is). You can pick up those HD5830's new for £80 nowa days. I don't wana hear any mer mer they are pun tang compared to the 5870 because that's not the point you can pick up 4 of them for £300 and that's what your paying for 1 5870 :D If so how much you making per month ?

@azboy you don't need to edit the source ncpu can be set in pyrits configuration file located at /root/.pyrit/config. Also this won't make any difference what so ever unless your getting a bottle neck between the CPU and GPU. The option is there to set the amount of cores you want working on the stuff your GPU can't do. I'm sure I read somewhere you can set this to a minus figure to allow pyrit to crunch on a set number of cores to ? But I can't remember if a negative int was used or it was set by the declaration type ? Also I would say unless you have a pretty bad ass CPU this would hinder rather than help. But ice never tried this so have a go and post your findings here ;)

Also the cal++ version mismatch can be hushed by editing setup.py and changing the vn to 0.4.1 :D the one thing that does need to be fixed is the storage buffer error when trying to run a pyrit server. It looks like they started to improve it and forgot half way through hehehe

PS. I don't know what kernel BT4 is rocking these days but if its anything above 2.6.38 and you want to install the latest 11.3 catalyst you need to patch up the kernel modules.

Here's a patch I quickly typed up to address these issues .

Code:

---

--- common/lib/modules/fglrx/build_mod/firegl_public.c
+++ common/lib/modules/fglrx/build_mod/firegl_public.c
@@ -114,7 +114,7 @@
 #include <linux/pci.h>
 #include <linux/wait.h>
 #include <linux/miscdevice.h>
-#include <linux/smp_lock.h>
+#include <linux/sched.h>
 // newer SuSE kernels need this
 #include <linux/highmem.h>
 
@@ -848,8 +848,8 @@
      * happen much less frequent then without this workaround.
      */
    if (state == PM_EVENT_SUSPEND)
-        acquire_console_sem();
-
+        console_lock();
+   
    if (firegl_cail_powerdown(privdev, state))
        ret = -EIO;
 
@@ -870,7 +870,7 @@
    }
 
    if (state == PM_EVENT_SUSPEND)
-        release_console_sem();
+        console_unlock();
 
    KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, ret, NULL); 
   
@@ -894,7 +894,7 @@
    if (PMSG_EVENT(pdev->dev.power.power_state) == 0) return 0;
 
    if (PMSG_EVENT(pdev->dev.power.power_state) == PM_EVENT_SUSPEND)
-        acquire_console_sem();
+        console_lock();
 
 #ifdef FIREGL_USWC_SUPPORT
    // Restore the PAT after resuming from S3 or S4.
@@ -919,7 +919,7 @@
    firegl_cail_powerup(privdev);
 
    if (PMSG_EVENT(pdev->dev.power.power_state) == PM_EVENT_SUSPEND)
-        release_console_sem();
+        console_unlock();
 
    PMSG_EVENT(pdev->dev.power.power_state) = 0;
    KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, 0, NULL); 
@@ -1894,13 +1894,13 @@
 /** \brief Grab global kernel lock */
 void ATI_API_CALL KCL_GlobalKernelLock(void)
 {
-    lock_kernel();
+    /* lock_kernel(); removed */
 }
 
 /** \brief Release global kernel lock */
 void ATI_API_CALL KCL_GlobalKernelUnlock(void)
 {
-    unlock_kernel();
+  /* unlock_kernel(); removed */
 }
 
 /*****************************************************************************/

---

There are a couple of other things like ATI have renamed there sdk to ATI APP and restructured the libraries. Calpp hasn't been updated yet to reflect these changes so you might have to hack the Makefile to compile. I did type out a little guide but got a 404 when posting so lost it :D

@drgr33n awesome post. I've always seen vague explanations for the version mismatch but never a fix/workaround. That was very simple and worked perfectly, Thank you!

how i can enabled crossfire

he is not working
-----------------------------
root@bt:~# aticonfig --lscs
Candidate Combination:
Master: 0:0:0
Slave: 0:0:0
CrossFire is disabled on current device
CrossFire Diagnostics:
CrossFire can work with P2P mapping through GART
---------------------------------------------------------
root@bt:~# aticonfig --lsch
No CrossFire chains defined
--------------------------------------------------------
root@bt:~# aticonfig --cfa
Error: --adapter must also be specified when using --add-crossfire-chain
---------------------------------------------------------
root@bt:~# aticonfig --lsa
* 0. 02:00.0 AMD Radeon HD 6500M/5600/5700 Series

* - Default adapter
---------------------------------------------------------
root@bt:~# aticonfig --lscc

Master adapter: 0. 02:00.0 AMD Radeon HD 6500M/5600/5700 Series
Candidates: none
---------------------------------------------------------
root@bt:~# sudo aticonfig --lsa
* 0. 02:00.0 AMD Radeon HD 6500M/5600/5700 Series

* - Default adapter
-----------------------------------------------------------
root@bt:~# pyrit list_cores
/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py:63: UserWarning: WARNING: Version mismatch between <module 'cpyrit._cpyrit_cpu' from '/usr/lib/python2.5/site-packages/cpyrit/_cpyrit_cpu.so'> ('0.4.0') and <module 'cpyrit._cpyrit_calpp' from '/usr/lib/python2.5/site-packages/cpyrit/_cpyrit_calpp.so'> ('0.4.0-dev (svn r304)')

"('%s')\n" % (_cpyrit_cpu, _cpyrit_cpu.VERSION, mod, ver))
Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

The following cores seem available...
#1: 'CAL++ Device #1 'AMD REDWOOD''
#2: 'CPU-Core (SSE2)'
#3: 'CPU-Core (SSE2)'
#4: 'CPU-Core (SSE2)'


Why is there a single device with the knowledge that there must be two

What is the solution to that

thx 4 help