When using the load balance feature between 2 pools, I always have more accepted shares on pool 0 than pool 1. If I switch the pools on my .conf file I get the same result. Pool 0 always has a considerably higher amount of accepted shares than pool 1.
I have noticed a similar behavior too, but with me pool 3 gets almost all of the shares and pools 0, 1 and 2 get starved. Sam This is simply that one pool has rolltime and the others do not. It's such an efficient option that it's really a waste of resources to not use it on the one pool since the others have not moved out of the dark ages. But I guess I could add more black magic to cope with that.... |
|
|
|
If you're on linux, it really is very little effort to build it yourself. Don't be afraid. Long term you're much better off.
Build what part? The driver, cgminer or...? cgminer You can only be getting that error if you're downloading something that needs a library that isn't on your machine when you build it, so I assume you're download my x86_64 built binary. |
|
|
|
Honestly I dunno wtf is wrong with your setup. The opencl library is required and unless you fix the way it's installed on your machine, then you have to compile it yourself.
I don't know, I used to have the driver and SDK 2.5 installed separately, but I don't remember how I did it. That's how I had originally gotten my phatk kernel that stopped working after cgminer 2.6. Now I just have the 12.1 driver installed and whichever SDK that comes with (2.6 I assume). Any attempts to install the SDK separately are met with segfaults. If you're on linux, it really is very little effort to build it yourself. Don't be afraid. Long term you're much better off. |
|
|
|
New version - 2.6.5, 15th August 2012
Damn, still requires that random file. Back to 2.6.2. Honestly I dunno wtf is wrong with your setup. The opencl library is required and unless you fix the way it's installed on your machine, then you have to compile it yourself. |
|
|
|
|
New version - 2.6.5, 15th August 2012
Bugfixes yay
Human readable changelog
Found the longstanding problem with dynamic mode not really working on windows - the windows timer resolution is only 15ms and we're trying to sample much smaller than that. This was leading to the time taken to do GPU work appearing as zero for many samples. I used oversampling of results to find a mean time.
gpu-memdiff should now take effect when you change gpu engine clock from the menu as well
Hopefully the ADL gpu-map feature should work now when you have more adl devices than opencl (more ATI cards that dont support opencl).
More tweaks to the queueing mechanism to increase efficiency and keep minirigs fully work laden.
failover-only is available via the RPC API now.
More tweaks to bitforce devices to decrease comms errors.
Fixes to writing json config files.
Updated miner.php
Full changelog
- Don't try to get bitforce temperature if we're polling for a result to
minimise the chance of interleaved responses.
- Set memory clock based on memdiff if present from with engine changes,
allowing it to parallel manual changes from the menu as well.
- Increase the timeout on bitforce as per Paul Sheppard's suggestion to account
for throttling + work time + excess.
- Fix ADL gpu-map not working when there are more ADL devices than openCL.
Initial patch supplied by Nite69. Modified to suit.
- Windows' timer resolution is limited to 15ms accuracy. This was breaking
dynamic intensity since it tries to measure below this. Since we are repeatedly
sampling similar timeframes, we can average the gpu_us result over 5 different
values to get very fine precision.
- Fix harmless unused warnings in scrypt.h.
- API allow display/change failover-only setting
- Check we are not lagging as well as there is enough work in getwork.
- Minimise locking and unlocking when getting counts by reusing shared mutex
lock functions.
- Avoid getting more work if by the time the getwork thread is spawned we find
ourselves with enough work.
- The bitforce buffer is cleared and hw error count incremented on return from a
failed send_work already so no need to do it within the send_work function.
- miner.php allow a custom page section to select all fields with '*' - e.g. to
create a STATS section on a custom page
- Escape " and \ when writing json config file
- miner.php optional single rig totals (on by default)
|
|
|
|
A bit later, gigavps found that 2.3f would sometimes just exit with no clear indication of why. He was desperate for a fix, and I believe contacted you guys, posted on the cgminer forum, etc. When no solution was forthcoming, he asked me if I could hack mother to detect that it had exited and start it back up. So I did.
Anyway I instrumented the newer cgminer restart problem in bamt and it is indeed in the /opt/bamt/mother monitoring file. The perl parsing of ps axu output fails to detect cgminer is there and it then calls /etc/init.d/mine restart . So it is in fact bamt that is restarting cgminer, and if I edit the mother script to parse the output of ps axu differently, it does NOT continually restart cgminer. Alas I don't really know perl, but it does seem to need fixing. If you copy this file on top of mother in /opt/bamt it shouldn't restart on you (note this is not the correct fix and will probably not restart cgminer should it actually really crash): http://ck.kolivas.org/apps/cgminer/temp/motherSo what would be best thing to do then, use ckolivas's fix OR don't apply BAMT fix 20 in the first place? fix 20 is what causes this problem in the first place. It's mean to be a watchdog for when cgminer fails but on cgminer 2.6+ it actually kills cgminer instead. If you want to use the latest cgminer, you either don't apply fix 20, or use my temporary fix above if you've already applied it. |
|
|
|
7970s only support memory 150 lower than engine speed without special tools that have access to unofficial overclocking (and cgminer is not one of those special tools).
I've always kinda wondered why AB can set my mem speed down to 300, but CGMiner can't. Will this be added in the future? No. cgminer uses the ATI Display Library to do all its manipulations. As you'd imagine, they're all "official" overclocking. Stuff that has unofficial modes pokes into the card in ways that AMD gives no data on, and only works on windows. |
|
|
|
Working great, 7970 with flashed Ghz edition vbios at 1220/700, Windows 8, on air cooling (fan @ 100%). 700+Mh/s. Love it. Going to watercool to get to 800+ this week.
Does the Ghz edition bios let you pass the 150 mhz max engine memory clock diff? Well, I'm not really sure about that - my card seems to report that it's still clocked at 1500Mhz no matter what I set the mem clocks to or what software I use (CCC, Afterburner, Trixx). Trixx seems to think the settings are working, but I'm skeptical. So, my quoted 700Mhz memory clock is what I set it to, but not necessarily what it is running at... If anyone knows of a way to unlock this Diamond 7970 a little further, I'd appreciate any advice. Especially voltage-wise since I plan to watercool soon and I don't think my VCC settings are taking (according to GPU-Z). It's a pretty cheap card - $399 at newegg after rebate. Check within cgminer while it's running. It tells you the real "current" settings. It's also why there's a small delay after you try to manually set a value from the menu it will report back the detected settings. 7970s only support memory 150 lower than engine speed without special tools that have access to unofficial overclocking (and cgminer is not one of those special tools). |
|
|
|
cgminer can't adjust 7970 voltages
5970 Must be reading asleep. Carry on. |
|
|
|
|
cgminer can't adjust 7970 voltages
|
|
|
|
Any thought on introducing DGM to deepbit?
Why fix what ain't broke? because it is broken, deepbit miners have to pay a "hopper" tax currently That doesn't seem to dissuade 3.5TH of miners from mining there. What this says about the miners is up for debate by the psychologists. Hoppers win, regular miners mine like worker ants blissfully unaware and happy. Seems like a good symbiotic relationship to me... Somehow I can't see it lasting though <_< |
|
|
|
FOR SCRYPT MINING:
I thought I should pop in here and comment.....
CGMiner 2.6.4 is ROCK SOLID. No Hicupps, No Crashes...nothing.
I am currently using it on all 3 recent generations of ATI Cards (5/6/7xxx) all using CAT 12.6/SDK 2.6 and everything just seems to WORK.
I have also found that the AUTOTUNE feature works great. I only specify --shaders, -I (Intensity) and -g (threads) and the performance is better than if I mess with it.
Thanks again for all your hard work Con.
Awesome. Thanks a lot for the feedback bitlane  |
|
|
|
|
Calm down. There's no doubt there were dud cgminer releases along the way, and I tried to get bugfixes out asap. Move on, nothing more to see here.
|
|
|
|
Case in point: The problem we are seeing now with 2.6.0 is due to a dead cgminer function in BAMT.. a function that only exists because cgminer kept crashing for Gigavps!
Thing is I proved it is NOT DEAD. You are killing it. I instrumented a clear call to the API telling it to quit and went into mother to find out why. You call /etc/init.d/mine restart inappropriately on a running cgminer. edit: Note I am NOT claiming bamt 0.4/0.5 was ever intended to run on 2.6.x cgminer, but it is not a failing cgminer issue. |
|
|
|
since its already utilizing 100% of my 12 threads
Somethings strange. 12 threads: 33mhash, 6 threads: 26mhash
Learn the difference between cores and threads on your CPU. |
|
|
|
Well after a few hours of messing around with this, I had to shoehorn shit all over the place to make it mine on a machine that did NOT have an AMD card which BAMT seems not to work with... Anyway I instrumented the newer cgminer restart problem in bamt and it is indeed in the /opt/bamt/mother monitoring file. The perl parsing of ps axu output fails to detect cgminer is there and it then calls /etc/init.d/mine restart . So it is in fact bamt that is restarting cgminer, and if I edit the mother script to parse the output of ps axu differently, it does NOT continually restart cgminer. Alas I don't really know perl, but it does seem to need fixing. If you copy this file on top of mother in /opt/bamt it shouldn't restart on you (note this is not the correct fix and will probably not restart cgminer should it actually really crash): http://ck.kolivas.org/apps/cgminer/temp/motherBAMT is only for AMD gpu mining. It is not designed to work without one. If you use the cgminer included in BAMT, you'll not have this problem. Newer versions of cgminer are not supported at this time. If we release an update, we will adjust mother to work with the updated version. I was responding to the numerous requests from people as to why bamt keeps restarting the newer versions. We know you only support older versions but that doesn't mean that everyone out there will want to stick to them. I instrumented it because cgminer kept getting blamed, and I had no care about the AMD aspect; I was just explaining why it was hard to test it on hardware I had available to try it on (all of which have nvidia GPUs). |
|
|
|
For those having issues with bamt continually restarting the latest cgminer, I've tracked it down to the mother file in bamt in /opt/bamt/mother . As a temporary fix, you can copy this hacked one to replace it: http://ck.kolivas.org/apps/cgminer/temp/mother |
|
|
|
Well after a few hours of messing around with this, I had to shoehorn shit all over the place to make it mine on a machine that did NOT have an AMD card which BAMT seems not to work with... Anyway I instrumented the newer cgminer restart problem in bamt and it is indeed in the /opt/bamt/mother monitoring file. The perl parsing of ps axu output fails to detect cgminer is there and it then calls /etc/init.d/mine restart . So it is in fact bamt that is restarting cgminer, and if I edit the mother script to parse the output of ps axu differently, it does NOT continually restart cgminer. Alas I don't really know perl, but it does seem to need fixing. If you copy this file on top of mother in /opt/bamt it shouldn't restart on you (note this is not the correct fix and will probably not restart cgminer should it actually really crash): http://ck.kolivas.org/apps/cgminer/temp/mother |
|
|
|
Hi!
Testing version 2.6.4 on Ubuntu 12.04, found a (minor) bug, but I think it could be an older one. Yesterday I configured my system to use the onboard GPU (3300) for display and the PCIe card (5770) for mining only. Unfortunately, ADL and CL GPU mapping does not seem to work.
Ok, fixed it by myself. There is definitely a bug. When finding ADL devices, one loop mixed up CL and ADL devices. Here is the diff which fixes it: hko@cave:~/src/cgminer/cgminer$ git diff
diff --git a/adl.c b/adl.c
index 69c06de..c60f08c 100644
--- a/adl.c
+++ b/adl.c
@@ -339,16 +339,16 @@ void init_adl(int nDevs)
}
}
- for (gpu = 0; gpu < devices; gpu++) {
+ for (gpu = 0; gpu < nDevs; gpu++) {
struct gpu_adl *ga;
int iAdapterIndex;
int lpAdapterID;
ADLODPerformanceLevels *lpOdPerformanceLevels;
int lev;
-
- i = vadapters[gpu].id;
+ int adlGpu = gpus[gpu].virtual_adl;
+ i = vadapters[adlGpu].id;
iAdapterIndex = lpInfo[i].iAdapterIndex;
- gpus[gpu].virtual_gpu = vadapters[gpu].virtual_gpu;
+ gpus[gpu].virtual_gpu = vadapters[adlGpu].virtual_gpu;
/* Get unique identifier of the adapter, 0 means not AMD */
result = ADL_Adapter_ID_Get(iAdapterIndex, &lpAdapterID);
@@ -358,11 +358,11 @@ void init_adl(int nDevs)
}
if (gpus[gpu].deven == DEV_DISABLED) {
- gpus[i].gpu_engine =
- gpus[i].gpu_memclock =
- gpus[i].gpu_vddc =
- gpus[i].gpu_fan =
- gpus[i].gpu_powertune = 0;
+ gpus[gpu].gpu_engine =
+ gpus[gpu].gpu_memclock =
+ gpus[gpu].gpu_vddc =
+ gpus[gpu].gpu_fan =
+ gpus[gpu].gpu_powertune = 0;
continue;
}
and a debug log file fromfixed code: [2012-08-11 16:01:32] Started cgminer 2.6.4
[2012-08-11 16:01:32] Loaded configuration file /home/xxxxxxx/.cgminer/cgminer.conf
[2012-08-11 16:01:32] CL Platform 0 vendor: Advanced Micro Devices, Inc.
[2012-08-11 16:01:32] CL Platform 0 name: AMD Accelerated Parallel Processing
[2012-08-11 16:01:32] CL Platform 0 version: OpenCL 1.2 AMD-APP (937.2)
[2012-08-11 16:01:32] Platform 0 devices: 1
[2012-08-11 16:01:32] 0 Juniper
[2012-08-11 16:01:32] GPU 0 iAdapterIndex 0 strUDID 296:38420:4098:33613:4163 iBusNumber 1 iDeviceNumber
5 iFunctionNumber 0 iVendorID 4098 strAdapterName ATI Radeon HD 3300 Graphics
[2012-08-11 16:01:32] GPU 1 iAdapterIndex 2 strUDID 512:26808:4098:9539:4098 iBusNumber 2 iDeviceNumber 0
iFunctionNumber 0 iVendorID 4098 strAdapterName ATI Radeon HD 5700 Series
[2012-08-11 16:01:32] ADL found more devices than opencl!
[2012-08-11 16:01:32] There is possibly at least one GPU that doesn't support OpenCL
[2012-08-11 16:01:32] Use the gpu map feature to reliably map OpenCL to ADL
[2012-08-11 16:01:32] Mapping OpenCL device 0 to ADL device 1
[2012-08-11 16:01:32] WARNING: Number of OpenCL and ADL devices did not match!
[2012-08-11 16:01:32] Hardware monitoring may NOT match up with devices!
[2012-08-11 16:01:32] GPU 0 ATI Radeon HD 5700 Series hardware monitoring enabled
[2012-08-11 16:01:32] Setting GPU 0 engine clock to 945
[2012-08-11 16:01:32] Setting GPU 0 memory clock to 180
[2012-08-11 16:01:32] Setting GPU 0 voltage to 1.125
[2012-08-11 16:01:32] Popping work to work thread
[2012-08-11 16:01:32] Probing for an alive pool
[2012-08-11 16:01:32] Popping work to stage thread
--- Nite69 WalletId: 17gNvfoD2FDqTfESUxNEmTukGbGVAiJhXp Much appreciated, thanks! |
|
|
|
|
You have to delete any .bins that cgminer generates whenever you change an SDK.
|
|
|
|
|
Show Posts
