-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 10:47:15 AM |
|
No idea then
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
BCMan
|
|
January 29, 2012, 10:53:11 AM |
|
No idea then I guess I'll just switch to 2.2.0 and 2.5 sdk with XP, when I'm not around/night. Because gpu clocks/temp autocontrol is essential for me.
|
|
|
|
BCMan
|
|
January 29, 2012, 11:03:39 AM |
|
Err, hardware monitoring in 2.2.0 isn't working even with 2.5 sdk. Just checked with XP.
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 11:07:43 AM |
|
Err, hardware monitoring in 2.2.0 isn't working even with 2.5 sdk. Just checked with XP.
Huh wot? Do you get any useful error messages when you start it with -D -T --verbose (as well as your usual parameters) ?
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
BCMan
|
|
January 29, 2012, 11:18:51 AM |
|
Thats what I have with these parameters.
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 11:28:42 AM |
|
Well that's interesting, you're getting the "adl found more devices than opencl" problem. How many GPUs do you have? Just one? Did you change anything in your driver setup at all? What output do you get if you use this http://ck.kolivas.org/apps/cgminer/temp/cgdebug.exe in the cgminer directory the same way you would use cgminer.exe and start with -T ? It will give more information about the devices with lines that look like this: [2012-01-22 17:31:58] lpAdapterID 20016752 iBusNumber 1 iDeviceNumber 0 iFunctionNumber 0 iVendorID 4098 strAdapterName AMD Radeon HD 6900 Series strDisplayName :0.0 lpInfo.strUDID 256:26393:4098:12583:5762
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
BCMan
|
|
January 29, 2012, 11:39:21 AM |
|
Well that's interesting, you're getting the "adl found more devices than opencl" problem. How many GPUs do you have? Just one? Did you change anything in your driver setup at all? What output do you get if you use this http://ck.kolivas.org/apps/cgminer/temp/cgdebug.exe in the cgminer directory the same way you would use cgminer.exe and start with -T ? It will give more information about the devices with lines that look like this: [2012-01-22 17:31:58] lpAdapterID 20016752 iBusNumber 1 iDeviceNumber 0 iFunctionNumber 0 iVendorID 4098 strAdapterName AMD Radeon HD 6900 Series strDisplayName :0.0 lpInfo.strUDID 256:26393:4098:12583:5762
2 gpus. 5770 and internal 4250 (set as primary). And no problems with this setup and v2.1.2. Driver installed in XP is 11.12 and 2.5 sdk, nothing else.
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 11:46:14 AM |
|
2 gpus. 5770 and internal 4250 (set as primary). And no problems with this setup and v2.1.2. Driver installed in XP is 11.12 and 2.5 sdk, nothing else. Okay so what's happening here is that the ATI display library is finding both GPUs but opencl is only finding one GPU... Now look at this post: I just had an annoying multi-hour debugging session, trying to figure out why cgminer thinks there's only one GPU in my (Debian Testing) system. $ aticonfig --list-ad * 0. 06:00.0 ATI Radeon HD 5800 Series 1. 07:00.0 ATI Radeon HD 5800 Series 2. 08:00.0 ATI Radeon HD 5450 Turns out that AMD is being stupid. Again. OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10) (don't remember where I downloaded it from): library works. OpenCL 1.2 AMD-APP (831.4) (available from http://developer.amd.com/sdks/AMDAPPSDK/Pages/default.aspx ) does NOT see more than one GPU. You can extract the build number etc. from the library with $ strings -a /pth/to/the/library.so | grep "^OpenCL.*AMD-APP" Yes I realise that's a linux report but it could be related. Next, download this bleeding edge build http://ck.kolivas.org/apps/cgminer/temp/cgminer.exeand try this command: cgminer.exe --ndevs
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
BCMan
|
|
January 29, 2012, 12:03:01 PM |
|
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 12:09:17 PM |
|
Question: Can your other device (4250) mine?
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 12:17:19 PM |
|
Question: Can your other device (4250) mine?
I guess you don't need to answer that, I checked. So this is the problem. One device that can mine and one that can't. There's already nothing to correlate openCL devices with devices that appear in the ATI display library apart from "how many there are" and "in what order they appear". Put a non-opencl device in there (like the 4250) and it's a mess... GAH. Nothing short of some kind of massive whitelist will fix this. If it worked previously you were lucky it wasn't monitoring the 1st card instead. EDIT: This recurring problem of having no way of correlating opencl and ATI devices is getting seriously long in the tooth. Can we get a re-post of those facepalms please?
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
BCMan
|
|
January 29, 2012, 12:28:41 PM |
|
Question: Can your other device (4250) mine?
I guess you don't need to answer that, I checked. So this is the problem. One device that can mine and one that can't. There's already nothing to correlate openCL devices with devices that appear in the ATI display library apart from "how many there are" and "in what order they appear". Put a non-opencl device in there (like the 4250) and it's a mess... GAH. Nothing short of some kind of massive whitelist will fix this. If it worked previously you were lucky it wasn't monitoring the 1st card instead. EDIT: This recurring problem of having no way of correlating opencl and ATI devices is getting seriously long in the tooth. Can we get a re-post of those facepalms please? But why 2.1.2 don't have such issue then? If it worked previously you were lucky it wasn't monitoring the 1st card instead. 2.1.2 hardware monitoring is working, right now, after I tested 2.2.0, without problems. So maybe just a bug in 2.2.0?
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 12:33:57 PM |
|
Question: Can your other device (4250) mine?
I guess you don't need to answer that, I checked. So this is the problem. One device that can mine and one that can't. There's already nothing to correlate openCL devices with devices that appear in the ATI display library apart from "how many there are" and "in what order they appear". Put a non-opencl device in there (like the 4250) and it's a mess... GAH. Nothing short of some kind of massive whitelist will fix this. If it worked previously you were lucky it wasn't monitoring the 1st card instead. EDIT: This recurring problem of having no way of correlating opencl and ATI devices is getting seriously long in the tooth. Can we get a re-post of those facepalms please? But why 2.1.2 don't have such issue then? It stopped after it found the first device. 2.2.0 finds all the devices and then reorders them correctly according to their PCI bus position. As I said you were lucky it wasn't giving you temps and fanspeed for the 4250 instead because it happened to put the 4250 second in the driver order even though you physically have it first in the slot - You can see it has a higher adapterindex in that list despite having a lower busnumber. As for a solution to this problem that is correct as opposed to "lucky"... I'm thinking, but I have no ideas apart from explicitly telling cgminer at this stage.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
The00Dustin
|
|
January 29, 2012, 12:35:57 PM |
|
Hmm thanks for the link, but that doesn't even appear in my code anywhere. Presumably that's ufa they're talking about. Meanwhile cgminer mines fine on my nvidia laptop so I guess I'm a bit late to be responding now regardless, but yes that code was for (and posted by) ufasoft. I quoted what I did because the person who they were responding to said cgminer stopped working in their environment with the same nvidia driver version leading me to believe it could possibly be a similar cause, so I thought I'd bring it up just in case.
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 12:43:13 PM |
|
But why 2.1.2 don't have such issue then?
It stopped after it found the first device. 2.2.0 finds all the devices and then reorders them correctly according to their PCI bus position. As I said you were lucky it wasn't giving you temps and fanspeed for the 4250 instead because it happened to put the 4250 second in the driver order even though you physically have it first in the slot - You can see it has a higher adapterindex in that list despite having a lower busnumber. As for a solution to this problem that is correct as opposed to "lucky"... I'm thinking, but I have no ideas apart from explicitly telling cgminer at this stage. This won't be the correct fix, but this exe should work around the problem for you for now (put into 2.2.0 directory): http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
jake262144
|
|
January 29, 2012, 12:47:14 PM Last edit: January 29, 2012, 09:59:02 PM by jake262144 |
|
...Can we get a re-post of those facepalms please?
Ask and you shall receive. root@haerdalis::/home/jake# /opt/bcm/cgminer-testing/cgminer [2012-01-29 13:48:56] Started cgminer 2.2.0 WARNING: All config files need .conf: /etc/modprobe.d/00local, it will be ignored in a future release. FATAL: Module nvidia not found. *** glibc detected *** /opt/bcm/cgminer-testing: realloc(): invalid old size: 0xbfa81ce8 *** ======= Backtrace: ========= /lib/i686/cmov/libc.so.6(+0x6b381)[0xb75b7381] /lib/i686/cmov/libc.so.6(+0x70aad)[0xb75bcaad] /lib/i686/cmov/libc.so.6(realloc+0xdd)[0xb75bcd8d] /opt/bcm/cgminer-testing[0x80590ad] /usr/lib/libcurl-gnutls.so.4(Curl_client_write+0x198)[0xb770e6e8] /usr/lib/libcurl-gnutls.so.4(Curl_readwrite+0x12c0)[0xb7721b00] /usr/lib/libcurl-gnutls.so.4(+0x29f1b)[0xb7721f1b] /usr/lib/libcurl-gnutls.so.4(curl_easy_perform+0x43)[0xb7722d93] /opt/bcm/cgminer-testing[0x805a1db] /opt/bcm/cgminer-testing[0x80509d2] /opt/bcm/cgminer-testing[0x80566a8] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb7562ca6] /opt/bcm/cgminer-testing[0x804ad01] ======= Memory map: ======== ...
Latest git tends to die a miserable death, Con. The previous build i reported testing some 12 hours ago works just fine.
|
|
|
|
BCMan
|
|
January 29, 2012, 12:54:35 PM |
|
But why 2.1.2 don't have such issue then?
It stopped after it found the first device. 2.2.0 finds all the devices and then reorders them correctly according to their PCI bus position. As I said you were lucky it wasn't giving you temps and fanspeed for the 4250 instead because it happened to put the 4250 second in the driver order even though you physically have it first in the slot - You can see it has a higher adapterindex in that list despite having a lower busnumber. As for a solution to this problem that is correct as opposed to "lucky"... I'm thinking, but I have no ideas apart from explicitly telling cgminer at this stage. This won't be the correct fix, but this exe should work around the problem for you for now (put into 2.2.0 directory): http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe Yeah, it's working, even with 2.1 sdk. Thanks!
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 12:58:52 PM |
|
Latest git tends to die a miserable death, Con. The previous build i reported testing some 12 hours ago works just fine.
Has been fixed. Dodgy cleanups.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
BCMan
|
|
January 29, 2012, 01:20:09 PM |
|
Do I need to enable engine clock autotune for "temp-cutoff" activation? Or it's active by default?
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4228
Merit: 1644
Ruu \o/
|
|
January 29, 2012, 01:23:51 PM |
|
Do I need to enable engine clock autotune for "temp-cutoff" activation? Or it's active by default?
You need to enable --auto-gpu .However if you dont give it a range for engine clock speeds, it won't adjust any clock speeds, but it will still cut off the device if it hits the --temp-cutoff threshold.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
|