Topic: Swedish ASIC miner company kncminer.com - page 1379. (Read 3050075 times)
Apparently all is hunky dory, well I think I'll wait until I wake up and this thread will be at page 650 it will be October 4th and full of glowing praise and no problems...and I'll never at cheese before bed again.
Time out.
KnC is saying that it is a power supply issue?
I disagree. PSUs do not just de-energize for no good reason... Just why does the PSU power down?.. and the Rosewill Lightning 1300 has a very good rating.
http://www.jonnyguru.com/modules.php?name=NDReviews&op=Story5&reid=258
http://www.newegg.com/Product/Product.aspx?Item=N82E16817182063
My PSU is no POS.
Rosewill has been known for making some junk in the past, but not this class of PSUs. I can take ANY device I find and plug and unplug it all day long and not expect the device to light up.
I would be willing to bet that the latent electrical problem is what causes the PSU to go into a protective shut down to begin with. If the PSU is suspect, why does the miner not fry when it is initially powered? Surge is a surge, but not necesarily a Serge.
Come on, KnC. I think you can do better. I have been very forgiving thus far.
KnC is saying that it is a power supply issue?
I disagree. PSUs do not just de-energize for no good reason... Just why does the PSU power down?.. and the Rosewill Lightning 1300 has a very good rating.
http://www.jonnyguru.com/modules.php?name=NDReviews&op=Story5&reid=258
http://www.newegg.com/Product/Product.aspx?Item=N82E16817182063
My PSU is no POS.
Rosewill has been known for making some junk in the past, but not this class of PSUs. I can take ANY device I find and plug and unplug it all day long and not expect the device to light up.
I would be willing to bet that the latent electrical problem is what causes the PSU to go into a protective shut down to begin with. If the PSU is suspect, why does the miner not fry when it is initially powered? Surge is a surge, but not necesarily a Serge.
Come on, KnC. I think you can do better. I have been very forgiving thus far.
Could it be due to only having a load on the 12V rail? Havent read the entire thread, but assuming your mining rig didnt go up in flames yet, perhaps you can try connecting a hdd to the PSU to put some load on the 5V.
(note: AFAIK, most 3.5" desktop drives use both 12v and 5v, but to be sure, if you have a 2.5" drive or something else that uses 5V, use that).
We all bought an unrefined product did we? Odd, I didn't see those words or anything like that when I paid for mine.
Not in any of the back patting videos or interviews either.
We bought a miner that we were told confidently would have margins upon margins capable of 400Gh and even today no-one has said that this (and the oct 15th date) has changed. Except of course to up it to 550 on the site and most promos ...which currently is false advertising ..as the past 20 pages here bear witness to.
As for all this shite about power consumption...right now is that a big priority to get down? I'd rather have a hashing rig while it's making enough BTC to make a few quid power bill extra irrelevent..later on the power consumption will matter more but not initially compared to a working rig. As long as the PSU handles it, we can wait for a firmware fix to get it down. Hashing reliably without smoke is the priority for users.
The sarcastic tone of Oramas post amazed me, people using fans to reduce temps ..planking? It worked. How bizarre is that? More to the fucking point no-one was talking from KNC end despite much asking...so what else were people to do? "We have a specialist flying in and we'll get back to you as soon as we know something." < see, took me 3 seconds to type that, and even some poor sweaty overworked KnC human could manage that surely?
The way to deal with trainwrecks like this isn't arrogance, sarcasm and silence ..it's communication and apologies and in many cases here where buyers have been so badly let down with multi hosted jupiters...fair compensation.
I wont deal with KnC again, nothing to do with the rigs, it's the denial and head in the sand stuff I can't be living with.
+100000 Not in any of the back patting videos or interviews either.
We bought a miner that we were told confidently would have margins upon margins capable of 400Gh and even today no-one has said that this (and the oct 15th date) has changed. Except of course to up it to 550 on the site and most promos ...which currently is false advertising ..as the past 20 pages here bear witness to.
As for all this shite about power consumption...right now is that a big priority to get down? I'd rather have a hashing rig while it's making enough BTC to make a few quid power bill extra irrelevent..later on the power consumption will matter more but not initially compared to a working rig. As long as the PSU handles it, we can wait for a firmware fix to get it down. Hashing reliably without smoke is the priority for users.
The sarcastic tone of Oramas post amazed me, people using fans to reduce temps ..planking? It worked. How bizarre is that? More to the fucking point no-one was talking from KNC end despite much asking...so what else were people to do? "We have a specialist flying in and we'll get back to you as soon as we know something." < see, took me 3 seconds to type that, and even some poor sweaty overworked KnC human could manage that surely?
The way to deal with trainwrecks like this isn't arrogance, sarcasm and silence ..it's communication and apologies and in many cases here where buyers have been so badly let down with multi hosted jupiters...fair compensation.
I wont deal with KnC again, nothing to do with the rigs, it's the denial and head in the sand stuff I can't be living with.
Totally.
Timmers you are being sensitive. Avenger I'm starting to believe you are a troll. Of course it's unrefined as you well knew. You knew perfectly well they were delivering a product to be placed in your hands in an expedited fashion upon receiving the chips. As such margin upon margins were in place to ensure no post chip receipt refinement was required prior to you being able to hash. Obviously this would mean improvements would then succeed the initiation of delivery, and will continue to do so. There is yet more to come. This is not a first for just Bitcoin mining, this is pretty much a first for the entire IC industry. It's insane. To get this, this right, first time, on 28nm tech is unheard of. Those involved; fab, suppliers, backend, etc. think this is remarkable, and it is.
^^^ Mega shill enabled.
My Jupiter is scheduled for delivery today. Of course I bought a Corsair HX850 - is there any *safe* way to use it, or should I not even plug the thing in?
What if I power on the HX850 and plug in the PCI-E connectors one at a time?
What if I power on the HX850 and plug in the PCI-E connectors one at a time?
NO! Never plug one at a time whilst on. and please step away from that PSU if you are even contemplating that!!
So even with the much better FW .95 you still wouldn't chance it? How about the 1250 series?
Not the point. He's talking about hot plugging the PCI-e connectors. Doesn't matter what the device is, that's a good way to let the smoke out.
Edit. others covered this. Oops.
I'm running 0.93. Just tried to upgrade to 0.95, and it seems to work, but after restart the web interface still says that the current firmware revision is 0.93. I tried to upgrade (downgrade) to other versions but it's the same.
It is possible that the upgrade was successful and the web interface displays the wrong version number? Is there a way to check firmware version through ssh?
at least you can access the miner page/tab....I cant... i get "ERROR 500 Internal server error"It is possible that the upgrade was successful and the web interface displays the wrong version number? Is there a way to check firmware version through ssh?
When I added my backup pools in CGMiner itself, I broke the web interface. I'm assuming that's the common cause for most people.
I would guess that the configuration is still saved in a text file you can hand-edit.
Yes. Or three or four.
I'm running 0.93. Just tried to upgrade to 0.95, and it seems to work, but after restart the web interface still says that the current firmware revision is 0.93. I tried to upgrade (downgrade) to other versions but it's the same.
It is possible that the upgrade was successful and the web interface displays the wrong version number? Is there a way to check firmware version through ssh?
at least you can access the miner page/tab....I cant... i get "ERROR 500 Internal server error"It is possible that the upgrade was successful and the web interface displays the wrong version number? Is there a way to check firmware version through ssh?
When I added my backup pools in CGMiner itself, I broke the web interface. I'm assuming that's the common cause for most people.
I think you mean ssh? What is ssl?
Switched my hosted Jupiter to eligius and I'm now getting close to 500 (around 480 450 420).
Thank you for .95!!! Can't wait for .96!!!
Time out.
KnC is saying that it is a power supply issue?
I disagree. PSUs do not just de-energize for no good reason... Just why does the PSU power down?.. and the Rosewill Lightning 1300 has a very good rating.
http://www.jonnyguru.com/modules.php?name=NDReviews&op=Story5&reid=258
http://www.newegg.com/Product/Product.aspx?Item=N82E16817182063
My PSU is no POS.
Rosewill has been known for making some junk in the past, but not this class of PSUs. I can take ANY device I find and plug and unplug it all day long and not expect the device to light up.
I would be willing to bet that the latent electrical problem is what causes the PSU to go into a protective shut down to begin with. If the PSU is suspect, why does the miner not fry when it is initially powered? Surge is a surge, but not necesarily a Serge.
Come on, KnC. I think you can do better. I have been very forgiving thus far.
KnC is saying that it is a power supply issue?
I disagree. PSUs do not just de-energize for no good reason... Just why does the PSU power down?.. and the Rosewill Lightning 1300 has a very good rating.
http://www.jonnyguru.com/modules.php?name=NDReviews&op=Story5&reid=258
http://www.newegg.com/Product/Product.aspx?Item=N82E16817182063
My PSU is no POS.
Rosewill has been known for making some junk in the past, but not this class of PSUs. I can take ANY device I find and plug and unplug it all day long and not expect the device to light up.
I would be willing to bet that the latent electrical problem is what causes the PSU to go into a protective shut down to begin with. If the PSU is suspect, why does the miner not fry when it is initially powered? Surge is a surge, but not necesarily a Serge.
Come on, KnC. I think you can do better. I have been very forgiving thus far.
If I have corsair HX850 PSUs for my miners should I immidietly change them or should I wait for official info?
I'd personally change bro. After their reset they supply peak current without ramping for approx 30 seconds is what I understood. That pops the cap, and so far it's the PSU that is most likely to cause this issue. Most other PSU's once reset gradually ramp current.
This makes 0 sense. Are you saying that other PSUs ramp up the current over 30 seconds? PC power supplies are voltage, not current, regulated. There's overcurrent protection, but that just shuts the thing down & stops it from toasting itself.
Agreed. Either he is misunderstanding (playing a game of telephone here) or it is just nonsense to shift the blame.
Power suplies don't ramp up current.
Power supplies don't force current.
A circuit DRAWS current.
If the circuit was damaged by drawing too much current then the circuit shouldn't draw so much current.
In simple terms a supply can be a current source or a voltage source. The power supply might show characteristics of either/or given that those are not simple devices. If its design says that at a given moment it needs to provide X amps of current to maintain or reach Y voltage, it will provide that current. If for some reason it does not know the voltage has been approached or reached, it will continue to provide that current unabated until it voltage limits. Until it knows that the required voltage has been reached it could source current that could drive the voltage above the specified max voltage of the circuit capacitors and BANG goes the capacitor exploding and outsourcing a gas that smells just like electronics burning.
Years ago, to induce permanent magnetism in Alnico slugs the slugs would be wound with a few, 2 or 3, turns of heavy wire. It requires a massive jolt of current flow. In order to attain that required jolt of current, a bank of capacitors were charged to a high voltage. The high voltage built the charge in the capacitors that allowed the high current.
It would take a high voltage to produce the current that results in a circuit voltage excessively high enough to blow the circuit capacitors.
soy
I already point it out thread.
First of all it isn't pin 4, 5, or 6 (#1 to #12 is the first row). The PS-ON pin is #16. When it is connected to ground (and ground) that will pull the voltage low. This is the "signal" to the PSU to power the output rails ("turn on" although that isn't technically correct).
http://www.mupuf.org/images/wt-rpm/connector_atx_pinout.gif[/img]
Any ground pin will work equally fine. As you can see in the pinout above there are multiple ground pins in the ATX-24 connector and they all are exactly the same. You are just completing a circuit from the positive voltage on pin #16 to any ground. What you call #5 & #6 are #17 & #18 and they are both ground pins. So is the next pin (#19) and the one of the other side of PS_ON (#15) as well as both of the pins diagonally (#3 & #5). Hell you could even connect a wire from PS_ON to a bare screw on the power supply and it would work (UL listed PSU means the metal chassis is also grounded).
First of all it isn't pin 4, 5, or 6 (#1 to #12 is the first row). The PS-ON pin is #16. When it is connected to ground (and ground) that will pull the voltage low. This is the "signal" to the PSU to power the output rails ("turn on" although that isn't technically correct).
http://www.mupuf.org/images/wt-rpm/connector_atx_pinout.gif[/img]
Any ground pin will work equally fine. As you can see in the pinout above there are multiple ground pins in the ATX-24 connector and they all are exactly the same. You are just completing a circuit from the positive voltage on pin #16 to any ground. What you call #5 & #6 are #17 & #18 and they are both ground pins. So is the next pin (#19) and the one of the other side of PS_ON (#15) as well as both of the pins diagonally (#3 & #5). Hell you could even connect a wire from PS_ON to a bare screw on the power supply and it would work (UL listed PSU means the metal chassis is also grounded).
1) You explained it best when you said that guides that say pin 4 &5 or 4&6 are actually meaning pin 16/14 and a ground pin, they are reading it wrong and backwards. I do not understand why they are doing that, but they are. You , yourself, are actually getting the pin numbers incorrect too -- saying #15, so i guess it is common.
2) What about taking the jumper out before turning off the PSU, is that good? it is what Redacted on here recommended.
You do not need to remove the jumper when shutting off the PSU. It doesn't change anything except you will not be able to turn the PSU back on without it.
We all bought an unrefined product did we? Odd, I didn't see those words or anything like that when I paid for mine.
Not in any of the back patting videos or interviews either.
We bought a miner that we were told confidently would have margins upon margins capable of 400Gh and even today no-one has said that this (and the oct 15th date) has changed. Except of course to up it to 550 on the site and most promos ...which currently is false advertising ..as the past 20 pages here bear witness to.
As for all this shite about power consumption...right now is that a big priority to get down? I'd rather have a hashing rig while it's making enough BTC to make a few quid power bill extra irrelevent..later on the power consumption will matter more but not initially compared to a working rig. As long as the PSU handles it, we can wait for a firmware fix to get it down. Hashing reliably without smoke is the priority for users.
The sarcastic tone of Oramas post amazed me, people using fans to reduce temps ..planking? It worked. How bizarre is that? More to the fucking point no-one was talking from KNC end despite much asking...so what else were people to do? "We have a specialist flying in and we'll get back to you as soon as we know something." < see, took me 3 seconds to type that, and even some poor sweaty overworked KnC human could manage that surely?
The way to deal with trainwrecks like this isn't arrogance, sarcasm and silence ..it's communication and apologies and in many cases here where buyers have been so badly let down with multi hosted jupiters...fair compensation.
I wont deal with KnC again, nothing to do with the rigs, it's the denial and head in the sand stuff I can't be living with.
Not in any of the back patting videos or interviews either.
We bought a miner that we were told confidently would have margins upon margins capable of 400Gh and even today no-one has said that this (and the oct 15th date) has changed. Except of course to up it to 550 on the site and most promos ...which currently is false advertising ..as the past 20 pages here bear witness to.
As for all this shite about power consumption...right now is that a big priority to get down? I'd rather have a hashing rig while it's making enough BTC to make a few quid power bill extra irrelevent..later on the power consumption will matter more but not initially compared to a working rig. As long as the PSU handles it, we can wait for a firmware fix to get it down. Hashing reliably without smoke is the priority for users.
The sarcastic tone of Oramas post amazed me, people using fans to reduce temps ..planking? It worked. How bizarre is that? More to the fucking point no-one was talking from KNC end despite much asking...so what else were people to do? "We have a specialist flying in and we'll get back to you as soon as we know something." < see, took me 3 seconds to type that, and even some poor sweaty overworked KnC human could manage that surely?
The way to deal with trainwrecks like this isn't arrogance, sarcasm and silence ..it's communication and apologies and in many cases here where buyers have been so badly let down with multi hosted jupiters...fair compensation.
I wont deal with KnC again, nothing to do with the rigs, it's the denial and head in the sand stuff I can't be living with.
+1
What denial? What head in the sands?? They worked their asses off to improve the issue, and ignored the FUD. The extra fans just waste electricity. The temps quoted from Bertmod were from the VRMs not the ASIC. Please explain what trainwreck exactly? They, in a week have delivered more hashrate than BFL have to date, and more boxes than Avalon ever achieved. They have just released an update that massively improves hashrate. It was a firmware, not a cooling issue. One week. Fair enough if you don't want to deal with them again, their engineering partners on this project think they are incredible, really. That's not hype.
C'mon, you seem intelligent enough to understand that not giving an update to your customers when something is delayed is poor business. Each day that I don't have my miner after 30 Sep is another day that it is late. Today is the 11th/12th of October. I do NOT have a tracking number and I have a day 2 order. I will be very lucky to get my day 2 order by Oct 15th. I should have gotten at least 12 updates/explanations/apologies since the 30th but I have not gotten 1. All I get is canned responses from KNC support saying everything is progressing nicely as the days fly by. Again, we are talking about an order that was marked as "This order has been scheduled for Shipping on day 2 of production". What day of production are we on? Where is my compensation or at the very least an explanation. It would look like this:
"Hello Mr. ____________,
We apologize but your order will not ship again today. There have been reports of units catching fire, overheating, locking up, and just generally under-performing so we have decided to stop shipping any further units until we figure this shit out. As compensation for this delay we will provide you a voucher for 5% off your next order for each day your unit is late. If we are 20 days late, your next order is absolutely free.
Again, sorry for the delay."
They may be doing amazing engineering but they are doing piss-poor business.
Just to clear here. Does the engineer think its a Corsair problem or a Corsair HX problem. I have a Corsair AX1200
tks
tks
I already point it out thread.
First of all it isn't pin 4, 5, or 6 (#1 to #12 is the first row). The PS-ON pin is #16. When it is connected to ground (and ground) that will pull the voltage low. This is the "signal" to the PSU to power the output rails ("turn on" although that isn't technically correct).
http://www.mupuf.org/images/wt-rpm/connector_atx_pinout.gif
Any ground pin will work equally fine. As you can see in the pinout above there are multiple ground pins in the ATX-24 connector and they all are exactly the same. You are just completing a circuit from the positive voltage on pin #16 to any ground. What you call #5 & #6 are #17 & #18 and they are both ground pins. So is the next pin (#19) and the one of the other side of PS_ON (#15) as well as both of the pins diagonally (#3 & #5). Hell you could even connect a wire from PS_ON to a bare screw on the power supply and it would work (UL listed PSU means the metal chassis is also grounded).
First of all it isn't pin 4, 5, or 6 (#1 to #12 is the first row). The PS-ON pin is #16. When it is connected to ground (and ground) that will pull the voltage low. This is the "signal" to the PSU to power the output rails ("turn on" although that isn't technically correct).
http://www.mupuf.org/images/wt-rpm/connector_atx_pinout.gif
Any ground pin will work equally fine. As you can see in the pinout above there are multiple ground pins in the ATX-24 connector and they all are exactly the same. You are just completing a circuit from the positive voltage on pin #16 to any ground. What you call #5 & #6 are #17 & #18 and they are both ground pins. So is the next pin (#19) and the one of the other side of PS_ON (#15) as well as both of the pins diagonally (#3 & #5). Hell you could even connect a wire from PS_ON to a bare screw on the power supply and it would work (UL listed PSU means the metal chassis is also grounded).
1) You explained it best when you said that kncminer guide that says pin 4 &5 and the guy who posted here who said pin 4&6 are actually meaning pin 16/14 and a ground pin, they are reading it wrong and backwards. I do not understand why they are doing that, but they are. You , yourself, are actually getting the pin numbers incorrect too -- saying #15, so i guess it is common.
2) What about taking the jumper out before turning off the PSU, is that good? it is what Redacted on here recommended.
mine core is dead only work with 0.90 and 0.91
i can not understand why?
Temperature sensor: 30.0 C
Die ID Cores ON Cores OFF %
0 0 48 0
1 0 48 0
2 0 48 0
3 0 48 0
i can not understand why?
Temperature sensor: 30.0 C
Die ID Cores ON Cores OFF %
0 0 48 0
1 0 48 0
2 0 48 0
3 0 48 0
I get the feeling Orama has me on his ignore list since he responded to pretty much everything except my posts 
HX 850 and HX 1050 is of same design, only difference is output as far as I know. So maybe it would be better to say be careful with the Corsair HX series.
Bitcoinorama, if I understand you correctly the issue only occurs after the ATX has shut down autoamtically.
When you then restart them they will do something odd, (i.e Voltage spike or something, Current surge seems odd as this would be an err on the Jupiter side).
this odd thing they are doing are frying the caps (Voltage spike => current surge) ore somethin.
This is exactly how our board was fried.
ATX shut down due to overload (
?)
When restarted... boom, smokes and fireworks.
did I get you right?
Bitcoinorama, if I understand you correctly the issue only occurs after the ATX has shut down autoamtically.
When you then restart them they will do something odd, (i.e Voltage spike or something, Current surge seems odd as this would be an err on the Jupiter side).
this odd thing they are doing are frying the caps (Voltage spike => current surge) ore somethin.
This is exactly how our board was fried.
ATX shut down due to overload (
?) When restarted... boom, smokes and fireworks.
did I get you right?
Precisely, that's what the GE guy stated. He said they surge for 30 seconds after reset, but after such time they are ok to switch off and on again, but by that time if your boards are connected, pop.
Was this fault reproduced in Da Lab? Scope/volt logger?
Of course! The tube screeny thing with a pen that you can never get the football on since all TV went digital, right?
For der fine werke like PSs, a $100 usb scope, a grabbyclip probe & a laptop
Edit: still find it difficult to believe that a brand name commercial PS that powered countless mobos without a hiccup turns out to be out of spec. Or were the caps bought at a Thai massage parlor?
HX 850 and HX 1050 is of same design, only difference is output as far as I know. So maybe it would be better to say be careful with the Corsair HX series.
Bitcoinorama, if I understand you correctly the issue only occurs after the ATX has shut down autoamtically.
When you then restart them they will do something odd, (i.e Voltage spike or something, Current surge seems odd as this would be an err on the Jupiter side).
this odd thing they are doing are frying the caps (Voltage spike => current surge) ore somethin.
This is exactly how our board was fried.
ATX shut down due to overload (?)
When restarted... boom, smokes and fireworks.
did I get you right?
Bitcoinorama, if I understand you correctly the issue only occurs after the ATX has shut down autoamtically.
When you then restart them they will do something odd, (i.e Voltage spike or something, Current surge seems odd as this would be an err on the Jupiter side).
this odd thing they are doing are frying the caps (Voltage spike => current surge) ore somethin.
This is exactly how our board was fried.
ATX shut down due to overload (
?) When restarted... boom, smokes and fireworks.
did I get you right?
Precisely, that's what the GE guy stated. He said they surge for 30 seconds after reset, but after such time they are ok to switch off and on again, but by that time if your boards are connected, pop.
Was this fault reproduced in Da Lab? Scope/volt logger?
Of course! The tube screeny thing with a pen that you can never get the football on since all TV went digital, right?
0.95 firmware seem to be working perfectly, power consumption, hash rate, rejects and hardware errors all improved 100%, ok, ok, I'm kidding... about 95% 
4 VRMs seem to be doing fine, but I've only been running for a few minutes, but looking great so far.
/joke
oh yeh, I realize why KnC removed the VRMs, they need to find Orama's wages from somewhere... I guess Orama doesn't come cheap, you know what those VRMs cost....
It costs for quality just like Orama
Did I just come up with the new slogan for the board..
/joke
4 VRMs seem to be doing fine, but I've only been running for a few minutes, but looking great so far.
/joke
oh yeh, I realize why KnC removed the VRMs, they need to find Orama's wages from somewhere... I guess Orama doesn't come cheap, you know what those VRMs cost....
It costs for quality just like Orama
Did I just come up with the new slogan for the board.. /joke
Email this to Sam, he's unlikely to see this otherwise!
Anyway I got to grab some shut eye. I'm an hour from where i'm staying and I need to grab 5 hours shut eye so I can let the GE guy in to work his magic tomo. Night!
HX 850 and HX 1050 is of same design, only difference is output as far as I know. So maybe it would be better to say be careful with the Corsair HX series.
Bitcoinorama, if I understand you correctly the issue only occurs after the ATX has shut down autoamtically.
When you then restart them they will do something odd, (i.e Voltage spike or something, Current surge seems odd as this would be an err on the Jupiter side).
this odd thing they are doing are frying the caps (Voltage spike => current surge) ore somethin.
This is exactly how our board was fried.
ATX shut down due to overload (?)
When restarted... boom, smokes and fireworks.
did I get you right?
Bitcoinorama, if I understand you correctly the issue only occurs after the ATX has shut down autoamtically.
When you then restart them they will do something odd, (i.e Voltage spike or something, Current surge seems odd as this would be an err on the Jupiter side).
this odd thing they are doing are frying the caps (Voltage spike => current surge) ore somethin.
This is exactly how our board was fried.
ATX shut down due to overload (
?) When restarted... boom, smokes and fireworks.
did I get you right?
Precisely, that's what the GE guy stated. He said they surge for 30 seconds after reset, but after such time they are ok to switch off and on again, but by that time if your boards are connected, pop.
Was this fault reproduced in Da Lab? Scope/volt logger?
Hosting Update:
0.95 FW update on my hosted units worked and they all seem to be hashing between 450-550GH.
1 out of the 11 is dead or unresponsive
1 might be having issues with going down randomly but I'm monitoring this one.
9 out of 11 going strong so far.
Did 0.95 fix anyone else that had KnC Hosting/datacenter issues?
0.95 FW update on my hosted units worked and they all seem to be hashing between 450-550GH.
1 out of the 11 is dead or unresponsive
1 might be having issues with going down randomly but I'm monitoring this one.
9 out of 11 going strong so far.
Did 0.95 fix anyone else that had KnC Hosting/datacenter issues?
Jump to: