In that case, wouldn't you be better just running bitcoin -gen ? See http://forum.bitcoin.org/index.php?topic=2356.0
Sorry, but the integrated CPU miner in the older builds is much slower than say CGMiner's 4way algorithm or Ufasoft's SSE2 optimization. 
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 838. (Read 5805998 times)
July 17, 2011, 04:12:54 AM
July 17, 2011, 03:58:08 AM
The windows build has gpu mining built into it. You cannot do plain cpu mining on the generic windows build unless you build it without GPU mining support.
I didn't realise that. The previous version I had - the on that had "Generate Coins" in a menu used the CPU to mine.
If the current Windows version really does use the GPU to mine, then why should I be using CGMiner? (Can't test at the moment due to PSU issue.) http://www.weusecoins.com/mining-guide.php seems to imply that GPU mining is not native to the Windows Bitcoin Application.
If the current Windows version really does use the GPU to mine, then why should I be using CGMiner? (Can't test at the moment due to PSU issue.) http://www.weusecoins.com/mining-guide.php seems to imply that GPU mining is not native to the Windows Bitcoin Application.
The Windows build of cgminer has gpu mining built into it.
Mining is being phased out from the official Bitcoin client.
July 17, 2011, 03:53:00 AM
EDIT: Me == Comprehension Fail 
Thanks for corrections below.
I didn't realise that. The previous version I had - the on that had "Generate Coins" in a menu used the CPU to mine.
If the current Windows version really does use the GPU to mine, then why should I be using CGMiner? (Can't test at the moment due to PSU issue.) http://www.weusecoins.com/mining-guide.php seems to imply that GPU mining is not native to the Windows Bitcoin Application. Likewise, https://en.bitcoin.it/wiki/FAQ#Why_was_the_.22Generate_coin.22_option_of_the_client_software_removed.3F makes no mention of this capability.
Thanks for corrections below.If the current Windows version really does use the GPU to mine, then why should I be using CGMiner? (Can't test at the moment due to PSU issue.) http://www.weusecoins.com/mining-guide.php seems to imply that GPU mining is not native to the Windows Bitcoin Application. Likewise, https://en.bitcoin.it/wiki/FAQ#Why_was_the_.22Generate_coin.22_option_of_the_client_software_removed.3F makes no mention of this capability.
July 17, 2011, 02:20:31 AM
The windows build has gpu mining built into it. You cannot do plain cpu mining on the generic windows build unless you build it without GPU mining support.
July 17, 2011, 02:18:01 AM
In that case, wouldn't you be better just running bitcoin -gen ? See http://forum.bitcoin.org/index.php?topic=2356.0
o July 17, 2011, 01:36:10 AM
In that case, wouldn't you be better just running bitcoin -gen ? See http://forum.bitcoin.org/index.php?topic=2356.0
July 17, 2011, 01:10:13 AM
no gpu, can not use
show can not find opencl.dll error
You need to install newer drivers for AMD card.show can not find opencl.dll error
July 17, 2011, 12:23:08 AM
Hi
at least your honest...I really like your miner..hence the pushing to get it fixed
I don't understand it either..but the records that deepbit keep show since using cgminer, stales have increased quite a bit.
Perhaps in how cgminer queues the shares??
anyways, I did not mean to offend and apologize if I did. Please keep up the good work and I realize you are not getting paid at this point.
Hi
at least your honest...I really like your miner..hence the pushing to get it fixed
I don't understand it either..but the records that deepbit keep show since using cgminer, stales have increased quite a bit. Perhaps in how cgminer queues the shares??
anyways, I did not mean to offend and apologize if I did. Please keep up the good work and I realize you are not getting paid at this point.
Hi
July 16, 2011, 11:20:45 PM
Hi
my stales/rejects on deepbit were very stable over n period. That same n period interval using cgminer showed large jump in stales/rejects. Put your ego aside and fix it for the peeps.
Hi
Ego? That's easy to say. I don't see where they're coming from and why they're lower with other miners so I don't know what to fix. my stales/rejects on deepbit were very stable over n period. That same n period interval using cgminer showed large jump in stales/rejects. Put your ego aside and fix it for the peeps.
Hi
July 16, 2011, 11:09:23 PM
Hi
my stales/rejects on deepbit were very stable over n period. That same n period interval using cgminer showed large jump in stales/rejects. Put your ego aside and fix it for the peeps.
Hi
my stales/rejects on deepbit were very stable over n period. That same n period interval using cgminer showed large jump in stales/rejects. Put your ego aside and fix it for the peeps.
Hi
July 16, 2011, 10:31:30 PM
Hi
You are in denial about the stales/rejects...this cgminer produces more stales than guiminer on same pool. Fix it and quit making excuses.
Hi
Fine, it's broken. Go use guiminer thanks. You are in denial about the stales/rejects...this cgminer produces more stales than guiminer on same pool. Fix it and quit making excuses.
Hi
July 16, 2011, 10:11:55 PM
Hi
You are in denial about the stales/rejects...this cgminer produces more stales than guiminer on same pool. Fix it and quit making excuses.
Hi
You are in denial about the stales/rejects...this cgminer produces more stales than guiminer on same pool. Fix it and quit making excuses.
Hi
July 16, 2011, 07:26:54 PM
Just tried version 1.2.7 on a rather up-to-date Mac, and OpenCL still isn't detected. For now I'm assuming the following bit in the configure file is to blame:
The Mac I have here is a 64bit machine and identifies itself as "x86_64-apple-darwin10.8.0", which means that the "*-*-darwin*" case is never reached.
Changing the case statement to the following enables OpenCL:
Unfortunately, I'm still getting the following error when makeing:
Code:
case $target in
*-*-mingw*)
have_x86_64=false
have_win32=true
PTHREAD_FLAGS=""
;;
x86_64-*)
have_x86_64=true
;;
*-*-darwin*)
have_x86_64=false
OPENCL_FLAGS="-framework OpenCL"
;;
*)
have_x86_64=false
;;
esac
Changing the case statement to the following enables OpenCL:
Code:
case $target in
*-*-mingw*)
have_x86_64=false
have_win32=true
PTHREAD_FLAGS=""
;;
x86_64-*-darwin*)
have_x86_64=true
OPENCL_FLAGS="-framework OpenCL"
;;
x86_64-*)
have_x86_64=true
;;
*-*-darwin*)
have_x86_64=false
OPENCL_FLAGS="-framework OpenCL"
;;
*)
have_x86_64=false
;;
esac
Unfortunately, I'm still getting the following error when makeing:
Code:
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -I./lib -I./lib -O3 -Wall -MT cgminer-main.o -MD -MP -MF .deps/cgminer-main.Tpo -c -o cgminer-main.o `test -f 'main.c' || echo './'`main.c
In file included from main.c:34:
compat.h:5: error: conflicting types for 'suseconds_t'
/usr/include/sys/types.h:250: error: previous declaration of 'suseconds_t' was here
make[2]: *** [cgminer-main.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
July 16, 2011, 06:14:19 PM
have you installed teh opencl-headers?
Are you trolling? He already said he installed them. July 16, 2011, 06:04:01 PM
have you installed teh opencl-headers?
July 16, 2011, 05:59:00 PM
There are instructions for the most convenient way of installing libs and includes in the README.
I already had them installed in /opt as the tutorial here does http://forum.bitcoin.org/?topic=7514.0 and I added the two symlinks and ran ldconfig according to your readme. Unfortunately I still get the opencl not detected error during the config.
July 16, 2011, 05:18:37 PM
There are instructions for the most convenient way of installing libs and includes in the README.
July 16, 2011, 05:15:45 PM
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.for ubuntu you can use just the debian ones (as there is no package in the repo...)
for other distros idk
after I installed the headers it worked for me maybe it does for you
July 16, 2011, 05:11:52 PM
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.for ubuntu you can use just the debian ones (as there is no package in the repo...)
for other distros idk
after I installed the headers it worked for me maybe it does for you
July 16, 2011, 05:09:18 PM
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. for ubuntu you can use just the debian ones (as there is no package in the repo...)
for other distros idk
Jump to: