Can you check to see if DHCP request was coming from the Ethernet or Wi-Fi or both?
It was ethernet because I had the laptop hard wired at the time. |
|
|
|
Did you try direct Ethernet connection to your computer/laptop and try to SSH while Wi-Fi router turned off while you reconfiged your computer's IP to 192.168.1.XXX to talk to the Antminer? if 1.XXX didn't work, did you try again with just in case 2.XXX IP on the computer?
If you can SSH into the box, you can adjust the config file manually
It does sounds like the conflict... On this case teamviewer won't do any good.
One thing tough, can you Portforward those internal IP to your external IP and see, if any one of them will get you through
AntMiner's control panel was i think it's on port 80
Hard Reset wise, I don't have the instruction.
One thing is if you set static on LAN for 192.168.XXX and then you set another Static on WAN for 192.168.XXX you brick the box I think. I need to go double check.
Tried all that, I've nmapped every possible port on every possible IP it could be on and there's nothing there. Somehow the packets get onto the network requesting a dhcp address when I packet sniff and the router responds with an address and adds it to its arp table, but the actual IP address is still dead after that. Nov 28 21:30:50 daemon DHCP SERVER: DHCPDISCOVER from c8:ee:a6:00:36:ed via br0 Nov 28 21:30:51 daemon DHCP SERVER: DHCP offer to c8:ee:a6:00:36:ed Nov 28 21:30:51 daemon DHCP SERVER: DHCP request from c8:ee:a6:00:36:ed Nov 28 21:30:51 daemon DHCP SERVER: DHCP ack to c8:ee:a6:00:36:ed |
|
|
|
Changed IP config, mined on wifi for 5 mins while I set the IP address to a static address at 192.168.1.60 on the lan, applied settings and since then the system has been uncontactable. Occasionally my dhcp server sees it request an IP address but I can't talk to it and then it disappears again from that IP address. Tried removing wifi aerial and powering it down and up, tried removing lan cable and powering it down and up, tried setting static addresses across all 192.168.1.x and 192.168.2.x and still can't talk to it anywhere. Plugged directly into it with a laptop, plugged it into a router, did everything I could think of to talk to it and can't seem to.
Anyone know how to reset it somehow back to defaults? Only button on the board has a meaningless "S1" label.
Hmm, I set a fixed IP address on the WAN interface of my Antminer (to match the subnet of my home LAN) Also at one point I had enabled WLAN simultaneously with WAN, and the device started using both interfaces simultaneously. Does yours still connect to the WLAN access point? If yes your best bet may be to try to log into it when it connects via WLAN. Tried connecting on every possible interface that was already set up and I can't even ping them any more. The dhcp server acknowledges a request but I can't ping it. Tried hard wired to my laptop again on various possible subnets as I said, nothing seems to work. Only thing that comes out of it is a dhcp request when packet sniffing but it never gets beyond that. |
|
|
|
Ouch, did you set the static IP on LAN??? Not on WAN???
What was your WAN setting?
I had set up the wifi to dhcp and it worked fine Then I added an (extra) ethernet connection as a dhcp client and it never overrided the wifi one so I changed the 192.168.2.117 address to a static 192.168.1.60 address with a suitable netmask and gateway and applied and then it disappeared from everywhere. Presumably there's some conflict going on between the dhcp wifi connection, the dhcp lan connection and the static lan connection and it can't make up its mind and decides not to work on any of them. My dhcp server receives and acknowledges requests for the c8:ee:a6:00:36:ed mac address and says it's assigning 192.168.1.60 to it, but I can never ping or connect to that address. It does that via both lan and wifi (I've tried disconnecting the aerial on the wifi to make it not really work and unplugging the ethernet cable to make that not work). |
|
|
|
Doesn't sound good... If you let me remote in via TeamViewer, I can give it a shot... May take a while to troubleshoot but I'm available for the next few hours. PM me for the teamview ID. ( http://www.teamviewer.com) That's not going to cut it... but thanks for the offer. I don't really see how a remote windows tool will work on my many linux PCs connected through my various subnets spread across my place, nor which one to give you access to nor how you're meant to poke around from them to find the hardware amongst that jungle... All I want to know is how to reset it. |
|
|
|
Not off to a good start... Changed IP config, mined on wifi for 5 mins while I set the IP address to a static address at 192.168.1.60 on the lan, applied settings and since then the system has been uncontactable. Occasionally my dhcp server sees it request an IP address but I can't talk to it and then it disappears again from that IP address. Tried removing wifi aerial and powering it down and up, tried removing lan cable and powering it down and up, tried setting static addresses across all 192.168.1.x and 192.168.2.x and still can't talk to it anywhere. Plugged directly into it with a laptop, plugged it into a router, did everything I could think of to talk to it and can't seem to.
Anyone know how to reset it somehow back to defaults? Only button on the board has a meaningless "S1" label.
|
|
|
|
|
Changed IP config, mined on wifi for 5 mins while I set the IP address to a static address at 192.168.1.60 on the lan, applied settings and since then the system has been uncontactable. Occasionally my dhcp server sees it request an IP address but I can't talk to it and then it disappears again from that IP address. Tried removing wifi aerial and powering it down and up, tried removing lan cable and powering it down and up, tried setting static addresses across all 192.168.1.x and 192.168.2.x and still can't talk to it anywhere. Plugged directly into it with a laptop, plugged it into a router, did everything I could think of to talk to it and can't seem to.
Anyone know how to reset it somehow back to defaults? Only button on the board has a meaningless "S1" label.
|
|
|
|
MrTeal and I have developed mining hardware called Chili using BFL chips and it uses the BLF driver. The driver interface / protocol defines a command (ZTX) that allows cgminer to request three voltages from the hardware. The 3 values are typically 3.3V, 1.0V, and 12V. cgminer displays the 3.3V value on the screen but in my opinion this is the least interesting voltage value. I would prefer it to show the (nominal) 1.0V value as this directly impacts hashing speed and power. On other BFL hardware, this value is fixed at the factory, but on a Chili, it is configurable by software allowing automatic overclocking. Thus the interest in displaying this value. Please consider this reply a formal request to change the displayed value from the 3.3V value to the 1.0V value. If you have enough screen real estate, it should show 3 digits to the right of the decimal point. Ex: 1.057V Thank you. BTW - We have added a new field to the ZCX command to distinguish our hardware apart from BFL hardware: "MANUFACTURER: MrTeal and ChipGeek\n" We're not as scary as we may appear. If you push code via github to cgminer that doesn't affect other drivers, we will probably give you some basic changes we'd prefer before merging the code with cgminer, but are happy to include code with the master cgminer code if you do it that way and are happy to support it. Ideally we prefer to get the hardware ourselves so we can extend/develop/bugfix/support the code for the hardware ourselves until the hardware is no longer relevant, but if not, I'm happy to merge code from you while you personally support the code unless it interferes with other drivers or the code stops being supported as bugs appear (which they always do). |
|
|
|
|
There is no need for a -nogpu executable with cgminer any more. They are all non-gpu builds because cgminer no longer supports GPU. Just use cgminer.exe
That said, the most common reason for devices not being detected on windows if you have installed the WinUSB driver with cgminer is trying to use usb3 slots.
|
|
|
|
|
These miners don't mine litecoin.
|
|
|
|
OK, tested! Aside [again] The previous run of 3.5.1 lasted 25 hours without problems, although I do remember seeing a few AMU LEDs come on yesterday for a couple of seconds and I noticed some messages which were something like the following (completely from memory, as no logging enabled, can't remember the exact mS timings): [2013-11-xx xx:xx:xx] TIMEOUT AMUx something took xxx mS, was xxx mS [2013-11-xx xx:xx:xx] TIMEOUT AMUy something took xxx mS, was xxx mS The above disturbances didn't cause any problems, so it may just be normal network problems, but I haven't noticed them before, so perhaps it's important, perhaps not. Anyway, the test of cgminer-ffs ran for almost 2 hours, then a zombie appeared. I turned on debug from the display and let run for a further 5 minutes, then stopped it. Logfile is here: https://dl.dropboxusercontent.com/u/44240170/logfile-ffs.txtThanks for that. No you were getting the timer overruns previously as well. I saw them on your successful logging when you put it up so even when it's "fine" it's not entirely fine, it's just that it sort of recovers. Next! http://ck.kolivas.org/apps/cgminer/temp/cgminer-w00t.exeEDIT: And one greater than 9000: http://ck.kolivas.org/apps/cgminer/temp/cgminer-9001.exe |
|
|
|
Can you try fff again and this time when it gets into the loop of errors, enable debug in the display menu and continue logging for a bit please?
OK, done. Aside: The previous overnight run of 3.5.1 went for 14 hours, no faults. Started cgminer-fff again. After about 3 hours I got several LEDs full on for a few seconds. Two of them went out and resumed mining but the 3rd appeared in the display as a zombie. I was sitting next to the PC at the time, so turned on debug straight away. I left it running for a further 5 minutes then stopped it. Logfile here, but I suspect it's not going to help: https://dl.dropboxusercontent.com/u/44240170/logfile-fff2.txtAnd...... Back to 3.5.1 again :/ Thanks very much for that. Believe it or not I am (very slowly) making progress. Here's the next test please: http://ck.kolivas.org/apps/cgminer/temp/cgminer-ffs.exe |
|
|
|
|
Cgminer is recognising it as a little single. Either a board's completely offline/dead or it isn't populated at all as Photon939 said.
|
|
|
|
|
I've got my hands full at the moment...
|
|
|
|
|
If they're in USB3 slots, move them to USB2.
|
|
|
|
I'm sure there will be no profit in this setup. Sure there will. I can guarantee you KnC will make a very nice profit from these. |
|
|
|
4 more hours mates and we know.
Technical difficulties; stand by as we have rescheduled our demonstration to (never) next Monday. |
|
|
|
his from 3.8.3 may give a clue:
[2013-11-26 11:54:02] SEM: Icarus USB open failed '/tmp/cgminer-usb-1-58' err (24) Too many open files
It revives the zombies until it runs out of file descriptors on unix. Maybe some similar resource exhaustion is happening on Windows?
Interesting thought. It's easy enough to raise the number of file descriptors allowed in unix, but the default on windows should be much higher. Either way we should be removing the semaphores when the devices get zombied so that's at least one fix worth adding, thanks. EDIT: Checked the code and the semaphores are being removed so that's not it. |
|
|
|
|
Show Posts
