Author

Topic: ANTMINER S3+ Discussion and Support Thread - page 245. (Read 710164 times)

legendary
Activity: 966
Merit: 1003
Dear Community,

Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community.
Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago..  
However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours.

Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or [email protected].

Thank you!

And what about support documents to BFG Miner for Development?
full member
Activity: 125
Merit: 100
Ha.. well there ya go  Tongue
Call off the raid.
hero member
Activity: 741
Merit: 514
https://www.bitmain.com
Dear Community,

Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community.
Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago..  
However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours.

Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or [email protected].

Thank you!
sr. member
Activity: 462
Merit: 250
Does anyone know how Kano was able to write his own version for the S1? Does he have supporting documents? Or did he just come up with a work around?
They had released the code for the driver for the S1.

With a lot of polling from a big customer they eventually released the S2 driver.

The S3 driver we've had no luck getting out of them.


To whom it may concern:

We WERE loyal BITMAIN customers owing to their shipping model, quality of product, and expeditious order fulfillment.
We WERE gearing up to place a large S3+ order.
That capex expenditure is now on hold.
We are now investigating a large purchase of BTC Garden AM-V2's instead.
2 of which are under going testing as I type this and, so far, we are impressed.

BITMAIN's illegal refusal to release current driver code for their S3 product line places the viability of mining with S3's in jeopardy.
BITMAIN's current "version" of the S3 code "has more bugs than a bait store".
This is exemplified by the activity in this thread.
The S3's are not the profitable "plug-n-play" S1 miners we came to so dearly love.

Additionally, we support the tireless, largely uncompensated, professional work done by CK and Kano.
We intend on voicing our discontent with BUTMAIN's pre-order business model (and yes we got taken by BFL), illegal refusal to release code as mandated by the GPL License, and buggy S/W by exercising our purchasing dollars/BTC elsewhere.

Wake up BITMAIN "you're not the only game in town".

PlanetCrypto
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C

With a lot of polling from a big customer they eventually released the S2 driver.

The S3 driver we've had no luck getting out of them.


Well, if a big customer can get them to release the code - I'm pretty sure that the community here can manage it. By my reckoning, if only 50% of cgminer users kicked up a fuss, they'd be completely swamped - same goes for S3 users.

Come on everyone - let's get it done!!!  Grin
full member
Activity: 177
Merit: 100
Is this the source for what Bitmain is using to roll the cgminer provided on the S3 Huh

https://github.com/bitmaintech/cgminer

8 )
Last commit to the code there:
LingchaoXu authored on 31 Dec 2013

If the S3 upgrade re-uses the controller from the S1, it does from the looks of it, would folding the customizations from their github repository into yours work?

8 )
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'




Questions if you don't mind:

1.  What is your wattage at the wall for 231.25M (please include other relevant data such as ambient room temp and PSU efficiency).
2.  What are the rest of the parameters (i.e. 'freq_value' and 'timeout') for 231.25M?
3.  How does one come up with the appropriate 'freq_value' and 'timeout' for a particular frequency?  Is there a certain formula/equation involved or is it pretty much a trial and error method?

Pardon my ignorance in this matter.




sure here is a full config file

with bonus extras

bold type are ones I found and tested

timeout is found by using the close timeout on the factory set ones.

 an example of a 'timeout' for 256.25 was done at 15   I found it to work  I tried it because factory freq 250 uses freq 16


root@antMiner:~# vi /etc/config/asic-freq

i...package 'cgminer'

config 'asic-freq' 'default'
        

      #option  'freq_value'   '1406'     #Freq at 256.25M = 512 gh uses  410 watts
       #option  'chip_freq'     '256.25'
       #option  'timeout'        '15'


        #option 'freq_value'    '0982'  # Freq at 250M = 500gh uses 400 watts
        #option 'chip_freq'     '250'
        #option 'timeout'       '16'

       #option  'freq_value'    '1306' # Freq at 243.75M = 490gh uses 390watts
        #option  'chip_freq'     '243.75'
        #option  'timeout'       '16'


        option 'freq_value'    '1286'  # Freq at 237.5M = 480gh uses 380 watts
        option 'chip_freq'     '237.5'
        option 'timeout'       '17'

        #option  'freq_value'    '1206'   # Freq at 231.25M = 465gh uses 375 watts
        #option  'chip_freq'     '231.25'
        #option   'timeout'       '17'




        #option 'freq_value'    '0882'  #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'    '1006'  #206.25M
        #option 'chip_freq'     '206.25'
        #option 'timeout'       '19'

        #option 'freq_value'    '0782'  #200M
        #option 'chip_freq'     '200'
        #option 'timeout'       '20'

        #option 'freq_value'    '1f07'  #196M
        #option 'chip_freq'     '196'
        #option 'timeout'       '20'

        #option 'freq_value'    '0f03'  #193M
        #option 'chip_freq'     '193'
        #option 'timeout'       '20'

        #option 'freq_value'    '0d83'  #175M
        #option 'chip_freq'     '175'
        #option 'timeout'       '23'

        #option 'freq_value'    '0b83'  #150M
        #option 'chip_freq'     '150'
        #option 'timeout'       '27'

        #option 'freq_value'    '0983'  #125M
        #option 'chip_freq'     '125'
        #option 'timeout'       '33'

        #option 'freq_value'    '0783'  #100M
        #option 'chip_freq'     '100'
        #option 'timeout'       '40'


legendary
Activity: 910
Merit: 1000
The settings were provided by bitmain in the .conf file.
legendary
Activity: 1081
Merit: 1001




Questions if you don't mind:

1.  What is your wattage at the wall for 231.25M (please include other relevant data such as ambient room temp and PSU efficiency).
2.  What are the rest of the parameters (i.e. 'freq_value' and 'timeout') for 231.25M?
3.  How does one come up with the appropriate 'freq_value' and 'timeout' for a particular frequency?  Is there a certain formula/equation involved or is it pretty much a trial and error method?

Pardon my ignorance in this matter.

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Is this the source for what Bitmain is using to roll the cgminer provided on the S3 Huh

https://github.com/bitmaintech/cgminer

8 )
Last commit to the code there:
LingchaoXu authored on 31 Dec 2013
full member
Activity: 177
Merit: 100
Is this the source for what Bitmain is using to roll the cgminer provided on the S3 Huh

https://github.com/bitmaintech/cgminer

8 )
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Does anyone know how Kano was able to write his own version for the S1? Does he have supporting documents? Or did he just come up with a work around?
They had released the code for the driver for the S1.

With a lot of polling from a big customer they eventually released the S2 driver.

The S3 driver we've had no luck getting out of them.
sr. member
Activity: 392
Merit: 250
HEY BitMain,...

WHAT"S going on with the ..."SHIPPING FROM STOCK...WITHIN 48 HOURS..." - Business model... Huh

Reference...: ... https://bitmaintech.com/about.htm

Another BFL...KnC...you name it ...in making...  IMHO...Wink

ZiG  

EDIT...: ...and PLEASE, RELEASE SOURCE CODE of your software under Open Source License as you agreed upon using it...and now spreading around the world ILLEGALLY...OK... Grin

LAST...: ...DO YOU THINK that BTC community ...we...will TOLERATE this forever... Huh
for the love of god please don't type like that

For the love of God? Who is God to you anyway?
sr. member
Activity: 392
Merit: 250
HEY BitMain,...

WHAT"S going on with the ..."SHIPPING FROM STOCK...WITHIN 48 HOURS..." - Business model... Huh

Reference...: ... https://bitmaintech.com/about.htm

Another BFL...KnC...you name it ...in making...  IMHO...Wink

ZiG  

EDIT...: ...and PLEASE, RELEASE SOURCE CODE of your software under Open Source License as you agreed upon using it...and now spreading around the world ILLEGALLY...OK... Grin

LAST...: ...DO YOU THINK that BTC community ...we...will TOLERATE this forever... Huh

30days  from the shipping date is very long for b8, bitmain please improve the shipping time.  Roll Eyes
member
Activity: 92
Merit: 10
Anyone knows how to determine the batch number of the ANTMINER S3 ?

There is something like a serial number in the product ?
ZiG
sr. member
Activity: 406
Merit: 250
HEY BitMain,...

WHAT"S going on with the ..."SHIPPING FROM STOCK...WITHIN 48 HOURS..." - Business model... Huh

Reference...: ... https://bitmaintech.com/about.htm

Another BFL...KnC...you name it ...in making...  IMHO...Wink

ZiG  

EDIT...: ...and PLEASE, RELEASE SOURCE CODE of your software under Open Source License as you agreed upon using it...and now spreading around the world ILLEGALLY...OK... Grin

LAST...: ...DO YOU THINK that BTC community ...we...will TOLERATE this forever... Huh
for the love of god please don't type like that

What... Huh ...do you mean... Huh

Thanks,

ZiG
newbie
Activity: 9
Merit: 0
HEY BitMain,...

WHAT"S going on with the ..."SHIPPING FROM STOCK...WITHIN 48 HOURS..." - Business model... Huh

Reference...: ... https://bitmaintech.com/about.htm

Another BFL...KnC...you name it ...in making...  IMHO...Wink

ZiG  

EDIT...: ...and PLEASE, RELEASE SOURCE CODE of your software under Open Source License as you agreed upon using it...and now spreading around the world ILLEGALLY...OK... Grin

LAST...: ...DO YOU THINK that BTC community ...we...will TOLERATE this forever... Huh
for the love of god please don't type like that
ZiG
sr. member
Activity: 406
Merit: 250
HEY BitMain,...

WHAT"S going on with the ..."SHIPPING FROM STOCK...WITHIN 48 HOURS..." - Business model... Huh

Reference...: ... https://bitmaintech.com/about.htm

Another BFL...KnC...you name it ...in making...  IMHO...Wink

ZiG  

EDIT...: ...and PLEASE, RELEASE SOURCE CODE of your software under Open Source License as you agreed upon using it...and now spreading around the world ILLEGALLY...OK... Grin

LAST...: ...DO YOU THINK that BTC community ...we...will TOLERATE this forever... Huh
sr. member
Activity: 241
Merit: 250
Good stuff Lohoris,

I hope the whole Bitcoin community here will all get behind the cgminer developers - they deserve our support, as do the many customers who are running Bitmain units with known security issues & unknown software inside them.....

Nice to see more posts about this  Smiley

Agreed.

BITMAIN: If you expect us to continue using and buying your products, you must follow the requirements of the license under which you got the source to cgminer and made modifications to it, then including it in your products. Not doing so only feeds the suspicion of something all not being as it should. You already have numerous people stating here on this discussion board that they will not buy any more of your products until the source code is released, as is required, so the developers can verify correctness and see what's necessary for security updates that have already been identified and that are absolutely necessary for safe continued operation. Not doing so adds to those, myself included, that view your products as suspect at this point, and are holding off purchasing more due to your failure to release the source as required.

Remember BITMAIN that there are other manufacturers that your customers can purchase from, and will if you demonstrate that you are not a trusted member of the mining community.

I'm adding myself to the list of those that will not purchase any more of your products until the source code is released, as required, for the developers review and inclusion in the source code tree.
legendary
Activity: 966
Merit: 1003
Good stuff Lohoris,

I hope the whole Bitcoin community here will all get behind the cgminer developers - they deserve our support, as do the many customers who are running Bitmain units with known security issues & unknown software inside them.....

Nice to see more posts about this  Smiley
Does anyone know how Kano was able to write his own version for the S1? Does he have supporting documents? Or did he just come up with a work around?
   Since Bitmain does not respond to 99.99% of the forum requests for help, comments, or anything else, its obvious they treat this entire forum as nothing more than an advertising billboard! They do not engage with this community ever!
Jump to: