I finally got things squared away and now cpuminer 1.0b is running 100% stably.
I am very pleased with it Sandor!
Now for the 24 hour acid test!
So far, so good.
Well done!
Topic: [GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 14. (Read 308626 times)
Anyone ever have trouble with Blades and CGMiner in windows? I get the pop up "pthreadGC2.dll" is missing, then CGMiner closes. So weird because it mines single Gridseeds just fine.
So much trouble I gave up and have been using CPUminer exclusively since!
Anyone ever have trouble with Blades and CGMiner in windows? I get the pop up "pthreadGC2.dll" is missing, then CGMiner closes. So weird because it mines single Gridseeds just fine.
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. 
Sandor,
using your latest version, 'I think' 1.0...
works great except that it's causing my farm to lose connection after a few hours...
stratum-recv-line failed
starting stratum on stratum+tcp:..maintheminingpools.com3002
Does not reconnect.
I can get it to reconnect via manual restart though.
Also, it takes up to a few minutes for 1.0 to start mining 2 of the miners as their stats stay at 0 until then.,
It's starting all miners clocks but seems that it is causing USB port issues. This is also causing me to have to go back and restart comm ports which just won't work for me. I ain't interested in having to do that again.
Perhaps the receive line failure is a clue?
Ver 2.3.2 doesn't cause this issue as far as I can tell. I keep track of it's overall performance by the total hash rate of my rig. It seems to stay pretty consistent and will run for days and days without interruption save a ddos attack.
Can you help? I love the display and stats 1.0 provides!
Thanks.
stratum_recv_line failed = connection problem. Try the latest binary and please upload the full log with protocol and debug output. Without it I cannot tell what the problem is.
Thanks Sandor, the help file is useless, it's all garbled.unformatted... what are the commands for saving a log file, again?
The version I'm having troubles with is 1.0b
I presume you want me to log this problem before I upgrade, right? I assume you have a 1.0c ready to go already?
Thanks
Add this to cmdline: "-D -P -L log.txt"
Yes I just uploaded a new binary for you to try, still v1.0b though.
Doesn't seem to work no matter where I put it into the command line. I deleted the " marks of course.
Trying your latest ver. Hope it works stably this time. I'll let you know in a few hours if/when....
Sorry " -L log.txt" is supposed to be "--log=log.txt"
Whats the best way to enable autotune for just one of my gridseeds? Run it on its own seperate instance of cpuminer until its tuned?
Seperate instance is the only way.
Sorry, I don't have time for the debugging game.
I'll keep watching the thread to see when you solve the issue.
Thanks and keep up the good work.
i have the same issue , change the psd, it runs good.
Good show....
I presume it works with the 5 chip pods also?
I haven't had to use any reset commands like that before. I had turned OFF comm port FIFO buffers. They are still OFF.
The original version 2.3.2 I was using that doesn't have stats at the top of the page, was working perfectly before I started upgrading to the latest versions, which have all had a series of bugs either newly created or missed in each 'fixed version' which is completely counter productive. So I wait and watch until I think it's safe to upgrade, then look what happens.... ;( I appreciate the efforts but, it's just disappointing if not completely avoidable.
I presume it works with the 5 chip pods also?
I haven't had to use any reset commands like that before. I had turned OFF comm port FIFO buffers. They are still OFF.
The original version 2.3.2 I was using that doesn't have stats at the top of the page, was working perfectly before I started upgrading to the latest versions, which have all had a series of bugs either newly created or missed in each 'fixed version' which is completely counter productive. So I wait and watch until I think it's safe to upgrade, then look what happens.... ;( I appreciate the efforts but, it's just disappointing if not completely avoidable.
I'm afraid I don't have any 5 chips so can't comment regarding them
I'm currently getting a pretty consistent and solid hashrate on Clevermining so fingers crossed it's all working fine - only 4 hours of mining so far though
You'll have to go back and do a bit of digging I believe
It resets the blade after that number of seconds (or something similar but more usefully technically) so stopping any garbage building up. Makes it in to a 24/7 miner
I believe I had that going when I got a nice 5 day run last week so I've put it on again to test
Backup plan is Hashra but Sandor's done such a great job I'll support by using and helping with debug (and donation if the mining continues long enough!)
It resets the blade after that number of seconds (or something similar but more usefully technically) so stopping any garbage building up. Makes it in to a 24/7 miner
I believe I had that going when I got a nice 5 day run last week so I've put it on again to test
Backup plan is Hashra but Sandor's done such a great job I'll support by using and helping with debug (and donation if the mining continues long enough!)
Good show....
I presume it works with the 5 chip pods also?
I haven't had to use any reset commands like that before. I had turned OFF comm port FIFO buffers. They are still OFF.
The original version 2.3.2 I was using that doesn't have stats at the top of the page, was working perfectly before I started upgrading to the latest versions, which have all had a series of bugs either newly created or missed in each 'fixed version' which is completely counter productive. So I wait and watch until I think it's safe to upgrade, then look what happens.... ;( I appreciate the efforts but, it's just disappointing if not completely avoidable.
When I just tried to restart Ver 1.0b it said "failed reading firmware version" and won't start mining.
Had to reset all 26 comm ports manually to get it working again.
There is some bug in ver 1.0b that is causing this to happen.
Please correct it!
Thanks
Had to reset all 26 comm ports manually to get it working again.
There is some bug in ver 1.0b that is causing this to happen.
Please correct it!
Thanks
You'll have to go back and do a bit of digging I believe
It resets the blade after that number of seconds (or something similar but more usefully technically) so stopping any garbage building up. Makes it in to a 24/7 miner
I believe I had that going when I got a nice 5 day run last week so I've put it on again to test
Backup plan is Hashra but Sandor's done such a great job I'll support by using and helping with debug (and donation if the mining continues long enough!)
It resets the blade after that number of seconds (or something similar but more usefully technically) so stopping any garbage building up. Makes it in to a 24/7 miner
I believe I had that going when I got a nice 5 day run last week so I've put it on again to test
Backup plan is Hashra but Sandor's done such a great job I'll support by using and helping with debug (and donation if the mining continues long enough!)
New session started at 0928 my time (it's now 1002 fyi)
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Set --gc3355-timeout=600
Have I been a fool in removing it? I thought an earlier comment said it was no longer needed
In addition - how do I set it, and the --log value in the config file?
EDIT: With 600 I've been getting a low hashrate averaging around 4.5mh/s it looks like, have changed to 300 as I had that in an earlier version and it seemed to work well
What does 'Set --gc3355-timeout=600' command set, exactly? Will it help keep my miners from losing comm?
My miners Ver 1.0b dropped out again during the wee hours. Not the 24/7 operation I was hoping for.
Is it perhaps too sensitive to short comm interruptions?
Anyone else having this problem with 1.0b?
New session started at 0928 my time (it's now 1002 fyi)
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Set --gc3355-timeout=600
Have I been a fool in removing it? I thought an earlier comment said it was no longer needed
In addition - how do I set it, and the --log value in the config file?
EDIT: With 600 I've been getting a low hashrate averaging around 4.5mh/s it looks like, have changed to 300 as I had that in an earlier version and it seemed to work well
New session started at 0928 my time (it's now 1002 fyi)
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Set --gc3355-timeout=600
OK and I've just noticed that the power use has dropped and the blade is not hot any more
cpuminer-gc3355 (v1.0b) - Started: [2014-05-13 09:28:54]
================================================================================
(2s) | 4.98/5.66 MH/s | A: 902 R: 18 HW: 0
Connected to eu.clevermining.com:3333 diff 512 with stratum as user xxxxxx
================================================================================
GSD 0: | 838 MHz | 2528.6/2831.5 KH/s | A: 458 R: 9 H: 0
GSD 1: | 838 MHz | 2452.8/2831.2 KH/s | A: 444 R: 9 H: 0
================================================================================
[2014-05-13 11:11:33.2925] 1: Resetting GC3355 chips
[2014-05-13 11:11:33.3145] 0: Resetting GC3355 chips
[2014-05-13 11:11:33.4125] 1: Dispatching new work to GC3355 cores (0xefd56b12
)
[2014-05-13 11:11:33.4345] 0: Dispatching new work to GC3355 cores (0xefd56b12
)
[2014-05-13 11:12:05.2803] Stratum difficulty set to 512
[2014-05-13 11:12:05.4993] Stratum detected new block
[2014-05-13 11:12:05.4993] New Job_id: b0d3 Diff: 512 Work_id: eff59ec4
[2014-05-13 11:12:05.5143] 1: Resetting GC3355 chips
[2014-05-13 11:12:05.5363] 0: Resetting GC3355 chips
[2014-05-13 11:12:05.6344] 1: Dispatching new work to GC3355 cores (0xeff59ec4
)
[2014-05-13 11:12:05.6564] 0: Dispatching new work to GC3355 cores (0xeff59ec4
)
So lasted 2.5 hours....
EDIT: Have restarted straight off, log saved if it would be of use. I can hear the fan noise change as the power kicks in and it begins actual mining again
cpuminer-gc3355 (v1.0b) - Started: [2014-05-13 09:28:54]
================================================================================
(2s) | 4.98/5.66 MH/s | A: 902 R: 18 HW: 0
Connected to eu.clevermining.com:3333 diff 512 with stratum as user xxxxxx
================================================================================
GSD 0: | 838 MHz | 2528.6/2831.5 KH/s | A: 458 R: 9 H: 0
GSD 1: | 838 MHz | 2452.8/2831.2 KH/s | A: 444 R: 9 H: 0
================================================================================
[2014-05-13 11:11:33.2925] 1: Resetting GC3355 chips
[2014-05-13 11:11:33.3145] 0: Resetting GC3355 chips
[2014-05-13 11:11:33.4125] 1: Dispatching new work to GC3355 cores (0xefd56b12
)
[2014-05-13 11:11:33.4345] 0: Dispatching new work to GC3355 cores (0xefd56b12
)
[2014-05-13 11:12:05.2803] Stratum difficulty set to 512
[2014-05-13 11:12:05.4993] Stratum detected new block
[2014-05-13 11:12:05.4993] New Job_id: b0d3 Diff: 512 Work_id: eff59ec4
[2014-05-13 11:12:05.5143] 1: Resetting GC3355 chips
[2014-05-13 11:12:05.5363] 0: Resetting GC3355 chips
[2014-05-13 11:12:05.6344] 1: Dispatching new work to GC3355 cores (0xeff59ec4
)
[2014-05-13 11:12:05.6564] 0: Dispatching new work to GC3355 cores (0xeff59ec4
)
So lasted 2.5 hours....
EDIT: Have restarted straight off, log saved if it would be of use. I can hear the fan noise change as the power kicks in and it begins actual mining again
New session started at 0928 my time (it's now 1002 fyi)
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
Initial session started, chips got to around 4.7mh/s and then stopped, I have restarted since and realised that overwrote the log but it seemed to be doing the same as above. Not sure what happens maybe it's some kind of loops it gets itself in to
OK so the CPUMiner gave in about 4am looks like
currently looking normal showing:
cpuminer-gc3355 (v1.0b) - Started: [2014-05-12 16:12:48]
================================================================================
(2s) | 4.43/5.67 MH/s | A: 7573 R: 116 HW: 0
Connected to eu.clevermining.com:3333 diff 512 with stratum as user xxxxxx
================================================================================
GSD 0: | 838 MHz | 2206.2/2832.8 KH/s | A: 3779 R: 53 H: 0
GSD 1: | 838 MHz | 2223.0/2832.8 KH/s | A: 3794 R: 63 H: 0
================================================================================
[2014-05-13 08:18:46.7366] 1: Resetting GC3355 chips
[2014-05-13 08:18:46.7496] 0: Resetting GC3355 chips
[2014-05-13 08:18:46.8566] 1: Dispatching new work to GC3355 cores (0xc756f334
)
[2014-05-13 08:18:46.8696] 0: Dispatching new work to GC3355 cores (0xc756f334
)
[2014-05-13 08:19:01.6194] Stratum difficulty set to 512
[2014-05-13 08:19:01.8404] Stratum detected new block
[2014-05-13 08:19:01.8404] New Job_id: b65e Diff: 512 Work_id: c765d325
[2014-05-13 08:19:01.8574] 1: Resetting GC3355 chips
[2014-05-13 08:19:01.8704] 0: Resetting GC3355 chips
[2014-05-13 08:19:01.9774] 1: Dispatching new work to GC3355 cores (0xc765d325
)
[2014-05-13 08:19:01.9904] 0: Dispatching new work to GC3355 cores (0xc765d325
)
So overall appearances seem good but the hashrate at the server is 0
EDIT: Version 1.0b
Looks like it lasted from ~ 16:00 - 04:00
so 12 hours
currently looking normal showing:
cpuminer-gc3355 (v1.0b) - Started: [2014-05-12 16:12:48]
================================================================================
(2s) | 4.43/5.67 MH/s | A: 7573 R: 116 HW: 0
Connected to eu.clevermining.com:3333 diff 512 with stratum as user xxxxxx
================================================================================
GSD 0: | 838 MHz | 2206.2/2832.8 KH/s | A: 3779 R: 53 H: 0
GSD 1: | 838 MHz | 2223.0/2832.8 KH/s | A: 3794 R: 63 H: 0
================================================================================
[2014-05-13 08:18:46.7366] 1: Resetting GC3355 chips
[2014-05-13 08:18:46.7496] 0: Resetting GC3355 chips
[2014-05-13 08:18:46.8566] 1: Dispatching new work to GC3355 cores (0xc756f334
)
[2014-05-13 08:18:46.8696] 0: Dispatching new work to GC3355 cores (0xc756f334
)
[2014-05-13 08:19:01.6194] Stratum difficulty set to 512
[2014-05-13 08:19:01.8404] Stratum detected new block
[2014-05-13 08:19:01.8404] New Job_id: b65e Diff: 512 Work_id: c765d325
[2014-05-13 08:19:01.8574] 1: Resetting GC3355 chips
[2014-05-13 08:19:01.8704] 0: Resetting GC3355 chips
[2014-05-13 08:19:01.9774] 1: Dispatching new work to GC3355 cores (0xc765d325
)
[2014-05-13 08:19:01.9904] 0: Dispatching new work to GC3355 cores (0xc765d325
)
So overall appearances seem good but the hashrate at the server is 0
EDIT: Version 1.0b
Looks like it lasted from ~ 16:00 - 04:00
so 12 hours
Has anyone encountered the following problem?:
I am running 20 grid seeds off a pi running hashra controlla (BFG). These are recently volt-modded 47.7k resistor to go about 510khsh.
Controller shows very little hw rejects at 1200.
PROBLEM: They are showing 510khsh on the controller, but poolside they only report about half that.
When I take I clock it back down to 800 from 1200, controller and poolside are aligned at about 340 per unit.
Thanks in advance for any help.
I am running 20 grid seeds off a pi running hashra controlla (BFG). These are recently volt-modded 47.7k resistor to go about 510khsh.
Controller shows very little hw rejects at 1200.
PROBLEM: They are showing 510khsh on the controller, but poolside they only report about half that.
When I take I clock it back down to 800 from 1200, controller and poolside are aligned at about 340 per unit.
Thanks in advance for any help.
Works fine here.
It works fine on 0.9F
Code:
cpuminer-gc3355 (v0.9f) - Started: [2014-05-12 23:00:49]
===================================================================================
(2s) | 3.39/3.64 MH/s | A: 1143 R: 3 HW: 41
Connected to us-east01.miningrigrentals.com:3333 diff 512 with stratum as user toxic0n.749
HELP GUYS
just got my blade. downloaded cgminer - http://cryptomining-blog.com/1990-updated-cgminer-3-7-2-with-support-for-gridseed-5-chip-and-80-chip-gc3355-asics/
yet when i run it.. it sees just 1 blade. both blades work but it will see just 1.
how do i make it run 2 blades?
runnign it:
cgminer –scrypt –gridseed-options=baud=115200, freq=800, chips=40 –hotplug=0 -o stratum+tcp://eu.multipool.us:7777 -u XXXX -p x
just got my blade. downloaded cgminer - http://cryptomining-blog.com/1990-updated-cgminer-3-7-2-with-support-for-gridseed-5-chip-and-80-chip-gc3355-asics/
yet when i run it.. it sees just 1 blade. both blades work but it will see just 1.
how do i make it run 2 blades?
runnign it:
cgminer –scrypt –gridseed-options=baud=115200, freq=800, chips=40 –hotplug=0 -o stratum+tcp://eu.multipool.us:7777 -u XXXX -p x
Just a guess and might only be part of your problem...you didn't put spaces after your commas.
I added them. This might be all you need to get it/them hashing.
I remember something about hotplug=5 or 40 or some shyt..
I'm a cpuminer head, not a cgminer head..
Let me know if I helped any
Edit,,, ahh, yep, chips=ruffles
Happy may be right, chips=80 sounds like a good guess..but there are cgminer experts out here who know exactly what is wrong and what to do to get you running. HELP GUYS
just got my blade. downloaded cgminer - http://cryptomining-blog.com/1990-updated-cgminer-3-7-2-with-support-for-gridseed-5-chip-and-80-chip-gc3355-asics/
yet when i run it.. it sees just 1 blade. both blades work but it will see just 1.
how do i make it run 2 blades?
runnign it:
cgminer –scrypt –gridseed-options=baud=115200,freq=800,chips=40 –hotplug=0 -o stratum+tcp://eu.multipool.us:7777 -u XXXX -p x
just got my blade. downloaded cgminer - http://cryptomining-blog.com/1990-updated-cgminer-3-7-2-with-support-for-gridseed-5-chip-and-80-chip-gc3355-asics/
yet when i run it.. it sees just 1 blade. both blades work but it will see just 1.
how do i make it run 2 blades?
runnign it:
cgminer –scrypt –gridseed-options=baud=115200,freq=800,chips=40 –hotplug=0 -o stratum+tcp://eu.multipool.us:7777 -u XXXX -p x
Just a guess: your blade is 80 chips but you've specified 40 chips in the cgminer command line. Have you tried setting it to 80 chips?
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
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
Works fine here.
To expand on this a bit, for me on windows and a single gridseed the miner won't actually connect to a pool. It says it's connected, resetting chips, sending work, ect ect, but nothing is happening at the pool's end. I tried a few different pools and even cgminer to make sure I wasn't losing my mind. I've only altered the conf.json for my port (1) and pool settings.
HELP GUYS
just got my blade. downloaded cgminer - http://cryptomining-blog.com/1990-updated-cgminer-3-7-2-with-support-for-gridseed-5-chip-and-80-chip-gc3355-asics/
yet when i run it.. it sees just 1 blade. both blades work but it will see just 1.
how do i make it run 2 blades?
runnign it:
cgminer –scrypt –gridseed-options=baud=115200,freq=800,chips=40 –hotplug=0 -o stratum+tcp://eu.multipool.us:7777 -u XXXX -p x
just got my blade. downloaded cgminer - http://cryptomining-blog.com/1990-updated-cgminer-3-7-2-with-support-for-gridseed-5-chip-and-80-chip-gc3355-asics/
yet when i run it.. it sees just 1 blade. both blades work but it will see just 1.
how do i make it run 2 blades?
runnign it:
cgminer –scrypt –gridseed-options=baud=115200,freq=800,chips=40 –hotplug=0 -o stratum+tcp://eu.multipool.us:7777 -u XXXX -p x
Jump to: