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

[juhakall]

I am also getting that same long poll error when connecting to hashpower.com. With 2.8.7 long polling works there.

[1715092841]

1715092841

[1715092841]

1715092841

[1715092841]

1715092841

[1715092841]

1715092841

[P_Shep]

Working nicely.
Have GW, GBT & Stratum pools all up and running.

Something in the order of:
11,000% efficiency on Eclipse (GBT + Var Diff)
1,800% efficiency on MaxBTC (GW)
550% efficiency on Ozcoin (Stratum)

Get VERY large discards on GBT though, on the order of 1000%
Roughly 30% on Stratum and GW

Kano, did you said you're gonna add data counters to the pools? That'd be very interesting to see.


 

[kano]

Working nicely.
Have GW, GBT & Stratum pools all up and running.

Something in the order of:
11,000% efficiency on Eclipse (GBT + Var Diff)
1,800% efficiency on MaxBTC (GW)
550% efficiency on Ozcoin (Stratum)

Get VERY large discards on GBT though, on the order of 1000%
Roughly 30% on Stratum and GW

Kano, did you said you're gonna add data counters to the pools? That'd be very interesting to see.
 

Yes I'll add data counters to the pools soon ...
I'm working on some MMQ stuff at the moment.

However ........ 11,000% efficiency?
What GH/s are you?
That seems too high ... though that is probably on a high hash rate?

I'm of course referring to the issue of work age and the negative affect on BTC.

[-ck]

Working nicely.
Have GW, GBT & Stratum pools all up and running.

Something in the order of:
11,000% efficiency on Eclipse (GBT + Var Diff)
1,800% efficiency on MaxBTC (GW)
550% efficiency on Ozcoin (Stratum)

Get VERY large discards on GBT though, on the order of 1000%
Roughly 30% on Stratum and GW

Kano, did you said you're gonna add data counters to the pools? That'd be very interesting to see.


 

The switch between regular and GBT pools is still not ideal and the GBT work on switching to it can be stale for a while. There is a fix in git for this.

[P_Shep]

Yes I'll add data counters to the pools soon ...
I'm working on some MMQ stuff at the moment.

However ........ 11,000% efficiency?
What GH/s are you?
That seems too high ... though that is probably on a high hash rate?

I'm of course referring to the issue of work age and the negative affect on BTC.

Yep, that high
It factors in the var diff shares (2.5 ish), so it's 'no of diff 1 equivalent shares'/'get block templates'*100.
Running at a little over 5GH/s.

[P_Shep]

Hmm, had this happen a couple of times now:

Code:

 [2012-11-08 14:59:15] Switching to http://pool.maxbtc.com:8332
 [2012-11-08 15:02:47] LONGPOLL from pool 2 requested work restart
 [2012-11-08 15:06:21] LONGPOLL from pool 2 requested work restart
 [2012-11-08 15:14:16] LONGPOLL from pool 2 detected new block
 [2012-11-08 15:14:35] LONGPOLL from pool 2 requested work restart
 [2012-11-08 15:17:03] LONGPOLL from pool 2 requested work restart
 [2012-11-08 15:17:10] LONGPOLL from pool 2 detected new block
 [2012-11-08 15:18:16] LONGPOLL from pool 2 requested work restart
 [2012-11-08 15:18:16] New block detected on network before longpoll
 [2012-11-08 15:18:29] LONGPOLL from pool 2 requested work restart

Crashed with signal 11! Will attempt to restart
 [2012-11-08 15:18:29] Started cgminer 2.9.1
 [2012-11-08 15:18:29] Loaded configuration file /opt/etc/cgminer.conf
 [2012-11-08 15:18:29] Icarus Detect: Test failed at /dev/usb/tts/0: get 00000000, should: 000187a2
 [2012-11-08 15:18:29] Icarus Detect: Test failed at /dev/usb/tts/1: get 00000000, should: 000187a2
 [2012-11-08 15:18:29] Icarus Detect: Test failed at /dev/usb/tts/2: get 00000000, should: 000187a2
 [2012-11-08 15:18:29] Icarus Detect: Test failed at /dev/usb/tts/3: get 00000000, should: 000187a2
 [2012-11-08 15:18:29] Icarus Detect: Test failed at /dev/usb/tts/4: get 00000000, should: 000187a2
 [2012-11-08 15:18:29] Icarus Detect: Test failed at /dev/usb/tts/5: get 00000000, should: 000187a2
 [2012-11-08 15:18:30] Probing for an alive pool
 [2012-11-08 15:18:32] GBT longpoll ID activated for http://us2.eclipsemc.com:8337
 [2012-11-08 15:18:32] Pool 1 http://pool.maxbtc.com:8332 alive
 [2012-11-08 15:18:32] Pool 2 http://pool.maxbtc.com:8332 alive
 [2012-11-08 15:18:34] Pool 3 http://us3.eclipsemc.com:8337 alive
 [2012-11-08 15:18:34] Pool 4 http://us2.ozco.in:8332 alive
 [2012-11-08 15:18:35] BFL2: Garbled response probably throttling, clearing buffer
 [2012-11-08 15:18:35] BFL3: Garbled response probably throttling, clearing buffer
 [2012-11-08 15:18:36] Pool 5 http://us1.eclipsemc.com:8337 alive
 [2012-11-08 15:18:37] API bind to port 4028 failed - trying again in 30sec
 [2012-11-08 15:18:37] BFL1: invalid nonce - HW error
 [2012-11-08 15:18:37] BFL1: invalid nonce - HW error
 [2012-11-08 15:18:37] BFL1: Error: Send work reports: NONCE-FOUND:19BCCFAE,CD347D9C

 [2012-11-08 15:18:37] BFL1: Error: Get result reports: OK

 [2012-11-08 15:18:37] BFL1: Error: Send work reports: ERR:UNKNOWN!!!

 [2012-11-08 15:18:37] BFL4: invalid nonce - HW error
 [2012-11-08 15:18:37] BFL4: invalid nonce - HW error
 [2012-11-08 15:18:38] BFL1: Garbled response probably throttling, clearing buffer
 [2012-11-08 15:18:38] BFL1: Garbled response probably throttling, clearing buffer
 [2012-11-08 15:18:39] BFL1: Comms error
 [2012-11-08 15:18:42] BFL1: Comms error
 [2012-11-08 15:18:47] BFL1: invalid nonce - HW error
 [2012-11-08 15:18:47] BFL1: invalid nonce - HW error
 [2012-11-08 15:18:47] BFL1: invalid nonce - HW error
 [2012-11-08 15:18:51] BFL1: took 8495ms - longer than 7000ms
 [2012-11-08 15:18:51] BFL1: Error: Get result reports: USY
 . . .

From then on, all BFLs get garbled, never to kick back into sync. Still get some use out of them, seem to run about half speed.

The attempted restart seems to be a new thing... shame it doesn't work. The script I use already restarts cgminer if it quits, and generally works.

[P_Shep]

I see, you've added a sig handler for segmentation faults.

Maybe some resources/ports/handles/file pointers/whatevers aren't being closed cleanly and things get messed up?

I'll put the --no-restart in my cmd line.

[P_Shep]

Another thing...
The Stratum pool isn't be read correctly from the conf file.
I added it via the API, saved config and it correctly shows in conf file:

   {
      "url" : "stratum+tcp://stratum.ozco.in:3333",
      "user" : "xxxxx",
      "pass" : "xxxxx"
   }

But then when cgminer starts, it shows via the API as a disabled pool, without the 'stratum+tcp://' prefix or port suffix, just 'stratum.ozco.in'.

[chewie]

Currently on 2.9.1 with all the same stats as in my previous post.  There has been several times where my GPU winds down(hash rate abruptly drops) after a block has been found, and then Cgminer crashes.  Fortunately, I was able to watch the crash occur, and there was nothing abnormal being displayed on the program  the moment before the crash happens.  I'm currently on a mining pool that uses GBT protocol.  Thanks, I thought I'd report this abnormality.

[-ck]

Another thing...
The Stratum pool isn't be read correctly from the conf file.
I added it via the API, saved config and it correctly shows in conf file:

   {
      "url" : "stratum+tcp://stratum.ozco.in:3333",
      "user" : "xxxxx",
      "pass" : "xxxxx"
   }

But then when cgminer starts, it shows via the API as a disabled pool, without the 'stratum+tcp://' prefix or port suffix, just 'stratum.ozco.in'.

Leave the striked out bit out of the conf file. It's a bug in the configuration reading code.

[mdude77]

cgminer 2.9.1 and 2.8.7 crash hard when mining on stratum pool and get disconnected.  I've seen it happen multiple times now.

windows 7 x64.

next time it happens I'll see if I can get some details from windows.

M

[crazyates]

cgminer 2.9.1 and 2.8.7 crash hard when mining on stratum pool and get disconnected.  I've seen it happen multiple times now.

windows 7 x64.

next time it happens I'll see if I can get some details from windows.

M

I'm on 2.8.7, and it crashed when I unplugged my wifi adapter. I didn't think anything of it, but it sounds similar.

[jamesg]

Somewhere between 2.8.5 and 2.9.1 the mhs 5s fields changed from 5 to 3. What is the setting to change this back to 5s?

Thanks,
gigavps

[Subo1977]

Somewhere between 2.8.5 and 2.9.1 the mhs 5s fields changed from 5 to 3. What is the setting to change this back to 5s?

Thanks,
gigavps

If you mean the Log interval then have a Look at the git in the section commits.

[tnkflx]

Con,

2.9.1 is extremely unstable for me on Win7 64bit... I went back to 2.8.5.

Can I get you extra debugging info?

[mdude77]

Con,

2.9.1 is extremely unstable for me on Win7 64bit... I went back to 2.8.5.

Can I get you extra debugging info?

2.9.1 is working fine here as long as the stratum pool I'm on is stable.  Otherwise it crashes.  2.8.7 does too.  Can you see if your instability issues are in 2.8.7?

M

[tnkflx]

Con,

2.9.1 is extremely unstable for me on Win7 64bit... I went back to 2.8.5.

Can I get you extra debugging info?

2.9.1 is working fine here as long as the stratum pool I'm on is stable.  Otherwise it crashes.  2.8.7 does too.  Can you see if your instability issues are in 2.8.7?

Upgraded to 2.8.7, lets see how well it goes

[-ck]

Somewhere between 2.8.5 and 2.9.1 the mhs 5s fields changed from 5 to 3. What is the setting to change this back to 5s?

Thanks,
gigavps

--log|-l <arg>      Interval in seconds between log output (default: 3)

That change was after 2.9.1 in git only at the moment

[-ck]

Con,

2.9.1 is extremely unstable for me on Win7 64bit... I went back to 2.8.5.

Can I get you extra debugging info?

Yes you can. The instructions and debug versions required are here:
http://ck.kolivas.org/apps/cgminer/debug/

Same goes for any windows related crashes.

[-ck]

OK I looked.. used the search function and even google but can't find an answer to this question...  I posted on a new thread and was directed to this one.  My question is why will cgminer running on ubuntu 12.04 64 bit will not submit shares (in a timely manner) for scrypt mining.  Hashrate in the cgminer console is ~310Kh/s but share submits are reporting 2Kh/s

Here is my post https://bitcointalk.org/index.php?topic=120773.0

When I posted it I was running 2.7.5 and now I am running 2.8.7 and having the same problem.  Any ideas?
Any help is much appreciated.

Naelr

I think my post got trumped by release 2.9.0... anyone have any ideas?

Naelr

It didn't really get trumped. No one has any idea. Usually if nothing is being produced or lots of HW errors despite a high hashrate, the intensity is too high.