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

[kano]

2.3.1f OK That's from my git that was added to BAMT after 2.3.1 was released
That was to add API support for FPGA's ... 29-Feb ... yep.

That problem description might suggest a possible problem ... not related to my git change ...
If no one else has said or done anything when I wake up I'll look at making a quick test binary for you then
- but it's 3am and I'm tired and likely to make mistakes now

[phorensic]

Uninstalled version "2.6", deleted the DLL's manually in System32 and SysWOW64 (necessary step going between versions!), then installed this new leaked version.  Deleted my kernel bins in cgminer dir as usual, then launched...

Can't really see any change in performance.  Hopefully this gives ckolivas and the kernel devs something to chew on and progress forward, though.

I'm very confused by the overall driver version thing. Is there a post (on this forum or somewhere else) that clarifies driver versions, OpenCL versions, which versions to use, how to change them and so on? I'm using Windows 7.

No and it's a shame because the good info is just spread out all over the place on these forums 

[Qu4k3r]

Hi  

I have a doubt...
Sorry if this is already asked but 235 pages are too long to read  

Can I set "Solo Mode" mining in CGminer as follows?

Code:

cgminer -o http://localhost:3332 -u MyUserName -p MyPassWord -I 9 --auto-fan --auto-gpu --gpu-engine 800,800,775 --gpu-memclock 300

Username and pass for solo mode mining are previously set with guiminer.

Thanks in advance  

[sveetsnelda]

You can only set the 7970 memory 150 lower than the engine clock speed. That's precisely why the memdiff feature exists in cgminer, so add this to your commands:
--gpu-memdiff -150

I didn't know that command existed.  Nice.

A BIOS flash will take care of that clock/voltage issue nicely.     (Assuming it's a dedicated rig, of course)

[os2sam]

Hi  

I have a doubt...
Sorry if this is already asked but 235 pages are too long to read  

Can I set "Solo Mode" mining in CGminer as follows?

Code:

cgminer -o http://localhost:3332 -u MyUserName -p MyPassWord -I 9 --auto-fan --auto-gpu --gpu-engine 800,800,775 --gpu-memclock 300

Username and pass for solo mode mining are previously set with guiminer.

Thanks in advance  

Sure you can.  Why wouldn't you be able to do that?

As long as you have your bitcoind/Bitcoin client started in server mode and the block chain up to date.

I don't know anything about GUIMiner and have no idea what that would have to do with anything.
Sam

[Qu4k3r]

Sure you can.  Why wouldn't you be able to do that?

As long as you have your bitcoind/Bitcoin client started in server mode and the block chain up to date.

I don't know anything about GUIMiner and have no idea what that would have to do with anything.
Sam

Thank you very much!

I mentioned guiminer becuase I used it in the past to do solo mining.
It sets my username/pass for solo mining and also launches btc client in server mode.

[-ck]

I've been watching and I think every-time a thread is idle for 60 seconds and is restarted, it increases overall RAM usage (like the previous thread isn't getting removed from RAM).  I use gpumax, which can have high idle times occasionally....  cgminer starts at 174 meg of RAM for me and currently its using 800 meg, so I think adding another stick of RAM would help, but only by delaying the time it takes for the system to run out of RAM.  If I restart cgminer, then its back to normal mem usage and slowly increases again.

Then you're onto something. It is dangerous to try and delete the ram used by the old threads because that just leads to a crash, so I specifically made the threads' ram not get cleaned up - so it is expected that ram usage will go up. However, you're doing something horribly wrong if your GPUs are going idle all the time. That's supposed to ONLY happen if your GPUs wedge because you're overclocking them too much and the GPU stops responding. I highly recommend reviewing your temperatures and clock speeds.

[kano]

...
The web server part is only for rig mining stats (BAMT).  It's cgminer that keeps growing in memory size.  I've been watching and I think every-time a thread is idle for 60 seconds and is restarted, it increases overall RAM usage (like the previous thread isn't getting removed from RAM).  I use gpumax, which can have high idle times occasionally....  cgminer starts at 174 meg of RAM for me and currently its using 800 meg, so I think adding another stick of RAM would help, but only by delaying the time it takes for the system to run out of RAM.  If I restart cgminer, then its back to normal mem usage and slowly increases again.

I've been reviewing the command switches and am not sure which one increases the time a thread can be idle before cgminer restarts it... can someone assist me with what switch does that?  I would like to set the thread idle limit to 120 or 180 seconds to see if that reduces my thread restarts (and therefore RAM usage).  I'm on cgminer v 2.3.1f.

Some questions regarding this
1) When you run "./cgminer --help" what does the 2nd line "Built with ..." say?

2) run "ps -eL | grep cgminer | grep -v grep | wc" and it will say how many threads there are

3) run "ps -eLF | grep cgminer | grep -v grep | tail -1" will show you the command running cgminer so you can be sure it matches exactly what you said

[Turbor]

Hey Con. Will you release a version with kanos work that supports mining with Icarus and BFL (windows7, 2.3.1f) ? There is a 7.5 BTC bounty for that. Would be nice

[boozer]

Some questions regarding this
1) When you run "./cgminer --help" what does the 2nd line "Built with ..." say?

2) run "ps -eL | grep cgminer | grep -v grep | wc" and it will say how many threads there are

3) run "ps -eLF | grep cgminer | grep -v grep | tail -1" will show you the command running cgminer so you can be sure it matches exactly what you said

Here's the information you requested:

root@oconner:/opt/miners/cgminer# ./cgminer --help
cgminer 2.3.1f
Built with GPU bitforce icarus mining support.

root@oconner:/opt/miners/cgminer# ps -eL | grep cgminer | grep -v grep | wc
     53     265    2014

root@oconner:/opt/miners/cgminer# ps -eLF | grep cgminer | grep -v grep | tail -1
root     27782 27781 27188  0   53 185303 388892 0 18:25 pts/1    00:00:00 /opt/miners/cgminer cgminer -Q 2 --api-listen --gpu-engine 700-825 700-825 700-830 700-815 700-820 700-830 --gpu-memclock 240 --auto-gpu --auto-fan --temp-target 75 -I 8 -o http://gpumax.com:8332 -u x-p x -o http://x:80 -u x -p x

[kano]

OK 53 isn't a big number so it's not what I was considering may be the cause.

The other two numbers there are not big yet either
SZ=185303 RSS=388892
if you have a sizeable number of devices on your rig (your options suggest 6 GPU devices? Are any of them dual?)

My rig has only 4 devices and it reads:
SZ=151618 RSS=127032
(and yes I use the code also from my GIT except I don't enable Bitforce being compiled in, I only add Icarus at the moment)

However, in my case it doesn't run rampant later on.

Definitely getting nowhere with this so far looking at the system process info.

How often does BAMT request status info from the API? And what API requests does it use? (I don't know exactly)
I guess if there was some accidental fast loop missing a delay accessing the API over and over again that might cause issues?
My monitoring in my current setup is a set of 3 API requests every 10 seconds, but in my previous configuration (same code and hardware a week ago) I also added on top of that another 1 API request every second - but that didn't cause extra RAM usage.

I guess I'll defer to the expert (ckolivas)
Going idle can be for two reasons, as you suggested if GPUMax isn't providing you with any work, but of course the normal reason is as ckolivas said, if your setting are too high.

Are those temp settings and clock settings in any way high for your GPU's?
(The numbers themselves don't seem high for many cards - but I guess that depends on what the cards are - and if they are old and no longer stable if OC'd)
Do you ever get any status change on any of the GPU's? (i.e. not Alive)

Oddly enough I am working on a notification Java app that uses the API that might help monitor this problem (that comment above about 3 API every 10 seconds - summary,devs,pools) if it is temp/clock related
(The code already done would be enough)
But I've been expending a lot of effort on threading the data handling part of it (and probably making it too complex) to ensure that blocking code is in threads unrelated to time sensitive code (and then there's the issue of RAM usage in Java that I need to resolve next ...)
So I seem to be talking way longer than I expected to get even a beta out

[boozer]

OK 53 isn't a big number so it's not what I was considering may be the cause.

The other two numbers there are not big yet either
SZ=185303 RSS=388892
if you have a sizeable number of devices on your rig (your options suggest 6 GPU devices? Are any of them dual?)

How often does BAMT request status info from the API? And what API requests does it use? (I don't know exactly)
I guess if there was some accidental fast loop missing a delay accessing the API over and over again that might cause issues?

My monitoring in my current setup is a set of 3 API requests every 10 seconds, but in my previous configuration (same code and hardware a week ago) I also added on top of that another 1 API request every second - but that didn't cause extra RAM usage.

I guess I'll defer to the expert (ckolivas)
Going idle can be for two reasons, as you suggested if GPUMax isn't providing you with any work, but of course the normal reason is as ckolivas said, if your setting are too high.

Are those temp settings and clock settings in any way high for your GPU's?
(The numbers themselves don't seem high for many cards - but I guess that depends on what the cards are - and if they are old and no longer stable if OC'd)
Do you ever get any status change on any of the GPU's? (i.e. not Alive)

They are all 5970's (dual gpu) so those temps are okay. I was actually using Phoenix until I just recently started with cgminer and had those clocks stable on phoenix for several weeks.  Not sure how often BAMT requests via API.  I have BAMT running on 2 rigs with 3 7970's each with same version of cgminer and do not see the issue on there.  I'll try running stock for awhile and see what happens.

[kano]

Hmm OK, so it's effectively 12 devices.
That's a lot of GPU devices

The RSS number is (obviously) what shows if you are using up more RAM and running out of it.
I guess what's needed now is to find out what is happening when that changes ... and does it jump up in steps, or is a gradual rise?

Edit: oh I just noticed another thing ... you have 2 pools and the main is GPUMax - does it swap pools a lot?

[-ck]

Going idle can be for two reasons, as you suggested if GPUMax isn't providing you with any work, but of course the normal reason is as ckolivas said, if your setting are too high.

Going idle can only be for ONE reason and that is the GPU not responding. Waiting on work from a server or network lag/outage does NOT register a mining thread as being idle. It makes no sense restarting a thread that is just waiting on work.

[kano]

Going idle can be for two reasons, as you suggested if GPUMax isn't providing you with any work, but of course the normal reason is as ckolivas said, if your setting are too high.

Going idle can only be for ONE reason and that is the GPU not responding. Waiting on work from a server or network lag/outage does NOT register a mining thread as being idle. It makes no sense restarting a thread that is just waiting on work.

OK, yep I'm just using bad nomenclature.
I simply meant if the device itself was not processing there could only be 2 reasons I can think of
Not getting work or being a problem with it.

[boozer]

Hmm OK, so it's effectively 12 devices.
That's a lot of GPU devices

Edit: oh I just noticed another thing ... you have 2 pools and the main is GPUMax - does it swap pools a lot?

Sorry for the confusion, I have 2 rigs with 3 5970's each that have the this issue (so 6 GPU's max in one of my rigs), the 2 rigs with 3 7970's each that work fine.
I haven't noticed a lot of pool swapping... occasionally one core will swap back and forth.

[-ck]

They are all 5970's (dual gpu) so those temps are okay. I was actually using Phoenix until I just recently started with cgminer and had those clocks stable on phoenix for several weeks.  Not sure how often BAMT requests via API.  I have BAMT running on 2 rigs with 3 7970's each with same version of cgminer and do not see the issue on there.  I'll try running stock for awhile and see what happens.

58x0 are amazing hashing beasts for so many reasons, and this is one of them - they're one of the few GPUs that actually recovers after dying a "soft" death and cgminer restarts their threads a short while later. Nonetheless, you should try and find clocks that don't make the GPUs ever crash as I'm pretty certain this is your problem.

[kano]

Hmm OK, so it's effectively 12 devices.
That's a lot of GPU devices

Edit: oh I just noticed another thing ... you have 2 pools and the main is GPUMax - does it swap pools a lot?

Sorry for the confusion, I have 2 rigs with 3 5970's each that have the this issue (so 6 GPU's max in one of my rigs), the 2 rigs with 3 7970's each that work fine.
I haven't noticed a lot of pool swapping... occasionally one core will swap back and forth.

I guess related to that (I mean ckolivas comment above)
Are the GPU's showing Temp & RPM?
If ADL isn't working (e.g. missing "export DISPLAY=:0" or the display isn't available for other reasons) then I guess the cards could just keep failing over and over.

[boozer]

I guess related to that (I mean ckolivas comment above)
Are the GPU's showing Temp & RPM?
If ADL isn't working (e.g. missing "export DISPLAY=:0" or the display isn't available for other reasons) then I guess the cards could just keep failing over and over.

Yea, I have the export Display=:0 as part of my start script.  I also have export GPU_USE_SYNC_OBJECTS=1... would that cause any issues since there are no 7970's?

Its been running for 6 hours now, but is up to 522 Meg of RAM... however it seems to be able to run longer since I lowered my intensity like ckolivas suggested. 

When I did cgminer on my 7970's, it was real easy to tell a clock issue, as they would get sick and/or die... however, I have not seen any problems like that on here, normally when I log on to check, everything appears normal except RAM usage is going up..... But again, ckolivas explained why this could be since he said the 59x0 series can recover easily.

How do identify issues in cgminer if they don't get labeled sick or dead?  Do I just need to filter the output something like -m idle to see only idle messages?  I trust ckolivas post above that clocks are the issue, but is there away to find which GPU(s) being restarted?

Code:

27782 root      20   0 1057m 522m  55m S  5.0 29.5  18:21.41 cgminer


cgminer version 2.3.1f - Started: [2012-03-17 15:52:48]
--------------------------------------------------------------------------------
 (5s):2263.1 (avg):2225.3 Mh/s | Q:12003  A:10923  R:94  HW:0  E:91%  U:31.16/m
 TQ: 4  ST: 5  SS: 13  DW: 387  NB: 46  LW: 0  GF: 25  RF: 119
 Connected to http://gpumax.com:8332 with LP as user x
 Block: 0000066396107079d1f26f4324da7369...  Started: [21:35:17]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  72.5C 4453RPM | 375.8/374.0Mh/s | A:1850 R:13 HW:0 U: 5.28/m I: 8
 GPU 1:  74.5C 4453RPM | 376.9/372.4Mh/s | A:1863 R:22 HW:0 U: 5.31/m I: 8
 GPU 2:  75.5C 4463RPM | 378.4/374.4Mh/s | A:1858 R:21 HW:0 U: 5.30/m I: 8
 GPU 3:  68.5C 4463RPM | 372.0/367.5Mh/s | A:1689 R:13 HW:0 U: 4.82/m I: 8
 GPU 4:  74.5C 3979RPM | 372.3/364.9Mh/s | A:1807 R:13 HW:0 U: 5.15/m I: 8
 GPU 5:  74.0C 3983RPM | 378.7/372.1Mh/s | A:1856 R:12 HW:0 U: 5.29/m I: 8
--------------------------------------------------------------------------------

[2012-03-17 21:43:28] Accepted 00000000.46f55b55.50517462 GPU 3 thread 6 pool 0
[2012-03-17 21:43:30] Accepted 00000000.b048d923.17e692c8 GPU 5 thread 10 pool 0
[2012-03-17 21:43:30] Accepted 00000000.98616a0b.58522de7 GPU 2 thread 5 pool 0
[2012-03-17 21:43:30] Accepted 00000000.39d5a007.49107274 GPU 0 thread 0 pool 0
[2012-03-17 21:43:30] Accepted 00000000.26108520.1ac3378d GPU 0 thread 1 pool 0
[2012-03-17 21:43:31] Accepted 00000000.cda7345f.774b39e8 GPU 5 thread 10 pool 0
[2012-03-17 21:43:38] Accepted 00000000.8e7044df.5236adda GPU 4 thread 8 pool 0

[kano]

The GPU's are showing Temp/RPM as you can see - so yep that means ADL is working.
That's all I was thinking there that maybe ADL wasn't able to get the Temp/RPM for some reason (even if the DISPLAY was set) so the cards were failing all the time.

There's no device failure statistics in cgminer other than HW which is 0 in your case.
Send ckolivas some BTC and ask him to implement it (or if he's not expecting to be able to do that soon - send it to me )
Then I could add a device status command in the API to return those numbers.

Edit: hmm the thread does have the timestamp it was last sick though ...