|
ZiG
|
 |
May 06, 2014, 01:23:47 AM |
|
GOOD JOB, buddy...!!!...  |
|
|
|
|
|
wolfey2014
|
|
May 06, 2014, 01:28:46 AM |
|
What is the command syntax for resetting the 5 chips when or after closing the program so the miners stop pulling current as if they were still hashing? Right now, the only way to get them back to idle (about 50% less current than when hashing) is to re-power them. Can you add this feature so it runs upon program close? Thanks |
I Modify Miners Professionally! PM me for details!
|
|
|
|
racebyu
|
|
May 06, 2014, 01:39:00 AM |
|
Perfect, downloaded and running now! What is the freq range, 800-1200? |
|
|
|
|
|
sandor111
|
|
May 06, 2014, 01:42:29 AM |
|
Perfect, downloaded and running now. What is the freq range, 800-1200? 600-1400 |
|
|
|
|
racebyu
|
|
May 06, 2014, 01:45:42 AM |
|
Perfect, downloaded and running now. What is the freq range, 800-1200? 600-1400 Thanks, Also the timeout number "N" is that in Minutes? What is a fair number to set this to, 10 or 10 minutes or is that too short. |
|
|
|
|
RowanX
Member
 Offline
Activity: 86
Merit: 10
|
|
May 06, 2014, 01:47:13 AM |
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply.  |
|
|
|
|
|
ZiG
|
|
May 06, 2014, 01:48:59 AM |
|
Perfect, downloaded and running now. What is the freq range, 800-1200? 600-1400 Thanks, Also the timeout number "N" is that in Minutes? What is a fair number to set this to, 10 or 10 minutes or is that too short. Timeout = N (seconds) ...in seconds... 10min x 60 sec = 600... Set N = 600 for 10 min ...I started with N=300 ...for 5 min...and later will increase, if they are stable... ZiG |
|
|
|
|
|
racebyu
|
|
May 06, 2014, 01:53:12 AM |
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply. I am running on a laptop and Win 7, only notice that error really when its first ramps up in hash rate, after it becomes stable as it reaches max hash rate there is not as many. |
|
|
|
|
|
racebyu
|
|
May 06, 2014, 01:54:01 AM |
|
Perfect, downloaded and running now. What is the freq range, 800-1200? Ok thanks, will add that in to the file also. 600-1400 Thanks, Also the timeout number "N" is that in Minutes? What is a fair number to set this to, 10 or 10 minutes or is that too short. Timeout = N (seconds) ...in seconds... 10min x 60 sec = 600... Set N = 600 for 10 min ...I started with N=300 ...for 5 min...and later will increase, if they are stable... ZiG |
|
|
|
|
|
jamieb81
|
|
May 06, 2014, 02:00:21 AM |
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply. I am running on a laptop and Win 7, only notice that error really when its first ramps up in hash rate, after it becomes stable as it reaches max hash rate there is not as many. same here on win8 works good only a few when they start up and once at optimum there are not many. Nothing that I cannot live with |
|
|
|
|
|
sandor111
|
|
May 06, 2014, 02:00:54 AM |
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply. In 0.9d, new work is sent when there is a new job and after a nonce is found, in 0.9c it would stop hashing immediately and send the new work. The latter is actually inefficient and slows down the mining. Could you post a log with --debug and --protocol option enabled? Personally I'm still getting 0.2% rejects whatever the pool I go with. |
|
|
|
|
reactor
|
|
May 06, 2014, 02:06:05 AM |
|
Brilliant. Just went the easy route and grabbed the rpi version, running it now. Had to take a break from Dark Souls 2 for this.  |
|
|
|
|
RowanX
Member
Offline
Activity: 86
Merit: 10
|
|
May 06, 2014, 02:09:09 AM |
|
I've only been running it for a little while but 0.9e seems to be giving the same problems as 0.9d, for me (Windows version). i.e. too many rejects with message "DEBUG: reject reason: unknown-work". Who here on Windows is or is not having the same issue? I've gone back to using 0.9c, again - its working fantastic. Sandor do you think this issue is likely to be specific to my setup? You are the magic jesus of mining and I look forward to your reply. In 0.9d, new work is sent when there is a new job and after a nonce is found, in 0.9c it would stop hashing immediately and send the new work. The latter is actually inefficient and slows down the mining. Could you post a log with --debug and --protocol option enabled? Personally I'm still getting 0.2% rejects whatever the pool I go with. Sure thing. Just add --debug and --protocol-dump to my bat file? I assume it will output the debug dump into a file in the same directory. How long should I run it for to produce something useful. An hour? I'll do it tomorrow its 3am here and I need to collapse. |
|
|
|
|
thearcticcat
Newbie
Offline
Activity: 8
Merit: 0
|
|
May 06, 2014, 02:33:21 AM |
|
in your windows binary the folder in the zip contains minerd-33355.exe instead of minerd-3355.exe couldnt figure out why it was just looking until i debugged and found minerd-3355.exe didn't exist xD loving all of your work sandor. nothing comes close to the speeds i can get on your fork. i am no longer receiving the Got nonce messages when I run autotune in this one (0.9e) though. any idea why? for example just 'accepted 9996dd55 GSD 1@4' |
|
|
|
|
|
sandor111
|
|
May 06, 2014, 02:43:25 AM |
|
in your windows binary the folder in the zip contains minerd-33355.exe instead of minerd-3355.exe couldnt figure out why it was just looking until i debugged and found minerd-3355.exe didn't exist xD loving all of your work sandor. nothing comes close to the speeds i can get on your fork. i am no longer receiving the Got nonce messages when I run autotune in this one (0.9e) though. any idea why? for example just 'accepted 9996dd55 GSD 1@4' Updated, thanks. Got nonce/autotune messages can be enabled with --debug. |
|
|
|
thearcticcat
Newbie
Offline
Activity: 8
Merit: 0
|
|
May 06, 2014, 02:49:09 AM |
|
thanks, appreciated
|
|
|
|
|
|
tc61
|
|
May 06, 2014, 02:54:29 AM |
|
Thank you!!!!
|
|
|
|
|
|
tc61
|
|
May 06, 2014, 02:58:58 AM |
|
Sandor111, is there a way in the batch file that you can specify a frequency for GDS 0 and another for GDS 1? Or do they both have to be the same?
thx
|
|
|
|
|
|
sandor111
|
|
May 06, 2014, 03:00:56 AM |
|
Sandor111, is there a way in the batch file that you can specify a frequency for GDS 0 and another for GDS 1? Or do they both have to be the same?
thx
Sure, look in my signature for examples on that. |
|
|
|
MatthewBCF
Member
Offline
Activity: 71
Merit: 10
|
|
May 06, 2014, 05:14:56 AM |
|
The freezing problem seems to have something to do.with the autotune feature. When enabled, it freezes every 2 hours or so everytime. When I disable it, now it has been running fine for 12 hours.
That's because the the autotune features prints a line immediately after another, so it's more likely to deadlock (tui_lock). Do you still experience freezing even with v0.9a? It should be a thing of the past now. Looks like "--freq=950" overrides the "--gc3355-freq=\\.\COM42:700"
How could i set one device lower/higher than all the rest without typing each individually?
Edit: OK. I got it. I needed to write individual freq before the overall.
I'm pretty sure it's not the case. The most specific frequency is always applied. Sandor111, I've been using the latest (0.9a) on/off for ~4 days and my blades are always freezing, esp when getting a new block or after I see "dispatching new work.." - One might conclude it is any message except "accepted" which has a chance of causing the freeze. I can't say I've tried everything, but I am pretty sure it isn't the cards as this is an issue occurring in cpuminer, not cgminer. Overall I think it is a fantastic step fwd, seems stable. I know you are going to add the single step freq soon too, so that will be a big plus. Otherwise, any ideas on why the blade freezes, particularly when the difficulty jumps and/or new block or dispatching work ..I wish I could be more precise but it is definitely when something besides hashing happens. I have a pile of 5chips that run on the same raspi with no issue too. Thanks |
Crypto with a purpose :: WATER / DGB / REDD / ECC / NOBL / EMC2 / SHARE
|
|
|
|
