Author

Topic: ANTMINER S3+ Discussion and Support Thread - page 161. (Read 710164 times)

soy
legendary
Activity: 1428
Merit: 1013
September 26, 2014, 01:55:42 PM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)

I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions.  I think there was a security issue with the original firmware.

I just tried an SSH access and the one device just times out the connection, the working one lets me log on as root. I think it's interesting that the first LuCI page comes up even though other pages and SSH don't work. At this point, without better diagnostics, I'd be inclined to let bitmain tell me what to do.

Trouble is that the downed miner won't bring up the HTTP interface, so there is no possibility at installing different firmware. Anyone know how to reset the device? We've tried the instructions for reset shown here, but no joy.

Can you ping it? If so try another browser? Default should be 192.168.1.99.


I've noticed that if I ssh into an S3 and command halt, unless I cold boot I can't get in.  The device will acknowledge a ping but port 80 seems closed.  And the halt command stops the cgminer-monitor so it doesn't restart at otherwise 3 minutes most.
soy
legendary
Activity: 1428
Merit: 1013
September 26, 2014, 01:47:37 PM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)

I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions.  I think there was a security issue with the original firmware.

I just tried an SSH access and the one device just times out the connection, the working one lets me log on as root. I think it's interesting that the first LuCI page comes up even though other pages and SSH don't work. At this point, without better diagnostics, I'd be inclined to let bitmain tell me what to do.

Trouble is that the downed miner won't bring up the HTTP interface, so there is no possibility at installing different firmware. Anyone know how to reset the device? We've tried the instructions for reset shown here, but no joy.

The reset button is a bit below the hole, not aligned well.  And I found on the S3 as well as a miner from another company that the reset doesn't work all that well.  What I try is holding it in for 30 seconds, then mashing it every few seconds for a while, then turning it off, letting it sit a  minute then rebooting while mashing the reset every few seconds a couple of times then letting it boot.

soy
legendary
Activity: 1428
Merit: 1013
September 26, 2014, 01:39:48 PM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

Try disconnecting the power supply from the S3 while you leave it off for some period before you retry.
soy
legendary
Activity: 1428
Merit: 1013
September 26, 2014, 01:32:15 PM
Ah, my problem S3 has been running 1d 16h and has slowed to 418.15.  Three hours ago it was 418.80.

I have been in an acrimonious email exchange with the reseller.  So, for me to ask him to submit the slow hashing blade for exchange would beg an extended delay.  To request an exchange from Bitmain would probably be met by an instruction to return the slow hashing board to the reseller.

I'm not certain it would be in my interest to return the hashing board.  If Bitmain would accept the board directly what is the estimated turn around time?  What is the estimated shipping from the US?  Answers to these questions would help inform my decision how to proceed.  Thanks.

soy


I realise that you may have tried this, but one of my S3s is similar to yours and gets slower and slower, eventually ending up in the 300s, so when I can see that its average is going down towards 420 again, I reboot it.  On the first or second reboot, it starts hashing at around 460 or more, with good speed for hours until it gradually starts sinking again over the next day or so.  With this method, I keep it averaging 440 for most of the time, which I can't complain about.  Sorry if you already tried and discounted this!  Smiley

Yes, a cold boot restores relatively normal hashrates but there is a continual decline.  I'm hoping it will settle out at a hashrate that is a stable floor.  I had tried anticipating when it would hit 5% less than 441, knowing that end point, 418.5, if the plot tracked a capacitor charging track a single timeconstant predicted five timeconstants would have expired this afternoon.  It finished early because the cold boot was late afternoon and much of that first timeconstant the S3 was in a cooler environment so the prediction was long.

Does either of your fan speeds seem slow relative to temperature?

Rebooting will restore the hashing for a while I suppose and cost less than a return.  
sr. member
Activity: 364
Merit: 250
September 26, 2014, 01:26:10 PM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)

I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions.  I think there was a security issue with the original firmware.

I just tried an SSH access and the one device just times out the connection, the working one lets me log on as root. I think it's interesting that the first LuCI page comes up even though other pages and SSH don't work. At this point, without better diagnostics, I'd be inclined to let bitmain tell me what to do.

Trouble is that the downed miner won't bring up the HTTP interface, so there is no possibility at installing different firmware. Anyone know how to reset the device? We've tried the instructions for reset shown here, but no joy.

Can you ping it? If so try another browser? Default should be 192.168.1.99.
newbie
Activity: 1
Merit: 0
September 26, 2014, 01:23:20 PM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)

I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions.  I think there was a security issue with the original firmware.

I just tried an SSH access and the one device just times out the connection, the working one lets me log on as root. I think it's interesting that the first LuCI page comes up even though other pages and SSH don't work. At this point, without better diagnostics, I'd be inclined to let bitmain tell me what to do.

Trouble is that the downed miner won't bring up the HTTP interface, so there is no possibility at installing different firmware. Anyone know how to reset the device? We've tried the instructions for reset shown here, but no joy.
newbie
Activity: 4
Merit: 0
September 26, 2014, 12:32:50 PM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)

I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions.  I think there was a security issue with the original firmware.

I just tried an SSH access and the one device just times out the connection, the working one lets me log on as root. I think it's interesting that the first LuCI page comes up even though other pages and SSH don't work. At this point, without better diagnostics, I'd be inclined to let bitmain tell me what to do.
sr. member
Activity: 364
Merit: 250
September 26, 2014, 11:48:53 AM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)

I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions.  I think there was a security issue with the original firmware.
newbie
Activity: 4
Merit: 0
September 26, 2014, 11:44:40 AM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
Given the length of time since purchase, I'm hesitant. Like I said. I'd rather not do something that makes it impossible to return. If I brick it, then I'm stuck. Also, I can't get to the web page that has the flashing initiation, it'll take some hoop jumping to get it done. I'll wait and see what others have to say that might help and are less drastic. (An additional diagnostic that is more information would be great, even if the diagnostic really does then point at a firmware upgrade. I'd then be willing to go there.)
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
September 26, 2014, 11:34:11 AM
Ah, my problem S3 has been running 1d 16h and has slowed to 418.15.  Three hours ago it was 418.80.

I have been in an acrimonious email exchange with the reseller.  So, for me to ask him to submit the slow hashing blade for exchange would beg an extended delay.  To request an exchange from Bitmain would probably be met by an instruction to return the slow hashing board to the reseller.

I'm not certain it would be in my interest to return the hashing board.  If Bitmain would accept the board directly what is the estimated turn around time?  What is the estimated shipping from the US?  Answers to these questions would help inform my decision how to proceed.  Thanks.

soy


what is your freq setting for this unit?

   Some of these units only run well at freq 212.50   .  You may have one of them and all the work you did to fix it was a waste of time.   I have a pair of these they were batch 1.  I did everything possible with one of them and did nothing with the other.

   So I then set both to freq 212.50 and they have run rock steady around  430gh since July 25 or so.  Try using setting of 212.5 to see if you stay stable at 430 gh.
sr. member
Activity: 364
Merit: 250
September 26, 2014, 11:27:24 AM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?

For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
sr. member
Activity: 364
Merit: 250
September 26, 2014, 11:26:27 AM
can someone explain this to me? What is wrong with this picture? I am running the latest image.... Fans even hitting 12,400 RPM, pretty soon my S3 is going to be flying around the room!



I have one where the fan speed is reporting as way too high seeing how these fans max out at 3000 rpm. I just ignore it because sound comparisons are telling me the fan is not spinning that fast and is in fact spinning at the proper speeds....

It would be nice to see why they are reporting this. I would swap out some other fans and see if its a faulty fan sense but logic dictates its a software problem because if the fan was actually reporting that speed the s3 would NEVER adjust it higher when it gets hotter and I hear the faulty reading s3 changing its fans speeds when it gets a little hotter....

Side note on your pictures.... 50C 51C?? wow you running those way too hot...
the ones I have sitting just out in the open not in a server room are at 42c/40c. u live in a bakery?

Yes, I want them to run hot because I make eggs in the morning on pan on top of the miner, and cookies in the evenings Wink I run these in my office, I have 17 of them plus other miners in a room with just one 6" vent. The degrees is about 95-100F, and there hasn't been any problems. Chips don't need to be that cold, they just need air over them to run. All the miners have been running fine, its just these funky readings and the fans do move faster, but I don't think they are REALLY going 12,000 RPM or they would be extremely loud.

newbie
Activity: 4
Merit: 0
September 26, 2014, 11:25:15 AM
I was directed here as maybe a quick fix for a problem. Please point me elsewhere if appropriate.

Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.

I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.

On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)

I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.

Thoughts on what I could try that won't make it so I can't return it?
member
Activity: 98
Merit: 10
September 26, 2014, 10:44:03 AM
Ah, my problem S3 has been running 1d 16h and has slowed to 418.15.  Three hours ago it was 418.80.

I have been in an acrimonious email exchange with the reseller.  So, for me to ask him to submit the slow hashing blade for exchange would beg an extended delay.  To request an exchange from Bitmain would probably be met by an instruction to return the slow hashing board to the reseller.

I'm not certain it would be in my interest to return the hashing board.  If Bitmain would accept the board directly what is the estimated turn around time?  What is the estimated shipping from the US?  Answers to these questions would help inform my decision how to proceed.  Thanks.

soy


I realise that you may have tried this, but one of my S3s is similar to yours and gets slower and slower, eventually ending up in the 300s, so when I can see that its average is going down towards 420 again, I reboot it.  On the first or second reboot, it starts hashing at around 460 or more, with good speed for hours until it gradually starts sinking again over the next day or so.  With this method, I keep it averaging 440 for most of the time, which I can't complain about.  Sorry if you already tried and discounted this!  Smiley
hero member
Activity: 569
Merit: 500
September 26, 2014, 10:35:43 AM
can someone explain this to me? What is wrong with this picture? I am running the latest image.... Fans even hitting 12,400 RPM, pretty soon my S3 is going to be flying around the room!



I have one where the fan speed is reporting as way too high seeing how these fans max out at 3000 rpm. I just ignore it because sound comparisons are telling me the fan is not spinning that fast and is in fact spinning at the proper speeds....

It would be nice to see why they are reporting this. I would swap out some other fans and see if its a faulty fan sense but logic dictates its a software problem because if the fan was actually reporting that speed the s3 would NEVER adjust it higher when it gets hotter and I hear the faulty reading s3 changing its fans speeds when it gets a little hotter....

Side note on your pictures.... 50C 51C?? wow you running those way too hot...
the ones I have sitting just out in the open not in a server room are at 42c/40c. u live in a bakery?
hero member
Activity: 524
Merit: 500
September 26, 2014, 10:05:30 AM
Ah, my problem S3 has been running 1d 16h and has slowed to 418.15.  Three hours ago it was 418.80.

I have been in an acrimonious email exchange with the reseller.  So, for me to ask him to submit the slow hashing blade for exchange would beg an extended delay.  To request an exchange from Bitmain would probably be met by an instruction to return the slow hashing board to the reseller.

I'm not certain it would be in my interest to return the hashing board.  If Bitmain would accept the board directly what is the estimated turn around time?  What is the estimated shipping from the US?  Answers to these questions would help inform my decision how to proceed.  Thanks.

soy


I had a friend that had to RMA a hash board with Bitmain. It took about 2 weeks from the time he shipped it to the time he got the replacement in hand. Mind you, his was completely dead so it was no loss to him to be without it.
soy
legendary
Activity: 1428
Merit: 1013
September 26, 2014, 08:50:09 AM
Ah, my problem S3 has been running 1d 16h and has slowed to 418.15.  Three hours ago it was 418.80.

I have been in an acrimonious email exchange with the reseller.  So, for me to ask him to submit the slow hashing blade for exchange would beg an extended delay.  To request an exchange from Bitmain would probably be met by an instruction to return the slow hashing board to the reseller.

I'm not certain it would be in my interest to return the hashing board.  If Bitmain would accept the board directly what is the estimated turn around time?  What is the estimated shipping from the US?  Answers to these questions would help inform my decision how to proceed.  Thanks.

soy
sr. member
Activity: 364
Merit: 250
September 26, 2014, 07:48:19 AM
Sooo... who's thrown away their BTC on the S4 already?

By the time you got your money back on the S4, there would have been 2 or more difficulty jumps. Anyone who bought this, even with the coupon just has a room heater.  Also, fans are very loud, do you see how fat those fans are? I think people are underestimating the noise this S4 is going to make. Same thing with the SP20.

I bought the Prisma ASICMiner 1.4Th/s for only $670 and that included the controller. I believe the Prisma is much quieter and smaller too.
hero member
Activity: 806
Merit: 507
Trusted Campaign manager
September 26, 2014, 07:00:00 AM
Selling S4 coupons for 0.25 BTC each. Send me a PM
how much is it worth? by bitmaintech...this one coupon ?
hero member
Activity: 616
Merit: 500
September 26, 2014, 03:15:09 AM
can someone explain this to me? What is wrong with this picture? I am running the latest image.... Fans even hitting 12,400 RPM, pretty soon my S3 is going to be flying around the room!


I'm also getting very high fan speed readings on the 2nd fan of some S3's.  I don't think that it is the real fan speed, only some software error in reporting. The sound is similar to the other S3's that report a more 'conventional' speed. (Don't rush to tie your S3 before it flies away...).

Cheers
Jump to: