Bitcoin Forum
July 12, 2024, 03:08:48 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: S1 to S3 Upgrade hashing speed off - HELP  (Read 1413 times)
bmoscato (OP)
Sr. Member
****
Offline Offline

Activity: 361
Merit: 267


View Profile
September 25, 2014, 12:01:34 PM
Last edit: September 25, 2014, 02:07:36 PM by bmoscato
 #1

I installed one of the upgrades for the S1 to s3 and my unit is only hashing between 215 and 270GH/S.  I flashes the ROM to antMiner_S320140826.bin.

I do not show temperature, fan 2 speed and my hash rate is slow.  I also do not show a BestShare number, yet the unit has ben hashing for over 9 hours.  I tried going directly to GHASH and also using BFG Miner in proxy mode, both yield the same results.  I tried frequencies 250, 225 and 218.75.

What should I do next?


bmoscato (OP)
Sr. Member
****
Offline Offline

Activity: 361
Merit: 267


View Profile
September 25, 2014, 10:05:14 PM
 #2

I reflashed the unit and had the same results when I pointed the miner at BFG Miner 4.8.0 in proxy mode... I tried pointing the unit directly at GHASH and its hashing around 470 GH/s.

I guess there's some limitation in BFG Miner?
buysolar
Member
**
Offline Offline

Activity: 125
Merit: 12


View Profile
September 25, 2014, 11:02:21 PM
 #3

Think I'll join in with your thread. Mines not hashing at all, showing 4 chains:

bmoscato (OP)
Sr. Member
****
Offline Offline

Activity: 361
Merit: 267


View Profile
September 26, 2014, 12:53:53 AM
 #4

Did you email their support? They got back me somewhat quickly. Did you try re-flashing with the S3+ firmware and make sure to uncheck "save settings" again? This may resolve the issue...
buysolar
Member
**
Offline Offline

Activity: 125
Merit: 12


View Profile
September 26, 2014, 08:00:19 AM
 #5

Did you email their support? They got back me somewhat quickly. Did you try re-flashing with the S3+ firmware and make sure to uncheck "save settings" again? This may resolve the issue...
Problem solved. I think the 4 pin connector terminal on the new board was not fully seated. It appears to be working properly now.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!