Just download 2.7.6 and now it shows "Diff 1, or Diff 2" ?
Yes, or Diff3 or Diff(n) depending on the difficulty of the share that you are receiving from the pool that you are on.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 482. (Read 5805728 times)
October 03, 2012, 09:48:10 PM
Yes, or Diff3 or Diff(n) depending on the difficulty of the share that you are receiving from the pool that you are on.
October 03, 2012, 09:42:19 PM
Just download 2.7.6 and now it shows "Diff 1, or Diff 2" ?
October 03, 2012, 05:34:12 PM
Scrypt mining is still broken in that it can not utilize high thread concurrencies (I need to use a thread concurrency of 24000 for my 7950s to mine effectively). The bug seems to be with the calculation for memory allocation. It can be easily duplicated by setting the thread concurrency above 8192, eg 12288. In reaper, any thread concurrency may be used as long as it is a multiple of 64 and produces a memory padding that fits within the card's memory space.
Using "set GPU_MAX_ALLOC_PERCENT=100" in Windows allows the program to run, but it doesn't hash at all and does not create a memory pad on the GPU.
I reported this several weeks ago and it still hasn't been addressed.
That's cause I have no idea what the problem is. Setting GPU_MAX_ALLOC_PERCENT does nothing on windows, only linux. Using "set GPU_MAX_ALLOC_PERCENT=100" in Windows allows the program to run, but it doesn't hash at all and does not create a memory pad on the GPU.
I reported this several weeks ago and it still hasn't been addressed.
October 03, 2012, 11:28:02 AM
Scrypt mining is still broken in that it can not utilize high thread concurrencies (I need to use a thread concurrency of 24000 for my 7950s to mine effectively). The bug seems to be with the calculation for memory allocation. It can be easily duplicated by setting the thread concurrency above 8192, eg 12288. In reaper, any thread concurrency may be used as long as it is a multiple of 64 and produces a memory padding that fits within the card's memory space.
Using "set GPU_MAX_ALLOC_PERCENT=100" in Windows allows the program to run, but it doesn't hash at all and does not create a memory pad on the GPU.
I reported this several weeks ago and it still hasn't been addressed.
Using "set GPU_MAX_ALLOC_PERCENT=100" in Windows allows the program to run, but it doesn't hash at all and does not create a memory pad on the GPU.
I reported this several weeks ago and it still hasn't been addressed.
October 02, 2012, 08:20:56 PM
In that case it might actually be the pool's fault setting a high rolltime and then rejecting the shares as late.
Thank you ckolivas, was afraid it may be something to do with the pool. I did find some other threads also stating that if time on the pool server was drifting too far it may be the cause too, hopefully Graet can uncover the issue cause I dont want to pool jump. October 02, 2012, 05:41:46 PM
Can you track down which version did *not* have this problem? cgminer only, please.
I tried your suggestion and jumped to another pool and I am at a:276 with only r:5 and those were all prevhash-stale. So it may be pool dependent, I even have I=18 right now and no issues with rejections.
October 02, 2012, 02:08:12 PM
I reported a crash earlier in this thread which I feel is related when doing scrypt mining. (here: https://bitcointalksearch.org/topic/m.1231316)
I found that 2.6.4 is the "newest" version that doesn't seem to exhibit the same symptoms.
UPDATE:
Also 2.6.4 of cgminer does it. https://dl.dropbox.com/u/7490029/cgm2.6.4.jpg
October 02, 2012, 01:53:43 PM
I reported a crash earlier in this thread which I feel is related when doing scrypt mining. (here: https://bitcointalksearch.org/topic/m.1231316)
I found that 2.6.4 is the "newest" version that doesn't seem to exhibit the same symptoms.
TY for finding that, the oldest copy I had on hand was 2.6.5 and the oldest windows version avail on his site is 2.6.6 so I had no way to test lower versions without a lot of digging. I found that 2.6.4 is the "newest" version that doesn't seem to exhibit the same symptoms.
October 02, 2012, 01:30:02 PM
Is this new? If so, can you pinpoint which version it started from? If not, is it unique to lc.ozco.in ?
As for version I had been running bfgminer, all the way up to 2.8.1 was getting the error so switched back to cgminer then have tried cgminer 2.7.5.
I reported a crash earlier in this thread which I feel is related when doing scrypt mining. (here: https://bitcointalksearch.org/topic/m.1231316)
I found that 2.6.4 is the "newest" version that doesn't seem to exhibit the same symptoms.
October 02, 2012, 01:04:43 PM
version 12.
Does CGMiner support a version with sunglasses?
LOL, forgot that an 8 next to an ) made sunglasses. I have version 12.8
October 02, 2012, 11:10:18 AM
Is this new? If so, can you pinpoint which version it started from? If not, is it unique to lc.ozco.in ?
As for version I had been running bfgminer, all the way up to 2.8.1 was getting the error so switched back to cgminer then have tried cgminer 2.7.5.
don't remember seeing it in 2.7.4, but I only fired a gpu back up last night on 2.7.5 to see if I could replicate rahlquist issue.
spoke to kano briefly before on irc
I'll fire up a 2.7.4 and check
awake: I wont be long
G
edit: it is there i'll regress through some versions in morning unless rahlquist spots the change before
October 02, 2012, 10:59:23 AM
Can you track down which version did *not* have this problem? cgminer only, please.
October 02, 2012, 10:49:39 AM
Can you track down which version did *not* have this problem? cgminer only, please.
I tried your suggestion and jumped to another pool and I am at a:276 with only r:5 and those were all prevhash-stale. So it may be pool dependent, I even have I=18 right now and no issues with rejections.
October 02, 2012, 10:30:46 AM
Is this new? If so, can you pinpoint which version it started from? If not, is it unique to lc.ozco.in ?
As for version I had been running bfgminer, all the way up to 2.8.1 was getting the error so switched back to cgminer then have tried cgminer 2.7.5.
October 02, 2012, 10:26:28 AM
Is this new? If so, can you pinpoint which version it started from? If not, is it unique to lc.ozco.in ?
As for version I had been running bfgminer, all the way up to 2.8.1 was getting the error so switched back to cgminer then have tried cgminer 2.7.5.
October 02, 2012, 10:02:35 AM
ckolivas,
I know LTC is no more your favorite thing than Stratum is Luke-jr's. However a few of us are starting to see a lot of rejections with time-too-old issues. Do you have any insight what might be done to stop these? I mentioned it over at #ozcoin and Graet was kind enough to fire up an instance and he got "<@Graet> A:644 R:197 after 1.5 hours" so you can see its a ton of rejects I have seen 44-50% on my own miners with no other hardware errors etc.
Anything you can suggest?
Is this new? If so, can you pinpoint which version it started from? If not, is it unique to lc.ozco.in ? I know LTC is no more your favorite thing than Stratum is Luke-jr's. However a few of us are starting to see a lot of rejections with time-too-old issues. Do you have any insight what might be done to stop these? I mentioned it over at #ozcoin and Graet was kind enough to fire up an instance and he got "<@Graet> A:644 R:197 after 1.5 hours" so you can see its a ton of rejects I have seen 44-50% on my own miners with no other hardware errors etc.
Anything you can suggest?
October 02, 2012, 09:44:52 AM
Do you get the same with 2.7.5 ?
Yes. https://dl.dropbox.com/u/7490029/cgm.jpgHere is what I am launching with, no .conf file stored, windows 7 64bit. 5770 card and Catalyst 12.7
cgminer.exe -o http://lc.ozco.in:9332/ -u username -p password --scrypt --shaders 800 --intensity 13 --worksize 256
October 02, 2012, 09:23:08 AM
version 12.
Does CGMiner support a version with sunglasses?
October 02, 2012, 08:54:10 AM
Well judging by the error CL etc etc Is SDK installed I would start there.
Make sure when you installed you didn't just get a driver but the full install with the SDK. What OS are you using as that has a lot of effect on how to get it to work.
Make sure when you installed you didn't just get a driver but the full install with the SDK. What OS are you using as that has a lot of effect on how to get it to work.
I figured SDK too which is why I went to AMD and downloaded the latest SDK version (SDK 2.7) AND the latest CCC version (version 12.
I am on Windows XP 32-bit
October 02, 2012, 07:33:36 AM
ckolivas,
I know LTC is no more your favorite thing than Stratum is Luke-jr's. However a few of us are starting to see a lot of rejections with time-too-old issues. Do you have any insight what might be done to stop these? I mentioned it over at #ozcoin and Graet was kind enough to fire up an instance and he got "<@Graet> A:644 R:197 after 1.5 hours" so you can see its a ton of rejects I have seen 44-50% on my own miners with no other hardware errors etc.
Anything you can suggest?
Do you get the same with 2.7.5 ? I know LTC is no more your favorite thing than Stratum is Luke-jr's. However a few of us are starting to see a lot of rejections with time-too-old issues. Do you have any insight what might be done to stop these? I mentioned it over at #ozcoin and Graet was kind enough to fire up an instance and he got "<@Graet> A:644 R:197 after 1.5 hours" so you can see its a ton of rejects I have seen 44-50% on my own miners with no other hardware errors etc.
Anything you can suggest?
Jump to: