Cgminer not working

[Aleppi]

I am using cgwatcher to run Cgminer to mine litecoins in the pool coinotron.com but every time I start mining I get the error that my vram size is set too large when I haven't set it to anything and then proceeds to disable gpus threads from 1 to 0.

Thanks in advance.

[hehehehhehehehe]

Try lowering your thread concurrency,

And what is it with EVERYONE mining now..

[rhyseyness]

Thread concurreny is too high.

Try starting at 8192 and increase in multiples of about 1000 from there until you find a sweet spot

[Swegly]

Thread concurreny is too high.

Try starting at 8192 and increase in multiples of about 1000 from there until you find a sweet spot

It works at 8192 but it only gives me 120Kh/s average. :C It is supposed to go over 700.

[Tigerbomb8]

It works at 8192 but it only gives me 120Kh/s average. :C It is supposed to go over 700.

Please don't hijack threads

[Aleppi]

Please don't hijack threads

Sorry that was me my friend had been logged in on my computer before and i forgot to log out but it is still giving me way too low Kh/s.

[FlakeyBanana]

Try lowering your thread concurrency,

And what is it with EVERYONE mining now..

the huge jump in LTC price it went from $10 to $40

[rhyseyness]

Sorry that was me my friend had been logged in on my computer before and i forgot to log out but it is still giving me way too low Kh/s.

 

So what happens when you increase thread concurrency in small increments?

[Aleppi]

So what happens when you increase thread concurrency in small increments?

I tried increasing it by 1000 like you said but anything above 8192 crashes.

[rhyseyness]

I tried increasing it by 1000 like you said but anything above 8192 crashes.

Hmm, that's strange.

What's your intensity at?

[Aleppi]

Hmm, that's strange.

What's your intensity at?

11

[rhyseyness]

11

In that case, I don't really know what to suggest

Sorry I couldn't be of more help.

Hopefully someone with a little more knowledge than me can come and help you out

[RuecanOnRails]

What are you mining on?

What is settings are you using with your batch file?

What are your core/mem clock speeds?

 

Have you tried replicating the settings people have used on here https://litecoin.info/Mining_Hardware_Comparison

 

 

The thread Concurrency needs stay within a number divisible by 8, Try increasing/decreasing with any of these values. 64, 128, 256, 512, 1024, 2048.

[Aleppi]

What are you mining on?

What is settings are you using with your batch file?

What are your core/mem clock speeds?

 

Have you tried replicating the settings people have used on here https://litecoin.info/Mining_Hardware_Comparison

 

 

The thread Concurrency needs stay within a number divisible by 8, Try increasing/decreasing with any of these values. 64, 128, 256, 512, 1024, 2048.

I am using cgminer with the rig in my sig and i am using the settings from this site

http://holynerdvana.blogspot.se/2013/11/litecoin-mining-with-r9-290-and-r9-290x.html

[RuecanOnRails]

Try a thread concurrency of 16384. and Intensity of 18 - 20.

 

I'd suggest following the similar guide to setting up a 7970 found in the scrypt-readme with CGminer.

---TUNING AN AMD RADEON 7970Example tuning a 7970 for Scrypt mining:On linux run this command:export GPU_MAX_ALLOC_PERCENT=100or on windows this:setx GPU_MAX_ALLOC_PERCENT 100in the same console/bash/dos prompt/bat file/whatever you want to call it,before running cgminer.First, find the highest thread concurrency that you can start it at. They shouldall start at 8192 but some will go up to 3 times that. Don't go too high on theintensity while testing and don't change gpu threads. If you cannot go above8192, don't fret as you can still get a high hashrate.Delete any .bin files so you're starting from scratch and see what bins getgenerated.First try without any thread concurrency or even shaders, as cgminer will try tofind an optimal valuecgminer -I 13If that starts mining, see what bin was generated, it is likely the largestmeaningful TC you can set.Starting it on mine I get:scrypt130302Tahitiglg2tc22392w64l8.binSee tc22392 that's telling you what thread concurrency it was. It should startwithout TC parameters, but you never know. So if it doesn't, start with--thread-concurrency 8192 and add 2048 to it at a time till you find the highestvalue it will start successfully at.Then start overclocking the eyeballs off your memory, as 7970s are exquisitelysensitive to memory speed and amazingly overclockable but please make sure itkeeps adequately cooled with --auto-fan! Do it while it's running from the GPUmenu. Go up by 25 at a time every 30 seconds or so until your GPU crashes. Thenreboot and start it 25 lower as a rough start. Mine runs stable at 1900 memorywithout overvolting. Overvolting is the only thing that can actually damage yourGPU so I wouldn't recommend it at all.Then once you find the maximum memory clock speed, you need to find the sweetspot engine clock speed that matches it. It's a fine line where one more MHzwill make the hashrate drop by 20%. It's somewhere in the .57 - 0.6 ratio range.Start your engine clock speed at half your memory clock speed and then increaseit by 5 at a time. The hashrate should climb a little each rise in engine speedand then suddenly drop above a certain value. Decrease it by 1 then until youfind it climbs dramatically. If your engine clock speed cannot get that highwithout crashing the GPU, you will have to use a lower memclock.Then, and only then, bother trying to increase intensity further.My final settings were:--gpu-engine 1141  --gpu-memclock 1875 -I 20for a hashrate of 745kH.Note I did not bother setting a thread concurrency. Once you have the magicendpoint, look at what tc was chosen by the bin file generated and then hardcode that in next time (eg --thread-concurrency 22392) as slight changes inthread concurrency will happen every time if you don't specify one, and the tcto clock ratios are critical!Good luck, and if this doesn't work for you, well same old magic discussionapplies, I cannot debug every hardware combo out there.Your numbers will be your numbers depending on your hardware combination and OS,so don't expect to get exactly the same results!