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

[ManiacMiner]

One question:  I have 3x750Ti (device 0,1,2) but if i want run only device 0 and 2 without 1 card. If setup in miner skminer.exe 127.0.0.1 9325 2 works devices 0,1 but i need 0,2. How can i do it with this miner. Thanks.

[antonio8]

You can share your .bat file here and a screenshot of the error, how many cards do you have?

Here is my bat for the computer with the wallet and 750ti's (total of 5):   skminer.exe 127.0.0.1 9325 5 20

On the image I don't have an account anywhere to upload and not sure how to insert but it says

Initializing Miner 127.0.0.1:9325 Threads = 5 Timeout = 20
connected to 127.0.0.1:9325...
[Master] Failed to Update Height
Connected to 127.0.01:9325...
[Master] Failed to Update Height
Repeats this until I terminate the miner

The computer with the 970 shows the same thing except for the 127.0.0.1 it has the ip address of the computer with the wallet running.

I have a config file to solo from another computer and it is:
rpcuser=MYUSER
rpcpassword=MYPASS
rpcallowip=127.0.0.*
rpcport=9325
server=1
daemon=1
listen=1

The wallet was created with a short cut and I went into properties and added the -server.

This is always how I have solo mined and haven't had any issues.

Your problem was that you've specified in the config file the rpcport=9325. This wallet has a separate channel and protocol (LLP) with a separate port to communicate with the solo miner. It doesn't uses RPC for it and the default RPC port is different.
[/quote]

Thanks for the explanation mumus.

I was just so used to solo mining I never thought about not needing the rpcport in or even needing a config file.

[djm34]

One question:  I have 3x750Ti (device 0,1,2) but if i want run only device 0 and 2 without 1 card, how can i do it with this miner, or this impossible now? Thanks.

for the moment you can't, however if you use a number of processor smaller than the number of card, then one of the gpu won't be used...
(obviously it won't be card #1 of your example)

[hero18688]

DEV，Will you add block explorer for this coin? This is the key factor for bigger exchange to list your coin.

[skunk]

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

[mumus]

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

If you just want to "simulate" a lower difficulty in the code then just simply do this in MinerThread.cpp (-> MinerThread::SK1024Miner() function)
            CBigNum target;
            target.SetCompact(m_pBLOCK->GetBits());            
            target.SetCompact(0x7e003fff); //simulate lower difficulty

With this setting my single 750ti "finds" a "block" every couple of seconds. Of course submission will fail but you can check that the mining algo code is working.  

[skunk]

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

If you just want to "simulate" a lower difficulty in the code then just simply do this in MinerThread.cpp (-> MinerThread::SK1024Miner() function)
            CBigNum target;
            target.SetCompact(m_pBLOCK->GetBits());            
            target.SetCompact(0x7e003fff); //simulate lower difficulty

With this setting my single 750ti "finds" a "block" every couple of seconds. Of course submission will fail but you can check that the mining algo code is working.  

thank you mumus, there are no submission attempts thus confirming the mining code is actually not working...
i've blindly tried to enable SKEIN_ERR_CHECK into hash/skein.h but nothing changed, do you know if there's something that could eventually be tuned in the code that could help fixing it?

[KryptoKash]

DEV，Will you add block explorer for this coin? This is the key factor for bigger exchange to list your coin.

block explorer will be worked on after the pools are done being coded... (next few days).

[enerbyte]

Here is my bat for the computer with the wallet and 750ti's (total of 5):   skminer.exe 127.0.0.1 9325 5 20

On the image I don't have an account anywhere to upload and not sure how to insert but it says

Initializing Miner 127.0.0.1:9325 Threads = 5 Timeout = 20
connected to 127.0.0.1:9325...
[Master] Failed to Update Height
Connected to 127.0.01:9325...
[Master] Failed to Update Height
Repeats this until I terminate the miner

The computer with the 970 shows the same thing except for the 127.0.0.1 it has the ip address of the computer with the wallet running.

I have a config file to solo from another computer and it is:
rpcuser=MYUSER
rpcpassword=MYPASS
rpcallowip=127.0.0.*
rpcport=9325
server=1
daemon=1
listen=1

The wallet was created with a short cut and I went into properties and added the -server.

This is always how I have solo mined and haven't had any issues.

try this:
1. Create new wallet.dat (remember to make a backup of the previous if you have some coins in it)
2. delete the .conf file
3. open the wallet.
4. open the miner (mumus version) with this configuration:

Code:

skminer.exe 127.0.0.1 9325 5

all this on the same computer you have 5 GTX 750ti and wallet.
On the computer that has the GTX 970, install the wallet and then follow the steps above.

Edit: The .conf file is not required. It's late here 4:00 a.m. I go to sleep.
Cheers!

Awesome. That did it.

The 5 750ti's are mining at 93,700 kh/s with a really big one every now and then, 111,663,099,635,905 kh/s

The 970 is working too the rig with the wallet at 42,500 kh/s with one big one every now and then 1,140,165,890,007,893 kh/s

I'll send you some coins when I find a block. Post your address.

Thanks again.

great, this is my address.

Code:

2S14hADFJiwiFFKS2RKxazosq2n8LCt97gepTf5KvC6jJZENpsj

Cheers!

[mumus]

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

If you just want to "simulate" a lower difficulty in the code then just simply do this in MinerThread.cpp (-> MinerThread::SK1024Miner() function)
            CBigNum target;
            target.SetCompact(m_pBLOCK->GetBits());            
            target.SetCompact(0x7e003fff); //simulate lower difficulty

With this setting my single 750ti "finds" a "block" every couple of seconds. Of course submission will fail but you can check that the mining algo code is working.  

thank you mumus, there are no submission attempts thus confirming the mining code is actually not working...
i've blindly tried to enable SKEIN_ERR_CHECK into hash/skein.h but nothing changed, do you know if there's something that could eventually be tuned in the code that could help fixing it?

Try to lower the const int throughput = 512*8 * 512 * 4; in sk1024.cu, for example to 512* 8 * 512 * 1 or just 512 *  512. Let me know if it worked or not. I'm trying to understand the code and now I'm playing now with another parameter that can be related and it may help. I'm a beginner in cuda coding and I definitely don't understand the code crypto algorithm yet.

[skunk]

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

If you just want to "simulate" a lower difficulty in the code then just simply do this in MinerThread.cpp (-> MinerThread::SK1024Miner() function)
            CBigNum target;
            target.SetCompact(m_pBLOCK->GetBits());            
            target.SetCompact(0x7e003fff); //simulate lower difficulty

With this setting my single 750ti "finds" a "block" every couple of seconds. Of course submission will fail but you can check that the mining algo code is working.  

thank you mumus, there are no submission attempts thus confirming the mining code is actually not working...
i've blindly tried to enable SKEIN_ERR_CHECK into hash/skein.h but nothing changed, do you know if there's something that could eventually be tuned in the code that could help fixing it?

Try to lower the const int throughput = 512*8 * 512 * 4; in sk1024.cu, for example to 512* 8 * 512 * 1 or just 512 *  512. Let me know if it worked or not. I'm trying to understand the code and now I'm playing now with another parameter that can be related and it may help. I'm a beginner in cuda coding and I definitely don't understand the code crypto algorithm yet.

unfortunately still no submission attempts, even not with just 512...

[djm34]

GTX 760 is an sm_30 GPU and the application only seems to work on GPUs with greater compute capability for now.

so is there a chance to get it fixed?
ps: could somebody tell if sm_30 cards are finding any block under windows?

I didn't find any on testnet with a 660.
I am looking into a new kernel for the compute_30 cards (they don't have enough registers for the current one... )
but I have many things on my plate at the moment...
(I might have something... but the diff on testnet is a bit too high to get a fast answer... so it tells you already it won't be fast...)

so would lowering minimal difficulty on testnet help?
@viz: are you about to release a c release of the wallet? could you also please consider lowering the diff. in this release?
i consider donating the first 24h (or more if asked) of mining with a fixed sm_30 miner if this would help as a incentive for your (or anybody else) time...
thank you.

edit: djm34, if you have a roughly idea about which code parameters needs to be changed to fix this, please explain what i should try so i could do a trial/error loop myself until a fix is found. i'm not a software developer, but i've enough programming knowledge to perform simple code read and modifications...

If you just want to "simulate" a lower difficulty in the code then just simply do this in MinerThread.cpp (-> MinerThread::SK1024Miner() function)
            CBigNum target;
            target.SetCompact(m_pBLOCK->GetBits());            
            target.SetCompact(0x7e003fff); //simulate lower difficulty

With this setting my single 750ti "finds" a "block" every couple of seconds. Of course submission will fail but you can check that the mining algo code is working. 

thank you mumus, there are no submission attempts thus confirming the mining code is actually not working...
i've blindly tried to enable SKEIN_ERR_CHECK into hash/skein.h but nothing changed, do you know if there's something that could eventually be tuned in the code that could help fixing it?

Try to lower the const int throughput = 512*8 * 512 * 4; in sk1024.cu, for example to 512* 8 * 512 * 1 or just 512 *  512. Let me know if it worked or not. I'm trying to understand the code and now I'm playing now with another parameter that can be related and it may help. I'm a beginner in cuda coding and I definitely don't understand the code crypto algorithm yet.

unfortunately still no submission attempts, even not with just 512...

It isn't related to the throughput.
I need to rewrite the kernel for skein for compute_30 and I don't have time at the moment to work on that task...

[antonio8]

@ enerbyte

Thanks again for the help.

[enerbyte]

@ enerbyte

Thanks again for the help.

received!
help as I can, although my English is not good.
I hope you find many blocks.

[RUNNY]

AMD GPU miner???

[cbuchner1]

AMD GPU miner???

the GPU mining channel draws way more power on my 780Ti's, so I am back to the CPU channel with our nonpublic GPU miner.
Rig runs quieter and cooler now.

here's what 36 hours on the GPU channel got me (on Linux, thanks Supercomputing for the makefiles):
98.5 MH/s | 98 Blks ACC=82 REJ=16 | Height = 28862 | Diff = 35 0-bits | 35:44:32

lots of rejects though.

Christian

[antonio8]

Can someone confirm the correct block? I show I am on block 28,947.

Just want to make sure I am not forked or anything from the amount I have found.

[enerbyte]

{
"blocks" : 28996,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000193,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"pooledtx" : 0,
"testnet" : false
}

[paulthetafy]

Has anyone experienced nvcc taking a long time to complete on linux?  Mine has been going for over an hour now and has till not finished. The process appears to be running fine but at 100% CPU.

[paulthetafy]

Has anyone experienced nvcc taking a long time to complete on linux?  Mine has been going for over an hour now and has till not finished. The process appears to be running fine but at 100% CPU.

Nevermind - it eventually finished!