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

[kano]

Hi Kano,
your FW for S2 works great on Ozco.in and Ghash.io pools but its nearly impossible to use Eligius pool.
Anyway thanks a lot.

I'm banned from posting in Eligius since wizkid didn't like people knowing the crap their pool does and deleted my posts.
So ... Eligius is low priority.

I still wonder why Eligius keeps such a high balance ...
https://blockchain.info/address/18d3HV2bm94UyY4a9DrPfoZ17sXuiDQq2B >400BTC
https://blockchain.info/address/1ChANGeATMH8dFnj39wGTjfjudUtLspzXr >200BTC
https://blockchain.info/address/14qgRxmyWwRweGY4mfjB5FRxr3Ak8Weu1w 1000 BTC
https://blockchain.info/address/1BRoZJLeLaR9T4PP2m1FJ5isqgQmhzMKBn 99.999 BTC

https://blockchain.info/address/18g3xd6WiEn6Wc88EK2B3oMnG7Y6KKwehM
That's an interesting payout

This one is interesting how it splits up a large amount into smaller and smaller amounts
https://blockchain.info/address/16qN6Xcm9tKoDTfeLjan5dgCEsDhWTxizK

[dmaxl]

However, yes I tried p2pool early (3am) this morning and indeed everything exploded into a mess of errors both on the S2 and p2pool
Will look into that ...

I'll save you some time because I ran into this same issue, albeit with litecoin but the cause should be the same.

The cause is the sanity checks introduced by commit e1c5050734123973b99d181c45e74b2cbb00272e.
Empty string extranonce1 values now cause an error in util.c near line 2581:

Code:

nonce1 = json_array_string(res_val, 1);
if (!valid_hex(nonce1)) {
    applog(LOG_INFO, "Failed to get valid nonce1 in initiate_stratum");
    free(sessionid);
    goto out;
}

P2pool doesn't implement extranonce1 and sends an empty string, causing initiate_stratum to fail and cgminer to fallback to longpoll, which doesn't work with p2pool. Arguably this is more of a p2pool problem, but a possible workaround would be to restore previous behavior which just checks that nonce1 != NULL.

[-ck]

However, yes I tried p2pool early (3am) this morning and indeed everything exploded into a mess of errors both on the S2 and p2pool
Will look into that ...

I'll save you some time because I ran into this same issue, albeit with litecoin but the cause should be the same.

The cause is the sanity checks introduced by commit e1c5050734123973b99d181c45e74b2cbb00272e.
Empty string extranonce1 values now cause an error in util.c near line 2581:

Code:

nonce1 = json_array_string(res_val, 1);
if (!valid_hex(nonce1)) {
    applog(LOG_INFO, "Failed to get valid nonce1 in initiate_stratum");
    free(sessionid);
    goto out;
}

P2pool doesn't implement extranonce1 and sends an empty string, causing initiate_stratum to fail and cgminer to fallback to longpoll, which doesn't work with p2pool. Arguably this is more of a p2pool problem, but a possible workaround would be to restore previous behavior which just checks that nonce1 != NULL.

Thanks for that, it's more lenient now in git.

[iglasses]

Can someone tell me what the heck I am doing wrong...I am trying to use the enable ants1 command at startup but I'm obviously not formatting it correctly because I keep getting 'unrecognized option'.

I am trying to use it like this...
cgminer --enable-ants1

What am I missing here?

The --enable-ants1 option is for when you build cgminer, not when you run it.

Well don't I feel like a dam fool. 
Thanks though!

ig

[kano]

However, yes I tried p2pool early (3am) this morning and indeed everything exploded into a mess of errors both on the S2 and p2pool
Will look into that ...

I'll save you some time because I ran into this same issue, albeit with litecoin but the cause should be the same.

The cause is the sanity checks introduced by commit e1c5050734123973b99d181c45e74b2cbb00272e.
Empty string extranonce1 values now cause an error in util.c near line 2581:

Code:

nonce1 = json_array_string(res_val, 1);
if (!valid_hex(nonce1)) {
    applog(LOG_INFO, "Failed to get valid nonce1 in initiate_stratum");
    free(sessionid);
    goto out;
}

P2pool doesn't implement extranonce1 and sends an empty string, causing initiate_stratum to fail and cgminer to fallback to longpoll, which doesn't work with p2pool. Arguably this is more of a p2pool problem, but a possible workaround would be to restore previous behavior which just checks that nonce1 != NULL.

Unfortunately, that's not the actual problem.
That's simply an unnecessary warning on the screen that ckolivas has now removed due to your help pointing it out.

I did mean this seriously:

... indeed everything exploded into a mess of errors both on the S2 and p2pool ...

I've not had time to track it down yet ...

[plekhanov]

I tried building 4.3.5 on Centos 6.4 x86_64 (2.6.32-431.17.1.el6.x86_64) with Antminer S1 support.  The build stops in the bitmain driver:

  CC     cgminer-driver-bitmain.o
driver-bitmain.c: In function 'bitmain_read':
driver-bitmain.c:940: error: 'struct bitmain_info' has no member named 'device_fd'
driver-bitmain.c: In function 'bitmain_write':
driver-bitmain.c:971: error: 'struct bitmain_info' has no member named 'device_fd'
driver-bitmain.c: In function 'bitmain_parse_results':
driver-bitmain.c:1316: error: request for member 'min' in something not a structure or union
make[2]: *** [cgminer-driver-bitmain.o] Error 1

[norgan]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

[canford]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

[norgan]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

yeah thanks I know about that one. but I just wondered if the main fork that says it supports s1 could be used to keep it more up to date. (I just like to have the latest lol)

[canford]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

yeah thanks I know about that one. but I just wondered if the main fork that says it supports s1 could be used to keep it more up to date. (I just like to have the latest lol)

Not sure, I think you'd have to build the binary for the S1 yourself.  Kano might update github with an updated version, though I'm not aware of any S1-related improvements.  My AntMiners are all running 4.3.2a from Kano's build.

[Buchi-88]

Good day,

i have an existing problem with my configuration:

8 x Antminer U2 +
8 x BFx2 Bitfury

as soon as I both operate (. / configure - enable-bitfury - enable-icarus) remains Cgminer hang over again, and "watchdog" restarts the Raspberry new!

Once I only BFx2 Bitfury (. / Configure - enable-bitfury) used, runs the Cgminer 24/7.

Code:

0: BXM 0       :                         | 3.810G / 3.751Gh/s WU:52.9/m
 1: BXM 1       :                         | 2.394G / 3.187Gh/s WU:44.6/m
 2: BXM 2       :                         | 3.136G / 3.167Gh/s WU:44.6/m
 3: BXM 3       :                         | 2.990G / 3.006Gh/s WU:42.1/m
 4: BXM 4       :                         | 3.767G / 3.819Gh/s WU:53.7/m
 5: BXM 5       :                         | 3.894G / 3.919Gh/s WU:55.0/m
 6: BXM 6       :                         | 3.952G / 3.932Gh/s WU:55.5/m
 7: BXM 7       :                         | 3.804G / 3.867Gh/s WU:54.4/m
--------------------------------------------------------------------------------
 [2014-06-12 23:19:41] Zero length string passed to valid_hex from in util.c ini
tiate_stratum():2609
 [2014-06-12 23:19:41] Zero length string passed to valid_hex from in util.c ini
tiate_stratum():2609

Exactly the same is in the use of Antminer (. / Configure - enable-icarus)?

The problem is only with the simultaneous use, is it possibly there is a compatibility issue between the two drivers?

I had raised the issue before, but still wanted to thoroughly test!

On the Pi is the newest Kernel installed.

regards

[kano]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

yeah thanks I know about that one. but I just wondered if the main fork that says it supports s1 could be used to keep it more up to date. (I just like to have the latest lol)

I'll not update the S1 until I've sorted out the S2 issues - since I've no idea if those issues will affect the S1 also - and the last S1 release is pretty stable.

[mdude77]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

yeah thanks I know about that one. but I just wondered if the main fork that says it supports s1 could be used to keep it more up to date. (I just like to have the latest lol)

I'll not update the S1 until I've sorted out the S2 issues - since I've no idea if those issues will affect the S1 also - and the last S1 release is pretty stable.

S1 patch works great with p2pool.  So I don't think the issues affect the S1.

M

[norgan]

are we able to update the cgminer on the s1 or is it best to leave with the older build?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

yeah thanks I know about that one. but I just wondered if the main fork that says it supports s1 could be used to keep it more up to date. (I just like to have the latest lol)

I'll not update the S1 until I've sorted out the S2 issues - since I've no idea if those issues will affect the S1 also - and the last S1 release is pretty stable.

S1 patch works great with p2pool.  So I don't think the issues affect the S1.

M

yeah there's nothing wrong with the current s1 build. I am just one of those who love to know I am running the very latest code. haha

[LARTAS]

Hi
My terraminer which is good
One CTA is showing high temperatures
CTA0 Metrics             High   Low          Avg
Core Temp 1 (°C)   91.14   63.74   77.77
Core Temp 2 (°C)   64.54   56            59.57
Ambient Temp (°C)   65.5           56          59.93
Fan Speed (RPM)   4782   4248   4,542
Pump Speed (RPM)   2990   2967   2,979

Who can help me? Before it get worst

[Micky25]

Hi
My terraminer which is good
One CTA is showing high temperatures
CTA0 Metrics             High   Low          Avg
Core Temp 1 (°C)   91.14   63.74   77.77
Core Temp 2 (°C)   64.54   56            59.57
Ambient Temp (°C)   65.5           56          59.93
Fan Speed (RPM)   4782   4248   4,542
Pump Speed (RPM)   2990   2967   2,979

Who can help me? Before it get worst

CoinTerra Support (CoinTerra)
May 13 15:23
The temps are operating in the expected range. It will not have an issue until 120C at which time it will shut itself off.
Regards,
Marshall

Comments: Hi, I have a very high difference on the temperatures of CTA0 and CTA1. Is there something I can do about this?
Thanks and best regards, Micky25
CTA0 Metrics High Low Avg
Core Temp 1 (°C) 108.49 76.79 87.35
Core Temp 2 (°C) 100.19 82.66 87.87
Ambient Temp (°C) 65.25 57.5 60.68
Fan Speed (RPM) 4122 3994 4,038
Pump Speed (RPM) 2991 2954 2,973
CTA1 Metrics High Low Avg
Core Temp 1 (°C) 64.23 55.89 60.13
Core Temp 2 (°C) 58.41 52.3 55.29
Ambient Temp (°C) 49.75 45.25 48.31
Fan Speed (RPM) 4225 4150 4,188
Pump Speed (RPM) 2952 2941 2,947

]

[-ck]

Comments: Hi, I have a very high difference on the temperatures of CTA0 and CTA1. Is there something I can do about this?

Unfortunately not.

[Taugeran]

im trying to get a MrTeal chili up and running on my BBB running some Onestringminer devices. alas when i plugged it in, it was recognized but once it was it started spewing "hex2bin scan failed" errors, as well as a single WARNING: firmware not recognized "mrteal fw version here" using Ver2.

0 hashrate is produced

this is cgminer 4.3.4 on a RevA6, running 5 OSM and [trying] 1 chili.

[detro]

Any idea when support for Rockminer r-box's will be available without having to hack up the code?

[-ck]

Any idea when support for Rockminer r-box's will be available without having to hack up the code?

Kano and I have both received rboxes to incorporate support into cgminer for, however the current code by the manufacturer for them trashes a whole lot of other cgminer driver code making the code not portable so it will take a while longer while we rewrite the driver.

EDIT: Experimental support is now in git.