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

[reactor]

0.9e ran just fine overnight.  Notice that the 5-chips are quirkier than the blades in terms of performance, but it could also be that I'm on a pool with a fixed [higher] difficulty.  Otherwise performance is consistent across all devices and hashrate has been the highest sustained ever on these things. 

Now I just gotta figure out what ZoomHash is doing about the insane price drop while my order was in processing and we'll be in business.

Great work sandor111 with 0.9e version.
Blade on Win7 laptop running since last night at 11:30pm no issues or resets.

Is there any way or chance to get a backup pool config setting in the bat file?
I know you have the reset for the Blades if not hashing but after X resets then
go to a backup pool? If you need a unit to test on you can use mine and I can
setup TeamViewer for access?

You sound like me, been trying to re-learn all the good linux stuff to create a script that is solid for restarts and the like.  Got a single shutdown on .9e earlier but no rhyme or reason why (wasn't recording logs anymore), otherwise it's beautiful.  My two new blades will be very happy there.

[1714767125]

1714767125

[1714767125]

1714767125

[reactor]

Weird, on 0.9e just noticed this message before the screen shutdown, spelling may be off:

SIGSEGV Received
Cleanup

then the screen shut down.  Reboot and everything is fine, but what's that about?

[Emu05]

Does anybody has sandors miner running on a windows server ? i´m getting an erro massage as soon as i start the minred.exe does anybody had the same problem / a solution for it

[sandor111]

Weird, on 0.9e just noticed this message before the screen shutdown, spelling may be off:

SIGSEGV Received
Cleanup

then the screen shut down.  Reboot and everything is fine, but what's that about?

I've updated the binaries once again (still v0.9e), this should fix the crash.

[edonkey]

Is there a way to have cpuminer automatically find all of the Gridseed 5-chip devices rather than specify each one via the --gc3355=/dev option?

[MatthewBCF]

Nice update Sandor - RE v0.9e - I see blades more stable now, but after time it still falls into the path of not posting work..the 5chips remain good though when that happens.

Trying with the new timeout flag to see if that keeps them going after 1-2 hrs.  Will report back if they don't recycle with the flag.

Alright the last 8+ hours with .9e has been rock solid as long as the timeout recycle is set..

I don't how many occurred but I randomly caught 3 recycles during that time. 

I just wish one of them wasn't throwing ~20HW error/hr.

This is by far and away the most solid I've with a steady 2.7MH @pool across all blades @838Mhz.

If anyone has ideas to squeeze out a bit more juice or calm the HW errors on a blade I'm all ears.

[Ranma13]

Is there a way to have cpuminer automatically find all of the Gridseed 5-chip devices rather than specify each one via the --gc3355=/dev option?

If you're on Linux, you can use this command:

Code:

minerd -o stratum+tcp://pool.com -u USERNAME -p PASSWORD --gc3355-autotune --gc3355=`ls -m /dev/ttyACM* | sed -e 's/, /,/g' | tr -d '\n'` --freq=1200

[plzt]

Nice update Sandor - RE v0.9e - I see blades more stable now, but after time it still falls into the path of not posting work..the 5chips remain good though when that happens.

Trying with the new timeout flag to see if that keeps them going after 1-2 hrs.  Will report back if they don't recycle with the flag.

Alright the last 8+ hours with .9e has been rock solid as long as the timeout recycle is set..

I don't how many occurred but I randomly caught 3 recycles during that time. 

I just wish one of them wasn't throwing ~20HW error/hr.

This is by far and away the most solid I've with a steady 2.7MH @pool across all blades @838Mhz.

If anyone has ideas to squeeze out a bit more juice or calm the HW errors on a blade I'm all ears.

I'm now on 21 hours and all seems to be good. Timeout set at 300

I've my blades set at 838 and getting the following stats:

 GSD 0 | 838 MHz | 2796.9/2828.6 KH/s | A: 12867 R: 45 H: 1

 GSD 1 | 838 MHz | 2811.4/2829.9 KH/s | A: 12943 R: 36 H: 2

[reactor]

Nice update Sandor - RE v0.9e - I see blades more stable now, but after time it still falls into the path of not posting work..the 5chips remain good though when that happens.

Trying with the new timeout flag to see if that keeps them going after 1-2 hrs.  Will report back if they don't recycle with the flag.

Alright the last 8+ hours with .9e has been rock solid as long as the timeout recycle is set..

I don't how many occurred but I randomly caught 3 recycles during that time. 

I just wish one of them wasn't throwing ~20HW error/hr.

This is by far and away the most solid I've with a steady 2.7MH @pool across all blades @838Mhz.

If anyone has ideas to squeeze out a bit more juice or calm the HW errors on a blade I'm all ears.

I'm now on 21 hours and all seems to be good. Timeout set at 300

I've my blades set at 838 and getting the following stats:

 GSD 0 | 838 MHz | 2796.9/2828.6 KH/s | A: 12867 R: 45 H: 1

 GSD 1 | 838 MHz | 2811.4/2829.9 KH/s | A: 12943 R: 36 H: 2

I've got to update to the new .9e, having some weird issues but I'm always distracted and don't catch what is happening before the script pushes through to a reboot.  Actually upped my timeout since the 5-chips were cutting out due to pool diff.  As opposed to what someone else said on here, I'm finding my devices jumping between what /dev/tty~~ they're on so I can't consistently put the 5-chips one spot and the blades in another.  Guess I'm glad I got the 5chips since they're discontinued now, but I'd still like to get my hash value for them.

Out of curiosity, since I'm still getting back in the linux bike after many years, I've got a question for folks.   If you use CGMiner you'll see a device id per device, can't remember off the top of my head but the 5chips had 4* and the blades had 6* (or the other way around), both easily associated with hashrates so you can know which device is which.  So...  first question, where do those ids come from?  From exploring lsusb and diving in from there I cannot find these ids anywhere, *but* if I can detect them and what usb location they're at I can script out different pools for 5chips and blades.  Mind you, this is all because I want to have this all on the rpi and not have my windows box on if I can avoid it.  And because over the course of this morning #4 has swapped between blade and 5chip in the work I've been doing, but with no rhyme or reason to when it switches on different reboots.  Have a better hub coming this morning so no chaining required anymore, but would like to find a software solution as well just for redundancy.

[sandor111]

cpuminer-gc3355 v0.9f

* Automatic detection of GC3355 miners (not for Windows): --gc3355-detect
* API: on the fly frequency setting
* API: allow simulaneous connections

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

[Kokok]

cpuminer-gc3355 v0.9f

* Automatic detection of GC3355 miners (not for Windows): --gc3355-detect
* API: on the fly frequency setting
* API: allow simulaneous connections

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

This just keeps getting better and better!
 

[sandor111]

Serial string is added to display when built from the last commit.

[plzt]

0.9e going strong for 28 hours so far

will update to f next time there's an interrupt

[fivejonnyfive]

Serial string is added to display when built from the last commit.

Nice! I was going to suggest that feature. Thanks mate.

[unamis76]

Having more hardware errors with 0.9e than I had with the cgminer I previously used. Using autotune frequencies for each chip. I know which chips are weaker, but I am not sure which ones are sending out the errors. Any way to discover this info on the log?

[toxic0n]

Having more hardware errors with 0.9e than I had with the cgminer I previously used. Using autotune frequencies for each chip. I know which chips are weaker, but I am not sure which ones are sending out the errors. Any way to discover this info on the log?

Create a php script as per below and you can see the individual chips and the HW errors on them.

Here is an example for PHP:

Code:

<?php
define("API_MINER_START_TIME", "t");
define("API_DEVICES", "d");
define("API_CHIPS", "c");
define("API_LAST_SHARE", "l");
define("API_CHIP_ACCEPTED", "ac");
define("API_CHIP_REJECTED", "re");
define("API_CHIP_HW_ERRORS", "hw");
define("API_CHIP_FREQUENCY", "fr");
define("API_CHIP_HASHRATE", "ha");
define("API_CHIP_SHARES", "sh");
if(!($fp = fsockopen("127.0.0.1", 4028, $errno, $errstr, 0)))
{
    die("Failed to open socket");
}
stream_set_blocking($fp, false);
$out = json_encode(array("get" => "stats"))."\n";
fwrite($fp, $out);
usleep(100000);
$out = "";
while(!feof($fp))
{
    if(!($str = fgets($fp, 2048))) break;
    $out .= $str;
}
fclose($fp);
$arr = json_decode($out);
print_r($arr);

This will print the JSON array.
To get the list of devices you would simply do

Code:

$devs = $arr[API_DEVICES];

[unamis76]

Having more hardware errors with 0.9e than I had with the cgminer I previously used. Using autotune frequencies for each chip. I know which chips are weaker, but I am not sure which ones are sending out the errors. Any way to discover this info on the log?

Create a php script as per below and you can see the individual chips and the HW errors on them.

Here is an example for PHP:

Code:

<?php
define("API_MINER_START_TIME", "t");
define("API_DEVICES", "d");
define("API_CHIPS", "c");
define("API_LAST_SHARE", "l");
define("API_CHIP_ACCEPTED", "ac");
define("API_CHIP_REJECTED", "re");
define("API_CHIP_HW_ERRORS", "hw");
define("API_CHIP_FREQUENCY", "fr");
define("API_CHIP_HASHRATE", "ha");
define("API_CHIP_SHARES", "sh");
if(!($fp = fsockopen("127.0.0.1", 4028, $errno, $errstr, 0)))
{
    die("Failed to open socket");
}
stream_set_blocking($fp, false);
$out = json_encode(array("get" => "stats"))."\n";
fwrite($fp, $out);
usleep(100000);
$out = "";
while(!feof($fp))
{
    if(!($str = fgets($fp, 2048))) break;
    $out .= $str;
}
fclose($fp);
$arr = json_decode($out);
print_r($arr);

This will print the JSON array.
To get the list of devices you would simply do

Code:

$devs = $arr[API_DEVICES];

Is there a more elaborate tutorial on how to make/apply this? Is it enough to install a webserver on my Raspberry? I am sorry, but i only use Linux for my mining rig, I don't have a deep Linux knowledge

[toxic0n]

You just need a webserver with php installed and put that script in your /var/www directory and give it a .php extension

Code:

sudo apt-get install lighttpd php5-cgi
sudo service lighttpd force-reload

[unamis76]

You just need a webserver with php installed and put that script in your /var/www directory and give it a .php extension

Code:

sudo apt-get install lighttpd php5-cgi
sudo service lighttpd force-reload

Thank you, will try it

[toxic0n]

No problem. Also, remember it is normal to see a number of HW errors while the autotune is ongoing. With the above script you can also see the individual chip frequencies it settles at and then set those via the command. That way you should see close to zero errors.