Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 408. (Read 5806004 times)

legendary
Activity: 1379
Merit: 1003
nec sine labore
Hi,

I have a problem with cgminer > 2.9.7 when using it with my CM1 boards (icarus emulation).

I start it as

Code:
cgminer -S /dev/1st-board -S /dev/2nd-board -S /dev/and_so_on --fix-protocol --failover-only --icarus-timing long -o http://rpc.hhtt.1209k.com:8337 -O 1Xyz..._128 

so I'm running with difficulty 128.

With 2.10.4 and now 2.10.5 board hashing speeds are insane, I reach Pethashes and I get tons, I mean tons, of HW: errors

I stop it, restart 2.9.7 with the same parameters (I'm using a script, btw) and all works as it should.

Are there problems with --icarus-timing long or icarus boards ?

spiccioli

Do you only have CM1 boards or do you have other devices also?
Also, rather than 'tons' give a screen shot or an API output.
API stats/summary/devs output would be helpful (stats shows the icarus-timing stats)
I haven't used icarus-timing for a while, so I've no idea if I've caused any problems with it recently
I'll check it after I've has a chance to look at you screen dump and the API stats/summary/devs

Aside:
The Icarus driver is the last of the serial-USB drivers, that I'll get around to updating some time in the ... future ... to use direct USB
But I'm now a bit short on time due to going to visit BFL on the 17th for a week so it may be a while before I update the Icarus code.


Hi kano,

there are two BFL but they're managed by a different instance of cgminer.

anyway, here it is a screenshot after half a minute since restart with 2.10.5

Code:
 cgminer version 2.10.5 - Started: [2013-02-08 12:36:49]
--------------------------------------------------------------------------------
 (5s):1.120E (avg):801.4Ph/s | Q:482  A:0  R:0  HW:99  E:0%  U:0.0/m
 ST: 0  SS: 0  DW: 1  NB: 1  LW: 2  GF: 0  RF: 0  WU: 96.9
 Connected to rpc.hhtt.1209k.com diff 128 with LP as user 1..._128
 Block: 00d9ec7e48042357...  Diff:3.27M  Started: [12:36:49]  Best share: 87
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 ICA  0:                | 268.3M/172.2Mh/s | A:0 R:0 HW:7 U:0.00/m
 ICA  1:                | 299.8M/161.4Mh/s | A:0 R:0 HW:7 U:0.00/m
 ICA  2:                | 236.2M/210.2Mh/s | A:0 R:0 HW:1 U:0.00/m
 ICA  3:                | 251.4M/237.0Mh/s | A:0 R:0 HW:2 U:0.00/m
 ICA  4:                | 381.7M/253.0Mh/s | A:0 R:0 HW:1 U:0.00/m
 ICA  5:                | 996.4P/400.7Ph/s | A:0 R:0 HW:6 U:0.00/m
 ICA  6:                | 159.7M/155.6Mh/s | A:0 R:0 HW:8 U:0.00/m
 ICA  7:                | 250.0M/232.5Mh/s | A:0 R:0 HW:9 U:0.00/m
 ICA  8:                | 378.7M/321.8Mh/s | A:0 R:0 HW:3 U:0.00/m
 ICA  9:                | 195.2P/133.6Ph/s | A:0 R:0 HW:7 U:0.00/m
 ICA 10:                | 260.4M/156.2Mh/s | A:0 R:0 HW:7 U:0.00/m
 ICA 11:                | 711.7M/439.0Mh/s | A:0 R:0 HW:3 U:0.00/m
 ICA 12:                | 284.5M/182.0Mh/s | A:0 R:0 HW:6 U:0.00/m
 ICA 13:                | 1.684E/534.3Ph/s | A:0 R:0 HW:6 U:0.00/m
 ICA 14:                | 278.5M/241.1Mh/s | A:0 R:0 HW:1 U:0.00/m
 ICA 15:                | 273.2M/174.7Mh/s | A:0 R:0 HW:9 U:0.00/m
 ICA 16:                | 330.7M/253.1Mh/s | A:0 R:0 HW:3 U:0.00/m
 ICA 17:                | 890.1M/457.4Mh/s | A:0 R:0 HW:3 U:0.00/m
 ICA 18:                | 150.4M/170.3Mh/s | A:0 R:0 HW:6 U:0.00/m
 ICA 19:                | 554.0M/319.4Mh/s | A:0 R:0 HW:5 U:0.00/m
--------------------------------------------------------------------------------

 [2013-02-08 12:38:54] ICA11: invalid nonce - HW error
 [2013-02-08 12:38:55] ICA1: invalid nonce - HW error
 [2013-02-08 12:38:56] ICA15: invalid nonce - HW error
 [2013-02-08 12:38:57] Icarus 2 Re-estimate: Hs=7.223040e-10 W=6.352486e-01 read_count=36 fullnonce=3.738s
 [2013-02-08 12:38:58] ICA7: invalid nonce - HW error
 [2013-02-08 12:39:01] ICA19: invalid nonce - HW error
 [2013-02-08 12:39:02] ICA3: invalid nonce - HW error
 [2013-02-08 12:39:02] Icarus 3 Re-estimate: Hs=-6.210501e-10 W=2.930369e+00 read_count=1 fullnonce=0.263s
 [2013-02-08 12:39:02] ICA12: invalid nonce - HW error
 [2013-02-08 12:39:04] ICA13: invalid nonce - HW error
 [2013-02-08 12:39:04] ICA7: invalid nonce - HW error
 [2013-02-08 12:39:05] ICA16: invalid nonce - HW error
 [2013-02-08 12:39:06] ICA10: invalid nonce - HW error
 [2013-02-08 12:39:07] ICA15: invalid nonce - HW error
 [2013-02-08 12:39:10] ICA10: invalid nonce - HW error
 [2013-02-08 12:39:11] ICA8: invalid nonce - HW error


See ICA 5/9/13 for example.

Thanks.

spiccioli
legendary
Activity: 1182
Merit: 1000
Never seen anything like it, and I have no idea how it could happen?

Here's the parsing code:

Code:
 job_id = json_array_string(val, 0);
 prev_hash = json_array_string(val, 1);
 coinbase1 = json_array_string(val, 2);
 coinbase2 = json_array_string(val, 3);
 bbversion = json_array_string(val, 5);
 nbit = json_array_string(val, 6);
 ntime = json_array_string(val, 7);
 clean = json_is_true(json_array_get(val, 8));

and here's the submit generation code:
Code:
  work->ntime = strdup(pool->swork.ntime);

  sprintf(s, "{\"params\": [\"%s\", \"%s\", \"%s\", \"%s\", \"%s\"], \"id\": %d, \"method\": \"mining.submit\"}",
   pool->rpc_user, work->job_id, work->nonce2, work->ntime, noncehex, sshare->id);

Pretty straight forward so your guess is as good as mine? Unless there's memory corruption going on in the miner because of scrypt's weird and wonderful use of memory, but you're describing a simple swapping which is not like memory corruption. Could you track the message the pool sent when the miner returns something odd to make sure it was sent out ok, because this is the first time this sort of bug has been reported and other scrypt pools have been supporting stratum for a while?


It is not only swapping values.  jobid, Extranonce2, ntime can be corrupted in many ways.( non hex characters, empty, even " chars ).
I didn't observe any swaps including nonce. This filed seems unaffected.



New version 2.10.5 improves things a little bit, but there is still a lot of binary mess in submitted works.
However there are miners who have almost 0% rejected shares and are using cgminer 2.10.4 or 2.10.5
Maybe problem is caused by too high cgminer's settings ?
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Ok I've put 2 versions in my cgminer-binaries github

2.10.5a 2.10.5 recompiled on 64 bit xubuntu 11.04 (as usual)
and
2.10.5c 2.10.5 recompiled on 64 bit xubuntu 11.04 + HotPlug as at 530e3b01
(this also includes all the new code I've written since 2.10.4 - most of it isn't in 2.10.5)


2.10.5a
An Xubuntu 11.04 x86_64 executable is in my github called cgminer-2.10.5a
https://github.com/kanoi/cgminer-binaries
(it also works on Fedora 16 and 17)

To get the binary simply:
wget https://github.com/kanoi/cgminer-binaries/raw/master/cgminer-2.10.5a
chmod +x cgminer-2.10.5a
md5sum cgminer-2.10.5a

15f89acdd0e7982faefbeecd26715ea8  cgminer-2.10.4a

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
First get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'

I ran it for a few minutes just to be sure I didn't mess up the compile Smiley

The same configure options as cvolivas' binary version
In case anyone was wondering:
CFLAGS="-O2 -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt
make clean
make



2.10.5c

Anyone interested in testing it (or my current git https://github.com/kanoi/cgminer/tree/hotplug if you wish to compile it yourself) please do.
I do not expect problems with it - but I'm pretty much the only one I'm certain who has tested it all - though others have tested a lot of it.

I've run it on BFL, Icarus, MMQ and GPU.
I've also compiled and run it now on rpi 2012-12-16-wheezy-raspbian and testing to see how reliable/unreliable USB is with that version of linux.
I've had a hotplug error once so far on rpi.

See back here for all the pre-hotplug changes:
https://bitcointalksearch.org/topic/m.1480806

My git contains the updated README files and the updated miner.php
https://github.com/kanoi/cgminer/tree/hotplug

Important re-paste from before:
Now some important information about the BFL USB driver.
On linux, if you wish to switch back to the 2.10.5a, 2.10.4a or earlier version, you'll need to unplug and re-plug in your FPGAs or reboot your rig.
On windows (as described in FPGA-README) you'll need to update your windows USB driver to use the new cgminer

To get the binary simply:
wget https://github.com/kanoi/cgminer-binaries/raw/master/cgminer-2.10.5c
chmod +x cgminer-2.10.5c
md5sum cgminer-2.10.5c

584398277df9d2add3bbf3684f7168e9 cgminer-2.10.5c

Almost the same configure options as cvolivas uses
In case anyone was wondering:
CFLAGS="-g -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt
make clean
make

The -g (instead of -O2) means it's a debug build so if anyone finds a problem and has cores enabled, it will dump a much more useful debug core.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Kano,

Will you have time to weave your magic with this latest release for use on 11.04 before you leave?  Wink

BFL eh? Sounds interesting....
Oh I didn't make an 11.04 2.10.5a ... ok will do soon.

Nice one kano, cheers.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Kano,

Will you have time to weave your magic with this latest release for use on 11.04 before you leave?  Wink

BFL eh? Sounds interesting....
Oh I didn't make an 11.04 2.10.5a ... ok will do soon.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Kano,

Will you have time to weave your magic with this latest release for use on 11.04 before you leave?  Wink

BFL eh? Sounds interesting....
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Hi,

I have a problem with cgminer > 2.9.7 when using it with my CM1 boards (icarus emulation).

I start it as

Code:
cgminer -S /dev/1st-board -S /dev/2nd-board -S /dev/and_so_on --fix-protocol --failover-only --icarus-timing long -o http://rpc.hhtt.1209k.com:8337 -O 1Xyz..._128 

so I'm running with difficulty 128.

With 2.10.4 and now 2.10.5 board hashing speeds are insane, I reach Pethashes and I get tons, I mean tons, of HW: errors

I stop it, restart 2.9.7 with the same parameters (I'm using a script, btw) and all works as it should.

Are there problems with --icarus-timing long or icarus boards ?

spiccioli

Do you only have CM1 boards or do you have other devices also?
Also, rather than 'tons' give a screen shot or an API output.
API stats/summary/devs output would be helpful (stats shows the icarus-timing stats)
I haven't used icarus-timing for a while, so I've no idea if I've caused any problems with it recently
I'll check it after I've has a chance to look at you screen dump and the API stats/summary/devs

Aside:
The Icarus driver is the last of the serial-USB drivers, that I'll get around to updating some time in the ... future ... to use direct USB
But I'm now a bit short on time due to going to visit BFL on the 17th for a week so it may be a while before I update the Icarus code.
legendary
Activity: 1379
Merit: 1003
nec sine labore
Hi,

I have a problem with cgminer > 2.9.7 when using it with my CM1 boards (icarus emulation).

I start it as

Code:
cgminer -S /dev/1st-board -S /dev/2nd-board -S /dev/and_so_on --fix-protocol --failover-only --icarus-timing long -o http://rpc.hhtt.1209k.com:8337 -O 1Xyz..._128 

so I'm running with difficulty 128.

With 2.10.4 and now 2.10.5 board hashing speeds are insane, I reach Pethashes and I get tons, I mean tons, of HW: errors

I stop it, restart 2.9.7 with the same parameters (I'm using a script, btw) and all works as it should.

Are there problems with --icarus-timing long or icarus boards ?

spiccioli
hero member
Activity: 574
Merit: 500
I have a new powercolor 7970 (my first 7970)

I cam only get ~ 450 K/hash stable with this card

--scrypt --thread-concumreancy 8000 i 16 g 4 -w 256

Is this normal for this card ??

Do i need mega thread concurency for ltc ... ??



hero member
Activity: 675
Merit: 514
For some reason I can't use the --debug option:
Code:
cgminer.exe -u name -p password -o http://localhost:8334 -I 3 --debug
After this
Code:
[2013-02-07 08:55:27] Probing for an alive pool
[2013-02-07 08:55:27] Popping work to stage thread
it crashes.
Without the debug option everything looks ok.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New release: 2.10.5, 7th February 2013

Maintenance release improving on the already good 2.10.4
Linux binaries are now made against ubuntu 12.10 which also work on ubuntu 12.04
Windows binaries are built from a new cross compile setup of mine so they include a new set of DLLs to suit in the archive.


Human readable changelog

Fixed the memory leak, the size of which was proportional to stratum share submissions.
Sped up work generation on stratum even more.
Fixed (one of?) the corrupt stratum share submission bug (found by Kanoi).
Fixed a potential overflow that pools could theoretically use to crash your miner or worse (found by luke-Jr).


Full changelog

- Fix logic fail on partial writes with stratum send that was leading to corrupt
message submissions.
- Do not consider every call to stratum_resumed a pool recovery unless it was
actually idle.
- Do not enable the pool disable on reject feature unless explicitly enabled
with --disable-rejecting.
- Stratum disconnect shares - count total against stale
- Use sanity checking to prevent a possible overflow with invalid data being
given by the pool for difficulty as reported by luke-Jr.
- Check for calloc failure for completeness in gen_stratum_work.
- Cache the coinbase length to speed up stratum work generation.
- Cache the header length when generating stratum work to avoid calculating it
on every work generation, and to only need one alloc+sprintf, speeding up work
generation.
- Use heap ram for coinbase in gen_stratum_work, zeroing it before use.
- Provide a wrapper for aligning lengths of size_t to 4 byte boundaries.
- Fix memory leak on stratum share submission.
- Zero the best share string memory when zeroing stats.
legendary
Activity: 1386
Merit: 1097
How does one force GBT usage in 2.10.4?

Trying to poke the ASIC miner into GBT'ing from bitcoind, rather than getwork'ing.


I did not add support for GBT from bitcoind, sorry. It's a different protocol to GBT from pools.

It is possible to use stratum server to connect cgminer to local bitcoind.

Cgminer -> stratum server -> bitcoind will work.

Stratum server in my github's stratum-mining repository is quite lightweight, it even doesnt need any database...
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
How does one force GBT usage in 2.10.4?

Trying to poke the ASIC miner into GBT'ing from bitcoind, rather than getwork'ing.


I did not add support for GBT from bitcoind, sorry. It's a different protocol to GBT from pools.
legendary
Activity: 1596
Merit: 1100
How does one force GBT usage in 2.10.4?

Trying to poke the ASIC miner into GBT'ing from bitcoind, rather than getwork'ing.

legendary
Activity: 1610
Merit: 1000
Kon (Kano),
Memleak is gone! I was mining with stratum and was hitting bug badly when submitting work


Thank you
legendary
Activity: 1386
Merit: 1097
I reported submitting binary mess in json payload days ago. I see that more and more often in my pool logs, probably as people are updating to the newest cgminer.
legendary
Activity: 1750
Merit: 1007
I've noticed the same thing as cointron from the first moment i implemented stratum support.

I've reported this a few times on BTC Guild.  Miners submitting blank/random byte data in ntime/extranonce occasionally.  This was a much older cgminer version that had the problem though, and I think that user stopped submitting bad data after upgrading.
sr. member
Activity: 288
Merit: 250
I've noticed the same thing as cointron from the first moment i implemented stratum support.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Hello guys, looking for a little advice. I'm running cgminer with Xubuntu Natty on my two rigs and am very happy with the stability and performance. My main PC, that I use daily, is Windoze 7 64bit - and I'm using my spare graphics cards on this to mine when it's switched on. The mobo has integrated Intel HD graphics which I use as the primary connection to my monitor via dvi and secondary to my HD TV via HDMI, leaving the graphics cards free for mining - or so I thought. When mining I still get the "lag" that is associated with mining on my Intel Graphics display, even though it is not being used for mining. Am I missing some kind of setting that will completely separate my integrated graphics from mining leaving it free for general usage without the "lag" issue? I have checked the readme, googled etc but can't seem to find a solution. My PC mobo & CPU support virtualization, so I did try installing Xubuntu on a virtual machine (Oracle VirtualBox) on my PC with the hope of mining that way, but setting up VGA passthrough is beyond my ability/knowledge of linux, as I've only just started using it and have been unable to find a tutorial that I fully understand or feel comfortable using (Linux noob  Grin).

Any help/suggestions or advice would be gratefully accepted.....

Peace.
Jump to: