BITMAIN Antminer S3 support and OverClocking thread - page 22.

Rabinovitch

legendary

Activity: 2030

Merit: 1076

BTCLife.global participant

Quote from: pekatete on August 30, 2014, 03:45:47 AM

as the new firmware has been noted for reverting the OC.

Why does it works normally on my S3s?..

Quote from: Darthswan on August 30, 2014, 08:12:23 AM

After update the firmware, go to the miner configuration tab and click on advance settings. You can change the clock speed there.

And press "Save&Apply" button to get it working at desireable frequency. Roll Eyes

Darthswan

hero member

Activity: 818

Merit: 508

Quote from: BossHog on August 30, 2014, 01:25:08 AM

Quote from: Rabinovitch on August 30, 2014, 12:19:08 AM

Quote from: BossHog on August 29, 2014, 11:58:38 PM

hello all, i have a stubborn s3 that will not accept OC...the frequency remains at the stock 218.75. i have tried selecting 237, 250, etc. and i cannot OC. i am plagued by the 218.75 frequency. any suggestions ?

Yep. Update a firmware from Bitmain's site and overclock your S3(s) via web-interface. Cool

maybe i am just tired, but this is getting worse. LoL i updated the firmware to the August file. now the antminer will not hash at all. it has both the red and green LED's on. and there is no frequency in the web UI. i went back into SSH, and have selected the frequency. however, the ant's red LED will not turn off. this is comical.

After update the firmware, go to the miner configuration tab and click on advance settings. You can change the clock speed there.

pekatete

hero member

Activity: 518

Merit: 500

Quote from: Rabinovitch on August 30, 2014, 12:19:08 AM

Quote from: BossHog on August 29, 2014, 11:58:38 PM

hello all, i have a stubborn s3 that will not accept OC...the frequency remains at the stock 218.75. i have tried selecting 237, 250, etc. and i cannot OC. i am plagued by the 218.75 frequency. any suggestions ?

Yep. Update a firmware from Bitmain's site and overclock your S3(s) via web-interface. Cool

Why update the firmaware?
After changing the speed all you had to do is reboot.
Now you have updated the firmaware, you'll have to do it all over again, only this time you need to change a different file as the new firmware has been noted for reverting the OC.

orviwan

newbie

Activity: 8

Merit: 0

Quote from: BossHog on August 30, 2014, 01:25:08 AM

Quote from: Rabinovitch on August 30, 2014, 12:19:08 AM

Quote from: BossHog on August 29, 2014, 11:58:38 PM

hello all, i have a stubborn s3 that will not accept OC...the frequency remains at the stock 218.75. i have tried selecting 237, 250, etc. and i cannot OC. i am plagued by the 218.75 frequency. any suggestions ?

Yep. Update a firmware from Bitmain's site and overclock your S3(s) via web-interface. Cool

maybe i am just tired, but this is getting worse. LoL i updated the firmware to the August file. now the antminer will not hash at all. it has both the red and green LED's on. and there is no frequency in the web UI. i went back into SSH, and have selected the frequency. however, the ant's red LED will not turn off. this is comical.

Flash the firmware again, but reset all settings too, then reconfigure.

BossHog

newbie

Activity: 2

Merit: 0

Quote from: Rabinovitch on August 30, 2014, 12:19:08 AM

Quote from: BossHog on August 29, 2014, 11:58:38 PM

hello all, i have a stubborn s3 that will not accept OC...the frequency remains at the stock 218.75. i have tried selecting 237, 250, etc. and i cannot OC. i am plagued by the 218.75 frequency. any suggestions ?

Yep. Update a firmware from Bitmain's site and overclock your S3(s) via web-interface. Cool

maybe i am just tired, but this is getting worse. LoL i updated the firmware to the August file. now the antminer will not hash at all. it has both the red and green LED's on. and there is no frequency in the web UI. i went back into SSH, and have selected the frequency. however, the ant's red LED will not turn off. this is comical.

Rabinovitch

legendary

Activity: 2030

Merit: 1076

BTCLife.global participant

Quote from: BossHog on August 29, 2014, 11:58:38 PM

hello all, i have a stubborn s3 that will not accept OC...the frequency remains at the stock 218.75. i have tried selecting 237, 250, etc. and i cannot OC. i am plagued by the 218.75 frequency. any suggestions ?

Yep. Update a firmware from Bitmain's site and overclock your S3(s) via web-interface. Cool

BossHog

newbie

Activity: 2

Merit: 0

hello all, i have a stubborn s3 that will not accept OC...the frequency remains at the stock 218.75. i have tried selecting 237, 250, etc. and i cannot OC. i am plagued by the 218.75 frequency. any suggestions ?

here are the steps i am following:
1. ssh into
2. cd /etc/config (enter)
3. vim asic-freq (enter)
4. type "i"
5. select removing # for new frequency in list
6. deselect old frequency by adding #
7. hit "esc"
8. type ":wq"
9. i go back into ssh mode, and verify that my selections are saved, and all looks how i left it.

am i missing something ? Thanks in advance

xjack

hero member

Activity: 539

Merit: 500

Quote from: JakeTri on August 15, 2014, 02:11:26 PM

Quote from: yosscal on August 15, 2014, 11:51:18 AM

Hi,
I just try to update S320140811 with frequency management.
The frequency 225 is not part of the option (I do not know why?), it goes directly from 218.75 to 237,5. Undecided

Can someone tell me which file to edit to add the 225 frequency in choice?
THX. Wink

The file with frequency values for the advanced page with miner settings is

Code:

/usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

Look at the end of the file for the frequency list.

Here are highlighted in red the lines with new frequency not included in the stock firmware.

Quote

pb:value("13:300:0b82", translate("300M"))
pb:value("14:293.75:1706", translate("293.75M"))
pb:value("14:287.5:0b02", translate("287.5M"))
pb:value("14:281.25:1606", translate("281.25M"))
pb:value("15:275:0a82", translate("275M"))
pb:value("15:268.75:1506", translate("268.75M"))
pb:value("15:262.5:0a02", translate("262.5M"))
pb:value("16:256.25:1406", translate("256.25M"))
pb:value("16:250:0982", translate("250M"))
pb:value("16:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M"))
pb:value("18:218.75:1106", translate("218.75M (default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))

Suggest this be added to the OP to help anyone running newer firmware who wants more OC options from the interface. Thanks JakeTri!

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: Darthswan on August 28, 2014, 03:47:44 PM

Quote from: windpath on August 28, 2014, 03:35:50 PM

...

Don't forget to X 100

Fixed, good catch

Darthswan

hero member

Activity: 818

Merit: 508

Quote from: windpath on August 28, 2014, 03:35:50 PM

It may be worth noting that while not often reported, DiffS (Stales) should also be included...

HW / (HW + DiffA + DiffR + DiffS) = HWE%

Don't forget to X 100

windpath

legendary

Activity: 1258

Merit: 1027

It may be worth noting that while not often reported, DiffS (Stales) should also be included...

HWE% = HW / (HW + DiffA + DiffR + DiffS) * 100

pekatete

hero member

Activity: 518

Merit: 500

Quote from: chadwickx16 on August 28, 2014, 03:14:44 PM

Quote from: pekatete on August 28, 2014, 02:42:50 PM

Quote from: chadwickx16 on August 28, 2014, 02:36:18 PM

HW/(HW+DiffA+DiffR)=HW%

I've always wanted to clarify this, so here goes.
What exactly does DiffR represent? I assumed this represented the number of rejected shares at the current Diff, but its rate of increase seems to be (at times) the size of the rejected share. If that, would that not throw the calculation off?

Here's what I found:

Quote from: optimator on May 17, 2013, 02:24:53 PM

--------------------------------------
Diff1 = The number of Difficulty 1 shares generated
DiffA = The number of Diff1 shares accepted
DiffR = The number of Diff1 shares rejected
LSD = Last Share Difficulty
Discarded = stale shares that cgminer knew were stale so it didn't even send them back to the pool
---------------------------------------

It is strange how the DiffR number differs widely (in shape and size) depending on which pool you mine at and which hardware you deploy.
The S3 for example does not show a best share on some pools whereas the S1 does, in the same breath, the S3 increments DiffR in multiples of 32 on some pools (in the case of ghash DiffR equates to stales) whereas I'd have expected it to be singulars as is on slush.

Which leads me to believe that some stats on the S3 are massaged thus the HW error percentage is ..... who knows!?

chadwickx16

hero member

Activity: 826

Merit: 1000

Quote from: pekatete on August 28, 2014, 02:42:50 PM

Quote from: chadwickx16 on August 28, 2014, 02:36:18 PM

HW/(HW+DiffA+DiffR)=HW%

I've always wanted to clarify this, so here goes.
What exactly does DiffR represent? I assumed this represented the number of rejected shares at the current Diff, but its rate of increase seems to be (at times) the size of the rejected share. If that, would that not throw the calculation off?

Here's what I found:

Quote from: optimator on May 17, 2013, 02:24:53 PM

--------------------------------------
Diff1 = The number of Difficulty 1 shares generated
DiffA = The number of Diff1 shares accepted
DiffR = The number of Diff1 shares rejected
LSD = Last Share Difficulty
Discarded = stale shares that cgminer knew were stale so it didn't even send them back to the pool
---------------------------------------

pekatete

hero member

Activity: 518

Merit: 500

Quote from: chadwickx16 on August 28, 2014, 02:36:18 PM

HW/(HW+DiffA+DiffR)=HW%

I've always wanted to clarify this, so here goes.
What exactly does DiffR represent? I assumed this represented the number of rejected shares at the current Diff, but its rate of increase seems to be (at times) the size of the rejected share. If that, would that not throw the calculation off?

chadwickx16

hero member

Activity: 826

Merit: 1000

Quote from: tbolt on August 28, 2014, 02:03:29 PM

Quote from: chadwickx16 on August 28, 2014, 10:49:51 AM

Quote from: Plumpkatt1 on August 28, 2014, 10:40:58 AM

Hello again.

I just received another S3 and have some questions. First off, how can I tell what batch this S3 is? I already have a Batch 6. I have provided a screenshot below. Please take a look and see what you think. I dont have it OCed. I do have the latest firmware on it. I am having issues with the HW errors. Are these specs too high? Should I b concerned? I have thought about taking it apart and applying new thermal paste. Think that might help?

Thanx again .

You're at a 1.2% HW error rate right now. But everything else looks fine. Looks like it may be a batch 1, especially if you bought it from a third party used.

New to S3's here.

How do you calculate the HW error rate?

What should the HW error rate on an S3 be?

HW/(HW+DiffA+DiffR)=HW%

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: tbolt on August 28, 2014, 02:03:29 PM

New to S3's here.

How do you calculate the HW error rate?

What should the HW error rate on an S3 be?

http://www.coincadence.com/antminer-s1-hardware-error/

tbolt

member

Activity: 74

Merit: 10

Quote from: chadwickx16 on August 28, 2014, 10:49:51 AM

Quote from: Plumpkatt1 on August 28, 2014, 10:40:58 AM

Hello again.

I just received another S3 and have some questions. First off, how can I tell what batch this S3 is? I already have a Batch 6. I have provided a screenshot below. Please take a look and see what you think. I dont have it OCed. I do have the latest firmware on it. I am having issues with the HW errors. Are these specs too high? Should I b concerned? I have thought about taking it apart and applying new thermal paste. Think that might help?

Thanx again .

You're at a 1.2% HW error rate right now. But everything else looks fine. Looks like it may be a batch 1, especially if you bought it from a third party used.

New to S3's here.

How do you calculate the HW error rate?

What should the HW error rate on an S3 be?

pekatete

hero member

Activity: 518

Merit: 500

Quote from: Plumpkatt1 on August 28, 2014, 10:40:58 AM

I just received another S3 and have some questions. First off, how can I tell what batch this S3 is?

The only way that I know of how to tell what batch it is is either buying it yourself from bitmain or asking the person who bought it.

Quote from: Plumpkatt1 on August 28, 2014, 10:40:58 AM

I already have a Batch 6. I have provided a screenshot below. Please take a look and see what you think. I dont have it OCed. I do have the latest firmware on it. I am having issues with the HW errors. Are these specs too high? Should I b concerned? I have thought about taking it apart and applying new thermal paste. Think that might help?

Yep, you ARE having an issue there with the HW errors. Too high for an S3 (and one running at stock frequency at that)!
1. Are you sure you are powering it up adequately? If that, do a power recycle (there may have been a power spike since you turned it on) and see if the errors settle.
2. I have noticed that the HW errors general % varies from pool to pool. I did not think this to be a contributing factor, but I have observed on my S3's that it may indeed be a factor, thus, try hashing on another pool for several hours. That being said, your error rate is far higher than what I'd attribute to a pool.

chadwickx16

hero member

Activity: 826

Merit: 1000

Quote from: Plumpkatt1 on August 28, 2014, 10:40:58 AM

Hello again.

I just received another S3 and have some questions. First off, how can I tell what batch this S3 is? I already have a Batch 6. I have provided a screenshot below. Please take a look and see what you think. I dont have it OCed. I do have the latest firmware on it. I am having issues with the HW errors. Are these specs too high? Should I b concerned? I have thought about taking it apart and applying new thermal paste. Think that might help?

Thanx again .

You're at a 1.2% HW error rate right now. But everything else looks fine. Looks like it may be a batch 1, especially if you bought it from a third party used.

Plumpkatt1

newbie

Activity: 64

Merit: 0

Hello again.

I just received another S3 and have some questions. First off, how can I tell what batch this S3 is? I already have a Batch 6. I have provided a screenshot below. Please take a look and see what you think. I dont have it OCed. I do have the latest firmware on it. I am having issues with the HW errors. Are these specs too high? Should I b concerned? I have thought about taking it apart and applying new thermal paste. Think that might help?

Thanx again .

Topic: BITMAIN Antminer S3 support and OverClocking thread - page 22. (Read 158140 times)