Swedish ASIC miner company kncminer.com

[kslavik]

Capitalising on the fact that I saw that dud cores are better disabled, here's an experimental binary that tunes things fairly aggressively:

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

First it enables all cores on startup (so it can take a while before it starts mining!)
Then it will disable cores after only 3 hw errors in a row, but staggers disabling of cores 5 seconds apart.
Then it tries re-enabling cores after only another minute, but staggers re-enabling them.
If the cores fail 3 times in a row, they're decommissioned at that point.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2

Was it done on purpose? Can we get it back, please?

[Phoenix1969]

Capitalising on the fact that I saw that dud cores are better disabled, here's an experimental binary that tunes things fairly aggressively:

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

First it enables all cores on startup (so it can take a while before it starts mining!)
Then it will disable cores after only 3 hw errors in a row, but staggers disabling of cores 5 seconds apart.
Then it tries re-enabling cores after only another minute, but staggers re-enabling them.
If the cores fail 3 times in a row, they're decommissioned at that point.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2

Was it done on purpose? Can we get it back, please?

That's probably a temporary thing 'till the memory leak is isolated Ckilovas is working on.  It most likely stops the leak.  But I could be wrong.....

[Micky25]

just to inform u that there is something going on with Nov. batch...  

my Status (ordernumber 85xx) has changed from 'payed' to 'in progress'.

Thats the best news all week

My order still just shows "paid" order 93xx

so next week + 2 PH? Interesting..

[monsieur]

just to inform u that there is something going on with Nov. batch...  

my Status (ordernumber 85xx) has changed from 'payed' to 'in progress'.

Thats the best news all week

My order still just shows "paid" order 93xx

so next week + 2 PH? Interesting..

I am scared. Will November customers please show respect to us October customers and not start hashing for a while once you get your units.

[Xian01]

Hard day. KNCminer Water cooling upgrade.
Just photo.
May the Force be with you

 Very nice work ! Are you noticing any improvement with your hash-rate running them cooler like that ?

 Really looking forward to ordering a couple of these units when they become available again. Having a blast tuning/tinkering the Bitfury rigs, and looking forward to tinkering with KNC devices.

[jonoiv]

just to inform u that there is something going on with Nov. batch...  

my Status (ordernumber 85xx) has changed from 'payed' to 'in progress'.

Thats the best news all week

My order still just shows "paid" order 93xx

so next week + 2 PH? Interesting..

I am scared. Will November customers please show respect to us October customers and not start hashing for a while once you get your units.

I thought you said you only had a USB erupter?

[monsieur]

just to inform u that there is something going on with Nov. batch...  

my Status (ordernumber 85xx) has changed from 'payed' to 'in progress'.

Thats the best news all week

My order still just shows "paid" order 93xx

so next week + 2 PH? Interesting..

I am scared. Will November customers please show respect to us October customers and not start hashing for a while once you get your units.

I thought you said you only had a USB erupter?

No, back then I meant KNC should help those newbie miners who are being introduced to bitcoin with Erupters by delaying November orders. I am a Saturn October customer (then upgraded to 5-unit machine). I also did a preorder of November, but was dumb enough to cancel it. So the only way for me not to feel too bad about this cancellation is if November units are delayed  

[DPoS]

Thanks guys.  That is a little disheartening.  Efficiency is really going to be key going forward.  Midsize miners will need lots of hashrate with minimal electric use to stay competitive.

no it is meaningless here.

I did the math in another thread but if it costs $100 electricity to run 2 jupiters and right now 2 jupiters will get you about ~25 BTC the next 30 days it doesn't matter if that power bill is $50, $100 or $300 compared to 25x$800=$20,000

so perhaps you could save $50 per month the next 6 months with some other lower power cost (vaporware) miner?  $300 over 6 months vs $XXX,XXX

Just make sure you keep your KNC miners running as close to 24/7 and all chips hashing as much as possible and enjoy the extra heat if it is winter in your area

[warhawk187]

I got an attack of the network lags after upgrading to 0.99  

Downgrading didn't help, powering down, restarting and rebooting didn't help. Even with cgminer not running ping times can take up to 2 seconds. SSH'ing in is excruciatingly slow. One time I couldn't even ssh in until I restarted it again. I just barely got it mining again. I saw others had gremlins that went away, but I can't seem to find any way to repair it.

I would try a different ethernet cable and/or switch.

I have a 4th module that was working a couple days ago, that now refuses to kick on. I haven't tried heating up much and have tried alternating ports and running enablecores and still nothing. Warming it up is my next option but does anyone have a proven method on getting a Die to come back? I had 2 not detected and managed to find ports where 3 'liked' being plugged into. But I have not eliminated all the combinations yet because I don't know if I should be power cycling these so frequently.

Flashing to 0.91 worked to get it to detect all 4 cores at one point, but haven't had luck since.

Have you checked the power cable or tried a different one?

You mean the blue PCI-E cable? I tried connecting it to different PCI-E connections with my PSU (1050W XFX Gold) I have tried different ports and still nothing. I will try to get it a little warm next.

[Bogart]

I have a 4th module that was working a couple days ago, that now refuses to kick on. I haven't tried heating up much and have tried alternating ports and running enablecores and still nothing. Warming it up is my next option but does anyone have a proven method on getting a Die to come back? I had 2 not detected and managed to find ports where 3 'liked' being plugged into. But I have not eliminated all the combinations yet because I don't know if I should be power cycling these so frequently.

Flashing to 0.91 worked to get it to detect all 4 cores at one point, but haven't had luck since.

Have you checked the power cable or tried a different one?

You mean the blue PCI-E cable? I tried connecting it to different PCI-E connections with my PSU (1050W XFX Gold) I have tried different ports and still nothing. I will try to get it a little warm next.

I mean change the blue cable itself for another one, or remove the blue cable altogether and plug the PS cable directly into the module.

[DPoS]

Capitalising on the fact that I saw that dud cores are better disabled, here's an experimental binary that tunes things fairly aggressively:

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

First it enables all cores on startup (so it can take a while before it starts mining!)
Then it will disable cores after only 3 hw errors in a row, but staggers disabling of cores 5 seconds apart.
Then it tries re-enabling cores after only another minute, but staggers re-enabling them.
If the cores fail 3 times in a row, they're decommissioned at that point.

Awesome. Thanks, ckolivas.

I'll fire it up now and report back my results after it has a chance to stabilize.

good work..  I suggested something similar eons ago but way before they gave up the keys to the code castle

hopefully the tuning application they are working on will have this ability in it as well (configurable)
this will allow our miners to stay more consistent than the crazy fluctuation

[DPoS]

Go back to 0.98.1, it's more reliable for many. Most people abandonded 0.99 as a lame duck.

98.1 beta seems to be the best in my book.. I run that on both of my 5 board Neptunes (or whatever we want to call them)

the newer cgminers are starting to have better features though, so hopefully we will be able to take those and run them on 98.1 beta  (unless there are some new files in .99 that I needs that I am not aware of)

[DPoS]

more great news for the bitcoin community

What's wrong with the regular condoms?

[lemonte]

just to inform u that there is something going on with Nov. batch...  

my Status (ordernumber 85xx) has changed from 'payed' to 'in progress'.

Thats the best news all week

My order still just shows "paid" order 93xx

Anyone know for certain that production has started ?

[RenHoek]

just to inform u that there is something going on with Nov. batch...  

my Status (ordernumber 85xx) has changed from 'payed' to 'in progress'.

Thats the best news all week

My order still just shows "paid" order 93xx

Anyone know for certain that production has started ?

knc promissed at farest Tuesday(11-26) as start of Produktion,
what correspond well with the Status change from today, i think!


   

[kronut]

KNC was on Swedish TV per hno :

http://www.svt.se/nyheter/sverige/svenskt-bolag-i-centrum-for-bitcoin-utvecklingen

4th picture has their video.

[fubly]

Go back to 0.98.1, it's more reliable for many. Most people abandonded 0.99 as a lame duck.

98.1 beta seems to be the best in my book.. I run that on both of my 5 board Neptunes (or whatever we want to call them)

the newer cgminers are starting to have better features though, so hopefully we will be able to take those and run them on 98.1 beta  (unless there are some new files in .99 that I needs that I am not aware of)

The file waas is new, i thing it does nearly the same what the old wasd does,
but i have no knowledge, which files handles this in fw 0.99.

We have to wait for the tuning suite, I think it will do this what happened with our RMA boards.

Reprogramm the eeproms on it.

[soapmodem]

Capitalising on the fact that I saw that dud cores are better disabled, here's an experimental binary that tunes things fairly aggressively:

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

First it enables all cores on startup (so it can take a while before it starts mining!)
Then it will disable cores after only 3 hw errors in a row, but staggers disabling of cores 5 seconds apart.
Then it tries re-enabling cores after only another minute, but staggers re-enabling them.
If the cores fail 3 times in a row, they're decommissioned at that point.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2

Was it done on purpose? Can we get it back, please?

That's probably a temporary thing 'till the memory leak is isolated Ckilovas is working on.  It most likely stops the leak.  But I could be wrong.....

As I mentioned in the official cgminer thread, the API works just fine, you just have to wait awhile for the new version to boot up due to the enabling of the cores at the beginning. Have a breather and congratulate yourself on making such a wise investment after launching it, and then do the normal 'screen -rd' ... or whatever it is you use.

[kslavik]

Capitalising on the fact that I saw that dud cores are better disabled, here's an experimental binary that tunes things fairly aggressively:

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

First it enables all cores on startup (so it can take a while before it starts mining!)
Then it will disable cores after only 3 hw errors in a row, but staggers disabling of cores 5 seconds apart.
Then it tries re-enabling cores after only another minute, but staggers re-enabling them.
If the cores fail 3 times in a row, they're decommissioned at that point.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2

Was it done on purpose? Can we get it back, please?

That's probably a temporary thing 'till the memory leak is isolated Ckilovas is working on.  It most likely stops the leak.  But I could be wrong.....

As I mentioned in the official cgminer thread, the API works just fine, you just have to wait awhile for the new version to boot up due to the enabling of the cores at the beginning. Have a breather and congratulate yourself on making such a wise investment after launching it, and then do the normal 'screen -rd' ... or whatever it is you use.

I'm pretty sure that API is NOT working, I'm running it for 3.8.2 for 2 hours already and even though I can see stats from Knc Miner webpage, I get this response from the cgminer API itself (i'm using 3rd party tool to connect to api): ..."Status":"E","Msg":"Invalid command". This response is an API response. So, it seems that most of the API commands were disabled. Version of cgminer 3.8.1 works just fine.

[Cablez]

Thanks guys.  That is a little disheartening.  Efficiency is really going to be key going forward.  Midsize miners will need lots of hashrate with minimal electric use to stay competitive.

no it is meaningless here.

I did the math in another thread but if it costs $100 electricity to run 2 jupiters and right now 2 jupiters will get you about ~25 BTC the next 30 days it doesn't matter if that power bill is $50, $100 or $300 compared to 25x$800=$20,000

so perhaps you could save $50 per month the next 6 months with some other lower power cost (vaporware) miner?  $300 over 6 months vs $XXX,XXX

Just make sure you keep your KNC miners running as close to 24/7 and all chips hashing as much as possible and enjoy the extra heat if it is winter in your area

Your math may be right but it disregards that the vast increase in BTC price is also going to bring about large increases in hashrate/difficulty with all the new 'get rich quick' thinking miners.  I personally have been asked about setting up BTC mines from 4 different people this week, it is just insane.  This is why efficiency gains are important to me because I certainly cannot get much cheaper electric where I live.