@Coinnilingus
Sent you PM for the RMA process info.
Topic: ANTMINER S3+ Discussion and Support Thread - page 150. (Read 710164 times)
If one hashing card connected to the control PCB and it doesn't hash, please try connecting the Hashing PCB to the other connector slot on the S3 control PCB. S3 control has to have Chain 1 side connected in order to hash.
UPDATE
I removed the cover from the s3 and noticed one of the capacitors had fallen off =)
is there a way to have the s3 hash with only 1 hashing board ? apparently if one board is faulty the s3 does not hash at all--am I wrong ?
UPDATE
I removed the cover from the s3 and noticed one of the capacitors had fallen off =)
is there a way to have the s3 hash with only 1 hashing board ? apparently if one board is faulty the s3 does not hash at all--am I wrong ?
I tried it, and it still does not hash. fans spin super loud almost like a leaf blower. the red light stays on, however I am able to access the UI. one of the capacitors fell off and has caused it to act bonkers.
If one hashing card connected to the control PCB and it doesn't hash, please try connecting the Hashing PCB to the other connector slot on the S3 control PCB. S3 control has to have Chain 1 side connected in order to hash.
UPDATE
I removed the cover from the s3 and noticed one of the capacitors had fallen off =)
is there a way to have the s3 hash with only 1 hashing board ? apparently if one board is faulty the s3 does not hash at all--am I wrong ?
UPDATE
I removed the cover from the s3 and noticed one of the capacitors had fallen off =)
is there a way to have the s3 hash with only 1 hashing board ? apparently if one board is faulty the s3 does not hash at all--am I wrong ?
Please hard-reset/factory reset your S3. If it was due to the messed up setting, this may fix the problem. You can reset it from the control panel or via a small hole next to the network port (while it is powered on for a few minutes, press and hold it for 3-5 seconds and let it go and wait for 2 mintues and then power it off) Restart your S3 and wait for 3 minutes and see if it is hashing.
If this doesn't work, please try upgrading the firmware to the newest version from http://www.bitmaintech.com Support Page, under S3 Firmware.
If nothing works, please contact 1-844-248-6246 and ask for tech support
If this doesn't work, please try upgrading the firmware to the newest version from http://www.bitmaintech.com Support Page, under S3 Firmware.
If nothing works, please contact 1-844-248-6246 and ask for tech support
I am experiencing something super weird with my s3. my s3 hashed like normal, however I powered off my s3 to do some dusting, when I powered it back on the fans spin like crazy and are super loud, and the red LED stays on. I can access the web UI, but the device will not hash.
does anyone know if this is fixable ? thanks
sorry if this topic has been discussed. I am skimming through the 370+ pg thread now to look for something similar.
does anyone know if this is fixable ? thanks
sorry if this topic has been discussed. I am skimming through the 370+ pg thread now to look for something similar.
I am experiencing something super weird with my s3. my s3 hashed like normal, however I powered off my s3 to do some dusting, when I powered it back on the fans spin like crazy and are super loud, and the red LED stays on. I can access the web UI, but the device will not hash.
does anyone know if this is fixable ? thanks
sorry if this topic has been discussed. I am skimming through the 370+ pg thread now to look for something similar.
UPDATE
I removed the cover from the s3 and noticed one of the capacitors had fallen off =)
is there a way to have the s3 hash with only 1 hashing board ? apparently if one board is faulty the s3 does not hash at all--am I wrong ?
does anyone know if this is fixable ? thanks
sorry if this topic has been discussed. I am skimming through the 370+ pg thread now to look for something similar.
UPDATE
I removed the cover from the s3 and noticed one of the capacitors had fallen off =)
is there a way to have the s3 hash with only 1 hashing board ? apparently if one board is faulty the s3 does not hash at all--am I wrong ?
Kano's update does work and function. You can try using them. (Can't provide warranty but it worked on over 500 S1 since he published it and no dead S1 due to it.) If the process failed or mis-typed something during the process, you can always factory reset the S1 and try again!!
cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
All Credit goes to Kano for this updated version for S1. Again, Thank you, KANO and Ckolivas
It worked for me but don't do using scripts above. The scripts above were a question I was asking M and he clarified that you need to go to the link above for the instructions. I did that and followed the instructions in the read me to upgrade my S1s. Not sure what the improvements are but it worked. cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
All Credit goes to Kano for this updated version for S1. Again, Thank you, KANO and Ckolivas
note Reboot is not a command nor is #Reboot... lala/ red anger. (ignore this < if u wish these to be a valid command u will need to do cp /sbin/reboot /sbin/Reboot ; chmod +x /sbin/Reboot /> ignore this)
per Kano u do this... (cuz he understands unix)
Next you need to restart cgminer on your AntS1
You can restart it, when logged into your ant, with the command
/etc/init.d/cgminer restart
You will get a message saying "stopped cgminer" if it was running
You will get a message "no cgminer found; none killed" if it wasn't running
If you also get a message "cgminer is already running" then wait 10 seconds
then reissue the command to restart cgminer
/etc/init.d/cgminer restart
so what is the point of this 4+ month old code?
Kano's update does work and function. You can try using them. (Can't provide warranty but it worked on over 500 S1 since he published it and no dead S1 due to it.) If the process failed or mis-typed something during the process, you can always factory reset the S1 and try again!!
cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
All Credit goes to Kano for this updated version for S1. Again, Thank you, KANO and Ckolivas
It worked for me but don't do using scripts above. The scripts above were a question I was asking M and he clarified that you need to go to the link above for the instructions. I did that and followed the instructions in the read me to upgrade my S1s. Not sure what the improvements are but it worked. cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
All Credit goes to Kano for this updated version for S1. Again, Thank you, KANO and Ckolivas
Dear Bitmain,
I recommend you to do a service like spondoolies tech. Free shipping or 1 month free hosting.
I recommend you to do a service like spondoolies tech. Free shipping or 1 month free hosting.
Kano's update does work and function. You can try using them. (Can't provide warranty but it worked on over 500 S1 since he published it and no dead S1 due to it.) If the process failed or mis-typed something during the process, you can always factory reset the S1 and try again!!
cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
All Credit goes to Kano for this updated version for S1. Again, Thank you, KANO and Ckolivas
cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
All Credit goes to Kano for this updated version for S1. Again, Thank you, KANO and Ckolivas
I have no conclusive scientific proof that it's helping but I have been able to operate my S3s with ambient temps up to 42C (107F) while clocked at 243.75M with no issues. Alternatively, you can run the S3s on its side (controller in vertical position and adjacent to the heat sinks instead of on top of it) or perhaps even upside down (controller underneath the heat sinks). I suggest to try these configurations out before you decide to RMA/replace the controller and see if it helps. It couldn't hurt.
I have nothing beyond an anecdotal "gut feel", but over the last few hours since reading this post, rotating all my S3's so they are laying on their side (Bitmain logo facing up), they do seem to be running slightly more stably and cooler... Will continue monitoring.Forgive me for budging in on this.
I totaly understand that most of the observations here are anecdotal, but I have never known any of my S3's to run without any of the fans turned on. Even when they are not hashing but connected to the pool, the fan still turns, albeit slowly. So my question is, how would the heat then have a chance of building up at the top?
Having said that, I'll give it a shot too.
I have considered your point of view also. However, the location of the controller in relation to the airflow generated by the fans is on the fringes at best and therefore not optimum. Like I said, the only way to conclusively determine validity is to stick temp sensors and gather data. Until then, it's anecdotal (however, supported by practical explanation).
Edit:
Re "practical explanation":
In the standard orientation, the top of the case where the controller is located feels warm/hot to the touch (depending on ambient room temp). Whereas in my current vertical airflow configuration, the surface area of the case/enclosure next to the controller (now at the bottom and on the side) is relatively much cooler to the touch. In fact, even in this vertical airflow orientation, the bottom part of the case is relatively cooler to the touch than that of the upper area.
Get the version via ssh. The webUI will always say the older version 
Looks like something obviously changed because both S3s seem to be hashing faster, showing best share in miner status, now showing stratum+tcp instead of http, and load numbers have dropped. What's the command to show version from SSH?/usr/bin/cgminer-api
scroll to the top to see the cgminer version.
M
I'm not sure. I do know Kano published an update for S1s to make things better. Not sure how much better it is, but it's something.
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
M
Thanks M for your help and your great Ant Monitor program. Would I load similar to how done for the S3 earlier with the mod below?
cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
It's not the same process. Go to the link I provided, the instructions are there.
M
I have no conclusive scientific proof that it's helping but I have been able to operate my S3s with ambient temps up to 42C (107F) while clocked at 243.75M with no issues. Alternatively, you can run the S3s on its side (controller in vertical position and adjacent to the heat sinks instead of on top of it) or perhaps even upside down (controller underneath the heat sinks). I suggest to try these configurations out before you decide to RMA/replace the controller and see if it helps. It couldn't hurt.
I have nothing beyond an anecdotal "gut feel", but over the last few hours since reading this post, rotating all my S3's so they are laying on their side (Bitmain logo facing up), they do seem to be running slightly more stably and cooler... Will continue monitoring.Forgive me for budging in on this.
I totaly understand that most of the observations here are anecdotal, but I have never known any of my S3's to run without any of the fans turned on. Even when they are not hashing but connected to the pool, the fan still turns, albeit slowly. So my question is, how would the heat then have a chance of building up at the top?
Having said that, I'll give it a shot too.
I have no conclusive scientific proof that it's helping but I have been able to operate my S3s with ambient temps up to 42C (107F) while clocked at 243.75M with no issues. Alternatively, you can run the S3s on its side (controller in vertical position and adjacent to the heat sinks instead of on top of it) or perhaps even upside down (controller underneath the heat sinks). I suggest to try these configurations out before you decide to RMA/replace the controller and see if it helps. It couldn't hurt.
I have nothing beyond an anecdotal "gut feel", but over the last few hours since reading this post, rotating all my S3's so they are laying on their side (Bitmain logo facing up), they do seem to be running slightly more stably and cooler... Will continue monitoring.Get the version via ssh. The webUI will always say the older version
Looks like something obviously changed because both S3s seem to be hashing faster, showing best share in miner status, now showing stratum+tcp instead of http, and load numbers have dropped. What's the command to show version from SSH?/usr/bin/cgminer-api
scroll to the top to see the cgminer version.
M
I'm not sure. I do know Kano published an update for S1s to make things better. Not sure how much better it is, but it's something.
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
M
Thanks M for your help and your great Ant Monitor program. Would I load similar to how done for the S3 earlier with the mod below?
cd /usr/bin
mv cgminer cgminer.bak
wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
mv AntS1 cgminer
chmod +x cgminer
#Reboot
I have no conclusive scientific proof that it's helping but I have been able to operate my S3s with ambient temps up to 42C (107F) while clocked at 243.75M with no issues. Alternatively, you can run the S3s on its side (controller in vertical position and adjacent to the heat sinks instead of on top of it) or perhaps even upside down (controller underneath the heat sinks). I suggest to try these configurations out before you decide to RMA/replace the controller and see if it helps. It couldn't hurt.
I have nothing beyond an anecdotal "gut feel", but over the last few hours since reading this post, rotating all my S3's so they are laying on their side (Bitmain logo facing up), they do seem to be running slightly more stably and cooler... Will continue monitoring. Is anyone else putting their S3's on LeaseRig? I have a couple on there and everything works great using the bitmain original cgminer. However, if I replace that with the new cgminer Ckolivas posted I get very erratic behavior when someone rents the miner. Things like low or 0 hashrate, it reboots, or otherwise just stops mining. If I swap out Ckolivas' new build of cgminer with the Bitmain original it all runs fine again.
Am I missing something? Setting something wrong?
Am I missing something? Setting something wrong?
Same here. All of mine run better with the Bitmain version (3.12.0). The 4.6.1 (and 4.6.0) starts off faster, but after letting it run 24 hours, the miner side average was a little lower than the Bitmain version. And the pool-side average with 4.6.x was much lower. I'm mining with ghash.io.
lol... They would not start mining if cgminer was not executable.
What batch of S3's do you have and do they have the latest firmware installed?
I did some tests after the original 4.6 was published (see link in my signature) and I experienced reduced hashrate and rolled back to the stock cgminer. However, when I upgraded my S1's with the upgrade kit, the upgraded (with the latest firmware) ones were hashing faster than my S3's, and the only difference was the firmware which I decided to upgrade and voilla, order was returned with the proper S3's hashing slightly higher (and consistently) than my upgrades. When 4.6.1 was published, I installed it on both factory S3's and my upgrades and BOTH hash better and faster than before.
So, to get the best / most out of cgminer 4.6.1 I'd ensure you have the latest firmware AND reboot via SSH after updgrading cgminer rather than restart.
EDIT: - Note that if you flush the latest firmware, you'll have to re-install cgminer 4.6.1 as the firmware has the stock version.
That's interesting. I held back on updating my under-performing S3 after reading your original post about reduced hash rate, but if 4.6.1 fixes that, I'll give it a go. Thanks.
Edit: when you say latest firmware, do you mean this one - antMiner_S320140826.bin which it says supports S3+? I am using ordinary S3s. Cheers.
Edit2: Confirmed by pekatete in another thread. Thanks again.
I've got an S3+ and it works fine but I have a problem:
When the unit has been hashing for a few days and I turn it off and re-start it, it won't re-start. It won't come back on the network. However, if I let the unit cool for about an hour and turn it back on, it just starts working like it should. I have gone through this a couple of times and it works like that consistently. It's not a huge deal because it works once it gets going, but I did run into an issue where after running for several days I could no longer access the control interface with my web browser, but it was still hashing away just fine.
Would this indicate some kind of thermal problem with the controller board? Is there a good way to get this fixed? I think if I send it in for RMA they will plug it in and it will work fine. To minimize downtime I'd prefer to buy a controller board and then return the defective one for a refund.
When the unit has been hashing for a few days and I turn it off and re-start it, it won't re-start. It won't come back on the network. However, if I let the unit cool for about an hour and turn it back on, it just starts working like it should. I have gone through this a couple of times and it works like that consistently. It's not a huge deal because it works once it gets going, but I did run into an issue where after running for several days I could no longer access the control interface with my web browser, but it was still hashing away just fine.
Would this indicate some kind of thermal problem with the controller board? Is there a good way to get this fixed? I think if I send it in for RMA they will plug it in and it will work fine. To minimize downtime I'd prefer to buy a controller board and then return the defective one for a refund.
I've always felt that since the controller sits directly on top of the heat sinks, its whole surface area is taking the brunt of the heat that's radiating/rising from them, hence I opted to set up my units in a vertical configuration (controller in vertical position, adjacent to the heat sinks instead of on top of them and at the bottom half of the unit/enclosure):
https://bitcointalksearch.org/topic/m.8227268
https://bitcointalksearch.org/topic/m.8471571
I have no conclusive scientific proof that it's helping but I have been able to operate my S3s with ambient temps up to 42C (107F) while clocked at 243.75M with no issues. Alternatively, you can run the S3s on its side (controller in vertical position and adjacent to the heat sinks instead of on top of it) or perhaps even upside down (controller underneath the heat sinks). I suggest to try these configurations out before you decide to RMA/replace the controller and see if it helps. It couldn't hurt.
Is anyone else putting their S3's on LeaseRig? I have a couple on there and everything works great using the bitmain original cgminer. However, if I replace that with the new cgminer Ckolivas posted I get very erratic behavior when someone rents the miner. Things like low or 0 hashrate, it reboots, or otherwise just stops mining. If I swap out Ckolivas' new build of cgminer with the Bitmain original it all runs fine again.
Am I missing something? Setting something wrong?
Am I missing something? Setting something wrong?
chmod +x cgminer
Did you make it executable?
To add to the above, low hashrate in the UI sometimes happens when you restart cgminer rather than reboot. After updating to the new cgminer and making it executable, reboot the S3 via SSH not the UI.
Yes - it's executable....it wouldn't be mining and giving the erratic behavior if it wasn't able to execute it.
What I'm meaning specifically is the erratic behavior (at least for me) ONLY happens when the miner gets leased. It will go on and offline and reboot and do all sorts of nonsense when the miner is on lease with cgminer 4.6+. As soon as I switch back to the Bitmain version (and reboot - I've rebooted both via ssh as well as webgui and both result the same), everything returns to normal. Nothing else is changed - only the cgminer binary. Which is why I'm thinking I'm either missing something or maybe the new cgminer binaries don't support or require a different command line options. I don't think it's the pools the miners are leased on either, I've seen different pools being used by different people leasing it.
I've got an S3+ and it works fine but I have a problem:
When the unit has been hashing for a few days and I turn it off and re-start it, it won't re-start. It won't come back on the network. However, if I let the unit cool for about an hour and turn it back on, it just starts working like it should. I have gone through this a couple of times and it works like that consistently. It's not a huge deal because it works once it gets going, but I did run into an issue where after running for several days I could no longer access the control interface with my web browser, but it was still hashing away just fine.
Would this indicate some kind of thermal problem with the controller board? Is there a good way to get this fixed? I think if I send it in for RMA they will plug it in and it will work fine. To minimize downtime I'd prefer to buy a controller board and then return the defective one for a refund.
When the unit has been hashing for a few days and I turn it off and re-start it, it won't re-start. It won't come back on the network. However, if I let the unit cool for about an hour and turn it back on, it just starts working like it should. I have gone through this a couple of times and it works like that consistently. It's not a huge deal because it works once it gets going, but I did run into an issue where after running for several days I could no longer access the control interface with my web browser, but it was still hashing away just fine.
Would this indicate some kind of thermal problem with the controller board? Is there a good way to get this fixed? I think if I send it in for RMA they will plug it in and it will work fine. To minimize downtime I'd prefer to buy a controller board and then return the defective one for a refund.
Is anyone else putting their S3's on LeaseRig? I have a couple on there and everything works great using the bitmain original cgminer. However, if I replace that with the new cgminer Ckolivas posted I get very erratic behavior when someone rents the miner. Things like low or 0 hashrate, it reboots, or otherwise just stops mining. If I swap out Ckolivas' new build of cgminer with the Bitmain original it all runs fine again.
Am I missing something? Setting something wrong?
Am I missing something? Setting something wrong?
Same here. All of mine run better with the Bitmain version (3.12.0). The 4.6.1 (and 4.6.0) starts off faster, but after letting it run 24 hours, the miner side average was a little lower than the Bitmain version. And the pool-side average with 4.6.x was much lower. I'm mining with ghash.io.
lol... They would not start mining if cgminer was not executable.
What batch of S3's do you have and do they have the latest firmware installed?
I did some tests after the original 4.6 was published (see link in my signature) and I experienced reduced hashrate and rolled back to the stock cgminer. However, when I upgraded my S1's with the upgrade kit, the upgraded (with the latest firmware) ones were hashing faster than my S3's, and the only difference was the firmware which I decided to upgrade and voilla, order was returned with the proper S3's hashing slightly higher (and consistently) than my upgrades. When 4.6.1 was published, I installed it on both factory S3's and my upgrades and BOTH hash better and faster than before.
So, to get the best / most out of cgminer 4.6.1 I'd ensure you have the latest firmware AND reboot via SSH after updgrading cgminer rather than restart.
EDIT: - Note that if you flush the latest firmware, you'll have to re-install cgminer 4.6.1 as the firmware has the stock version.
Jump to: