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

https://bitcointalksearch.org/topic/bash-scripts-for-rpc-interface-to-cgminer-suggestions-welcome-66779

An example would be line 60, however all it does is pop up a non modal window.  You can modify it to email you with

echo "$node gpu$i reports $STATUS" | mail -s "Device Failure" [email protected]

or whatever else you want.

Has anyone written a script that checks if any GPUs are DEAD/OFF via the API?  I'd like to create something that checks periodically and restarts cgminer if that happens (since a restart usually fixes the issue).  If someone already has a simple script to talk to cgminer, I'd love to use it as a starting point.

That is weird.  Makes me think something larger is going on with your system.  AMD drivers can be weird sometimes but I don't think any GPU should show "disabled" while under load.

You may want to read my code instead, as python is much more readable than java and you have everything I needed on mpbm in one single source.

https://github.com/nelisky/Modular-Python-Bitcoin-Miner/blob/ztex/worker/fpgamining/ztexdev.py

I will try to find you on irc once I get some work things out of the way.

I took that to mean that the MH/s gets slower on the GPU with 'd' but you could be right.  Regardless, the advice from DAT after your last post (and just before this post) is exactly what Windows miners need.  (and there's still no thumbs up emoticon)

The #0 GPU is rarely the one driving the display.  It is up to windows crazy device number scheme.  Only only Windows rig (3x watercooled 5970s) the "display GPU" was #4.  When one 5970s died and I RMAed it (4 GPUs installed) he "display GPU" become #1.  When I got the RMA back (6 GPUs) the "display GPU" after a reinstall become #2.  So it varied and it was never #0 in this limited sample set.

So windows users should identify the display GPU.  If you have multiple physical displays as long as they are all connected to a single card one GPU will handle them all even on dual GPU cards like 5970s.  If you have multiple displays connected to multiple cards well change that it is sub optimal.

To identify the display GPU:
1) stop mining
2) open GPU-Z sensor tab (be sure record data when not shown is checked), AB, or CCC.
3) All GPU should be ~0% GPU load.
4) Do something which requires the GPU acceleration flash accelerated video, (although you should turn it back off when mining), Afterburner test tool, play some 3D game (in windowed mode would be best).
5) Look which GPU load increases.  Record this GPU number.

Now you think you might be done but you aren't (because windows & ADL library used by cgminer order cards differently sometimes).
Leave whatever tool you are using open.
5) Start cgminer  (you can use low intensity and stock clocks for stability)
6) You should see all GPU go to 99% load
7) Disable each GPU one at a time until you find the one which causes load on the GPU identified in #4 (in GPU-Z / AB) to go to zero.
Wait a few seconds between each GPU disable as sometimes it take a couple seconds for the tools to show a drop in GPU load.

That is the GPU in cgminer that is driving the display.  Yes windows is asinine.  You likely want to write it down.

On edit: clarified a few steps.

Actually he said:
Which sounds like it could be the wrong GPU is 'd'
i.e. as you increase the intensity on the display GPU it should of course get less responsive

Being smart without actually being smart is awesome...  I forgot about the gpu ordering issue, so basically each of these needs tried if there's not an easier way to work out which is the display (since board order and driver order don't match and even differ between OS):Good thing it isn't dual-GPU, that would make it a real PITA.

EDIT: Even assuming there's no good way to determine which is which short of such testing, wouldn't display performance have been noticeably worse in the previously attemptedif it wasn't making the display GPU dynamic?

... and on a different subject ... ZTEX

I wasted an hour or so on it so far and worked out what appears to be the commands
(and changed all the cgminer code that needs changing and created a template ztex.c)

So if anyone has one it would be good if they could drop by #cgminer on FreeNode and I'll ask you to run a few commands so I can work out what the commands really are.

I asked the ZTEX people and got 2 useless replies in one email:
1) Read the java code, the mining commands for the bitstreams aren't documented
(yeah I had already done that that's why I asked to confirm what I had worked out)
2) "You cannot do this within a day."
lol - well I've only spend a couple of hours on it so far ...
(and then decided after than comment ... stuff it I'll do it tomorrow ... or whenever ...)

Actually - that's the smartest comment yet on the subject ...
Because it could be that GPU0 isn't the display ...
i.e. you'd have to make sure which GPU's are the display and set it lower.
Then I'm almost certain the rest could be higher ...

Edit: though I should point out ... The 7970 is a single GPU

Isn't the 7970 a dual-gpu card?  Maybe having the display on the first card means both of those GPUs affect Windows because of this?  IOW, instead ofmaybeor with 1/3rd the 9's if you only have 2 cards.

Well I have actually discussed recently what the intensity actually does.

It simply divides up the work based on: a higher intensity means longer work for the GPU to do non-stop.

... now where was that post ...
https://bitcointalksearch.org/topic/m.771425

So each step up in intensity is making the GPU process twice as long between very short 'rests'
(though they are only cgminer GPU rests while the CPU readies the next GPU request, not OS rests)

Heh I only wrote the API (and a few patches here and there)

But yeah I didn't see any comments about using multiple intensities - that's why I said that.

Have you tried anything like 7,X,X for any of X=8, 9, 10 or 11?
(since d has other effects also)

That's very strange that the other cards doing nothing in the system except mining would require a setting of 7

Is there anything unusual about your setup?
(obviously not this: but what I mean would be like having 1 display on each card or some other unusual setup)

Edit: I'll also add that a few 100 share test is pretty small ... and could be unreliable.
Give it an hour at least to be sure of the value.

Yep it is known.
It "appears" to be the ATI ADL library gives up after a long time so it's been resigned to the can't fix basket.
Of course it could be some obscure hard to find cgminer bug, but if it was and since it takes such a long time to happen, it's not likely to be found through any testing looking for the cause of it.

ckvolias:

forgive me if this has already been reported but I have been super busy lately and not able to follow the thread

using latest cgminer 2.3.1-2 win7 64x

after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue

screenshot....

Not sure if this has been covered in previous posts, but MAN, 227 pages of posts to read, and searches don't turn up anything, so what the hey.

Just went from 2.2.6 to 2.3.1 and went from mid 500s on each 7970 and dropped to... 25.

At first I assumed it was to do with the new GPU interval setting it was annoying me about, but after wasting an hour playing with that to no avail I started looking for other causes. The first thing I noticed was it seemed to be taking 99% of each GPU to turn up 25 Mhash/sec. I tried phatk and went to 150 per GPU. POCLBM came in first with 552 at 12 intensity (I don't want the fans offensively loud).

So, not sure what's changed. I have not tried other kernels in the past so I can't tell if phatk has always sucked or, like Diablo, has just started sucking.

Anyway, I hope this helps anyone else with a 7970 confused by a sudden performance hit after an update!

outsidefactor

The point he has already stated is that if you are using more than one GPU in your computer - you are wasting the others.

The stability issue is the display GPU.
Set the other GPU's to higher intensity.

You are reducing the performance of the other GPU's by using the same settings on all of them that you have determined are needed to keep the display GPU stable.

Why would I buy 7970s just to test out your flawed theory?

Try turning the SINGLE GPU connected to a display to dynamic as suggested in the README and you can increase the intensity to where it should be without issue.   As far as 5 threads being optimal?  LOLZ. 

They are all different between SDK packs or Catalyst versions. As for "better", that's more difficult to answer...

Awhile ago I checked some of them:

Thank a lot, I'll use your experience at once  :-) Workss great (Win 7, 1170/1350 -I 7).