Author

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

legendary
Activity: 1795
Merit: 1208
This is not OK.
Re: Cross Compiling...

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

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 Smiley

legendary
Activity: 1204
Merit: 1000
฿itcoin: Currency of Resistance!

.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

 Embarrassed
full member
Activity: 216
Merit: 100
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
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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 Smiley
Stopped ringing and been fine ever since Tongue

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 Smiley
hero member
Activity: 518
Merit: 500
Quote from: DeathAndTaxes

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. Grin LOL !
donator
Activity: 1218
Merit: 1079
Gerald Davis
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.  Sad.  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.
newbie
Activity: 78
Merit: 0
...
- Update example web miner.php to use new API commands
Anyone who used the old one this one should be interesting to look at once or twice Smiley
(I of course use it to view the status of my rig since it's all in one page)
Of course there are other more complex ones out there for pure display only
This one also happens to allow you to change everything that the API allows (unless I missed something Tongue)

looks neat

i guess its not posible to use it to read more than one pc, right?
donator
Activity: 1218
Merit: 1079
Gerald Davis
Quote
- The --donation feature is GONE.

I am sorry to see it go but I understand the logic (complexity, potential source of bugs that only donators get, etc).

 I never used it, relying instead on manual donations & bounties.  I hope those that did use it continue to make donations manually.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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)
member
Activity: 77
Merit: 10
I cant start miner now with new version

:

     -02-06 08








[2012-02-06 08:39:17] Failed to init GPU thread 0, disabling device 0
[2012-02-06 08:39:17] Restarting the GPU from the menu will not fix this.
[2012-02-06 08:39:17] Try restarting cgminer.
Press enter to continue:
39:17] No long-poll found on any pool server



-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New version: 2.2.3

Links for both binary and source in top post.

Note this version has extra goodness for mining on p2pool, though other pools will of course benefit too.

Human readable summary of possibly user visible changes:

- New opencl kernels to work half decently on GCN hardware 79xx and to make phatk2 work on them, NVIDIA devices and much older ATI GPUs.

- OpenCL Platform information is now available when cgminer is called with --ndevs, including what devices are available on each platform. cgminer also now supports the --gpu-platform command line option which allows you to choose what platform to use, should you have multiple installed (eg both NVIDIA and ATI, or mutliple SDKs from ATI). Note you MUST delete any *.bin files generated before starting for new binaries to be generated using the chosen platform.

- Some pools support an extension called "submitold" which recommends you actually submit stales. Instead of universally throwing them out (default cgminer behaviour) or submitting all of them (when you enable --submit-stale), this allows the pool to tell cgminer what it wants you to do. On pools that your stale count doesn't matter (like p2pool) there is a theoretically miniscule chance this share is worth submitting, and on merged mining pools, it might be okay to submit shares from a valid BTC block but not a valid NMC block. You can actually see this in action in this latest version with output that looks like this:

Code:
[2012-02-06 22:15:25] Stale share detected, submitting as pool requested
[2012-02-06 22:15:25] Rejected 00000000.302ced5f.c73e1884 GPU 2 thread 2 pool 0
As you can see, it was still rejected by p2pool here, but that is harmless.

- More work is "rolled" on longpoll. This should minimise the dip in hashrate across longpolls, and decrease the "pool is not providing work fast enough" warnings on pools that support n-rolltime. It will also increase the dreaded "efficiency" rating.

- GPU threads on the same GPU now start work staggered, with the first thread on each GPU having no delay. This means all GPUs should be busy ahead of extra threads on a GPU that is already busy. This should further decrease the dips across block changes/longpolls/network delays.

- Hopefully the "linked GPU" (eg 5970) scenario where a GPU would be apparently randomly turned off is fixed.

- When a GPU hangs now, the fan control should still keep trying to keep it at target temperature if it's hung running flat out. This should decrease crashes.

- The --donation feature is GONE.

- The wrong "thread" will not be reported if a GPU is disabled.

- Some networks can take extraordinarily long for the pool detection to work so the 15 second timeout has been increased to 60 seconds. This will help those who have had apparently everything set up fine but ended up with pool communication failure at startup.

- Enabling the -T text only option will guarantee that the formatted "curses" output will never occur. This makes debugging easier.

- Bitforce devices should actually work now.

- More information available (last share) in the changed RPC API.

---
Changelog:

2.2.3:
- Revert "Rewrite the convoluted get_work() function to be much simpler and roll
work as much as possible with each new work item." This seems to cause a race on
work in free_work(). Presumably other threads are still accessing the structure.

2.2.2:
- Provide support for the submitold extension on a per-pool basis based on the
value being detected in a longpoll.
- Don't send a ping to a dynamic device if it's not enabled as that will just
enable it for one pass and then disable it again.
- Rewrite the convoluted get_work() function to be much simpler and roll work as
much as possible with each new work item.
- Roll as much work as possible from the work returned from a longpoll.
- Rolling work on each loop through the mining thread serves no purpose.
- Allow to stage more than necessary work items if we're just rolling work.
- Replace divide_work with reuse_work function used twice.
- Give rolled work a new ID to make sure there is no confusion in the hashtable
lookups.
- Remove now-defunct hash_div variables.
- Remove unused get_dondata function.
- Silence ADL warnings.
- Silence unused parameter warnings.
- Stagger the restart of every next thread per device to keep devices busy ahead
of accessory threads per device.
- Deprecate the --donation feature. Needlessly complex, questionable usefulness,
depends on author's server and a central pool of some kind, and was not heavily
adopted.
- It's devices that report back now, not threads, update message.
- Continue auto-management of fan and engine speeds even if a device is disabled
for safety reasons.
- No need to check we're highest performance level when throttling GPU engine
speed.
- Abstract out tests for whether work has come from a block that has been seen
before and whether a string is from a previously seen block.
- Probe but don't set the timeout to 15 seconds as some networks take a long
time to timeout.
- Remove most compiler warnings from api.c
- Add last share's pool info in cgpu_info
- Allow the OpenCL platform ID to be chosen with --gpu-platform.
- Iterate over all platforms displaying their information and number of devices
when --ndevs is called.
- Deprecate main.c
- Some networks can take a long time to resolve so go back to 60 second timeouts
instead of 15.
- Only enable curses on failure if curses is desired.
- Fix warnings in bitforce.c
- Bugfix: Need to open BitForce tty for read-write
- Fix various build issues.
- Modularize code: main.c -> device-cpu + device-gpu
- Fix phatk kernel not working on non-bitalign capable devices (Nvidia, older
ATI).
- Update poclbm kernel for better performance on GCN and new SDKs with bitalign
support when not BFI INT patching. Update phatk kernel to work properly for non
BFI INT patched kernels, providing support for phatk to run on GCN and non-ATI
cards.
- Return last accepted share pool/time for devices
- Display accepted share pool/time for CPUs
- Bug intensity always shows GPU 0
- Update example web miner.php to use new API commands
full member
Activity: 373
Merit: 100
@kano: The first thing I did before posting was "ulimit -c unlimited; make clean; ./autogen.sh && ..." just to get a clean core dump.
Yep - sorry - but I thought I better mention the obvious just in case Smiley
... and mine hadn't yet crashed either - but the 725 comment also meant that was possibly the reason mine hadn't crashed.
My guess is your hash rate is a lot higher than mine? Or you were unlucky Tongue

The way my luck has been going in the last 25 years... Tongue
BTW, I only have ~55 MH/s. And I got the first instance of the crash on a pure-CPU machine where I was trying the new version out. That thing barely has 1.5 MH/s...
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Hmm... could be a race on the work item. Can you "git checkout a3e77937c8b8d924b2671aa4a77e9f13689ac64a", rebuild, and see if it goes away?

Running more than twice as long as before and no crash yet. I'll post again, should this post trigger another crash, but so far it looks good.


@kano: The first thing I did before posting was "ulimit -c unlimited; make clean; ./autogen.sh && ..." just to get a clean core dump.
Yep - sorry - but I thought I better mention the obvious just in case Smiley
... and mine hadn't yet crashed either - but the 725 comment also meant that was possibly the reason mine hadn't crashed.
My guess is your hash rate is a lot higher than mine? Or you were unlucky Tongue

Edit: yeah I'm running 2.2.3 now also
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hmm... could be a race on the work item. Can you "git checkout a3e77937c8b8d924b2671aa4a77e9f13689ac64a", rebuild, and see if it goes away?

Running more than twice as long as before and no crash yet. I'll post again, should this post trigger another crash, but so far it looks good.


@kano: The first thing I did before posting was "ulimit -c unlimited; make clean; ./autogen.sh && ..." just to get a clean core dump.
Quick bugfix then, and I'm going to release it as 2.2.3. Thanks.
full member
Activity: 373
Merit: 100
Hmm... could be a race on the work item. Can you "git checkout a3e77937c8b8d924b2671aa4a77e9f13689ac64a", rebuild, and see if it goes away?

Running more than twice as long as before and no crash yet. I'll post again, should this post trigger another crash, but so far it looks good.


@kano: The first thing I did before posting was "ulimit -c unlimited; make clean; ./autogen.sh && ..." just to get a clean core dump.
hero member
Activity: 518
Merit: 500
IMHO all of these strange cgminer issues are on Windblows only / mostly. I would avoid that platform if I were mining.

You are gamers so that is why you won't consider Linux. Try dual booting and cgminer works flawlessfly for me on Linux.

I think it should be like Xchat program : free for Linux and if you need support on Windows you have to pay.

Windows is just too much hassle for mining. Good luck !
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Sigh - after running for quite a while - even my lowly 725MH/s finally got the error (just now) ... wait for another update.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
A mining buddy Eliden got some weird problem with all versions of cgminer from 2.0.7 to 2.1.2

http://img841.imageshack.us/img841/6650/88077886.png this is the screenshot

The temps and the rpm of the fan disappearing on start of cgminer

Cgminer only reports what the ATI display library shows and does not show anything if it's not reporting results from a device. At the mercy of the ATI display library. If it stops reporting values there's nothing cgminer can do about it.
hero member
Activity: 686
Merit: 500
I haven't used it remote. I have one with a monitor and it is the same.
Jump to: