BannedDK (OP)
Member
Offline
Activity: 109
Merit: 10
|
|
January 08, 2016, 05:05:03 PM Last edit: January 11, 2016, 12:00:49 PM by BannedDK |
|
as the subject says, should i upgrade the firmware of all my miners or is it pointless if they run smooth? Im no pro with cgminer or anything. just plug and play. I joined the mining fun about 6 month ago. 3 x S3 old firmware tried to search for an answer but to many post to go through with the words "upgrade firmware" /BannedDk
|
|
|
|
toptek
Legendary
Offline
Activity: 1274
Merit: 1000
|
|
January 09, 2016, 03:14:02 AM |
|
AS a rules never upgrade the firm ware unless there is some thing new in the upgrade or you are having issue that the new firm ware might fix and the Warning is do it at your risk .
but if your like me i do it if it needs it or not @ my own risk , i have this thing about all my PC's etc and keeping them updated with all software they use including the firmware, on any thing i own .
|
|
|
|
OneInchWonder
|
|
January 09, 2016, 04:04:22 AM |
|
If it was we. No. If there is nothing wrong then why go change things.
I have a dead S3 do to fail update.
|
get.uber.com/drive/?invite_code=brianp6308ue
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
January 09, 2016, 04:17:10 AM |
|
If it's an S3, do my update. Faster miner, lower load average, better web display, all known Bitmain bugs not present, newer version of cgminer with all related enhancements ... etc etc https://github.com/kanoi/cgminer-binaries/tree/master/AntS3Generic rules don't apply
|
|
|
|
OneInchWonder
|
|
January 09, 2016, 05:22:54 AM |
|
I will give it try. Is your update for S3, S3+ or both because i have both.
|
get.uber.com/drive/?invite_code=brianp6308ue
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
January 09, 2016, 11:07:09 AM |
|
I will give it try. Is your update for S3, S3+ or both because i have both. Both, but it wont fix a broken miner. My post was to the OP, not to fixing miners that are broken. Put it on the un-broken ones My update can't kill a miner, it's not a flash.
|
|
|
|
BannedDK (OP)
Member
Offline
Activity: 109
Merit: 10
|
|
January 09, 2016, 02:46:01 PM |
|
thanks alot, ill try it out on the s3´s when i got the time. a faster miner is always welcome
|
|
|
|
OneInchWonder
|
|
January 09, 2016, 05:32:43 PM |
|
I will give it try. Is your update for S3, S3+ or both because i have both. Both, but it wont fix a broken miner. My post was to the OP, not to fixing miners that are broken. Put it on the un-broken ones My update can't kill a miner, it's not a flash. Thanks for the info. The broken one is shiped out to Pinhead to look at.
|
get.uber.com/drive/?invite_code=brianp6308ue
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
January 09, 2016, 08:39:46 PM |
|
thanks alot, ill try it out on the s3´s when i got the time. a faster miner is always welcome Oh there might be some misunderstanding there ... It wont hash GHs noticeably faster - you wont get an obvious hash rate increase You will expect a minor improvement there though. The miner code itself is optimised to use way less CPU so it will be faster at processing incoming work, processing shares and sending them out. So everything runs way smoother and way less internal latency in the miner. You'll notice it obviously on the web page itself, it will usually update much faster. ... and of course as I mentioned, you'll see the Load Average much lower (in the top left) I also allow the internal work diff to be higher, closer to the pool value, so that also reduces the amount of internal processing, but shows higher variance on the miner display. That won't, however, change the amount of shares sent to the pool at all, it's an internal performance improvement.
|
|
|
|
OneInchWonder
|
|
January 09, 2016, 09:04:17 PM |
|
Updated both S3 and S3+. Had no problems. I can tell miner is running way better. I looked at the numbers on the top left and they way down from 2.70+ to under .5 most of the time. Also over clocking the S3 is just like S3+ now.
Thanks.
My broken miner had this on it. It was my first miner and wanted to see what this mining is about.
|
get.uber.com/drive/?invite_code=brianp6308ue
|
|
|
BannedDK (OP)
Member
Offline
Activity: 109
Merit: 10
|
|
January 09, 2016, 10:02:42 PM |
|
thanks alot, ill try it out on the s3´s when i got the time. a faster miner is always welcome Oh there might be some misunderstanding there ... It wont hash GHs noticeably faster - you wont get an obvious hash rate increase You will expect a minor improvement there though. The miner code itself is optimised to use way less CPU so it will be faster at processing incoming work, processing shares and sending them out. So everything runs way smoother and way less internal latency in the miner. You'll notice it obviously on the web page itself, it will usually update much faster. ... and of course as I mentioned, you'll see the Load Average much lower (in the top left) I also allow the internal work diff to be higher, closer to the pool value, so that also reduces the amount of internal processing, but shows higher variance on the miner display. That won't, however, change the amount of shares sent to the pool at all, it's an internal performance improvement. i know it wont be Hashing faster, but just perform faster 2 of them are really slow, takes ages to log in and see stats and so on, so a upgrade might be usefull
|
|
|
|
rkinnin
|
|
January 12, 2016, 01:04:45 AM |
|
do you have anything for c1's?
|
|
|
|
kano
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
January 12, 2016, 04:33:37 AM |
|
do you have anything for c1's? No.
|
|
|
|
quadriple7
|
|
February 07, 2016, 02:36:49 PM |
|
yes in my opinion you should do that becouse it will work much better .
|
|
|
|
redukt
Newbie
Offline
Activity: 54
Merit: 0
|
|
February 21, 2016, 04:43:18 AM |
|
do you have anything for c1's? User smit1237 had an update for the C1 which at the very least made the stats page more useful. The site I pulled the update from appears to be offline now however.
|
|
|
|
|