|
xjack
|
 |
July 30, 2014, 01:58:21 AM |
|
How do I tell what version of the firmware I have?
Thanks!
WebUI - Status->Kernel Log. The first line ends with a date, it corresponds to the build date. Firmware date is the filename that bitmain assigned. Linux version 3.10.12 (xxl@ubuntu) (gcc version ...snip... #140 Mon Jul 21 17:27:04 CST 2014 so... antMiner_S320140721.bin = July 21, 2014 build. |
|
|
|
Cryptoexpert
Newbie
 Offline
Activity: 3
Merit: 0
|
|
July 30, 2014, 05:38:28 AM |
|
hello all:)
i have always temp 0 but my fan changes speed from time to time. is there any way to check the sensors?
Firmware #134 Fri Jul 11 10:42:43 CST 2014
|
|
|
|
|
emediacoin
Newbie
Offline
Activity: 7
Merit: 0
|
|
July 30, 2014, 07:35:30 AM |
|
hello all:)
i have always temp 0 but my fan changes speed from time to time. is there any way to check the sensors?
Firmware #134 Fri Jul 11 10:42:43 CST 2014
I am having the same issue... |
|
|
|
|
|
Lucko
|
|
July 30, 2014, 03:27:52 PM
Last edit: July 30, 2014, 03:40:39 PM by Lucko |
|
I had same issue. It was a solderbridge on one of the hashing boards on other side of a flat cable connector. Removed it and it start showing temps.
|
|
|
|
|
macgyver007
Member
Offline
Activity: 105
Merit: 10
|
|
July 31, 2014, 07:26:56 PM |
|
generated a table to work with, based on the S1/S2 tables: ...package 'cgminer'
config 'asic-freq' 'default'
#option 'freq_value' '1486' #262.5M
#option 'chip_freq' '262.5'
#option 'timeout' '15'
#option 'freq_value' '1386' #250M
#option 'chip_freq' '250'
#option 'timeout' '16'
#option 'freq_value' '1306' #243.75M
#option 'chip_freq' '243.75'
#option 'timeout' '17'
#option 'freq_value' '1286' #237.5M
#option 'chip_freq' '237.5'
#option 'timeout' '17'
#option 'freq_value' '1206' #231.25M
#option 'chip_freq' '231.5'
#option 'timeout' '18'
#option 'freq_value' '1185' #225M
#option 'chip_freq' '225'
#option 'timeout' '18'
option 'freq_value' '1106' #218.75M
option 'chip_freq' '218.75'
option 'timeout' '18'
#option 'freq_value' '1086' #212.5M
#option 'chip_freq' '212.5'
#option 'timeout' '18'
#option 'freq_value' '0782' #200M
#option 'chip_freq' '200'
#option 'timeout' '20'
first off thanks to you. second can you find a number between 200 and 212.50 ( 206.25 ) comes to mind third can you find something for 215.625 my guess for 206.25 would be (use at your own risk): option 'freq_value' '1006' #206.25M option 'chip_freq' '206.25' option 'timeout' '19' With all my due respect for your time and effort, but this table is NOT very applicable to S3... You can NOT apply the same S1 math/calculations... to S3, because these are using different chips with different PFD (PLL Frequency Divider...I guess), subject to different conditions...due to chips redesign...I guess...  BM frequency table - from BM1382 datasheet ...: Work Input timing Clock Freq.(M) Hash rate(G) Reg.value Ideal delay(ms) Recommenddelay(ms) 100 6.30 0783 42.6 38 125 7.88 0983 34.0 31 150 9.45 0b83 28.4 26 175 11.03 0d83 24.3 22 200 12.60 0782 21.3 19 225 14.18 0882 18.9 17 250 15.75 0982 17.0 15 275 17.33 0a82 15.5 14 300 18.90 0b82 14.2 13 325 20.48 0c82 13.1 12 350 22.05 0d82 12.2 11 375 23.63 0e82 11.3 10 400 25.20 08f2 10.6 10 These are the same in S3's "asic-freq" file... Conditions for S3 valid frequency divider's values now are different...check them here...: https://bitmaintech.com/files/download/BM1382_Datasheet_v3.0.pdf ... Pay attention to ..." For normal operation the following constrains MUST be satisfied..." I did NOT check Your value(s) on my S3's, but seems like they are NOT the same "animals"...  Cheers ZiG Agree Bitmain chart is much different for the same values...and they follow the equation..I wouldn't use the above chart values only the ones from the BITMAIN specsheet |
|
|
|
|
|
ZiG
|
|
August 01, 2014, 03:06:52 AM |
|
generated a table to work with, based on the S1/S2 tables: ...package 'cgminer'
config 'asic-freq' 'default'
#option 'freq_value' '1486' #262.5M
#option 'chip_freq' '262.5'
#option 'timeout' '15'
#option 'freq_value' '1386' #250M
#option 'chip_freq' '250'
#option 'timeout' '16'
#option 'freq_value' '1306' #243.75M
#option 'chip_freq' '243.75'
#option 'timeout' '17'
#option 'freq_value' '1286' #237.5M
#option 'chip_freq' '237.5'
#option 'timeout' '17'
#option 'freq_value' '1206' #231.25M
#option 'chip_freq' '231.5'
#option 'timeout' '18'
#option 'freq_value' '1185' #225M
#option 'chip_freq' '225'
#option 'timeout' '18'
option 'freq_value' '1106' #218.75M
option 'chip_freq' '218.75'
option 'timeout' '18'
#option 'freq_value' '1086' #212.5M
#option 'chip_freq' '212.5'
#option 'timeout' '18'
#option 'freq_value' '0782' #200M
#option 'chip_freq' '200'
#option 'timeout' '20'
first off thanks to you. second can you find a number between 200 and 212.50 ( 206.25 ) comes to mind third can you find something for 215.625 my guess for 206.25 would be (use at your own risk): option 'freq_value' '1006' #206.25M option 'chip_freq' '206.25' option 'timeout' '19' With all my due respect for your time and effort, but this table is NOT very applicable to S3... You can NOT apply the same S1 math/calculations... to S3, because these are using different chips with different PFD (PLL Frequency Divider...I guess), subject to different conditions...due to chips redesign...I guess... BM frequency table - from BM1382 datasheet ...: Work Input timing Clock Freq.(M) Hash rate(G) Reg.value Ideal delay(ms) Recommenddelay(ms) 100 6.30 0783 42.6 38 125 7.88 0983 34.0 31 150 9.45 0b83 28.4 26 175 11.03 0d83 24.3 22 200 12.60 0782 21.3 19 225 14.18 0882 18.9 17 250 15.75 0982 17.0 15 275 17.33 0a82 15.5 14 300 18.90 0b82 14.2 13 325 20.48 0c82 13.1 12 350 22.05 0d82 12.2 11 375 23.63 0e82 11.3 10 400 25.20 08f2 10.6 10 These are the same in S3's "asic-freq" file... Conditions for S3 valid frequency divider's values now are different...check them here...: https://bitmaintech.com/files/download/BM1382_Datasheet_v3.0.pdf ... Pay attention to ..." For normal operation the following constrains MUST be satisfied..." I did NOT check Your value(s) on my S3's, but seems like they are NOT the same "animals"... Cheers ZiG Agree Bitmain chart is much different for the same values...and they follow the equation..I wouldn't use the above chart values only the ones from the BITMAIN specsheet I am trying to get the pattern of the smaller steps...like 12.5MHz...6.75Mhz ...etc... |
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
August 01, 2014, 03:55:56 AM |
|
Anyone that updated firmware that was overclocked? I have one happy overclocked a little. I'm just scared to mess with whats working. Wondering what you overclocks think of newer firmware. I don't care about beeps just speed  |
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
August 01, 2014, 12:45:55 PM |
|
Anyone that updated firmware that was overclocked? I have one happy overclocked a little. I'm just scared to mess with whats working. Wondering what you overclocks think of newer firmware. I don't care about beeps just speed I dropped the new firmware on my batch 1 units the day it was released. It had absolutely no impact on their ability (or, really lack thereof) to over clock. My batch 4 units all came with that firmware installed from the factory. I have not yet tried to over clock the batch 4 units, although every one of them is very happily hashing at 440GH/s, so I might tweak them a little and see what happens. |
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
philipma1957
Legendary
Offline
Activity: 4158
Merit: 8042
'The right to privacy matters'
|
|
August 01, 2014, 06:31:28 PM |
|
Anyone that updated firmware that was overclocked? I have one happy overclocked a little. I'm just scared to mess with whats working. Wondering what you overclocks think of newer firmware. I don't care about beeps just speed I dropped the new firmware on my batch 1 units the day it was released. It had absolutely no impact on their ability (or, really lack thereof) to over clock. My batch 4 units all came with that firmware installed from the factory. I have not yet tried to over clock the batch 4 units, although every one of them is very happily hashing at 440GH/s, so I might tweak them a little and see what happens. good news on the batch 4 gear. I have 2 coming today I want the same results 440 at 218 freq. and the new firmware |
|
|
|
Jorsher
Newbie
Offline
Activity: 7
Merit: 0
|
|
August 01, 2014, 06:56:04 PM |
|
My two B1 arrived in the middle east today. Had to go to USA then be reshipped...
Anyway. One of them had the old firmware and was set to 350mhz from the factory in the cleanly formatted asic-freq. Obviously didn't run worth a crap and every chip x'ed out. WTF? The other had the new firmware and was set at 218.75mhz in a sloppy as hell asic-freq.
I updated the other to the latest firmware, added the 218.75 settings, and it ran fine.
At them both to 250mhz. Both have one chip x'ed. One has averaged 482ghs and the other 379ghs. Going to try 237mhz and see how they go, and order some thermal paste which won't arrive for two weeks to clean their mess...
350mhz from the factory? WTF bitmaintech?
|
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
August 01, 2014, 07:03:21 PM |
|
Anyone that updated firmware that was overclocked? I have one happy overclocked a little. I'm just scared to mess with whats working. Wondering what you overclocks think of newer firmware. I don't care about beeps just speed I dropped the new firmware on my batch 1 units the day it was released. It had absolutely no impact on their ability (or, really lack thereof) to over clock. My batch 4 units all came with that firmware installed from the factory. I have not yet tried to over clock the batch 4 units, although every one of them is very happily hashing at 440GH/s, so I might tweak them a little and see what happens. good news on the batch 4 gear. I have 2 coming today I want the same results 440 at 218 freq. and the new firmware So, just for fun I've tried a few different clock settings on the batch 4 gear. One unit clocked successfully up to 250 with all "o" chip status; however, the HW error rate was quite high, and for some reason it never made it above 400GH/s. I have since set that unit to 237.5, and it has been hashing at 475GH/s for about 3 hours now. Another unit at 250 immediately started showing "x" in a few chips. I set it to 237.5 and it, too, has been hashing at 475 for the past 3 hours. Yet another unit is like my batch 1 units... just won't over clock at all, but is very happy at 218.75 and 440GH/s. One thing I have noticed... my batch 1 units have almost nonexistent hardware errors. After hashing for the past 3 hours, one has an error rate of 0.0046% and the other is 0.00079%. All told: Batch 1| Clock | Speed | HW Error % | | 218.75 | 440.33 | 0.0046% | | 212.5 | 428.36 | 0.00079% |
Batch 4| Clock | Speed | HW Error % | | 237.5 | 476.14 | 0.1079% | | 237.5 | 475.11 | 0.1932% | | 218.75 | 441.72 | 0.0166% |
|
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
philipma1957
Legendary
Offline
Activity: 4158
Merit: 8042
'The right to privacy matters'
|
|
August 01, 2014, 10:53:32 PM |
|
my 2 from batch 4 came in. since no beep they must have the new firmware A screen shot of the 2. I left one alone. I clocked one to 225  |
|
|
|
bitmutiny
Member
Offline
Activity: 91
Merit: 11
No banking,Only Bitcoin!
|
|
August 02, 2014, 12:31:07 AM |
|
I have had 2 units from batch 1 running like freakin champs set to 250mhz giving me 505-510 ghs on btcguild (best hashrate out of eligius and ghash) for almost two weeks. To say the least I'm stoked. If somebody wants to post the correct #'s for 262.5mhz I will consider testing. If all goes well I'll push them up to 275mhz. What's the worst that could happen as long as I keep a close eye on them?   |
|
|
|
|
chadwickx16
|
|
August 02, 2014, 01:10:50 AM |
|
I have had 2 units from batch 1 running like freakin champs set to 250mhz giving me 505-510 ghs on btcguild (best hashrate out of eligius and ghash) for almost two weeks. To say the least I'm stoked.
If somebody wants to post the correct #'s for 262.5mhz I will consider testing. If all goes well I'll push them up to 275mhz. What's the worst that could happen as long as I keep a close eye on them?
Best of luck, I got 2 B2's that won't OC over 218.75. |
|
|
|
|
squashpile
|
|
August 02, 2014, 01:47:18 AM |
|
I have one batch 4 that shows fan speed of 0. Not a big deal because the fan is working. Just wondering if anyone else has that problem? The temp sensor is working. Just not fan speed on chain 2.
Seems fine so far running @ 225 too.
|
SquashPool - 0% Fee - Dedicated P2Pool VPS - Atlanta, GA - SSD - Gig uplink
|
|
|
|
ZiG
|
|
August 02, 2014, 03:12:42 AM |
|
I have one batch 4 that shows fan speed of 0. Not a big deal because the fan is working. Just wondering if anyone else has that problem? The temp sensor is working. Just not fan speed on chain 2.
Seems fine so far running @ 225 too.
Probably a bad PWM sensor...or a bad wiring for it...Try to swap with the other, working fan... ZiG |
|
|
|
|
|
squashpile
|
|
August 02, 2014, 03:31:43 AM |
|
Thanks for the info ZiG. I'll open it up and get around to it eventually. I have one batch 4 that shows fan speed of 0. Not a big deal because the fan is working. Just wondering if anyone else has that problem? The temp sensor is working. Just not fan speed on chain 2.
Seems fine so far running @ 225 too.
Probably a bad PWM sensor...or a bad wiring for it...Try to swap with the other, working fan... ZiG |
SquashPool - 0% Fee - Dedicated P2Pool VPS - Atlanta, GA - SSD - Gig uplink
|
|
|
|
ZiG
|
|
August 02, 2014, 03:49:20 AM |
|
Thanks for the info ZiG. I'll open it up and get around to it eventually. I have one batch 4 that shows fan speed of 0. Not a big deal because the fan is working. Just wondering if anyone else has that problem? The temp sensor is working. Just not fan speed on chain 2.
Seems fine so far running @ 225 too.
Probably a bad PWM sensor...or a bad wiring for it...Try to swap with the other, working fan... ZiG Glad to help, buddy... |
|
|
|
|
catoboli
Member
Offline
Activity: 78
Merit: 10
|
|
August 02, 2014, 05:29:02 PM |
|
I purchased mine through eBay and must have gotten an earlier batch.
i am trying to OC i was able to oc up to 237.5 without getting any x's but power draw from the wall doesn't go up and my hash rate goes down. when i leave at 218.5 i get 450 @350w at the wall(i use platinum rated PSUs). i can't even clock this thing at 225 without the HR going down.
Have we found a fix for this yet or is it just how its gonna be?
|
|
|
|
catoboli
Member
Offline
Activity: 78
Merit: 10
|
|
August 02, 2014, 05:53:52 PM |
|
I purchased mine through eBay and must have gotten an earlier batch.
i am trying to OC i was able to oc up to 237.5 without getting any x's but power draw from the wall doesn't go up and my hash rate goes down. when i leave at 218.5 i get 450 @350w at the wall(i use platinum rated PSUs). i can't even clock this thing at 225 without the HR going down.
Have we found a fix for this yet or is it just how its gonna be?
Additionally Ive noticed that as soon as i start overlocking my reject rate goes way up, somewhere in the neighborood of 25% HW stays very low. might this play a role in why my 5s hash is 480ish but average is closer to 400? |
|
|
|
|
