Topic: ANTMINER C1 Discussion and Support Thread - page 18. (Read 129188 times)

I could be wrong but I think in first page FAQ Dogies sd card image will bring it to factory, including IP.   If someone could please confirm that has used his image.

It seems deliberate as if to dissuade.  

And no, simply flashing the card wouldn't give me the fix I need.  It would be in the .1.0 network after flashing the card unless you have an idea how to reset the 192.168.1.99 to another subnet on the card before it goes in the machine.

So, no.  Holding the reset for 90 seconds brings it to that, 192.168.1.99,  state.

The S5's wake up to DHCP so subnets are not a problem.  But water cooled has lower temps than hard fan like the S5.

The second C1 still has the ssh login failure.  To test if the problem was a wrong key failure, I ssh'd in from a machine that had never connected to the second C1 but the failure still occurred.

Glad to hear you are getting closer.  Sounds like one is done.

If you have to do this often I still highly suggest making it where you can get to micro sd card.  If you had that you could have them fixed in 15 minutes with just flashing the micro sd card.

Okay, without taking the hood off,  reset the miner using the hard reset button.  To get a reliable reset I had to use an egg timer set for 1min30sec and with the button depressed applied power and started the timer.  Using a spare router I did finally get 192.168.1.99 and although I had gotten this before, after changing the options it got lost so this time first thing I did was only change static to DHCP.  That worked and checking the router I found the assigned IP. logged in and it seemed okay.  I shut it down and timed out 90 seconds dead no power with the RJ45 cable disconnected.  After 90 seconds dead I put the ethernet cable to the subnet switch and started the miner.  Then it was up and running on the subnet.  It seems luckier to leave the default pools to be among the last thing to change, heh, heh.  Oh, and ssh login works with root/admin.  Haven't done the second C1 with the login problem tho.  A couple of things I did notice, the first time after getting it up on the subnet, I put the laptop in that room up on the subnet as well and went to ssh in.  I said no to permanently remember the key and was refused.  When I ssh'd in from my regular machine it asked to permanently remember the key again although it had the key from before the change.  So, reflashing won't fix the ssh won't allow login.  Hard reset does and keeps the new firmware and changes the key such that one needs to give it a permanent yes. 

truc·u·lent
ˈtrəkyələnt/
adjective
adjective: truculent

    eager or quick to argue or fight; aggressively defiant.
    "his days of truculent defiance were over"
    synonyms:   defiant, aggressive, antagonistic, combative, belligerent, pugnacious, confrontational, ready for a fight, obstreperous, argumentative, quarrelsome, uncooperative;

This crap has my whole subnet down

Yes, perhaps.  I run nmap and see it has port 22/tcp ssh open as well as 80/tcp http but it's no help.

Since I'm at the Dec firmware maybe I should use the reset button, a hard reset should do it.

Or first I can restore to the Nov as I saved an archive then reflash to the newer firmware - it may be that just because I put don't save the settings, it looked at the firmware and say it's the same so I won't.

--------------
System Configuration Restore Successed -- rebooting
 Firmware still Dec 17 so Restore is only for setting not firmware.
 

It might be nothing but I personally would not shutdown miner when flashing.  I would let it do the restart, if it shutdown before it's finished it can give you some troubles.

I think you had your C1's where it's hard to get into but it might be easiest/take less time to find a way to get into your C1's and flash the micro sd.

The problem again:  On both C1's I put a script in /sbin and ran cp -rf /etc/shadow /config/ but then lost ssh login on both.  root/admin root/mypassword root/root, nothing works.

C1#1 had a November firmware and C1#2 had the December firmware.  I just used the GUI Upgrade to flash a new image and brought C1#1 up to the Wed Dec 17 firmware.  I flashed while retaining setting because it's not on the 192.168.1.0 network.  I still cannot ssh into the C1.

So I reflashed with Keep Settings unchecked.  Waited 90 seconds.  Shut the miner down.  Then expecting the miner to wakeup on the 192.168.1.0 network, swapped routers.  Then I couldn't find the miner on the .1.0 net so I ran tcpdump and saw the antminer looking for the gateway of the other network.  So I swapped the miner to the other network and do have a GUI but still can't login to ssh.  But it seems to be happily mining on the old settings, e.g. 243.75M/0725.

I know flashing the image changed the firmware when it changed from Nov to Dec firmware on Overview->System->File System Version.  But when I flashed that firmware again with the Keep Settings unchecked, it didn't revert to the stock settings. 

Hi,

If anyone is interested, here is updated firmware for AntMiners C1 with extranonce.subscribe support and fresh cgminer version:

AntMiner C1:
https://www.nicehash.com/download/AntMiner_C1_SD-firmware_cgminer_4.9.0_nicehash.tar.gz

Details explained here: https://www.nicehash.com/index.jsp?p=software#asic, firmware was prepared by smit1237 (thanks!).


Kind regards,
NiceHash.com

And on removing the board from the cooling block or inside heatsink on any S3 or C1, it looks like peeling it off would lead to damage.  These board were not made to flex.  I suggest one of the break off razor knives with a new long blade.  After screws are removed, slide in at a lower corner and work across.  

I have an slow s3 from Pines Computer in Florida bought on Amazon.  I suspect careless peeling may be the reason the boards are slower and inefficient.  If the underside ASIC heatsink plate soldering to the ground plane underneath has been damaged then it will be hotter.  A board flex could do that.  It will be the first Bitmain miner I will eventually retire and then I'll put it in an oven with the ASICs exposed to reflow the solder then test.

In my case it was the water block.

..Try the thermal paste first

I have upraded my water cooling after original pump died.  I'm guessing thermal past for me at least.

It really was the water block or only the termal paste?

My Notes from the teardown of my C1 Miner


1. Be aware that the cooling blocks (that nearly all screws in the C1 attach to)
are made of extremely soft aluminum. Very easy to strip.

2. Use only a LIGHT 2-finger torque on all of the screws.

3. The 4 Spring loaded screws that attach the Air cooled side heatsinks (fins)
were by far the hardest to get right. Extreme care should be taken with these screws
Very light touch using a good screwdriver. The heads on these screws are also easy
to strip out. LIGHT touch.

Do not over tighten these 4 screws, I believe these 4 screws are capable of bottoming out
in their screw threads in the cooling block

4. When reassembling, compare the Air cooled fins position (or orientation)
to one of the other hashing boards. You can use vias or one of the components on the board
to eyeball the position of the heatsink. These Air cooled heatsinks float on the top
of the ASIC chips, hence the Springs to keep the force.

5. Once installed, you can compare the Spring action (tension) between two or more
of the hashing boards. You can rock the board up a bit (1mm) if you reach your fingertips
underneath the top of the heatsink. This is only to compare the tension between
two different heatsinks. You don't have to do this.

6. Also, do not tighten with any force the Cooling block coolant connections as
they will sheer off completely if too much force is used (soft aluminum).

7. The Cooling blocks are available from the SysCooling web site.

http://shop.syscooling.com/goods.php?id=47

8. Reapply thermal paste on the ASIC chips

If it happens after a few hours, it is a cooling problem.

I had to replace the cooling block to fix my very similar problem.

I had 5 Xs on the 2nd chain hash board after a couple of hours.

I attempted a check of the thermal paste.  Tried to do this without cutting the cooling connection but instead twisting.  Didn't work.  I gave up and let it be.  Those screw pairs on the S3's and S3+'s are only half used on each side, one screw per pair.  Probably thru hole and the other board on the far side using the other screw.  Easy to strip one of those and since not a pair it gets difficult.  Unless you plan to go hole hog and rip it apart ....

Connect 1 hashing PCB at a time to the control PCB and you should be able to pin point it to the troubled Hashing PCB.

Then you can try reapply thermo paste and see if it will resolve the case.  If not and if it is still within the 90-day warranty, you can send it back to Denver or EU area service center or to the Factory in China and the replacement be send to you

China: +86 18511636219

US or EU techs you can reach them at +1-844-248-6246 x2

I have one that does this aswell.  I have tried new firmware.  Nothing I did seems to stop it after a few hours going down.  I think it's one of my boards a this point.

I wonder if I could find the blade and redo thermal paste on it would help.  But I have been afraid I will lose entire board if I happen to be wrong.