[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
howtos:software:boinc_gpu_ati_slackware [2014/02/23 08:17 (UTC)] – [This howto is used based on Slackware64 14.0 and boinc 7.2.33 x64, and ATI HD 4350 (RV710) videocard.] wisedraco | howtos:software:boinc_gpu_ati_slackware [2014/02/24 22:55 (UTC)] (current) – [This howto is used based on Slackware64 14.0 and boinc 7.2.33 x64, and ATI HD 4350 (RV710) videocard.] sycamorex | ||
---|---|---|---|
Line 6: | Line 6: | ||
- | Firstly - install a fresh slackware64 14.0 | + | Firstly - install a fresh slackware64 14.0. Then we download |
- | then we download latest BOINC client from | + | |
- | http:// | + | Put the file '' |
+ | <note important> | ||
- | Put the file ( boinc_7.2.33_x86_64-pc-linux-gnu.sh ) on home catalog under user, from who we plan start the boinc client/ | + | Then do: |
- | <note important> | + | |
- | then do | + | < |
- | '' | + | After that in our home directory there will be the " |
- | After that we get " | + | Download catalyst 13.1 drivers from AMD/ATI site (the latest version |
- | now is time to prepare videocard | + | |
- | download catalyst 13.1 drivers | + | < |
+ | Then we must also download SDK 2.9 from [[http:// | ||
- | '' | + | Now under root unzip catalyst 13.1 and type: |
+ | < | ||
- | then we must also downlo9ad SDK 2.9 for get OpenCL support for Videocard: | + | and install it. |
+ | After that untar AMD-APP-SDK-v2.8-lnx32.tgz, | ||
- | '' | + | Now you need to run a window manager from selected user ('' |
+ | < | ||
- | + | You should | |
- | now under root unzip catalyst 13.1, do | + | |
- | + | ||
- | '' | + | |
- | + | ||
- | and let it to install. | + | |
- | after that untar AMD-APP-SDK-v2.8-lnx32.tgz | + | |
- | + | ||
- | after all that, run window manager from selected user ( '' | + | |
- | and do ./boinc | + | |
- | + | ||
- | You must see something like: | + | |
Line 150: | Line 141: | ||
After that you have a working BOINC installation. | After that you have a working BOINC installation. | ||
- | To start participating in projects, go to setiathome.berlkeley.edu, | + | To start participating in projects, go to setiathome.berlkeley.edu, |
- | in second case ( via bam.boinc.com) you can attach your project | + | In the second case (via bam.boinc.com) you can attach your project |
- | in one window ( console) run ./boinc . | + | |
- | then open another console ( window) with the same user, and in BOINC directory do | + | |
- | ./boinccmd --join_acct_mgr http:// | + | * In one terminal window run ./boinc . |
+ | * Open another terminal window with the same user, and in the BOINC directory type: | ||
- | then in first console ( where you run ./boinc) you see messages like " | + | < |
- | If you want to edit boinc preferences, | + | * in first console (where you ran '' |
+ | |||
+ | If you want to edit boinc preferences, | ||
< | < | ||
Line 198: | Line 190: | ||
===== ATI GPU without X window manager ===== | ===== ATI GPU without X window manager ===== | ||
- | If you not want to use X Window manager ( say, on server), but want to use ATI GPU in boinc, you can go that way: | + | If you do not want to use X Window manager (say, on a server), but want to use ATI GPU in boinc, you can go that way: |
+ | |||
+ | In the home directory of the account you want to run '' | ||
- | in account, from who you want run boinc homedir, make a script called " | ||
< | < | ||
#!/bin/sh | #!/bin/sh | ||
/ | / | ||
- | |||
</ | </ | ||
Line 212: | Line 204: | ||
</ | </ | ||
- | then, in the same directory | + | Then in the same directory |
< | < | ||
Line 218: | Line 210: | ||
</ | </ | ||
- | make it executable too: | + | Make it executable too: |
< | < | ||
Line 224: | Line 216: | ||
</ | </ | ||
- | now you must run that script ( dummy_wm.boinc ) in that way, for it be stay running. | + | Now you must run that script ('' |
- | if you log in in your server via ssh, for example, and run that script, boinc running, but when you log out, it stopped. | + | If you log in in your server via ssh, for example, and run that script, boinc will be running, but when you log out, it will stop. |
- | i use that way, for task stay running after logout: | + | To keep the task running after you log out, start it as follows: |
< | < | ||
at -v -f / | at -v -f / | ||
</ | </ | ||
- | it start task after 1 minute from now. | + | It will start the task after 1 minute from now. |
- | you can check running status | + | You can check the running status |
- | / | + | < |
and | and | ||
- | / | + | < |
- | + | ||
- | you always also can get come info about tasks via commands | + | |
+ | You can always get some info about tasks with the following command: | ||
< | < | ||
Line 248: | Line 239: | ||
/ | / | ||
- | |||
</ | </ | ||
- | |||
- | |||
==== ATI VideoCard stats info ==== | ==== ATI VideoCard stats info ==== | ||
- | you can also get some info about your videocard | + | You can also get some info about your video card state via commands (must be executed under the root account): |
< | < | ||
Line 265: | Line 253: | ||
< | < | ||
| | ||
- | |||
</ | </ | ||
- | |||
- | |||