Author

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

hero member
Activity: 576
Merit: 500
When I went to 2.7.1, at some point one of my cgminers switched pools, and then would not switch back:



Bonuspool is definitely up and the cgminer on the right is connected to it, but on the left, it keeps saying it is online, won't switch to it, stays on pool 1, then says pool 0 is not responding (even though it isn't offline).
sr. member
Activity: 378
Merit: 250
Other vector sizes have been tried. They suck.
They've been tried with scrypt you say?  Because, with scrypt, a lot of the overhead is shifted to the loading and unloading of data.  And I recall having 8 vectors working for me better than 4 with the VLIW5 based GPU as long as the code could be written to support it.
Instead of just one uint8, we have two uint4 variables that have to load back and forth.  Now, it might just be me, but that seems rather inefficient doing that many reads and writes.
If someone would give it a try, I think we could determine it once and for all.
hero member
Activity: 591
Merit: 500
Hopefully the dynamic mode for GPUs is fixed on windows.
What about on Linux? I've been noticing the -10 bug pop up since I upgraded to 2.7 last night. I've had to start just manually switching my intensity from 4 to 6.
hero member
Activity: 807
Merit: 500
So I tried to use scrypt on cgminer 2.7.1 just to see what kind of hashrate I would get with my 5830.  This is the command I ran:

GPU_MAX_ALLOC_PERCENT=100 GPU_USE_SYNC_OBJECTS=1 DISPLAY=:0 cgminer --shaders 1120 --intensity 12 --scrypt  (tried with --benchmark and with a pool in case --benchmark wouldn't work).  Instead of getting an idea of my hashrate, I got a failure.  Perhaps my SDK is too old, but I'm not sure.  Anyone have any clue what this is about?:
Code:
 [2012-08-21 12:22:05] Started cgminer 2.7.1

/tmp/OCLKybKEH.cl(583): error: the opencl builtin function can only takes
          [unsigned] char/short/int/long[n] as first argument
                B[i+4] = EndianSwap(tmp[i]);
                         ^

/tmp/OCLKybKEH.cl(583): error: mixed vector-scalar operation not allowed
          unless up-convertable(scalar-type=>vector-element-type)
                B[i+4] = EndianSwap(tmp[i]);
                         ^

/tmp/OCLKybKEH.cl(590): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(594): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(607): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(611): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(624): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(642): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(663): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(677): warning: unrecognized #pragma
  #pragma unroll
          ^

/tmp/OCLKybKEH.cl(636): warning: variable "ySIZE" was declared but never
          referenced
        const uint ySIZE = (1024/LOOKUP_GAP+(1024%LOOKUP_GAP>0));
                   ^

/tmp/OCLKybKEH.cl(707): warning: unrecognized #pragma
  #pragma unroll
          ^

12 errors detected in the compilation of "/tmp/OCLKybKEH.cl".

 [2012-08-21 12:22:05] Failed to init GPU thread 0, disabling device 0
 [2012-08-21 12:22:05] Restarting the GPU from the menu will not fix this.
 [2012-08-21 12:22:05] Try restarting cgminer.
newbie
Activity: 21
Merit: 0
Hi,

Big problems with my miner. I have been mining 2-3 months, but I had to make fresh install of my backup computer. All steps and logs are here:

https://bitcointalksearch.org/topic/cgminer-does-nothing-101758

Please, someone? RCP calls and job curls are missing... I have spotted the part in cgminer.c code, but so far I have not added own debugging messages while I hope someone knows what is wrong.

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Also, 2.7.1 segfaulted on me. I couldn't find a core file, is there normally one produced?
On linux to produce a core file you usually have to type something like:
ulimit -c 2097152
before you start cgminer, to get a core file on a crash (that number I think means 2GB limit on the core size)
I always set a limit since once I got a strange crash that was about 60GB and I was running it on a network drive (at home) and my home network was rather slow for a few minutes, while it created the core file Smiley

Edit: then to get a possibly useful trace of the core file core.nnn to pastebin:
gdb cgminer core.nnn
bt
hero member
Activity: 896
Merit: 1000
New version - 2.7.1, 21st August 2012
Something odd :
I have 6 mining rigs. 4 have multiple cards, 2 have a single card with a total of 21 cards. Until 2.7.1, I've had next to zero hardware errors reported by cgminer, only one card in the 21 had occasional (maybe 1/day) errors, it was a 5870 in a 5-card rig.
With 2.7.1, I've got hardware errors reported on all cards in the rigs with multiple cards (in fact 18 out of 19 cards have errors). The cards in a single-card rig don't have errors reported (even a 5970 with its 2 GPUs, so if it may be linked to the number of cards, it's not with the number of GPUs).

Could something have prevented errors to be reported with previous versions ?

Some additional, maybe related information :
I had hardware errors on a 7970 when I used 2 threads on it, switching everything to dynamic with a 250ms target made these errors disappear (with no noticeable difference in hashrate).

All the cards are overclocked/downvolted/... but are set in a configuration which is(/was ?) known to be stable (ie: each time a card is SICK/DEAD or crashes cgminer it is downclocked), it's only when a new card is added that a rig can be temporarily unstable the time I find its sweet spot.

Note that I detect card making cgminer crash by monitoring their temperature: on my configuration a card was most of the time not detected SICK (I suspect it as something to do with my using the API to monitor the rigs: it seemed to crash cgminer before the 60s SICK delay) but crashed cgminer, before each crash I could witness the temperature of the offending card dropped markedly.
legendary
Activity: 952
Merit: 1000
hero member
Activity: 481
Merit: 500
Also, 2.7.1 segfaulted on me. I couldn't find a core file, is there normally one produced?
hero member
Activity: 481
Merit: 500
I noticed on btcguild I only get around 80 percent efficiency but on ozcoin.net I'm getting 270 percent. Can I assume btcguild doesn't support rolltime and that I'm getting more coin with ozcoin.net? (PPS vs. PPS)
legendary
Activity: 952
Merit: 1000
..and now I may lie down for a week to recover...

Even God rested on the seventh day.  Grin
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New version - 2.7.1, 21st August 2012

Bugfixes galore \o/ The emphasis was just on outstanding bugfixes on this release to try and get a nice stable release out after the frantic pace of development recently.

Human readable changelog:
The occasional strange behaviour where lots of work would end up on backup pools in failover mode should be fixed.
The occasional scenario where one pool dies and the others behave like they're slow to provide work should be fixed.
Very high hashrate (U > 100) machines should now be able to work unhindered even on pools that don't support rolltime.
The -r and -R options no longer do anything and are deprecated in preference for faster communications and simpler code.
Hopefully the dynamic mode for GPUs is fixed on windows.
cgminer dying on switching users on windows should be fixed (it may actually restart itself to recover unless --no-restart is specified).
Hopefully the 7 day windows crash bug has been fixed
Share submissions that are re-sent will have (resend) appended to the log
Hopefully the gpu-map feature is working for more adl devices than opencl.
BFL autodetect fixes on windows.
New API features
New miner.php features.


Full changelog:
- Update windows build instructions courtesy of sharky.
- Increase max curls to number of mining threads + queue * 2, accounting for up
and downstream comms.
- Queue enough requests to get started.
- There is no point trying to clone_work in get_work() any more since we clone
on every get_work_thread where possible.
- There is no point subtracting 1 from maxq in get_work_thread.
- Only set lagging flag once there are no staged work items.
- select_pool does not switch back to the primary once lagging is disabled.
- miner.php allow page title to be defined in myminer.php
- Free work before retrying in get_work_thread.
- Increment total work counter under mutex lock.
- Increment the queued count after the curl is popped in case there's a delay
waiting on curls and we think we've queued work when in fact we're waiting
- API new command 'coin' with mining information
- Do the dynamic timing in opencl code over a single pass through scanhash to
make sure we're only getting opencl times contributing to the measured inte
- Increase curl reaping time to 5 minutes since comms between  curl requests can
be 2 mins apart with lots of rolltime.
- No need for extra variable in hash_push.
- Remove short options -r and -R to allow them to be reused and remove readme
entries for deprecated options.
- Avoid attempting to recursively lock the console mutex by disabling warnings
in gpu_fanpercent when fanspeed monitoring fails on windows. Debugged by luke-jr
- Deprecate the opt_fail_pause parameter, leaving a null placeholder for
existing configurations.
- Don't pause after failed getwork, set lagging flag and reassess.
- Add message to share if it's a resubmit.
- We should not be pausing in trying to resubmit shares.
- Get rid of the extending fail pause on failed connects since we discard work
after a period.
- get_work always returns true so turn it into a void function.
- get_work never returns false so get rid of fail pause loop.
- Get rid of pause and retry from get_upstream_work so we only do it from one
place.
- Deprecate the opt_retries feature as no one wants cgminer to automatically
abort. Leave a null placeholder for configurations that still have it.
- Reinstate fix ADL gpu-map not working when there are more ADL devices than
openCL patch by Nite69. Add virtual adl mapping for when none is specified o
- miner.php show summary Diff1 Shares total
- miner.php fix Work Utility totals
- miner.php format new Work Utility and Diff1 Shares
- API V1.17 show Work Utility and Diff1 Shares

..and now I may lie down for a week to recover...
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
On second thought, there may be a bug here... will investigate tomorrow.
About this, I have confirmed there is a bug in 2.7 where it can get into a situation where it can't queue enough work and continually thinks one pool is not providing enough work. I have fixed this in git but this has introduced a new crash which kano is trying to help me track down. In the meantime, anyone on 2.7.0 should probably enable --failover-only to mitigate its problems.
Lem
newbie
Activity: 78
Merit: 0
Hi! Maybe I found a problem with 2.7.0, which made me revert back to my prevoius 2.6.4.

Here it is my log.  My pool strategy is failover, from my config file ("failover" : true).

Code:
 [2012-08-20 23:08:23] Accepted ad5ca87d.4b16b22d GPU 0 pool 0
 [2012-08-20 23:08:24] Accepted d8ad5aa6.0fb8ad81 GPU 0 pool 0
 [2012-08-20 23:08:26] Accepted 61bbdca3.1386ba69 GPU 1 pool 0
 [2012-08-20 23:08:30] Accepted 49bdbbae.0871fe44 GPU 1 pool 0
 [2012-08-20 23:08:34] Accepted 870dd767.c9515add GPU 1 pool 0
 [2012-08-20 23:08:37] Accepted b7cee592.ec5e3309 GPU 1 pool 0
 [2012-08-20 23:08:38] Accepted 365bcc52.fec963e5 GPU 0 pool 0

Here above things are going fine, I'm mining on pool0. Then pool0 (mtred) has a problem and cgminer correctly switches to pool1:

Code:
 [2012-08-20 23:08:41] Accepted ead48465.46ad7724 GPU 1 pool 0
 [2012-08-20 23:08:42] Accepted 1d460512.a8785f1a GPU 1 pool 0
 [2012-08-20 23:08:44] Accepted 5ed61a6e.7299324d GPU 0 pool 0
 [2012-08-20 23:09:37] Accepted 4429754e.30542bf0 GPU 0 pool 2
 [2012-08-20 23:09:48] Pool 0 communication failure, caching submissions
 [2012-08-20 23:09:55] Accepted a590ee8b.e6770be8 GPU 1 pool 5
 [2012-08-20 23:09:59] Accepted 4860ba37.6b16d191 GPU 1 pool 5
 [2012-08-20 23:10:01] Accepted 39a965e6.bbe16b68 GPU 0 pool 3
 [2012-08-20 23:10:03] Accepted 7f11bb6f.550cfc5d GPU 1 pool 5
 [2012-08-20 23:10:10] Pool 0 not providing work fast enough
 [2012-08-20 23:10:11] Accepted 294331c9.edf6e0d9 GPU 0 pool 3
 [2012-08-20 23:10:53] Share became stale while retrying submit, discarding
 [2012-08-20 23:11:00] Share became stale while retrying submit, discarding
 [2012-08-20 23:11:02] Share became stale while retrying submit, discarding
 [2012-08-20 23:11:03] Share became stale while retrying submit, discarding
 [2012-08-20 23:11:04] Pool 0 http://mtred.com:8337 not responding!
 [2012-08-20 23:11:04] Switching to http://pool.ABCPool.co:8332
 [2012-08-20 23:11:04] Pool 1 not providing work fast enough
 [2012-08-20 23:11:05] Accepted 4e517d74.ff47c0ad GPU 1 pool 5
 [2012-08-20 23:11:06] Accepted d17757f8.5b11eefd GPU 1 pool 2
 [2012-08-20 23:11:06] Accepted d9e05eda.d3af4bf6 GPU 0 pool 3
 [2012-08-20 23:11:10] Accepted a87aea73.95598277 GPU 0 pool 1
 [2012-08-20 23:11:12] Accepted 62a2a162.cd607138 GPU 1 pool 2
 [2012-08-20 23:11:15] Accepted 96f5970d.9e46aa62 GPU 0 pool 1
 [2012-08-20 23:11:15] Share became stale while retrying submit, discarding
 [2012-08-20 23:11:16] Accepted e77a20af.e0fba971 GPU 0 pool 1
 [2012-08-20 23:11:20] Accepted 0a266610.fae7fe6a GPU 1 pool 2
 [2012-08-20 23:11:21] Accepted 6b4536ea.1ed3bc85 GPU 1 pool 1
 [2012-08-20 23:11:21] Accepted a25fd978.9b6a051a GPU 1 pool 2

It looks like also pool1 (ABCpool) is having a problem, so cgminer starts getting work from, and sending shares to, all the other pools. I've never seen so much spread before (I mean: the activity to the selected pool, pool1, is so little!), but I'm fine with it.

Code:
 [2012-08-20 23:11:23] Accepted 1b6adfc5.af50778e GPU 0 pool 5
 [2012-08-20 23:11:29] Accepted 00f4739d.fad0da5b GPU 0 pool 5
 [2012-08-20 23:11:29] Accepted c576c791.18bf0748 GPU 0 pool 5
 [2012-08-20 23:11:32] Accepted 8fcc5991.2cd4715c GPU 1 pool 1
 [2012-08-20 23:11:37] Accepted 3e57ca56.a4efec72 GPU 1 pool 1
 [2012-08-20 23:11:38] Accepted f2c7f9ac.35af1141 GPU 1 pool 1
 [2012-08-20 23:11:41] Accepted cdbf7c3c.128e1ad8 GPU 0 pool 3
 [2012-08-20 23:11:44] Accepted 2c6f4420.8dd5a69c GPU 0 pool 5
 [2012-08-20 23:11:45] Accepted 8d1eca17.543d2c2a GPU 1 pool 1
 [2012-08-20 23:11:53] Share became stale while retrying submit, discarding
 [2012-08-20 23:11:54] Accepted 913bdc64.b3e010fe GPU 0 pool 3
 [2012-08-20 23:11:57] Accepted f5abfb67.86c42279 GPU 1 pool 2
 [2012-08-20 23:11:57] Accepted 01b7bb38.90f01708 GPU 0 pool 5
 [2012-08-20 23:11:58] Accepted 7929b2e6.f0a03878 GPU 1 pool 2
 [2012-08-20 23:12:00] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:01] Accepted 4ccaa5cc.64c3961a GPU 0 pool 3
 [2012-08-20 23:12:02] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:02] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:02] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:02] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:02] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:03] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:03] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:03] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:03] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:03] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:04] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:04] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:04] Share became stale while retrying submit, discarding
 [2012-08-20 23:12:05] Accepted f69dea76.22d1035a GPU 0 pool 3
 [2012-08-20 23:12:06] Accepted c0d926df.b4edf6d0 GPU 0 pool 5
 [2012-08-20 23:12:07] Accepted 9971b7b3.ee9e5b58 GPU 1 pool 1
 [2012-08-20 23:12:14] Accepted ba206344.926b3324 GPU 1 pool 2
 [2012-08-20 23:12:19] Accepted 55196693.119567fe GPU 0 pool 3

The behaviour remains the same (I cut the log), then the problem: I switch to pool2 (deepbit) sending, as usual, an API request to cgminer. Cgminer obeys ("Connected to http://deepbit..."), pool2 (deepbit) has no problem at all (verified), but despite it cgminer keeps on sending shares everywhere!

Code:
 [2012-08-20 23:25:05] Accepted 3d3b8e8b.ce1081bc GPU 0 pool 5
 [2012-08-20 23:25:10] Accepted ed1ff46e.5c7edd2c GPU 0 pool 1
 [2012-08-20 23:25:10] Accepted 6b536501.c2e55d11 GPU 0 pool 1
 [2012-08-20 23:25:11] Switching to http://pit.deepbit.net:8332
 [2012-08-20 23:25:14] Accepted a5d4229e.056bcc96 GPU 0 pool 1
 [2012-08-20 23:25:16] Accepted df7ee3b1.74c47722 GPU 0 pool 5
 [2012-08-20 23:25:20] Accepted 6ae8fcc8.1535576b GPU 0 pool 5
 [2012-08-20 23:25:29] Accepted 1011f94f.0b847218 GPU 0 pool 5
 [2012-08-20 23:25:29] Accepted 30df90af.aa0212bd GPU 1 pool 3
 [2012-08-20 23:25:41] Accepted d0e595c1.bfc81aca GPU 0 pool 5
 [2012-08-20 23:25:43] Accepted 8205f7c1.41922dcf GPU 1 pool 2
 [2012-08-20 23:25:49] Accepted 9017eea8.6cd43a89 GPU 0 pool 5
 [2012-08-20 23:25:52] Accepted 9de1355c.0a121775 GPU 0 pool 1
 [2012-08-20 23:25:54] Accepted 0d813bb3.b8676a4f GPU 0 pool 1
 [2012-08-20 23:25:56] Accepted febc43cd.e891452c GPU 0 pool 1
 [2012-08-20 23:25:58] Accepted 1a1588be.5cc55105 GPU 0 pool 5
 [2012-08-20 23:26:02] Accepted 3ab19d48.8c6564ef GPU 1 pool 3
 [2012-08-20 23:26:04] Accepted e70a75e0.9ccf7c43 GPU 0 pool 2
 [2012-08-20 23:26:05] Accepted b40944ab.342e7fb3 GPU 0 pool 1
 [2012-08-20 23:26:09] Accepted c4e0045c.adf7f6d1 GPU 1 pool 5
 [2012-08-20 23:26:10] Accepted c8f114fc.36310859 GPU 0 pool 2
 [2012-08-20 23:26:10] Accepted a9b71b26.f8717314 GPU 1 pool 5
 [2012-08-20 23:26:16] Accepted 4cdc01b1.a83183dd GPU 1 pool 1
 [2012-08-20 23:26:20] Accepted 26c93d21.dbd60dc2 GPU 0 pool 3
 [2012-08-20 23:26:26] Accepted 500627dd.293578cb GPU 0 pool 3
 [2012-08-20 23:26:26] Accepted 5d870790.ccd40e87 GPU 0 pool 3
 [2012-08-20 23:26:26] Accepted 01f0aa42.cb83ecc1 GPU 0 pool 3
 [2012-08-20 23:26:31] Accepted f912d7cd.7ff1906d GPU 0 pool 3
 [2012-08-20 23:26:31] Accepted 033fc9d9.b04961f1 GPU 0 pool 3
 [2012-08-20 23:26:36] Accepted 31b41f26.721fd92c GPU 1 pool 5
 [2012-08-20 23:26:39] Accepted c5fc2dcb.cc02eb3f GPU 0 pool 3
 [2012-08-20 23:26:46] Accepted 23b3e0a0.ebf52368 GPU 1 pool 2
 [2012-08-20 23:26:48] Accepted 05c01a34.989b1098 GPU 0 pool 3
 [2012-08-20 23:27:03] Accepted 26f7405c.d2499ba8 GPU 0 pool 3
...

After some minutes, I quitted and reverted back to 2.6.4.

HTH.
Thanks for everything.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Other vector sizes have been tried. They suck.
sr. member
Activity: 378
Merit: 250
Just a thought for the Litecoin Scrypt OpenCL miner.  Combine the multiple uint4 vectors into uint8 so that the SIMD processors can do their job more efficiently.  It will have the same number of reads and writes, but the instructions should be fewer.  This is just a theory anyway.  I would try it myself, but it requires a modification to almost the entire code that I'm not capable of myself.  There's just too many offsets and the code is designed using the outdated w, x, y and z vectors instead of s0 - s3 so expanding upon it is difficult at best.
I had managed about half of it last night until I got to the bottom where the W and w variables came together.  One of those needs to be changed so that they can be told apart from each other.
But yeah, if the same instructions are going to be used on two (or more) sets of vector 4 types, they need to be combined for simplicity.
Could use a comment on this.
sr. member
Activity: 383
Merit: 250
Updated Windows compile instructions:

http://pastebin.com/3pzivj32

Hopefully this will be included in the next release of cgminer as well.

This was tested on both Windows 7 and Windows XP.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
On second thought, there may be a bug here... will investigate tomorrow.
About this, I have confirmed there is a bug in 2.7 where it can get into a situation where it can't queue enough work and continually thinks one pool is not providing enough work. I have fixed this in git but this has introduced a new crash which kano is trying to help me track down. In the meantime, anyone on 2.7.0 should probably enable --failover-only to mitigate its problems.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Does anyone know why CGminer (fresh copy) Keeps changing my clocks?!!
When i open/close the program it changes my clocks to a different OC setting...
Sounds like there is a config file somewhere.  I haven't messed with config files, but presumably you didn't delete the directory where the fresh copy was placed or the config file is stored in you working directory, outside of the directory where the fresh copy of cgminer has been place.
Bingo!
Thanks
Somehow it was running my other cgminers configfile *shrugs* Moved the cgminer folder to it's own and everything was fine

Lord knows why, but cgminer's default behaviour is to load cgminer.conf whether it's specified in the cmd line or not. if you specify a different conf file, it'll load both.
The reasoning behind it is quit simple:
If you save your config using the default save file, cgminer will always load it next time.

The problem is of course is if you put a 'cgminer.conf' in the place where it looks for the default it will always load it

Linux: ~/.cgminer/cgminer.conf
Windows: current directory: cgminer.conf

If you saved it using cgminer screen keys to the default location (press S and W), then of course it makes sense.

... and yes this has been explained in this thread a few times.

And is the first paragraph at the beginning of the "EXECUTIVE SUMMARY ON USAGE:" in the README

After saving configuration from the menu, you do not need to give cgminer any
arguments and it will load your configuration.


Though I'm not saying I like it - but it definitely has it's use ...
legendary
Activity: 1795
Merit: 1208
This is not OK.
Does anyone know why CGminer (fresh copy) Keeps changing my clocks?!!
When i open/close the program it changes my clocks to a different OC setting...
Sounds like there is a config file somewhere.  I haven't messed with config files, but presumably you didn't delete the directory where the fresh copy was placed or the config file is stored in you working directory, outside of the directory where the fresh copy of cgminer has been place.
Bingo!
Thanks
Somehow it was running my other cgminers configfile *shrugs* Moved the cgminer folder to it's own and everything was fine

Lord knows why, but cgminer's default behaviour is to load cgminer.conf whether it's specified in the cmd line or not. if you specify a different conf file, it'll load both.
Jump to: