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

[Buchi-88]

@choklivas

THX for the new version, i will test and report

regards

[tuanvie]

win 7 x86 if it works stable?
I often have problems: (

[os2sam]

win 7 x86 if it works stable?
I often have problems: (

Is that a question or a statement?

If your asking if CGMiner works with 32 bit Windoze 7?  The answer is yes.

[tuanvie]

win 7 x86 if it works stable?
I often have problems: (

Is that a question or a statement?

If your asking if CGMiner works with 32 bit Windoze 7?  The answer is yes.

I mean, I often fail to use it on win 7 x86,
and if you can help command for maximum performance?

[os2sam]

win 7 x86 if it works stable?
I often have problems: (

Is that a question or a statement?

If your asking if CGMiner works with 32 bit Windoze 7?  The answer is yes.

I mean, I often fail to use it on win 7 x86,
and if you can help command for maximum performance?

Hmm, works fine for me.

There is no command to maximize performance for my setup, which is USB BE's and a Jalapeno.  I just run CGMiner with the  pool stuff and it detects and sets everything for me.

[tadzio]

Im running 3x Bi*Furry on powered USB HUB - power is sufficient.
Randomly (after 10m - 4h) I get:

Code:

BXF 2 BXFWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT

and miner crushes (WIN 7).
Any idea?

[-ck]

Im running 3x Bi*Furry on powered USB HUB - power is sufficient.
Randomly (after 10m - 4h) I get:

Code:

BXF 2 BXFWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT

and miner crushes (WIN 7).
Any idea?

That is a sign of hardware instability, not software. If you're 100% sure you have enough power (and most people don't have as much as they think they have) then the next thing to do is actively cool them better.

EDIT: Do you mean "crashes" when you say "crushes"? In that case you may be able to help by running a debug version and following the instructions in here:
http://ck.kolivas.org/apps/cgminer/debug/

Read the README-debug file.

[tadzio]

Im running 3x Bi*Furry on powered USB HUB - power is sufficient.
Randomly (after 10m - 4h) I get:

Code:

BXF 2 BXFWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT

and miner crushes (WIN 7).
Any idea?

That is a sign of hardware instability, not software. If you're 100% sure you have enough power (and most people don't have as much as they think they have) then the next thing to do is actively cool them better.

EDIT: Do you mean "crashes" when you say "crushes"? In that case you may be able to help by running a debug version and following the instructions in here:
http://ck.kolivas.org/apps/cgminer/debug/

Read the README-debug file.

Hardware is actively cooled and working in air conditioned room - always below 42C.

Here is the debug:

Code:

cgminerBD.exe caused an Access Violation at location 74de9b60 in module msvcrt.dll Reading from location 02ec0000.

Registers:
eax=02ebfa1c ebx=02ebff20 ecx=3ffffe87 edx=00000000 esi=02ec0000 edi=02ebf87c
eip=74de9b60 esp=02ebf370 ebp=02ebf378 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206

Call stack:
74DE9B60  msvcrt.dll:74DE9B60  memcpy
00449697  cgminerBD.exe:00449697
cgminerBD.exe caused an Access Violation at location 7708e3be in module ntdll.dll Reading from location 2db62da2.

Registers:
eax=01ea9058 ebx=01ec1dd8 ecx=003c0000 edx=01ec1dd8 esi=2db62d9e edi=01ec1dd0
eip=7708e3be esp=02a3fc30 ebp=02a3fc64 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Call stack:
7708E3BE  ntdll.dll:7708E3BE  RtlInitUnicodeString
7708E023  ntdll.dll:7708E023  RtlFreeHeap
74DE98CD  msvcrt.dll:74DE98CD  free
004947D7  cgminerBD.exe:004947D7
00494FF2  cgminerBD.exe:00494FF2
00495072  cgminerBD.exe:00495072
00490C71  cgminerBD.exe:00490C71
004910C6  cgminerBD.exe:004910C6
00491114  cgminerBD.exe:00491114
004912BB  cgminerBD.exe:004912BB
00489F9E  cgminerBD.exe:00489F9E
0048A0FC  cgminerBD.exe:0048A0FC
0042538D  cgminerBD.exe:0042538D
004C015B  cgminerBD.exe:004C015B
74DF1287  msvcrt.dll:74DF1287  _itow_s
74DF1328  msvcrt.dll:74DF1328  _endthreadex
759A336A  kernel32.dll:759A336A  BaseThreadInitThunk
77099F72  ntdll.dll:77099F72  RtlInitializeExceptionChain
77099F45  ntdll.dll:77099F45  RtlInitializeExceptionChain

[-ck]

http://ck.kolivas.org/apps/cgminer/debug/

Read the README-debug file.

Hardware is actively cooled and working in air conditioned room - always below 42C.

Here is the debug:

Code:

Thanks. There's not much information in that. Did you use the debug cgminer.exe binary from that directory as well?

[tadzio]

http://ck.kolivas.org/apps/cgminer/debug/

Read the README-debug file.

Hardware is actively cooled and working in air conditioned room - always below 42C.

Here is the debug:

Code:

Thanks. There's not much information in that. Did you use the debug cgminer.exe binary from that directory as well?

Yes I did. I've run it again.
On the miner console I get this:

Code:

[2014-05-27 07:50:08] BXF 2 BXFWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2014-05-27 07:50:14] BXF 2 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-05-27 07:50:14] BXF 2: Error 0 sending BXFWork sent 0 of 162

Debug:

Code:

cgminerDebug.exe caused an Access Violation at location 74de9a24 in module msvcrt.dll Reading from location 7881399c.

Registers:
eax=00000001 ebx=00000000 ecx=74616368 edx=00000003 esi=78813999 edi=78813d65
eip=74de9a24 esp=041fd4f0 ebp=041fd4f8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Call stack:
74DE9A24  msvcrt.dll:74DE9A24  memcpy
00449AB1  cgminerDebug.exe:00449AB1
00449F3C  cgminerDebug.exe:00449F3C
00465685  cgminerDebug.exe:00465685
00468704  cgminerDebug.exe:00468704
004C015B  cgminerDebug.exe:004C015B
74DF1287  msvcrt.dll:74DF1287  _itow_s
74DF1328  msvcrt.dll:74DF1328  _endthreadex
759A336A  kernel32.dll:759A336A  BaseThreadInitThunk
77099F72  ntdll.dll:77099F72  RtlInitializeExceptionChain
77099F45  ntdll.dll:77099F45  RtlInitializeExceptionChain
cgminerDebug.exe caused an Access Violation at location 74de9b60 in module msvcrt.dll Reading from location 3429275a.

Registers:
eax=02f9f8c2 ebx=02f9ff20 ecx=33b4345a edx=00000000 esi=3429275a edi=02f9f234
eip=74de9b60 esp=02f9f0f0 ebp=02f9f0f8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Call stack:
74DE9B60  msvcrt.dll:74DE9B60  memcpy
00449697  cgminerDebug.exe:00449697
0044A5AE  cgminerDebug.exe:0044A5AE
004654E6  cgminerDebug.exe:004654E6
00469933  cgminerDebug.exe:00469933
00469A35  cgminerDebug.exe:00469A35
0046834A  cgminerDebug.exe:0046834A
0046887C  cgminerDebug.exe:0046887C
004C015B  cgminerDebug.exe:004C015B
74DF1287  msvcrt.dll:74DF1287  _itow_s
74DF1328  msvcrt.dll:74DF1328  _endthreadex
759A336A  kernel32.dll:759A336A  BaseThreadInitThunk
77099F72  ntdll.dll:77099F72  RtlInitializeExceptionChain
77099F45  ntdll.dll:77099F45  RtlInitializeExceptionChain
cgminerDebug.exe caused an Access Violation at location 74de9b60 in module msvcrt.dll Reading from location 77c75ae9.

Registers:
eax=0365f822 ebx=0365ff20 ecx=22e7a74e edx=00000001 esi=77c75ae9 edi=0365f194
eip=74de9b60 esp=0365f050 ebp=0365f058 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Call stack:
74DE9B60  msvcrt.dll:74DE9B60  memcpy
00449697  cgminerDebug.exe:00449697
0044A5AE  cgminerDebug.exe:0044A5AE
004654E6  cgminerDebug.exe:004654E6
00469933  cgminerDebug.exe:00469933
00469A35  cgminerDebug.exe:00469A35
004691EA  cgminerDebug.exe:004691EA
0046982E  cgminerDebug.exe:0046982E
0041F641  cgminerDebug.exe:0041F641
0041F976  cgminerDebug.exe:0041F976
004C015B  cgminerDebug.exe:004C015B
74DF1287  msvcrt.dll:74DF1287  _itow_s
74DF1328  msvcrt.dll:74DF1328  _endthreadex
759A336A  kernel32.dll:759A336A  BaseThreadInitThunk
77099F72  ntdll.dll:77099F72  RtlInitializeExceptionChain
77099F45  ntdll.dll:77099F45  RtlInitializeExceptionChain

[mdude77]

I have two Antminer S2s.  Both misbehave the same way with p2pool.  Within minutes of pointing them at p2pool, my hashrate drops to 930gh/s or lower. 

It shows this way on p2pool, on the S2 LCD, and on the S2 web UI.

It stays this way, or gets worse, as time goes by.  I've run against p2pool for days this way trying different things, and the result is always the same.  Yet running on a conventional pool (like Eligius), things run fine immediately and ongoing.

I've tried adjusting my pseudo share size.

I've tried running on a local node, my public node (other side of the country), and at least one other public p2pool node that was close to me.

Since S2s use cgminer, I was hoping a dev might be able to shed some light on this for me.

BTW, my S1s work fine with p2pool.  At 1/5 the hashrate, but they do work fine.


I apologize if this has been mentioned already.  I stopped following this thread a while ago.

Thanks.

M

[kano]

I have two Antminer S2s.  Both misbehave the same way with p2pool.  Within minutes of pointing them at p2pool, my hashrate drops to 930gh/s or lower.  

It shows this way on p2pool, on the S2 LCD, and on the S2 web UI.

It stays this way, or gets worse, as time goes by.  I've run against p2pool for days this way trying different things, and the result is always the same.  Yet running on a conventional pool (like Eligius), things run fine immediately and ongoing.

I've tried adjusting my pseudo share size.

I've tried running on a local node, my public node (other side of the country), and at least one other public p2pool node that was close to me.

Since S2s use cgminer, I was hoping a dev might be able to shed some light on this for me.

BTW, my S1s work fine with p2pool.  At 1/5 the hashrate, but they do work fine.


I apologize if this has been mentioned already.  I stopped following this thread a while ago.

Thanks.

M

You are running bitmain's S2 driver. Don't do that on p2pool. Also don't do that with bitmain's S1 driver.

Bitmain does some terrible things in their driver including ... discarding stale work in the driver before passing it to the work validation code.
This means on p2pool that if you find a stale block that is still a valid network block, it will be discarded. Oh well.

Use my driver for S1 if you don't want to throw such valid blocks away on p2pool.

My S2 driver is still in development - I'm still trying to work out why the device thinks it's a good idea to have >8000 work items queued in it - more than 30s of work - and to work out how to reduce that without letting it get idle - so I'm still waiting on source code from bitmain.

My blackarrow minion RPi driver is able to handle > 2TH/s of work at 1diff verifying every share returned at 1diff.
The S2 driver, on a faster BBB, should be able to handle 1TH/s of work at 1diff also. It doesn't. So I need to work out how to fix that - but I need the SPI kernel driver code bitmain wrote, for me to work that out.

[Killerloop]

Hi, I noticed a strange behaviour in my mining equipment:
Sometimes out of a sudden I receive BTB: Idled 1 miners for no reason at all. No new block detected by stratum.

http://imageshack.com/a/img841/5870/h19c.png

I am running BitBurner stacks with --avalon-auto on GHash.io

What are the reasons for "idling" miners at such low temperatures and no block detected? Is something wrong with the equipment?
However utility remains pretty high at 22,24 shares/min.

Thanks in advance.

[mdude77]

You are running bitmain's S2 driver. Don't do that on p2pool. Also don't do that with bitmain's S1 driver.

Bitmain does some terrible things in their driver including ... discarding stale work in the driver before passing it to the work validation code.
This means on p2pool that if you find a stale block that is still a valid network block, it will be discarded. Oh well.

Use my driver for S1 if you don't want to throw such valid blocks away on p2pool.

Thanks!  I also get duplicates on p2pool when using my Ants.  I think I only saw that with S2s, though.

My S2 driver is still in development - I'm still trying to work out why the device thinks it's a good idea to have >8000 work items queued in it - more than 30s of work - and to work out how to reduce that without letting it get idle - so I'm still waiting on source code from bitmain.

My blackarrow minion RPi driver is able to handle > 2TH/s of work at 1diff verifying every share returned at 1diff.
The S2 driver, on a faster BBB, should be able to handle 1TH/s of work at 1diff also. It doesn't. So I need to work out how to fix that - but I need the SPI kernel driver code bitmain wrote, for me to work that out.

I appreciate it!

M

[kano]

Hi, I noticed a strange behaviour in my mining equipment:
Sometimes out of a sudden I receive BTB: Idled 1 miners for no reason at all. No new block detected by stratum.

http://imageshack.com/a/img841/5870/h19c.png

I am running BitBurner stacks with --avalon-auto on GHash.io

What are the reasons for "idling" miners at such low temperatures and no block detected? Is something wrong with the equipment?
However utility remains pretty high at 22,24 shares/min.

Thanks in advance.

Might mean your network connection had a hiccup.
Otherwise, ignore it.
I found that message in my cgminer logs 39,007 times with my one BTB board from 12-Sep-2013 until I permanently switched it off on 16-Apr-2014

[Killerloop]

Might mean your network connection had a hiccup.
Otherwise, ignore it.
I found that message in my cgminer logs 39,007 times with my one BTB board from 12-Sep-2013 until I permanently switched it off on 16-Apr-2014

Hmm this is weird...
I restarted CGMiner, the problem no longer shows up and hashrate has increased. Could be a memory leak? I'm taking a look.

[Taugeran]

Hi, I noticed a strange behaviour in my mining equipment:
Sometimes out of a sudden I receive BTB: Idled 1 miners for no reason at all. No new block detected by stratum.

http://imageshack.com/a/img841/5870/h19c.png

I am running BitBurner stacks with --avalon-auto on GHash.io

What are the reasons for "idling" miners at such low temperatures and no block detected? Is something wrong with the equipment?
However utility remains pretty high at 22,24 shares/min.

Thanks in advance.

Might mean your network connection had a hiccup.
Otherwise, ignore it.
I found that message in my cgminer logs 39,007 times with my one BTB board from 12-Sep-2013 until I permanently switched it off on 16-Apr-2014

Any interest in selling said bitburner fury?

[kano]

Hi, I noticed a strange behaviour in my mining equipment:
Sometimes out of a sudden I receive BTB: Idled 1 miners for no reason at all. No new block detected by stratum.

http://imageshack.com/a/img841/5870/h19c.png

I am running BitBurner stacks with --avalon-auto on GHash.io

What are the reasons for "idling" miners at such low temperatures and no block detected? Is something wrong with the equipment?
However utility remains pretty high at 22,24 shares/min.

Thanks in advance.

Might mean your network connection had a hiccup.
Otherwise, ignore it.
I found that message in my cgminer logs 39,007 times with my one BTB board from 12-Sep-2013 until I permanently switched it off on 16-Apr-2014

Any interest in selling said bitburner fury?

It's not a fury.

[Killerloop]

It's not a fury.

Yes it is... BitBurner Fury Rev 1.1

[kano]

It's not a fury.

Yes it is... BitBurner Fury Rev 1.1

Mine isn't