Topic: Swedish ASIC miner company kncminer.com - page 69. (Read 3049514 times)
I am ready to test whenever you can seed me the new version
Just implemented a working option in MINING page to enable / disable API read only access from ALL IP's =-), will make it into my next release.
v.99c is available to all paid members now!!!! : http://bitcoinlasvegas.net/kncminer-titan-custom-firmware-mod-paid-membership-page/
Vegas
Vegas
Do you have the source posted as well?
https://github.com/GenTarkin/Titan/releases/tag/v.99c
so far .99c is working great i had one cube that kept throwing my miner into a reboot loop it seems to be stable now so thank you
v.99c is available to all paid members now!!!! : http://bitcoinlasvegas.net/kncminer-titan-custom-firmware-mod-paid-membership-page/
Vegas
Vegas
Do you have the source posted as well?
My cubes reinitialize every 5 minutes or so recently. Is there any fix for this?
Off the top of my head ....PSU? more off the top of my head make a new SD card get a class 10 version I use Sandisk 8gb class 10's usually on ebay 2 for 12 bucks or some such with shipping ..I had a surge where it said not internet but the other miner worked so did an SD re-do (after a storm) took care of the problem
hmmmm...what else
if you got a backup you could try re-installing that (i do so on a new sd however)
anyway I know zip but no one has replied ...hopefully better options by them..just what I'd do if I had another SD laying about
My cubes reinitialize every 5 minutes or so recently. Is there any fix for this?
v.99c is available to all paid members now!!!! : http://bitcoinlasvegas.net/kncminer-titan-custom-firmware-mod-paid-membership-page/
Vegas
Vegas
!!!ANNOUNCING!! v.99c for premium/prepaid/predonated members!
--v.99b is now available for *free*(.75% don) users.
PREMIUM members, you should soon see the updated v.99c in your member page which you were supplied when you purchased the firmware. "vegasguy" will supply you with more info.
Release notes: https://github.com/GenTarkin/Titan/releases/tag/v.99c
For people running the *free*(donate version) v.99a version, you can either update via the UPGRADE button on STATUS page OR download the .bin file from here: https://github.com/GenTarkin/Titan/releases/tag/v.99b
--v.99b is now available for *free*(.75% don) users.
PREMIUM members, you should soon see the updated v.99c in your member page which you were supplied when you purchased the firmware. "vegasguy" will supply you with more info.
Release notes: https://github.com/GenTarkin/Titan/releases/tag/v.99c
Code:
AutoBypass Dies, BFGminer 5.3.0, pf4g's KNCminion & more!
Major changes in this release:
1. Auto-bypass of dies which cause constant soft / hard resets. How this works: If a die has caused more than 5 soft / hard resets within
2 hours then that die will be flagged for autobypass - meaning monitoring of its "hashing health" will be further ignored and the die will be on
its own. Its DCDC's will still be monitored for temperature conditions though, so if soft / hard resets are being caused by temp issues ..
these will NOT be ignored! The list of dies bypassed is persistent across pi reboots etc, when a die has been bypassed a message will be
shown on ADVANCED page w/ an option to clear the autobypass file.
2. Updated BFGminer to 5.3.0
3. Integrated pf4g's KNCminion webgui extension & added a link "more goodies" on status page.
Minor changes & fixes:
1. Disabled http access logging by default(option still exists to enable in SYSTEM page).
2. Set bfgminer 5.1.0 as default miner to be ran (can still change it to 5.3.0 via ADVANCED page).
3. Minor tweaks to ADVANCED running bfgminer version readout.
4. Added reset count per die to /var/log/monitordcdc.log
5. Optimized various sections of my code additions in monitoring script.
6. v.99b made available for "free" users.
NOTES - as usual , please contact me in bitcointalk.org forum or litecointalk.org for w/ bugs, questions etc...
Major changes in this release:
1. Auto-bypass of dies which cause constant soft / hard resets. How this works: If a die has caused more than 5 soft / hard resets within
2 hours then that die will be flagged for autobypass - meaning monitoring of its "hashing health" will be further ignored and the die will be on
its own. Its DCDC's will still be monitored for temperature conditions though, so if soft / hard resets are being caused by temp issues ..
these will NOT be ignored! The list of dies bypassed is persistent across pi reboots etc, when a die has been bypassed a message will be
shown on ADVANCED page w/ an option to clear the autobypass file.
2. Updated BFGminer to 5.3.0
3. Integrated pf4g's KNCminion webgui extension & added a link "more goodies" on status page.
Minor changes & fixes:
1. Disabled http access logging by default(option still exists to enable in SYSTEM page).
2. Set bfgminer 5.1.0 as default miner to be ran (can still change it to 5.3.0 via ADVANCED page).
3. Minor tweaks to ADVANCED running bfgminer version readout.
4. Added reset count per die to /var/log/monitordcdc.log
5. Optimized various sections of my code additions in monitoring script.
6. v.99b made available for "free" users.
NOTES - as usual , please contact me in bitcointalk.org forum or litecointalk.org for w/ bugs, questions etc...
For people running the *free*(donate version) v.99a version, you can either update via the UPGRADE button on STATUS page OR download the .bin file from here: https://github.com/GenTarkin/Titan/releases/tag/v.99b
Im seeing miners from batch 2 for sale with 5 cubes? Was KNC going to send the 5th cube to all their favoured early buyers?
No, they were doing what they were contractually obligated to do. Instead of improving the hardware and software, they just included another cube to reach 400Mh/s, which is nice, but remember that Batch #1, with only four cubes, already missed it's power consumption target by 100%. They just added another cube , made the situation worse, and called it Batch #2.
Im seeing miners from batch 2 for sale with 5 cubes? Was KNC going to send the 5th cube to all their favoured early buyers?
Ok, Im gonna call a vote... Who all would be ok w/ readonly api access from *any* ip address... (all subnet ip's & any external ip's that are allowed access through firewall)
Not me. Just do some checkboxes, dude.
Hrm... will see, maybe Ill just throw this bit into the next release after v99c .. =)
Ok, Im gonna call a vote... Who all would be ok w/ readonly api access from *any* ip address... (all subnet ip's & any external ip's that are allowed access through firewall)
Not me. Just do some checkboxes, dude.
I think a check box might be a good idea for anyone looking to leave there miner locked down to remote access
Ok, Im gonna call a vote... Who all would be ok w/ readonly api access from *any* ip address... (all subnet ip's & any external ip's that are allowed access through firewall)
Not me. Just do some checkboxes, dude.
Ok, Im gonna call a vote... Who all would be ok w/ readonly api access from *any* ip address... (all subnet ip's & any external ip's that are allowed access through firewall)
i can test it with my management software once you seed me the new copy and give you feedback
What management software are you using?
Well, Ive confirmed --api-network gets completely ignored if --api-allow is specified. Thats dumb.... it should truely "override" and not fucking ignore it. Oh well =)
I guess the monitoring of rigs read only will be harder then I thought, unless I allow 0/0 (all) read only access =P
I guess the monitoring of rigs read only will be harder then I thought, unless I allow 0/0 (all) read only access =P
i can test it with my management software once you seed me the new copy and give you feedback
Small update:
My next release will ALSO have upgraded bfgminer 5.3.0 in it and some minor monitoring script code tweaks I found =)
Oh and also --api-network added to bfgminer.sh
My next release will ALSO have upgraded bfgminer 5.3.0 in it and some minor monitoring script code tweaks I found =)
Oh and also --api-network added to bfgminer.sh
Awesome Thank you
Yeahp, I hope the --api-network addition functions as I intend it to =-P .. noone did get back to me about its EXACT behaviour when --api-allow is in effect.
Small update:
My next release will ALSO have upgraded bfgminer 5.3.0 in it and some minor monitoring script code tweaks I found =)
Oh and also --api-network added to bfgminer.sh
My next release will ALSO have upgraded bfgminer 5.3.0 in it and some minor monitoring script code tweaks I found =)
Oh and also --api-network added to bfgminer.sh
Awesome Thank you
Jump to: