Swedish ASIC miner company kncminer.com

[Biomech]

Tldr
Blah blah whiny whiner lies

So now you think you will be vindicated if neptunes don't ship on time or only produce 3th ? STFU. Anything you say is a prediction, nobody cares. Everything related to bitcoin has been a gamble you moron, show me a sure thing and I'll show you a lie. Like I said, you're gonna keep using that Jupiter till the day it isn't PROFITABLE!! Such a tool.

I predict that tomorrow, the sun will appear to rise in the east as the earth rotates. I'm not lying.


Sorry, man, I couldn't resist.

[Searing]

Tldr
Blah blah whiny whiner lies

So now you think you will be vindicated if neptunes don't ship on time or only produce 3th ? STFU. Anything you say is a prediction, nobody cares. Everything related to bitcoin has been a gamble you moron, show me a sure thing and I'll show you a lie. Like I said, you're gonna keep using that Jupiter till the day it isn't PROFITABLE!! Such a tool.

I predict that tomorrow, the sun will appear to rise in the east as the earth rotates. I'm not lying.


Sorry, man, I couldn't resist.

ack . you are lying this does not apply  to 1) the north pole or south pole 2) the international space station (so there)

[sickpig]

Just clicked Apply in each miner Networking Tab and the FREE changed to USED in the DHCP table:

https://i.imgur.com/em3yQah.png

That was probably the cause, but I have no idea why.

I'm glad you've found a solution.

I've to say that the miners' network stack is not the best their part, more than once I've found two or more dhclients running on the miner side. For me, switching to a manual network configuration have solved all the problems and glitches that seem related to the network stack, so far.

That is a good switch according to Amazon reviews - it is the best selling one with an average score of 4.7 out out of 5: http://www.amazon.co.uk/TP-Link-TL-SF1008D-100Mbps-Unmanaged-Desktop/dp/B000MGBOHA

I was not implying that your current switch isn't good, far from that. It was just a piece of advice that save me a lot of troubleshooting in the past, the cheapest route is not the safer one, usually.

[Biomech]

Tldr
Blah blah whiny whiner lies

So now you think you will be vindicated if neptunes don't ship on time or only produce 3th ? STFU. Anything you say is a prediction, nobody cares. Everything related to bitcoin has been a gamble you moron, show me a sure thing and I'll show you a lie. Like I said, you're gonna keep using that Jupiter till the day it isn't PROFITABLE!! Such a tool.

I predict that tomorrow, the sun will appear to rise in the east as the earth rotates. I'm not lying.


Sorry, man, I couldn't resist.

ack . you are lying this does not apply  to 1) the north pole or south pole 2) the international space station (so there)

Well Played, Sir! Well played!  I must bow to your wisdom...

[CYPER]

I've to say that the miners' network stack is not the best their part, more than once I've found two or more dhclients running on the miner side. For me, switching to a manual network configuration have solved all the problems and glitches that seem related to the network stack, so far.

What do you mean when you say "manual network configuration"?
Static IP addresses setup at the miner? or Reserved IP addresses setup at the router like me?

[sickpig]

I've to say that the miners' network stack is not the best their part, more than once I've found two or more dhclients running on the miner side. For me, switching to a manual network configuration have solved all the problems and glitches that seem related to the network stack, so far.

What do you mean when you say "manual network configuration"?
Static IP addresses setup at the miner? or Reserved IP addresses setup at the router like me?

The former (static ip at the miner)

[CYPER]

I've to say that the miners' network stack is not the best their part, more than once I've found two or more dhclients running on the miner side. For me, switching to a manual network configuration have solved all the problems and glitches that seem related to the network stack, so far.

What do you mean when you say "manual network configuration"?
Static IP addresses setup at the miner? or Reserved IP addresses setup at the router like me?

The former (static ip at the miner)

I tried that at first, but my router kept changing the IP addresses randomly.

[r1senfa17h]

Obviously, if the value of bitcoin skyrocketed, one would have done better by simply buying and holding. If I knew the future and knew that bitcoin would significantly increase in value, I would buy and hold.

I suppose significantly is the key word there. It's definitely going to rise over time. No surefire way to know how much time or value. B&H is one solid thing to do with these coins, in addition to mining.

With these numbers, I expect a Neptune to generate 7.5 BTC before it stops being profitable. I had no illusions about receiving more BTC than the ~12/each I spent. And yet I still bought three.

Finally, one of only a couple of us who is making a realistic projection. Mine was 4-6 with an upper of 12 depending on factors.

All I could do was shake my head in disbelief at the folks who bought Neptunes thinking they would crank out like 50 coins.

Realistic?
8 billion jump in one change in July?
57266 TH/s added to the network in a 10-12 days period?
That's 10K Neptunes at 5TH/s.

exactly.... not gonna happen

I hope you're right. I sincerely want you to be right. I have chosen to be pessimistic with my calculations because I know my natural optimism often gets the better of me while investing and I'm trying to counter it and prevent disappointment. Of course I realize that exponential growth is unsustainable forever. I know it's not done yet though, and I can't predict how much longer it will last.

[sickpig]

I've to say that the miners' network stack is not the best their part, more than once I've found two or more dhclients running on the miner side. For me, switching to a manual network configuration have solved all the problems and glitches that seem related to the network stack, so far.

What do you mean when you say "manual network configuration"?
Static IP addresses setup at the miner? or Reserved IP addresses setup at the router like me?

The former (static ip at the miner)

I tried that at first, but my router kept changing the IP addresses randomly.

I think this is due so a stale "udhcpc" (dhcpclient) floating around. If my theory is correct the problem will be fixed by a reboot or by killing the stale dhcpclient process (login via ssh; ps | grep dhcp; kill <stale_process_pid>).

 

[CYPER]

I've to say that the miners' network stack is not the best their part, more than once I've found two or more dhclients running on the miner side. For me, switching to a manual network configuration have solved all the problems and glitches that seem related to the network stack, so far.

What do you mean when you say "manual network configuration"?
Static IP addresses setup at the miner? or Reserved IP addresses setup at the router like me?

The former (static ip at the miner)

I tried that at first, but my router kept changing the IP addresses randomly.

I think this is due so a stale "udhcpc" (dhcpclient) floating around. If my theory is correct the problem will be fixed by a reboot or by killing the stale dhcpclient process (login via ssh; ps | grep dhcp; kill <stale_process_pid>).

 

Thanks.
How many of these should I see in the list?

  323 root      2148 S    udhcpc -b -x hostname Jupiter-1 eth0
14003 root      2152 S    grep dhcp
29312 root      2148 S    udhcpc -b -x hostname Jupiter-1 eth0

[sickpig]

Thanks.
How many of these should I see in the list?

  323 root      2148 S    udhcpc -b -x hostname Jupiter-1 eth0
14003 root      2152 S    grep dhcp
29312 root      2148 S    udhcpc -b -x hostname Jupiter-1 eth0

I think that one is enough. you should kill the one with the lower pid. But i'd prefer if you check it with someone else that is using the dhcp network settings.

usually there's only one dhclient for each network interface. If I were you I would simply reboot the miner and check how many udhcpc will be running.

but i'd dare to say that you could do this the next time a network glitch appear, this way you could use the downtime to test this solution without wasting mining time.

[isimme]

https://www.kncminer.com/categories/miners

Neptune Second Batch
41
Neptune is our first 20nm product and will be shipping in Q2 of 2014. This order is for the second batch which will leave about one month after the first batch
The stats and performance that we can release today are
Minimum 3000GH/s of hashing speed that 3TH Over 5 times the speed of our first Jupiter release
   (we reserve the right to increase this as we get closer to shipment)
A 30% reduction in watts per GH
Based on the existing Jupiter design (See photo, however this may change as development progresses)
Shipment begins in Q2 of 2014
Bitcoins first ever 20nm miner brought to you form the company who shipped the first 28nm bitcoin miner
Limited batch of 1200 units,
Payment for this product is bitcoins and bank transfer only.
$ 9,995.00

[flexgroo]

I am putting my order in now, just got the email from KNC telling me about the second batch, they say it should be delivered about 1 month after the first batch...

anyone have any idea on the diff by then? im guessing Apr maybe May... or should i just spend the 10k on btc, lol

[de_ixie]

I am confused - should be named 3rd batch - not second 

[jelin1984]

Any news about knc new firmware??

[helmax]

wht sells again?

like i say knc is kidding with us and our money

where network protection

where is 3000$ more other batch now is 10000

3600 machines

maybe are right calculation by other member we only get 7 bitcoins

mining is out control

[CYPER]

Thanks.
How many of these should I see in the list?

  323 root      2148 S    udhcpc -b -x hostname Jupiter-1 eth0
14003 root      2152 S    grep dhcp
29312 root      2148 S    udhcpc -b -x hostname Jupiter-1 eth0

I think that one is enough. you should kill the one with the lower pid. But i'd prefer if you check it with someone else that is using the dhcp network settings.

usually there's only one dhclient for each network interface. If I were you I would simply reboot the miner and check how many udhcpc will be running.

but i'd dare to say that you could do this the next time a network glitch appear, this way you could use the downtime to test this solution without wasting mining time.

Thank you. I posted my problem at my ISP forum and someone suggested a possible solution where Static IP addresses would not get changed by the router - I should set Static IP addresses that are not in the DHCP pool - anything below .64:

[r1senfa17h]

I've put up a new binary for knc devices based on the new cgminer 3.9.0 that has some fixes for the high hw error on rEligius problem people are having. Note it's not comprehensively better, and to make it work even better, it is much more reliable if you start cgminer with the extra options -q -T (quiet and text only).

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

I've noticed higher hashrates overall with this binary, along with substantially lower hardware error rates especially across block changes on any pool.

Thanks ckolivas! I've been running this for about 30 minutes on Eligius and it appears to have taken the HW error rate on my 6-module October Jupiter from 2.2% to 1.8%. I also like that the reported GH/s seems to line up much better with the WU, which means I should see the same hashrate at the pool as reported by cgminer .

[bobsag3]

Out of 6 nov jupiters, I now have 3 dead moduals, and a completely dead Jupiter. RMA is pretty fast... but Ill be down almost $1k in shipping by the time this is done. Seriously thinking about just chaging back the dead one... Not worth it after 2 weeks dead then another 3 weeks in RMA.

[CYPER]

Out of 6 nov jupiters, I now have 3 dead moduals, and a completely dead Jupiter. RMA is pretty fast... but Ill be down almost $1k in shipping by the time this is done. Seriously thinking about just chaging back the dead one... Not worth it after 2 weeks dead then another 3 weeks in RMA.

They make you pay for shipping?