CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 946.

serg_25

newbie

Activity: 51

Merit: 0

Guys what i'm doing wrong...
git clone https://github.com/sp-hash/ccminer.git
./autogen.sh
./configure.sh
everything is fine here.
but when i try to make:

Code:

/usr/local/cuda/bin/nvcc -gencode=arch=compute_52,code=\"sm_52,compute_52\" -gencode=arch=compute_50,code=\"sm_50,compute_50\" -I/usr/local/cuda/include -I. -O3 -Xcompiler -Wall  --ptxas-options="-v" --maxrregcount=128 -o heavy/heavy.o -c heavy/heavy.cu
nvcc fatal   : Unsupported gpu architecture 'compute_52'
make[2]: *** [heavy/heavy.o] Error 1

i'm using GTX 750Ti card and

Code:

nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2014 NVIDIA Corporation
Built on Thu_Jul_17_21:41:27_CDT_2014
Cuda compilation tools, release 6.5, V6.5.12

Thanks

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Sorry. It was the minercontrol software I use that produce this file

but you can always run ccminer with >logfile.log in the end. Then all the output to the shell will be to file instead.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: sp_ on September 16, 2015, 10:47:31 AM

Can I see your error.log file on the time of the crash?

ERROR.LOG--

I wasn't logging the event. I just took a quick look at CCminer "help" and I do not see a "log" command, although I do see a "-D" debug comand. I never bothered to create an "error.log" file, actually.

There are several new command line switches not documented in the "help" output.

I could solo-mine again, but it means going without coin. I still would like to understand the miner better. --scryptr

qqqq

legendary

Activity: 1596

Merit: 1011

Quote from: sp_ on September 16, 2015, 10:47:31 AM

Can I see your error.log file on the time of the crash?

Do your miner has a logger system ? Cause i didn't find some flags like cgminer's 2>logfile.txt
And i can't find any error.log file in folder with miner.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Can I see your error.log file on the time of the crash?

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: qqqq on September 16, 2015, 09:22:14 AM

Quote from: scryptr on September 16, 2015, 09:16:57 AM

Quote from: antonio8 on September 16, 2015, 06:48:55 AM

Quote from: sp_ on September 16, 2015, 06:23:54 AM

Wich version is it working in?

You can try to set:

LP_SCANTIME 60

instead of 25 in ccminer.cpp

I'll try and find the version but none of the .60's have worked solo mining for me.

SCANTIME--

Sorry for my ignorance, but I need an explanation of what "scantime" actually does. I spent more than 24 hours solo-mining, and apparently found 3 or 4 blocks of VTC. I never was credited the blocks because of the crashes. So, about the time I should be getting an "accepted" message, something goes wrong.

The miner just crashed. I didn't know why at the time, but it occured about the same frequency at which I should be finding blocks.

--scryptr

Same case but one crash is enough for me to understand that has a bug.

From http://cryptomining-blog.com/ - We are experiencing some issues with this release for solo mining, so you might want to stick to 66 or earlier for local wallet mining, the miner seems to be crashing when it finds a block.

VERSION dot 66--

I was solo-mining with version 66. There was a string of posts several pages back about solo-mining, that is why I attempted to solo-mine VTC. Several miners were trying to find a version of CCminer that works solo-mining. And, I did read the CryptoMining Blog article.

Release dot 66 hashes away at VTC, communicates with the wallet, and crashes on finding a block. I will also say that even though I used a similar setup for FeatherCoin, I was not able to communicate properly with the wallet, and could not generate hash for FTC. FTC is really a better candidate for solo-mining at its current difficulty.

--scryptr

qqqq

legendary

Activity: 1596

Merit: 1011

Quote from: scryptr on September 16, 2015, 09:16:57 AM

Quote from: antonio8 on September 16, 2015, 06:48:55 AM

Quote from: sp_ on September 16, 2015, 06:23:54 AM

Wich version is it working in?

You can try to set:

LP_SCANTIME 60

instead of 25 in ccminer.cpp

I'll try and find the version but none of the .60's have worked solo mining for me.

SCANTIME--

Sorry for my ignorance, but I need an explanation of what "scantime" actually does. I spent more than 24 hours solo-mining, and apparently found 3 or 4 blocks of VTC. I never was credited the blocks because of the crashes. So, about the time I should be getting an "accepted" message, something goes wrong.

The miner just crashed. I didn't know why at the time, but it occured about the same frequency at which I should be finding blocks.

--scryptr

Same case but one crash is enough for me to understand that has a bug.

From http://cryptomining-blog.com/ - We are experiencing some issues with this release for solo mining, so you might want to stick to 66 or earlier for local wallet mining, the miner seems to be crashing when it finds a block.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: antonio8 on September 16, 2015, 06:48:55 AM

Quote from: sp_ on September 16, 2015, 06:23:54 AM

Wich version is it working in?

You can try to set:

LP_SCANTIME 60

instead of 25 in ccminer.cpp

I'll try and find the version but none of the .60's have worked solo mining for me.

SCANTIME--

Sorry for my ignorance, but I need an explanation of what "scantime" actually does. I spent more than 24 hours solo-mining, and apparently found 3 or 4 blocks of VTC. I never was credited the blocks because of the crashes. So, about the time I should be getting an "accepted" message, something goes wrong.

The miner just crashed. I didn't know why at the time, but it occured about the same frequency at which I should be finding blocks.

--scryptr

chrysophylax

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

Quote from: theotherme on September 16, 2015, 04:04:57 AM

Quote from: serg_25 on September 16, 2015, 03:18:49 AM

Hi miners.
Can you please advice, for 750Ti card what is the best Nvidia driver version for linux x64?
in Ubuntu official repo stable is this one - NVIDIA binary driver - version 340.76

P.S. as i understand from this thread, CUDA must be 6.5.

The easiest, is probably to keep the drivers which get installed when CUDA 6.5 gets installed.

in fedora 20 x64 - the latest of the drivers are very stable ... so it is a situation of whether you want to muck around with settings to get the best one - or ( as suggested ) stay with the drivers that are installed ...

as for it being a 'must' with cuda - 6.5 is the most stable AND the highest hashrate ... technically it will compile and run using the 'other' cuda kits - but not well ... i also have a fedora 22 x64 with cuda 7.0.28 and that is running very stable now using x11 ( and a couple of other algos - though you do get errors with most algos ) but at the loss of hashrate ...

so it doesnt HAVE to be cuda 6.5 - but you are much better off with it ... as cuda 7.0 and 7.5 so far come out with lots of other issues ...

#crysx

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

This is a bug T Nelson is good at finding..

Solomine in a testnet with low hashrate. Probobly a division by zero or something in the hashrate statistics.

antonio8

legendary

Activity: 1400

Merit: 1000

Quote from: sp_ on September 16, 2015, 06:23:54 AM

Wich version is it working in?

You can try to set:

LP_SCANTIME 60

instead of 25 in ccminer.cpp

I'll try and find the version but none of the .60's have worked solo mining for me.

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: sp_ on September 16, 2015, 06:23:54 AM

Wich version is it working in?

You can try to set:

LP_SCANTIME 60

instead of 25 in ccminer.cpp

is it different than using "-s"?

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Wich version is it working in?

You can try to set:

LP_SCANTIME 60

instead of 25 in ccminer.cpp

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: qqqq on September 16, 2015, 01:40:55 AM

When issue with solo mining will be fixed ? I mean crashing miner when block is found. http://cryptomining-blog.com/5730-updated-windows-binary-of-the-ccminer-1-5-67-git-fork-by-sp-for-maxwell/

66 release has the same problem also.

IT DOES CRASH--

I suspected as much when I set it up to mine VTC solo. The miner crashed 3-4 times, about the same frequency at which I should be finding blocks. Each different rig crashed at least once. The blocks never made their way to my wallet; I gave up in frustration. It looked to be working properly. I was using release dot 66.

--scryptr

theotherme

member

Activity: 81

Merit: 10

Quote from: serg_25 on September 16, 2015, 03:18:49 AM

Hi miners.
Can you please advice, for 750Ti card what is the best Nvidia driver version for linux x64?
in Ubuntu official repo stable is this one - NVIDIA binary driver - version 340.76

P.S. as i understand from this thread, CUDA must be 6.5.

The easiest, is probably to keep the drivers which get installed when CUDA 6.5 gets installed.

serg_25

newbie

Activity: 51

Merit: 0

Hi miners.
Can you please advice, for 750Ti card what is the best Nvidia driver version for linux x64?
in Ubuntu official repo stable is this one - NVIDIA binary driver - version 340.76

P.S. as i understand from this thread, CUDA must be 6.5.

qqqq

legendary

Activity: 1596

Merit: 1011

When issue with solo mining will be fixed ? I mean crashing miner when block is found. http://cryptomining-blog.com/5730-updated-windows-binary-of-the-ccminer-1-5-67-git-fork-by-sp-for-maxwell/

66 release has the same problem also.

t-nelson

member

Activity: 70

Merit: 10

Quote from: scryptr on September 15, 2015, 03:49:48 PM

Quote from: sp_ on September 14, 2015, 03:58:03 PM

Quote from: Cryptozillah on September 14, 2015, 07:41:27 AM

All systems have fresh Win 8.1 installations.
I am running the 355.60 Driver on all rigs and i am using the 61 build due to best performance for me with that one.

Can you try build 67 please.

Do you have a cudart32_65.dll in the ccminer folder?

Downgrading the driver could increase by 200-300KHASH per 750ti. (Hot tip

)

Don't forget to donate guys.

TWO NICKLES...

I flipped both you and t-nelson a nickle. The work fixing the "ctrl-c" exit, and the "cpu-mining" switch were both significant contributions. The hash rate really went up on my 970s with the "cpu-mining" switch, frm 14.5Mh/s to 16.5 -17Mh/s. My 750ti cards also do better.

Thank you! --scryptr

Danke!

chrysophylax

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

Quote from: pallas on September 15, 2015, 08:08:57 AM

Quote from: chrysophylax on September 15, 2015, 07:47:57 AM

Quote from: sp_ on September 15, 2015, 06:51:37 AM

Here is from the DJM-34 code: default lyra2v2 intensites.

unsigned int intensity = 256*256*8;
intensity = (device_sm[device_map[thr_id]] == 500) ? 256 * 256 * 4 : intensity;

-X 8 on gtx ,950,960,970, 980,980ti
-X 4 on gtx 750,750ti

While in my modded lyra2v2 I use

-X 18 on 970,980,980ti
-X 16 on 750ti
-X 5 on 750
-x 16 on 960

With my mod (sp-mod 67) lyra2v2 is doing 5 MHASH with overclocking. DJM34's is doing 4,5 with overclocking.

(My version is around 10% faster on the 750ti)

sp - would it be too difficult to setup a table of the default intensities for the various algorithms used by his fork? ...

that would help greatly with a LOT of the issues that are present ...

i can even set one up - but i would need to be updated regularly and consistently for any changes that will occur between updates ...

btw - donation links are ready - and will be published in the next couple of days ( when i get back to the office ) ... they test well with thefarm - but would like to test them with community support with mining - for donations ( if of course you want to donate that way ) ...

#crysx

what about making a header file with a data structure containing all the default intensities?
and maybe other miner settings...

that would be good - though i believe placing all the default intensities and settings would be more beneficial on the op - unless they change way too often ...

i just think that there is no where near enough information to users ( veteran and new miners alike ) to get the most out of the mining experience ... and the best hashrate ...

too high intensity - too low - just right - extra parameters on some algos ( like 'throughput' ) - common settings - etc ...

none of this exists ...

even as a veteran miner - i STILL dont understand 'throughput' or '0xblah' parameters in certain algos ... there is no documentation or direction ... we all just have to wing it - and hope for the best - AND ask questions here that would not have to be asked ( cluttering the input to the page - and announcements ( yes - im VERY guilty of that ) ) had there been the relevant info in the first place ...

i would be more than happy to compile such a list - and keep it updated - as long as i have ALL the relevant info at my beckon call ...

ONE resource - ONE place - ONE list ... copied all over the place - that EVERYONE can use to reference ...

ill even start a new thread for it today if that sounds like a good idea to everyone ...

btw pallas - will be responding to the pm today ... ive just been inundated unfortunately - and wont have much 'free' time ( pfft - as if ) till next week ... i really appreciate your ideas and input ...

#crysx

Strannik-74

full member

Activity: 348

Merit: 102

del =)

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 946. (Read 2347664 times)