Bitcoin Forum
November 18, 2017, 04:56:28 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 [2046] 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 ... 2138 »
  Print  
Author Topic: Swedish ASIC miner company kncminer.com  (Read 3006777 times)
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 01:08:45 AM
 #40901

TXSteve, so the way these things work is every loop of the monitoring script it scans how much current is going through the DCDC's and if under 5 amps is going through it basically incriments the value /var/run/dieXX
once /var/run/dieXX reaches over the threshold variable it takes action to reset the die. So...basically if the ASICs dont have work due to a shitty pool configuration like when renting... that /var/run/dieXX will get incrimented, if the pool is shitty enough and it increments over threshold ... no matter what... one of the reset actions will be taken.
Im not exactly sure whats a good way to recode this so it can differentiate between possible pool comm issues vs an actual die needing reset.
I could impliment maybe 2 thresholds, one being a lower one for the pool issues then another maybe being double of the first one?Huh and if thats reached then it performs a hard reset.
I dont know, what do you think?
Or anyone else care to chime in?
Im just kinda doing a ton of trial and error here LOL!


How this all was originally(the way KNC set it up) was on threshold and if that threshold was hit it just performed a soft reset for an eternity.



In the short term, I was thinking, pool issues aside. Now since we have this other stupid mode of failure where the waas command succeeds but it really doesnt bring the die back to life .... I could do another loop which would attempt soft resets up to say 5x sleep after each attempt, run the dcdc function to see if current is over 5A and each incriment its not, of course increase /var/run/dieXX ... then inside that same loop if /var/run/dieXX goes over the threhold then start a hard reset. I think that would solve the issue I ran into just today =)

how about this? An "auto on/auto off" button & a "manual reset" button. On problematic rigs we turn auto reset off, & use manual reset as needed. It still beats physically powering down the rig, and restarting it ...just a thought

I only have one die with these flaky soft resets, so it may not be a huge overall problem

Trying to keep this as automated as possible and least user invasive as possible =), its hard for me to code custom stuff for webgui since I dont have much experience w/ all the crazy shit they have going on involving it. LOL

this v.93 seems to be running pretty good, even the flaky soft reset die seems to have stabilized after several hard resets

when bfgminer randomly shuts down I attribute that to hard resets



Yeahp, bfgminer cant be running in order for a proper dcdc power down / up ... dont know if it has to do w/ bus traffic or what, but seems the dcdc power down / up does something but bfgminer will continually ignore them.

If those loops are too big a pain the neck to implement I wouldn't worry about them
A blockchain platform for effective freelancing
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1510980988
Hero Member
*
Offline Offline

Posts: 1510980988

View Profile Personal Message (Offline)

Ignore
1510980988
Reply with quote  #2

1510980988
Report to moderator
GenTarkin
Legendary
*
Offline Offline

Activity: 2170


View Profile
August 13, 2015, 03:34:23 AM
 #40902

TXSteve, so the way these things work is every loop of the monitoring script it scans how much current is going through the DCDC's and if under 5 amps is going through it basically incriments the value /var/run/dieXX
once /var/run/dieXX reaches over the threshold variable it takes action to reset the die. So...basically if the ASICs dont have work due to a shitty pool configuration like when renting... that /var/run/dieXX will get incrimented, if the pool is shitty enough and it increments over threshold ... no matter what... one of the reset actions will be taken.
Im not exactly sure whats a good way to recode this so it can differentiate between possible pool comm issues vs an actual die needing reset.
I could impliment maybe 2 thresholds, one being a lower one for the pool issues then another maybe being double of the first one?Huh and if thats reached then it performs a hard reset.
I dont know, what do you think?
Or anyone else care to chime in?
Im just kinda doing a ton of trial and error here LOL!


How this all was originally(the way KNC set it up) was on threshold and if that threshold was hit it just performed a soft reset for an eternity.



In the short term, I was thinking, pool issues aside. Now since we have this other stupid mode of failure where the waas command succeeds but it really doesnt bring the die back to life .... I could do another loop which would attempt soft resets up to say 5x sleep after each attempt, run the dcdc function to see if current is over 5A and each incriment its not, of course increase /var/run/dieXX ... then inside that same loop if /var/run/dieXX goes over the threhold then start a hard reset. I think that would solve the issue I ran into just today =)

how about this? An "auto on/auto off" button & a "manual reset" button. On problematic rigs we turn auto reset off, & use manual reset as needed. It still beats physically powering down the rig, and restarting it ...just a thought

I only have one die with these flaky soft resets, so it may not be a huge overall problem

Trying to keep this as automated as possible and least user invasive as possible =), its hard for me to code custom stuff for webgui since I dont have much experience w/ all the crazy shit they have going on involving it. LOL

this v.93 seems to be running pretty good, even the flaky soft reset die seems to have stabilized after several hard resets

when bfgminer randomly shuts down I attribute that to hard resets



Yeahp, bfgminer cant be running in order for a proper dcdc power down / up ... dont know if it has to do w/ bus traffic or what, but seems the dcdc power down / up does something but bfgminer will continually ignore them.

If those loops are too big a pain the neck to implement I wouldn't worry about them

Well, I rewrote the soft / hard reset code =)
Basically, once it detects a die in error via /var/run/dieXX
It calls the reset die function, it first attempts a soft reset... if that fails right off the bat via waas -s failing then it performs a hard reset. (waas -s shouldnt fail because of pool comm errors)
If waas -s succeeds then it calls bfgminer to perform its internal die reconfiguration update
Then script waits 30 seconds and measures the current output of die in question
If either of the DCDC's are below current treshold then it incriments error count
It will loop through the soft die resets up to 10 times, if it fails 10x then it performs a hard reset.
So, it gives the die roughly 5-6 mins to "work" ... meaning have current flowing through it greater than the threshold, via soft resets.
If that fails it hard resets.

What ya think?
I updated github w/ the changes if you wanna test.

I can say it seems the soft reset logic is working. I have yet to be able to see a hard reset take place, I have to actually wait till my unit acts up to confirm hard reset functionality LOL!

GenTarkin's MOD Kncminer Titan custom firmware! v1.0.4! <--- CLICK HERE
Donations: bitcoin- 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At || litecoin- LYXrLis3ik6TRn8tdvzAyJ264DRvwYVeEw
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 10:14:10 AM
 #40903

cool, I'll check it out
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 11:38:38 AM
 #40904

cool, I'll check it out

It looks good, however I did see one small issue. I raised the MHz on the flaky soft reset die to stress it and bfgminer wouldn't load. It got stuck in a hard reset loop when the die failed. I was able to change the advanced setting to get out of the loop, but maybe need to delay the hard reset routine for a few min to let bfgminer load when there is a bad die that's overclocked or not turned off

ok I just noticed something ... If I get a bunch of "Got nonce for unknown work in slot xx" errors scrolling then it goes straight to hard reset ... (this may tie in with the bgfminer not loading loop).

other than that everything is working fine

I'll get another cup of coffee & watch this for awhile, see if I can notice anything else that might help you troubleshoot it

...... ok this time the "Got nonce for unknown work in slot xx" errors didn't trigger an instant hard reset and it reset successfully, must have been coincidence earlier
helmax
Sr. Member
****
Offline Offline

Activity: 441



View Profile
August 13, 2015, 01:03:07 PM
 #40905

guys some help

my controller only say STOPPED status page
cgminer dont start

neptune machine
how i can fix?
or anyone have SD FULL image for put in SDcard

already test recovery sd card but dont work

any help please?


kncminer say already dont have warranty

looking job
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 01:10:42 PM
 #40906

cool, I'll check it out

It looks good, however I did see one small issue. I raised the MHz on the flaky soft reset die to stress it and bfgminer wouldn't load. It got stuck in a hard reset loop when the die failed. I was able to change the advanced setting to get out of the loop, but maybe need to delay the hard reset routine for a few min to let bfgminer load when there is a bad die that's overclocked or not turned off

ok I just noticed something ... If I get a bunch of "Got nonce for unknown work in slot xx" errors scrolling then it goes straight to hard reset ... (this may tie in with the bgfminer not loading loop).

other than that everything is working fine

I'll get another cup of coffee & watch this for awhile, see if I can notice anything else that might help you troubleshoot it

...... ok this time the "Got nonce for unknown work in slot xx" errors didn't trigger an instant hard reset and it reset successfully, must have been coincidence earlier

ok looks like just getting random hard resets instead of running thru the soft reset loop. Most of the time it runs thru the loop. If I disable the flaky die there aren't any problems

btw, that die is set at 150 MHz so it has less amp draw
GenTarkin
Legendary
*
Offline Offline

Activity: 2170


View Profile
August 13, 2015, 01:24:28 PM
 #40907

cool, I'll check it out

It looks good, however I did see one small issue. I raised the MHz on the flaky soft reset die to stress it and bfgminer wouldn't load. It got stuck in a hard reset loop when the die failed. I was able to change the advanced setting to get out of the loop, but maybe need to delay the hard reset routine for a few min to let bfgminer load when there is a bad die that's overclocked or not turned off

ok I just noticed something ... If I get a bunch of "Got nonce for unknown work in slot xx" errors scrolling then it goes straight to hard reset ... (this may tie in with the bgfminer not loading loop).

other than that everything is working fine

I'll get another cup of coffee & watch this for awhile, see if I can notice anything else that might help you troubleshoot it

...... ok this time the "Got nonce for unknown work in slot xx" errors didn't trigger an instant hard reset and it reset successfully, must have been coincidence earlier

The hard reset most ikely took place because that die was probably not able to be reconfigured via waas -s and that command failed, whenver that command fails it will do a hard reset. That command should never return failed. If it does that means soft resets wont bring it back.
The 2nd time it may have just been that the soft reset worked for it =)

As far as ur first issue ... again, if u raised the die to a mhz where it wont even acknowledge waas -s commands or it returns failed it will do a hard reset no matter what.
Can you post the contents of ur log file where this all took place so I can guauge to see if my guesses are correct?


I also had some interesting behaviour on my titan this morning. One die went down, 10 soft resets failed then it did a hard reset on the cube - worked as designed. Then another die went "down" shortly after and it completely failed waas -s command so it carried out the hard reset. Worked as designed as well =)

GenTarkin's MOD Kncminer Titan custom firmware! v1.0.4! <--- CLICK HERE
Donations: bitcoin- 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At || litecoin- LYXrLis3ik6TRn8tdvzAyJ264DRvwYVeEw
GenTarkin
Legendary
*
Offline Offline

Activity: 2170


View Profile
August 13, 2015, 01:26:23 PM
 #40908

cool, I'll check it out

It looks good, however I did see one small issue. I raised the MHz on the flaky soft reset die to stress it and bfgminer wouldn't load. It got stuck in a hard reset loop when the die failed. I was able to change the advanced setting to get out of the loop, but maybe need to delay the hard reset routine for a few min to let bfgminer load when there is a bad die that's overclocked or not turned off

ok I just noticed something ... If I get a bunch of "Got nonce for unknown work in slot xx" errors scrolling then it goes straight to hard reset ... (this may tie in with the bgfminer not loading loop).

other than that everything is working fine

I'll get another cup of coffee & watch this for awhile, see if I can notice anything else that might help you troubleshoot it

...... ok this time the "Got nonce for unknown work in slot xx" errors didn't trigger an instant hard reset and it reset successfully, must have been coincidence earlier

ok looks like just getting random hard resets instead of running thru the soft reset loop. Most of the time it runs thru the loop. If I disable the flaky die there aren't any problems

btw, that die is set at 150 MHz so it has less amp draw
So, for the die thats at 150mhz ... are either of the DCDC's less than 5amp output for more than a few mins? If so, thats why its carrying out the hard reset. Paste contents of /var/log/monitordcdc.log if ya could =) thanks

If it turns out that one of the DCDC's is putting out current but the other is not, I may just change the comparison to DCDC1 AND DCDC2 less than threshold rather than OR. Because both will be less than 5 if the die is not working at all.

GenTarkin's MOD Kncminer Titan custom firmware! v1.0.4! <--- CLICK HERE
Donations: bitcoin- 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At || litecoin- LYXrLis3ik6TRn8tdvzAyJ264DRvwYVeEw
helmax
Sr. Member
****
Offline Offline

Activity: 441



View Profile
August 13, 2015, 01:26:36 PM
 #40909

guys some help

my controller only say STOPPED status page
cgminer dont start

neptune machine
how i can fix?
or anyone have SD FULL image for put in SDcard

already test recovery sd card but dont work

any help please?


kncminer say already dont have warranty

any help please

looking job
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 01:49:28 PM
 #40910

cool, I'll check it out

It looks good, however I did see one small issue. I raised the MHz on the flaky soft reset die to stress it and bfgminer wouldn't load. It got stuck in a hard reset loop when the die failed. I was able to change the advanced setting to get out of the loop, but maybe need to delay the hard reset routine for a few min to let bfgminer load when there is a bad die that's overclocked or not turned off

ok I just noticed something ... If I get a bunch of "Got nonce for unknown work in slot xx" errors scrolling then it goes straight to hard reset ... (this may tie in with the bgfminer not loading loop).

other than that everything is working fine

I'll get another cup of coffee & watch this for awhile, see if I can notice anything else that might help you troubleshoot it

...... ok this time the "Got nonce for unknown work in slot xx" errors didn't trigger an instant hard reset and it reset successfully, must have been coincidence earlier

ok looks like just getting random hard resets instead of running thru the soft reset loop. Most of the time it runs thru the loop. If I disable the flaky die there aren't any problems

btw, that die is set at 150 MHz so it has less amp draw
So, for the die thats at 150mhz ... are either of the DCDC's less than 5amp output for more than a few mins? If so, thats why its carrying out the hard reset. Paste contents of /var/log/monitordcdc.log if ya could =) thanks

If it turns out that one of the DCDC's is putting out current but the other is not, I may just change the comparison to DCDC1 AND DCDC2 less than threshold rather than OR. Because both will be less than 5 if the die is not working at all.

I bet that's it, in adv settings one die is showing zero amps, the other die isn't even listed -- I know it's hashing because I turned off the good dies and got 10 mhs in bfgminer for that bad die, about half what it's suppose to be

here's the end of the log, it's getting pretty big

Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "200" } }
STATUS=S,When=1439479313,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "200" } }
STATUS=S,When=1439479352,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
KnC: Frequency change FAILED! { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "200" } }
Soft reset failed, initiatng hard reset
Stopping bfgminer.
Power cycling ASIC# 5
INFO: Attempt to power down dc/dc
INFO: Attempt to power UP dc/dc
Starting bfgminer.
[2015-08-13 15:23:46] Die 5- restarted
Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2
Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4
Moving on with dead die test, no manual disabled die found
[2015-08-13 15:28:51] Die 5-1 requires restart
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479743,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479781,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479818,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479857,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479897,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479936,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479973,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
KnC: Frequency change FAILED! { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
Soft reset failed, initiatng hard reset


I was scrolling thru the log and saw this  "Failed multiple soft reset attempts, performing hard reset" -- above it there were 10 soft reset attempts like above -- however  there aren't any die configuration failed error messages in bfgminer

....  ok I just confirmed in bfgminer -- 10 successful soft restarts and the 11th goes straight to hard restart   :|

... it's not detecting a successful restart because of the low/zero amp issue??
vegasguy
Legendary
*
Offline Offline

Activity: 1246


"Yobit pump alert software" Link in my signature!


View Profile
August 13, 2015, 03:03:54 PM
 #40911

Guys, Ive donated to GenTarkin as he has done a wonderful job. Has anyone else?

There will be no more updates from KNCminer. GenTarkin is the ONLY one, and he is doing a better job, than KNCminer ever did!! Donate, so we dont lose him. @Gentarkin, please post your BTC address and/or LTC address. Thanks.

Vegas



I want to make sure everyone knows that I just released my software called "Yobit pump alert". THis is custom software that uses an algo to detect the start of a pump here on yobit, the second it starts. YOu can even filter the coins you see by price. Most pumps start less than 100 sats , so you can easily filter the cheap coins, so they are the only ones displayed Smiley https://bitcointalk.org/index.php?topic=1945937.msg20241953#msg20241953
jelin1984
Legendary
*
Offline Offline

Activity: 1582



View Profile
August 13, 2015, 03:56:04 PM
 #40912

How we can mining etherium with titan


Any details here
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686

FUN > ROI


View Profile
August 13, 2015, 04:11:37 PM
 #40913

How we can mining etherium with titan
You can't - completely different hashing algorithm.
https://forum.ethereum.org/discussion/197/how-to-help-secure-the-ethereum-network-faq

GenTarkin
Legendary
*
Offline Offline

Activity: 2170


View Profile
August 13, 2015, 06:06:38 PM
 #40914

cool, I'll check it out

It looks good, however I did see one small issue. I raised the MHz on the flaky soft reset die to stress it and bfgminer wouldn't load. It got stuck in a hard reset loop when the die failed. I was able to change the advanced setting to get out of the loop, but maybe need to delay the hard reset routine for a few min to let bfgminer load when there is a bad die that's overclocked or not turned off

ok I just noticed something ... If I get a bunch of "Got nonce for unknown work in slot xx" errors scrolling then it goes straight to hard reset ... (this may tie in with the bgfminer not loading loop).

other than that everything is working fine

I'll get another cup of coffee & watch this for awhile, see if I can notice anything else that might help you troubleshoot it

...... ok this time the "Got nonce for unknown work in slot xx" errors didn't trigger an instant hard reset and it reset successfully, must have been coincidence earlier

ok looks like just getting random hard resets instead of running thru the soft reset loop. Most of the time it runs thru the loop. If I disable the flaky die there aren't any problems

btw, that die is set at 150 MHz so it has less amp draw
So, for the die thats at 150mhz ... are either of the DCDC's less than 5amp output for more than a few mins? If so, thats why its carrying out the hard reset. Paste contents of /var/log/monitordcdc.log if ya could =) thanks

If it turns out that one of the DCDC's is putting out current but the other is not, I may just change the comparison to DCDC1 AND DCDC2 less than threshold rather than OR. Because both will be less than 5 if the die is not working at all.

I bet that's it, in adv settings one die is showing zero amps, the other die isn't even listed -- I know it's hashing because I turned off the good dies and got 10 mhs in bfgminer for that bad die, about half what it's suppose to be

here's the end of the log, it's getting pretty big

Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "200" } }
STATUS=S,When=1439479313,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "200" } }
STATUS=S,When=1439479352,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
KnC: Frequency change FAILED! { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "200" } }
Soft reset failed, initiatng hard reset
Stopping bfgminer.
Power cycling ASIC# 5
INFO: Attempt to power down dc/dc
INFO: Attempt to power UP dc/dc
Starting bfgminer.
[2015-08-13 15:23:46] Die 5- restarted
Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2
Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4
Moving on with dead die test, no manual disabled die found
[2015-08-13 15:28:51] Die 5-1 requires restart
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479743,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479781,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479818,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479857,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479897,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479936,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
{ "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
STATUS=S,When=1439479973,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0|
Attempting softreset of ASIC# 5 DIE# 1
KnC: Frequency change FAILED! { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } }
Soft reset failed, initiatng hard reset


I was scrolling thru the log and saw this  "Failed multiple soft reset attempts, performing hard reset" -- above it there were 10 soft reset attempts like above -- however  there aren't any die configuration failed error messages in bfgminer

....  ok I just confirmed in bfgminer -- 10 successful soft restarts and the 11th goes straight to hard restart   :|

... it's not detecting a successful restart because of the low/zero amp issue??

Can you try my latest commit? I just uploaded it.
Let me know what happens, also could u paste a screenshot of that 150mhz die from advanced screen config?
Thanks

GenTarkin's MOD Kncminer Titan custom firmware! v1.0.4! <--- CLICK HERE
Donations: bitcoin- 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At || litecoin- LYXrLis3ik6TRn8tdvzAyJ264DRvwYVeEw
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 06:33:52 PM
 #40915

here's the screen shot, trying your latest commit now

GenTarkin
Legendary
*
Offline Offline

Activity: 2170


View Profile
August 13, 2015, 06:38:47 PM
 #40916

here's the screen shot, trying your latest commit now



Wait, this is while bfgminer says its configured successfully?! ... cuz according to screenshot its not configured successfully at all, its not hashing ... thats why it got hard reset.

GenTarkin's MOD Kncminer Titan custom firmware! v1.0.4! <--- CLICK HERE
Donations: bitcoin- 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At || litecoin- LYXrLis3ik6TRn8tdvzAyJ264DRvwYVeEw
xenostar
Newbie
*
Offline Offline

Activity: 14


View Profile
August 13, 2015, 06:45:34 PM
 #40917

https://github.com/GenTarkin/Titan/releases/tag/v.93

New release published!!

---details---

Login through SSH & webgui is now: admin/admin        (should be anyways LOL! Hope I updated it correctly) =P test it peoples! =)

If soft die reset fails then initiate hard reset sequence (power off cube, restart bfgminer)
Instead of setting Dies w/ overheating DCDC's to OFF, now scales down 25mhz each check until DCDC's are under temp threshold.. If goes to 100 then sets die to OFF.
Added more temps to temp threshold setting, including all numbers between 90 & 95

*default DCDC temp monitoring settings are: ENABLED / 90C

---details---


Please test everyone, Ill fix as issues arise. Please Please donate =) Helps fuel my motivation to continue improving upon stuff =)

instead of burning the new img file I tried doing a git pull:

cd knc-asic
git stash save --keep-index                (didn't need this line on all rigs)
git pull
cd
./update-webgui.sh

seems to work but did I miss anything??




If I wanted to update my pi to your firmware without win32diskimager flashing the full image, what would be my commands?

git pull
./update-webgui.sh

thats it? How do I specify your git repository? Im a little confused as TXSteve added that 'didnt need this line on all rigs' comment so not sure if I need that git stash line or not.

I need to upgrade a remote box to test with this fw but dont have physical access. Im assuming this will work?
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 06:55:17 PM
 #40918

here's the screen shot, trying your latest commit now



Wait, this is while bfgminer says its configured successfully?! ... cuz according to screenshot its not configured successfully at all, its not hashing ... thats why it got hard reset.

yeah it an odd one, it is hashing -- that die never displays -- if I turn off all the good dies and let that die run I get aprox 10 mh/s on that bad die

btw that latest commit fixed it, the soft resets are random as needed -- before they occurred every 37 secs or so while in that loop
TXSteve
Sr. Member
****
Offline Offline

Activity: 340


View Profile
August 13, 2015, 06:58:55 PM
 #40919

https://github.com/GenTarkin/Titan/releases/tag/v.93

New release published!!

---details---

Login through SSH & webgui is now: admin/admin        (should be anyways LOL! Hope I updated it correctly) =P test it peoples! =)

If soft die reset fails then initiate hard reset sequence (power off cube, restart bfgminer)
Instead of setting Dies w/ overheating DCDC's to OFF, now scales down 25mhz each check until DCDC's are under temp threshold.. If goes to 100 then sets die to OFF.
Added more temps to temp threshold setting, including all numbers between 90 & 95

*default DCDC temp monitoring settings are: ENABLED / 90C

---details---


Please test everyone, Ill fix as issues arise. Please Please donate =) Helps fuel my motivation to continue improving upon stuff =)

instead of burning the new img file I tried doing a git pull:

cd knc-asic
git stash save --keep-index                (didn't need this line on all rigs)
git pull
cd
./update-webgui.sh

seems to work but did I miss anything??




If I wanted to update my pi to your firmware without win32diskimager flashing the full image, what would be my commands?

git pull
./update-webgui.sh

thats it? How do I specify your git repository? Im a little confused as TXSteve added that 'didnt need this line on all rigs' comment so not sure if I need that git stash line or not.

I need to upgrade a remote box to test with this fw but dont have physical access. Im assuming this will work?

I burned the img file on the 1st upgrade then you can do a git pull (may be another way)
if the git pull gives an error then run the git stash line

git stash save --keep-index
git pull
./update-webgui.sh

reboot
xenostar
Newbie
*
Offline Offline

Activity: 14


View Profile
August 13, 2015, 07:07:07 PM
 #40920

https://github.com/GenTarkin/Titan/releases/tag/v.93

New release published!!

---details---

Login through SSH & webgui is now: admin/admin        (should be anyways LOL! Hope I updated it correctly) =P test it peoples! =)

If soft die reset fails then initiate hard reset sequence (power off cube, restart bfgminer)
Instead of setting Dies w/ overheating DCDC's to OFF, now scales down 25mhz each check until DCDC's are under temp threshold.. If goes to 100 then sets die to OFF.
Added more temps to temp threshold setting, including all numbers between 90 & 95

*default DCDC temp monitoring settings are: ENABLED / 90C

---details---


Please test everyone, Ill fix as issues arise. Please Please donate =) Helps fuel my motivation to continue improving upon stuff =)

instead of burning the new img file I tried doing a git pull:

cd knc-asic
git stash save --keep-index                (didn't need this line on all rigs)
git pull
cd
./update-webgui.sh

seems to work but did I miss anything??




If I wanted to update my pi to your firmware without win32diskimager flashing the full image, what would be my commands?

git pull
./update-webgui.sh

thats it? How do I specify your git repository? Im a little confused as TXSteve added that 'didnt need this line on all rigs' comment so not sure if I need that git stash line or not.

I need to upgrade a remote box to test with this fw but dont have physical access. Im assuming this will work?

I burned the img file on the 1st upgrade then you can do a git pull (may be another way)
if the git pull gives an error then run the git stash line

git stash save --keep-index
git pull
./update-webgui.sh

reboot

Ahh, that makes sense. Thanks for the confirmation, looks like I wont be able to remote upgrade this.
Pages: « 1 ... 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 [2046] 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 ... 2138 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!