https://bitcointalksearch.org/topic/official-cgminer-mining-software-thread-for-linuxwinosxmipsarmr-pi-4110-28402
I really appreciate the time and effort ckolivas has put into adding scrypt to cgminer. this threads time is over
Topic: ATTN Litecoin GPU Miners - Scrypt support for cgminer (Read 175818 times)
I would like to refer everyone to the main cgminer thread
https://bitcointalksearch.org/topic/official-cgminer-mining-software-thread-for-linuxwinosxmipsarmr-pi-4110-28402
I really appreciate the time and effort ckolivas has put into adding scrypt to cgminer.
this threads time is over
https://bitcointalksearch.org/topic/official-cgminer-mining-software-thread-for-linuxwinosxmipsarmr-pi-4110-28402
I really appreciate the time and effort ckolivas has put into adding scrypt to cgminer. this threads time is over
(long rant snipped).
But I like reading rants come on give it all you got. Doesn't scrypt just piss you off, don't you hate us all for putting you through all this black magic? Come on ckolivas get mad!
(long rant snipped).
But I like reading rants come on give it all you got. Doesn't scrypt just piss you off, don't you hate us all for putting you through all this black magic? Come on ckolivas get mad!
Has this thread been abandoned ? Is that it....SCRYPT Enabled, take it or leave it ?
Now hang on a sec. I've been busting my balls since the scrypt code started working on the last few releases. There have been spot fires all over the place with unexpected bugs, bfl fuckage and to top it off, jesus fucking haunting my threads. I have spent, and still AM spending, shit loads of time getting this fucking bastard working properly... (long rant snipped).Take scrypt discussion to the main cgminer thread, it's part of it now, but I have to prioritise support.
Has this thread been abandoned ? Is that it....SCRYPT Enabled, take it or leave it ?
I don't know if anyone else is experiencing this also, but....
After fighting with crashing miners and CGMiner 2.6.1, I decided to go back to the 'EE' Windows beta build of 2.5.0 and I am getting a TON LESS stales while pool mining.
Still using CAT 12.6/SDK 2.6 (which I have been using from the start) and I haven't changed anything except for the CGMiner version.
Any idea why 2.6.1 (or for me anyway) causes on average 1%+ increase in stales ? (along with the obvious crashes)......
After fighting with crashing miners and CGMiner 2.6.1, I decided to go back to the 'EE' Windows beta build of 2.5.0 and I am getting a TON LESS stales while pool mining.
Still using CAT 12.6/SDK 2.6 (which I have been using from the start) and I haven't changed anything except for the CGMiner version.
Any idea why 2.6.1 (or for me anyway) causes on average 1%+ increase in stales ? (along with the obvious crashes)......
Hey Con, as per my question in a previous post.....
Quote
Would it be possible that when in --SCRYPT mode that the units displayed are 100% in KH/s ? (GPU, Rig Summary/5s/AVG & API output ?)
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
Oh, so it is a known problem. mk. Thanks.
Is there a way to implement an option to add thread-concurrency configuration through cgminer.exe?
Everytime I do a [W], cgminer overwrites my config file, removing
from cgminer.conf.
Or is it already there and I am overlooking it?
https://github.com/ckolivas/cgminer/pull/279 Everytime I do a [W], cgminer overwrites my config file, removing
Code:
"thread-concurrency" : "7200,7200",
from cgminer.conf.
Or is it already there and I am overlooking it?
Is there a way to implement an option to add thread-concurrency configuration through cgminer.exe?
Everytime I do a [W], cgminer overwrites my config file, removing
from cgminer.conf.
Or is it already there and I am overlooking it?
Everytime I do a [W], cgminer overwrites my config file, removing
Code:
"thread-concurrency" : "7200,7200",
from cgminer.conf.
Or is it already there and I am overlooking it?
2x5970, gets me 1388 kH/s, 347Kh/s per core with these parameters :
--scrypt --thread-concurrency 8000 --intensity 18 --lookup-gap 2 --gpu-threads 2 --gpu-memclock 1050 --gpu-engine 750 --auto-fan --auto-gpu --temp-target 81 --worksize 256
Stales at ~1-3% depending on how fast the network is running as most of them come on the new blocks.
--scrypt --thread-concurrency 8000 --intensity 18 --lookup-gap 2 --gpu-threads 2 --gpu-memclock 1050 --gpu-engine 750 --auto-fan --auto-gpu --temp-target 81 --worksize 256
Stales at ~1-3% depending on how fast the network is running as most of them come on the new blocks.
Got cgminer isn't responding. What's your driver version ?
Ubuntu 11.04 12.6 display driver SDK 2.7.
2x5970, gets me 1388 kH/s, 347Kh/s per core with these parameters :
--scrypt --thread-concurrency 8000 --intensity 18 --lookup-gap 2 --gpu-threads 2 --gpu-memclock 1050 --gpu-engine 750 --auto-fan --auto-gpu --temp-target 81 --worksize 256
Stales at ~1-3% depending on how fast the network is running as most of them come on the new blocks.
--scrypt --thread-concurrency 8000 --intensity 18 --lookup-gap 2 --gpu-threads 2 --gpu-memclock 1050 --gpu-engine 750 --auto-fan --auto-gpu --temp-target 81 --worksize 256
Stales at ~1-3% depending on how fast the network is running as most of them come on the new blocks.
Got cgminer isn't responding. What's your driver version ?
That means the settings aren't at best. Play with it, try lower concurrencys and higher ones. The settings won't be the same as reaper. Try other worksizes.
2x5970, got 1022 kH/s with this parameter :
--scrypt --thread-concurrency 6144 --intensity 13 --lookup-gap 2 --gpu-threads 1 --gpu-memclock 1100 --gpu-engine 775 --auto-fan --temp-target 75 --worksize 256
Still less than 1.2 MH/s from reaper with the same configuration.
But temperature so far is good, better than reaper's temperature.
EDIT : Got 1.2 MH/s with intensity 15
I'm afraid to raise intensity because of the warning in readme : "Intensities over 13 start writing over the same ram and it is highly dependent on the GPU, but they can start actually DECREASING your hashrate, or even worse, start producing garbage with rejects skyrocketing."
EDIT 2 : Still fluctuating, now at 1.0 MH/s average.
2x5970, gets me 1388 kH/s, 347Kh/s per core with these parameters :
--scrypt --thread-concurrency 8000 --intensity 18 --lookup-gap 2 --gpu-threads 2 --gpu-memclock 1050 --gpu-engine 750 --auto-fan --auto-gpu --temp-target 81 --worksize 256
Stales at ~1-3% depending on how fast the network is running as most of them come on the new blocks.
That means the settings aren't at best. Play with it, try lower concurrencys and higher ones. The settings won't be the same as reaper. Try other worksizes.
2x5970, got 1022 kH/s with this parameter :
--scrypt --thread-concurrency 6144 --intensity 13 --lookup-gap 2 --gpu-threads 1 --gpu-memclock 1100 --gpu-engine 775 --auto-fan --temp-target 75 --worksize 256
Still less than 1.2 MH/s from reaper with the same configuration.
But temperature so far is good, better than reaper's temperature.
EDIT : Got 1.2 MH/s with intensity 15
I'm afraid to raise intensity because of the warning in readme : "Intensities over 13 start writing over the same ram and it is highly dependent on the GPU, but they can start actually DECREASING your hashrate, or even worse, start producing garbage with rejects skyrocketing."
EDIT 2 : Still fluctuating, now at 1.0 MH/s average.
Could the 'sickness' simply be a low value output in MH/s, causing CGMiner to panic ?
No, but that bug WAS in 2.6.0 which was the main reason for 2.6.1We have found that this problem you describe happens with driver 12.6 when it doesn't happen with the earlier drivers which were better (specifically the so-called 8.921 release which was the first beta driver supporting 7970s).
so if i am not mistaken the main difference between LTC and BTC was the fact that LTC was targeted at CPU mining only.
now that you can mine it on GPU, arent both currencies basically the same? making one redundant?
now that you can mine it on GPU, arent both currencies basically the same? making one redundant?
Nah, no FPGA's or ASIC's for LTC. (thus still accessible by the common man) LTC will have more coins in the wild. Faster confirms. LTC ftw.
edit... delayed reaction. doh.
...
Would it be possible that when in --SCRYPT mode that the units displayed are 100% in KH/s ? (GPU, Rig Summary/5s/AVG & API output ?)
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
Would it be possible that when in --SCRYPT mode that the units displayed are 100% in KH/s ? (GPU, Rig Summary/5s/AVG & API output ?)
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
As you probably have noticed, there is no space for the Kh/s in the upper row when you are in 1000 range
Mine shows Kh/s
You sure about THAT ?
My API Web App displays whatever it's fed and does so automatically (kh rather than the MH as I showed above)...
(although values are dynamic, units are static in the app and need to be changed....not a big deal)
...
Would it be possible that when in --SCRYPT mode that the units displayed are 100% in KH/s ? (GPU, Rig Summary/5s/AVG & API output ?)
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
Would it be possible that when in --SCRYPT mode that the units displayed are 100% in KH/s ? (GPU, Rig Summary/5s/AVG & API output ?)
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
As you probably have noticed, there is no space for the Kh/s in the upper row when you are in 1000 range
Mine shows Kh/s
so has anyone tested cgminer with 5850s? is it faster than reaper and therefore worth me switching over, or is it roughly the the same hashrate?
I seem to be experiencing a problem with the new CGMiner 2.6.1-official that was not affecting 2.5.0.Scrypt_beta_ee
CGMiner now seems to be seeing cards at times as sick and the program crashes. It has happened to each of my miners at least once since I switched from the 'EE' Beta 2.5.0 yesterday, to 2.6.1 Official.
The last beta ('EE') seemed to run fine for multiple days, but I have yet to experience a SOLID 24 hours from 2.6.1-Official.....without a crash.
The 'EE' version, for reference...
You know it's interesting, I'm in the middle of tracking down the cause of this exact issue for someone else. It turns out that the change to avoid flooding pools on longpoll means I limit outgoing connections - this means there is more likely to be a period a GPU is idle while waiting for work. Now what's interesting is that short periods of idle followed by huge bursts of activity again tend to make cards more unstable than running them flat out 100% of the time. Some testing showed the cards needed to have their clocks decreased quite a lot to be able to tolerate this. So overclocking which was fine before suddenly becomes unstable. I'm experimenting with a feature I call no-idle which gives GPUs fake work to keep them busy to see if this improves stability, but it's still early stages. If you have more stability with the scrypt patched 2.5.0, then by all means go with that for now.CGMiner now seems to be seeing cards at times as sick and the program crashes. It has happened to each of my miners at least once since I switched from the 'EE' Beta 2.5.0 yesterday, to 2.6.1 Official.
The last beta ('EE') seemed to run fine for multiple days, but I have yet to experience a SOLID 24 hours from 2.6.1-Official.....without a crash.
The 'EE' version, for reference...
Could this problem simply be a bi-product of the switch to displaying MH/s while SCRYPT mining in 2.6.1 ?
In the 2.5.0 'EE' SCRYPT Beta, CGMiner displayed KH/s exclusively (GPU, Rig Summary/5s/AVG & API).
In 2.6.1, while SCRYPT mining, CGMiner seems to mix the 2 scales using KH/s for individual GPUs and then MH/s for Rig Summary/5s/AVG & API output.
Isn't this item the most significant difference that has changed from 2.5.0beta to 2.6.1official ? (for SCRYPT mining anyway).
Could the 'sickness' simply be a low value output in MH/s, causing CGMiner to panic ?
Would it be possible that when in --SCRYPT mode that the units displayed are 100% in KH/s ? (GPU, Rig Summary/5s/AVG & API output ?)
Or, perhaps have the option to specify in the CMD line using something like [ --units khash] or [--units mhash] ?
...Just a thought.
thanks again,
bitlane.
Jump to: