Quote from: proteus7 on January 19, 2018, 07:55:16 PM

TitanXP is just a 1080ti (same GP102 proc) with 2 additional SMDs enabled (30 vs 28) and an additional GB of RAM? every other miner for 1080ti also works on it...

Quote from: luxferro on January 19, 2018, 04:11:01 PM

Quote from: proteus7 on January 19, 2018, 02:25:03 AM

hsrminer_neoscrypt isn't working on my cards. Tried zpool and ahashpool. Any ideas?

INFO : [18:23:36] : Securing devfee mining...
INFO : [18:23:36] : Dev_Main OK.
INFO : [18:23:36] : Dev_Backup OK.
INFO : [18:23:36] : Dev pools checked, at least 1 accessible, continue...
INFO : [18:23:36] : POOL: stratum+tcp://neoscrypt.mine.zpool.ca:4233
INFO : [18:23:36] : Checking for NVML...
INFO : [18:23:36] : NVML monitoring enabled, continue...
INFO : [18:23:36] : 2 GPUs found/specified, initializing miner...
INFO : [18:23:42] : Share difficulty reset -- 256 (0.00391)
INFO : [18:23:42] : New block #61884 received, new difficulty is 474.676
INFO : [18:23:43] : GPU #1: TITAN Xp COLLECTORS EDITION, flags: 0, 0, 0
INFO : [18:23:43] : GPU #0: TITAN Xp COLLECTORS EDITION, flags: 0, 0, 0
INFO : [18:23:43] : submit_upstream_work stratum_send_line failed
INFO : [18:23:43] : ...retry after 10 seconds
INFO : [18:23:43] : Share Rejected, Invalid share
INFO : [18:23:43] : Share Rejected, Duplicate share
INFO : [18:23:43] : Share Rejected, Duplicate share
INFO : [18:23:43] : Share Rejected, Duplicate share
INFO : [18:23:43] : Share Rejected, Duplicate share

This miner doesn't work with Titans. See the "0,0,0" flags? I'm pretty sure that means it's not supported yet... that is if this is still going to be developed.

Well I have a Titan X pascal too, and this is the conclusion I've come to. I've seen others with the same issue. Also, if you search this thread for 0,0,0 flags, you'll see posts by the dev saying that the gpu that had those flags wasn't supported - he then added support for someones laptop gpu. So it's not going to work on titan X's because he probably checks the videocard model vs some whitelist in his programming inside the miner.

I've posted numerous times in various threads on this forum in hopes he would see it and fix it. And even opened an issue about it on github. But he seems to be taking a break or something.