<<  >> (p.366)
    Author Topic: ANTMINER S3+ Discussion and Support Thread  (Read 710650 times)

    • Phosphorous
    Hero Member
    *****
    Offline Offline

    Activity: 556
    Merit: 500


    View Profile
    October 10, 2014, 11:42:11 PM
     #7301
    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.

  • nst6563
    Sr. Member
    ****
    Offline Offline

    Activity: 252
    Merit: 254


    View Profile
    October 11, 2014, 02:19:18 AM
     #7302
    Quote from: pekatete on October 10, 2014, 11:02:12 PM
    Quote from: faetos on October 10, 2014, 10:57:06 PM
    Quote from: nst6563 on October 10, 2014, 10:53:15 PM
    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?  

    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.

  • visdude
    Legendary
    *
    Offline Offline

    Activity: 1081
    Merit: 1001


    View Profile
    October 11, 2014, 05:54:23 AM
    Last edit: October 11, 2014, 12:46:18 PM by visdude
     #7303
    Quote from: Phosphorous on October 10, 2014, 11:42:11 PM
    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.

    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://bt.irlbtc.com/view/671189.msg8227268#msg8227268
    https://bt.irlbtc.com/view/671189.msg8471571#msg8471571

    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.

  • moss
    Member
    **
    Offline Offline

    Activity: 98
    Merit: 10


    View Profile
    October 11, 2014, 10:26:34 AM
    Last edit: October 11, 2014, 09:22:51 PM by moss
     #7304
    Quote from: pekatete on October 10, 2014, 11:15:19 PM
    Quote from: MissouriMiner on October 10, 2014, 11:04:55 PM
    Quote from: nst6563 on October 10, 2014, 10:53:15 PM
    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?  

    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. Smiley

    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.  Smiley

  • Xian01
    Legendary
    *
    Offline Offline

    Activity: 1652
    Merit: 1067


    Christian Antkow


    View Profile
    October 11, 2014, 09:46:20 PM
     #7305
    Quote from: visdude on October 11, 2014, 05:54:23 AM
    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.

  • Moria843
    Sr. Member
    ****
    Offline Offline

    Activity: 442
    Merit: 250


    Found Lost beach - quiet now


    View Profile
    October 11, 2014, 09:53:49 PM
     #7306
    Quote from: mdude77 on October 06, 2014, 01:30:24 AM
    Quote from: Moria843 on October 06, 2014, 01:14:58 AM
    Quote from: mdude77 on October 06, 2014, 01:02:18 AM
    Quote from: Moria843 on October 06, 2014, 12:51:22 AM
    Quote from: IYFTech on October 05, 2014, 11:39:04 PM
    Get the version via ssh. The webUI will always say the older version  Wink
    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
    Must have worked; both showing 4.6.0. Will this version work on my undervoltaged S1s?

    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?

    cdusr/bin
    mv cgminer cgminer.bak
    wget https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
    mv AntS1 cgminer
    chmod +x cgminer
    #Reboot
    Hot time, summer in the city, back of my mine getting hot & gritty!!!

  • visdude
    Legendary
    *
    Offline Offline

    Activity: 1081
    Merit: 1001


    View Profile
    October 11, 2014, 10:58:34 PM
     #7307
    Quote from: Xian01 on October 11, 2014, 09:46:20 PM
    Quote from: visdude on October 11, 2014, 05:54:23 AM
    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.
    I know what you mean.  I have always wanted to stick some temp sensors around the controller and get readings in different configurations/orientations in an effort to conclusively determine if they do make a difference but I can't afford the down time ("if it ain't broke, don't fix it" mentality on my part).  However, the one thing that we can go by to make sense out of it is that we do know that heat rises and in an enclosed environment, it would accumulate at the top.

  • pekatete
    Hero Member
    *****
    Offline Offline

    Activity: 518
    Merit: 500



    View Profile WWW
    October 11, 2014, 11:26:21 PM
     #7308
    Quote from: visdude on October 11, 2014, 10:58:34 PM
    Quote from: Xian01 on October 11, 2014, 09:46:20 PM
    Quote from: visdude on October 11, 2014, 05:54:23 AM
    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.
    I know what you mean.  I have always wanted to stick some temp sensors around the controller and get readings in different configurations/orientations in an effort to conclusively determine if they do make a difference but I can't afford the down time ("if it ain't broke, don't fix it" mentality on my part).  However, the one thing that we can go by to make sense out of it is that we do know that heat rises and in an enclosed environment, it would accumulate at the top.


    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.
    S3 Overclock  |  S3+ Voltage OC  |  Dell 550W PSU Connectors  |  Coincut.com Fast UK BTC Exchange | 
    BTC: 1AwgqD7A2KuQ4WT4273JXZPUf29BAbdp2

  • mdude77
    Legendary
    *
    Offline Offline

    Activity: 1540
    Merit: 1001



    View Profile
    October 11, 2014, 11:50:53 PM
     #7309
    Quote from: Moria843 on October 11, 2014, 09:53:49 PM
    Quote from: mdude77 on October 06, 2014, 01:30:24 AM
    Quote from: Moria843 on October 06, 2014, 01:14:58 AM
    Quote from: mdude77 on October 06, 2014, 01:02:18 AM
    Quote from: Moria843 on October 06, 2014, 12:51:22 AM
    Quote from: IYFTech on October 05, 2014, 11:39:04 PM
    Get the version via ssh. The webUI will always say the older version  Wink
    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
    Must have worked; both showing 4.6.0. Will this version work on my undervoltaged S1s?

    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?

    cdusr/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 mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!

  • visdude
    Legendary
    *
    Offline Offline

    Activity: 1081
    Merit: 1001


    View Profile
    October 11, 2014, 11:58:47 PM
    Last edit: October 12, 2014, 12:39:50 AM by visdude
     #7310
    Quote from: pekatete on October 11, 2014, 11:26:21 PM
    Quote from: visdude on October 11, 2014, 10:58:34 PM
    Quote from: Xian01 on October 11, 2014, 09:46:20 PM
    Quote from: visdude on October 11, 2014, 05:54:23 AM
    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.
    I know what you mean.  I have always wanted to stick some temp sensors around the controller and get readings in different configurations/orientations in an effort to conclusively determine if they do make a difference but I can't afford the down time ("if it ain't broke, don't fix it" mentality on my part).  However, the one thing that we can go by to make sense out of it is that we do know that heat rises and in an enclosed environment, it would accumulate at the top.


    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.

  • MyRig
    Donator
    Hero Member
    *
    Offline Offline

    Activity: 792
    Merit: 510


    support@myrig.com


    View Profile WWW
    October 13, 2014, 02:34:30 AM
     #7311
    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!!


    cdusr/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
    Antminer & DragonMint Repair  E-mail: support@myrig.com   T: @MyRig_com
    Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA

  • MasterRadix
    Full Member
    ***
    Offline Offline

    Activity: 224
    Merit: 100


    View Profile
    October 13, 2014, 10:13:07 AM
     #7312
    Dear Bitmain,

    I recommend you to do a service like spondoolies tech. Free shipping or 1 month free hosting.

  • Moria843
    Sr. Member
    ****
    Offline Offline

    Activity: 442
    Merit: 250


    Found Lost beach - quiet now


    View Profile
    October 13, 2014, 02:33:31 PM
     #7313
    Quote from: BitmainWarranty on October 13, 2014, 02:34:30 AM
    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!!


    cdusr/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. Cool
    Hot time, summer in the city, back of my mine getting hot & gritty!!!

  • bspurloc
    Hero Member
    *****
    Offline Offline

    Activity: 569
    Merit: 500


    View Profile
    October 13, 2014, 08:15:29 PM
     #7314
    Quote from: Moria843 on October 13, 2014, 02:33:31 PM
    Quote from: BitmainWarranty on October 13, 2014, 02:34:30 AM
    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!!


    cdusr/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. Cool

    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 cpsbin/rebootsbin/Reboot ; chmod +xsbin/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?

  • Coinnilingus
    Newbie
    *
    Offline Offline

    Activity: 26
    Merit: 0


    View Profile
    October 14, 2014, 12:04:48 AM
    Last edit: October 14, 2014, 02:35:20 AM by Coinnilingus
     #7315
    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 ?

  • MyRig
    Donator
    Hero Member
    *
    Offline Offline

    Activity: 792
    Merit: 510


    support@myrig.com


    View Profile WWW
    October 14, 2014, 02:58:08 AM
     #7316
    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



    Quote from: Coinnilingus on October 14, 2014, 12:04:48 AM
    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.   
    Antminer & DragonMint Repair  E-mail: support@myrig.com   T: @MyRig_com
    Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA

  • MyRig
    Donator
    Hero Member
    *
    Offline Offline

    Activity: 792
    Merit: 510


    support@myrig.com


    View Profile WWW
    October 14, 2014, 03:36:06 AM
     #7317
    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 ?
    Antminer & DragonMint Repair  E-mail: support@myrig.com   T: @MyRig_com
    Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA

  • Coinnilingus
    Newbie
    *
    Offline Offline

    Activity: 26
    Merit: 0


    View Profile
    October 14, 2014, 03:51:01 AM
     #7318
    Quote from: BitmainWarranty on October 14, 2014, 03:36:06 AM
    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 ?


    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. 

  • MyRig
    Donator
    Hero Member
    *
    Offline Offline

    Activity: 792
    Merit: 510


    support@myrig.com


    View Profile WWW
    October 14, 2014, 04:04:30 AM
     #7319
    @Coinnilingus

    Sent you PM for the RMA process info.
    Antminer & DragonMint Repair  E-mail: support@myrig.com   T: @MyRig_com
    Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA

  • btchigh
    Newbie
    *
    Offline Offline

    Activity: 3
    Merit: 0


    View Profile
    October 14, 2014, 04:40:07 AM
     #7320
    Just looked at the ordering 10x S3-B10, and noted no more DHL shipping choice to US (only UPS), and shipping cost of 1.1 BTC...!
    ...cancelled..! No Thx. I see the same type costs building on the S4 side.. Sad
    Pages: « 1 ... 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 [366] 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 ... 515 »
      Print  
Page 365
Viewing Page: 366

IRLBTC™ © 2025 IRLBTC.com