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

[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.

[Mblackout]

If i have a box running CGMINER as a service is there a way to monitor the stats from the CLI or linux? 

[techman05]

Kano . I tried to follow the instructions to get 4.2 to install on the antminer and it still shows 3.12 after a reboot. It seems to be mining but with the patch its seems its lost something.

Code:

Collected errors:
 * opkg_conf_load: Could not lock /var/lock/opkg.lock: Resource temporarily unavailable.

  this seems to have gone away after another reset btw

did I miss a step and fudge something uo?

[-ck]

New release: 4.2.2, 29th March 2014

Bugfixes and cosmetic updates.


Human readable changelog:

- Fix for memory leaks when mining solo
- Fix for a rare corruption possibility with solo mining.
- Support for a whole lot more USB hubs on windows.
- Added rules for using cointerra on PC in case anyone besides me actually does this.
- Revamped the hashrate meter to be far more reliable internally.
- Added rolling hashrates for 1 min, 5 min and 15 mins to the main display and per device to the API as well.
- Revamped the display since it was getting too wide: It now is back to the narrower size it was a few versions ago and toggles between the different data at regular intervals based on the opt log interval variable. Toggling can be disabled via the Display menu.
- Added serial number to the unique identifier on-screen when it exists instead of an arbitrary device number. This currently only tags hashfast, cointerra and BF1 devices which have serial numbers.
- Support reading configuration files with -c command from web URLs.
- Fixes for building with libcurl disabled.
- Other minor bugfixes and trivial changes.


Full changelog:

- Minor correctness fix for unnecessary free
- Clean up various curl build issues
- allow url based config files
- Frequency only needs 3 digits for cointerra statline
- Use the serial number as unique_id for cta display
- Make it possible to enable/disable the status window from switching via the
display menu
- We should not update the tv hashmeter time unless we're updating the hashrates
- Add cointerra devices to udev rules.
- Use hashfast unique id instead of number since the unique id is displayed
- Remove displayed space
- Left align the displayed unique id
- Use the hashfast opname as its unique identifier
- Display BF1 serial number as its unique identifier
- Display a unique identifier instead of a number if the device has one
- Use an alternating status display to return to a compact width of 80
characters, allowing more information to be displayed.
- No need for looking for khash hashrates in summary any more
- Fix two potential minor mem leaks
- Fix memory leaks in setup and generate work for gbt solo.
- Fix off by one malloc size error
- Fix memory leak in update_gbt_solo
- Put sanity check on decay_time to prevent updates with no time
- Add 3 rolling average hashrates to API output for summary and devs.
- Use the extra status screen real estate better, displaying rolling 1/5/15min
average hashrates as well.
- Revamp the ageing crufty hashmeter code to have proper exponential decaying
values and store rolling 1/5/15min hashrates.
- Increment total_work under control lock.
- Trivial variable reuse
- Add support for other usb3 hubs on windows

[canford]

4.2.2 breaks Cgminer Status Summary display on the Avalon Mini, reverted to 4.2.1.  4.2.2 working on Windows 7 with BE's.

[kano]

4.2.2 breaks Cgminer Status Summary display on the Avalon Mini, reverted to 4.2.1.  4.2.2 working on Windows 7 with BE's.

To state that correctly: the luci code to display the API has been broken since it was first written - both in the Avalon and the Ant (the Ant simply copied the Avalon code and then broke it even more)
It doesn't use the field names to find the data, it numerically indexes into the data.

The API output (since I first wrote it) has always had the same key names to the same data, and that hasn't changed with 4.2.2
4.2.2 has simply added more fields to the summary between "MHS 5s" and "Found Blocks"

When you have a set of "Name"->"Data", it is foolish to not use "Name" to locate "Data"

[kano]

Kano . I tried to follow the instructions to get 4.2 to install on the antminer and it still shows 3.12 after a reboot. It seems to be mining but with the patch its seems its lost something.

Code:

Collected errors:
 * opkg_conf_load: Could not lock /var/lock/opkg.lock: Resource temporarily unavailable.

  this seems to have gone away after another reset btw

did I miss a step and fudge something uo?

https://github.com/kanoi/cgminer-binaries/issues/2