Topic: ATTN Litecoin GPU Miners - Scrypt support for cgminer - page 13. (Read 175855 times)

thnx bud.

doesnt seem to work right for me..
Each time i try to launch it, my fourth 7970 crashes..

But it works well, with an earlier version

Sweet. Works on 7970 - gets the optimum values automatically.

Under Ubuntu 12.04 with 12.6 drivers and sdk  with the latest build of cgminer the highest you can set the thread concurrency is 2048 I'm trying to figure why I guess that is the limit in cgminer and not reaper if the kernels are similar?

four 5850s

"intensity" : "11,11,11,11",
"vectors" : "1,1,1,1",
"worksize" : "128,128,128,128",
"kernel" : "scrypt,scrypt,scrypt,scrypt",
"gpu-engine" : "0-750,0-700,0-700,0-700",
"gpu-memclock" : "1000,1000,1000,1000",
"gpu-vddc" : "1.000,0.950,0.950,0.950",
"gpu-threads" : "2",
"scrypt" : true,

this works perfectly at -I 11  ~675 kh
at -I 12 start errors miss-target

I get the same exact results under reaper

worksize 128
aggression 11
threads_per_gpu 2
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 2048

aggression 11 works great no errors  ~ 675 kh
aggression 12 throws errors


Ok the best results for reaper for me seems to be

worksize 128
aggression 12
threads_per_gpu 2
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 5760

this works great no errors ~1030kh pool reports roughly same

I don't have any 5850s running under windows to seem if the results are the same. The same settings that work on both give nearly identical khs in both programs, but the difference is the thread concurrency maximum of 2048 in cgminer vs. 5760 in reaper? this even make sense lol?

I have a couple 5870s I'm need to test this out on but I'm thinking 4 x shader count is the optimum?

I just noticed that reaper builds the buffer at 360mb @ 5760tc   4 x 360 = 1440

--shaders

win32: http://www.mediafire.com/?prbt07a4scihahm

ckolivas just released this new option.

but nobody have compiled a new version of cgminer yet.

i used shaders option with this release http://www.mediafire.com/?0ue7860yv89o05y on windows 7 64 bit & getting this error


My bat file is cgminer.exe --scrypt --url http://lc.ozco.in:9332 --userpass xxx:xxx --shaders 1600 -I 13

  Fixed as of version f98774c

Here is a more detailed breakdown of the most common AMD/ATI Based mining cards with their shader/processor count:
Look up your card, and then in the "Clock rate" column, your "Core (MHz)" and the corresponding processors/shaders is the first # in column "Config core"

Some cards have the same model numbers yet they differ in their shader/processor count

HD 5xxx https://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units#Evergreen_series_.28HD_5xxx.29

HD 6xxx https://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units#Northern_Islands_.28HD_6xxx.29_series

HD 7xxx https://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units#Southern_Islands_.28HD_7xxx.29_series

More better, more effectively

any body else having troubles running cgminer on p2pool?

Added the --shaders option now
- Make the thread concurrency and lookup gap options hidden on the command line and autotune parameters with a newly parsed --shaders option.

So you should only need to try --shaders and -I now. Note that any intensity above 13 is a gamble and highly dependent on hardware/software combination as to whether it's better, so -I 13 is a good start.

Here's the table again:

And for those who need me to spell it out, let's say you have a 5830, try this first:
--shaders 1120 -I 13

1. it reports you are over the limit and the device merrily goes away trashing data
2. it reports you are over the limit and you try to set it over that limit and the device just refuses

Devices respond differently to different invalid values. That's why it's a warning.

I readed that post

but I don't undestend why:

I assume you read my long post about intensity, maximum buffer size, valid shares, trampled memory, thread concurrency and so on? I mined for half hour on coinotron and it returned valid shares for that half hour and coinotron reported back the same rate I was hashing at.

coinotron difficulty is
"target": "000000000000000000000000000000000000000000000000000000c0cc0c0000"
default is
0xffff

Edit: There is an upper limit to difficulty it will accept, but that's only relevant to solo mining magnitudes, and then it will safely submit more attempts at solving it than necessary, not the other way around, so you should never miss a share unless you screw up your tc/lg settings making for invalid work.

thanks alot

on a somewhat related issue: can I nail you some time on getting a mingw gcc environment capable of compiling btc and ltc running?

win32: http://www.mediafire.com/?0ue7860yv89o05y  

what internal difficulty on coinontron?
with internal difficulty 256 dont work on intensivity >10 on old and updated git's

tested on coinotron works fine now

Your system ram matters as well as your OS with this.