Topic: Swedish ASIC miner company kncminer.com - page 1206. (Read 3049524 times)

soy, phoenix1969, btc_uzr, (and all others I forget) WHO ARE THE UNOFFICIAL CUSTOMER SUPPORT TEAM for KNC,

I THANK YOU.

I know there many who have contributed their knowledge, expertise, and testing stats, you are included in that thank you.

I know there should be more honorable mentions, so please cont. to mention them in your replies....since this is the only true form of support we have currently. I do thank knc for their efforts as well, as they did surmount that mountain peek.

just plain crazy isn't?

My rig room is at 84 degree F, and my saturn is running the best it's ever ran....

btcg stats:
miner_knc   256.86 GH/s   44,536k (99.83%)

when before w/ extra fans and a/c I was at 220/230GH/s max at btcg....

I was right when I signaled two weeks ago at #kncminer channel that the Saturn seems to work better in higher temperature.
Now many people confirm it.
Going from 40-42 C to 48.5-50 C moves avg from 267 to 274 (at cgminer AND at the pool) and WU from 3850-3900 to 4010.

eligius pool anyone can connect?

i see errors in my cgminer

I have similar problems with my Saturn. Download bertmod and check the stats of your VRMs. You might have a bad unit or two. I have 3 bad VRMs out of my two boards. My guess is that with BAD VRMs you cannot update to the higher fw, probably because they are more well adjusted to work with the VRMs, and since some VRMs are not functioning [properly, or at all, like in my case], its causing the later fw to not work. The only fw I can get running stable is fw 0.9.4. Out of my Saturn, I am averaging 150gh/s.

Check with the bertmod patch, you might need to RMA the board. Or you could try all the tricks the good folks here have discussed. I've tried them all (other then disabling fans), and nothing fixed it.

Bertmod: http://forum.kncminer.com/forum/main-category/main-forum/6183-bertmod-0-2-unofficial-firmware-mod-feedback-thread

Well I still am getting the "Running (Connect to CGMiner API failed)" error from the web GUI.
Yes, I have cleared the cash on the browser, AND used a different browser.

More importantly I can tell it isn't doing anything because the pool isn't getting much work.

Looks like 0.96 isn't up to prime time for my Mercury.  Going back to 0.95 because at least that was hashing something.  Unless there is something else to do to get 0.96 to work?

Thanks,

_theJestre

Hotter is better! I had a supplemental house fan & turned it off. ASICs fans are unplugged. Only
left the tilted case fans on. FW 9.7 and Enablecores afterwards. No Bertmod yet. HW error rate
was 19% before. Hashrate was mid-250s before. WU was 3900ish before.
Considering putting the case back on also...

I doubt its the assembly. Its almost certainly because they chose not to test and bin the chips. All wafers have defunct chips and chips of varying quality, thats a given. Almost all asic manufacturers test their chips on the wafer, and then again once they are packaged, tossing out the broken ones and binning the others according to how well they perform (power consumption, clock speed, if applicable, number of working cores) and use different bins for different products (think various AMD or Intel chips with different clockspeeds), or combine good and not so good chips to get a more predictable end product (afaik, thats what BFL does).

KnC seems to solder all their chips on a module, and they will do a final assembly functional test, but whether you get 4 excellent or 4 mediocre chips or a mix of both is just a matter of luck.

Sort-a like buying any CPU/GPU -- some take clock better than others, no cause for complaints as long as all manage the datasheet specs.
If it becomes profitable in the future, KNC will sell you "Deluxe 1337 Black Edition," with 100% good cores guaranteed

I doubt its the assembly. Its almost certainly because they chose not to test and bin the chips. All wafers have defunct chips and chips of varying quality, thats a given. Almost all asic manufacturers test their chips on the wafer, and then again once they are packaged, tossing out the broken ones and binning the others according to how well they perform (power consumption, clock speed, if applicable, number of working cores) and use different bins for different products (think various AMD or Intel chips with different clockspeeds), or combine good and not so good chips to get a more predictable end product (afaik, thats what BFL does).

KnC seems to solder all their chips on a module, and they will do a final assembly functional test, but whether you get 4 excellent or 4 mediocre chips or a mix of both is just a matter of luck.

It's s shame that there seems to be such a variance in build quality between rigs, things like slack screws make me think whoever assembled these things probably hadn't much experience.

These formulae were posted by Kano in a KNC thread, they merely allow you to compute your hashrate properly:

https://bitcointalksearch.org/topic/m.3309728

ElGabo has:

11213824*2^32/(25*3600+2.5*60)
   5.3425410e+11
534 GH/s in accepted shares.

420356*2^32/(25*3600+2.5*60)
   2.0026792e+10
20 GH/s in hardware errors for less than 5% HW

72191.*2^32/(25.*3600.+2.5*60)
   3.4393565e+09
3.4 GH/s in rejected shares (538 GH/s full hashrate).


Which are outstanding values compared with what many people here, including me, have. Unfortunately it's hard to figure out what factors affect the real hashrates as most people do not post the source of their numbers and some others, like edgar, will prefer to cover the thread in flame instead of making some effort to search the threads, understand and cooperate.

My other question was if temperatures affect the output in your machine ElGabo, and if that affects HW (positively or negatively) but your HW is so low that your machine doesn't seem good to test this. Unless when the temperature is high (seeing that your screenshot shows very low temperatures) your hardware error rate goes much higher  (which would be the opposite of what people including Phoenix and DigginDeep just above seem to be seeing). Then we could see if that VRM output correlates. Is that the case?


tunctioncloud: 0.97 is horrible for my machine and many others.