 "But surely if we hand write "fragile" in marker pen, they'll know it's a piece of delicate electronics worth $8000 and handle it carefully?" Holy shit! There's actually a joke that goes along with that, which appears a little insenstive now. And as a result a miner was actually packed in that box by mistake. I actually drew that on there myself, but I swear that left with UPS in mint condition;  Thanks for posting that, that actually appears to have been damaged purposely and maliciously, and as far as i'm concerned should burn UPS's delivery contract.  And no Xialla, get your facts straight KnC is NOT ignoring complaints, they've ordered a lot stronger boxes, and are awaiting delivery of them, as mentioned earlier. I see, with the end pieces of foam, there are voids under the sides of the box that can easily implode to force. |
|
|
|
i still have no "miner settings" page when tab is pressed, but i was able to config cgminer thru the ssl...?  not bad for a saturn...eh? Best thing I've read all week, happy for you  @Biomech. Wasps then? Contains wasps, that's work? lol Beautiful. You're a lucky guy, KnC miners and you live in Hawaii. |
|
|
|
ps | grep cgminer
Ps ax doesn't work. It's nit the usual ps. It is the one that come with busybox
ps aux? |
|
|
|
why is the miner setting page totally blank? says webpage not available...?
Okay, back from working outside. The poster was correct, the # is the command prompt and if you add a user, when you login as the user the command prompt will be $ so if you see the # prompt you have root privileges, if you have the $ you have user privileges. did you run #cgminer --help or #cgminer --help | more if you are connecting to eligius then the command will be #cgminer -o stratum+tcp://mining.eligius.st:3334 -u (here put your bitcoin address to which the bitcoins will be sent) -p (anypassword) |
|
|
|
I now have the miner plugged directly to the laptop, which has access to the wifi...alot less garble, but still see no ip for the miner...
Eric, if you are sitting behind a router you can Nmap your network and find all the machines responding on port 80... PM me if you need help with this on a whole new day now... im on the knc page no miner window....  every other tab works...? im logged in on putty too, but dont kno commands...lol I put in screen ~r and it says screen terminating...? status page says cgminer is running... but when i click on miner tab...nada, blank browser page That's screen dash r not screen tilde r. try #ps aux | grep cgminer if you only see grep cgminer then it isn't running but if you see two line, the first is the one that started cgminer running when Jupiter booted. If only the one line saying grep cgminer, then you'll need to start cgminer. To start cgminer first see the commands: #cgminer --help Then when you decide how to configure it, start it up with #screen cgminer -o stratum+tcp://xxx.xxx.xxx.xxx --userpass xxxxx:yyyy or perhaps -u xxxx -p yyyy |
|
|
|
woke up and it just connected easy, now new problem...
no miner page!
i can ssl in i think... how to show the screen tho....is it "screen ~r" or something like that?
Yes. Download Putty, install Putty in your Windows machine. Double click the Putty icon. Enter the IP address and hit open. A box not unlike a dos command box will open and be black until the Jupiter responds. A login prompt will appear, enter what the manual says, then a password prompt, etc., you'll be connected via ssh as ssh is the default of Putty. Now you'll be at a command line. Command #pwd and your directory id will be displayed - so you know where you are. If you logged in a root it will say /root/. If you want to run as root, fine I suppose or you can add a user. Then give the command #screen -r and you should see cgminer, or if not try #screen -dr |
|
|
|
I'm guessing that voltage control suffers near zero current.
Yes, at zero current, voltage is zero. Happens when you turn the switch off. Otherwise, the PSU itself draws enough current to keep the constant voltage regulation circuitry regulating a constant voltage. I plan to power thru a 6 outlet strip having an off/on switch. When I want the miner off it's that switch that gets put off. The off/on power supply switches might be nice but the way those blown caps are appearing, I'm not going to use a power supply off/on switch. |
|
|
|
This whole 'blame the power supply' story sounds pretty suspect to me. The power supply can't 'force' current into a board... There is clearly a board design problem here, and it looks to me to be highly unlikely that any specific known-to-be-fully-standards-compliant power supply would be more likely to cause it, other than simply being capable of providing higher instantaneous current - which is clearly not a flaw in a power supply.
I imagine this will turn out to be something that happens when you do something like turning the power on and off at exactly the wrong cadence, or something like that. Somebody probably left a necessary diode out of the design.
Correct, and capacitors can't be damaged by having current applied "before they've discharged their load", nor could a PSU force current through one. Capacitors would be damaged by excessive voltage over their rated dielectric rating, and PSUs are designed to keep voltage constant through their rated current capacity. There's a great deal of bad/incorrect information being passed around here. I'm guessing that voltage control suffers near zero current. |
|
|
|
don''t turn it off and on a lot then.. That is what was causing the issue from what he said
which one tell that?
maybe that make chips faulty?
or make the psu wrong???
that particular PSU was sending more current so that cap couldn't handle getting hit again without discharging its high load It would be a voltage spike blowing the capacitor. I had a great old switching supply putting out 16.5VDC from an old heavy laptop. I had a zTex FPGA board mounted in a small box with fans. The small box had a voltage regulator on perf board to knock down the voltage from 16.5 to 12v. I added an off/on switch to the box. Big mistake. Flipped it off for some reason. Now with the off/on switch in place I wasn't unplugging the supply. The switching supply, floating, was looking at an open with the switch on off. A voltage built up and I was eventually startled with a BANG, very loud. A cap had blown. Could it be the switching supplies are being unplugged while still powered up, allowing a voltage buildup. Even if unplugged the reattached to power, that buildup of excessive voltage on the disconnected PCIE-4 leads might still be there. Plug it in a BAM. |
|
|
|
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.xhtmlYes, 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 |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
I now have the miner plugged directly to the laptop, which has access to the wifi...alot less garble, but still see no ip for the miner...
How many RJ45 ports does your wifi router have? Are you connecting more than one item to a cable modem? Cable modems (sometimes) come with a USB port and an RJ45 port. This does not mean you can use both. It's one or the other. If your home has a single computer to the cable modem then that's all the cable modem is going to accept. If one wants more than one computer to the cable modem one plugs the upstream port of a router to the cable modem and then has the multiple downstream port switches (RJ45 ports) and possibly wireless. When you boot a computer with DHCP to the cable modem it will not be assigned an IP address in the 192.168.xxx.xxx range but if you plug into the router, you will. If you connect wirelessly to the router you will also get assigned via DHCP an address in the 192.168.xxx.xxx range. Your computer shows an IP address of 192.168.43.51 I believe with a gateway of 192.168.43.1. The .43 is unusual. Still, if the wifi router is assigning addresses in the 192.168.43.0 net then you should be able to plug your computer cat5 RJ45 cable into the back of the wifi router and boot and still get assigned a 192.168.43.0 net address. There should be more than one RJ45 downlink port on the wifi router. Plug both the computer and the Jupiter into different RJ45 ports on the wifi router. Boot the computer, boot the Jupiter, open a browser on the computer and go to http://192.168.43.1, log into your wifi router, go to status, go to local network, bring up the DHCP client table, see what DHCP addresses have been assigned, and there should be two, the one assigned to your computer and one assigned to the Jupiter. Open putty on the computer, input the address assigned to the Jupiter, open, sign into the Jupiter. You're home free. |
|
|
|
I now have the miner plugged directly to the laptop, which has access to the wifi...alot less garble, but still see no ip for the miner...
Close. Now try plugging it directly into the router. Nah, he's surreptitiously trying to connect to a neighbor's router to run his Hawaii Jupiter. |
|
|
|
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 I think I read somebody else having a similar failure which resolved when he replaced the cat5 cable. There is a DHCP server working as two of the base network (192.168.43.0/24) addresses are dynamic not static. The server should assign addresses in its range to the bridged devices. So, again, I think the bridge isn't set up properly. If the bridge is set up properly he should be able to run a cable to the bridge from a laptop, boot the laptop with DHCP for it's interface IP assignment, and get assigned an address on that laptop in the 192.168.43.0 network, say 192.168.43.100 which he would ascertain by bringing up a dos cmd box on the laptop and using ipconfig /all. Are you sure a bridge is what you want? Perhaps you want a repeater. Linksys shows bridging to be adding ports to the original router. Your router might have a 4 port switch on the back and be able to assign any number of IP address via DHCP using wireless. Linksys, Cisco, shows a bridge as taking a second router attaching it to the first adding its 4 port switch to the first giving you 8 RJ45 ports on the base network. If you're trying to connect a wireless router in one room to a laptop in another and have that act as a bridge, I think you need to use something like DD-WRT and make a repeater rather than a bridge. The laptop acting as a router on its own would assign addresses to a network distinct from the one in the other room and relay the data. But I'm guessing here. I had only looked at it briefly the other day after spotting an option on a Linksys wireless router that said BRIDGE. Dropped my whole network trying that and didn't hash for a while. Decided I might do it but not anytime soon. |
|
|
|
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 I think I read somebody else having a similar failure which resolved when he replaced the cat5 cable. There is a DHCP server working as two of the base network (192.168.43.0/24) addresses are dynamic not static. The server should assign addresses in its range to the bridged devices. So, again, I think the bridge isn't set up properly. If the bridge is set up properly he should be able to run a cable to the bridge from a laptop, boot the laptop with DHCP for it's interface IP assignment, and get assigned an address on that laptop in the 192.168.43.0 network, say 192.168.43.100 which he would ascertain by bringing up a dos cmd box on the laptop and using ipconfig /all. Ipconfig /all is a good command to know. I taught my boss that at work years ago when he was having a problem with the company network. |
|
|
|
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 I think I read somebody else having a similar failure which resolved when he replaced the cat5 cable. There is a DHCP server working as two of the base network (192.168.43.0/24) addresses are dynamic not static. The server should assign addresses in its range to the bridged devices. So, again, I think the bridge isn't set up properly. If the bridge is set up properly he should be able to run a cable to the bridge from a laptop, boot the laptop with DHCP for it's interface IP assignment, and get assigned an address on that laptop in the 192.168.43.0 network, say 192.168.43.100 which he would ascertain by bringing up a dos cmd box on the laptop and using ipconfig /all. |
|
|
|
do these things default to a 127.0.0.1 address when no DHCP SERVER to assign IP addie???
127.0.0.1 is only for devices to talk to themselves (localhost) Let me re-phrase the question, what happens or what IP address is assigned to a KNC Miner, if these isn't a DHCP server on the network? What would be the resolution to connecting to the KNC miner at this point. Thanks. I don't have your answer but I think you wonder if some oddball IP address is assigned when there isn't a valid DHCP server or even an internet connection as happens in Windows. |
|
|
|
|
Show Posts
