Topic: Swedish ASIC miner company kncminer.com - page 809. (Read 3050071 times)
I am confused - should be named 3rd batch - not second
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
anyone have any idea on the diff by then? im guessing Apr maybe May... or should i just spend the 10k on btc, lol
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
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
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.
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
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'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
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.
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.
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'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'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?
Tldr
Blah blah whiny whiner lies
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...
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.
Tldr
Blah blah whiny whiner lies
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)
Tldr
Blah blah whiny whiner lies
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.
Guys, I need you help with the weirdest problem:
Since yesterday my miners have started to disappear from my local network all of a sudden and that happens too often now.
All my miners are connected to a TP-Link TL-SF1008D 8-Port 10/100Mbps Unmanaged Desktop Switch, which is then connected to my router Technicolor TG582n (given by ISP):
https://i.imgur.com/8HmLmKO.png
When the problems happens the blinking light at the back of the router, where the switch is connected has gone off, yet the all 7 lights (6 miners + incoming cable) are ON.
Until yesterday I wasn't sure what is the problem, but now I know: when I unplug the switch from the router and plug it back in = they appear back in the network.
Additionally this morning my own PC reported network conflict: some other machine on the network got its IP too, which never happened.
+ I have setup the DHCP table manually. The 101 to 106 are the miners. Before it said state USED and now it is free, but they are hashing.
https://i.imgur.com/GPiLxxb.png
Do you have any experience with bad switches? Any ideas what is causing the issue?
Thank you.
Since yesterday my miners have started to disappear from my local network all of a sudden and that happens too often now.
All my miners are connected to a TP-Link TL-SF1008D 8-Port 10/100Mbps Unmanaged Desktop Switch, which is then connected to my router Technicolor TG582n (given by ISP):
https://i.imgur.com/8HmLmKO.png
When the problems happens the blinking light at the back of the router, where the switch is connected has gone off, yet the all 7 lights (6 miners + incoming cable) are ON.
Until yesterday I wasn't sure what is the problem, but now I know: when I unplug the switch from the router and plug it back in = they appear back in the network.
Additionally this morning my own PC reported network conflict: some other machine on the network got its IP too, which never happened.
+ I have setup the DHCP table manually. The 101 to 106 are the miners. Before it said state USED and now it is free, but they are hashing.
https://i.imgur.com/GPiLxxb.png
Do you have any experience with bad switches? Any ideas what is causing the issue?
Thank you.
if you could, just go down the road and buy a new switch, hopefully it is the cause of the problem. A 8 port switch cost almost nothing. buy a good one while at it.
Just clicked Apply in each miner Networking Tab and the FREE changed to USED in the DHCP table:
That was probably the cause, but I have no idea why.
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
Guys, I need you help with the weirdest problem:
Since yesterday my miners have started to disappear from my local network all of a sudden and that happens too often now.
All my miners are connected to a TP-Link TL-SF1008D 8-Port 10/100Mbps Unmanaged Desktop Switch, which is then connected to my router Technicolor TG582n (given by ISP):
https://i.imgur.com/8HmLmKO.png
When the problems happens the blinking light at the back of the router, where the switch is connected has gone off, yet the all 7 lights (6 miners + incoming cable) are ON.
Until yesterday I wasn't sure what is the problem, but now I know: when I unplug the switch from the router and plug it back in = they appear back in the network.
Additionally this morning my own PC reported network conflict: some other machine on the network got its IP too, which never happened.
+ I have setup the DHCP table manually. The 101 to 106 are the miners. Before it said state USED and now it is free, but they are hashing.
https://i.imgur.com/GPiLxxb.png
Do you have any experience with bad switches? Any ideas what is causing the issue?
Thank you.
Since yesterday my miners have started to disappear from my local network all of a sudden and that happens too often now.
All my miners are connected to a TP-Link TL-SF1008D 8-Port 10/100Mbps Unmanaged Desktop Switch, which is then connected to my router Technicolor TG582n (given by ISP):
https://i.imgur.com/8HmLmKO.png
When the problems happens the blinking light at the back of the router, where the switch is connected has gone off, yet the all 7 lights (6 miners + incoming cable) are ON.
Until yesterday I wasn't sure what is the problem, but now I know: when I unplug the switch from the router and plug it back in = they appear back in the network.
Additionally this morning my own PC reported network conflict: some other machine on the network got its IP too, which never happened.
+ I have setup the DHCP table manually. The 101 to 106 are the miners. Before it said state USED and now it is free, but they are hashing.
https://i.imgur.com/GPiLxxb.png
Do you have any experience with bad switches? Any ideas what is causing the issue?
Thank you.
if you could, just go down the road and buy a new switch, hopefully it is the cause of the problem. A 8 port switch cost almost nothing. buy a good one while at it.
Guys, I need you help with the weirdest problem:
Since yesterday my miners have started to disappear from my local network all of a sudden and that happens too often now.
All my miners are connected to a TP-Link TL-SF1008D 8-Port 10/100Mbps Unmanaged Desktop Switch, which is then connected to my router Technicolor TG582n (given by ISP):
When the problems happens the blinking light at the back of the router, where the switch is connected has gone off, yet the all 7 lights (6 miners + incoming cable) are ON on the switch.
Until yesterday I wasn't sure what is the problem, but now I know: when I unplug the switch from the router and plug it back in = they appear back in the network.
Additionally this morning my own PC reported network conflict: some other machine on the network got its IP too, which never happened.
+ I have setup the DHCP table manually. The 101 to 106 are the miners. Before it said state USED and now it is free, but they are hashing.
Just clicked Apply in each miner Networking Tab and the FREE changed to USED in the DHCP table:
Do you have any experience with bad switches? Any ideas what is causing the issue?
Thank you.
Since yesterday my miners have started to disappear from my local network all of a sudden and that happens too often now.
All my miners are connected to a TP-Link TL-SF1008D 8-Port 10/100Mbps Unmanaged Desktop Switch, which is then connected to my router Technicolor TG582n (given by ISP):
When the problems happens the blinking light at the back of the router, where the switch is connected has gone off, yet the all 7 lights (6 miners + incoming cable) are ON on the switch.
Until yesterday I wasn't sure what is the problem, but now I know: when I unplug the switch from the router and plug it back in = they appear back in the network.
Additionally this morning my own PC reported network conflict: some other machine on the network got its IP too, which never happened.
+ I have setup the DHCP table manually. The 101 to 106 are the miners. Before it said state USED and now it is free, but they are hashing.
Just clicked Apply in each miner Networking Tab and the FREE changed to USED in the DHCP table:
Do you have any experience with bad switches? Any ideas what is causing the issue?
Thank you.
@avenger
We've spent some of the day hashing (!) over warranty options for those chips of ours.
As I mentioned earlier today, the 10-day warranty was legal boilerplate. And we can and will give a longer warranty for the box, psu, and board.
But for the chips, we cannot realistically offer even a 90-day warranty.
Trolls are funny.
...
I do wonder - what else is going on today, that these repeated 'embarrassing' posts are supposed to distract us from?
Amy
.... Who is somewhat regretting her decision to hang out on the forums this afternoon.
P.S. If people DO have other questions about HashFast, please feel free to send them my way.
Ask if they're still on schedule for shipping next week.
Not surprisingly, this was indeed one of the questions that came up last night.
And, as of a few days ago, ... ... it looks like we're probably going to slip, by about a week.
For our mining rigs we have chosen to specify power supplies that are rated 20% higher than the highest wattage we expect even including significant overclocking. The GN chip uses 250W at nominal, and we have designed all the systems to handle upto 350W. When the mini motherboard is supplying 350W to the chip (this level of overclock should result in up to 540GH/s) the mini motherboard may consume up to 411W of 12v, due to losses in the VRM. Add 25W for fans, and you get to 436W per mini-motherboard.
So essentially roughly the same power efficiency as KNC, shipped late and at higher cost.
I'd like to write today about a small piece of why we are confident our product is better than KnCs.
So today's topic: Our silicon design is superior.
Both are 28nm designs, but HashFast's is far more powerful and energy-efficient.
....
One wafer of HashFast's chips has the same capacity as 11 to 16 wafers of KNCs. The initial engineering run from TSMC is limited to 12 wafers, out of which KNC will be able to satisfy 11 to 16 times fewer customers than HashFast will be able to. You'll get your units faster once production starts from us.
In addition, the HashFast chip operates much more efficiently. You get four times the hash rate for the same amount of power (250W)
So today's topic: Our silicon design is superior.
Both are 28nm designs, but HashFast's is far more powerful and energy-efficient.
....
One wafer of HashFast's chips has the same capacity as 11 to 16 wafers of KNCs. The initial engineering run from TSMC is limited to 12 wafers, out of which KNC will be able to satisfy 11 to 16 times fewer customers than HashFast will be able to. You'll get your units faster once production starts from us.
In addition, the HashFast chip operates much more efficiently. You get four times the hash rate for the same amount of power (250W)
Thanks for the details Simon.
If the chip is rated for 5years at 500GH, why is the warranty only 10 to 30 days?
.....If the chip is rated for 5years at 500GH, why is the warranty only 10 to 30 days?
We've spent some of the day hashing (!) over warranty options for those chips of ours.
As I mentioned earlier today, the 10-day warranty was legal boilerplate. And we can and will give a longer warranty for the box, psu, and board.
But for the chips, we cannot realistically offer even a 90-day warranty.
So you got the chips today? It's the 17th, your projected date for getting the chips from TSMC? Am i misremembering?
Trolls are funny.
...
I do wonder - what else is going on today, that these repeated 'embarrassing' posts are supposed to distract us from?
Amy
.... Who is somewhat regretting her decision to hang out on the forums this afternoon.
P.S. If people DO have other questions about HashFast, please feel free to send them my way.
I'm at a BTC meetup in Sunnyvale, where the Hashfast VP of Engineering is giving a talk right now.
This is admittedly rather time-sensitive, but if anyone has any questions, I'll be happy to ask 'em!
This is admittedly rather time-sensitive, but if anyone has any questions, I'll be happy to ask 'em!
Ask if they're still on schedule for shipping next week.
Not surprisingly, this was indeed one of the questions that came up last night.
And, as of a few days ago, ... ... it looks like we're probably going to slip, by about a week.
For our mining rigs we have chosen to specify power supplies that are rated 20% higher than the highest wattage we expect even including significant overclocking. The GN chip uses 250W at nominal, and we have designed all the systems to handle upto 350W. When the mini motherboard is supplying 350W to the chip (this level of overclock should result in up to 540GH/s) the mini motherboard may consume up to 411W of 12v, due to losses in the VRM. Add 25W for fans, and you get to 436W per mini-motherboard.
So.. we are starting to get some power numbers:
https://hashfast.com/second-tests/
So... we are looking at ~600W total for around ~500GH? Obviously the 25% extra hashrate is nice, but I thought we were expecting the total power to be under 1J/GH.
I guess that isn't going to happen unless we underclock.
https://hashfast.com/second-tests/
Quote
“We’ve got two dies up on this. Right now we are clocking it at 700mhz and .84v core voltage. It’s doing 248Gh/s on only 2 dies! Half a Golden Nonce.
Consumption is around 300 watts total and 78C die temp.
Consumption is around 300 watts total and 78C die temp.
So... we are looking at ~600W total for around ~500GH? Obviously the 25% extra hashrate is nice, but I thought we were expecting the total power to be under 1J/GH.
I guess that isn't going to happen unless we underclock.
So essentially roughly the same power efficiency as KNC, shipped late and at higher cost.
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.
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.
Thank you for all that you have done!
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.
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.
Jump to: