Swedish ASIC miner company kncminer.com

[Crypto_Cumbrian]

You know, a lot of the problems people have had could have been prevented by a decent burn in period. It would be fine with buyers if it meant a day late delivery because the rigs would be hashing on the pool details given so it wouldn't mean any lost income. They would just be hashing there instead of at our end but where faults are so much easier to fix.

That's my thoughts exactly.

The Testing before shipping, should be against your Pool details (as provided for configuration) and then Shipped when the Unit achieves the advertised Hash Rate.

KNC has employed us all as unpaid beta testers.

[1714876537]

1714876537

[1714876537]

1714876537

[1714876537]

1714876537

[1714876537]

1714876537

[1714876537]

1714876537

[1714876537]

1714876537

[WastedLTC]

You know, a lot of the problems people have had could have been prevented by a decent burn in period. It would be fine with buyers if it meant a day late delivery because the rigs would be hashing on the pool details given so it wouldn't mean any lost income. They would just be hashing there instead of at our end but where faults are so much easier to fix.

That's my thoughts exactly.

The Testing before shipping, should be against your Pool details (as provided for configuration) and then Shipped when the Unit achieves the advertised Hash Rate.

KNC has employed us all as unpaid beta testers.

Things didn't work well til version 95 for many, do you really want them to hold onto the units til then???   Would be better to hash at 380 and then boost to 525 via firmware.

[mininganon]

I JUST GOT 48 F'ing cores online/a dead die is ALIVE, first try with enablecores.bin on firmware .94!

I'm glad.

Was getting a 486ghs(avg) in CG now getting after a few min 516ghs(avg) WOAH!! All I did was stop CGminer by pressing q inside it, then I applied the enablecores.bin and rebooted. I'm an 8 VRM Jupiter guys DO THIS, stop waiting.

so let check if I understand this correctly.

1) u where running on 0.94 @ 486GH/s
2) you have a die on one of your ASIC slot with all 48cores disabled.
3) you stopped cgminer
4) apply enablecore.bin from web interface
5) click on the reboot link in the web interface.
6) after that you're mining @ 516GH/s

is it right ?

HAHA yes I know it's wild! To be more specific my 5 second before was 505+- 10ghs with a usually solid 486 CG average. After the enablecore.bin procedure you reiterated above I'm getting 5 second going from 510 to 550ghs and a solid  514 avg as i type no issues to report at the moment. I'm going to let this run for a while and update later. Hopefully .94 doesn't play the slow down game with me anymore as it use to after 4-6 hours of hashing. If it does I'll just fix it with a halt and a 2 min cool down every 6 hours which puts me back on a plane for hours.

Becoming less hostile to KNC by the share lol

[sickpig]

I JUST GOT 48 F'ing cores online/a dead die is ALIVE, first try with enablecores.bin on firmware .94!

I'm glad.

Was getting a 486ghs(avg) in CG now getting after a few min 516ghs(avg) WOAH!! All I did was stop CGminer by pressing q inside it, then I applied the enablecores.bin and rebooted. I'm an 8 VRM Jupiter guys DO THIS, stop waiting.

so let check if I understand this correctly.

1) u where running on 0.94 @ 486GH/s
2) you have a die on one of your ASIC slot with all 48cores disabled.
3) you stopped cgminer
4) apply enablecore.bin from web interface
5) click on the reboot link in the web interface.
6) after that you're mining @ 516GH/s

is it right ?

HAHA yes I know it's wild! To be more specific my 5 second before was 505+- 10ghs with a usually solid 486 CG average. After the enablecore.bin procedure you reiterated above I'm getting 5 second going from 510 to 550ghs and a solid  514 avg as i type no issues to report at the moment. I'm going to let this run for a while and update later. Hopefully .94 doesn't play the slow down game with me anymore as it use to after 4-6 hours of hashing. If it does I'll just fix it with a halt and a 2 min cool down every 6 hours which puts me back on a plane for hours.

Becoming less hostile to KNC by the share lol

thanks again for sharing! I'm in your precise situation. to add some other info: I wasn't able to run my miners with .92 nor .93 due to very frequent cgminer restart so I sticked with 0.91 for quite a while. I've briefly use .94 and switch to .95 as soon as it was published.


One last question: On the "once" flaky die how many cores enabled do you have now ?

[MrHempstock]

Woke up to shipping emails from DHL today   

Excellent news! The one upside to waiting so long is at least you can stand on the shoulders of giants so to speak with regards to the setup and tweaking that's apparently necessary to get these miners running at full speed. Everyone's already gone through most of (hopefully) the headaches and learning curves.

[Biffa]

its a pool difficulty setting.... settable in your pool options/account page ..maybe...if they allow it
although eligius says the min diff doesnt work yet...it does now, for the last 2 days...

ok I use slush...mainly cause i'm always reading about eligius being down or getting dos attacks or some such

not sure if true what I see

Searing

Slush does automatic diff you can't manually change it.

[markm]

I hope DHL works better for you guys than UPS is working for me.

Friday I kept checking their website all night, by morning it still said the thing had eventually left Quebec having been checked by customs at the airport then to some town then checked by customs again then back to the airport then finally on route.

So I went downstairs to put instructions on the front door even though it apparently had not yet arrived in Halifax/Dartmouth yet.

But on the door was a notice saying they already attempted delivery.

I walked a couple blocks to the local UPS store because the website still showed it only leaving Quebec not yet in Nova Scotia.

They claimed its nothing to do with them, had me phone an 800 number, that said they will text message the driver. Took my phone number to call me back with instructions how to go pick it up or when the driver could be back with the package.

Monday morning, still no return phone call, I checked the sign was still on the door and that the website said it was on a truck on its way to be delivered.

A while later the website suddenly says a second delivery attempt has been made. I checked the door, no sign anyone has been here at all.

So now I have phoned the 800 number again, they claim within an hour I will hear back by phone from dispatch with instructions where to come myself to pick it up over in Dartmouth today...

They said their records show the person I talked to on the phone on friday did not escalate the thing at all, no message was sent by them to the driver nor the dispatch centre.

Not impressed with UPS at all...

I don't know who everyone else had been sending me stuff by, maybe FedEx or something, other packages in the past I have always been able to pick up here in Halifax after 4:30 pm when the truck finishes its route. UPS's canned recording claims one cannot do that, apparently their normal deal is you have to wait until they have made three separate attempts to deliver it on three different busness days and maybe only then might get to go pick it up, or maybe not even then since it also said something about sending it back to sender on same day as the third attempt. Really crappy "service"...

-MarkM-

[sickpig]

Yup! I've my PSU unboxed, cables ran, firmwares downloaded (0.97 being released today  ), list of hardware checks, immediate fan mod- I'm ready to roll.  

good for you!

fw 0.97? are you sure ?

[sickpig]

Yup! I've my PSU unboxed, cables ran, firmwares downloaded (0.97 being released today  ), list of hardware checks, immediate fan mod- I'm ready to roll.  

good for you!

fw 0.97? are you sure ?

According to KnC, yep

ok so they're planning to release 0.97 today, but it hasn't been released yet.

[sickpig]

Yup! I've my PSU unboxed, cables ran, firmwares downloaded (0.97 being released today  ), list of hardware checks, immediate fan mod- I'm ready to roll.  

good for you!

fw 0.97? are you sure ?

According to KnC, yep

ok so they're planning to release 0.97 today, but it hasn't been released yet.

Correct. I had e-mailed them regarding the status of my order(s) and had inquired on the performance issues people were having and Emilia stated a new FW will be on their site later today.

So Customer Support said that they'll release a new fw later this day, hopefully Emilia's right. Last CS said something like that we spent 3 days waiting

[the-skeptic]

So I am in Beijing for business and get my tracking number today (#3523 July 10). Good thing my brother is camping out on my couch waiting for the yellow truck full of magic

[markm]

This time UPS did phone back, they say I can go pick the thing up after 5pm at their depot in Dartmouth.

Why they couldn't do that back on Friday they didn't say.

-MarkM-

[soy]

Can anyone assist me?

Im trying to bridge the ethernet connection on my computer so I can login to my Mercury unit.
But I dont know what IP to hit in order to get into the config.

So say I directly connect my Jupiter to my laptop via ethernet, does anyone know what IP the machine will try to assign itself and what Windows might give it. Say if I try to bridge ethernet to ethernet?

1. undo the bridge
go to your connection properties on the laptop(of the actual internet connection, not ethernet), and turn DHCP ON under the ipv4 settings. assign it an ip address.
2.download advanced ip scanner, and prep it to scan the range you just used on the laptop.
3. cold start the miner.
4. Run the IP Scanner.. it will show knc after it finds it...takes about 30 seconds. you will need to scroll down the list to find it.
If it doesnt show right away, scan again right away.
once you have the IP, type it into chrome address bar, use admin/admin, and go directly to the networking page to program your IP in before anything else, or you will have to sniff it out all over again if you reboot for any reason.

IMPORTANT: remember to turn DHCP OFF (uncheck the box)on the miners GUI Networking page before you attempt to save the info.

Might try to get bridging working on an RPi but there's work to do on the truck, on the car, on the pumphouse roof, and a cold front is heading south this way, not to mention adding tantalum caps to the Merc Asic module and testing.

[The Avenger]

So I am in Beijing for business and get my tracking number today (#3523 July 10). Good thing my brother is camping out on my couch waiting for the yellow truck full of magic

They are only at #35xx? And today is the 4th day after their "3-5 days behind" on production announcement? The bullshit from KNC continues.

[DPoS]

I JUST GOT 48 F'ing cores online/a dead die is ALIVE, first try with enablecores.bin on firmware .94!

Was getting a 486ghs(avg) in CG now getting after a few min 516ghs(avg) WOAH!! All I did was stop CGminer by pressing q inside it, then I applied the enablecores.bin and rebooted. I'm an 8 VRM Jupiter guys DO THIS, stop waiting.

hope it lasts.. I brought one sickly die back twice and the second time it lasted about 8 hours and just went back to sleep.

Nothing can bring it back now, I think when this happens it is not really the chip but part of the board's other components (VRMs/caps) that fail it

but who knows, they are releasing another firmware - wish they gave release notes

[soy]

Got a RMA Number for 3 Faulty (under performing boards) on my Jupiter.

I asked about comp for my loss and for my Time , they will not offer any compensation.

Also the worrying thing is they Said and I Quote " The replacement boards can not be guaranteed to run at the Advertised speed as they are untested".

Well better go get some Thermal paste and await their return.

So they can''t test replacements before sending them? You could return bad boards and get more bad ones in return? That's poor.

Piss Poor.

Well the Boards are on the way to the post office.

My now 1 Board Jupiter is Hashing away at a Happy 140Gh/s on CGMiner and reporting 137Gh/s at BTC-Guild.

*Tip  T20 required for Case, T8 required for Board to case and a PH1 required for Heat-Sink cross bar.

My module took a T10.

[soy]

Looking at the rise in the bitcoin exchange rate I cant help but wonder if people are seeing that mining won't break even, or is unaffordable and are buying instead to a greater extent?

Maybe the miners arent selling.  Supply vs demand.

Possibly. Saving up for another round of nail biting on the next gen of rigs? lmao

ditto to get ROI back or double down say in feb for next round of "Searing vs the ASIC BEAST from non-fiat land"

Yes, I think it's go big or go home.  Will have to keep adding to hash power to stay up while those faint of heart or broke fold.

[DPoS]

You know, a lot of the problems people have had could have been prevented by a decent burn in period. It would be fine with buyers if it meant a day late delivery because the rigs would be hashing on the pool details given so it wouldn't mean any lost income. They would just be hashing there instead of at our end but where faults are so much easier to fix.

That's my thoughts exactly.

The Testing before shipping, should be against your Pool details (as provided for configuration) and then Shipped when the Unit achieves the advertised Hash Rate.

KNC has employed us all as unpaid beta testers.

Things didn't work well til version 95 for many, do you really want them to hold onto the units til then???   Would be better to hash at 380 and then boost to 525 via firmware.

THAT was because of the quick switch to 4 VRMs...  THEN they were in the situation you mentioned.

why they don't do burn in now on people's pool accounts is anyone's guess after .95 was released.  Probably too much of a logistic hassle

[soy]

Would really appreciate it if anyone getting a miner with fans knocked off in transit mark those ASIC modules some way that if later there's one or more modules with failing cores it can be noted as previously had the fan knocked off or not.

Theory: if a shock separated a solder point on the ball grid array of the ASIC module but still makes physical contact tho not flowed-solder contact, it will make a somewhat higher resistance point under current and raise temperature and that raised temperature will cause cores with gates at the hot spot to have more errors.

[DPoS]

Would really appreciate it if anyone getting a miner with fans knocked off in transit mark those ASIC modules some way that if later there's one or more modules with failing cores it can be noted as previously had the fan knocked off or not.

Theory: if a shock separated a solder point on the ball grid array of the ASIC module but still makes physical contact tho not flowed-solder contact, it will make a somewhat higher resistance point under current and raise temperature and that raised temperature will cause cores with gates at the hot spot to have more errors.

would be easier to mark the ones that the fans stayed on... but since they bounce around, anything can be hit from any fan