Swedish ASIC miner company kncminer.com

[plasmoske]

Awesome. I guess you'll be at the Atlanta Bitcoin conference then

[The Avenger]

Unofficially, i'm currently assembling your kit, so cheers whoever gave them the Ikea chair assembly image.

You're welcome  

I've been asked if I'm free this weekend, but Mon is the 30th.

Time for your job interview. Bring a soldering iron, might be like this  

[Spelon]

@Bitcoinorama

Are you now officialy work for Knc miners? They have presented you an working unit what you wanted to see first before you accept the job offer.
Maybe premature, but if you are working for them now (you already are, kind of), I believe congrats are in order  
Great work my man!

Yes, they want me to stick around. Actually let me rephrase that; i've been forced to stick around in yesterday's clothing as they won't leave the factory until production is ramped up, and my clothing is in my hotel room, in Stockholm, that apparently wasn't needed.

They've asked my first official engagement to be to deliver a Jupiter to Becky and Austin, of Life on Bitcoin at the Atlanta Bitcoin Conference this coming weekend. Which is cool as it was my suggestion they get involved when I emailed them the Kickstarter fundraiser for the film a week after the original openday. However, I'm only happy to agree if i'm permitted access to a change of clothing from now, until then.

Unofficially, i'm currently assembling your kit, so cheers whoever gave them the Ikea chair assembly image.

Any guesstimates on how may kits that been completed? Waiting for a bat signal to light up so I can swing by and pick up the orders.

[sickpig]

Unofficially, i'm currently assembling your kit, so cheers whoever gave them the Ikea chair assembly image.

back to work then and stop wasting time posting on stupid forum

[kano]

...
Been meaning to ask for ages, which of the ASIC chips do you find the best/easiest to develop your code for?

It's not really the chip that matters, as much as it is the firmware to hardware combination.

Part of the reason why I wrote this thread:
https://asktom.cf/index.php?topic=294499.0

A good example of this is the BitFury chip.
About 25% of the chip doesn't work, it returns lots of bad nonces that you need to fix, and in the BitFury boards you have to do GPIO to it to mine on it with the RPi - horrific.

Yet the Burnin BitFury board will have a neat and tidy Firmware similar to the BTB Avalon chip boards he's already made and the only trick left will of course be handling the bad nonces it returns ... who knows maybe he'll solve that in the firmware also? (No idea - I expect he wont but it would be nice)
The firmware isn't 'awesome' but it works

Even better, the Klondike firmware is probably the best simple firmware so far, you send it commands as you like, and asynchronously it replies as it can answer each request. But the chips ... not really relevant.

The BFL firmware is way more complex, but you can ignore most of it, and then it becomes all very simple to use, and with the input and output queues in the firmware, you can easily keep the high hash rate chips from ever going idle.

What's left? Asicminer.
The AMU USB is a complete PITA coz they made it emulate an old Icarus, provide no temperature information and used an annoying USB chip in it.
The basic Icarus protocol is simply:
1) Send 64 bytes
2) Wait for 4 bytes
and that's it. Simple but completely lacking in any extra functionality, with no input queue so USB latency is "absolutely" high.
However, Since it is ridiculously slow, it doesn't matter that the USB latency per work item is large, since each work item takes over 10 seconds to process, so it is "relatively" low.

No one has got it perfect yet, and that's why that thread I created exists.
I have passed that information on to a few of the manufacturers when they have asked for my input over the past year, but hopefully more of them will actually take notice of most of it ...

[itod]

you will ssh into web interface of beaglebone.

How will this be done?

I found a guide to this
http://learn.adafruit.com/ssh-to-beaglebone-black-over-usb/overview
however, it requires a USB.

KNC have said they are disabling the USB on the beaglebone in their build, so is there another way?

Your device will either get fixed IP address in factory or it will get one from your router. If it will be fixed you'll get a documentation which one it is. If you get one from your router you have to log on to your router and see the IP of the newly added device. Once you know your IP proceed with the following step:
http://learn.adafruit.com/ssh-to-beaglebone-black-over-usb/ssh-with-windows-and-putty

[The Avenger]

you will ssh into web interface of beaglebone.

How will this be done?

I found a guide to this
http://learn.adafruit.com/ssh-to-beaglebone-black-over-usb/overview
however, it requires a USB.

KNC have said they are disabling the USB on the beaglebone in their build, so is there another way?

Your device will either get fixed IP address in factory or it will get one from your router. If it will be fixed you'll get a documentation which one it is. If you get one from your router you have to log on to your router and see the IP of the newly added device. Once you know your IP proceed with the following step:
http://learn.adafruit.com/ssh-to-beaglebone-black-over-usb/ssh-with-windows-and-putty

Cool. I saw Putty mentioned somewhere, now I get it.

[Bitcoinorama]

[-ck]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

What does a hardware error actually represent, is it a fault or something else?

The chip says "here's a share". Cgminer checks it and goes "nope, wrong". That's a hardware error. Could be for any number of reasons, including (worst case scenario) a design flaw.

[Bitcoinorama]

Unofficially, i'm currently assembling your kit, so cheers whoever gave them the Ikea chair assembly image.

You're welcome  

I've been asked if I'm free this weekend, but Mon is the 30th.

Time for your job interview. Bring a soldering iron, might be like this  

Haha, yeah that was it. They found it very funny. Thanks for that, appreciated!

[rizzman]

Has anyone seen the latest statistics from the Jupiter they have mining? It was fluctuating up to 800Ghz AND IS STABLE AT 650!

http://eligius.st/~wizkid057/newstats/userstats.php/17Czc8RVL3FU5T2MLx2zLbRnpfBNgH9vFo

[-Redacted-]

We need to add 20 more pages to this thread then.
O'rama - Did they see the Toyota version of that cartoon?

[-ck]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

ahh, and you are planning to do it? will you receive some KNC miner for testing and driver development?

Earlier on knc said they'd engage us early on in the development process... but then didn't, and wrote their own driver for cgminer. I can't predict what they'll do now and how that will impact on whether code will be merged or maintained in cgminer, but I will be asking for them to provide their driver code publicly.

[adrd]

What if 469GH/s is with 1% of chip working? Are we getting 46,9TH/s devices?!

[bobsag3]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

ahh, and you are planning to do it? will you receive some KNC miner for testing and driver development?

Earlier on knc said they'd engage us early on in the development process... but then didn't, and wrote their own driver for cgminer. I can't predict what they'll do now and how that will impact on whether code will be merged or maintained in cgminer, but I will be asking for them to provide their driver code publicly.

Sigh.
It really wouldn't be that hard for them y'know...

What if 469GH/s is with 1% of chip working? Are we getting 46,9TH/s devices?!

You would probably need a building to power that. or 2

[ASIC-K]

What if 469GH/s is with 1% of chip working? Are we getting 46,9TH/s devices?!

hahahah good one!

[ASIC-K]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

ahh, and you are planning to do it? will you receive some KNC miner for testing and driver development?

Earlier on knc said they'd engage us early on in the development process... but then didn't, and wrote their own driver for cgminer. I can't predict what they'll do now and how that will impact on whether code will be merged or maintained in cgminer, but I will be asking for them to provide their driver code publicly.

doesnt really matter though right? once you get your hands on one, you can make your own awesome driver anyway....

[The Avenger]

Unofficially, i'm currently assembling your kit, so cheers whoever gave them the Ikea chair assembly image.

You're welcome  

I've been asked if I'm free this weekend, but Mon is the 30th.

Time for your job interview. Bring a soldering iron, might be like this  

Haha, yeah that was it. They found it very funny. Thanks for that, appreciated!

No problem.

Let them know I called dibs on the first 1BTC they mined on the 1st jupiter. https://asktom.cf/index.php?topic=170332.msg3276905#msg3276905

I'm going to frame it and pin it to my wall (metaphorically speaking   ).

[canth]

Has anyone seen the latest statistics from the Jupiter they have mining? It was fluctuating up to 800Ghz AND IS STABLE AT 650!

http://eligius.st/~wizkid057/newstats/userstats.php/17Czc8RVL3FU5T2MLx2zLbRnpfBNgH9vFo

That could be more than one machine...maybe Jupiter + Mercury? I wouldn't give too much weight to those numbers unless we know that they're only running 1 Jupiter on those workers.

[-ck]

I've said this phrase too often, but "Excuse my ignorance", shouldn't CGMiner display the actual mining rate without having to do calculations?
When I look at my erupters mining, it is displaying 333MHash/s each, plain as day. Why not here?

That's because the implementation of the hashrate meter is driver dependent, and in this case, we didn't write the driver. When we do write the driver, the hashrate displayed is the effective valid hashrate only (i.e. not hardware errors).

ahh, and you are planning to do it? will you receive some KNC miner for testing and driver development?

Earlier on knc said they'd engage us early on in the development process... but then didn't, and wrote their own driver for cgminer. I can't predict what they'll do now and how that will impact on whether code will be merged or maintained in cgminer, but I will be asking for them to provide their driver code publicly.

doesnt really matter though right? once you get your hands on one, you can make your own awesome driver anyway....

Yes I'll support any device I have myself.

But I don't see confirmation that we'll be given hardware, and I'm not buying one.