Swedish ASIC miner company kncminer.com - page 1256.

soy

legendary

Activity: 1428

Merit: 1013

Quote from: texaslabrat on October 21, 2013, 01:21:25 PM

Quote from: soy on October 21, 2013, 01:17:16 PM

Quote from: soy on October 21, 2013, 01:05:01 PM

Quote from: soy on October 21, 2013, 12:54:47 PM

Quote from: Phoenix1969 on October 21, 2013, 12:43:05 PM

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network. A gateway on 192.168.1.1 is on network 192.168.1.0.

And got the RPI working as a router. It had an eth0 address 192.168.1.50 before. I added the Cisco USB adapter. That was given the address 192.168.1.116.

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well. Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked. Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse. Say you have a non-wireless router. Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

You guys are making integration into a wireless network waaaaay too difficult. I mean, if you enjoy creating Rube Goldberg inspired networks, then by all means don't let me stop you. However for those who want something a little more straight-forward, let me introduce you to:

http://www.amazon.com/gp/product/B003KPBRRW/ref=oh_details_o04_s02_i01?ie=UTF8&psc=1

What? spend more money?

soy

legendary

Activity: 1428

Merit: 1013

Quote from: Phoenix1969 on October 21, 2013, 01:20:35 PM

I tried wireless routers, bridges, modems, and smoke signals.....
the best/most stable connection to wireless I found, was thru a cheapo laptop & a simple ethernet switch. I have 2 desktops, and 3 miners connected to the web thru the laptop's wifi to the android.
Rock solid

This was my first attempt at wireless isolation. Nothing like the dependability of a cat5 connection so unless I hear thunder....

texaslabrat

newbie

Activity: 56

Merit: 0

Quote from: soy on October 21, 2013, 01:17:16 PM

Quote from: soy on October 21, 2013, 01:05:01 PM

Quote from: soy on October 21, 2013, 12:54:47 PM

Quote from: Phoenix1969 on October 21, 2013, 12:43:05 PM

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network. A gateway on 192.168.1.1 is on network 192.168.1.0.

And got the RPI working as a router. It had an eth0 address 192.168.1.50 before. I added the Cisco USB adapter. That was given the address 192.168.1.116.

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well. Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked. Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse. Say you have a non-wireless router. Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

You guys are making integration into a wireless network waaaaay too difficult. I mean, if you enjoy creating Rube Goldberg inspired networks, then by all means don't let me stop you. However for those who want something a little more straight-forward, let me introduce you to:

http://www.amazon.com/gp/product/B003KPBRRW/ref=oh_details_o04_s02_i01?ie=UTF8&psc=1

Phoenix1969

legendary

Activity: 938

Merit: 1000

LIR DEV

I tried wireless routers, bridges, modems, and smoke signals.....
the best/most stable connection to wireless I found, was thru a cheapo laptop & a simple ethernet switch. I have 2 desktops, and 3 miners connected to the web thru the laptop's wifi to the android.
Rock solid

soy

legendary

Activity: 1428

Merit: 1013

Quote from: soy on October 21, 2013, 01:05:01 PM

Quote from: soy on October 21, 2013, 12:54:47 PM

Quote from: Phoenix1969 on October 21, 2013, 12:43:05 PM

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network. A gateway on 192.168.1.1 is on network 192.168.1.0.

And got the RPI working as a router. It had an eth0 address 192.168.1.50 before. I added the Cisco USB adapter. That was given the address 192.168.1.116.

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well. Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked. Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse. Say you have a non-wireless router. Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

Darn 60 something unread messages I've got to catch on back there, got no work done outside, will do my mileage on my treadmill rather than on the road so at least I'll get in an hour running. Didn't get to adding caps to the ASIC module to test if it can then run better on 0.95. I have one die that keeps losing 1 to 3 cores and I think it's possibly the VRM getting the least cooling, but where does the time go. Isn't that a song? ...where does the time go?

Phoenix1969

legendary

Activity: 938

Merit: 1000

LIR DEV

Am I having a nightmare, or did KNC forget to give us an update?

xstr8guy

hero member

Activity: 784

Merit: 1004

Glow Stick Dance!

Quote from: timmmers on October 21, 2013, 11:36:27 AM

Oh, you cant blame Avenger for holding them to their confident promises that they made over and over. That is their mess completely. They seem to think that one rig displayed on 30th Sept. hashing over the spec is worthy of claiming ALL rigs are similar. A great many aren't close to spec. We didn't pay for a lucky dip. ALL rigs should meet the min stats.

No, but you did pay for 400Gh/s. Anything over that spec is gravy.

soy

legendary

Activity: 1428

Merit: 1013

Quote from: soy on October 21, 2013, 12:54:47 PM

Quote from: Phoenix1969 on October 21, 2013, 12:43:05 PM

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network. A gateway on 192.168.1.1 is on network 192.168.1.0.

And got the RPI working as a router. It had an eth0 address 192.168.1.50 before. I added the Cisco USB adapter. That was given the address 192.168.1.116.

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well. Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked. Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

soy

legendary

Activity: 1428

Merit: 1013

Quote from: Phoenix1969 on October 21, 2013, 12:43:05 PM

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network. A gateway on 192.168.1.1 is on network 192.168.1.0.

xyzzy099

legendary

Activity: 1066

Merit: 1098

Quote from: Paladin69 on October 21, 2013, 12:50:38 PM

Quote from: Templer on October 21, 2013, 12:48:00 PM

Quote from: Altomesi on October 21, 2013, 12:25:26 PM

Quote from: Phoenix1969 on October 21, 2013, 11:57:35 AM

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

If the pools were all ddos'd before a difficulty change, could that mess with the adjustment and keep it lower than it should?

I don't think so. The diff change is calculated based on how fast the last 2016 blocks were generated, right? So unless you DDOS them for the whole 2016 block run, it won't make much difference.

Templer

full member

Activity: 218

Merit: 100

Quote from: Bargraphics on October 21, 2013, 12:49:26 PM

Quote from: Templer on October 21, 2013, 12:48:00 PM

Quote from: Altomesi on October 21, 2013, 12:25:26 PM

Quote from: Phoenix1969 on October 21, 2013, 11:57:35 AM

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

Web server is down, pool is up. Pool is what matters however I'm sure they are aware of it and are working to remedy the web server.

Thx...thats really what matters! i give a shit about stats, the income have to be correct^^

sry for OT

Paladin69

hero member

Activity: 784

Merit: 1000

Quote from: Altomesi on October 21, 2013, 11:23:08 AM

Quote from: jelin1984 on October 21, 2013, 11:20:10 AM

he next difficulty is estimated to change by 34.72% to 360,699,846 on block #266,111. That should be 5 days 5 hours 59 mins 42 seconds from now.

Thanks for ruining my day... Wink

The final will go above 400m at this rate.

Paladin69

hero member

Activity: 784

Merit: 1000

Quote from: Templer on October 21, 2013, 12:48:00 PM

Quote from: Altomesi on October 21, 2013, 12:25:26 PM

Quote from: Phoenix1969 on October 21, 2013, 11:57:35 AM

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

If the pools were all ddos'd before a difficulty change, could that mess with the adjustment and keep it lower than it should?

Bargraphics

hero member

Activity: 518

Merit: 500

Every man is guilty of all the good he did not do.

Quote from: Templer on October 21, 2013, 12:48:00 PM

Quote from: Altomesi on October 21, 2013, 12:25:26 PM

Quote from: Phoenix1969 on October 21, 2013, 11:57:35 AM

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

Web server is down, pool is up. Pool is what matters however I'm sure they are aware of it and are working to remedy the web server.

Templer

full member

Activity: 218

Merit: 100

Quote from: Altomesi on October 21, 2013, 12:25:26 PM

Quote from: Phoenix1969 on October 21, 2013, 11:57:35 AM

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

Phoenix1969

legendary

Activity: 938

Merit: 1000

LIR DEV

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

soy

legendary

Activity: 1428

Merit: 1013

Quote from: soy on October 21, 2013, 09:23:18 AM

Quote from: Phoenix1969 on October 20, 2013, 07:56:48 PM

Quote from: OmegaNemesis28 on October 20, 2013, 07:45:17 PM

Can anyone assist me?

Im trying to bridge the ethernet connection on my computer so I can login to my Mercury unit.
But I dont know what IP to hit in order to get into the config.

So say I directly connect my Jupiter to my laptop via ethernet, does anyone know what IP the machine will try to assign itself and what Windows might give it. Say if I try to bridge ethernet to ethernet?

1. undo the bridge
go to your connection properties on the laptop(of the actual internet connection, not ethernet), and turn DHCP ON under the ipv4 settings. assign it an ip address.
2.download advanced ip scanner, and prep it to scan the range you just used on the laptop.
3. cold start the miner.
4. Run the IP Scanner.. it will show knc after it finds it...takes about 30 seconds. you will need to scroll down the list to find it.
If it doesnt show right away, scan again right away.
once you have the IP, type it into chrome address bar, use admin/admin, and go directly to the networking page to program your IP in before anything else, or you will have to sniff it out all over again if you reboot for any reason.

IMPORTANT: remember to turn DHCP OFF (uncheck the box)on the miners GUI Networking page before you attempt to save the info.

Might try to get bridging working on an RPi but there's work to do on the truck, on the car, on the pumphouse roof, and a cold front is heading south this way, not to mention adding tantalum caps to the Merc Asic module and testing.

Drat, dropped my whole network again.

Tried bridging RPI with wlan0 and eth0 on same network 192.168.1.0/24. I had been using the RPI for a mining proxy but shifted that load to another. Stock RPI. Added a Cisco USB 802.11g adapter and it came right up and was assigned an address. Added route "route 192.168.1.x (the eth0 IP) wlan0".

Then I woke up an old WinXP Home laptop having an address on the 192.168.1.0 network but plugged into the RPI eth0 port. On that I added a route "route add 192.168.1.y (RPI wireless IP address) eth0" and I could ping that address.

When I ran "route" no options on the RPI it showed a route with the computer name of the WinXP! So, the RPI had communicated with the WinXP laptop. But when I tried pinging the gateway of network 192.168.1.0, which of course is 192.168.1.1, it failed. I wasn't getting forwarded on the RPI.

So on the RPI I tried "sysctl -w net.ipv4.conf.all.forwarding=1" which I got from here (http://www.raspberrypi.org/phpBB3/viewtopic.php?f=36&t=52246) but it still didn't forward. so I tried going to a separate net as he had done, changed the eth0 port on the RPI to 192.168.2.x and tried to add a route between the two subnets on the Cisco E900 router but that's when my network crashed. Have it up now and still trying.

Altomesi

newbie

Activity: 19

Merit: 0

Quote from: Phoenix1969 on October 21, 2013, 11:57:35 AM

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

Crypto_Cumbrian

member

Activity: 113

Merit: 10

Quote from: tgerring on October 21, 2013, 11:36:01 AM

Quote from: sickpig on October 21, 2013, 09:59:18 AM

Quote from: DPoS on October 21, 2013, 09:53:40 AM

Quote from: soy on October 21, 2013, 09:50:15 AM

Would ROFL except it made me sad.

your theory seems to be true though.. my one board with the dead die runs significantly hotter than the rest and that is with it hashing at 75%

can't see anything with the eyes that stands out, and while it hashes at 75% not really worth it to keep shutting things down to fudge with it for now

maybe RMA it when KNC gets out of the woods

me too have a completely dead die but all my fans where in place (i've checked while unboxing).

this happens for the two jupiters I own. (so one bad asic slot ech jup)

the common thing is that both the "flaky" asics are marked with a #3 stickers.

edit1: i've asked to hno (OrSoC eng) on irc channel it there's a relation between number on sticker and quality and he said a "weak one", but he didn't say everything he knows imho (and I can understand him)

Any significance to the sticker numbers? All my Jupiter boards have a "1" and I've been running 525-550GH/s fairly consistently.

Not for me. All my boards have #1 on them. Three of them now on their way back to KNC via a RMA return.

jelin1984

legendary

Activity: 2408

Merit: 1004

again??

Topic: Swedish ASIC miner company kncminer.com - page 1256. (Read 3049528 times)