OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 652.

jake262144

full member

Activity: 210

Merit: 100

Quote from: bulanula on February 14, 2012, 07:11:01 AM

So always use intensity 9 to avoid this bug then ?

Thanks !

Not quite. Always use a STATIC intensity, no matter whether it's set to 6, 8, or 14 as long as you don't use d.

DAT is using intensity 9 because he has some powerful cards. Remember that intensity is a fine-tuning parameter and higher does not necessarily mean better.
Cards pulling 230MHash/s are generally better suited with intensity 8.

bulanula

hero member

Activity: 518

Merit: 500

So always use intensity 9 to avoid this bug then ?

Thanks !

simonk83

hero member

Activity: 798

Merit: 1000

Now you mention it, I'm having the same issue with dynamic. I just wasn't sure what was causing it

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: leveer on February 14, 2012, 12:37:06 AM

Quote from: -ck on February 13, 2012, 11:17:11 PM

Hmm well dynamic could be the culprit then indeed. And that won't really have anything to do with the 2nd thread being disabled, but perhaps because the worksize is constantly changing, it might not be offsetting the right amount and repeating work. That will need fixing...

I was noticing higher rejects with 2.2.x also, and upon searching, found this same problem with dynamic intensity. Switched to a static intensity, and the problem went away.

I recommend everyone stop using dynamic till it's fixed then.

leveer

newbie

Activity: 42

Merit: 0

Quote from: -ck on February 13, 2012, 11:17:11 PM

Hmm well dynamic could be the culprit then indeed. And that won't really have anything to do with the 2nd thread being disabled, but perhaps because the worksize is constantly changing, it might not be offsetting the right amount and repeating work. That will need fixing...

I was noticing higher rejects with 2.2.x also, and upon searching, found this same problem with dynamic intensity. Switched to a static intensity, and the problem went away.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: -ck on February 13, 2012, 11:17:11 PM

Hmm well dynamic could be the culprit then indeed. And that won't really have anything to do with the 2nd thread being disabled, but perhaps because the worksize is constantly changing, it might not be offsetting the right amount and repeating work. That will need fixing...

Yeah I am going to get some sleep but it is pushing 180 shares now and 0 rejects (on static intensity 9 for both GPUs).

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Hmm well dynamic could be the culprit then indeed. And that won't really have anything to do with the 2nd thread being disabled, but perhaps because the worksize is constantly changing, it might not be offsetting the right amount and repeating work. That will need fixing...

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: -ck on February 13, 2012, 11:04:10 PM

Quote from: DeathAndTaxes on February 13, 2012, 10:52:17 PM

Kernel is "phatk120213.cl"

I didn't specify vectors or worksize but based bin file name I am guessing this is vector 2, work size 128
"phatk120213Cypressbitalignv2w128long4.bin"

Interesting, I can't reproduce it here, but can you try starting with -k poclbm just to see if it goes away?

Tried poclbm. Both kernels had the same high reject "duplicate work" and the rate is very high 5% to 10%. Interestingly I noticed I had left both GPUs dynamic and 2nd thread is disabled for dymamic GPUs. This is the first version I remember using which had this I thought it might be relevent. I switched them both to intensity 9 and the issue has gone away ... so far. It has gone 88 shares without a reject. I'll run 1000 or so shares and give an update and then reboot and try dynamic again.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: DeathAndTaxes on February 13, 2012, 10:52:17 PM

Kernel is "phatk120213.cl"

I didn't specify vectors or worksize but based bin file name I am guessing this is vector 2, work size 128
"phatk120213Cypressbitalignv2w128long4.bin"

Interesting, I can't reproduce it here, but can you try starting with -k poclbm just to see if it goes away?

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Kernel is "phatk120213.cl"

I didn't specify vectors or worksize but based bin file name I am guessing this is vector 2, work size 128
"phatk120213Cypressbitalignv2w128long4.bin"

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: -ck on February 13, 2012, 10:43:19 PM

Interesting. It is only recently that cgminer has been reporting the reject reason. This is the same GPU each time as well, which suggests more a bug in the (new) kernel code rather than from the pool. This may be related to vectors code. What kernel is in use on this and are vectors enabled? I'm guessing poclbm+2 vectors on the GPU in question.

Which one is default?

I have to check.

Quote

Further question: You're not using old kernels or kernel bins just renamed are you?

No this is actually a clean install of OS, drivers, SDK, cgminer.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: -ck on February 13, 2012, 10:35:04 PM

Interesting. It is only recently that cgminer has been reporting the reject reason. This is the same GPU each time as well, which suggests more a bug in the (new) kernel code rather than from the pool. This may be related to vectors code. What kernel is in use on this and are vectors enabled? I'm guessing poclbm+2 vectors on the GPU in question.

Further question: You're not using old kernels or kernel bins just renamed are you?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: DeathAndTaxes on February 13, 2012, 10:18:30 PM

Has anyone else been noticing rejects due to "duplicate work"? Never seen them before and now I get a whole bunch Huh

Code:

[2012-02-13 19:12:06] Accepted 00000000.f2ee24c9.e04e32cb GPU 0 thread 0
[2012-02-13 19:12:17] Rejected 00000000.f2ee24c9.e04e32cb GPU 0 thread 0 (Duplicate proof of work)

[2012-02-13 19:13:19] Accepted 00000000.1a280744.98022220 GPU 0 thread 0
[2012-02-13 19:13:31] Rejected 00000000.1a280744.98022220 GPU 0 thread 0 (Duplicate proof of work)

[2012-02-13 19:14:39] Accepted 00000000.f7ef4cdb.7e200dc7 GPU 0 thread 0
[2012-02-13 19:14:51] Rejected 00000000.f7ef4cdb.7e200dc7 GPU 0 thread 0 (Duplicate proof of work)

Just recently upgraded to cgminer 2.2.5 so maybe that has something to do with it Huh

It might be the pool but I am only seeing it on the rig running 2.2.5 (11.2 driver, 2.5 SDK)

Normally have about 0.2% reject rate on this one rig I am hitting >5% and 98 or 99 are duplicate work errors.

Interesting. It is only recently that cgminer has been reporting the reject reason. This is the same GPU each time as well, which suggests more a bug in the (new) kernel code rather than from the pool. This may be related to vectors code. What kernel is in use on this and are vectors enabled? I'm guessing poclbm+2 vectors on the GPU in question.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Has anyone else been noticing rejects due to "duplicate work"? Never seen them before and now I get a whole bunch Huh

Code:

[2012-02-13 19:11:24] Accepted 00000000.2619a155.ed384bea GPU 1 thread 2
[2012-02-13 19:11:38] Accepted 00000000.8838a80d.96c958d4 GPU 0 thread 0
[2012-02-13 19:11:47] Accepted 00000000.214556b0.ba092fd5 GPU 0 thread 0
[2012-02-13 19:12:00] Accepted 00000000.9975d582.daf96e80 GPU 1 thread 2
[2012-02-13 19:12:00] Accepted 00000000.d297def1.91edf24f GPU 1 thread 2
[2012-02-13 19:12:02] Accepted 00000000.573f7c77.06d0fc66 GPU 1 thread 2
[2012-02-13 19:12:06] Accepted 00000000.f2ee24c9.e04e32cb GPU 0 thread 0
[2012-02-13 19:12:17] Rejected 00000000.f2ee24c9.e04e32cb GPU 0 thread 0 (Duplicate proof of work)
[2012-02-13 19:12:30] Accepted 00000000.1bf59c07.3c7f586f GPU 1 thread 2
[2012-02-13 19:12:32] Accepted 00000000.e532e770.a05bf028 GPU 1 thread 2
[2012-02-13 19:12:38] Accepted 00000000.08a9e3d4.924dda98 GPU 1 thread 2
[2012-02-13 19:12:38] Accepted 00000000.394f1fd3.69766f8b GPU 1 thread 2
[2012-02-13 19:12:40] Accepted 00000000.37baeeb8.9ff952b9 GPU 0 thread 0
[2012-02-13 19:12:44] Accepted 00000000.4bd24021.be829d7f GPU 1 thread 2
[2012-02-13 19:12:45] Accepted 00000000.3d2a6b7b.1c084ace GPU 1 thread 2
[2012-02-13 19:12:51] Accepted 00000000.ae0ffa31.6be7d934 GPU 0 thread 0
[2012-02-13 19:12:58] Accepted 00000000.3a0ae6e9.a45bf70b GPU 1 thread 2
[2012-02-13 19:13:06] Accepted 00000000.7cec99e2.261908de GPU 0 thread 0
[2012-02-13 19:13:06] Accepted 00000000.f1876059.5632d07f GPU 1 thread 2
[2012-02-13 19:13:09] Accepted 00000000.e99d4580.8e65208a GPU 0 thread 0
[2012-02-13 19:13:11] Accepted 00000000.11d37c47.d18b4acc GPU 1 thread 2
[2012-02-13 19:13:19] Accepted 00000000.1a280744.98022220 GPU 0 thread 0
[2012-02-13 19:13:22] Accepted 00000000.873664ef.0111697a GPU 1 thread 2
[2012-02-13 19:13:31] Rejected 00000000.1a280744.98022220 GPU 0 thread 0 (Duplicate proof of work)
[2012-02-13 19:13:50] Accepted 00000000.79fb7bad.6b775f75 GPU 0 thread 0
[2012-02-13 19:13:54] Accepted 00000000.21e40877.39880863 GPU 0 thread 0
[2012-02-13 19:13:57] Accepted 00000000.3f627669.a5e15dde GPU 1 thread 2
[2012-02-13 19:14:02] Accepted 00000000.da047662.f1b31d69 GPU 1 thread 2
[2012-02-13 19:14:08] Accepted 00000000.becd9e94.675d42ec GPU 1 thread 2
[2012-02-13 19:14:13] Accepted 00000000.6030ccf8.7c393ded GPU 1 thread 2
[2012-02-13 19:14:15] Accepted 00000000.20edc5a5.2cec4640 GPU 1 thread 2
[2012-02-13 19:14:16] Accepted 00000000.bbc6d677.ae2bd3b0 GPU 1 thread 2
[2012-02-13 19:14:21] Accepted 00000000.c7e82506.3858ace8 GPU 1 thread 2
[2012-02-13 19:14:24] Accepted 00000000.eafb918c.1429db5d GPU 0 thread 0
[2012-02-13 19:14:26] Accepted 00000000.7b59f5c8.9a141209 GPU 0 thread 0
[2012-02-13 19:14:29] Accepted 00000000.0f9659d9.dcee6c6b GPU 0 thread 0
[2012-02-13 19:14:38] Accepted 00000000.48ac059c.177c87e6 GPU 1 thread 2
[2012-02-13 19:14:39] Accepted 00000000.773bef37.282f8829 GPU 1 thread 2
[2012-02-13 19:14:39] Accepted 00000000.f7ef4cdb.7e200dc7 GPU 0 thread 0
[2012-02-13 19:14:40] Rejected 00000000.0f9659d9.dcee6c6b GPU 0 thread 0 (Duplicate proof of work)
[2012-02-13 19:14:51] Rejected 00000000.f7ef4cdb.7e200dc7 GPU 0 thread 0 (Duplicate proof of work)
[2012-02-13 19:14:56] Accepted 00000000.1d239039.73151bc4 GPU 1 thread 2

Just recently upgraded to cgminer 2.2.5 so maybe that has something to do with it Huh

It might be the pool but I am only seeing it on the rig running 2.2.5 (11.2 driver, 2.5 SDK)

Normally have about 0.2% reject rate on this one rig I am hitting >5% and 98 or 99 are duplicate work errors.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

cgminer mines fine on nvidia (if not the fastest)
python-pyopencl is the package you need on ubuntu

cgminer -n shows this:
[2012-02-14 13:27:59] CL Platform 0 vendor: NVIDIA Corporation
[2012-02-14 13:27:59] CL Platform 0 name: NVIDIA CUDA
[2012-02-14 13:27:59] CL Platform 0 version: OpenCL 1.1 CUDA 4.1.1

Presumably the most basic of cuda tools will work also on windows.

os2sam

legendary

Activity: 3586

Merit: 1098

Think for yourself

Quote from: kano on February 13, 2012, 07:16:22 PM

Quote from: Schleicher on February 13, 2012, 06:07:37 PM

Quote from: Elmojo on February 13, 2012, 04:15:55 PM

If you know of a more appropriate CUDA miner, I'd love to hear about it!

rpcminer-cuda is the only CUDA miner, I think.
But rpcminer doesn't support longpolling or any other advanced features.
OpenCL miners are a little bit slower.

cgminer does it - but it seems no one who uses it knows what is required to install to get it working Tongue

Does it or Did it? I see no references anymore to NVidia or CUDA on the top post.
Sam

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Endeavour79 on February 13, 2012, 08:45:38 PM

I have a question regarding the SDKs..

For HD5xxx users the SDK 2.1 is the fastest and I would like to use it.
Does it already contain all the functions we need for CGMINER, supporting GPUClock, Memory and Fan settings?
Is this related to SDK or driver version?

Driver has those functions. 11.6 or greater driver. SDK 2.1 should be fine.

Endeavour79

full member

Activity: 174

Merit: 100

I have a question regarding the SDKs..

For HD5xxx users the SDK 2.1 is the fastest and I would like to use it.
Does it already contain all the functions we need for CGMINER, supporting GPUClock, Memory and Fan settings?
Is this related to SDK or driver version?

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Schleicher on February 13, 2012, 06:07:37 PM

Quote from: Elmojo on February 13, 2012, 04:15:55 PM

If you know of a more appropriate CUDA miner, I'd love to hear about it!

rpcminer-cuda is the only CUDA miner, I think.
But rpcminer doesn't support longpolling or any other advanced features.
OpenCL miners are a little bit slower.

cgminer does it - but it seems no one who uses it knows what is required to install to get it working Tongue

Schleicher

hero member

Activity: 675

Merit: 514

Quote from: Elmojo on February 13, 2012, 04:15:55 PM

If you know of a more appropriate CUDA miner, I'd love to hear about it!

rpcminer-cuda is the only CUDA miner, I think.
But rpcminer doesn't support longpolling or any other advanced features.
OpenCL miners are a little bit slower.

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 652. (Read 5805998 times)