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

[nst6563]

Will this keep auto tuning? it don't even touch 361 KH/s.

GSD 0: | 855 MHz | 247.3/347.2 KH/s | A: 38 R: 0 H: 4

You should set log = true also so you have a record of the autotune results and how long it took.  When I ran autotune, I left it for a couple hours and checked back and it was finished.

[pekv2]

Does it auto tune everytime it is restarted? or shutdown then started does it autotune again?

[reactor]

Does it auto tune everytime it is restarted? or shutdown then started does it autotune again?

Generally you run autotune until it finishes, capture the final values, then re-start with those values and no autotune.  It is basically taking care of the step, test, step, test... for you so you get max performance per chip, but leaving it on indefinitely adds no value since it'll restart the step process again.

[pekv2]

tnx reactor, nst6563 also explained it over pm.

I'm liking this sandors cpuminer. very neat.

now to enable log in the json is what I don't know how to do. I asked nst6563 over PM, sure he is writing it up as we type.

[pekv2]

well, I


C:\Users\Admin\Desktop\minerd-gc3355>minerd-gc3355.exe -c config.json
minerd-gc3355.exe: config.json:18: '}' expected near '"log"'

C:\Users\Admin\Desktop\minerd-gc3355>pause
Press any key to continue . . .

I added "log" : true and got above error.

[reactor]

well, I


C:\Users\Admin\Desktop\minerd-gc3355>minerd-gc3355.exe -c config.json
minerd-gc3355.exe: config.json:18: '}' expected near '"log"'

C:\Users\Admin\Desktop\minerd-gc3355>pause
Press any key to continue . . .

I added "log" : true and got above error.

If you want to be super-safe, use Sandor's example config and just modify it, making sure starting/trailing braces are always there.  If you put the log at the end of the file, make sure it looks like so:

"log" : true
}
 
The } will be closing out the object.  I'm on right now, feel free to PM me the json and I can look at it for 'ya.

[pekv2]

well, I


C:\Users\Admin\Desktop\minerd-gc3355>minerd-gc3355.exe -c config.json
minerd-gc3355.exe: config.json:18: '}' expected near '"log"'

C:\Users\Admin\Desktop\minerd-gc3355>pause
Press any key to continue . . .

I added "log" : true and got above error.

If you want to be super-safe, use Sandor's example config and just modify it, making sure starting/trailing braces are always there.  If you put the log at the end of the file, make sure it looks like so:

"log" : true
}
 
The } will be closing out the object.  I'm on right now, feel free to PM me the json and I can look at it for 'ya.

I tried cmd line way to.

C:\Users\Admin\Desktop\minerd-gc3355>minerd-gc3355.exe -c config.json --log
minerd-gc3355.exe: option `--log' requires an argument
Try `minerd --help' for more information.

C:\Users\Admin\Desktop\minerd-gc3355>pause
Press any key to continue . . .

K I will pm the json.

[pekv2]

I got it by using the cmd line

Code:

--log=C:\Users\Admin\Desktop\minerd-gc3355\log.log

so my .bat looks like

Code:

minerd-gc3355.exe -c config.json --log=C:\Users\Admin\Desktop\minerd-gc3355\log.log
pause

Ty, to nst6563 and reactor and --help LOl


I'm on my way to tuning.

---

Edit

lmao that was a difficult one for all three of us LOL. rofl. right in the --help file derp.

[nst6563]

I got it by using the cmd line

Code:

--log=C:\Users\Admin\Desktop\minerd-gc3355\log.log

so my .bat looks like

Code:

minerd-gc3355.exe -c config.json --log=C:\Users\Admin\Desktop\minerd-gc3355\log.log
pause

Ty, to nst6563 and reactor and --help LOl


I'm on my way to tuning.

---

Edit

lmao that was a difficult one for all three of us LOL. rofl. right in the help file derp.

amazing no one ever checks the helpfile....it's the little things that get ya

[pekv2]

--log=log.txt

"log" : "log.txt"

They both work.

or

log.log will work as well

like

--log=log.log

"log" : "log.log"

[smtn512]

Sandor, ever since 0.9g, I'm getting the following message when connecting to MiningRigRentals. As you can see, the stratum server name also changes to some odd characters. Eventually, it says it cannot connect to stratum "http(null)". Not sure if it's an issue on my side or not

https://i.imgur.com/mSV3y1F.gif

Sandor, have you had a chance to look at this please? Something changed after 0.9f, I can't connect to MiningRigRentals with any of the latest versions. I think when they redirect the stratum connection to a different port, it fails?

Code:

 
[2014-05-12 22:51:13] Stratum connection failed: Couldn't resolve host 'http(null)'
 [2014-05-12 22:51:13] ...retry after 5 seconds

Toxic0n, I've encountered a similar issue with my gblade, with 1.0a and b, on ltcrabbit.com. On a vardiff port, I was eventually pushed up to 512 diff and within hours, sometimes only minutes of hitting diff 512 I would get this connection issue. Ltcrabbit doesn't have any option for fixed difficulty, except a fixed 16 diff port. I've been using the 16 diff port for nearly 48 hours no with no issue at all. I'm looking for a good multipool that offers fixed diff settings now to test further... Hope this helps.

[wolfey2014]

Does it auto tune everytime it is restarted? or shutdown then started does it autotune again?

Generally you run autotune until it finishes, capture the final values, then re-start with those values and no autotune.  It is basically taking care of the step, test, step, test... for you so you get max performance per chip, but leaving it on indefinitely adds no value since it'll restart the step process again.

+1 - I agree with ya! Good observation! I concur!

[Dabs]

So I should autotune once, for several hours (maybe overnight) with the -debug and -log.

Then sift through the log to get all the values, plug it into the config, and start.

[pekv2]

So I should autotune once, for several hours (maybe overnight) with the -debug and -log.

Then sift through the log to get all the values, plug it into the config, and start.

Autotune once if using cpuminer of sandors.

once autotune is done

You can open the log and just search for "autotune stopped" and grab the speed from the line right above it for use in the config.

remove autotune from json.

start.

[pekv2]

Does anyone know what the 288.7 means?

[michelem]

Don't remember if someone asked for it here btw Minera image file for Raspberry PI is ready to be downloaded if you wanna give a try without the worry of install/ssh anything.

http://j.mp/minera-latest-img

Please refer to the README here.

Official forum thread is here: https://bitcointalk.org/index.php?topic=596620.0

Enjoy it.

[reactor]

Does anyone know what the 288.7 means?

Current 'average' / Long 'average'

Not sure what span current covers, but when my miners start up the first value remains high and the second catches up over time.

[sandor111]

Does anyone know what the 288.7 means?

Current 'average' / Long 'average'

Not sure what span current covers, but when my miners start up the first value remains high and the second catches up over time.

The first is the effective hashrate (pool hashrate), the second is the current hashrate. The first will tend to get closer to the second over time.

[reactor]

I upgraded to 1.0b for CPUMiner and am experiencing a weird issue, not sure if anyone else is seeing this.

When running, I'll experience the occasional New job > Chips reset > Chips get new work and everything continues to process like awesomeness.  Everything is running very stable and all blades are averaging over 2.8MH per side, so I'm a happy camper.  But this morning I noticed a slight down-tick from my pool average so I went to investigate.

Long story short, every time one of these work resets happens I get a kworker.  They're matched to the usb locations of blade halves, so eventually I'll have kworker/0:2, kworker/0:0, etc., littering my processes.  And bogging down my RPi.  While doing this research and at some point after it hit eight kworkers (for the 4 blades on this pi) the cpuminer instance stopped reporting work, verified poolside.  So I killed my processes and went about restarting my mining loop and CPUminer just hung with no output.  Looked and sure enough all eight kworker instances were there, however I cannot 'kill' them whatsoever, even prevented a reboot from the command line.  Cold-rebooting my system cleared everything as expected, but now I'm running again and noticing the kworkers.  

I started the process when I began writing this post, right now I've got three kworkers going.  Will update if this keeps up, but may downgrade back to .9e (last place my blades lived happily without hassle).  Anyone else seeing this?

Edit: Since I'm now monitoring for this, just noticed I went from kworker/0:2, 0:0, 0:1 to just kworker/0:2,0:0 over the course of a few minutes.  So I'm not sure if these are processing that aren't terminating correctly or if there *should* be a kworker(s) sitting there threading out the work.

[edonkey]

I'm using cpuminer v1.0a under Ubuntu 12.10. I've got the minerd application set to load via rc.local as part of a Minera installation.

I've got a problem after a reboot where minerd goes into a weird state where it doesn't hash anything. When I grab the stats with a python script I wrote, I see the following weirdness:

Code:

{
    "start_time": 1399756136, 
    "err": 0, 
    "devices": {
        "ttyACM1": {
            "serial": "6D89577A4857", 
            "chips": []
        }, 
        "ttyACM0": {
            "serial": "6D8A21A34857", 
            "chips": []
        }, 
        "ttyACM2": {
            "serial": "6D8E40854857", 
            "chips": []
        }
    }
}

If I manually stop and start minerd, it starts working. But that kind of the defeats the purpose of the auto restart feature.

Any ideas what might cause this? Maybe minerd is being launched too early, where certain system resources are not yet available?

I posted this in the Minera thread, but it seems like this is an issue with cpuminer being started under rc.local.