[GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 25.

PVmining

sr. member

Activity: 330

Merit: 252

Quote from: sandor111 on May 05, 2014, 08:20:17 PM

* Add --gc3355-timeout=N option: restart GC3355 chips when no share is submitted and timeout expires. N = value in seconds.

does it restart a single chip, or the complete GS?

I had some problems to get cpuminer 9.d working with higher diff rates (512) - a few versions ago wafflepool & clevermining for example worked.
Now it seems as some single chips don't start working att all. I use 5 chip GS with fixed frequency for every single chip.

kenshirothefist

sr. member

Activity: 457

Merit: 273

I'd like to contact David Bartley (dtbartle), the author of CGMiner 3.7.2 with GridSeed GC3355 support (https://github.com/dtbartle/cgminer-gc3355). Does anybody know if he is a member of this (or any other) forum? I would like to ask him if he could include some additional patches.

MatthewBCF

member

Activity: 71

Merit: 10

Quote from: fivejonnyfive on May 06, 2014, 12:23:37 AM

Quote from: sandor111 on May 05, 2014, 10:00:56 PM

Quote from: tc61 on May 05, 2014, 09:58:58 PM

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.

Just curious, On a Raspberry Pi do the device names stay constant across reboots? I think I was accidentally sold a voltmodded gridseed (which I'd be pretty stoked about) but the fast one last time I booted doesn't seem to be the fast one this time I booted.

For me the devices stay the same ..as long as usb cables aren't moved (duh?). I've given up trying to expect consistency until they are hashing for awhile..then it settles in. I've seen sometimes 250% of expected rate at the start, but it will settle down.

fivejonnyfive

sr. member

Activity: 294

Merit: 250

Quote from: sandor111 on May 05, 2014, 10:00:56 PM

Quote from: tc61 on May 05, 2014, 09:58:58 PM

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.

Just curious, On a Raspberry Pi do the device names stay constant across reboots? I think I was accidentally sold a voltmodded gridseed (which I'd be pretty stoked about) but the fast one last time I booted doesn't seem to be the fast one this time I booted.

MatthewBCF

member

Activity: 71

Merit: 10

Quote from: MatthewBCF on May 06, 2014, 12:14:56 AM

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 figure examples worth 1000 words too. Notice the timestamps from the top 3 accepted and then it just drops into new block but no work, waiting changes nothing.

[2014-05-06 05:17:36] Accepted 8ccd7d9d GSD 0@22
[2014-05-06 05:17:47] Accepted 26722406 GSD 0@6
[2014-05-06 05:17:48] Accepted 1340d68a GSD 0@3
[2014-05-06 05:18:05] Stratum difficulty changed
[2014-05-06 05:18:05] Dispatching new work to GC3355 threads
[2014-05-06 05:18:05] New job_id: 5b2d Diff: 263
[2014-05-06 05:18:05] Accepted 5352d64d GSD 0@13
[2014-05-06 05:18:10] New job_id: 5b64 Diff: 263
[2014-05-06 05:18:10] Stratum detected new block
[2014-05-06 05:18:50] New job_id: 5c39 Diff: 263
[2014-05-06 05:18:50] Stratum detected new block
[2014-05-06 05:18:56] New job_id: 5c96 Diff: 263
[2014-05-06 05:18:56] Stratum detected new block
[2014-05-06 05:19:03] New job_id: 5cf6 Diff: 263
[2014-05-06 05:19:03] Stratum detected new block

MatthewBCF

member

Activity: 71

Merit: 10

Quote from: sandor111 on April 30, 2014, 01:31:38 PM

Quote from: surgexvb on April 30, 2014, 01:29:21 PM

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.

Quote from: Kergekoin on April 30, 2014, 09:31:16 AM

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

sandor111

hero member

Activity: 616

Merit: 500

Quote from: tc61 on May 05, 2014, 09:58:58 PM

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.

tc61

hero member

Activity: 494

Merit: 500

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

tc61

hero member

Activity: 494

Merit: 500

Thank you!!!!

thearcticcat

newbie

Activity: 8

Merit: 0

thanks, appreciated

sandor111

hero member

Activity: 616

Merit: 500

Quote from: thearcticcat on May 05, 2014, 09:33:21 PM

Quote from: sandor111 on May 05, 2014, 08:20:17 PM

cpuminer-gc3355 v0.9e

* Any frequency is supported now.
* Add --gc3355-timeout=N option: restart GC3355 chips when no share is submitted and timeout expires. N = value in seconds.
* Fix GC3355 firmware detection and hashrate display
* Fix stability issues with Blades
* Autotune: only 5-chip USB miner

Binaries have been updated.
Windows: https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip
Raspberry PI: https://www.dropbox.com/s/xc3lvysi8vtrt00/minerd-gc3355

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

Activity: 8

Merit: 0

Quote from: sandor111 on May 05, 2014, 08:20:17 PM

cpuminer-gc3355 v0.9e

* Any frequency is supported now.
* Add --gc3355-timeout=N option: restart GC3355 chips when no share is submitted and timeout expires. N = value in seconds.
* Fix GC3355 firmware detection and hashrate display
* Fix stability issues with Blades
* Autotune: only 5-chip USB miner

Binaries have been updated.
Windows: https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip
Raspberry PI: https://www.dropbox.com/s/xc3lvysi8vtrt00/minerd-gc3355

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'

RowanX

member

Activity: 86

Merit: 10

Quote from: sandor111 on May 05, 2014, 09:00:54 PM

Quote from: RowanX on May 05, 2014, 08:47:13 PM

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.

reactor

sr. member

Activity: 420

Merit: 250

Quote from: sandor111 on May 05, 2014, 08:20:17 PM

cpuminer-gc3355 v0.9e

* Any frequency is supported now.
* Add --gc3355-timeout=N option: restart GC3355 chips when no share is submitted and timeout expires. N = value in seconds.
* Fix GC3355 firmware detection and hashrate display
* Fix stability issues with Blades
* Autotune: only 5-chip USB miner

Binaries have been updated.
Windows: https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip
Raspberry PI: https://www.dropbox.com/s/xc3lvysi8vtrt00/minerd-gc3355

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. Cheesy

sandor111

hero member

Activity: 616

Merit: 500

Quote from: RowanX on May 05, 2014, 08:47:13 PM

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.

jamieb81

sr. member

Activity: 308

Merit: 250

Quote from: racebyu on May 05, 2014, 08:53:12 PM

Quote from: RowanX on May 05, 2014, 08:47:13 PM

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

racebyu

sr. member

Activity: 346

Merit: 260

Quote from: ZiG on May 05, 2014, 08:48:59 PM

Quote from: racebyu on May 05, 2014, 08:45:42 PM

Quote from: sandor111 on May 05, 2014, 08:42:29 PM

Quote from: racebyu on May 05, 2014, 08:39:00 PM

Quote from: sandor111 on May 05, 2014, 08:20:17 PM

cpuminer-gc3355 v0.9e

* Any frequency is supported now.
* Add --gc3355-timeout=N option: restart GC3355 chips when no share is submitted and timeout expires. N = value in seconds.
* Fix GC3355 firmware detection and hashrate display
* Fix stability issues with Blades
* Autotune: only 5-chip USB miner

Binaries have been updated.
Windows: https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip
Raspberry PI: https://www.dropbox.com/s/xc3lvysi8vtrt00/minerd-gc3355

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

racebyu

sr. member

Activity: 346

Merit: 260

Quote from: RowanX on May 05, 2014, 08:47:13 PM

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.

ZiG

sr. member

Activity: 406

Merit: 250

Quote from: racebyu on May 05, 2014, 08:45:42 PM

Quote from: sandor111 on May 05, 2014, 08:42:29 PM

Quote from: racebyu on May 05, 2014, 08:39:00 PM

Quote from: sandor111 on May 05, 2014, 08:20:17 PM

cpuminer-gc3355 v0.9e

* Any frequency is supported now.
* Add --gc3355-timeout=N option: restart GC3355 chips when no share is submitted and timeout expires. N = value in seconds.
* Fix GC3355 firmware detection and hashrate display
* Fix stability issues with Blades
* Autotune: only 5-chip USB miner

Binaries have been updated.
Windows: https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip
Raspberry PI: https://www.dropbox.com/s/xc3lvysi8vtrt00/minerd-gc3355

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

RowanX

member

Activity: 86

Merit: 10

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.

Topic: [GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 25. (Read 308807 times)