NSGminer v0.9.4: The Fastest NeoScrypt GPU Miner

[ghostlander]

testing orbit@TBF

Also 10-15% of "share is above target"

Switch from vardiff to the fixed diff of 4 (64 in the pool).

--thread-concurrency 8192   --lookup-gap 2

These are ignored by the miner.

[1714259878]

1714259878

[OverP]

Just to let you guys know, it is entirely possible to improve the OpenCL kernel of this miner by eliminating scratchpad registers (register spills). I am currently getting 795KH/s, a 30% increase in speed, with a RX 480 and a heavily modified kernel. It is also possible to optimize the generated GCN code and make the kernel even faster.

I am currently focused on Ethereum mining because it is more profitable, but I might release my custom NeoScrypt  kernel when I have a chance.

Is your miner ready?

[semajjames]

I am Solo mining with 2 rigs and one separate pc running the wallet,,
everything seem's fine with all the miners untill a rig finds a block at this point the coin gets to the wallet ok but the miner starts saying that the wallet ip/port address is not responding and the hashing stops and say's wait
Anything obvious that could cause this ?

cheers  

[fredeq]

Any way to run nsgminer on new 4xx series cards?
Guess its the problem with 16.x drivers.

[OverP]

480produces370Kh

[zawawa]

I totally forgot to announce it here. With Gateless Gate, my new miner, you should be able to get 700Kh/s with an overclocked RX 480:

https://github.com/zawawawa/gatelessgate
https://bitcointalk.org/index.php?topic=1716584

Let me know if you are still interested.

[ghostlander]

I have given your kernel a spin on my notebook with HD6750, got 25KH/s. My current parallel kernel outputs 45KH/s there with 3x lower kernel binary size. Perhaps your kernel isn't supposed to run on this hardware. I'll check with newer video cards later.

[aciddude]

@Ghostlander

I'm getting:

Invalid (out of bounds) block target 0xDE1D0F1C




This is just solomining on 0.9.6

[ghostlander]

@Ghostlander

I'm getting:

Invalid (out of bounds) block target 0xDE1D0F1C




This is just solomining on 0.9.6

The miner receives incorrect input data and tells you. The current FTC network difficulty is about 10^4. The miner reports 10^18.

[ghostlander]

I have given your kernel a spin on my notebook with HD6750, got 25KH/s. My current parallel kernel outputs 45KH/s there with 3x lower kernel binary size. Perhaps your kernel isn't supposed to run on this hardware. I'll check with newer video cards later.

A follow-up. I've tested it on a HD7990. Produces 900KH/s vs. 880KH/s of my kernel. No scratch registers used, but ISA size is 174Kb vs. 40Kb of my kernel. It stores all data buffers as uint's and bitaligns them for processing using conditionals. This is an interesting approach, though not for older GPUs definitely because they hate branching. That's why I went another way to optimise for older and newer GPUs at the same time. I guess it's time to split work into two separate kernels and optimise them independently.

[aciddude]

@Ghostlander

I'm getting:

Invalid (out of bounds) block target 0xDE1D0F1C




This is just solomining on 0.9.6

The miner receives incorrect input data and tells you. The current FTC network difficulty is about 10^4. The miner reports 10^18.

How does this make sense when I'm connected to a fully synced 0.9.6 client ?

[ghostlander]

@Ghostlander

I'm getting:

Invalid (out of bounds) block target 0xDE1D0F1C




This is just solomining on 0.9.6

The miner receives incorrect input data and tells you. The current FTC network difficulty is about 10^4. The miner reports 10^18.

How does this make sense when I'm connected to a fully synced 0.9.6 client ?

Those who did QA on the v0.9.6 missed the solo mining part, i.e. getwork. It's broken. Try with the v0.8.7.3 to see the difference.

[aciddude]

@Ghostlander

I'm getting:

Invalid (out of bounds) block target 0xDE1D0F1C




This is just solomining on 0.9.6

The miner receives incorrect input data and tells you. The current FTC network difficulty is about 10^4. The miner reports 10^18.

How does this make sense when I'm connected to a fully synced 0.9.6 client ?

Those who did QA on the v0.9.6 missed the solo mining part, i.e. getwork. It's broken. Try with the v0.8.7.3 to see the difference.

Ok thanks man, I'll ask the Feathercoin Devs to look into it.

[zawawa]

I have given your kernel a spin on my notebook with HD6750, got 25KH/s. My current parallel kernel outputs 45KH/s there with 3x lower kernel binary size. Perhaps your kernel isn't supposed to run on this hardware. I'll check with newer video cards later.

A follow-up. I've tested it on a HD7990. Produces 900KH/s vs. 880KH/s of my kernel. No scratch registers used, but ISA size is 174Kb vs. 40Kb of my kernel. It stores all data buffers as uint's and bitaligns them for processing using conditionals. This is an interesting approach, though not for older GPUs definitely because they hate branching. That's why I went another way to optimise for older and newer GPUs at the same time. I guess it's time to split work into two separate kernels and optimise them independently.

Yeah, my optimizations are only for GCN. Like you said, they don't make any sense for VLIW4/5.
I did a quick run and got 970KH/s on my stock 7990 with Crimson 16.9.2.
I am currently working on an offline OpenCL compiler for GCN with inline assembly support.
If I can pull this off, we will see more interesting stuff. 

[Lanet]

Hi I want to know if this temperature is normal or I have to turn it off the video card already has 2 years of normal use just now I start to mine.

Where I can calculate earnings with NeoScrypt. Do you recommend mining with nvidia video cards?

https://i.imgur.com/UP3sWuI.jpg

[Lanet]

any solution?

[ghostlander]

any solution?

WhatToMine.com

[supersnips]

Nsgminer links are infected with  "Trojan.Win64.BitMiner.w"  be careful! 

here the file checked:
https://www.virustotal.com/de/file/0596f12456d2b41a4d3dd87598e8e9d1577d50d8ce1bdf3f217eec7df5b7ed59/analysis/1484997882/

and here the link: https://www.virustotal.com/de/url/8b8de9675bb64a4e5ecbcabd2e20374e657a760be2a252a398ccdbd6ce572a29/analysis/1487950100/








ccminer link seems clean.

[ghostlander]

Nsgminer links are infected with  "Trojan.Win64.BitMiner.w"  be careful!  

here the file checked:
https://www.virustotal.com/de/file/0596f12456d2b41a4d3dd87598e8e9d1577d50d8ce1bdf3f217eec7df5b7ed59/analysis/1484997882/

and here the link: https://www.virustotal.com/de/url/8b8de9675bb64a4e5ecbcabd2e20374e657a760be2a252a398ccdbd6ce572a29/analysis/1487950100/

ccminer link seems clean.

Miner "infected" with a miner. You must be genius.

[supersnips]

Nsgminer links are infected with  "Trojan.Win64.BitMiner.w"  be careful!  

here the file checked:
https://www.virustotal.com/de/file/0596f12456d2b41a4d3dd87598e8e9d1577d50d8ce1bdf3f217eec7df5b7ed59/analysis/1484997882/

and here the link: https://www.virustotal.com/de/url/8b8de9675bb64a4e5ecbcabd2e20374e657a760be2a252a398ccdbd6ce572a29/analysis/1487950100/

ccminer link seems clean.

Miner "infected" with a miner. You must be genius.

you forgot the Trojan there. well i dont get this message on other miners at all.

But

 if this isnt one, thanks for your work and effort to the community. i just shared what i saw, everybody needs to decide for them selve to use or not.