you need the opencl-headers (building needs headers and dev files not what you normaly use for running programs)
for ubuntu you can use just the debian ones (as there is no package in the repo...)
for other distros idk
Erm yeah, the app sdk IS the headers and those CFLAGS and LDFLAGS are exactly for specifying the paths to said headers and libraries. |
|
|
|
|
Ok, can you allow a higher askrate? I usually for a CPU input at least 10-11 minutes on a getwork.
|
|
|
|
|
Well, i'm not sure exactly where's the problem but try going in via a terminal into the app sdk and make; make install-ing it to the system directories and then just run CFLAGS="-O3 -Wall -march=native" ./configure to see if it helps.
|
|
|
|
0.18 uploaded
With OpenCL support.
Single miner process can work on multiple GPU devices
Any changes to the cpu mining code? |
|
|
|
|
Well i see you have downloaded the 64bit version of the stream SDK. Are you on a 64 bit linux?
|
|
|
|
You need to run aclocal before autogen.sh or ./configure. If you dont have it, install automake or autotool.
Thanks, I installed automake and got a bit further but now I get the error configure.ac:125: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation. You know, i've also gotten this error, but not on cgminer. Try doing ./autogen.sh m4_pattern_allow or ./configure m4_pattern_allow or even "m4_pattern_allow ./autogen.sh" and so on. |
|
|
|
|
You need to run aclocal before autogen.sh or ./configure. If you dont have it, install automake or autotool.
|
|
|
|
ufasoft, does your miner get new work per thread, or two threads work on the same getwork? The latter would be better for in future versions.
Now single getwork used. Its range distributed between working threads. So you split the nonces to try between threads and give them the same work? Cool. Is it possible we can increase the askrate above 60? |
|
|
|
no gpu, can not use
show can not find opencl.dll error
You need to install newer drivers for AMD card. |
|
|
|
|
And why did you even think that? Currently, no miner under Windows offers no cpu usage at all due to the unconfirmed bug in the drivers.
|
|
|
|
|
conman, a small reminder for the fixme in the fulltest function in util.c
|
|
|
|
|
ufasoft, does your miner get new work per thread, or two threads work on the same getwork? The latter would be better for in future versions.
|
|
|
|
Just to say, that's not gigahashes. It's called nonces really or whatever, but i am pretty much sure it's not GH/s. It's just numbers which the GPU can go over very quickly, where the CPU(my phenom 955) can do around 3 million hashes per second, or 3 million nonces per second. Each nonce gives a hash/second. You can start over the nonce range every second with new hashes. So your 3 MH/s only covers less than 0.1% of the nonce range before it can start over from the beginning. As far as i know, per each getwork you have to try 2^32 nonces, if you dont find any hashes that match the diff, you request new work, and the process repeats itself. |
|
|
|
|
Just to say, that's not gigahashes. It's called nonces really or whatever, but i am pretty much sure it's not GH/s. It's just numbers which the GPU can go over very quickly, where the CPU(my phenom 955) can do around 3 million hashes per second, or 3 million nonces per second.
|
|
|
|
Honestly luke, that looks like the exact ripoff of my suggestion for splitting a single work across multiple threads on a CPU miner with a given noncerange. So the 2^32 range is divided by the number of threads. No number of threads on a single cost-effective machine (CPU or GPU) will ever max out 4 GH/s. Putting this in the protocol (though it could be done in the miner additionally) allows the work to be split among multiple unrelated miners. Anyhow, I don't see your "suggestion" anywhere, much less before I wrote up mine. "Ripoff" doesn't apply to independent research. Not that i understand where these 4 gigahashes of yours come from, but this is my suggestion. http://forum.bitcoin.org/index.php?topic=21275.msg350512#msg350512 |
|
|
|
|
Honestly luke, that looks like the exact ripoff of my suggestion for splitting a single work across multiple threads on a CPU miner with a given noncerange. So the 2^32 range is divided by the number of threads.
|
|
|
|
|
Whats the difference between setting it via Task Manager?
|
|
|
|
|
Perhaps you did not read that i said CPU miner. For the CPU miner to scan ALL the 4 billion nonces, even 10 minutes are not enough
|
|
|
|
I noticed a bug in the CPU miner which was not in the previous versions. If i set the scantime to very high(above 60) eventually the cpu miner runs out of nonces and shit start to happen.
Is that a technical term? Which exactly? |
|
|
|
|
I noticed a bug in the CPU miner which was not in the previous versions. If i set the scantime to very high(above 60) eventually the cpu miner runs out of nonces and shit start to happen.
|
|
|
|
|
Show Posts
