Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 313.

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: Sy on October 23, 2014, 04:54:16 AM

So CPU mining is over? Or does the CPU use a different diff (channels?)

I must admit, I don't understand either how the two can coexist.. what is the block reward for the cpu channel ?

Sy

legendary

Activity: 1484

Merit: 1003

Bounty Detective

So CPU mining is over? Or does the CPU use a different diff (channels?)

go6ooo1212

legendary

Activity: 1512

Merit: 1000

quarkchain.io

Thanks , guys , I didn't see the modded exe, and I try it later...

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: McNulty on October 22, 2014, 07:51:37 PM

Quote from: djm34 on October 22, 2014, 06:56:08 PM

Quote from: go6ooo1212 on October 22, 2014, 05:22:08 PM

Would you share some command line , I can't see any command line helpfile...
EDIT: I've set it , but getting only booos on my 900s

that's strange which exe are you using ? (did you recompile with 5.2 ? ).
My 980's are running fine, speed around 50~56MH/s

Regarding the 780, yeah the speed shouldn't be that high, it probably doesn't work properly.
Try the exe by mumus, using as #thread the number of cards.
I'll release soon a more conservative kernel for these cards having problem...

It's already the case, the "original" miner gets only booos

decrease the throughput, although with 4gb... (deactivate sli if it is activated).
The kernel being optimized for the 900's (well at least my 980's) you shouldn't have any problem at all

McNulty

hero member

Activity: 539

Merit: 500

Quote from: djm34 on October 22, 2014, 06:56:08 PM

Quote from: go6ooo1212 on October 22, 2014, 05:22:08 PM

Would you share some command line , I can't see any command line helpfile...
EDIT: I've set it , but getting only booos on my 900s

that's strange which exe are you using ? (did you recompile with 5.2 ? ).
My 980's are running fine, speed around 50~56MH/s

Regarding the 780, yeah the speed shouldn't be that high, it probably doesn't work properly.
Try the exe by mumus, using as #thread the number of cards.
I'll release soon a more conservative kernel for these cards having problem...

It's already the case, the "original" miner gets only booos

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: go6ooo1212 on October 22, 2014, 05:22:08 PM

Would you share some command line , I can't see any command line helpfile...
EDIT: I've set it , but getting only booos on my 900s

that's strange which exe are you using ? (did you recompile with 5.2 ? ).
My 980's are running fine, speed around 50~56MH/s

Regarding the 780, yeah the speed shouldn't be that high, it probably doesn't work properly.
Try the exe by mumus, using as #thread the number of cards.
I'll release soon a more conservative kernel for these cards having problem...

paulthetafy

hero member

Activity: 820

Merit: 1000

guys im still struggling with the linux compilation. I'm now getting...

Code:

make  all-recursive
make[1]: Entering directory `/home/ubuntu/skminer_source'
Making all in compat
make[2]: Entering directory `/home/ubuntu/skminer_source/compat'
make[3]: Entering directory `/home/ubuntu/skminer_source/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/ubuntu/skminer_source/compat'
make[2]: Leaving directory `/home/ubuntu/skminer_source/compat'
make[2]: Entering directory `/home/ubuntu/skminer_source'
make[2]: *** No rule to make target `skminer.o', needed by `skminer'.  Stop.
make[2]: Leaving directory `/home/ubuntu/skminer_source'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ubuntu/skminer_source'
make: *** [all] Error 2

I fixed the "))))" error in configure, ran autogen.sh, ./configure, then make
Any ideas?

go6ooo1212

legendary

Activity: 1512

Merit: 1000

quarkchain.io

Would you share some command line , I can't see any command line helpfile...
EDIT: I've set it , but getting only booos on my 900s

McNulty

hero member

Activity: 539

Merit: 500

yeah, something is wrong

mumus

sr. member

Activity: 291

Merit: 250

Quote from: McNulty on October 22, 2014, 04:27:59 PM

with mumus miner (doesn't work at all with previous one):

Quote

C:\skminer>skminer.exe 127.0.0.1 9325 2
   ***** skMiner for nVidia GPUs by djm34 *****
   This is version v0.1
   based on ccMiner by Christian Buchner and Christian H. 2014 ***
   and on primeminer by Videlicet
   Copyright 2014 djm34
   BTC donation address: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze
Initializing Miner 127.0.0.1:9325 Threads = 2 Timeout = 10
Connected to 127.0.0.1:9325...
[MASTER] Coinshield Network: New Block 23706
[METERS] 2334273060603 Hashes | 138261746.2 kHash/s | Height = 23706
[METERS] 2561923131645 Hashes | 152859375.4 kHash/s | Height = 23706
[METERS] 2579035894005 Hashes | 154147145.7 kHash/s | Height = 23706
[METERS] 2586912797856 Hashes | 154065439.7 kHash/s | Height = 23706
[METERS] 2550900499419 Hashes | 152292567.1 kHash/s | Height = 23706
[METERS] 2575974051720 Hashes | 153688565.8 kHash/s | Height = 23706
[METERS] 2563164645777 Hashes | 153107021.4 kHash/s | Height = 23706
[MASTER] Coinshield Network: New Block 23707
[METERS] 2072607180066 Hashes | 122850286.3 kHash/s | Height = 23707
[METERS] 2582047404636 Hashes | 154142881.3 kHash/s | Height = 23707

with a GTX 780 (win7 x64 344.11 nvidia drivers)

and only 14% GPU usage (i've tried different thread settings, "best" with 1 and 2)

Wow. With your card is 10000x faster than mine. My hash rate is 16000 khas/s

mumus

sr. member

Activity: 291

Merit: 250

Quote from: djm34 on October 22, 2014, 04:25:50 PM

Quote from: mumus on October 22, 2014, 04:04:19 PM

Hi,
After all the miner is working, I've succeed to find blocks both on testnet and main net but it takes some time. The trick is that the above mentioned throughput parameter has to be lowered or the number of threads (which was hard coded to 4) must be lowered. Currently with a single 750ti I can get about 16Mhash/s which was enough to get around 1 block/hour after running 3-4h.
In case someone else want to give a try, here is an updated binary where the number of threads can be specified as a parameter after the port number.

actually it is a bug and shouldn't be a free parameter (well not yet actually and not like that) it should be "num_processors" ie in the context, the numbers of cards (put it in the printf but forgot to put it in the routine). putting a number smaller than the actual number of card will run on a fewer number of cards

When the thread parameter is not specified i took the num_processors

McNulty

hero member

Activity: 539

Merit: 500

with mumus miner (doesn't work at all with previous one):

Quote

C:\skminer>skminer.exe 127.0.0.1 9325 2
   ***** skMiner for nVidia GPUs by djm34 *****
   This is version v0.1
   based on ccMiner by Christian Buchner and Christian H. 2014 ***
   and on primeminer by Videlicet
   Copyright 2014 djm34
   BTC donation address: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze
Initializing Miner 127.0.0.1:9325 Threads = 2 Timeout = 10
Connected to 127.0.0.1:9325...
[MASTER] Coinshield Network: New Block 23706
[METERS] 2334273060603 Hashes | 138261746.2 kHash/s | Height = 23706
[METERS] 2561923131645 Hashes | 152859375.4 kHash/s | Height = 23706
[METERS] 2579035894005 Hashes | 154147145.7 kHash/s | Height = 23706
[METERS] 2586912797856 Hashes | 154065439.7 kHash/s | Height = 23706
[METERS] 2550900499419 Hashes | 152292567.1 kHash/s | Height = 23706
[METERS] 2575974051720 Hashes | 153688565.8 kHash/s | Height = 23706
[METERS] 2563164645777 Hashes | 153107021.4 kHash/s | Height = 23706
[MASTER] Coinshield Network: New Block 23707
[METERS] 2072607180066 Hashes | 122850286.3 kHash/s | Height = 23707
[METERS] 2582047404636 Hashes | 154142881.3 kHash/s | Height = 23707

with a GTX 780 (win7 x64 344.11 nvidia drivers)

and only 14% GPU usage (i've tried different thread settings, "best" with 1 and 2)

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: mumus on October 22, 2014, 04:04:19 PM

Quote from: djm34 on October 22, 2014, 11:00:32 AM

Quote from: mumus on October 22, 2014, 10:52:29 AM

Quote from: Chris84 on October 22, 2014, 10:29:21 AM

Quote from: mumus on October 22, 2014, 10:18:36 AM

Quote from: djm34 on October 22, 2014, 09:12:04 AM

Quote from: mumus on October 22, 2014, 08:47:49 AM

Quote from: djm34 on October 22, 2014, 07:57:35 AM

the 780 is this compute 30 or 35 ?

My 780ti works well on it.
I think too, it is a problem with the gpu not working properly on your card, if it always return, it means it doesn't work properly.
however, the 750ti shouldn't have any problem.

Any of your cards attached to a monitor ?

For info it was compiled with vs2013
and boost 1_56 (the others dependencies being those of ccminers, except for pthread which isn't needed. )

also make sure you have the latest drivers and compiled with cuda 6.5

The miner still doesn't works here.
I'm also using VS2013. I've downloaded and installed the latest driver and CUDA Toolkit today. I'm on Windows 8.1 if that makes any difference. The Nvidia card is the only card in the system and it's attached to the main monitor.

I am also on 8.1, try to go sk1024.cu and replace const int throughput = 512*8 * 512 * 4; by const int throughput = 512*8 * 512 * 2;

Ok. Modifying the throughput parameter did the trick but I had to go down to 512*8 * 512 * 1. (RAM usage on the video card goes up about 1G+). Now the miner started to work reporting about 16000 kHash/s.I'm running the miner against testnetbut still no block was found after about 20min. I guess this is not good.

Did you build the miner with a compute-level, that is supported by your gpu?

My card supports 5.0 and it seams that the project parameters indicates that it's set to 5

it is set to compute 3.0; 3.5 and 5.0 (with the current version don't try to use 5.2, I have finally one version which works with compute 5.2, will update soon... no difference though...)

Hi,
After all the miner is working, I've succeed to find blocks both on testnet and main net but it takes some time. The trick is that the above mentioned throughput parameter has to be lowered or the number of threads (which was hard coded to 4) must be lowered. Currently with a single 750ti I can get about 16Mhash/s which was enough to get around 1 block/hour after running 3-4h.
In case someone else want to give a try, here is an updated binary where the number of threads can be specified as a parameter after the port number.

actually it is a bug and shouldn't be a free parameter (well not yet actually and not like that) it should be "num_processors" ie in the context, the numbers of cards (put it in the printf but forgot to put it in the routine). putting a number smaller than the actual number of card will run on a fewer number of cards
and a larger number will rise cpu usage...

mumus

sr. member

Activity: 291

Merit: 250

Quote from: djm34 on October 22, 2014, 11:00:32 AM

Quote from: mumus on October 22, 2014, 10:52:29 AM

Quote from: Chris84 on October 22, 2014, 10:29:21 AM

Quote from: mumus on October 22, 2014, 10:18:36 AM

Quote from: djm34 on October 22, 2014, 09:12:04 AM

Quote from: mumus on October 22, 2014, 08:47:49 AM

Quote from: djm34 on October 22, 2014, 07:57:35 AM

the 780 is this compute 30 or 35 ?

My 780ti works well on it.
I think too, it is a problem with the gpu not working properly on your card, if it always return, it means it doesn't work properly.
however, the 750ti shouldn't have any problem.

Any of your cards attached to a monitor ?

For info it was compiled with vs2013
and boost 1_56 (the others dependencies being those of ccminers, except for pthread which isn't needed. )

also make sure you have the latest drivers and compiled with cuda 6.5

The miner still doesn't works here.
I'm also using VS2013. I've downloaded and installed the latest driver and CUDA Toolkit today. I'm on Windows 8.1 if that makes any difference. The Nvidia card is the only card in the system and it's attached to the main monitor.

I am also on 8.1, try to go sk1024.cu and replace const int throughput = 512*8 * 512 * 4; by const int throughput = 512*8 * 512 * 2;

Ok. Modifying the throughput parameter did the trick but I had to go down to 512*8 * 512 * 1. (RAM usage on the video card goes up about 1G+). Now the miner started to work reporting about 16000 kHash/s.I'm running the miner against testnetbut still no block was found after about 20min. I guess this is not good.

Did you build the miner with a compute-level, that is supported by your gpu?

My card supports 5.0 and it seams that the project parameters indicates that it's set to 5

it is set to compute 3.0; 3.5 and 5.0 (with the current version don't try to use 5.2, I have finally one version which works with compute 5.2, will update soon... no difference though...)

Hi,
After all the miner is working, I've succeed to find blocks both on testnet and main net but it takes some time. The trick is that the above mentioned throughput parameter has to be lowered or the number of threads (which was hard coded to 4) must be lowered. Currently with a single 750ti I can get about 16Mhash/s which was enough to get around 1 block/hour after running 3-4h.
In case someone else want to give a try, here is an updated binary where the number of threads can be specified as a parameter after the port number. (for example: skminer.exe 127.0.0.1 9325 1) I use 1 thread for my single card.
https://mega.co.nz/#!SYlHEA5b!LBCpXiW9YRAi1-5opgaMbXMO4N3Xux6o6MMrKLbrQC0

cestballot

sr. member

Activity: 318

Merit: 250

Nexus pool : http://nexusniropool.cestballot.fr/

wow, probably the most fair/unfair launch I have never seen.

Lips sealed

go6ooo1212

legendary

Activity: 1512

Merit: 1000

quarkchain.io

Is there any pool running it?

totoy

hero member

Activity: 623

Merit: 500

Quote from: yampi on October 22, 2014, 01:06:00 PM

Difficulty is supposed to be approximately around 6, yet it's been showing like that for a while.
Minor little bug, I guess?

Quote from: Videlicet on October 22, 2014, 04:22:45 AM

Working on this at the moment. The difficulty is calculated properly, just the display number is incorrect. I'll post 1.0.1c with the fixes to give accurate difficulty numbers when finished.

Viz.

yampi

sr. member

Activity: 433

Merit: 250

Code:

{
"blocks" : 23508,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000038,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"pooledtx" : 0,
"testnet" : false
}

Difficulty is supposed to be approximately around 6, yet it's been showing like that for a while.
Minor little bug, I guess?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: yampi on October 22, 2014, 12:13:35 PM

1. Download CUDALOADER
2. Open CUDA Miner with it
3. Huh

??
4. Profit.

read the date of that article...

yampi

sr. member

Activity: 433

Merit: 250

It is kind of funny how CUDA miner was finished earlier than OpenCL.

Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 313. (Read 785531 times)