|
just to add a little to the offtopic... linux support is currently outstanding compared to what it was when I started using it, in 1993! ;-)
so, a great improvement and counting.
it's the most widespread operating system for a reason; it just doesn't have the desktop crown (yet).
in this specific case, it's just that most miners are using windows: if we all start using linux, miner developers wouldn't care to do the win versions and they would also save time and resources.
|
|
|
|
opencl.dll form 14.12? Where can I get the file?
I believe you can extract it from the driver package, but I'm a linux guy so I never tried it myself. |
|
|
|
But i think it's probably drivers' fault
if you are on windows, you can keep your driver and compile the opencl on 14.12 just by putting opencl.dll in the miner's folder. |
|
|
|
80°C for a GTX980 is a normal operating temperature. I have a similar setup (two GTX 980 evga) and with quark algo and a reasonable overclock ( +100 but they are already oc : so I ran them at about 1500mhz @gpu) they are between 77-80.
Those mining with amd card are used to go higher!!!
I've mined at 94C for months ;-) we have destroyed about 16 x gigabyte 280x oc cards with those temps ... 1 x gigabyte 750ti oc ( powered ) has a fan that is shutdown due to temps as well ... thank God they have a 3 year warranty ...  ... #crysx maybe the 290(x) is different, one of them run for about a year at 94C and is still fine, overclocking and all :-) |
|
|
|
{
"pools" : [
{
"name" : "NiceHash_Lyra2RE",
"url" : "ca.simplemulti.com:3374",
"user" : "VpzyncgawVk3kC7Yp5M8YHVcS97bYLvQCs",
"pass" : "x",
"algorithm" : "Lyra2RE",
"intensity" : "18",
"gpu-engine" : "935",
"gpu-memclock" : "1500",
"worksize" : "128",
"gpu-threads" : "2"
},
}
Drivers the latest 15.4 Beta
try: "intensity" : "15", "gpu-engine" : "835", I never tried compiling the opencl code using 15.4: it might need tweaking for that version. You can try 14.12 or I can send you the precompiled bin (64 bit for hawaii). |
|
|
|
80°C for a GTX980 is a normal operating temperature. I have a similar setup (two GTX 980 evga) and with quark algo and a reasonable overclock ( +100 but they are already oc : so I ran them at about 1500mhz @gpu) they are between 77-80.
Those mining with amd card are used to go higher!!!
I've mined at 94C for months ;-) |
|
|
|
I'm having 800kh on my r 290 ( 3GB ) what's the problem?
Which driver version are you using? Which settings: clocks, intensity etc.? Please paste the full commandline or conf file. |
|
|
|
|
are you saying that cpu coins are going better? or PoS?
|
|
|
|
Does anyone have a way to make this work with 290x?
If you are talking about the Russian optimised miner for quark and qubit, try renaming the Tahiti binary to Hawaii. Worked for some. |
|
|
|
in fact its just a coding copy paste typo from cpu or ccminer code...
Originally from sph -sgminer, not a copy paste typo, just bad precompiler code ;-) |
|
|
|
With the real sgminer i hit 4.6Mh/s and with that strange "sgminer-with-optimized-quark-and-qubit-kernels" i can not even score a little 1Mh/s.
The results are real. I also got bad results with 14.6, but decided to try with 15.4 beta, and confirm the results. without much effort 280x 10,1 m gpu/mem 1050/1500 -g 1 -w 64 -X 64 Works with Hawaii also. And on *nix. the bins on linux? ... how? ... please do tell  ... #crysx quarkcoinTahitigw64l4ku0.bin > win quarkcoinTahitigw64l8ku0.bin > lin no: l4 = 4 octects = 32 bit binary l8 = 8 octects = 64 bit binary they both work on windows and linux, but on linux we do not have the modified miner to run them with. again: different kernels with different parameters than stock miner! |
|
|
|
did some optimization on quark: +75% (roughly)  yeah... well 10 Mh/s on 750Ti?? That's really great!! will you merge the mods, make a new repo or sell it? |
|
|
|
he said and i quote AGAIN
You are a believer and you mine a coin to help with its network; in this case you shouldn't care about profits etc.
Even if you mine a coin with low payout, as a believer your belief is that the coin will someday be successful and you are contributing to that success. A believer's reasons may be different than a skilled investor but both expect profit. Even someone actually not mining a coin for profit, a coin's dev perhaps, would be invested in the coin in other ways where they do expect a profit. by "help with its network" I mean increase the hashrate in order to secure it. if you plan to sell the coin, it means you don't believe in it: if you do, you should plan to keep and use it directly. |
|
|
|
|
I just wonna say that if you plan to mine a coin and wait for it to rise in value, then you'd better buy it and save the hassle.
If you have a good margin on mining, which happens to the few people who can optimize the miner themselves or have very low electricity cost, then mine the coin with better margin, sell it for BTC and back to point one.
Or
You are a believer and you mine a coin to help with its network; in this case you shouldn't care about profits etc.
|
|
|
|
Just for fun: managed to run it on my gtx 750.
It gives 650 khs instead of 880khs with sp_'s ccminer. Not bad but cpu usage is huge.
In order to make it work I needed to change long long constants in Lyra2cl to unsigned long as long long is not supported in nvidia opencl
__constant static const sph_u64 blake2b_IV[8] =
{
0x6a09e667f3bcc908UL, 0xbb67ae8584caa73bUL,
0x3c6ef372fe94f82bUL, 0xa54ff53a5f1d36f1UL,
0x510e527fade682d1UL, 0x9b05688c2b3e6c1fUL,
0x1f83d9abfb41bd6bUL, 0x5be0cd19137e2179UL
};
Then it was an error in keccak1600.cl with
inline void keccak_block(ulong *s) {
I added static
inline static void keccak_block(ulong *s) {
and the problems seems to vanish.
Then it was an error with 2d array init skein256.cl
__constant static const ulong ROT256[8][4] = {
46, 36, 19, 37,
33, 27, 14, 42,
17, 49, 36, 39,
44, 9, 54, 56,
39, 30, 34, 24,
13, 50, 10, 17,
25, 29, 39, 43,
8, 35, 56, 22,
};
I've added more {} to form this
__constant static const ulong ROT256[8][4] = {
{46, 36, 19, 37},
{33, 27, 14, 42},
{17, 49, 36, 39},
{44, 9, 54, 56},
{39, 30, 34, 24},
{13, 50, 10, 17},
{25, 29, 39, 43},
{8, 35, 56, 22}
};
And it finally got compiled.
It works and receives "accepted" from the pool )))
I used "intensity" : "14", "worksize" : "512", "gpu-threads" : "1" to run ...
gpu_z shows 100% load for gpu engine and memory, the same is with ccminer )))
Thanks very much for testing this! Long long is not used on amd, there is an ifdef which defines sph_u64 differently on nvidia (legacy sph stuff I didn't care to polish yet). I will update the two archives and the post, to add intel and nvidia compatibility, later. High cpu usage can be avoided by setting GPU_USE_SYNC_OBJECTS=1, don't know if there is an equivalent for nvidia. |
|
|
|
What speed are people getting with this miner with the omega 14.12 drivers?
I've been using omega drivers when developing it. |
|
|
|
Congrats Pallas
Your Miner/Kernel combination allowed me to tap into my Lenovo intel graphics for another 100Kh. I appreciate it.
Do the other kernels work I tried them multiple times but I can not get them to work on the intel graphics but the Lyra works great.
Thanks again.
Glad it works on Intel GPUs as well! :-) About the other kernels, you can try adding the missing .cl files into the kernel folder, getting them from the stock sgminer. Not guaranteed to work.... |
|
|
|
|
Max worksize is 256. If you put a higher number, it still uses 256 (just look at the bin filename).
|
|
|
|
|
On a site whose goal is making money, security should be the main concern. On all sites it should be, IMHO.
It should open after at least a penetration test and a security audit.
|
|
|
|
|
Show Posts
