Pages:
Author

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

sr. member
Activity: 378
Merit: 250
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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

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.
hero member
Activity: 616
Merit: 500
I don't think --gc3355-timeout is needed anymore. I think I have fixed what is causing the GC3355 to stop hashing, if you send work and reset too fast, it will corrupt the registers. Solved it by waiting a minimum of 100ms before and 100ms after resetting.
hero member
Activity: 616
Merit: 500
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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

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.
member
Activity: 86
Merit: 10
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?
sr. member
Activity: 378
Merit: 250
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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

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....
hero member
Activity: 616
Merit: 500
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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

here's another fairly simple question, I'm sure...

How do you update to a newer version without wiping everything out and installing from scratch? I thought I read something about a command that uses 'pull'. I am still learning, but catching on...

Thanks again...

Execute in cpuminer-gc3355 directory:
Code:
git fetch
git reset --hard origin/master
git pull origin/master
newbie
Activity: 54
Merit: 0
here's another fairly simple question, I'm sure...

How do you update to a newer version without wiping everything out and installing from scratch? I thought I read something about a command that uses 'pull'. I am still learning, but catching on...

Thanks again...
sr. member
Activity: 378
Merit: 250
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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
hero member
Activity: 616
Merit: 500
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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.
sr. member
Activity: 378
Merit: 250
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley

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.
hero member
Activity: 616
Merit: 500
Nicehash is fixed now, so anyone who wants to mine there, grab the latest binary and go ahead. Smiley
sr. member
Activity: 378
Merit: 250
Like Eurovision is not manipulated, you really think it's the people voting  Cheesy

Ok I stop now, this has nothing to do in the thread here  Kiss


Sandor I figured out the overheating problem I had with a previous version

My internet would have a few down minutes at night and CPUminer would freeze.

When it stops working the units overheat. I have done a simulation by only plugging in the units and stopping the internet and they star overheating only in this case.

Have not had any issue with latest version.

Damn! He got me again.....  Roll Eyes
sr. member
Activity: 308
Merit: 250
Like Eurovision is not manipulated, you really think it's the people voting  Cheesy

Ok I stop now, this has nothing to do in the thread here  Kiss


Sandor I figured out the overheating problem I had with a previous version

My internet would have a few down minutes at night and CPUminer would freeze.

When it stops working the units overheat. I have done a simulation by only plugging in the units and stopping the internet and they star overheating only in this case.

Have not had any issue with latest version.
member
Activity: 86
Merit: 10
I'm getting the lowest ever rejects with this evenings build! Smiley

Over the last 90mins:
A:3467  R:5  H:3  (0.14% rejects)

[SPOILER]p.s. congrats Austria on winning the Eurovision![/SPOILER]

I'm sorry but that "thing" singing for Austria should not be allowed. A gay ok, THAT no..

The millions of people who voted think differently. Lol going way o/t now sorry thread.
sr. member
Activity: 308
Merit: 250
I'm getting the lowest ever rejects with this evenings build! Smiley

Over the last 90mins:
A:3467  R:5  H:3  (0.14% rejects)

[SPOILER]p.s. congrats Austria on winning the Eurovision![/SPOILER]

I'm sorry but that "thing" singing for Austria should not be allowed. A gay ok, THAT no..
member
Activity: 86
Merit: 10
I'm getting the lowest ever rejects with this evenings build! Smiley

Over the last 90mins:
A:3467  R:5  H:3  (0.14% rejects)

[SPOILER]p.s. congrats Austria on winning the Eurovision![/SPOILER]
sr. member
Activity: 378
Merit: 250
Sandor111,

Just upgraded to the latest version and I get an error can not find "libjansson-4.dll"

thx



Yo Sandor, I'll take this one, if you don't mind.
I'm using ver1.0 as of this morning. 3 of my 26 miners are showing comparatively very low accepts compared to the rest since 1200 hrs today. Approximately 100 accepts less than the rest.
Their stats haven't changed in over the last 15 or so minutes.
one pod says 73.5/477KHs A:72 R:0 H:1
other...        168/375KHs   A:80 R:0 H:9
other...        123/488KHs   A:71 R:0 H:1

Before I go tearing into checking my configs, drivers, hardware, what do you think it may be?
Tanks and nicely done on handling A R H issues.  Grin

tc61,
It's on your hard drive in the previous versions's folder or perhaps in your system file.
I run mine in the same folder as the main program. Works fine.
Search for it, find it, copy and paste it into the appropriate directory and off you go!
Happy hashing, again  Grin

Edit, Sandor -
now it's lost connection to stratum.....retries aren't working.....guess I need to throw in a pool switcher now...darn it! I wonder of those pods have low counts because they lost connection to the server earlier without indicating it.
Going back to 2.3.2 - old faithful until this is solved, I recon.
Why does version 2.3.2 never have this problem?
Been mining straight 24/7 for days now with it, upgrade to Ver1.0 and well lookee here...surprise!  Roll Eyes

Edit edit...Sandor, sorry, mate, it's the pool! frikkin went into maintenance mode without notifying anyone!
But please answer up on the rest of it please.
sr. member
Activity: 378
Merit: 250
Sandor111,

Just upgraded to the latest version and I get an error can not find "libjansson-4.dll"

thx



Yo Sandor, I'll take this one, if you don't mind.
I'm using ver1.0 as of this morning. 3 of my 26 miners are showing comparatively very low accepts compared to the rest since 1200 hrs today. Approximately 100 accepts less than the rest.
Their stats haven't changed in over the last 15 or so minutes.
one pod says 73.5/477KHs A:72 R:0 H:1
other...        168/375KHs   A:80 R:0 H:9
other...        123/488KHs   A:71 R:0 H:1

Before I go tearing into checking my configs, drivers, hardware, what do you think it may be?
Tanks and nicely done on handling A R H issues.  Grin

tc61,
It's on your hard drive in the previous versions's folder or perhaps in your system file.
I run mine in the same folder as the main program. Works fine.
Search for it, find it, copy and paste it into the appropriate directory and off you go!
Happy hashing, again  Grin
member
Activity: 93
Merit: 10
ok... then its something other....... maybe debug mode.. i test it next day...
hero member
Activity: 616
Merit: 500
Copy the missing file from some other  versions from cgminer or bfgminer over, it works.

2. Setting the parameter --gc3355-timeout=360 makes my blade slow and i can hear the fan wobling, every second i get the messege "0: reseting gs3355 chips"
without my blade gets stuck after some time...

Resetting GC3355 chips has nothing to do with --gc3355-timeout, it is simply clearing the previous work in the chips to make room for new work, standard procedure.
Pages:
Jump to: