First off, this is going to sound extremely STUPID because I know neither how to code or the proper questions to ask.....lol
'Efficiency' (E)
Can this value be queried using RPC ? or does this value have to be calculated locally using 'Q' and 'A' (say, for a monitoring Script)....?
ie. I can retreive the ACCEPTED value per miner (A) value using ($value['Accepted'])......the REJECTED value per miner using ($value['Rejected'])
I have tried throwing in 'Efficiency' as a tag and can't seem to get a value per miner for it. A little help ?
Again, I apologize for soiling the sanctity of coding....and for being so stupid...lol
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 627. (Read 5806103 times)
February 29, 2012, 07:03:31 AM
February 29, 2012, 05:54:49 AM
And I've updated my git with the new code:
https://bitcointalksearch.org/topic/m.775068
https://bitcointalksearch.org/topic/m.775068
February 28, 2012, 09:47:06 PM
Kano & Conman,
I have my BFL single running on BAMT with cgminer but it would seem that the API call "devs" does not report back about the BFL single. Here is the output from the "devs" call.
...
So the devs call is missing all BFL info.
I have my BFL single running on BAMT with cgminer but it would seem that the API call "devs" does not report back about the BFL single. Here is the output from the "devs" call.
...
So the devs call is missing all BFL info.
Yeah, cgminer is missing all FPGA related API stuff
https://bitcointalksearch.org/topic/bounty-35-btc-integrate-support-for-other-devices-in-the-cgminer-api-66699
February 28, 2012, 12:59:14 PM
Kano & Conman,
I have my BFL single running on BAMT with cgminer but it would seem that the API call "devs" does not report back about the BFL single. Here is the output from the "devs" call.
So the devs call is missing all BFL info.
I have my BFL single running on BAMT with cgminer but it would seem that the API call "devs" does not report back about the BFL single. Here is the output from the "devs" call.
Code:
STATUS=S
,Code=9
,Msg=2 GPU(s)
,Description=cgminer 2.2.7
|GPU=0,Enabled=Y,Status=Alive,Temperature=73.50,Fan Speed=2355,Fan Percent=48,GPU Clock=895,Memory Clock=1000,GPU Voltage=1.100,GPU Activity=99,Powertune=0,MHS av=364.64,MHS 5s=368.09,Accepted=81,Rejected=0,Hardware Errors=0,Utility=4.87,Intensity=9,Last Share Pool=0,Last Share Time=1330436872
|GPU=1,Enabled=Y,Status=Alive,Temperature=73.50,Fan Speed=1892,Fan Percent=42,GPU Clock=895,Memory Clock=1000,GPU Voltage=1.100,GPU Activity=99,Powertune=0,MHS av=363.33,MHS 5s=367.82,Accepted=73,Rejected=0,Hardware Errors=0,Utility=4.38,Intensity=9,Last Share Pool=0,Last Share Time=1330436857
So the devs call is missing all BFL info.
Yeah, cgminer is missing all FPGA related API stuff
February 28, 2012, 12:23:28 PM
Thanks tenzor.
Yeah. I am looking forward to these tasty results !
February 28, 2012, 10:15:13 AM
Thanks tenzor.
February 28, 2012, 09:17:33 AM
The ADL library isn't just randomly dying here. It happens at 200k accepted shares (this was easy for me to recognize since I have a 32 GH/s mining farm). I'm just pointing out my observation so hopefully it gets fixed.
This time. Has it died @ 200K previously too? Does it die at 200K each time? If it is a repeatable and verifiable bug that is more useful than just it dying once @ 200K (which may not have any significance).
Hrm, I looked back over my 24 rigs and I'm afraid I was wrong. It doesn't always happen 200k but the bug is occurring on all of them within hours of each other after running for about a week straight with 4 GPU's per rig. It will take some time but i'll try to identify the exact trigger.
February 28, 2012, 08:56:32 AM
Kano & Conman,
I have my BFL single running on BAMT with cgminer but it would seem that the API call "devs" does not report back about the BFL single. Here is the output from the "devs" call.
So the devs call is missing all BFL info.
I have my BFL single running on BAMT with cgminer but it would seem that the API call "devs" does not report back about the BFL single. Here is the output from the "devs" call.
Code:
STATUS=S
,Code=9
,Msg=2 GPU(s)
,Description=cgminer 2.2.7
|GPU=0,Enabled=Y,Status=Alive,Temperature=73.50,Fan Speed=2355,Fan Percent=48,GPU Clock=895,Memory Clock=1000,GPU Voltage=1.100,GPU Activity=99,Powertune=0,MHS av=364.64,MHS 5s=368.09,Accepted=81,Rejected=0,Hardware Errors=0,Utility=4.87,Intensity=9,Last Share Pool=0,Last Share Time=1330436872
|GPU=1,Enabled=Y,Status=Alive,Temperature=73.50,Fan Speed=1892,Fan Percent=42,GPU Clock=895,Memory Clock=1000,GPU Voltage=1.100,GPU Activity=99,Powertune=0,MHS av=363.33,MHS 5s=367.82,Accepted=73,Rejected=0,Hardware Errors=0,Utility=4.38,Intensity=9,Last Share Pool=0,Last Share Time=1330436857
So the devs call is missing all BFL info.
February 28, 2012, 08:33:24 AM
The ADL library isn't just randomly dying here. It happens at 200k accepted shares (this was easy for me to recognize since I have a 32 GH/s mining farm). I'm just pointing out my observation so hopefully it gets fixed.
This time. Has it died @ 200K previously too? Does it die at 200K each time? If it is a repeatable and verifiable bug that is more useful than just it dying once @ 200K (which may not have any significance).
February 28, 2012, 08:20:12 AM
Found a small bug, when cgminer passes 200k accepted shares in Windows 7 the GPU temp and fan speed columns go completely blank and are also unable to be accessed via the API (which I noticed vis ANUBIS).
Ha, +1, I also noticed this, didn't link it with the 200k shares though... ;-)
Not really helpful, but you can check the API config command:
It will say (ADL=Y,ADL in use=N) if all cards are showing blank for the GPU/Fan/Temp values.
If any cards are still working (unexpected) then it will still say (ADL in use=Y)
Also, if you are using ANUBIS - does it have a log of the stats over time?
You should be able to tell exactly what and where if it logs all the stats (I don't know how much it logs)
ANUBIS doesn't log anything, and all the cards are still working and hashing away. It's just a bug that affects the display of those values and makes those specific values unretrievable via the API.
The ADL library that AMD wrote and cgminer uses is what controls GPU/Fan/Temp.
The ADL library is known to just give up and die sometimes.
cgminer keeps going but can no longer access that information ... that's why it's blank (like if you forget "export DISPLAY=:0" in linux)
You will find that anything in cgminer that requires ADL now no longer works.
That really means: if cgminer was given --auto-gpu or --auto-fan (or both) it is also time to stop and restart cgminer since it is no longer monitoring your fan and/or gpu.
The ADL library isn't just randomly dying here. It happens at 200k accepted shares (this was easy for me to recognize since I have a 32 GH/s mining farm). I'm just pointing out my observation so hopefully it gets fixed.
February 28, 2012, 06:58:51 AM
Found a small bug, when cgminer passes 200k accepted shares in Windows 7 the GPU temp and fan speed columns go completely blank and are also unable to be accessed via the API (which I noticed vis ANUBIS).
Ha, +1, I also noticed this, didn't link it with the 200k shares though... ;-)
Not really helpful, but you can check the API config command:
It will say (ADL=Y,ADL in use=N) if all cards are showing blank for the GPU/Fan/Temp values.
If any cards are still working (unexpected) then it will still say (ADL in use=Y)
Also, if you are using ANUBIS - does it have a log of the stats over time?
You should be able to tell exactly what and where if it logs all the stats (I don't know how much it logs)
ANUBIS doesn't log anything, and all the cards are still working and hashing away. It's just a bug that affects the display of those values and makes those specific values unretrievable via the API.
The ADL library that AMD wrote and cgminer uses is what controls GPU/Fan/Temp.
The ADL library is known to just give up and die sometimes.
cgminer keeps going but can no longer access that information ... that's why it's blank (like if you forget "export DISPLAY=:0" in linux)
You will find that anything in cgminer that requires ADL now no longer works.
That really means: if cgminer was given --auto-gpu or --auto-fan (or both) it is also time to stop and restart cgminer since it is no longer monitoring your fan and/or gpu.
February 28, 2012, 06:44:26 AM
Found a small bug, when cgminer passes 200k accepted shares in Windows 7 the GPU temp and fan speed columns go completely blank and are also unable to be accessed via the API (which I noticed vis ANUBIS).
Ha, +1, I also noticed this, didn't link it with the 200k shares though... ;-)
Not really helpful, but you can check the API config command:
It will say (ADL=Y,ADL in use=N) if all cards are showing blank for the GPU/Fan/Temp values.
If any cards are still working (unexpected) then it will still say (ADL in use=Y)
Also, if you are using ANUBIS - does it have a log of the stats over time?
You should be able to tell exactly what and where if it logs all the stats (I don't know how much it logs)
ANUBIS doesn't log anything, and all the cards are still working and hashing away. It's just a bug that affects the display of those values and makes those specific values unretrievable via the API.
February 28, 2012, 06:13:12 AM
I would love to see an expanded version of this that goes down to 100 (or lower) memclock using latest version of cgminer, latest drivers, and SDK 2.1.
Here is some tests
Do you have a 5870 to test with?
@tenzor Were you running this on linux? And are you willing to share the script you used to generate these results?
Here is it
http://pastebin.com/gpFDyXef
requires screen
Copy it into cgminer's directory. Make sure you change values on config section. Results will appear in directory defined in "results" variable. Make sure it writable.
Cgminer always include default config, so rename it or remove. Config to run cgminer in "cgminer_config_path" var. Here is my config for device #0 (test0.conf)
Code:
{
"pools" : [
{
"url" : "http://pit.deepbit.net:8332",
"user" : "XXX",
"pass" : "XXX"
}
],
"intensity" : "9",
"gpu-engine" : "0-930",
"gpu-fan" : "0-85",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"auto-fan" : true,
"expiry" : "120",
"gpu-threads" : "2",
"log" : "5",
"no-restart" : true,
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"temp-hysteresis" : "3",
"api-listen" : true,
"donation" : "0.00",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}
sometimes X server hangs, in this case script will create file "reboot_required" in current dir, so you could use ither script to reboot automatically
First parameter is device number to run tests on. It 0 by default.
Also run another instances of cgminer befor running this script, because it will overwrite another GPU clock values.
Sometimes identical GPUs with same clocks produce different MH/s, so be careful comparing results from different GPU.
Results will appear in subfolders in json files. I wrote php script that draw graphs. http://dl.dropbox.com/u/569082/cgminer-tester.zip Put it into webserver webroot somewere, tests put in tests dir inside.
Currently I am testing 5850 all kernels 150-300 memclock. I expect results will be ready after 3 days
February 28, 2012, 04:58:59 AM
Found a small bug, when cgminer passes 200k accepted shares in Windows 7 the GPU temp and fan speed columns go completely blank and are also unable to be accessed via the API (which I noticed vis ANUBIS).
Ha, +1, I also noticed this, didn't link it with the 200k shares though... ;-)
Not really helpful, but you can check the API config command:
It will say (ADL=Y,ADL in use=N) if all cards are showing blank for the GPU/Fan/Temp values.
If any cards are still working (unexpected) then it will still say (ADL in use=Y)
Also, if you are using ANUBIS - does it have a log of the stats over time?
You should be able to tell exactly what and where if it logs all the stats (I don't know how much it logs)
February 28, 2012, 04:24:00 AM
Found a small bug, when cgminer passes 200k accepted shares in Windows 7 the GPU temp and fan speed columns go completely blank and are also unable to be accessed via the API (which I noticed vis ANUBIS).
Ha, +1, I also noticed this, didn't link it with the 200k shares though... ;-)
February 28, 2012, 03:34:24 AM
Found a small bug, when cgminer passes 200k accepted shares in Windows 7 the GPU temp and fan speed columns go completely blank and are also unable to be accessed via the API (which I noticed vis ANUBIS).
February 28, 2012, 01:28:32 AM
I'll be taking an extended break from coding on cgminer shortly since most things are stable at the moment for my sanity.
This begins now and I have disabled all notifications from the forum and github so do not be surprised when I don't respond for many days. Email me if it's urgent but try to use the forums please as there are heaps of helpful people here. Thanks everyone for your understanding.Take your time, enjoy your break and come back, when the fire is burning again
.Dia
February 27, 2012, 09:22:50 PM
Some of my 5970's are not accepting any commands from cgminer. I had to use afterburner on about half my rigs. This is to be expected?
What do you mean not accepting commands?
You can't change any parameter to any value? If so that is something new but likely you mean "I am trying to raise voltage or select a clock way outside what bios allows" right?
cgminer can't FORCE the card to do anything (not even return to stock clocks). All it can do is ask.
cgminer: "card #1 please raise clock to 800 Mhz"
card #1: "request recevied"
card #1 (internally): fuck off cgminer I am tired.
If I put in 725 engine in cgminer it displays back
Engine Clock: 157 Mhz
Memory Clock: 150 Mhz
Vddc:0.950 V
February 27, 2012, 07:46:56 PM
Edit 3: Well, I took one idea from your code and created this one .
.Code:
if((V[7].x == 0x136032edU) + (V[7].y == 0x136032edU))
output[FOUND] = output[NFLAG & nonce.x] = (V[7].x == 0x136032edU) ? nonce.x : nonce.y;
Nice!
Here is alternative solution that should have the same performance as yours (same min & max exec time, same alu count, etc):
Code:
V[7] -= 0x136032EDu;
uint result = V[7].x ? 0u:nonce.x;
result = V[7].y ? result:nonce.y;
if (result)
output[FOUND] = output[NFLAG & result] = result;
Would be nice to see if there's any significant difference between both on real GCN hardware!
---------------------------------
EDIT: Another similar performance solution:
Code:
bool result = V[7].x == 0x136032EDu ? true:false;
result = V[7].y == 0x136032EDu ? true:result;
if (result)
output[FOUND] = output[NFLAG & nonce.x] = (V[7].x == 0x136032EDu) ? nonce.x : nonce.y;
February 27, 2012, 06:09:24 PM
I'll be taking an extended break from coding on cgminer shortly since most things are stable at the moment for my sanity.
This begins now and I have disabled all notifications from the forum and github so do not be surprised when I don't respond for many days. Email me if it's urgent but try to use the forums please as there are heaps of helpful people here. Thanks everyone for your understanding.Jump to: