Topic: Swedish ASIC miner company kncminer.com - page 1104. (Read 3050068 times)

The ram issue is created by the addition of unofficial mods that run simultaneous to the official firmware. They require optimisation. We have been in touch with the developer of those mods, as they are really useful, and we do want to consider supporting them, but in a means that does not deteriorate the long term performance of the product.

I do not doubt mods will occur, it's inevitable, and if all our boards start mysteriously dying of a similar symptom not present in our own they will be inspected for signs of stress, and if found to have been consequence of unofficial modding, then obviously RMA will be invalid.

Latter revisions of boards will undoubtedly be pushed harder as we learn the loads the chip is capable of, the chip itself is not the issue, but the boards themselves will require supporting components to undergo continuous revision.

Logic dictates unless the coin price vastly increases, and if hashrate takes a beating than a year long warranty is sufficient. That said the genesis block is already being proven incorrect.

In any case people will always demand an RMA and not mention how boards died. Sometimes it will be obvious, but rather they are the consequence of what was officially released.

I do not doubt mods will occur, it's inevitable, and if all our boards start mysteriously dying of a similar symptom not present in our own they will be inspected for signs of stress, and if found to have been consequence of unofficial modding, then obviously RMA will be invalid.

Latter revisions of boards will undoubtedly be pushed harder as we learn the loads the chip is capable of, the chip itself is not the issue, but the boards themselves will require supporting components to undergo continuous revision.

Does anyone know if it is OK to connect 2 of my modules from Jupiter 1 to Jupiter 2. I will move just the ribbon data cables over, so Jupiter 2 has 6 modules connected to it, but 2 of these are still powered by Jupiter 1 PSU.

I don't understand this ram issue....my Saturn has been running 0.97 for at least a week straight without a reboot.
And I only rebooted it then to change pools.

It doesn't slow down, it doesn't increase errors....it just keeps trucking along at 284.5gh.

Yep, I think the same about RMA.

But you know, if you don't do, will do somebody else......

Just an other question: Will you use this machine for one year? (No offense, and I know it's in law and other blah blah)

But I think KNC won't RMA fired boards. If somebody kill it, dot it at your own risk. If i push the VRM-s with a screwdriver under load and after that I can smell a bit smoke will you RMA my board?

If I fry the board with a 3rd party firmware will you make RMA?

If I fry the board with HALF offical frimware with some overclocking wich was made by the engineers who made the machine but there is a HUGE USE AT YOUR OWN RISK after the dl link will you make RMA?

I think you know the answer, like everybody.

Still no offense, I like KNC and you, but it would be better some half offical overclock then non offical.

But it's just my opinion.....

Yeah, but that would likely be a killer for the year long warranty given. Would be an RMA nghtmare bro...

By the way that "substandard cooling" you currently have is rated for 320 Watts;

http://www.arctic.ac/worldwide_en/products/cooling/cpu/freezer-30-co.html

It's way more than enough...

Yeah, but that would likely be a killer for the year long warranty given. Would be an RMA nghtmare bro...

By the way that "substandard cooling" you currently have is rated for 320 Watts;

http://www.arctic.ac/worldwide_en/products/cooling/cpu/freezer-30-co.html

It's way more than enough...

Hey O'rama!

They should make a firmware which doesn't care about watts and other bitching.....

Just run as fast as possible (maybe if it needs proper cooling). I think lots of us can do proper cooling and don't care this time about watts, just the hash power.

And yes, apply this FW for your own risk....

Just an idea....

So i will say it was the case on 80% of the units delivered between oct 3rd and oct 10th, my 2 jupiters + saturn pulled 2,2kW from the wall till they got fixed with 0.93

Umm, that's cool, but I can assure you not that's clearly not he case on all units. I have pictures of the one I took to Atlanta using a Kill-A-Watt, and there were enough witnesses that were present, including members of this forum (Bargraphics, Phin Gage), and representatives from competing companies that saw this for their own eyes. Also there's plenty in this thread amongst the first recipients to verify otherwise.

All

I have three firmware updates in this release,

For people wanting to go back to the original release of .90 it can be found here

www.kncminer.com/userfiles/file/kncminer-0.90.bin.

Note: This release uses more power and is only recommended if you are having issues with the later releases.

Well that is surprising given the results that later cropped up with overcurrent PSU's and exploding capacitors..do you have a link to those kill-a-watt photos from Atlanta?  I don't remember the values you saw there versus what was in the youtube video in Sweden.  And just to clarify..when I said "tweaked" I meant subsequent production machines, not the one you took to Atlanta.  In other words, my assumption was that the initial "beta" firmware or whatever you had then was running at say .8V and then when you guys decided on the production values for the boxes that were going to start shipping it was bumped to .9V for the added stability/speed benefits that brings.  I wasn't suggesting that you custom-tuned the Atlanta box.  But however it worked out in the order of events...there were definitely some growing pains in relation to power at the PSU and the power through the VRMs that had to be ironed out, as I know you are extremely familiar with

As for the 8/4 thing...well, you keep saying it didn't matter when the facts showed that it did.  There was a material difference in how those things ran before/after the change which had to be accounted for in new firmware.  Again, I don't think it was some malicious conspiracy or anything..but I do think it was a reckless change that was done without adequate testing which caused issues that had to be addressed further down the road.