Pages:
Author

Topic: Swedish ASIC miner company kncminer.com - page 95. (Read 3049528 times)

legendary
Activity: 2450
Merit: 1002
Came across a behviour issue on my Titan, I just now noticed it issues a soft reset via waas and that returns success yet it still fails to RECONFIGURE successfully in bfgminer. So, a hard reset would be inevitable and really theres no way to differentiate at this point between a soft reset full success vs failure =/
May have to reimpliment hard reset no matter what.

EDIT: yeah what a bummer, its attemping multiple soft resets w/ no success yet waas doesnt fail. I dont know if there is a way around that at this point, may have to revert just hard resets, bummer.

EDIT: rethinking it out, I may have another way to detect die status as a fallback. Coding that in will be tricky, will have to wait till later =)
Damn these things for failing so many different ways ROFL!
legendary
Activity: 2450
Merit: 1002
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??




everything is upgraded and running fine so far,  just a couple observations:

-- the temp throttling is sweet, it doesn't even reboot bfgminer,  nice!!

-- you might want to implement a delay of a few min or so before triggering a hard reset because:
           a) a soft reset sometimes needs a few tries before it works and this will minimizes bfgminer restarts
               -- when the rig is rented and the customer is using an unstable pool that takes forever for vardif to adjust & stabilize,
                  frequent restarts are particularly troublesome
           b) a delay will be needed to optimize voltages & MHz, and/or to monitor which die is triggering the resets
 
anyway I'll send .5 btc to 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At   (sent)

thx again, nice work  Smiley



AWESOME !!! Thanks a ton!!!
I just uploaded another change for webgui, it now shows bfgminer version in status screen.
Ill look into the delay for ya =)
Ill get to working on auto upscaling of cores that previously were downclocked. Have a busy schedule coming up so may not be released as quickly and this is fairly complex =)

Regarding the soft reset, do you know where the soft reset actually fails? during the waas -s command or when bfgminer is told to reconfigure...?
When u see this behaviour happen can you post the relevant contents of /var/log/monitordcdc.log? That way I can see exactly what needs delayed.(or tried a few times)

If I had to guess, soft resets I check to see when they fail the waas command. I base the success / fail of that on whether a hard reset needs to be issued. So, I could do a timed loop of say up to 5 soft resets(on like a couple second timer) via waas command and if they all fail then perform hard reset, the first one that passes it exits loop then proceeds to tell BFGminer to do its die reconfigure. *NOT: The waas command has to succeed before BFGminer will show a "die successfully configured" message.
How that sound?

no, I don't know where the soft reset actually fails, I get the standard "die configuration failed" message and it tries again 20 or 30 sec later. If I can catch it I'll get the log file. I am using awesome miner to trigger hashrate alerts and can then monitor what's happening, but if the hard reset happens too quickly it doesn't trigger -- it instead triggers the rig offline alert, but then it's too late to see what happened

what you suggested sounds good to me
Ok, cool yeah "die configuration failed" .. if I would have to assume, means the waas soft reset has failed. At least, when my rig requires a hard reset ... thats the message I get until doing the hard reset. Ill impliment the loop sometime either today or tonight =)
If other people could test out the firmware that would be great and any donations helps =)
Thanks again for ur generous donation TXSteve, I really appreciate it =)
sr. member
Activity: 342
Merit: 250
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??




everything is upgraded and running fine so far,  just a couple observations:

-- the temp throttling is sweet, it doesn't even reboot bfgminer,  nice!!

-- you might want to implement a delay of a few min or so before triggering a hard reset because:
           a) a soft reset sometimes needs a few tries before it works and this will minimizes bfgminer restarts
               -- when the rig is rented and the customer is using an unstable pool that takes forever for vardif to adjust & stabilize,
                  frequent restarts are particularly troublesome
           b) a delay will be needed to optimize voltages & MHz, and/or to monitor which die is triggering the resets
 
anyway I'll send .5 btc to 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At   (sent)

thx again, nice work  Smiley



AWESOME !!! Thanks a ton!!!
I just uploaded another change for webgui, it now shows bfgminer version in status screen.
Ill look into the delay for ya =)
Ill get to working on auto upscaling of cores that previously were downclocked. Have a busy schedule coming up so may not be released as quickly and this is fairly complex =)

Regarding the soft reset, do you know where the soft reset actually fails? during the waas -s command or when bfgminer is told to reconfigure...?
When u see this behaviour happen can you post the relevant contents of /var/log/monitordcdc.log? That way I can see exactly what needs delayed.(or tried a few times)

If I had to guess, soft resets I check to see when they fail the waas command. I base the success / fail of that on whether a hard reset needs to be issued. So, I could do a timed loop of say up to 5 soft resets(on like a couple second timer) via waas command and if they all fail then perform hard reset, the first one that passes it exits loop then proceeds to tell BFGminer to do its die reconfigure. *NOT: The waas command has to succeed before BFGminer will show a "die successfully configured" message.
How that sound?

no, I don't know where the soft reset actually fails, I get the standard "die configuration failed" message and it tries again 20 or 30 sec later. If I can catch it I'll get the log file. I am using awesome miner to trigger hashrate alerts and can then monitor what's happening, but if the hard reset happens too quickly it doesn't trigger -- it instead triggers the rig offline alert, but then it's too late to see what happened

what you suggested sounds good to me
legendary
Activity: 2450
Merit: 1002
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??




everything is upgraded and running fine so far,  just a couple observations:

-- the temp throttling is sweet, it doesn't even reboot bfgminer,  nice!!

-- you might want to implement a delay of a few min or so before triggering a hard reset because:
           a) a soft reset sometimes needs a few tries before it works and this will minimizes bfgminer restarts
               -- when the rig is rented and the customer is using an unstable pool that takes forever for vardif to adjust & stabilize,
                  frequent restarts are particularly troublesome
           b) a delay will be needed to optimize voltages & MHz, and/or to monitor which die is triggering the resets
 
anyway I'll send .5 btc to 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At   (sent)

thx again, nice work  Smiley



AWESOME !!! Thanks a ton!!!
I just uploaded another change for webgui, it now shows bfgminer version in status screen.
Ill look into the delay for ya =)
Ill get to working on auto upscaling of cores that previously were downclocked. Have a busy schedule coming up so may not be released as quickly and this is fairly complex =)

Regarding the soft reset, do you know where the soft reset actually fails? during the waas -s command or when bfgminer is told to reconfigure...?
When u see this behaviour happen can you post the relevant contents of /var/log/monitordcdc.log? That way I can see exactly what needs delayed.(or tried a few times)

If I had to guess, soft resets I check to see when they fail the waas command. I base the success / fail of that on whether a hard reset needs to be issued. So, I could do a timed loop of say up to 5 soft resets(on like a couple second timer) via waas command and if they all fail then perform hard reset, the first one that passes it exits loop then proceeds to tell BFGminer to do its die reconfigure. *NOT: The waas command has to succeed before BFGminer will show a "die successfully configured" message.
How that sound?
sr. member
Activity: 342
Merit: 250
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??




everything is upgraded and running fine so far,  just a couple observations:

-- the temp throttling is sweet, it doesn't even reboot bfgminer,  nice!!

-- you might want to implement a delay of a few min or so before triggering a hard reset because:
           a) a soft reset sometimes needs a few tries before it works and this will minimizes bfgminer restarts
               -- when the rig is rented and the customer is using an unstable pool that takes forever for vardif to adjust & stabilize,
                  frequent restarts are particularly troublesome
           b) a delay will be needed to optimize voltages & MHz, and/or to monitor which die is triggering the resets
 
anyway I'll send .5 btc to 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At   (sent)

thx again, nice work  Smiley


legendary
Activity: 2450
Merit: 1002
Can you make your firmware
Work

With rasberry pi 2. Version?


That will be great

Titan firmware

I only have a pi to work on, so no.
legendary
Activity: 2450
Merit: 1002
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??




U would want to do the git pull from /home/pi (default dir that u log into via ssh) ... cuz otherwise the changed webpages wont download.
Then yeah, run the update-webgui.sh and u should ... *should* be set ... haha
(reapply desired temp threshold settings via webgui) .. mine defaults to ON/90
legendary
Activity: 2408
Merit: 1004
Can you make your firmware
Work

With rasberry pi 2. Version?


That will be great

Titan firmware
sr. member
Activity: 440
Merit: 250
anyone have full image SD card 1.5 GB for neptune ?
sr. member
Activity: 342
Merit: 250
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??


hero member
Activity: 784
Merit: 1004
Glow Stick Dance!
I can check it out pretty quickly

btw, it doesn't seem like the max temp is working, I have it set for 90c and a die hit 92c, nothing happened


Testing a rearrangement & rewrite of hard reset detection. Will have to wait till mine actually needs resetting to see if it works. If it does, it should differentiate between soft reset success vs fail and then applying hard power reset to cube if needed.
My Titan doesnt experience successfull soft resets. So, will need someone to test it out once I verify the soft reset fail then hard reset works.
It doesnt happen instantly. Think it loops every 4 seconds. Ill test it here in a lil while. I dont see why it wouldnt work but Ill double check =)
Grr nevermind, somehow it stopped writing to the config file. Ill have to look into it later. Not sure how it broke =P
Probably a typo somewhere lol

well I had 1 hard reset work flawlessly  Smiley

I'll pledge .5 btc for your efforts, if you can just drop the MHz from 325 to 300, instead of turning the die off. Also can you add another temp cut-off 93c -- I manually turn them down around 92/93 - it's usually at those temps for only a few hours, and haven't had any problems
[/quote]

Hrm....ok well I found an issue w/ the changes but only as of this morning when I started editing the code again, these erronous edits did not make it into my latest release. I fixed the issues but the release u downloaded should still have worked properly.

Any chance you can paste the contents of /var/log/monitordcdc.log when the thermal trip doesnt work for you?
It would require ssh'n into the pi and copying the contents of that file to a text file.

The test works perfect on my box when I set the temp threshold to 70....(added as a testing temp =) )
I dont even have to hit refresh on the advanced settings page, I can see the dies get turned to 0's that go over threshold, after bfgminer restarts.

Also, yes when I have more time, now that I see how KNC updates clocks without needing to restart bfgminer, I will implement a soft clock scale down w/o needing a bfgminer restart. =) I will also put 92/93C in there for ya =)
[/quote]
[/quote]

Fix the damn broken quotes! It's unreadable.
copper member
Activity: 2898
Merit: 1465
Clueless!
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 =)

heh you keep adding stuff I need before i can get to installing it due to work at the end of the month...heh all suggestions I needed heh Smiley

anyway gotta buy me some coin on coinbase and shoot you some again when i can get off work enough to test this and or at least get you some btc
(main hoard is in paper wallet in safety deposit box) Smiley

I'm sure there are more then a few of us that will trickle you some more btc Smiley

again i'm sure i include everyone we appreciate your efforts (by the by all my posts till the end of the month will be away from miners at work...no joy to play with toys)

legendary
Activity: 2450
Merit: 1002
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 =)
sr. member
Activity: 342
Merit: 250
A list of changes in my next build:
Proper handling of soft vs hard die resets(if soft reset fails then proceeds to do hard reset via cube power cycling & BFGminer restart)
Custom 92/93C added to dropdown list
A scaling down of dies who's VRM (DCDC) temps cross over threshold

Future build to do:
Add auto clock scaling up for dies which were previously scaled down due to VRM overheating.


sounds great!

Thanks =), Im uploading hopefully a working img now.

I also changed back the login password to admin/admin for both ssh & webgui
*I attempted to anyways...haha will need testing =)

Once you test out this build TXSteve, please send .5btc my way =) I would greatly appreciate it =) ... That will get me rollin on auto reupping the clocks of Dies that have been declocked due to DCDC overheat.
(this will be more difficult to code cuz now I gotta keep track of original settings n do lots of comparing while running =P )

no problem I'll check it out & take care of it tomorrow, about ready to call it a day here

thx again
legendary
Activity: 2450
Merit: 1002
A list of changes in my next build:
Proper handling of soft vs hard die resets(if soft reset fails then proceeds to do hard reset via cube power cycling & BFGminer restart)
Custom 92/93C added to dropdown list
A scaling down of dies who's VRM (DCDC) temps cross over threshold

Future build to do:
Add auto clock scaling up for dies which were previously scaled down due to VRM overheating.


sounds great!

Thanks =), Im uploading hopefully a working img now.

I also changed back the login password to admin/admin for both ssh & webgui
*I attempted to anyways...haha will need testing =)

Once you test out this build TXSteve, please send .5btc my way =) I would greatly appreciate it =) ... That will get me rollin on auto reupping the clocks of Dies that have been declocked due to DCDC overheat.
(this will be more difficult to code cuz now I gotta keep track of original settings n do lots of comparing while running =P )
sr. member
Activity: 342
Merit: 250
A list of changes in my next build:
Proper handling of soft vs hard die resets(if soft reset fails then proceeds to do hard reset via cube power cycling & BFGminer restart)
Custom 92/93C added to dropdown list
A scaling down of dies who's VRM (DCDC) temps cross over threshold

Future build to do:
Add auto clock scaling up for dies which were previously scaled down due to VRM overheating.


sounds great!
sr. member
Activity: 342
Merit: 250

Weird, so freaking weird, maybe I messed up something in bulding my latest .img file. Ill double verify the code works again on my box tonight and make a fresh image. Im also rewriting the code atm to impliment a sliding scale for clocking down the dies which have overheating VRM's rather than just shutting them off =)
I may add an auto clock up based on a temp threshold as well.
You wanted 92/93C thresholds right? Ill throw those in there as well.

Hey "autoclock up based on threshold" ?  That would be too cool. That occurred to me but I didn't want to impose, however now that you mention it ....   Smiley  One thing about "auto up", I have a couple dies I was able to revive by running low MHz like 150 MHz ... I wouldn't want to "auto up " these dies, just the ones that were knocked down a notch

92/93 would be great... I have a few cubes that hug 90c on a hot day but I don't want to knock them down, just the 1 or 2 that go higher on an extra HOT day, so far we've hit 105f and 101f ... that way I can leave the house without worrying as much, already blew up one meter box -- that's fixed but things can & will go wrong so can't be too safe.

btw while I am on it, the reason meter box blew up was because of corroded connections that overheated & actually melted the insulation, etc.  When I analyzed everything I found that I was drawing more than twice as much power on 1 110v leg than the other. So make sure your rigs are reasonably balanced on your electrical service. Buy a quality ammeter open your electrical box & actually check the draw on each leg and make adjustments if necessary. Also check the draw on each 20 amp breaker to make sure it's not over 16 amps  and put heavy duty 20 amp outlets in your receptacle boxes. Just saying ... can't be too careful when you are running a heavy load 24/7

txSteve

legendary
Activity: 2450
Merit: 1002
A list of changes in my next build:
Proper handling of soft vs hard die resets(if soft reset fails then proceeds to do hard reset via cube power cycling & BFGminer restart)
Custom 92/93C added to dropdown list
A scaling down of dies who's VRM (DCDC) temps cross over threshold

Future build to do:
Add auto clock scaling up for dies which were previously scaled down due to VRM overheating.
legendary
Activity: 2450
Merit: 1002
GenTarkin here's the contents of the monitordcdc.log file

[2015-08-11 14:45:08] Start

that's it

I set threshold to 85c  -- there was one die at 85c and another at 86c, prior to this the log file was empty

hope that helps

wtf .... weird hrm.... can you post a screenshot of temps & the monitordcdc.log file when it should be going off?
Thanks... in all my tests it works just fine ... so this is puzzling










Weird, so freaking weird, maybe I messed up something in bulding my latest .img file. Ill double verify the code works again on my box tonight and make a fresh image. Im also rewriting the code atm to impliment a sliding scale for clocking down the dies which have overheating VRM's rather than just shutting them off =)
I may add an auto clock up based on a temp threshold as well.
You wanted 92/93C thresholds right? Ill throw those in there as well.

I figured it out =) , one of the temp monitoring files I made didnt make it to github, therefore not making it to the img. Sorry =), next build will include the fix and all the goodie updates =)
legendary
Activity: 2450
Merit: 1002
That was something we were considering , but after looking everything over, its a really bad idea. Im sure Tarkin will remove that option in the next release.

@GenTarkin. The biggest threat to these miners is the temp of the VRM. I think the critical temp of the vrm is around 85C. Can you put a switch in that will shut down the die @85C , that we can choose to have this active or not, or even better have a drop down to choose the shutoff temp, and a switch to activate or not.  I can send more btc if you can do this. This prevents permanent damage to the VRM, thats what overheats, NOT the processors or dies.

Vegas

UPDATE: have a working VRM checker. It basically disables the die whos VRM is over 85. It simply turns it to OFF in webgui and restarts bfgminer. The die can of course be turned back on by selecting a freqency in webgui and reapplying settings.
Controlling it via webgui is probably not gonna be an option at least for now. I have no idea how that portion of the webgui code works lol.
Will post when its ready for download =)

The VRMs enter thermal shutdown at 120C to protect themselves, anything over about 105C is getting sketchy but under that things will make it..
Are you sure? Well, people cast in what they want the thermal trigger at and Ill change it to that. For now its 85C

Note donations would be greatly appreciated =)
I still have yet to be paid in full for the .5btc bounty =/

I hope you fare better than I did, had hundreds of installs, I helped dozens of people myself, someone started selling it on ebay, etc..  In the end managed 0.32 BTC in total from a few people.. The dozens I helped actually all said they would donate but just needed it working for now, in the end just a handful of honest people.
Yeah, its unfortunate, but at least the bounty was delivered upon =) ... back then for you .32btc was worth way much more in fiat then it is now haha =)
Pages:
Jump to: