Swedish ASIC miner company kncminer.com

[The Avenger]

FAKE! That box is too sturdy and in too good shape to be a KNC shipping box.

[trepex]

Update: 1h Bitminter reported speed: 247Gh/s

Hello,

I am a DAY1 hosting customer (Saturn). I did not receive an email about the hosting.
As I did read about people having received their login credentials some hours ago, I called KnC.
Spoke to the guy with the Englisch accent. He asked for my order number, looked up something and
told me that a colleague would send out my login credentials within 5 minutes.

I received the e-mail after some minutes.

Logged in to the portal. My miner had been pre-configured to use the KnC pool.

I reconfigured it to use Bitminter and Slush as backup pool (yeah! the interface did allow for backup pools!) and after some minutes I saw traffic arriving at Bitminter.

Short term bitminter stats did show 220,204,95,240,224Gh/s. (Update: later seen 271Gh as well)
It looks like my miner at home is running at about >20Gh/s faster.

Ralf / trepex

[Paladin69]

Thanks KnC for lying about the network protection.

they didn't lie,  they showed concern.. let it unfold and see

  they aren't ASIC gods that can turn your whine into money

I disagree.  Well, except for whining that equates to uselessness.  But the ASIC game is now in their court and the bottom line is shipping to such a heavily populated area will damage those that invested in their NRE costs.  What they do DOES depend heavily on our bottom line.  Seems like a kick in the face.

I'm sick of whining too.  I was heavily invested in BFL.  I am just sick of getting fucked over.  Completely fucking sick of it.  I can't catch a break.  I don't want to make just enough so I have to spend it all on next-generation as well.  It does sound like this KnC China endeavor will be REALLY bad for us.  Wonderful for KnC I guess...

Everybody is just so god damn greedy.  I am tired of the rat race.

[timmmers]

Thanks KnC for lying about the network protection.

they didn't lie,  they showed concern.. let it unfold and see

  they aren't ASIC gods that can turn your whine into money

I disagree.  The ASIC game is now in their court and the bottom line is shipping to such a heavily populated area will damage those that invested in their NRE costs.  Seems like a kick in the face.

I'm sick of whining too.  I was heavily invested in BFL.  I am just sick of getting fucked over.  Completely fucking sick of it.  I can't catch a break.  I don't want to make just enough so I have to spend it all on next-generation as well.  It does sound like this KnC China endeavor will be REALLY bad for us.  Wonderful for KnC I guess...

Everybody is just so god damn greedy.  I am tired of the rat race.

..and they did say that they would not be selling rigs over winter if other companies didn't ..which despite being nonsense is the exact opposite of what they are doing in China, couldn't find a place more likely to flood the market than China. I'd put money on the whole mfg and logistics over there being much more efficient too.

[Vorksholk]

Has there been any info about when day 2 orders will ship? (Ones marked with the order info number to be shipping on day 2 of production).

[Puppet]

Everybody is just so god damn greedy.  I am tired of the rat race.

Why did you get in to it? Serious question, its not like this hasnt been predictable and predicted ad nauseum.
You thought you would be the only one greedy?

But hey, maybe this will cheer you up:

Last 120   10/10/2013 02:07   262666-262786   270 514 499   x1.43
http://dot-bit.org/tools/nextDifficulty.php

Looks like ~270M next difficulty. Could have been worse if that KnC datacenter was actually working .

[soy]

no progress... nmap says need to specify a host...i tried both desktop ip's, but that doesnt seem to give me anything.
there was a 0.0.0.0 ip address in wireshark...?  I tried everry ip address I found...the miner is running, the ethernet lights are pinging away..... huh...  I'm ready to get an ulcer

Try ipconfig /all and you'll probably see the .1 is  your gateway, the .51 is assigned to the machine you're using.  .255 should be the broadcast address of the subnet.  As I understand bridging, if done properly, the computers after the bridge should have addresses in the same subnet as the .1, .51 and .555.  So, the bridge isn't setup correctly I think.

Perhaps the bridging software you added is waking up with a setup IP address 239.255.255.250 or 224.0.0.2 and you can't access the setup page simply because you don't have a route to that address.

A typical home router, wifi or otherwise, has a single downlink and a single uplink port.  The single downlink port is internal and is assigned the address you designate as the gateway but come configured with the internal downlink (gateway) address as the lowest in the function downlink network.  Attached to this internal single downlink is possibly a 4 port ethernet switch which will appear on the back as four RJ45 ethernet connections; the internal downlink is also attached to a wifi port (if the router has wifi); and lastly the internal downlink port is attached to a DHCP server.  The internal uplink port is attached to an RJ45 ethernet port on the back marked uplink.

A home router has a setup page which has the same address as its gateway.  If you log into your wifi router on 192.168.43.1 and change the gateway address to 192.168.43.13, as soon as you click SAVE on the router setup page, you'll lose connectivity - so don't do that unless you want to hide your gateway.

The DHCP server has addresses it may assign and these are some distance numerically from the gateway.  A linksys router might give DHCP 50 addresses starting from 192.168.43.50 and end at 192.168.43.100.  Your router likely starts its DHCP addresses at 192.168.43.50.  You computer has likely been assigned 192.168.43.51 (judging by your graphic).  The address 192.168.43.50 was likely assigned to a tablet or nook or kindle sometime in the last 24 hours and the router remembered it and didn't assign it to your computer but arp -a doesn't show it because it isn't in use.

So, if the bridging/routing software you added to your computer isn't accessible, you need to put your computer on the same network as it is.

Say the routing software software is showing 239.255.255.250 as its IP address and you can't access it.  Let's try this:  Right click your wireless icon and disable wireless so you can't get to the internet.  Open a dos cmd box and do ipconfig /all and see if the wireless connection is still showing an address.  Release that address with ipconfig /release 192.168.43.51 and run ipconfig /all again and see that it has been released.

Right click your ethernet icon and open network connections.  Go to your Local Area Connection properties and scroll down to Internet Protocol (TCP/IP), highlight and click Properties.  It might have DHCP ticked.  Unclick it and assign this address 239.255.255.249, netmask 255.255.255.0, gateway 239.255.255.001, click OK

Now, in your dos box, command "route print" and see if a route to net 239.255.255.0 exists and trying entering http://239.255.255.001 in your browser address field.  With luck that's the bridging software's setup page.  If not try http://239.255.255.250 in your browser field.

If neither of those work you might try the 224.0.0.0 network address since it's showing 224.0.0.2; assign the ethernet connection an address of 224.0.0.10, gateway 224.0.0.1, and try and access http://224.0.0.1 or http://224.0.0.2 after checking that a route has been added to 224.0.0.0/24

If you get to the bridging software setup page you can configure it with a 192.168.43.x address, then enable wireless, change your ethernet connection back to DHCP, reboot and see what crops up.

This is mostly guess work.

[Paladin69]

Everybody is just so god damn greedy.  I am tired of the rat race.

Why did you get in to it? Serious question, its not like this hasnt been predictable and predicted ad nauseum.
You thought you would be the only one greedy?

But hey, maybe this will cheer you up:

Last 120   10/10/2013 02:07   262666-262786   270 514 499   x1.43
http://dot-bit.org/tools/nextDifficulty.php

Looks like ~270M next difficulty. Could have been worse if that KnC datacenter was actually working .

I am not saying KnC doesn't deserve a lions share for the work they have done.  But a little respect for customer ROI would be fucking nice for once.

I'll agree I am jumping the gun.  I'll wait this out.  But that KnC China thing is certainly a kick in the balls.  I am late on this.  Just wasn't aware of it until recently.  They will still be incredibly wealthy without China.  It's almost as if the "Network Protection Statement" was designed to just get people to fill up their October slots.

[Puppet]

I am not saying KnC doesn't deserve a lions share for the work they have done.  But a little respect for customer ROI would be fucking nice for once.

Even if KnC voluntarily sacrificed its own revenue and profits for its old customers by halting or limiting production, it would hardly matter because Hashfast, Avalon, Bitfury, BFL, cointerra etc couldnt care less about old KnC customers' ROI. Its a race between vendors, and you are getting squeezed.

[xyzzy099]

no progress... nmap says need to specify a host...i tried both desktop ip's, but that doesnt seem to give me anything.
there was a 0.0.0.0 ip address in wireshark...?  I tried everry ip address I found...the miner is running, the ethernet lights are pinging away..... huh...  I'm ready to get an ulcer

Try ipconfig /all and you'll probably see the .1 is  your gateway, the .51 is assigned to the machine you're using.  .255 should be the broadcast address of the subnet.  As I understand bridging, if done properly, the computers after the bridge should have addresses in the same subnet as the .1, .51 and .555.  So, the bridge isn't setup correctly I think.

Perhaps the bridging software you added is waking up with a setup IP address 239.255.255.250 or 224.0.0.2 and you can't access the setup page simply because you don't have a route to that address.

A typical home router, wifi or otherwise, has a single downlink and a single uplink port.  The single downlink port is internal and is assigned the address you designate as the gateway but come configured with the internal downlink (gateway) address as the lowest in the function downlink network.  Attached to this internal single downlink is possibly a 4 port ethernet switch which will appear on the back as four RJ45 ethernet connections; the internal downlink is also attached to a wifi port (if the router has wifi); and lastly the internal downlink port is attached to a DHCP server.  The internal uplink port is attached to an RJ45 ethernet port on the back marked uplink.

A home router has a setup page which has the same address as its gateway.  If you log into your wifi router on 192.168.43.1 and change the gateway address to 192.168.43.13, as soon as you click SAVE on the router setup page, you'll lose connectivity - so don't do that unless you want to hide your gateway.

The DHCP server has addresses it may assign and these are some distance numerically from the gateway.  A linksys router might give DHCP 50 addresses starting from 192.168.43.50 and end at 192.168.43.100.  Your router likely starts its DHCP addresses at 192.168.43.50.  You computer has likely been assigned 192.168.43.51 (judging by your graphic).  The address 192.168.43.50 was likely assigned to a tablet or nook or kindle sometime in the last 24 hours and the router remembered it and didn't assign it to your computer but arp -a doesn't show it because it isn't in use.

So, if the bridging/routing software you added to your computer isn't accessible, you need to put your computer on the same network as it is.

Say the routing software software is showing 239.255.255.250 as its IP address and you can't access it.  Let's try this:  Right click your wireless icon and disable wireless so you can't get to the internet.  Open a dos cmd box and do ipconfig /all and see if the wireless connection is still showing an address.  Release that address with ipconfig /release 192.168.43.51 and run ipconfig /all again and see that it has been released.

Right click your ethernet icon and open network connections.  Go to your Local Area Connection properties and scroll down to Internet Protocol (TCP/IP), highlight and click Properties.  It might have DHCP ticked.  Unclick it and assign this address 239.255.255.249, netmask 255.255.255.0, gateway 239.255.255.001, click OK

Now, in your dos box, command "route print" and see if a route to net 239.255.255.0 exists and trying entering http://239.255.255.001 in your browser address field.  With luck that's the bridging software's setup page.  If not try http://239.255.255.250 in your browser field.

If neither of those work you might try the 224.0.0.0 network address since it's showing 224.0.0.2; assign the ethernet connection an address of 224.0.0.10, gateway 224.0.0.1, and try and access http://224.0.0.1 or http://224.0.0.2 after checking that a route has been added to 224.0.0.0/24

If you get to the bridging software setup page you can configure it with a 192.168.43.x address, then enable wireless, change your ethernet connection back to DHCP, reboot and see what crops up.

This is mostly guess work.

Those 239.x.x.x and 224.x.x.x addresses are multicast addresses that are not applicable to the problem you are trying to solve, I think.

http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml

[soy]

Have i just killed the Jupiter!?!

Just setup a new miner. Fired it up and recognized that one front-fan didnt work.

I didnt care cause without the case airflow should be OK. I started to change the setting via the webinterface and then the miner suddenly shut down.

I checked everything and found that the front-fan wasnt working cause a blade was STUCK!

So i "unstuck" it and fired the miner up again but NOTHING happens...........  

Whats going on???

Had the same prob...
Just switch it a few times on and of...

OK i will try that. thx!

Better not quickly toggle the on/off.  Switch it on and off a few times true but with 15 to 30 seconds, preferabley 30 seconds, between state change.  The fired/fried capacitors fault hasn't been identified yet and toggling the miner quickly on/off is begging for trouble.

[soy]

Thanks KnC for lying about the network protection.

they didn't lie,  they showed concern.. let it unfold and see

  they aren't ASIC gods that can turn your whine into money

I disagree.  The ASIC game is now in their court and the bottom line is shipping to such a heavily populated area will damage those that invested in their NRE costs.  Seems like a kick in the face.

I'm sick of whining too.  I was heavily invested in BFL.  I am just sick of getting fucked over.  Completely fucking sick of it.  I can't catch a break.  I don't want to make just enough so I have to spend it all on next-generation as well.  It does sound like this KnC China endeavor will be REALLY bad for us.  Wonderful for KnC I guess...

Everybody is just so god damn greedy.  I am tired of the rat race.

..and they did say that they would not be selling rigs over winter if other companies didn't ..which despite being nonsense is the exact opposite of what they are doing in China, couldn't find a place more likely to flood the market than China. I'd put money on the whole mfg and logistics over there being much more efficient too.

Negotiating with native Chinese buyers might be muy different than negotiating with us.

[rebelrat]

I am not saying KnC doesn't deserve a lions share for the work they have done.  But a little respect for customer ROI would be fucking nice for once.

Even if KnC voluntarily sacrificed its own revenue and profits for its old customers by halting or limiting production, it would hardly matter because Hashfast, Avalon, Bitfury, BFL, cointerra etc couldnt care less about old KnC customers' ROI. Its a race between vendors, and you are getting squeezed.

It's a Gold rush - so remember, in a Gold rush, only the people that sell the shovels get rich

[robix]

Are they shipping anything? Did anyone get a tracking number today?

[ur0pl]

I see stats about cores disabled and cores enabled/on. how come some cores get disabled? how come all the cores don't work. i dont understand. is something broken? not enough testing? not enough heatsinks?

[ImI]

Have i just killed the Jupiter!?!

Just setup a new miner. Fired it up and recognized that one front-fan didnt work.

I didnt care cause without the case airflow should be OK. I started to change the setting via the webinterface and then the miner suddenly shut down.

I checked everything and found that the front-fan wasnt working cause a blade was STUCK!

So i "unstuck" it and fired the miner up again but NOTHING happens........... 

Whats going on???

UPDATE:

Fan is working normal again.

Situation is like this:

I start the miner and everything is OK, i can access the webinterface and edit things.

After pretty exactly 1 min the miner shuts down abruptly... 

[Paladin69]

I am not saying KnC doesn't deserve a lions share for the work they have done.  But a little respect for customer ROI would be fucking nice for once.

Even if KnC voluntarily sacrificed its own revenue and profits for its old customers by halting or limiting production, it would hardly matter because Hashfast, Avalon, Bitfury, BFL, cointerra etc couldnt care less about old KnC customers' ROI. Its a race between vendors, and you are getting squeezed.

I just still haven't recovered from the Big Fucking Lie...or the "Long Con", however you want to put it.  And I'm wrongly blaming others for it.  It's just a shame that people who found out about something first got screwed instead of being rewarded for it.

Yep, I guess we're all suckers being sold shovels.  But these companies need to understand that as well.  I guess they don't care to be in business for more than 6 months.  At least the top brass.  The difficulty is going to run away from everyone.

[cognoscente]

Have i just killed the Jupiter!?!

Just setup a new miner. Fired it up and recognized that one front-fan didnt work.

I didnt care cause without the case airflow should be OK. I started to change the setting via the webinterface and then the miner suddenly shut down.

I checked everything and found that the front-fan wasnt working cause a blade was STUCK!

So i "unstuck" it and fired the miner up again but NOTHING happens...........  

Whats going on???

UPDATE:

Fan is working normal again.

Situation is like this:

I start the miner and everything is OK, i can access the webinterface and edit things.

After pretty exactly 1 min the miner shuts down abruptly...  

what's the make and model of the power supply? Did you use a paper clip?

[cognoscente]

I am not saying KnC doesn't deserve a lions share for the work they have done.  But a little respect for customer ROI would be fucking nice for once.

Even if KnC voluntarily sacrificed its own revenue and profits for its old customers by halting or limiting production, it would hardly matter because Hashfast, Avalon, Bitfury, BFL, cointerra etc couldnt care less about old KnC customers' ROI. Its a race between vendors, and you are getting squeezed.

I just still haven't recovered from the Big Fucking Lie...or the "Long Con", however you want to put it.  And I'm wrongly blaming others for it.  It's just a shame that people who found out about something first got screwed instead of being rewarded for it.

Yep, I guess we're all suckers being sold shovels.  But these companies need to understand that as well.  I guess they don't care to be in business for more than 6 months.  At least the top brass.  The difficulty is going to run away from everyone.

+1  They're acting like deer in the headlights.  Frozen with fear, unable to do the right thing.

[soy]

no progress... nmap says need to specify a host...i tried both desktop ip's, but that doesnt seem to give me anything.
there was a 0.0.0.0 ip address in wireshark...?  I tried everry ip address I found...the miner is running, the ethernet lights are pinging away..... huh...  I'm ready to get an ulcer

Try ipconfig /all and you'll probably see the .1 is  your gateway, the .51 is assigned to the machine you're using.  .255 should be the broadcast address of the subnet.  As I understand bridging, if done properly, the computers after the bridge should have addresses in the same subnet as the .1, .51 and .555.  So, the bridge isn't setup correctly I think.

Perhaps the bridging software you added is waking up with a setup IP address 239.255.255.250 or 224.0.0.2 and you can't access the setup page simply because you don't have a route to that address.

A typical home router, wifi or otherwise, has a single downlink and a single uplink port.  The single downlink port is internal and is assigned the address you designate as the gateway but come configured with the internal downlink (gateway) address as the lowest in the function downlink network.  Attached to this internal single downlink is possibly a 4 port ethernet switch which will appear on the back as four RJ45 ethernet connections; the internal downlink is also attached to a wifi port (if the router has wifi); and lastly the internal downlink port is attached to a DHCP server.  The internal uplink port is attached to an RJ45 ethernet port on the back marked uplink.

A home router has a setup page which has the same address as its gateway.  If you log into your wifi router on 192.168.43.1 and change the gateway address to 192.168.43.13, as soon as you click SAVE on the router setup page, you'll lose connectivity - so don't do that unless you want to hide your gateway.

The DHCP server has addresses it may assign and these are some distance numerically from the gateway.  A linksys router might give DHCP 50 addresses starting from 192.168.43.50 and end at 192.168.43.100.  Your router likely starts its DHCP addresses at 192.168.43.50.  You computer has likely been assigned 192.168.43.51 (judging by your graphic).  The address 192.168.43.50 was likely assigned to a tablet or nook or kindle sometime in the last 24 hours and the router remembered it and didn't assign it to your computer but arp -a doesn't show it because it isn't in use.

So, if the bridging/routing software you added to your computer isn't accessible, you need to put your computer on the same network as it is.

Say the routing software software is showing 239.255.255.250 as its IP address and you can't access it.  Let's try this:  Right click your wireless icon and disable wireless so you can't get to the internet.  Open a dos cmd box and do ipconfig /all and see if the wireless connection is still showing an address.  Release that address with ipconfig /release 192.168.43.51 and run ipconfig /all again and see that it has been released.

Right click your ethernet icon and open network connections.  Go to your Local Area Connection properties and scroll down to Internet Protocol (TCP/IP), highlight and click Properties.  It might have DHCP ticked.  Unclick it and assign this address 239.255.255.249, netmask 255.255.255.0, gateway 239.255.255.001, click OK

Now, in your dos box, command "route print" and see if a route to net 239.255.255.0 exists and trying entering http://239.255.255.001 in your browser address field.  With luck that's the bridging software's setup page.  If not try http://239.255.255.250 in your browser field.

If neither of those work you might try the 224.0.0.0 network address since it's showing 224.0.0.2; assign the ethernet connection an address of 224.0.0.10, gateway 224.0.0.1, and try and access http://224.0.0.1 or http://224.0.0.2 after checking that a route has been added to 224.0.0.0/24

If you get to the bridging software setup page you can configure it with a 192.168.43.x address, then enable wireless, change your ethernet connection back to DHCP, reboot and see what crops up.

This is mostly guess work.

Those 239.x.x.x and 224.x.x.x addresses are multicast addresses that are not applicable to the problem you are trying to solve, I think.

http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml

Yes, I see now:
The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private networks:

   10.0.0.0        -   10.255.255.255
   172.16.0.0      -   172.31.255.255
   192.168.0.0     -   192.168.255.255