python OpenCL bitcoin miner - page 42.

jiffy

newbie

Activity: 27

Merit: 0

Quote from: davout on December 23, 2010, 04:32:07 AM

you have to wait 120 blocks before the coins mature,
otherwise you might spend coins that were generated on a chain fork

Thanks a lot for quick reply, davout!

Is it possible to see this on blockexplorer.com? What do I have to look for?

davout

legendary

Activity: 1372

Merit: 1008

1davout

you have to wait 120 blocks before the coins mature,
otherwise you might spend coins that were generated on a chain fork

jiffy

newbie

Activity: 27

Merit: 0

Hi,

poclbm finally told me that a block was accepted (after 3 days with 0,23Ghash/s).

bitcoind getinfo shows no balance of +50 until now, though.

I read somewhere that this might take very long because the new block is checked very intensively. Couldn't find the text again, though.

So can you tell me that I can calm down or went something wrong and the 3 days of work are gone for somebody else?

GeorgeH

member

Activity: 83

Merit: 10

Quote from: distant on December 20, 2010, 09:08:36 PM

Does anyone know what the optimal settings are for a GTX 580?

Thanks,
DiSTANT

Sell it and buy an ATI card.

brocktice

sr. member

Activity: 292

Merit: 250

Apparently I inspired this image.

Quote from: fisuk on December 21, 2010, 02:16:58 AM

Quote from: gohan on December 20, 2010, 07:56:32 PM

Finally got my hands on a GTX 275. Reporting stats:

CPU: Core2 Extreme QX6700, 2.67 GHz
OS: Gentoo Linux 2.6.34
Client: Classic 0.3.19 (local build)
khash/sec: ~5000

GPU: Nvidia GeForce GTX 275
Miner: m0mchil's OpenCL (2010-12-20)
Options: -r 3 -f 10 -w 256
khash/sec: ~49500

I have an old motherboard (PCIe 1.0a, etc.) which has a lot of strain on it, so your results with the same CPU or GPU could be better. It seems I should've gone for an ATI radeon though.

Yeah, I guess the problem lies with Nvidia's OpenCL drivers which are less than optimal. If there was a CUDA miner available, Nvidia users would probably get more comparable results.. So, who's up to the task? Wink

Nvidia hardware sucks for mining at the hardware level. CUDA won't help.

fisuk

newbie

Activity: 1

Merit: 0

Quote from: gohan on December 20, 2010, 07:56:32 PM

Finally got my hands on a GTX 275. Reporting stats:

CPU: Core2 Extreme QX6700, 2.67 GHz
OS: Gentoo Linux 2.6.34
Client: Classic 0.3.19 (local build)
khash/sec: ~5000

GPU: Nvidia GeForce GTX 275
Miner: m0mchil's OpenCL (2010-12-20)
Options: -r 3 -f 10 -w 256
khash/sec: ~49500

I have an old motherboard (PCIe 1.0a, etc.) which has a lot of strain on it, so your results with the same CPU or GPU could be better. It seems I should've gone for an ATI radeon though.

Yeah, I guess the problem lies with Nvidia's OpenCL drivers which are less than optimal. If there was a CUDA miner available, Nvidia users would probably get more comparable results.. So, who's up to the task? Wink

distant

newbie

Activity: 7

Merit: 0

Does anyone know what the optimal settings are for a GTX 580?

Thanks,
DiSTANT

gohan

jr. member

Activity: 52

Merit: 1

Finally got my hands on a GTX 275. Reporting stats:

CPU: Core2 Extreme QX6700, 2.67 GHz
OS: Gentoo Linux 2.6.34
Client: Classic 0.3.19 (local build)
khash/sec: ~5000

GPU: Nvidia GeForce GTX 275
Miner: m0mchil's OpenCL (2010-12-20)
Options: -r 3 -f 10 -w 256
khash/sec: ~49500

I have an old motherboard (PCIe 1.0a, etc.) which has a lot of strain on it, so your results with the same CPU or GPU could be better. It seems I should've gone for an ATI radeon though.

dbc

newbie

Activity: 3

Merit: 0

Looking at the opencl kernel, can the belowOrEquals function not avoid the endian related comparison of seperate bytes, instead moving the switch into the python code when creating targetH and targetG. Then less branches in kernel and perhaps better stream usage?

ColdHardMetal

hero member

Activity: 700

Merit: 500

Hello,

I downloaded the miner and followed the instructions from the OP. I feel as though I have it set up correctly. When I try to run the miner a new CMD window flashes on my screen too rapidly to read anything, or even see if it says anything. I don't get any errors in the CMD window I'm using to launch the miner but I really don't feel like it's working. I'm also not sure how I'm able to tell if it is working.

Any assistance would be appreciated.

Thanks.

BitLex

hero member

Activity: 532

Merit: 505

Quote from: slush on December 19, 2010, 10:56:37 AM

Oh! Good to know!

i guess it is, should have mentioned that earlier.

i tried -testnet, cuz i didnt want to wait a day or 2 to let it happen and it's the exact same invalid-floods as soon as the first hash is found (the first one even makes it to the wallet sometimes).

slush

legendary

Activity: 1386

Merit: 1097

Quote from: BitLex on December 19, 2010, 10:37:50 AM

its not only the pool, its the same on local getwork-servers, aka mainline-clients.

Oh! Good to know! I didn't realized that. So it should not be related to 'max_jobs' solution in pool.

BitLex

hero member

Activity: 532

Merit: 505

its not only the pool, its the same on local getwork-servers, aka mainline-clients.

davout

legendary

Activity: 1372

Merit: 1008

1davout

I was getting the very same messages even before trying pooled mining

slush

legendary

Activity: 1386

Merit: 1097

Quote from: davout on December 19, 2010, 10:18:59 AM

I'm getting these too, didn't get them at all before git pulling latest miner version...

Your limit is already over 20 parallel jobs (increased before days). I hope m0mchil's miner is not so hungry

.

slush

legendary

Activity: 1386

Merit: 1097

Are you still using separate workers for each chip/gpu?

To m0mchil - how many getworks() do you prefetch now? I probably have to tune "max_jobs" for those cards.

I see _this_ problem is on my side, because I register every getwork for later checks. Due to optimizations, I have 10 jobs per worker, which worked very well for all miners and 5970. But when m0mchil made some changes, maybe he is prefetching more jobs and I throw away oldest one; it leads to 'stale' errors.

I will increase max_jobs to 20 for your card. Please report if it goes better.

Quote from: BitLex on December 19, 2010, 10:01:00 AM

this only happens on device=2, no matter if device=1 is used or not, no matter what clock-speed, even below stock-settings device=2 floods its "invalid or stale"-msg

running device=2 (or both devices) on poclbm_py2exe_20101126 works perfect, both GPUs get <300M, find hashes, which are added to different "pool.Worker-shares" as expected, no troubles at all.

it seems something happened in between 20101126 - 20101214, which effects HD5970s, or multi-gpu-cards,
had no problems before running 2 single-gpu cards.

think i'll keep 20101126 running for now, or am i missing some new required features here?
don't need to know if any single hash has been accepted, as long as >95% are, but i need to run both GPUs, not just one. Wink

davout

legendary

Activity: 1372

Merit: 1008

1davout

I'm getting these too, didn't get them at all before git pulling latest miner version...

BitLex

hero member

Activity: 532

Merit: 505

Quote from: davout on December 16, 2010, 06:03:38 PM

Hey momchil, i'm getting loads of these while running your latest git code, weird thing is that I'm getting these messages on only one of the two cores of my 5970, I don't really know what it means, should I downclock it a bit ?

Code:

16/12/2010 23:57, 1a8eed81, invalid or stale
16/12/2010 23:57, 68c13670, invalid or stale
16/12/2010 23:59, 910435fc, invalid or stale
290592 khash/s

just got a HD5970 and of course had to try all kinds of settings, drivers and sdk versions to see what works best for me and i came across some similar problems.

running poclbm_py2exe_20101218, or poclbm_py2exe_20101214 pre-compiled binaries (on XP64),
device=1 works fine as usual (<300M),
device=2 though, as soon as it finds the first winning hash, gets this

Code:

19/12/2010 14:56, 0cfc0e17, accepted
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
19/12/2010 14:56, fbe37df7, invalid or stale
...
...

this only happens on device=2, no matter if device=1 is used or not, no matter what clock-speed, even below stock-settings device=2 floods its "invalid or stale"-msg

running device=2 (or both devices) on poclbm_py2exe_20101126 works perfect, both GPUs get <300M, find hashes, which are added to different "pool.Worker-shares" as expected, no troubles at all.

it seems something happened in between 20101126 - 20101214, which effects HD5970s, or multi-gpu-cards,
had no problems before running 2 single-gpu cards.

think i'll keep 20101126 running for now, or am i missing some new required features here?
don't need to know if any single hash has been accepted, as long as >95% are, but i need to run both GPUs, not just one. Wink

Elanthius

newbie

Activity: 45

Merit: 0

Quote from: m0mchil on December 18, 2010, 08:54:00 AM

Elanthius, in previous version I forgot to remove OpenCL.dll from the py2exe distribution. It is not there in current version and you should check that you have Stream SDK 2.2 installed and proper version of OpenCL.dll loadable by miner. Be sure there aren't multiple versions - for example if an nvidia one from previous drivers load first it could give you this error.

Hmm, I have an nvidia card that is OpenCL capable. I tried copying over the OpenCL.dll from system32 but that still crashes. In the end I just copied the dll out of the previous version and that seems fine. I'm getting 20Mh/s on a GeForce 8800 so its definitely using OpenCL appropriately.

m0mchil

full member

Activity: 171

Merit: 127

Elanthius, in previous version I forgot to remove OpenCL.dll from the py2exe distribution. It is not there in current version and you should check that you have Stream SDK 2.2 installed and proper version of OpenCL.dll loadable by miner. Be sure there aren't multiple versions - for example if an nvidia one from previous drivers load first it could give you this error.

Topic: python OpenCL bitcoin miner - page 42. (Read 1239060 times)