Swedish ASIC miner company kncminer.com

[flexgroo]

What I believe this means was that there was an acceptable delay in payment for the wires and therefore the note acknowledges this.

Nothing's been finalised with respect to future Jupiter, or Neptune sales. Everything's been winding down here prior to Xmas with the exception of the engineers who are working through to meet some self imposed deadlines. There's some to and fro with Alchip before designs are finalised, and obviously for all concerned the sooner there is agreement with all parties the better so aside from Cust serv and finance it's still all hands on deck. I'm still coughing and spluttering, but a million times better than the tail end of Vegas, so thanks to all that said the kind words. Indeed the plane was a nightmare come landing. I couldn't equalise and my head felt it was about to detonate. I couldn't hear for 3 days. The fact I couldn't speak was largely seen as a blessing...

Anyway I see no reason why wire x-fers wouldn't be accepted for future purchase, but as it was mentioned above it does highlight the obstacles within traditional electronic payment

As always I think we all appreciate your efforts.....now to my next dilemma ...sell my oct Jupiter for coin and re-up on another Neptune or just run it till she winds down

hmmm..

Searing

how can you get another neptune? i thought they are sold out... i really wanted one, heck i might even take a 500 gh/s right now, anything is better then nothing, course a 500 gh/s might not make anything by the end of january

[DPoS]

how can you get another neptune? i thought they are sold out... i really wanted one, heck i might even take a 500 gh/s right now, anything is better then nothing, course a 500 gh/s might not make anything by the end of january

it'll give you some good heat till spring!

[Searing]

What I believe this means was that there was an acceptable delay in payment for the wires and therefore the note acknowledges this.

Nothing's been finalised with respect to future Jupiter, or Neptune sales. Everything's been winding down here prior to Xmas with the exception of the engineers who are working through to meet some self imposed deadlines. There's some to and fro with Alchip before designs are finalised, and obviously for all concerned the sooner there is agreement with all parties the better so aside from Cust serv and finance it's still all hands on deck. I'm still coughing and spluttering, but a million times better than the tail end of Vegas, so thanks to all that said the kind words. Indeed the plane was a nightmare come landing. I couldn't equalise and my head felt it was about to detonate. I couldn't hear for 3 days. The fact I couldn't speak was largely seen as a blessing...

Anyway I see no reason why wire x-fers wouldn't be accepted for future purchase, but as it was mentioned above it does highlight the obstacles within traditional electronic payment

As always I think we all appreciate your efforts.....now to my next dilemma ...sell my oct Jupiter for coin and re-up on another Neptune or just run it till she winds down

hmmm..

Searing

how can you get another neptune? i thought they are sold out... i really wanted one, heck i might even take a 500 gh/s right now, anything is better then nothing, course a 500 gh/s might not make anything by the end of january

sorry figure of speech ment some more Jupiters if they release them in the wild before the neptunes....(I confuse easy...according to the news media I'm a lemming in this bitcoin bubble)

[sickpig]

Next difficulty retarget occurs at block 276191.0 (eta 1.8 days): 1184765576.11 / +30.4% [est.]

wow.

every time KnC hits the market this kind of growth happens.

Anyone have an an idea of in what measure other asic vendors (bitmain, bitfury, avalon 2nd gen) contributed to this last jump?

I don't think there were a lot of KNC's shipped this difficulty.  Most of the November batch would have been shipped during the previous difficulty.

I suspect that most of the TH added this difficulty were probably from private mining operations.

you were right. this is an example $2 million+ bitcoin mining facility launched in Iceland .

/sarcasm

I'm not blaiming  KnC for having sold so much hashrate to a single entity.  I'm just wondering  how many others had the same idea and were able to stash enough hash power to make their project worthty.

[flexgroo]

well 500 gh/s be the min by jan to make anything or ROI?  I see the bfl 30 to 60 gh/s selling like crazy on ebay, for 500 plus dollars, and i dont see how they can even mine.. let alone all the usb miners at less then a gh/s

[Puppet]

well 500 gh/s be the min by jan to make anything or ROI? 

ROI is not dependent on hashrate. Its dependent on cost per hashrate. Costs and revenue scale pretty much linearly.
As for ROI, I never expected asic miners you buy from vendors to be profitable. Not back in March, not next March. There might be exceptions once in a while if you get lucky by being shipped early and other vendors being delayed, but on average IMO its a guaranteed (BTC denominated) loss.

[flexgroo]

ok now i am even more confused then before, lol..

the neptunes are 3 th/s they should make close to 1 btc a day? if so then hopfully they are paid for after a few weeks, then you have to worry about power bill i guess

Looks like i might just keep sending my btc into a cloud pool, and see what happens in the next few months, been trading for week now and am up to 3.5 bc, started at .60

[Bitcoinorama]

Next difficulty retarget occurs at block 276191.0 (eta 1.8 days): 1184765576.11 / +30.4% [est.]

wow.

every time KnC hits the market this kind of growth happens.

Anyone have an an idea of in what measure other asic vendors (bitmain, bitfury, avalon 2nd gen) contributed to this last jump?

I don't think there were a lot of KNC's shipped this difficulty.  Most of the November batch would have been shipped during the previous difficulty.

I suspect that most of the TH added this difficulty were probably from private mining operations.

you were right. this is an example $2 million+ bitcoin mining facility launched in Iceland .

/sarcasm

I'm not blaiming  KnC for having sold so much hashrate to a single entity.  I'm just wondering  how many others had the same idea and were able to stash enough hash power to make their project worthty.

That was all October. It's cloudhashing.

[Puppet]

ok now i am even more confused then before, lol..

the neptunes are 3 th/s they should make close to 1 btc a day?

At todays difficulty, yes. By the time you receive it, only a fraction of that, and by the end of next year, probably just bitcoin dust.
How much and how fast exactly difficulty will go up is anyone's guess, it depends among other things how many people think like you, but its not going to remain where it is now. A hint:

http://bitcoin.sipa.be/speed-lin-ever.png

[Bitcoinorama]

Ok, for those that like using Eligius, one of our software engineers has been working tirelessly y'day and this morn chasing ghosts to create a patch that fixes excessive hardware errors reported by CGMiner. We've seen this propagate more at Eligius than other pools we've tried.

So here's a fix for the issue that appeared to be in the KnC driver code of CGMiner.

Anyone on Eligius (Bargraphics for sure) care to confirm the improvement?

We've had it running for an hour on the box I was running around the States with the last couple of weeks, and there's a significant improvement, but we need more guinea pigs to confirm...

 Root cause of the problem: several work items were assigned the same
  work_id in the active works queue of the knc driver. Thus when good
  nonce report arrived from the FPGA, wrong work item was picked up from
  the queue, and submit_nonce evaluated that as an error.
  Fix: Limit the work_id counter update rate. Update it only to the number of
  works actually consumed by the FPGA, not to the number of works send.

https://github.com/KnCMiner/cgminer/commit/ff0dbafe804925c93dad5b74a4f040d12a20dcae

[merv77]

Hi Orama,

is this patch for both October and November Jupiters?

and how is it applied?

thanks

[helmax]

@orama how i apply that?
i use eligius have lot HW nov jupiter

[RickJamesBTC]

@orama how i apply that?
i use eligius have lot HW nov jupiter

I've said it like a dozen times in this thread. DON'T USE ELIGIUS with nov jupiters...

Didn't see oramas post above lol. Maybe.... just maybe I'll give them another shot. but ghash is working so damn well

[Bitcoinorama]

Hi Orama,

is this patch for both October and November Jupiters?

and how is it applied?

thanks

Yes, it applies to both October, and November Jupiters.

It's a source-code patch for the cgminer code. In this form it's for trial only by experienced users who are able to build from source code can use it.

Binary update for the general public will be released tomorrow - because we are still testing it.

[The Avenger]

To be fair to the ckolivas etc, shouldn't this read

create a patch that fixes excessive hardware errors reported caused by CGMiner KnC driver code of CGMiner.

when the bug stems from KNC driver code, not CGMiner?

[pvnamk19]

Hi Orama,

Any news for Nov. Miner tuning? My Jupiter has Die #0 problems and lost ~42GH/s on average.

Thanks!

[Bitcoinorama]

Hi Orama,

Any news for Nov. Miner tuning? My Jupiter has Die #0 problems and lost ~42GH/s on average.

Thanks!

There will be a tuning suite for Nov, but not this side of Jan, as everything there is winding down. There's just some ongoing Neptune work. There will also be the means to vary SPI clock frequency. I saw it in the original tuning suite as a feature, but that hadn't been developed into the recent release. It was purely part of a template I saw.

As for the spiteful comments above yours, it was clearly stated;

So here's a fix for the issue that appeared to be in the KnC driver code of CGMiner.

Nothing's hidden as to where the bug was situated, the changes have been published on GitHub for all to see. Stop trying to stir to the pot at every slight opportunity, it's clear I wasn't blaming Con for anything. Pathetic.

[CYPER]

There will be a tuning suite for Nov, but not this side of Jan, as everything there is winding down. There's just some ongoing Neptune work. There will also be the means to vary SPI clock frequency. I saw it in the original tuning suite as a feature, but that hadn't been developed into the recent release. It was purely part of a template I saw.

Can you please elaborate on what that option does as I believe many of us are just changing values without knowing what they actually do  
The voltage settings are clear, but the SPI voltage and frequency not so much. I know they are related to the communication between each board and the controller board, so do they increase the signal to noise ratio or am I talking rubbish  

[The Avenger]

Basically the results of my testing are: anyone running a KnC device on any pool is losing at least 10 to 20 Gh per Jupiter device due to false HW errors.

So - "good shares wrongly reported as HW errors" - we've all been losing mining revenue since October due to a bug caused by knc poor/untested driver code? Is this correct? I'd say that's pathetic.

And of course knc *don't* put their hands up and say "our fault, sorry". You just say it "appeared" to be in knc code, when it obviously is in the knc code. And you also say knc "create a patch that fixes excessive hardware errors reported by CGMiner", which implies it's a problem with CGMiner. Just the way it's worded suggests CGMiner is reporting an excessive number of hardware errors and you've created a patch to fix that. I'd say that's pathetic too.

But hey, I'll wait for the official apology from kfc for their poor coding and resultant losses for customers. Next newsletter?

[edgar]

facts are now considered spiteful?

how about misinformation, an abhorrent lack of taking responsibility for continuous failings and glorification of effort made by others??

how many times ave i asked about these million plus HW errors to be told, dont worry, its nothing, they dont count??

this is an exact repeat of the behaviour displayed when i repeatedly asked about the PCI-e cables & dead die issues and received not a single, honest relevant word until it was tacked onto the next batches guidelines as though it was never an issue to begin with and the dozen or so shitty firmware upgrades were never to blame.

whats really pathetic is the little girls who are scurrying to your undeserved defense as i type these few oft-ignored facts....again

and the continued reliance upon them as though forced ignorance is actual bliss.

better than BFL...big 'wow' i've had diarrhea better than BFL. certainly delivered more and faster.

better than avalon, maybe, and i do mean maybe... the rigs ARE more powerful but MUCH less stable & in my experience 'customer support' is about the same.

no replies or chastisement and scorn poured upon the victimS (plural) of the aforementioned beta mining rigs

whats swedish for chi?