I still have problems with two rigs shutting themself down from time to time but i think that is due to faulty gpu:s involved in those rigs.
The motherboard could be out of power. remove a card and see if it helps over time.
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 942. (Read 2347664 times)
The motherboard could be out of power. remove a card and see if it helps over time.
I switched build from r61 to r67 on all my Nvidia gear and i got slightly slower speed per card reported by ccminer but noticed that my rejected hash at NiceHash went down a bit.
One day of mining donated and on its way:
https://blockchain.info/tx/a13c767b0d1940e769fa72927cbfccbc3787c040df1a02951fb20efc55200180
One day of mining donated and on its way:
https://blockchain.info/tx/a13c767b0d1940e769fa72927cbfccbc3787c040df1a02951fb20efc55200180
Thanks alot:) Release 68 will be faster.
I have submitted fixes in the atomic conversions. Lyra2v2 should now be fine.
But Djm-34's private kernal is doing 6.2MHASH on the 750ti. That is why lyra2v2 is not profitable to mine...
lolwut !? yeah it's my fault... sure 
please spare me this kind of bullshit...
(if it was an attempt at motivating me to release it... it pretty much failed...
)You have the fastest kernal in the world. You are the best optimizer in the lyra2v2 algo for the 750ti.
TSIV has already reached 5,7MHASH.
Without opensourcing, someone else will make a faster kernal. It's just a matter of time.
But Djm-34's private kernal is doing 6.2MHASH on the 750ti. That is why lyra2v2 is not profitable to mine...
lolwut !? yeah it's my fault... sure please spare me this kind of bullshit...
(if it was an attempt at motivating me to release it... it pretty much failed...
)
I switched build from r61 to r67 on all my Nvidia gear and i got slightly slower speed per card reported by ccminer but noticed that my rejected hash at NiceHash went down a bit.
I still have problems with two rigs shutting themself down from time to time but i think that is due to faulty gpu:s involved in those rigs.
One day of mining donated and on its way:
https://blockchain.info/tx/a13c767b0d1940e769fa72927cbfccbc3787c040df1a02951fb20efc55200180
I still have problems with two rigs shutting themself down from time to time but i think that is due to faulty gpu:s involved in those rigs.
One day of mining donated and on its way:
https://blockchain.info/tx/a13c767b0d1940e769fa72927cbfccbc3787c040df1a02951fb20efc55200180
I think problem start from commit "Removed some more instructions in Blake512, Bmw512,lyra2 and lyra2v2".
found it now. Will submitt a fix.
But Djm-34's private kernal is doing 6.2MHASH on the 750ti. That is why lyra2v2 is not profitable to mine...
SP_ (and all ccminer devs) you made really great job. lyra2v2 hashing extremely fast on such small cards.
after couple hours of playing with configs i could reach:
after couple hours of playing with configs i could reach:
Code:
[2015-09-17 17:38:00] GPU #0: GeForce GTX 750 Ti, 5025 Temp= 50C Fan= 41%
crazy speed.Can anyone else build the latest on git and test it. lyra2v2 (linux)
Just pulled (latest commit is t-nelson logger stuff), hashing to nicehash and nothing submitted:I think lyra2v2 was broken some checkins ago. Probobly in the hashing. I will take a look later.
So you're telling me I'm probably not going to find a block and trigger this crash @HEAD?
I've locally reverted the commit mentioned by Slava_K. Hopefully that does the trick.
I think problem start from commit "Removed some more instructions in Blake512, Bmw512,lyra2 and lyra2v2".
Can anyone else build the latest on git and test it. lyra2v2 (linux)
Just pulled (latest commit is t-nelson logger stuff), hashing to nicehash and nothing submitted:I think lyra2v2 was broken some checkins ago. Probobly in the hashing. I will take a look later.
I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.
What is this witchery? Not that I'm complaining...
BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c
which distro did you use? ... redhat based or debian based? ...What is this witchery? Not that I'm complaining...
BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c
My miner is on CentOS6, because nvidia's debian repository was acting up at the time.
My desktop is on Ubuntu. I don't like it that much, but once you clean it up, it's okay. And the list of supported OSes from nvidia is so short it doesn't leave much of a choice.
Can anyone else build the latest on git and test it. lyra2v2 (linux)
Just pulled (latest commit is t-nelson logger stuff), hashing to nicehash and nothing submitted:[2015-09-17 08:34:35] Stratum difficulty set to 2
[2015-09-17 08:34:36] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:34:59] GPU #0: GeForce GTX 750 Ti, 3994 Temp= 46C Fan= 90%
[2015-09-17 08:34:59] GPU #1: GeForce GTX 750 Ti, 4499 Temp= 47C Fan= 90%
[2015-09-17 08:35:24] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:35:24] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 48C Fan= 90%
[2015-09-17 08:35:24] GPU #0: GeForce GTX 750 Ti, 3991 Temp= 47C Fan= 90%
[2015-09-17 08:35:25] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:35:25] GPU #1: GeForce GTX 750 Ti, 4486 Temp= 48C Fan= 90%
[2015-09-17 08:35:25] GPU #0: GeForce GTX 750 Ti, 3952 Temp= 47C Fan= 90%
[2015-09-17 08:35:46] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:35:46] GPU #0: GeForce GTX 750 Ti, 3969 Temp= 47C Fan= 90%
[2015-09-17 08:35:46] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 49C Fan= 90%
[2015-09-17 08:36:06] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:06] GPU #0: GeForce GTX 750 Ti, 3969 Temp= 48C Fan= 90%
[2015-09-17 08:36:06] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 50C Fan= 90%
[2015-09-17 08:36:35] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:35] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:35] GPU #0: GeForce GTX 750 Ti, 3953 Temp= 48C Fan= 90%
[2015-09-17 08:36:35] GPU #1: GeForce GTX 750 Ti, 4497 Temp= 50C Fan= 90%
[2015-09-17 08:36:35] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:36:35] GPU #0: GeForce GTX 750 Ti, 3917 Temp= 48C Fan= 90%
[2015-09-17 08:36:35] GPU #1: GeForce GTX 750 Ti, 4486 Temp= 50C Fan= 90%
[2015-09-17 08:37:01] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:37:01] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 50C Fan= 90%
[2015-09-17 08:37:01] GPU #0: GeForce GTX 750 Ti, 3968 Temp= 48C Fan= 90%
[2015-09-17 08:37:02] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369266
[2015-09-17 08:37:02] GPU #1: GeForce GTX 750 Ti, 4496 Temp= 50C Fan= 90%
[2015-09-17 08:37:02] GPU #0: GeForce GTX 750 Ti, 3895 Temp= 48C Fan= 90%
[2015-09-17 08:37:03] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:03] GPU #0: GeForce GTX 750 Ti, 3902 Temp= 48C Fan= 90%
[2015-09-17 08:37:03] GPU #1: GeForce GTX 750 Ti, 4496 Temp= 50C Fan= 90%
[2015-09-17 08:37:27] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:27] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:27] GPU #1: GeForce GTX 750 Ti, 4497 Temp= 50C Fan= 90%
[2015-09-17 08:37:27] GPU #0: GeForce GTX 750 Ti, 3937 Temp= 48C Fan= 90%
[2015-09-17 08:37:35] Stratum difficulty set to 1
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:53] GPU #1: GeForce GTX 750 Ti, 4497 Temp= 51C Fan= 90%
[2015-09-17 08:37:53] GPU #0: GeForce GTX 750 Ti, 3978 Temp= 48C Fan= 90%
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:53] GPU #0: GeForce GTX 750 Ti, 3880 Temp= 49C Fan= 90%
[2015-09-17 08:37:53] GPU #1: GeForce GTX 750 Ti, 4490 Temp= 50C Fan= 90%
[2015-09-17 08:37:53] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369267
[2015-09-17 08:37:54] GPU #1: GeForce GTX 750 Ti, 4495 Temp= 50C Fan= 90%
[2015-09-17 08:37:54] GPU #0: GeForce GTX 750 Ti, 3889 Temp= 48C Fan= 90%
[2015-09-17 08:38:04] lyra2rev2.eu.nicehash.com:3347 lyra2v2 block 369268
[2015-09-17 08:38:04] GPU #0: GeForce GTX 750 Ti, 3965 Temp= 48C Fan= 90%
[2015-09-17 08:38:04] GPU #1: GeForce GTX 750 Ti, 4498 Temp= 51C Fan= 90%
Is the block number supposed to repeat like that?
To answer my own question: No it is not.
Quote
is there any way you could supply methe table of default intensities and special command paramaters ( if there are any - as i know scrypt and another algo use more parameters ( like thoughput and so forth ) ) ? ...
i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...
#crysx
i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...
#crysx
Seems like this question was asked by you several time to sp_ already, but i think it's not difficult to check by yourself.
what i did to check it in linux:
Code:
grep -rnw '/you/path/to/folder/ccminer-1.5.67/' -e "pattern"
where pattern - intensity
where pattern - intensity
in input you will see that this info (ofcourse different files for different algo. example for lyra2v2)
Code:
/lyra2/lyra2REv2.cu:85: uint32_t intensity = 256 * 256 * 8;
lets check this file lyra2REv2.cu
Code:
if (strstr(props.name, "970"))
{
intensity = 256 * 256 * 18;
tpb = 9;
}
else if (strstr(props.name, "980"))
{
intensity = 256 * 256 * 18;
tpb = 7;
}
else if (strstr(props.name, "750 Ti"))
{
intensity = 256 * 256 * 16;
tpb = 16;
}
else if (strstr(props.name, "750"))
{
intensity = 256 * 256 * 5;
tpb = 7;
}
else if (strstr(props.name, "960"))
{
intensity = 256 * 256 * 16;
tpb = 7;
}
{
intensity = 256 * 256 * 18;
tpb = 9;
}
else if (strstr(props.name, "980"))
{
intensity = 256 * 256 * 18;
tpb = 7;
}
else if (strstr(props.name, "750 Ti"))
{
intensity = 256 * 256 * 16;
tpb = 16;
}
else if (strstr(props.name, "750"))
{
intensity = 256 * 256 * 5;
tpb = 7;
}
else if (strstr(props.name, "960"))
{
intensity = 256 * 256 * 16;
tpb = 7;
}
i think this can be an answer about default intensity settings.
P.S. i'm not dev, just lot of years with linux. maybe this info wrong.
P.P.S. i'm super amator in mining, only for 2-3 days, but already find that it's really interesting. Thanks for dev that support that ccminer project.
I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.
I usually use the internal gpu of the motherboard to do the display in windows, and the cards 100% for mining.
...anyway ... i have reverted back to x11 sp ... v67 doesnt seem to have any issues whatsoever with the algo - even compiled in cuda 7 ...
is there any way you could supply methe table of default intensities and special command paramaters ( if there are any - as i know scrypt and another algo use more parameters ( like thoughput and so forth ) ) ? ...
i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...
-i 22.9 is good. I think scryptr is using -i 23.5 on linux.
The problem is that the optimal intensity is different from card to card and build to build.
I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.
I usually use the internal gpu of the motherboard to do the display in windows, and the cards 100% for mining.
which simply means you require two gpus to do that - where as we only need the one ...
...anyway ... i have reverted back to x11 sp ... v67 doesnt seem to have any issues whatsoever with the algo - even compiled in cuda 7 ...
is there any way you could supply methe table of default intensities and special command paramaters ( if there are any - as i know scrypt and another algo use more parameters ( like thoughput and so forth ) ) ? ...
i can compile them and collate them in one place so that everyone can use them as a reference for the different cards they use ...
#crysx
I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.
I usually use the internal gpu of the motherboard to do the display in windows, and the cards 100% for mining.
so i can use only default Intensity which is hardcoded to miner. but with such default config i can get only 2.8mh seems like to low.
The speed depends on the clock on the on the Card, and if you have a 6 pin power adapter on the card.
Some cards are clock higher as default. X11 will perform above 3MHASH with a core of 1350Mz and up to 3400-3500 with 1500 Mz
I use .67 A good result for the GTH 960.
Ps. I do not know how correctly sent to the creator of the beer, let it be income for the day. For _SP transaction ID
7d52b98dc6448bdfdcd64fafc3fffb20a2d641a8e867ac591878cdd4e2b298bc
Ps. I do not know how correctly sent to the creator of the beer, let it be income for the day. For _SP transaction ID
7d52b98dc6448bdfdcd64fafc3fffb20a2d641a8e867ac591878cdd4e2b298bc
Thanks for your support.
I just switched my desktop (the one with the GTX970 G1 Gaming) from windows to linux and got a very nice surprise: on windows, when mining, the mouse is lagging and the machine is pretty much unusable. On linux, no such thing! The machine is happily mining Quark at 17MH while I watch a 1080p video on Youtube.
What is this witchery? Not that I'm complaining...
BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c
What is this witchery? Not that I'm complaining...
BTW, it's about time for my donation, so here's a beer SP: 3bb1e5e50d3967cfc8f5e14aa700c316fc69c45380fcad938aed2d67fc62615c
Thanks for your support.
Jump to: