btchris, please send me a personal message. Since your are using the 'compiled' version (and nobody reported such problem recently with it) I want to know what is your GPU and how do you start poclbm (what parameters you use).
Topic: python OpenCL bitcoin miner - page 45. (Read 1239149 times)
Thanks David. I forgot to remove that one and now I am unable to remove your quote of it
btchris, please send me a personal message. Since your are using the 'compiled' version (and nobody reported such problem recently with it) I want to know what is your GPU and how do you start poclbm (what parameters you use).
btchris, please send me a personal message. Since your are using the 'compiled' version (and nobody reported such problem recently with it) I want to know what is your GPU and how do you start poclbm (what parameters you use).
I've run into this using the latest (20101126) miner executable under windows. I've also seen it once before using an earlier version, I believe 20101102. The miner seems to run fine for a while, and then this error comes up, and the miner exits. Any thoughts? Anything about my setup I can provide to help?
P.S. m0mchil, I can't find a donation address for you... if you had one in your sig, it would be much easier to bribe you for support
sys:1: DeprecationWarning: struct integer overflow masking is deprecated
Traceback (most recent call last):
File "poclbm.py", line 140, in
File "pyopencl\__init__.pyc", line 205, in kernel_call
OverflowError: long int too large to convert
P.S. m0mchil, I can't find a donation address for you... if you had one in your sig, it would be much easier to bribe you for support
Just took the time to write up a long post on how to get this working in windows (complete step by step guide)
http://www.newslobster.com/random/how-to-get-started-using-your-gpu-to-mine-for-bitcoins-on-windows
Feel free to add it to the first post or tell your friends or spam this link all over the internet
http://www.newslobster.com/random/how-to-get-started-using-your-gpu-to-mine-for-bitcoins-on-windows
Feel free to add it to the first post or tell your friends or spam this link all over the internet
You probably get the same result if you remove the GPU kernel call completely
I still remember when I was tweaking m0mchil's miner in the hope I could make it somewhat faster on NVidia, once I had that magnificent amount of hashes too I thought w000t. Then I saw the compile error at the top
Compilation fails with vectors...
I still remember when I was tweaking m0mchil's miner in the hope I could make it somewhat faster on NVidia, once I had that magnificent amount of hashes too I thought w000t. Then I saw the compile error at the top
Compilation fails with vectors...
LobsterMan what the hell kind of graphics card are you running to get those numbers? 
I run 2 GTX275's, but I think that for some reason, when I specify -v it displays the cumulative hashes as the rate/sec, which is obviously incorrect. It crashes within 10-15 seconds anyway, so I guess nvidia cards just don't play nice with vectors...
I managed to get mine to "work" too. I get less hashes out of my graphics card (1400k/s) than from the CPUs (1800k/s). I am also running X, so maybe that matters (but I doubt that).
Why are the AMD GPUs so much faster for this kind of work? From the numbers I have seen in this thread they are truly crushing nvidia. Are the nvidia cards better at doing floating point computations (or at least _something_) or are they basically just obsolete?
Why are the AMD GPUs so much faster for this kind of work? From the numbers I have seen in this thread they are truly crushing nvidia. Are the nvidia cards better at doing floating point computations (or at least _something_) or are they basically just obsolete?
LobsterMan what the hell kind of graphics card are you running to get those numbers?
Thanks for the updates, m0mchil, and for integrating getwork into the mainline client, Satoshi! I've also updated my minerd.py to incorporate m0mchil's latest changes, and I've tested it in the testnet and verified that it finds blocks appropriately with the svn r191.
New version works very nicely, except if I try to add -v to my launch options on an nvidia gtx275
It crashes shortly thereafter
It crashes shortly thereafter
Code:
Faulting application name: poclbm.exe, version: 0.0.0.0, time stamp: 0x4918019b
Faulting module name: nvcuda.dll, version: 8.17.12.6099, time stamp: 0x4cb9d8c5
Exception code: 0xc0000005
Fault offset: 0x000285d5
Faulting process id: 0x480
Faulting application start time: 0x01cb8d411389c8bb
Faulting application path: C:\Users\[user]\Desktop\poclbm_py2exe_20101126\poclbm.exe
Faulting module path: C:\Windows\system32\nvcuda.dll
Report Id: 5a9d2442-f934-11df-8ff5-0026185aa540
Fixed.
poclbm_py2exe_20101125 doesnt work for me
(Bitcoin 0.3.17 official @ win7 64)
sharound(..........) errors
(Bitcoin 0.3.17 official @ win7 64)
sharound(..........) errors
Same here. Got an ATI card and latest (10.11) drivers. Also Win7 64.
Code:
error: function
"amd_bitalign" declared implicitly
sharound(D,E,F,G,H,A,B,C,R(37),0x766A0ABB);
^
works fine for me with 0.3.17 on both, winXP&7 64.
poclbm_py2exe_20101125 doesnt work for me
(Bitcoin 0.3.17 official @ win7 64)
sharound(..........) errors
(Bitcoin 0.3.17 official @ win7 64)
sharound(..........) errors
Updated the miner to work with official bitcoin SVN 189.
Thank you satoshi, it is a small fix, I hope it will be ready tomorrow.
A revised version of getwork is now in the official client, but the miners need to be updated a little to use it.
Hi m0mchil, firstly thank you for your work. Is there any way to include getwork patch into official client? I'm using bitcoin on old centos server and compiling is pain here!
updated to SVN 186
Thanks m0mchil for keeping up on the updates!GPU miners, please upgrade as soon as possible to shut down the free transaction abuse! This version has the new priority-based limit on free transaction spam.
Just updated to SVN 181 and fixed getwork patch to wait 60 seconds between rebuilding the block with new transactions. This is actually the behavior of the original client, was forgotten in the patch by mistake. Fixes heavy CPU usage on every getwork request (this became obvious with recent heavy transaction spam). Please upgrade.
Before SVN 184, compiling transactions into a block used an n^2 algorithm. The new efficient single-pass algorithm is orders of magnitude quicker. (O(n) vs O(n^2)/2 algorithm, n=200 maybe 10 to 100 times quicker)
updated to SVN 186
Jump to: