Pages:
Author

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

hero member
Activity: 616
Merit: 500
I woke up this morning and found the Blade miner had stopped again during the night
using the latest software. I did turn OFF the FIFO buffers and set the baud speed to
115200 for ports 3 & 4 which are being used. Anything else I can check?

Its not the Blade as if I use BFGminer it works for days on end but lower hash power.
The software has stopped working on 3 different pools randomly and the laptop is hard
wired to the network console.
 
Here is a picture of the software as it was this morning on the Mining Pool Co.



Sadly I'm facing the same, have two blades running on-location right now and I get at least one half dropping off every ~6 hours.  Thought it was a power issue so I moved them to different locations but still the same.  Already abandoned both BFG and CG miners as CPUMiner has been the most stable, but regardless cannot keep the blades running without issue.  A few times I've seen the LIBUSB errors pop up, but generally by the time I see the dropoff I only see a screen like the above with a few stratum messages, a few new jobs listed, but nothing accepted and the rate moving down.

Trying a different usb hub this morning, but overall getting very frustrated at keeping these online.  Tuned units of any other sort haven't kept me this involved in tuning/restarting/etc. in a long time. :/

It could be a Windows thing, did any if you try a different platform?

I gave up on Windows + gridseed a long time ago. Smiley  I'm on rpi right now but having some of the same issues, cannot seem to keep my two blades + three 5-chips running steadily for any duration.  Have tried different power configurations, different usb layouts, hell, different areas of the room, different frequencies, using 1 CGM instance vs. 7 CPUM instances, nada, still can't go ~12 hours without needing to reset a device or do a reboot to bring a few back.  Previously just restarting CGM/CPUM on the device worked a couple of times but eventually needs to reboot.

Great devices, just frustrating right now.

Do you mind posting the full log (with --debug), till the point when the Blades stop hashing? That could help identify the cause.
sr. member
Activity: 420
Merit: 250
I woke up this morning and found the Blade miner had stopped again during the night
using the latest software. I did turn OFF the FIFO buffers and set the baud speed to
115200 for ports 3 & 4 which are being used. Anything else I can check?

Its not the Blade as if I use BFGminer it works for days on end but lower hash power.
The software has stopped working on 3 different pools randomly and the laptop is hard
wired to the network console.
 
Here is a picture of the software as it was this morning on the Mining Pool Co.



Sadly I'm facing the same, have two blades running on-location right now and I get at least one half dropping off every ~6 hours.  Thought it was a power issue so I moved them to different locations but still the same.  Already abandoned both BFG and CG miners as CPUMiner has been the most stable, but regardless cannot keep the blades running without issue.  A few times I've seen the LIBUSB errors pop up, but generally by the time I see the dropoff I only see a screen like the above with a few stratum messages, a few new jobs listed, but nothing accepted and the rate moving down.

Trying a different usb hub this morning, but overall getting very frustrated at keeping these online.  Tuned units of any other sort haven't kept me this involved in tuning/restarting/etc. in a long time. :/

It could be a Windows thing, did any if you try a different platform?

I gave up on Windows + gridseed a long time ago. Smiley  I'm on rpi right now but having some of the same issues, cannot seem to keep my two blades + three 5-chips running steadily for any duration.  Have tried different power configurations, different usb layouts, hell, different areas of the room, different frequencies, using 1 CGM instance vs. 7 CPUM instances, nada, still can't go ~12 hours without needing to reset a device or do a reboot to bring a few back.  Previously just restarting CGM/CPUM on the device worked a couple of times but eventually needs to reboot.

Great devices, just frustrating right now.  Sucks too cause I have decent USB3 hubs but the devices won't go near 'em and I don't feel like buying pricier usb2 hubs just to test if that is the issue.  Running 2 devices (with plug-in power supplies) per 4-port powered hub that used to easily run 4 AsicMiner or 3 Ant sticks just fine, so I doubt it is the hubs.  Just tired of hardware management. Smiley
hero member
Activity: 616
Merit: 500
I woke up this morning and found the Blade miner had stopped again during the night
using the latest software. I did turn OFF the FIFO buffers and set the baud speed to
115200 for ports 3 & 4 which are being used. Anything else I can check?

Its not the Blade as if I use BFGminer it works for days on end but lower hash power.
The software has stopped working on 3 different pools randomly and the laptop is hard
wired to the network console.
 
Here is a picture of the software as it was this morning on the Mining Pool Co.



Sadly I'm facing the same, have two blades running on-location right now and I get at least one half dropping off every ~6 hours.  Thought it was a power issue so I moved them to different locations but still the same.  Already abandoned both BFG and CG miners as CPUMiner has been the most stable, but regardless cannot keep the blades running without issue.  A few times I've seen the LIBUSB errors pop up, but generally by the time I see the dropoff I only see a screen like the above with a few stratum messages, a few new jobs listed, but nothing accepted and the rate moving down.

Trying a different usb hub this morning, but overall getting very frustrated at keeping these online.  Tuned units of any other sort haven't kept me this involved in tuning/restarting/etc. in a long time. :/

It could be a Windows thing, did any if you try a different platform?
sr. member
Activity: 420
Merit: 250
I woke up this morning and found the Blade miner had stopped again during the night
using the latest software. I did turn OFF the FIFO buffers and set the baud speed to
115200 for ports 3 & 4 which are being used. Anything else I can check?

Its not the Blade as if I use BFGminer it works for days on end but lower hash power.
The software has stopped working on 3 different pools randomly and the laptop is hard
wired to the network console.
 
Here is a picture of the software as it was this morning on the Mining Pool Co.



Sadly I'm facing the same, have two blades running on-location right now and I get at least one half dropping off every ~6 hours.  Thought it was a power issue so I moved them to different locations but still the same.  Already abandoned both BFG and CG miners as CPUMiner has been the most stable, but regardless cannot keep the blades running without issue.  A few times I've seen the LIBUSB errors pop up, but generally by the time I see the dropoff I only see a screen like the above with a few stratum messages, a few new jobs listed, but nothing accepted and the rate moving down.

Trying a different usb hub this morning, but overall getting very frustrated at keeping these online.  Tuned units of any other sort haven't kept me this involved in tuning/restarting/etc. in a long time. :/
sr. member
Activity: 346
Merit: 260
I woke up this morning and found the Blade miner had stopped again during the night
using the latest software. I did turn OFF the FIFO buffers and set the baud speed to
115200 for ports 3 & 4 which are being used. Anything else I can check?

Its not the Blade as if I use BFGminer it works for days on end but lower hash power.
The software has stopped working on 3 different pools randomly and the laptop is hard
wired to the network console.
 
Here is a picture of the software as it was this morning on the Mining Pool Co.


hero member
Activity: 546
Merit: 500
d looks fine to me. pool shows my efficency of 99.8%, while pool average is 98,65%
member
Activity: 86
Merit: 10
I'm getting a lot of rejects with cpuminer 0.9d. Didn't have this problem with 0.9c, I'm certain. Just me?

e.g. with 0.9c I was pleasantly surprised to see the poolside reject rate fall to a new all-time low of 0.38%. After switching to 0.9d, its gone up to 5.27% and climbing, and I can see reports of rejects locally a few times every minute. So I've gone back to 0.9c for now. Rejects such as:

"DEBUG: reject reason: unknown-work"
"DEBUG: reject reason: high hash"
sr. member
Activity: 378
Merit: 250
Can someone compile and post the latest cpuminer from sandor11 for windows?

Thanks!

Yep, you can always find the latest updates via a link in Sandor111's signature, too.....
sr. member
Activity: 308
Merit: 250
Can someone compile and post the latest cpuminer from sandor11 for windows?

Thanks!

it's already been done

https://www.dropbox.com/s/ttqa9p851siz8oi/minerd-gc3355.zip
sr. member
Activity: 423
Merit: 250
Can someone compile and post the latest cpuminer from sandor11 for windows?

Thanks!
sr. member
Activity: 378
Merit: 250
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

I heard the  volt mod on the blade can cause issues with the regs on the board overheating
due to no heat sinks on them like the round miners? Has anyone on here cranked a blade
up to see what the max Mhs is with a 39ohm or higher resistor?

Ahh! You don't know what you've been missing  Grin
Have a looksee! >>>> https://bitcointalksearch.org/topic/gridseed-g-blade-overclocking-7mhs-improvements-and-repair-576784 < edit....DOH!
Enjoy!
Wolfey2014
sr. member
Activity: 346
Merit: 260
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

I heard the  volt mod on the blade can cause issues with the regs on the board overheating
due to no heat sinks on them like the round miners? Has anyone on here cranked a blade
up to see what the max Mhs is with a 39ohm or higher resistor?
sr. member
Activity: 346
Merit: 260
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still is 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

Real random, 1 time was only after about 50 min of use on a pool.
The other time was after 5 hours on a another pool.
I just turned OFF the FIFO buffers on two Com ports, I am running on a Win 7 Acer laptop.
Should the Com ports "Bits per Second" is at 9600, should I turn this up higher on each port.

Reset baud to 115200 - Uncheck 'Use FIFO buffers' = OFF....
'OK' out of it and repeat for each associated comm port.
This may very well solve your intermittent comm problem with the pool servers as csmflynt3 correctly recognizes.

Great, done.
Will see what happens tonight.
Thanks Wolfey2014!
sr. member
Activity: 378
Merit: 250
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still is 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

Real random, 1 time was only after about 50 min of use on a pool.
The other time was after 5 hours on a another pool.
I just turned OFF the FIFO buffers on two Com ports, I am running on a Win 7 Acer laptop.
Should the Com ports "Bits per Second" is at 9600, should I turn this up higher on each port.

Reset baud to 115200 - Uncheck 'Use FIFO buffers' = OFF....
'OK' out of it and repeat for each associated comm port.
This may very well solve your intermittent comm problem with the pool servers as csmflynt3 correctly recognizes.
sr. member
Activity: 346
Merit: 260
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still is 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem

Real random, 1 time was only after about 50 min of use on a pool.
The other time was after 5 hours on a another pool.
I just turned OFF the FIFO buffers on two Com ports, I am running on a Win 7 Acer laptop.
Should the Com ports "Bits per Second" is at 9600, should I turn this up higher on each port.
member
Activity: 86
Merit: 10
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!

That sounds more like the connection to the pool is the problem
sr. member
Activity: 378
Merit: 250
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?

Yes, a common problem that has been solved in various ways including turning off comm port FIFO buffers for every comm port associated with your rig.
Lots of data on it in this thread and the volt mod thread.
Search FIFO Buffers to learn more.
Good luck!
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
I'm using version 0.9d, only two instances instead of 17. (Only because they are on different pools.) But reduced to one worker instead of individual workers.
sr. member
Activity: 346
Merit: 260
Running the software I have had my Blade stop running a few times on two different pools.
Its just says "New job: dxxx Diff:32" a few times then "Stratum connection timed out"?
The hash rate still reads 5.2Mhs but there is no activity, Anyone seen this before?
Pages:
Jump to: