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

[Peao]

"File not found" @ http://ck.kolivas.org/apps/cgminer/cgminer-2.2.3-x86_64-built.tar.bz2

 

[1713867061]

1713867061

[1713867061]

1713867061

[1713867061]

1713867061

[1713867061]

1713867061

[1713867061]

1713867061

[bulanula]

So after 9 months on mining with 30 GPU (15x 15970s) I have two "degraded" GPUs.  GPU #0 on .183 rig and GPU #5 on the .184 rig (which will crash about once a day - hard hang even on stock w/ low temps).  I also have "lost" 2 fans.  Be interesting to see what my "attrition" will be at the one year mark.

Good to see that these cards are somewhat resistant to mining long term !
 
We need more analysis like this done. I just started mining so hopefully I won't have anything to report for a looooong while. LOL !

[kano]

Well I can quote 6 months (yeah that's not very long) but only on a pair of GA HD 6950's and only running at 900 which is not OC (but RAM UC to -125, below GPU)

Only thing that happened once about 2 months ago is one fan started to ring and after about 1.5 days I hit it a few times
Stopped ringing and been fine ever since

However ... since about when BTC got down to $5 on the way down (about 4 months ago) I've been switching it off weekdays for 6 hours each day (due to electricity rate bands - it's about 44c a kWh during those 6 hours - more than double before or after and 4 times off peak) and that goes against what I always tell people about their computers and that is that things fail due to change (switch on and off) more often that just due to running non-stop (when things tend to be stable) if you use them regularly also.

However since we push the cards so hard that probably doesn't count in this case ... any down time may be good recuperation time for them

[TurdHurdur]

How do you specify differing vector and worksize for different cards?
cgminer: -v: '4,2' is not a number
cgminer: -w: '128,64' is not a number

[ThiagoCMC]

"File not found" @ http://ck.kolivas.org/apps/cgminer/cgminer-2.2.3-x86_64-built.tar.bz2

 

.tar.bz2 isn't found and:

lrzuntar cgminer-2.2.3-x86_64-built.tar.lrz
Output filename is: ./cgminer-2.2.3-x86_64-built.tar...Decompressing...
Attempting to work with file produced by newer lrzip version 0.6 file.
Decompressing...Unexpected initial tag 1 in streams
Failed to open_stream_in in runzip_chunk
No such file or directory
Fatal error - exiting

 

[P_Shep]

Re: Cross Compiling...

1. Added #define _GNU_SOURCE to bitforce.c (was having problems with pthread_rwlock_t)
- Not fixed

2. Had to comment out the functional affine_to_cpu, leaving just the empty stub in main.c because my libraries evidently don't support processor affinity (Ancient compiler again, I guess). Perhaps a test for cpu_set_t could be done or something.
- Fixed

[ancow]

lrzuntar cgminer-2.2.3-x86_64-built.tar.lrz
Output filename is: ./cgminer-2.2.3-x86_64-built.tar...Decompressing...
Attempting to work with file produced by newer lrzip version 0.6 file.
Decompressing...Unexpected initial tag 1 in streams
Failed to open_stream_in in runzip_chunk
No such file or directory
Fatal error - exiting

You don't think the highlighted bit could be part of your problem?

[-ck]

"File not found" @ http://ck.kolivas.org/apps/cgminer/cgminer-2.2.3-x86_64-built.tar.bz2

 

Fixed

[Red Emerald]

Thanks for the tweaks for p2pool!

[rcocchiararo]

i guess its not posible to use it to read more than one pc, right?

Kano code is just an "example" (Kano wrote the RPC code for cgminer BTW).  Other people have written multi-rig management/reporting tools which use the RPC functionality in cgminer.  There are two web based tools and BAMT uses RPC for both web based tools and console tools.

Code:

                  Temp    Load  Rate     Accept/Invalid    Status
  192.168.0.181 0: 68.5c+   99%  372 Mhs  13268/31 (0.23%)  up: 1 day, 18:31
                1: 75.5c    99%  377 Mhs  13238/28 (0.21%)  load: 0.00, 0.00, 0.00
                2: 80c+     99%  380 Mhs  13138/39 (0.30%)
                3: 71c+     99%  381 Mhs  13318/43 (0.32%)
                4: 79.5c-   99%  384 Mhs  12976/22 (0.17%)
                5: 64c      99%  378 Mhs  13228/28 (0.21%)
  192.168.0.182 0: 80.5c    99%  330 Mhs  11629/22 (0.19%)  up: 2 days, 11:57
                1: 77c+     99%  379 Mhs  12729/34 (0.27%)  load: 0.00, 0.00, 0.00
                2: 74.5c    99%  379 Mhs  12652/30 (0.24%)
                3: 72.5c    99%  382 Mhs  12568/21 (0.17%)
                4: 74c      99%  377 Mhs  12590/31 (0.25%)
                5: 72.5c+   99%  381 Mhs  12651/23 (0.18%)
  192.168.0.183 0: 73.5c     0%  331 Mhs  4815/8 (0.17%)    up: 17:34
                1: 74.5c-   99%  361 Mhs  5326/6 (0.11%)    load: 0.04, 0.03, 0.00
                2: 67.5c    99%  378 Mhs  5424/6 (0.11%)
                3: 67c+     99%  375 Mhs  5481/11 (0.20%)
                4: 71.5c    99%  386 Mhs  5501/7 (0.13%)
                5: 69.5c+   99%  378 Mhs  5540/6 (0.11%)
  192.168.0.184 0: 69c      99%  369 Mhs  410/0 (0.00%)     up:  1:19
                1: 66.5c+   99%  396 Mhs  367/0 (0.00%)     load: 0.00, 0.00, 0.00
                2: 68c      99%  361 Mhs  376/0 (0.00%)
                3: 64c+     99%  367 Mhs  404/0 (0.00%)
                4: 68c+     99%  371 Mhs  348/0 (0.00%)
                5: 62c      99%  330 Mhs  375/1 (0.27%)
Total: 8968.82 Mhash/s  183140 accepted, 396 invalid (0.22%)

This is the multi-rig monitoring view in BAMT.  Also the nice thing about the RPC code (I organized the bounty project BTW) is that if existing solutions don't do what you want it to do, you (or someone else) can also write another one.  Since the RPC API is a standardized set of queries it doesn't require modifying the cgminer to implement new "front ends".


Off topic:  192.168.0.183's GPU #0 must have bad VRM.  .  It will thermally cut out for a second or so every 20 or 30 seconds.  The core is not running too hot so it makes me think it is the VRMs.  Since mpgumon only gets updates once every 30 seconds or so it will either show 99% or 0% depending on timing.  I have dropped that GPU back to stock but it keeps "cycling" on & off.  I think it is degraded.  

So after 9 months on mining with 30 GPU (15x 15970s) I have two "degraded" GPUs.  GPU #0 on .183 rig and GPU #5 on the .184 rig (which will crash about once a day - hard hang even on stock w/ low temps).  I also have "lost" 2 fans.  Be interesting to see what my "attrition" will be at the one year mark.

Will look into that.

I tried with "cgminer web monitor", but it tells me that my VGAs are offline.

Then i installed anubis, flashy and nice, but i would preffer not to have mysql installed.

[kano]

...
I tried with "cgminer web monitor", but it tells me that my VGAs are offline.
...

What options did you use to run cgminer?
You of course need --api-listen before anything will work.
You need --api-network if the monitoring tool is on a different computer or if the monitoring tool doesn't allow 127.0.0.1 when it is on the same computer

Edit: I'm thinking of adding --api-allow IP[/N],IP2[/N2]...
not sure about deprecating --api-network - but probably easiest to just leave it (unless ckolivas has a preference about that)

[The00Dustin]

Edit: I'm thinking of adding --api-allow IP[/N],IP2[/N2]...
not sure about deprecating --api-network - but probably easiest to just leave it (unless ckolivas has a preference about that)

I think, as a general rule of thumb, it should be possible for any network service to accept connections from any IP, making it possible to restrict this is good, but IMHO --api-network shouldn't be deprecated unless --api-allow will accept *[/*].  While this won't likely ever affect me, it would affect anyone that wants to monitor rigs in a datacenter from a home computer with a dynamic IP, especially one where the ISP forces IP changes daily or more frequently.

[kano]

Edit: I'm thinking of adding --api-allow IP[/N],IP2[/N2]...
not sure about deprecating --api-network - but probably easiest to just leave it (unless ckolivas has a preference about that)

I think, as a general rule of thumb, it should be possible for any network service to accept connections from any IP, making it possible to restrict this is good, but IMHO --api-network shouldn't be deprecated unless --api-allow will accept *[/*].  While this won't likely ever affect me, it would affect anyone that wants to monitor rigs in a datacenter from a home computer with a dynamic IP, especially one where the ISP forces IP changes daily or more frequently.

Then I guess next would be to add security also
Meh, I've written security stuff in Java (it's there already) but never C, I guess I should read up ... but then windows appears in the middle of it all and makes you wanna run screaming from the room ...

ssh tunnels are nice and easy

Anyway - yes I think I'd prefer to leave --api-network and add --api-allow as a second option.
(/me adds it to the list of things I should get done)

[Red Emerald]

Edit: I'm thinking of adding --api-allow IP[/N],IP2[/N2]...
not sure about deprecating --api-network - but probably easiest to just leave it (unless ckolivas has a preference about that)

I think, as a general rule of thumb, it should be possible for any network service to accept connections from any IP, making it possible to restrict this is good, but IMHO --api-network shouldn't be deprecated unless --api-allow will accept *[/*].  While this won't likely ever affect me, it would affect anyone that wants to monitor rigs in a datacenter from a home computer with a dynamic IP, especially one where the ISP forces IP changes daily or more frequently.

Then I guess next would be to add security also
Meh, I've written security stuff in Java (it's there already) but never C, I guess I should read up ... but then windows appears in the middle of it all and makes you wanna run screaming from the room ...

ssh tunnels are nice and easy

Anyway - yes I think I'd prefer to leave --api-network and add --api-allow as a second option.
(/me adds it to the list of things I should get done)

I think the flags work well as they are.  Theres firewalls and hosts.allow for limiting access, so I don't see any reason to add it to cgminer.

[Frizz23]

Which flags do I have to use to get the best out of my 7970?

[-ck]

Which flags do I have to use to get the best out of my 7970?

cgminer is currently not performing that well yet on 7970. The best you'll get is likely to be with -g 3 -I 9 and no other flags. It defaults to -v 1 -w 256 -k poclbm when it detects a 7970.

[BOARBEAR]

Presuming (on windows) you ran a previous version and it worked and the new version doesn't ...

The output of use would be "cgminer -n" and "cgminer -D -T ..." (where ... are the other options you normally use)

[2012-02-07 07:12:29] Started cgminer 2.2.3                   
[2012-02-07 07:12:29] CL Platform 0 vendor: Advanced Micro Devices, Inc.                   
[2012-02-07 07:12:29] CL Platform 0 name: AMD Accelerated Parallel Processing                   
[2012-02-07 07:12:29] CL Platform 0 version: OpenCL 1.1 AMD-APP (898.1)                   
[2012-02-07 07:12:29] Platform 0 devices: 1                   
[2012-02-07 07:12:29] Testing pool http://127.0.0.1:8332                   
[2012-02-07 07:12:29] Popping work to stage thread                   
[2012-02-07 07:12:29] Popping work to work thread                   
[2012-02-07 07:12:29] Successfully retrieved and deciphered work from pool 0 http://127.0.0.1:8332                   
[2012-02-07 07:12:29] Pushing pooltest work to base pool                   
[2012-02-07 07:12:29] Pool 0 http://127.0.0.1:8332 active                   
[2012-02-07 07:12:29] Pushing ping to longpoll thread                   
[2012-02-07 07:12:29] Pushing work to getwork [2que0u1e2 - 0 2 - 0 7   0 7 : 1 2 : 2 9 ]   P u s
hing ping to thread 0                   
[2012-02-07 07:12:29] Popping work to stage thre[a2d0 1 2 - 0 2 - 0 7   0 7 : 1 2 : 2 9 ]   I
nit GPU thread 0 GPU 0 virtual GPU 0                   
[2012-02-07 07:12:29] CL Platform vendor: Advanced Micro Devices, Inc.                   
[2012-02-07 07:12:29] CL Platform name: AMD Accelerated Parallel Processing                   
[2012-02-07 07:12:29] CL Platform version: OpenCL 1.1 AMD-APP (898.1)                   
[2012-02-07 07:12:29] List of devices:                   
[2012-02-07 07:12:[2290]1 2N-o0 2l-o0n7g -0p7o:l1l2 :f2o9u]n d    0o   nC yapnrye spso o l   s e r v e r                     
         
[2012-02-07 07:12:29] Selected 0: Cypress                   
[2012-02-07 07:12:29] Preferred vector width reported 4                   
[2012-02-07 07:12:29] Max work group size reported 256                   
[2012-02-07 07:12:29] No binary found, generating from source                   
[2012-02-07 07:12:29] Setting worksize to 64                   
[2012-02-07 07:12:29] Patched source to suit 4 vectors                   
[2012-02-07 07:12:29] cl_amd_media_ops found, setting BITALIGN                   
[2012-02-07 07:12:29] BFI_INT patch requiring device found, patched source with BFI_INT                   
[2012-02-07 07:12:29] CompilerOptions: -D WORKSIZE=64 -D VECTORS4 -D BITALIGN -D BFI_INT                   
[2012-02-07 07:12:29] Error: Building Program (clBuildProgram)                   
[2012-02-07 07:12:29]                     
[2012-02-07 07:12:29] Failed to init GPU thread 0, disabling device 0                   
[2012-02-07 07:12:29] Restarting the GPU from the menu will not fix this.                   
[2012-02-07 07:12:29] Try restarting cgminer.                   
[2012-02-07 07:12:29] Init GPU thread 1 GPU 0 virtual GPU 0                   
[2012-02-07 07:12:29] CL Platform vendor: Advanced Micro Devices, Inc.                   
[2012-02-07 07:12:29] CL Platform name: AMD Accelerated Parallel Processing                   
[2012-02-07 07:12:29] CL Platform version: OpenCL 1.1 AMD-APP (898.1)                   
[2012-02-07 07:12:29] List of devices:                   
[2012-02-07 07:12:29]    0   Cypress                   
[2012-02-07 07:12:29] Selected 0: Cypress                   
[2012-02-07 07:12:29] Preferred vector width reported 4                   
[2012-02-07 07:12:29] Max work group size reported 256                   
[2012-02-07 07:12:29] No binary found, generating from source                   
[2012-02-07 07:12:29] Setting worksize to 64                   
[2012-02-07 07:12:29] Patched source to suit 4 vectors                   
[2012-02-07 07:12:29] cl_amd_media_ops found, setting BITALIGN                   
[2012-02-07 07:12:29] BFI_INT patch requiring device found, patched source with BFI_INT                   
[2012-02-07 07:12:29] CompilerOptions: -D WORKSIZE=64 -D VECTORS4 -D BITALIGN -D BFI_INT                   
[2012-02-07 07:12:29] Error: Building Program

[-ck]

Debugging requires:
-D --verbose -T
as the README file says...

[BOARBEAR]

Debugging requires:
-D --verbose -T
as the README file says...

[2012-02-07 07:49:21] Started cgminer 2.2.3                    
[2012-02-07 07:49:21] CL Platform 0 vendor: Advanced Micro Devices, Inc.                    
[2012-02-07 07:49:21] CL Platform 0 name: AMD Accelerated Parallel Processing                    
[2012-02-07 07:49:21] CL Platform 0 version: OpenCL 1.1 AMD-APP (898.1)                    
[2012-02-07 07:49:21] Platform 0 devices: 1                    
[2012-02-07 07:49:21] Testing pool http://127.0.0.1:8332                    
[2012-02-07 07:49:21] Popping work to stage thread                    
[2012-02-07 07:49:21] Popping work to work thread                    
[2012-02-07 07:49:21] Successfully retrieved and deciphered work from pool 0 http://127.0.0.1:8332                    
[2012-02-07 07:49:21] Pushing pooltest work to base pool                    
[2012-02-07 07:49:21] Pool 0 http://127.0.0.1:8332 active                    
[2012-02-07 07:49:21] Pushing ping to longpoll thread                    
[2012-02-07 07:49:21] Pushing work to getwork[20 1q2u-e0u2e- 0 7   0 7 : 4 9 : 2 1 ]   P u s h i n g
 ping to thread 0                    
[2012-02-07 07:49:21] Popping work to stage th[r2e0a1d2 - 0 2 - 0 7   0 7 : 4 9 : 2 1 ]   I n i
t GPU thread 0 GPU 0 virtual GPU 0                    
[2012-02-07 07:49:21] CL Platform vendor: Advanced Micro Devices, Inc.                    
[2012-02-07 07:49:21] CL Platform name: AMD Accelerated Parallel Processing                    
[2012-02-07 07:49:21] CL Platform version: OpenCL 1.1 AMD-APP (898.1)                    
[2012-02-07 07:49:21] List of devices:                    
[2012-02-07 07:49:[2210]1 2N-o0 2l-o0n7g -0p7o:l4l9 :f2o1u]n d    0o   nC yapnrye spso o l   s e r v e r                      
        
[2012-02-07 07:49:21] Selected 0: Cypress                    
[2012-02-07 07:49:21] Preferred vector width reported 4                    
[2012-02-07 07:49:21] Max work group size reported 256                    
[2012-02-07 07:49:21] No binary found, generating from source                    
[2012-02-07 07:49:21] Setting worksize to 64                    
[2012-02-07 07:49:21] Patched source to suit 4 vectors                    
[2012-02-07 07:49:21] cl_amd_media_ops found, setting BITALIGN                    
[2012-02-07 07:49:21] BFI_INT patch requiring device found, patched source with BFI_INT                    
[2012-02-07 07:49:21] CompilerOptions: -D WORKSIZE=64 -D VECTORS4 -D BITALIGN -D BFI_INT                    
[2012-02-07 07:49:21] Error: Building Program (clBuildProgram)                    
[2012-02-07 07:49:21]                    
[2012-02-07 07:49:21] Failed to init GPU thread 0, disabling device 0                    
[2012-02-07 07:49:21] Restarting the GPU from the menu will not fix this.                    
[2012-02-07 07:49:21] Try restarting cgminer.                    
[2012-02-07 07:49:21] Init GPU thread 1 GPU 0 virtual GPU 0                    
[2012-02-07 07:49:21] CL Platform vendor: Advanced Micro Devices, Inc.                    
[2012-02-07 07:49:21] CL Platform name: AMD Accelerated Parallel Processing                    
[2012-02-07 07:49:21] CL Platform version: OpenCL 1.1 AMD-APP (898.1)                    
[2012-02-07 07:49:21] List of devices:                    
[2012-02-07 07:49:21]    0   Cypress                    
[2012-02-07 07:49:21] Selected 0: Cypress                    
[2012-02-07 07:49:21] Preferred vector width reported 4                    
[2012-02-07 07:49:21] Max work group size reported 256                    
[2012-02-07 07:49:21] No binary found, generating from source                    
[2012-02-07 07:49:21] Setting worksize to 64                    
[2012-02-07 07:49:21] Patched source to suit 4 vectors                    
[2012-02-07 07:49:21] cl_amd_media_ops found, setting BITALIGN                    
[2012-02-07 07:49:21] BFI_INT patch requiring device found, patched source with BFI_INT                    
[2012-02-07 07:49:21] CompilerOptions: -D WORKSIZE=64 -D VECTORS4 -D BITALIGN -D BFI_INT                    
[2012-02-07 07:49:21] Error: Building Program

cgminer crashed

[dlasher]

let me show you a snap shot from my anubis console of one of the 4 rigs I have with 5870s each.

I apologize if this is linked somewhere else in this massive thread, but is that interface/summary/scripts opensource/linkable/etc?