dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 24, 2015, 08:41:16 AM |
|
Is there any way to tell which S3's have the variable voltage?
my one and only S3 is a batch 8 everything else i have is S3+
I would have thought the PCBs look physically different in the DC/DC area, but I've personally only seen one variant. I do know that there are many, many, many variants though.
|
|
|
|
|
|
|
|
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
pekatete
|
|
January 24, 2015, 10:46:29 AM |
|
Going further than others: Don't bother, you're more likely to end up with 4 fried PSUs and potentially a damaged S3. Even if you could underclock sufficiently you'd still be cross loading 2 PSUs. And even if that wasn't a problem (which it is), you're running PSUs at 24/7 load which they're likely not designed to do. tldr, don't.
Powering each blade with a different PSU is NOT an issue - that has been sufficiently answered. The rest of your assertions @dogie, are your usual waffle .... thin on facts, un-necessarily verbose!
|
|
|
|
marvykkio
|
|
January 24, 2015, 11:05:04 AM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 24, 2015, 01:10:57 PM |
|
Going further than others: Don't bother, you're more likely to end up with 4 fried PSUs and potentially a damaged S3. Even if you could underclock sufficiently you'd still be cross loading 2 PSUs. And even if that wasn't a problem (which it is), you're running PSUs at 24/7 load which they're likely not designed to do. tldr, don't.
Powering each blade with a different PSU is NOT an issue - that has been sufficiently answered. The rest of your assertions @dogie, are your usual waffle .... thin on facts, un-necessarily verbose! I was suggesting 2 PSUs per board, because you're going to struggle to do ANYTHING with 60W per PCB. If you've got something to contribute, keep it civil please.
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 24, 2015, 01:11:16 PM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW Can you post a screenshot of your status please?
|
|
|
|
pekatete
|
|
January 24, 2015, 01:37:31 PM |
|
Going further than others: Don't bother, you're more likely to end up with 4 fried PSUs and potentially a damaged S3. Even if you could underclock sufficiently you'd still be cross loading 2 PSUs. And even if that wasn't a problem (which it is), you're running PSUs at 24/7 load which they're likely not designed to do. tldr, don't.
Powering each blade with a different PSU is NOT an issue - that has been sufficiently answered. The rest of your assertions @dogie, are your usual waffle .... thin on facts, un-necessarily verbose! I was suggesting 2 PSUs per board, because you're going to struggle to do ANYTHING with 60W per PCB. If you've got something to contribute, keep it civil please. And what was new in your suggestion that was not expressly covered prior to your follow-up waffle? 2 PSU's per board or 3 60W PSU's per 6 pin PCI-E plug is, in the context, the same thing ... and that was adequately pointed out; Thus aside from being verbose in your going further comment, you brought nothing new to the table, well, aside from your verbosity ..... (read waffle!). Now if you really want to know what civility entails, then you'd be glad to know that pretence is counter to the universal norms of civility ... aka, if you (and here I mean dogie) have nothing to say, do not say it!
|
|
|
|
pekatete
|
|
January 24, 2015, 01:43:20 PM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW Can you post a screenshot of your status please? It is well documented in these threads that starting with the Dec firmware, all updates result in increased HW errors and / or occurance of X's on chips (if not both) to a large extent. That you have not picked up on this and keep advising people to update is a truly astounding feat of stupidity. I'd err on the side of advising to only update firmware if there is some catastrophic event that's occured.
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 24, 2015, 02:01:28 PM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW Can you post a screenshot of your status please? It is well documented in these threads that starting with the Dec firmware, all updates result in increased HW errors and / or occurance of X's on chips (if not both) to a large extent. That you have not picked up on this and keep advising people to update is a truly astounding feat of stupidity. I'd err on the side of advising to only update firmware if there is some catastrophic event that's occured. That's not true. Just ignore him.
|
|
|
|
pekatete
|
|
January 24, 2015, 02:39:59 PM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW Can you post a screenshot of your status please? It is well documented in these threads that starting with the Dec firmware, all updates result in increased HW errors and / or occurance of X's on chips (if not both) to a large extent. That you have not picked up on this and keep advising people to update is a truly astounding feat of stupidity. I'd err on the side of advising to only update firmware if there is some catastrophic event that's occured. That's not true. Just ignore him. Stick your head in the sand with your own rigs and don't advise people to do what others (including myself) have observed and reported in these threads. By your own admission you only have seen one make of S3, but you keep assuming all S3 variants are the same in your advice. I do not expect you to alter your opinion, not even with empirical evidence contrary to your advice, but that is more a reflection on you than the authenticity of the facts. I've come to expect waffle responses from you to a large extent, but do not hold your breath 'cause if i happen to stumble on it, I'll put the record straight. So here goes, if your S3 (and this is more true for S3's as opposed to S3+'s) is running OK, there is no performance reason to update your firmware. The Oct firmware that does not respond to the reset button is inherently irrecoverable should disaster occur, but runs a lot better than subsequent firmware releases, aka Nov & Dec 2014 and Jan 2015 firmwares. The reset button flaw of the Oct firmware is critical, but I have yet to hear of anyone having a bricked control board without having fidgeted with firmware updates, so I'd err on not updating at the expense of increased HW % and /or X's and / or o's on chips.
|
|
|
|
bitsolutions
|
|
January 24, 2015, 06:00:38 PM |
|
Stick your head in the sand with your own rigs and don't advise people to do what others (including myself) have observed and reported in these threads. By your own admission you only have seen one make of S3, but you keep assuming all S3 variants are the same in your advice. I do not expect you to alter your opinion, not even with empirical evidence contrary to your advice, but that is more a reflection on you than the authenticity of the facts. I've come to expect waffle responses from you to a large extent, but do not hold your breath 'cause if i happen to stumble on it, I'll put the record straight.
So here goes, if your S3 (and this is more true for S3's as opposed to S3+'s) is running OK, there is no performance reason to update your firmware. The Oct firmware that does not respond to the reset button is inherently irrecoverable should disaster occur, but runs a lot better than subsequent firmware releases, aka Nov & Dec 2014 and Jan 2015 firmwares.
The reset button flaw of the Oct firmware is critical, but I have yet to hear of anyone having a bricked control board without having fidgeted with firmware updates, so I'd err on not updating at the expense of increased HW % and /or X's and / or o's on chips.
People have bricked the Oct 24'th firmware a lot by messing up their network settings. I haven't seen any performance issues with the Jan firmware although I generally only look at total hashrate stats.
|
Mining Software Developer.
|
|
|
aarons6
Legendary
Offline
Activity: 1736
Merit: 1006
|
|
January 25, 2015, 02:38:44 AM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW Can you post a screenshot of your status please? It is well documented in these threads that starting with the Dec firmware, all updates result in increased HW errors and / or occurance of X's on chips (if not both) to a large extent. That you have not picked up on this and keep advising people to update is a truly astounding feat of stupidity. I'd err on the side of advising to only update firmware if there is some catastrophic event that's occured. That's not true. Just ignore him. it is true, i tested it.. the 2015 firmware has way more errors then the 12/19 one.. it went from .0008% to .03% in just 24 hours running, then i got 1 x which i never had before. i would use the 12/19 FW.. it seems stable. perhaps its from the turning off the auto voltage?
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 25, 2015, 09:39:12 AM |
|
I have installed the latest firmware 01.09.2015, really do not be problems, but there are always errors HW Can you post a screenshot of your status please? It is well documented in these threads that starting with the Dec firmware, all updates result in increased HW errors and / or occurance of X's on chips (if not both) to a large extent. That you have not picked up on this and keep advising people to update is a truly astounding feat of stupidity. I'd err on the side of advising to only update firmware if there is some catastrophic event that's occured. That's not true. Just ignore him. it is true, i tested it.. the 2015 firmware has way more errors then the 12/19 one.. it went from .0008% to .03% in just 24 hours running, then i got 1 x which i never had before. i would use the 12/19 FW.. it seems stable. perhaps its from the turning off the auto voltage? That 0.0292% increase is so insignificant that its the equivalent of going from 460GH to 459.9GH. There are other useful improvements over the 12/19 included. As to pekatete saying 12/19 has hardware errors is insane as there was no change. And as bitsolutions says, fixing that reset button functionality is imperative and recommended for all. tldr if you are worried about 0.1GH, use 12/19, if not use the latest.
|
|
|
|
quakefiend420
Legendary
Offline
Activity: 784
Merit: 1000
|
|
January 25, 2015, 09:40:40 AM |
|
Is there any way to tell which S3's have the variable voltage?
my one and only S3 is a batch 8 everything else i have is S3+
I'd like to know the answer to this too. I've installed the firmware that should allow voltage control on one of my S3s and it appears to have no effect. Any way to determine batch without opening them up?
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 25, 2015, 09:56:28 AM |
|
Is there any way to tell which S3's have the variable voltage?
my one and only S3 is a batch 8 everything else i have is S3+
I'd like to know the answer to this too. I've installed the firmware that should allow voltage control on one of my S3s and it appears to have no effect. Any way to determine batch without opening them up? The versions are cross batch so it doesn't help. The solution is as you've done, alter voltage at the same clocks and see if power consumpption changes.
|
|
|
|
oldjoker
Newbie
Offline
Activity: 5
Merit: 0
|
|
January 25, 2015, 11:43:05 AM |
|
what is the best firmware for S3+ and S3 ? do they have the same firmware ?
|
|
|
|
MyRig
Donator
Hero Member
Offline
Activity: 792
Merit: 510
support@myrig.com
|
|
January 25, 2015, 12:03:23 PM |
|
yes, you can use the same S3+ firmware for the S3. If your miner has an older firmware prior to October 24 version, please update to the newer firmware such as December 19th version. Other wise, if your miner is working, please keep it as is!!! https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633what is the best firmware for S3+ and S3 ? do they have the same firmware ?
|
Antminer & DragonMint Repair E-mail: support@myrig.com T: @MyRig_com Return Address: MyRig 3700 Quebec Street, Unit 100-239, Denver, Colorado 80207, USA
|
|
|
sloopy
|
|
January 25, 2015, 04:33:41 PM |
|
yes, you can use the same S3+ firmware for the S3. If your miner has an older firmware prior to October 24 version, please update to the newer firmware such as December 19th version. Other wise, if your miner is working, please keep it as is!!! https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633what is the best firmware for S3+ and S3 ? do they have the same firmware ?
I think you should post this at every S3 thread. I have a few going now but knowing this would have been nice a month ago. The reset button doesn't work if we leave it "As Is" older than 12-19, but if on October 14 you have best hash rate. Maybe consider adding a note regarding selling your S3: Change the login and pass back to root / root please. For the purchasers out here it makes things work when we open the box if we can access the GUI.
|
Transaction fees go to the pools and the pools decide to pay them to the miners. Anything else, including off-chain solutions are stealing and not the way Bitcoin was intended to function. Make the block size set by the pool. Pool = miners and they get the choice.
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 25, 2015, 05:21:27 PM |
|
Maybe consider adding a note regarding selling your S3: Change the login and pass back to root / root please. For the purchasers out here it makes things work when we open the box if we can access the GUI. If you're buying a second hand S3 from Ebay / Amazon etc, that's up to the seller. Bitmain can't regulate that or force sellers to upgrade their firmware / set password to default.
|
|
|
|
pekatete
|
|
January 25, 2015, 05:55:18 PM |
|
Maybe consider adding a note regarding selling your S3: Change the login and pass back to root / root please. For the purchasers out here it makes things work when we open the box if we can access the GUI. If you're buying a second hand S3 from Ebay / Amazon etc, that's up to the seller. Bitmain can't regulate that or force sellers to upgrade their firmware / set password to default. Why not state the obvious then? I'd say having a working reset button resolves the issue sloopy asked, but seeing it is bitmain who released and distributed firmware that disabled the reset button, it is not too much to ask of bitmain. If that is too much, then bitmain should offer a free service to recover locked out S3's, since the lock-out can only happen when the reset button is not functional due to the botched firmware. Now tell me, which is the cheaper option for bitmain?
|
|
|
|
adaseb
Legendary
Offline
Activity: 3752
Merit: 1710
|
|
January 26, 2015, 12:14:23 PM |
|
Hey guys,
If you want WIFI to work on your S3.
Just disassemble an old laptop. Pretty much any laptop made in the last decade which has wifi. And use the antenna in your S3.
You basically need to disassemble the entire laptop to get to the LCD, and disassemble to LCD to see the antenna's. It has the perfect connector.
At first I tried using an antenna from an iPhone but those were smaller. But any laptop wifi's should work. If you don't know how to disassemble a laptop just go to youtube and search for disassemble instructions.
WIthout an antenna it only detected 3 networks. 50% max range and kept disconecting every few hours about a foot away from the router. With the antenna detects about 40 networks and my router is 99% signal strength.
No idea why include the wifi adapter but not a simple $0.50 antenna.
|
|
|
|
|