Pages:
Author

Topic: Official FutureBit Moonlander 2 Driver and Support Thread - page 94. (Read 71725 times)

sr. member
Activity: 952
Merit: 339
invest trade and gamble wisely
Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.

how is one a problem? you can usually tell if one jammed up by looking at the red light..

I got a couple miners that will slow down to 2 MH, so the red light will still blink. 

I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times. 

I'm mining on litecoinpool.org.  The sticks will mine just fine for a few hours then they'll slow down to 2MH or so.

Well, then I was wrong Sad
I'm now 18 hours without stop on litecoinpool.org (would be more but there was electricity outage).
newbie
Activity: 42
Merit: 0
Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.

how is one a problem? you can usually tell if one jammed up by looking at the red light..

I got a couple miners that will slow down to 2 MH, so the red light will still blink. 

I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times. 

I'm mining on litecoinpool.org.  The sticks will mine just fine for a few hours then they'll slow down to 2MH or so.

I use litecoinpool.org and it seems ok with me - Been running for nearly a week with no issues (getting a constant 4.44Mh/s) and this is my setup:
https://bitcointalksearch.org/topic/m.25653813

What setup do you have? hub / os / etc ?

newbie
Activity: 32
Merit: 0
Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.

how is one a problem? you can usually tell if one jammed up by looking at the red light..

I got a couple miners that will slow down to 2 MH, so the red light will still blink. 

I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times. 

I'm mining on litecoinpool.org.  The sticks will mine just fine for a few hours then they'll slow down to 2MH or so.
sr. member
Activity: 952
Merit: 339
invest trade and gamble wisely
Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.

how is one a problem? you can usually tell if one jammed up by looking at the red light..

I got a couple miners that will slow down to 2 MH, so the red light will still blink. 

I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times. 
newbie
Activity: 32
Merit: 0
Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.

how is one a problem? you can usually tell if one jammed up by looking at the red light..

I got a couple miners that will slow down to 2 MH, so the red light will still blink. 
full member
Activity: 658
Merit: 118
I'm having trouble trying to solo mine a small coin, nyancoin, directly from the wallet. It seems to start up ok, but immediately after a new block is found in the network, one or two minutes, then the miner is declared sick by bfgminer and presumably stops working (I let it run for a day or so in which time should have found a bunch of blocks)

Any ideas for a fix?

I dont believe bfgminer has support for scrypt solo-mining. (unless your mining off a solo pool directly).

I was able to solo mine scrypt (a coin called linx) using the Windows version of your build. Just used http://:rpcport and the rpcuser and pass I setup in the coin's conf file.

Code:
bfgminer.exe --scrypt -o http://localhost:4321  -u  -p   -S MLD:all --set MLD:clock=756
legendary
Activity: 2174
Merit: 1401
I'm having trouble trying to solo mine a small coin, nyancoin, directly from the wallet. It seems to start up ok, but immediately after a new block is found in the network, one or two minutes, then the miner is declared sick by bfgminer and presumably stops working (I let it run for a day or so in which time should have found a bunch of blocks)

Any ideas for a fix?

I dont believe bfgminer has support for scrypt solo-mining. (unless your mining off a solo pool directly).
legendary
Activity: 2174
Merit: 1401
@jstefanop

 Why are we unable to setup failover pools?

did you try #skipcbcheck on all of the urls?

yes if I add a failover pool they stop mining after a few minutes

Basic bfgminer features should work normally, since this is just a direct build off luke-jr's main branch with my driver code added. Have no idea why it would not be working.
legendary
Activity: 3136
Merit: 1116
I'm having trouble trying to solo mine a small coin, nyancoin, directly from the wallet. It seems to start up ok, but immediately after a new block is found in the network, one or two minutes, then the miner is declared sick by bfgminer and presumably stops working (I let it run for a day or so in which time should have found a bunch of blocks)

Any ideas for a fix?
newbie
Activity: 24
Merit: 0

wondering what the
Code:
pause
exit
does

Pause - Puts a message on the screen saying "Press any key to continue..." and halts the program until a key is pressed. If something crashes in one of the previous lines, this helps you read what it is. Otherwise, it'd just close and you wouldn't know what to do.

Exit - Closes the program. Makes it stop running and go away.

aah yes, thanks! is there also a command to have it restart when the hashrate goes down or there are too many stales/problems?
full member
Activity: 658
Merit: 118

wondering what the
Code:
pause
exit
does

Pause - Puts a message on the screen saying "Press any key to continue..." and halts the program until a key is pressed. If something crashes in one of the previous lines, this helps you read what it is. Otherwise, it'd just close and you wouldn't know what to do.

Exit - Closes the program. Makes it stop running and go away.
newbie
Activity: 24
Merit: 0
I have found a fix for most users that are experiencing issues with the miners just stopping!

 if you use the conf file and you add more than 1 pool the miners will all stop when network difficulty information is gathered from the other pools.

 Fix: set 1 pool in your conf and remove the pool from the cmd/bat file, if you leave the same pool in the cmd/bat file it still treats it like having 2 pools.

my bat file:

bfgminer.exe --scrypt -S MLD:all
pause
exit


hope that helps!

I'm still newer to this...what exactly did you put in your .conf file? Can you post or PM me an example? TIA

wondering what the
Code:
pause
exit
does
hero member
Activity: 630
Merit: 506
@jstefanop

 Why are we unable to setup failover pools?

did you try #skipcbcheck on all of the urls?

yes if I add a failover pool they stop mining after a few minutes
are your failover pools all the same coin?

i have 3 pools in mine and they dont seem to be affecting anything.

Ok I will try that
legendary
Activity: 1736
Merit: 1006
@jstefanop

 Why are we unable to setup failover pools?

did you try #skipcbcheck on all of the urls?

yes if I add a failover pool they stop mining after a few minutes
are your failover pools all the same coin?

i have 3 pools in mine and they dont seem to be affecting anything.
hero member
Activity: 630
Merit: 506
@jstefanop

 Why are we unable to setup failover pools?

did you try #skipcbcheck on all of the urls?

yes if I add a failover pool they stop mining after a few minutes
newbie
Activity: 3
Merit: 0
I have found a fix for most users that are experiencing issues with the miners just stopping!

 if you use the conf file and you add more than 1 pool the miners will all stop when network difficulty information is gathered from the other pools.

 Fix: set 1 pool in your conf and remove the pool from the cmd/bat file, if you leave the same pool in the cmd/bat file it still treats it like having 2 pools.

my bat file:

bfgminer.exe --scrypt -S MLD:all
pause
exit


hope that helps!

I'm still newer to this...what exactly did you put in your .conf file? Can you post or PM me an example? TIA
legendary
Activity: 1736
Merit: 1006
@jstefanop

 Why are we unable to setup failover pools?

did you try #skipcbcheck on all of the urls?
hero member
Activity: 630
Merit: 506
@jstefanop

 Why are we unable to setup failover pools?
tgz
newbie
Activity: 26
Merit: 0

Thanks dem0nlord, I'll load screen and try that out today...


Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.
Not sure what the problems are but if one miner drops in hash value it will be the one with reduced rate of "red-flashing" LED.
This will be hard if the hashing is only a slight amount lower or your pool/diff has them all blinking slow anyway.

legendary
Activity: 1736
Merit: 1006
Has anyone figured out a good way to single out a problematic miner in an array of miners?  I rather not have to run them all individually to find the problem child.

how is one a problem? you can usually tell if one jammed up by looking at the red light..
Pages:
Jump to: