Topic: Ubuntu Natty Narwhal 11.04 Mining Guide / HOWTO - page 23. (Read 281459 times)
Fair enough... made the change and fixed the _32
What's the case for putting your stream path in local.conf as opposed to the .bashrc file?
It will always be available. If it's in .bashrc you have to set it explicitly if you're for instance running the script from cron or a boot script.Also, it turns out the lib path in the 32 bit package is just lib/x86, not lib/x86_32.
Somebody?
I got can't locate libboost from
#screen -S update sudo apt-get install fglrx vim openssh-server g++ libboost-all-dev subversion git-core python-numpy
Then I had to go to System Settings -> Update Manager -> Settings... -> Ubuntu Software -> [Check] Community-maintained Open Source software (Universe)
After which I had this
cryptsetup: WARNING: failed to detect canonical device of aufs
cryptsetup: WARNING: could not determine root device from /etc/fstab
from
screen -S update sudo apt-get install fglrx vim openssh-server g++ libboost-all-dev subversion git-core python-numpy
I continued to follow the rest of the steps with no other notable warnings or errors until.
make -j3
this is the output
src/wrapper/wrap_cl.hpp:20:19: fatal error: CL/cl.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
make: *** [all] Error 1
Someone wanna help?
#screen -S update sudo apt-get install fglrx vim openssh-server g++ libboost-all-dev subversion git-core python-numpy
Then I had to go to System Settings -> Update Manager -> Settings... -> Ubuntu Software -> [Check] Community-maintained Open Source software (Universe)
After which I had this
cryptsetup: WARNING: failed to detect canonical device of aufs
cryptsetup: WARNING: could not determine root device from /etc/fstab
from
screen -S update sudo apt-get install fglrx vim openssh-server g++ libboost-all-dev subversion git-core python-numpy
I continued to follow the rest of the steps with no other notable warnings or errors until.
make -j3
this is the output
src/wrapper/wrap_cl.hpp:20:19: fatal error: CL/cl.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
make: *** [all] Error 1
Someone wanna help?
Ok, I've made some changes and fixed the problems noted based on the suggestions. What's the case for putting your stream path in local.conf as opposed to the .bashrc file?
As far as v2.4 goes... if someone wants to send me a 6xxx series card to test with, I will be happy to do it. I don't have one currently, so I haven't gone down that road. If anyone has a line on 6990's, please let me know, I'm looking to purchase two.
As far as v2.4 goes... if someone wants to send me a 6xxx series card to test with, I will be happy to do it. I don't have one currently, so I haven't gone down that road. If anyone has a line on 6990's, please let me know, I'm looking to purchase two.
Great, I'll test the 32-Bit now since I my friend just passed 1 over to me, I'll let you know if there are other stuff. Anyway the erm. set to 'Universe' thing I read is about installing libboost, I'm not sure if it's relevant but after enabling that setting installing libboost went through.
I did, and it shows 725 and current clock. Something is not letting me oc it...will flashing it fix it?
You won't see your card set to peak speeds until you actually have a load put on the GPU. You need to fire up the miner and it should bump the clock speed up to the peak.
He doesn't actually know them tho...you know what I mean? He's not actually thattt tech savvy...I doubt he would know how to oc either.
Hey does anyone know how to solve this:
I got a 5850, by afox, cuz my dad works for that company.
However, when I try to overclock it using the aticonfig --od-setclock=800, 1100 --adapter=3 (Which is max)
Nothing happens. I use aticonfig --odgc --adapter=all to show the clock speeds and it says current clocks : 725, 1000. Current peak : 800, 1100.
So...the peak changed but the current clock isn't changing. I used AMDOverdriveCtrl, and the "high" profile is indeed 800mhz, but it's not going there. Clicking "set" doesn't do anything either...
Help!?! Do I need to flash the bios?
I got a 5850, by afox, cuz my dad works for that company.
However, when I try to overclock it using the aticonfig --od-setclock=800, 1100 --adapter=3 (Which is max)
Nothing happens. I use aticonfig --odgc --adapter=all to show the clock speeds and it says current clocks : 725, 1000. Current peak : 800, 1100.
So...the peak changed but the current clock isn't changing. I used AMDOverdriveCtrl, and the "high" profile is indeed 800mhz, but it's not going there. Clicking "set" doesn't do anything either...
Help!?! Do I need to flash the bios?
Ask your dad?
Cubedroot, I had this problem once,and I have no idea why. But I can say what fixed it. Use the environment variable:
export GPU_USE_SYNC_OBJECTS=1
Then fireup poclb.
regards,
MintyMark
export GPU_USE_SYNC_OBJECTS=1
Then fireup poclb.
regards,
MintyMark
Hey does anyone know how to solve this:
I got a 5850, by afox, cuz my dad works for that company.
However, when I try to overclock it using the aticonfig --od-setclock=800, 1100 --adapter=3 (Which is max)
Nothing happens. I use aticonfig --odgc --adapter=all to show the clock speeds and it says current clocks : 725, 1000. Current peak : 800, 1100.
So...the peak changed but the current clock isn't changing. I used AMDOverdriveCtrl, and the "high" profile is indeed 800mhz, but it's not going there. Clicking "set" doesn't do anything either...
Help!?! Do I need to flash the bios?
I got a 5850, by afox, cuz my dad works for that company.
However, when I try to overclock it using the aticonfig --od-setclock=800, 1100 --adapter=3 (Which is max)
Nothing happens. I use aticonfig --odgc --adapter=all to show the clock speeds and it says current clocks : 725, 1000. Current peak : 800, 1100.
So...the peak changed but the current clock isn't changing. I used AMDOverdriveCtrl, and the "high" profile is indeed 800mhz, but it's not going there. Clicking "set" doesn't do anything either...
Help!?! Do I need to flash the bios?
I have a 6870 for sale...idk if you want.
Ok, I've made some changes and fixed the problems noted based on the suggestions. What's the case for putting your stream path in local.conf as opposed to the .bashrc file?
As far as v2.4 goes... if someone wants to send me a 6xxx series card to test with, I will be happy to do it. I don't have one currently, so I haven't gone down that road. If anyone has a line on 6990's, please let me know, I'm looking to purchase two.
As far as v2.4 goes... if someone wants to send me a 6xxx series card to test with, I will be happy to do it. I don't have one currently, so I haven't gone down that road. If anyone has a line on 6990's, please let me know, I'm looking to purchase two.
Hi all-
So I'm about to dive into this. On the AMD website they say "Stream SDK" is now "APP SDK":
http://developer.amd.com/sdks/AMDAPPSDK/downloads/Pages/default.aspx
I have 69XX cards so I know I need 2.3 or 2.4 APP SDK.
They provide a link to the 2.4 install:
http://developer.amd.com/Downloads/AMD-APP-SDK-v2.4-lnx32.tgz
which I presume I would substitute for the 2.1 link provided in the instructions.
So when I look at the installation notes for APP SDK 2.4, it says a prerequisite is the latest Catalyst drivers, which I guess is this bit:
http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx
which provides a link to a .run file. Yet your instructions don't mention downloading this first, or at all, that I can see.
Are the installation notes from AMD just wrong that I need to install these catalyst drivers first?
Also, if I were to follow these instructions, and they worked, then would I have catalyst available, with it's GUI for adjusting clock speed and such?
Thanks.
So I'm about to dive into this. On the AMD website they say "Stream SDK" is now "APP SDK":
http://developer.amd.com/sdks/AMDAPPSDK/downloads/Pages/default.aspx
I have 69XX cards so I know I need 2.3 or 2.4 APP SDK.
They provide a link to the 2.4 install:
http://developer.amd.com/Downloads/AMD-APP-SDK-v2.4-lnx32.tgz
which I presume I would substitute for the 2.1 link provided in the instructions.
So when I look at the installation notes for APP SDK 2.4, it says a prerequisite is the latest Catalyst drivers, which I guess is this bit:
http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx
which provides a link to a .run file. Yet your instructions don't mention downloading this first, or at all, that I can see.
Are the installation notes from AMD just wrong that I need to install these catalyst drivers first?
Also, if I were to follow these instructions, and they worked, then would I have catalyst available, with it's GUI for adjusting clock speed and such?
Thanks.
32-bit 16. echo export LD_LIBRARY_PATH=/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_32/:$LD_LIBRARY_PATH >> .bashrc
this is correct? so does the 32-bit do,
No, that line should bethis is correct? so does the 32-bit do,
32-bit 16. echo export LD_LIBRARY_PATH=/opt/ati-stream-sdk-v2.1-lnx32/lib/x86_32/:$LD_LIBRARY_PATH >> .bashrc
32-bit 24. ./configure.py --cl-inc-dir=/opt/ati-stream-sdk-v2.1-lnx32/include/ --cl-lib-dir=/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_32
is wrong too, should be
32-bit 24. ./configure.py --cl-inc-dir=/opt/ati-stream-sdk-v2.1-lnx32/include/ --cl-lib-dir=/opt/ati-stream-sdk-v2.1-lnx32/lib/x86_32
is wrong too, should be
32-bit 24. ./configure.py --cl-inc-dir=/opt/ati-stream-sdk-v2.1-lnx32/include/ --cl-lib-dir=/opt/ati-stream-sdk-v2.1-lnx32/lib/x86_32
wait...
32-bit 16. echo export LD_LIBRARY_PATH=/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_32/:$LD_LIBRARY_PATH >> .bashrc
this is correct? so does the 32-bit do,
32-bit 11. sudo tar xvfz ati-stream-sdk-v2.1-lnx32.tgz -C /opt
or
64-bit 11. sudo tar xvfz ati-stream-sdk-v2.1-lnx64.tgz -C /opt
?
I've got no experience in Linux less so in scripting... zzz. I even had problem trying to install Win7 off my ext.HDD (doesn't boot Idk why)... But I'm trying.
Is there any simple site I can learn the basics to automating the drivers (& poclbm) install, after which I need to learn how to script poclbm to run for all my GPU and OC them -.- am I heading in the right direction with this? or are there easier ways to do it?
32-bit 16. echo export LD_LIBRARY_PATH=/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_32/:$LD_LIBRARY_PATH >> .bashrc
this is correct? so does the 32-bit do,
32-bit 11. sudo tar xvfz ati-stream-sdk-v2.1-lnx32.tgz -C /opt
or
64-bit 11. sudo tar xvfz ati-stream-sdk-v2.1-lnx64.tgz -C /opt
?I've got no experience in Linux less so in scripting... zzz. I even had problem trying to install Win7 off my ext.HDD (doesn't boot Idk why)... But I'm trying.
Is there any simple site I can learn the basics to automating the drivers (& poclbm) install, after which I need to learn how to script poclbm to run for all my GPU and OC them -.- am I heading in the right direction with this? or are there easier ways to do it?
11. & 13. are the similar. I'm not sure if it's a required step. Although in 13, 32-bit and 64-bit is doing the same thing.
No idea why 13 is there, it's already done in 11, and yes, the 32 bit version is wrong in 13.16. is really confusing is it right? I'm not sure. And I don't know where everything goes so yea... -.-|||
No, its supposed to be like that, although I prefer this version:sudo sh -c 'echo "/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_64/" >> /etc/ld.so.conf.d/local.conf'
sudo ldconfig
Also, the 32 and 64 bit versions could be grouped better to avoid having so many "do either this or that" lines, and some of them could be done in one line using wildcard for the 32/64 part. Regarding all the echo lines, it's possible that people aren't in the home dir when they start. In that case it will fail miserably. Use ~/.bashrc instead just in case.
I ran those scripts on a 10.10 32 bit install and I am having problems across multiple GPUs. I am running three Sapphire 5850's
When I run poclbm without any arguments it will list all of my GPUs as such:
0 Cypress
1 Cypress
2 Cypress
3 AMD Sempron(tm) 140 Process
So, i think great, its running! I then open a new terminal window and do the following:
It will fire up and run great, and give me decent hashrates since I have not overclocked them yet For example, I am getting about 250,000 Khash/s
So, I open up second terminal window to get a miner running on the second GPU. I run the following in it:
It connects and works like normal, but the hashrate is off... it starts off slow, about 20,000 khash/sec, but then it will get to about 125,000 khash/sec. Its also at this point that I notice the first miner I ran earlier is also dropping its hasrate to about the same. Eventually both terminals will get to a point where their hasrates are equal and total up to about 250,000 Khash/sec...which is about what I get on one card!
So, I am thinking that both miners are computing on the same GPU regardless of which device I specifiy in the command.
What am I doing wrong?
When I run poclbm without any arguments it will list all of my GPUs as such:
Quote
0 Cypress
1 Cypress
2 Cypress
3 AMD Sempron(tm) 140 Process
So, i think great, its running! I then open a new terminal window and do the following:
Quote
./poclbm.py -d 0 --host=btcguild.com --port=8332 --user=MINER_gpu0 --pass=RPCPASS -v -w 128
It will fire up and run great, and give me decent hashrates since I have not overclocked them yet For example, I am getting about 250,000 Khash/s
So, I open up second terminal window to get a miner running on the second GPU. I run the following in it:
Quote
./poclbm.py -d 1 --host=btcguild.com --port=8332 --user=MINER_gpu1 --pass=RPCPASS -v -w 128
It connects and works like normal, but the hashrate is off... it starts off slow, about 20,000 khash/sec, but then it will get to about 125,000 khash/sec. Its also at this point that I notice the first miner I ran earlier is also dropping its hasrate to about the same. Eventually both terminals will get to a point where their hasrates are equal and total up to about 250,000 Khash/sec...which is about what I get on one card!
So, I am thinking that both miners are computing on the same GPU regardless of which device I specifiy in the command.
What am I doing wrong?
Instead of having to be rewritten for 32 bit, it needs to be rewritten for SDK 2.4...
Or just a separate guide.
Or just a separate guide.
Jump to: