OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[BoogieMan82]

Thanks for the information, this is what it looks like now (I still wish the values were doubled though)!

http://www.getfreebitcoins.us/wp-content/uploads/2014/03/Bitminer-U2b.jpg

Has anyone tried to bump these u2 miners up.  2.0GH is the start speed so I'd hope we'd get close to 2.5 or 2.6GH

Size being a secondary issue it took a long while for cgminer to see it . I have in total 8 of a combination of u1's and 2's but I only showed 7 till I restarted. I'm still having troubles where the u2 device's lights wont go on or the way I expect them. The one I thought I would need to return is working properly and the one I didn'ts lights don't come on when I shut down cgminer.

These u2's are picky buggers  but it may just be they are different enough to cause me migranes

AMU of 258.3 (2.1GH) is the best I can get out of mine (unless I decide to modify the resistors) or else I get a bunch of HW errors.

[1714285480]

1714285480

[1714285480]

1714285480

[1714285480]

1714285480

[zamot]

Here's another new AntS1 binary.

An endian issue was found in the solo code for the ant (no issue for desktop computers), so this update includes the fix for that.
I've removed both old AntS1 binaries

This uses the same patch as before for the luci display.
My source for this version is here:
https://github.com/kanoi/cgminer/tree/ants1-4.2.0-00567a4

The binary and README are in my cgminer-binaries git here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1  <-- Follow this link to get the new binary

Read the README on the screen there for how to replace the /usr/bin/cgminer binary in your AntS1 with the new one.

This binary includes all cgminer changes up to 4.2.0 and forward after that up to:
https://github.com/ckolivas/cgminer/commit/cec48cee5f1759e5996de5339537fab4aeff416c

The previous report of having trouble with running the binary turned out to be caused by incorrectly specifying cgminer options.

Kano, there is an minor "optical bug" in miner status displaying LSTime. It does not display actual difference since last time the pool was contacted. Instead displays times remaining since some distant past - i think since 01-01-1970

[-ck]

PS:

Guy's
What about
   cg_wlock(&control_lock);
   .....local_work++;
   .....total_work++;
   cg_wunlock(&control_lock);
I think there is a need to lock them everywhere or ?

Thanks

Mostly harmless, but probably wouldn't hurt to protect them with the write lock for when mining at multiple different types of pools at once (eg GBT + stratum), yes, thanks.

Super,
If you can add local_work++ inside total_work_inc will be great 

That's a purely cosmetic number and adding locking for it does not protect anything of any value.

[kano]

...
Kano, there is an minor "optical bug" in miner status displaying LSTime. It does not display actual difference since last time the pool was contacted. Instead displays times remaining since some distant past - i think since 01-01-1970

I've mentioned this before.

The problem is that bitmain changed the content of the API field.
So from a cgminer point of view, there is no fix.
What they changed in their fork was: instead of providing a unix time stamp like 1395777236, which cgminer did, still does, and forever will, they now send out a string like "10:05:23" meaning a bit over 10 minutes in the past.

Of course I will not change the API to break all code that uses LSTime.
The only fix that doesn't break cgminer is to revert the antminer code that displays the web page.

Artpego posted an antminer luci fix (revert) about 2 pages back:
https://bitcointalk.org/index.php?topic=28402.msg5852062#msg5852062

[kano]

Well if I disconnect the power and re-connect after 10-15min it runs normally for 5-10min and then the it brakes down. Am clueless

It sounds like a hardware problem - but since it is all custom hardware, it's most likely a bitmain hardware issue for them to fix, since we know the software works under normal conditions for literally 10 of thousands of antminers.

[zamot]

Well if I disconnect the power and re-connect after 10-15min it runs normally for 5-10min and then the it brakes down. Am clueless

Maybe it is an power issue. I had the same issue and after i connected an old CD drive to power supply it is stable. Before that power supply shuts down ( 650 W for one antminer S1), now it has constant load on CD drive and it works.

[loshia]

Con,

I am looking at stale_work() code. I am wandering if work gets stale in solo and gbt also?

if (pool->gbt_workid)
      work->job_id = strdup(pool->gbt_workid);
Shall job_id be checked inside stale_work code. For stratum it is considered as stale if there is no share but for gbt and solo?
Thanks

[ZBC3]

I updated to 4.2.1, but now my one string miners aren't recognized, my bitf burner fury had lots of read errors, and my avalon thumbs by drillbit aren't recognized. It is recognizing the bitfury thumbs and 8 board by drillbit, and my bitburner fury (4 stack) us hashing at around 30.

Any suggestions?

I think it's an avalon read buff error or something like that for the bitburner fury

[techman05]

Kano just wondering but as I'm getting one of those s1's soon I have to ask if they make it easy to update or are there special thing I need to do to make updates to it.

Hopefully all the questions I'm asking are in your read me but I ask just in case.

Thanks

[kano]

Kano just wondering but as I'm getting one of those s1's soon I have to ask if they make it easy to update or are there special thing I need to do to make updates to it.

Hopefully all the questions I'm asking are in your read me but I ask just in case.

Thanks

To replace cgminer to a new version:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

There are other methods to do larger updates (ipk files) and of course a full flash of the OS, but from a mining point of view, just putting in the new cgminer as described above is all that is needed.

[kano]

Well if I disconnect the power and re-connect after 10-15min it runs normally for 5-10min and then the it brakes down. Am clueless

Maybe it is an power issue. I had the same issue and after i connected an old CD drive to power supply it is stable. Before that power supply shuts down ( 650 W for one antminer S1), now it has constant load on CD drive and it works.

I've had my smaller ant (90GH/s) stop mining a few times and I checked dmesg today and noticed the -71 error
rebooting it directly (ssh in and 'reboot') has cleared it each time

[ZBC3]

Never mind, it was definitely user error. I've reinstalled and am working perfectly again.

Thank you

[daddyfatsax]

I have 2 bitfury rigs, v2.2 and v1.2, that I am trying to get cgminer running on. I compiled with --enable-bab and my v2.2 rig works fine, my v1.2 rig is just showing HW errors. From the ASICreadme I can see the options are --bab-options max:def:min. I want my v1.2 rig to start with --bab-options max:55def:54, is that the correct way to start it? Just want to make sure I am doing this correctly, chainminer is a pain in the ass and my stratum proxy keeps dying. Even if I restart the stratum proxy every hour it eventually just craps out.

Thanks.

[Truman]

Is there shortly a support for the gridseed miners?

[fhh]

Is there shortly a support for the gridseed miners?

surly not - they are bad scrypt boys
and the sha256 part? nobody needs it!

[Littleshop]

Well if I disconnect the power and re-connect after 10-15min it runs normally for 5-10min and then the it brakes down. Am clueless

It sounds like a hardware problem - but since it is all custom hardware, it's most likely a bitmain hardware issue for them to fix, since we know the software works under normal conditions for literally 10 of thousands of antminers.

Try downclocking it and see if it fixes it.  If you do not have to downclock it too far it might be worth keeping now vs sending back. 

[kano]

I have 2 bitfury rigs, v2.2 and v1.2, that I am trying to get cgminer running on. I compiled with --enable-bab and my v2.2 rig works fine, my v1.2 rig is just showing HW errors. From the ASICreadme I can see the options are --bab-options max:def:min. I want my v1.2 rig to start with --bab-options max:55def:54, is that the correct way to start it? Just want to make sure I am doing this correctly, chainminer is a pain in the ass and my stratum proxy keeps dying. Even if I restart the stratum proxy every hour it eventually just craps out.

Thanks.

At the moment, the code has trouble with more than 2 boards per SPI channel.
I think I know what needs to be changed, but haven't gone near it for a few weeks.
My BA setup with 7 boards gets 270GH/s no trouble since I use a BA V2 controller that has 4 SPI connectors and I put 2 boards on each (1 on one)

The --bab-options is only the numbers so for setting max,def only: --bab-options "55:54"
You can leave any blank and it will use the default for the blank ones and you only need to specify up to the ones you wish to change,

[-ck]

I'm pretty happy with my testing so far.  But the memory utilization is still climbing, 408MB so far.

Found this memory leak and it's now fixed in git, but there won't be a new version out just yet as I fix other issues first.

[daddyfatsax]

I have 2 bitfury rigs, v2.2 and v1.2, that I am trying to get cgminer running on. I compiled with --enable-bab and my v2.2 rig works fine, my v1.2 rig is just showing HW errors. From the ASICreadme I can see the options are --bab-options max:def:min. I want my v1.2 rig to start with --bab-options max:55def:54, is that the correct way to start it? Just want to make sure I am doing this correctly, chainminer is a pain in the ass and my stratum proxy keeps dying. Even if I restart the stratum proxy every hour it eventually just craps out.

Thanks.

At the moment, the code has trouble with more than 2 boards per SPI channel.
I think I know what needs to be changed, but haven't gone near it for a few weeks.
My BA setup with 7 boards gets 270GH/s no trouble since I use a BA V2 controller that has 4 SPI connectors and I put 2 boards on each (1 on one)

The --bab-options is only the numbers so for setting max,def only: --bab-options "55:54"
You can leave any blank and it will use the default for the blank ones and you only need to specify up to the ones you wish to change,

I will give that a try when I get home. Thanks for the help!

[os2sam]

I'm pretty happy with my testing so far.  But the memory utilization is still climbing, 408MB so far.

Found this memory leak and it's now fixed in git, but there won't be a new version out just yet as I fix other issues first.

Thanks for the update.  I look forward to testing the new version when it's ready.