Pages:
Author

Topic: Bounty for Open-Sourced XMR/Cryptonight GPU Miner Bounties Thread - page 9. (Read 170943 times)

legendary
Activity: 2968
Merit: 1198
Tsiv: The bounty addresses below will be used. It seems that the BTC part (.2 BTC) has already been paid by HardwarePal.

XMR: 42uasNqYPnSaG3TwRtTeVbQ4aRY3n9jY6VXX3mfgerWt4ohDQLVaBPv3cYGKDXasTUVuLvhxetcuS16 ynt85czQ48mbSrWX

Sent 300

Code:
[wallet]: transfer 19 42uasNqYPnSaG3TwRtTeVbQ4aRY3n9jY6VXX3mfgerWt4ohDQLVaBPv3cYGKDXasTUVuLvhxetcuS16ynt85czQ48mbSrWX 300
Money successfully sent, transaction
member
Activity: 81
Merit: 1002
It was only the wind.
I'm planning to go ahead and send my 300 XMR pledge to tsiv for his nv miner. If anyone has any reason why I should not do this (for example, critical pieces of code or documentation are incomplete or missing) then please speak up now. I haven't been following the development that closely so I don't know the details beyond that he seems to have delivered a genuinely useful miner.



There's no critical piece of code or docs missing as far as I know - I think there's a bug making it impossible to use all of your GPU's memory, though, or even over half of it.
kbm
member
Activity: 84
Merit: 10
As of today I'll be considering the bounty for the Nvidia GPU miner to be fulfilled by Tsiv. It seems as if it's in widespread use and there are few problems. Thank you very much for your effort!

Tsiv: The bounty addresses below will be used. It seems that the BTC part (.2 BTC) has already been paid by HardwarePal.

XMR: 42uasNqYPnSaG3TwRtTeVbQ4aRY3n9jY6VXX3mfgerWt4ohDQLVaBPv3cYGKDXasTUVuLvhxetcuS16 ynt85czQ48mbSrWX
BTC: 1JHDKp59t1RhHFXsTw2UQpR3F9BBz3R3cs


There will be no collection, and everyone who has pledged should just send to those addresses and then post the tx info here if you'd like.

-updated by kbm

Sent 150 XMR to address above:

Money successfully sent, transaction


equipoise: sent you a couple xmr outside the bounty for that reg file, thanks!
member
Activity: 76
Merit: 10
As of today I'll be considering the bounty for the Nvidia GPU miner to be fulfilled by Tsiv. It seems as if it's in widespread use and there are few problems. Thank you very much for your effort!

Tsiv: The bounty addresses below will be used. It seems that the BTC part (.2 BTC) has already been paid by HardwarePal.

XMR: 42uasNqYPnSaG3TwRtTeVbQ4aRY3n9jY6VXX3mfgerWt4ohDQLVaBPv3cYGKDXasTUVuLvhxetcuS16 ynt85czQ48mbSrWX
BTC: 1JHDKp59t1RhHFXsTw2UQpR3F9BBz3R3cs


There will be no collection, and everyone who has pledged should just send to those addresses and then post the tx info here if you'd like.

-updated by kbm
member
Activity: 81
Merit: 1002
It was only the wind.
Since I'm quite bored right now, I think I'll let another fun piece of code go.

Code:
// tsiv
__constant__ uint8_t d_sub_byte[16][16];

const uint8_t sub_byte[16][16] = {
    { 0x63, 0x7c, 0x77, 0x7b, 0xf2, 0x6b, 0x6f, 0xc5, 0x30, 0x01, 0x67, 0x2b, 0xfe, 0xd7, 0xab, 0x76 },
    { 0xca, 0x82, 0xc9, 0x7d, 0xfa, 0x59, 0x47, 0xf0, 0xad, 0xd4, 0xa2, 0xaf, 0x9c, 0xa4, 0x72, 0xc0 },
    { 0xb7, 0xfd, 0x93, 0x26, 0x36, 0x3f, 0xf7, 0xcc, 0x34, 0xa5, 0xe5, 0xf1, 0x71, 0xd8, 0x31, 0x15 },
    { 0x04, 0xc7, 0x23, 0xc3, 0x18, 0x96, 0x05, 0x9a, 0x07, 0x12, 0x80, 0xe2, 0xeb, 0x27, 0xb2, 0x75 },
    { 0x09, 0x83, 0x2c, 0x1a, 0x1b, 0x6e, 0x5a, 0xa0, 0x52, 0x3b, 0xd6, 0xb3, 0x29, 0xe3, 0x2f, 0x84 },
    { 0x53, 0xd1, 0x00, 0xed, 0x20, 0xfc, 0xb1, 0x5b, 0x6a, 0xcb, 0xbe, 0x39, 0x4a, 0x4c, 0x58, 0xcf },
    { 0xd0, 0xef, 0xaa, 0xfb, 0x43, 0x4d, 0x33, 0x85, 0x45, 0xf9, 0x02, 0x7f, 0x50, 0x3c, 0x9f, 0xa8 },
    { 0x51, 0xa3, 0x40, 0x8f, 0x92, 0x9d, 0x38, 0xf5, 0xbc, 0xb6, 0xda, 0x21, 0x10, 0xff, 0xf3, 0xd2 },
    { 0xcd, 0x0c, 0x13, 0xec, 0x5f, 0x97, 0x44, 0x17, 0xc4, 0xa7, 0x7e, 0x3d, 0x64, 0x5d, 0x19, 0x73 },
    { 0x60, 0x81, 0x4f, 0xdc, 0x22, 0x2a, 0x90, 0x88, 0x46, 0xee, 0xb8, 0x14, 0xde, 0x5e, 0x0b, 0xdb },
    { 0xe0, 0x32, 0x3a, 0x0a, 0x49, 0x06, 0x24, 0x5c, 0xc2, 0xd3, 0xac, 0x62, 0x91, 0x95, 0xe4, 0x79 },
    { 0xe7, 0xc8, 0x37, 0x6d, 0x8d, 0xd5, 0x4e, 0xa9, 0x6c, 0x56, 0xf4, 0xea, 0x65, 0x7a, 0xae, 0x08 },
    { 0xba, 0x78, 0x25, 0x2e, 0x1c, 0xa6, 0xb4, 0xc6, 0xe8, 0xdd, 0x74, 0x1f, 0x4b, 0xbd, 0x8b, 0x8a },
    { 0x70, 0x3e, 0xb5, 0x66, 0x48, 0x03, 0xf6, 0x0e, 0x61, 0x35, 0x57, 0xb9, 0x86, 0xc1, 0x1d, 0x9e },
    { 0xe1, 0xf8, 0x98, 0x11, 0x69, 0xd9, 0x8e, 0x94, 0x9b, 0x1e, 0x87, 0xe9, 0xce, 0x55, 0x28, 0xdf },
    { 0x8c, 0xa1, 0x89, 0x0d, 0xbf, 0xe6, 0x42, 0x68, 0x41, 0x99, 0x2d, 0x0f, 0xb0, 0x54, 0xbb, 0x16 }
};

__device__ __forceinline__ void cryptonight_aes_set_key( uint32_t *key, const uint32_t *data )
{
    int i, j;
    const int key_base = 8;
    uint8_t temp[4];
    const uint32_t aes_gf[] = { 0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80, 0x1b, 0x36 };
   
    MEMSET4(key, 0, 40);
    MEMCPY4(key, data, 8);

for( i = key_base; i < 40; i++ ) {

*(uint32_t *)temp = key[i - 1];

if( i % key_base == 0 ) {

            *(uint32_t *)temp = ROTR32(*(uint32_t *)temp, 8);

for( j = 0; j < 4; j++ )
                temp[j] = d_sub_byte[(temp[j] >> 4) & 0x0f][temp[j] & 0x0f];

*(uint32_t *)temp ^= aes_gf[i / key_base - 1];
}
else if( i % key_base == 4 )
            for( j = 0; j < 4; j++ )
                temp[j] = d_sub_byte[(temp[j] >> 4) & 0x0f][temp[j] & 0x0f];

        key[i] = key[(i - key_base)] ^ *(uint32_t *)temp;
}
}

// Wolf
__device__ __constant__ uint8_t d_sbox[256];

const uint8_t sbox[256] =
{
0x63, 0x7c, 0x77, 0x7b, 0xf2, 0x6b, 0x6f, 0xc5, 0x30, 0x01, 0x67, 0x2b, 0xfe, 0xd7, 0xab, 0x76,
0xca, 0x82, 0xc9, 0x7d, 0xfa, 0x59, 0x47, 0xf0, 0xad, 0xd4, 0xa2, 0xaf, 0x9c, 0xa4, 0x72, 0xc0,
0xb7, 0xfd, 0x93, 0x26, 0x36, 0x3f, 0xf7, 0xcc, 0x34, 0xa5, 0xe5, 0xf1, 0x71, 0xd8, 0x31, 0x15,
0x04, 0xc7, 0x23, 0xc3, 0x18, 0x96, 0x05, 0x9a, 0x07, 0x12, 0x80, 0xe2, 0xeb, 0x27, 0xb2, 0x75,
0x09, 0x83, 0x2c, 0x1a, 0x1b, 0x6e, 0x5a, 0xa0, 0x52, 0x3b, 0xd6, 0xb3, 0x29, 0xe3, 0x2f, 0x84,
0x53, 0xd1, 0x00, 0xed, 0x20, 0xfc, 0xb1, 0x5b, 0x6a, 0xcb, 0xbe, 0x39, 0x4a, 0x4c, 0x58, 0xcf,
0xd0, 0xef, 0xaa, 0xfb, 0x43, 0x4d, 0x33, 0x85, 0x45, 0xf9, 0x02, 0x7f, 0x50, 0x3c, 0x9f, 0xa8,
0x51, 0xa3, 0x40, 0x8f, 0x92, 0x9d, 0x38, 0xf5, 0xbc, 0xb6, 0xda, 0x21, 0x10, 0xff, 0xf3, 0xd2,
0xcd, 0x0c, 0x13, 0xec, 0x5f, 0x97, 0x44, 0x17, 0xc4, 0xa7, 0x7e, 0x3d, 0x64, 0x5d, 0x19, 0x73,
0x60, 0x81, 0x4f, 0xdc, 0x22, 0x2a, 0x90, 0x88, 0x46, 0xee, 0xb8, 0x14, 0xde, 0x5e, 0x0b, 0xdb,
0xe0, 0x32, 0x3a, 0x0a, 0x49, 0x06, 0x24, 0x5c, 0xc2, 0xd3, 0xac, 0x62, 0x91, 0x95, 0xe4, 0x79,
0xe7, 0xc8, 0x37, 0x6d, 0x8d, 0xd5, 0x4e, 0xa9, 0x6c, 0x56, 0xf4, 0xea, 0x65, 0x7a, 0xae, 0x08,
0xba, 0x78, 0x25, 0x2e, 0x1c, 0xa6, 0xb4, 0xc6, 0xe8, 0xdd, 0x74, 0x1f, 0x4b, 0xbd, 0x8b, 0x8a,
0x70, 0x3e, 0xb5, 0x66, 0x48, 0x03, 0xf6, 0x0e, 0x61, 0x35, 0x57, 0xb9, 0x86, 0xc1, 0x1d, 0x9e,
0xe1, 0xf8, 0x98, 0x11, 0x69, 0xd9, 0x8e, 0x94, 0x9b, 0x1e, 0x87, 0xe9, 0xce, 0x55, 0x28, 0xdf,
0x8c, 0xa1, 0x89, 0x0d, 0xbf, 0xe6, 0x42, 0x68, 0x41, 0x99, 0x2d, 0x0f, 0xb0, 0x54, 0xbb, 0x16
};

__device__ __forceinline__ void cryptonight_aes_set_key(uint8_t * __restrict__ SharedSBox, uint32_t * __restrict__ Key, const uint32_t * __restrict__ Data)
{
uint32_t i;
uint8_t rcon[16] = { 0x8d, 0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80, 0x1b, 0x36, 0x6c, 0xd8, 0xab, 0x4d, 0x9a };

for(i = 0; i < 8; ++i) Key[i] = Data[i];

for(; i < 40; ++i)
{
uint32_t temp = Key[i - 1];
uint8_t *temp2;

// Modulus is slow - and i mod 8 == i & 7
if(!(i & 7))
{
temp = (temp >> 8) | (temp << 24);
temp2 = (uint8_t *)&temp;

temp2[0] = SharedSBox[temp2[0]];
temp2[1] = SharedSBox[temp2[1]];
temp2[2] = SharedSBox[temp2[2]];
temp2[3] = SharedSBox[temp2[3]];
temp2[0] ^= rcon[i >> 3];
}
else if((i & 7) == 4)
{
temp2 = (uint8_t *)&temp;
temp2[0] = SharedSBox[temp2[0]];
temp2[1] = SharedSBox[temp2[1]];
temp2[2] = SharedSBox[temp2[2]];
temp2[3] = SharedSBox[temp2[3]];
}

Key[i] = Key[i - 8] ^ temp;
}
}

No ouch slow divides or modulus operations or useless memset calls. Uses an SBox in shared memory, but it can easily be modified to use one on the device (which is actually how I had it earlier, that's what the unused d_sbox is for). Also, no unconditionally executed inner loop, either - if you have a dword to XOR, then XOR a dword, not 4 bytes one at a time. Also makes use of restricted pointers, not sure if they help, but hey, it might, and I may as well since I don't alias any of those pointers. Also, IMO, it's one hell of a lot more readable.
legendary
Activity: 2968
Merit: 1198
I'm planning to go ahead and send my 300 XMR pledge to tsiv for his nv miner. If anyone has any reason why I should not do this (for example, critical pieces of code or documentation are incomplete or missing) then please speak up now. I haven't been following the development that closely so I don't know the details beyond that he seems to have delivered a genuinely useful miner.

legendary
Activity: 2968
Merit: 1198
Is there a pre-existing XMR bounty wallet for the ATI miner?

If not, perhaps HardwarePal could make one, publish the view key?  I don't want to hold it, just send to it.

I think smooth was collecting, but if HardwarePal is hiring someone directly then that would probably be okay, so long as the view key is published. Maybe we should check with smooth to see if he's collected anything? It doesn't seem like anyones working on this bounty besides HardwarePal, so my part of the ATI bounty still stands to be claimed by what's being worked on (150 XMR - Keyboard-Mash), and it looks like Tsiv will be claiming the Nvidia miner bounty. Tsiv can you please provide an XMR address and viewkey here?

I did not collect anything for this bounty. I collected for the pool bounty (already awarded) and GUI bounty (not yet awarded).

I did personally pledge toward both the ATI and nv bounties. As far as I'm concerned tsiv has earned the nv bounty and it should be paid once someone steps forward to manage the process (I can do it but not for the next week or so) or unless someone has a counterargument.



Where exactly is an official thread with detail and setup/manual etc. for a GUI miner? Also shouldn't the miner work on all NV cards?  Huh

All cards? I'd say no. A good range if widely available cards is good enough.

As for the official thread with instructions etc. good question.
legendary
Activity: 1498
Merit: 1000
Is there a pre-existing XMR bounty wallet for the ATI miner?

If not, perhaps HardwarePal could make one, publish the view key?  I don't want to hold it, just send to it.

I think smooth was collecting, but if HardwarePal is hiring someone directly then that would probably be okay, so long as the view key is published. Maybe we should check with smooth to see if he's collected anything? It doesn't seem like anyones working on this bounty besides HardwarePal, so my part of the ATI bounty still stands to be claimed by what's being worked on (150 XMR - Keyboard-Mash), and it looks like Tsiv will be claiming the Nvidia miner bounty. Tsiv can you please provide an XMR address and viewkey here?

I did not collect anything for this bounty. I collected for the pool bounty (already awarded) and GUI bounty (not yet awarded).

I did personally pledge toward both the ATI and nv bounties. As far as I'm concerned tsiv has earned the nv bounty and it should be paid once someone steps forward to manage the process (I can do it but not for the next week or so) or unless someone has a counterargument.



Where exactly is an official thread with detail and setup/manual etc. for a GUI miner? Also shouldn't the miner work on all NV cards?  Huh
legendary
Activity: 2968
Merit: 1198
Is there a pre-existing XMR bounty wallet for the ATI miner?

If not, perhaps HardwarePal could make one, publish the view key?  I don't want to hold it, just send to it.

I think smooth was collecting, but if HardwarePal is hiring someone directly then that would probably be okay, so long as the view key is published. Maybe we should check with smooth to see if he's collected anything? It doesn't seem like anyones working on this bounty besides HardwarePal, so my part of the ATI bounty still stands to be claimed by what's being worked on (150 XMR - Keyboard-Mash), and it looks like Tsiv will be claiming the Nvidia miner bounty. Tsiv can you please provide an XMR address and viewkey here?

I did not collect anything for this bounty. I collected for the pool bounty (already awarded) and GUI bounty (not yet awarded).

I did personally pledge toward both the ATI and nv bounties. As far as I'm concerned tsiv has earned the nv bounty and it should be paid once someone steps forward to manage the process (I can do it but not for the next week or so) or unless someone has a counterargument.

full member
Activity: 137
Merit: 100
And a crosspost from the CudaMiner/ccMiner thread:

Aaand I'm back. Had to focus a bit on shit I've been neglecting lately, including but not limited to my actual job and sleep  Grin

Say bye to (most of) the lag on Windows if you're willing to take a slight hit in performance. Basically I'm now splitting the heaviest part of the Cryptonight core into smaller batches with a little sleep between launching the batches. The default is still no splitting and no sleeping on Linux, on Windows it gets split into 64 batches with 100 microseconds sleep between the batches. Both values can be set on the command line per-device. I'm running it as I type this and while there is still noticeable lag, it's not too bad. The performance hit is pretty negligible on the defaults, something like 5 H/s. Well, on my system anyway.

Latest win32 binary at https://github.com/tsiv/ccminer-cryptonight/releases/tag/v0.14 and source at https://github.com/tsiv/ccminer-cryptonight as you might expect.
full member
Activity: 137
Merit: 100
I promised a bounty for the Nvidia miner even though all my Nvidia cards are in the cupboard  Grin
Post a BTC donation address tsiv so I can send my share (0.2BTC as listed)

Any chance somebody tried the Gtx580 or Gtx680 I have 2 of each which I might slap on a system if worthwhile
Tsiv donations and updates

Sent my promised 0.2BTC now  (0.20133330 to be exact)

Thaaank you, sir, received and much appreciated.
full member
Activity: 137
Merit: 100
Is there a pre-existing XMR bounty wallet for the ATI miner?

If not, perhaps HardwarePal could make one, publish the view key?  I don't want to hold it, just send to it.

I think smooth was collecting, but if HardwarePal is hiring someone directly then that would probably be okay, so long as the view key is published. Maybe we should check with smooth to see if he's collected anything? It doesn't seem like anyones working on this bounty besides HardwarePal, so my part of the ATI bounty still stands to be claimed by what's being worked on (150 XMR - Keyboard-Mash), and it looks like Tsiv will be claiming the Nvidia miner bounty. Tsiv can you please provide an XMR address and viewkey here?


I have a an XMR address up on the Github project  page, no viewkey though. If you need one I guess I can always create a new wallet for it, seeing as I can't figure out how to get the viewkey for an existing wallet. Apparently it is only shown once on wallet creation and if you ignored it (I did, didn't even know such a thing existed) you're out of luck? Another curve ball by the XMR wallet, they just keep coming Smiley
hero member
Activity: 644
Merit: 502
I tried, but it says "Maximum Spot Instance Count Exceeded" and fails to launch the instance.
 Huh
legendary
Activity: 1596
Merit: 1030
Sine secretum non libertas
Amazing spot pricing on AWS g2 instances right now, $0.077/hr.  I think one is good for about 200hps with tsiv.
full member
Activity: 238
Merit: 100
Stand on the shoulders of giants
newbie
Activity: 33
Merit: 0
i suggest all the people who have problems with ccminer-cryptnight post a issue on the github repo
sr. member
Activity: 392
Merit: 250
 Has anybody successfully connected to minergate's pool?
tsiv's ccminer crash when it saids pool set diff 444.



member
Activity: 81
Merit: 10
my N card: GPU #0: FATAL: failed to allocate device memory for long state,why?
sr. member
Activity: 280
Merit: 250
No command line "-l". Default 40x8. Tried 80x8 and 40x16, but they were worse. Surely Windows can't be nerfing the GPU so badly?

Update. I read a post here:
http://www.holynerdvana.com/2014/07/mining-cryptonote-coins-with-nvidia.html
and started playing around with the -l switch. On Windows 8.1 this makes a massive difference. With 750 ti, switching to -l 8x32 boosts performance to the expected 200+ H/s. Night and day difference. Other settings may improve that further, but that's a reasonable starter for 8.1 miners.
Edit: best combo so far found: -l 8x30 for 260 H/s.
Cheers, Q
legendary
Activity: 2156
Merit: 1131
I can't run tsiv's ccminer under win8.1.Driver crash everytime I start ccminer.Any solution?

The NVIDIA drivers will "time out" and give you a crash message. This is Windows basically detecting that the drivers haven't responded properly for a while, and so it stops them and of course your mining quits as well. You can usually get around this via a registry edit, but in some cases even that may not work all the time so be prepared to fiddle around a bit. The registry hack is easy enough:

    Run "regedit.exe" from the Start Menu.
    Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers"
    Right-click on the right panel and create a new 32-bit DWORD value.
    Name the key "TdrDelay" and assign it a value of anywhere from 10 to 30 (decimal -- 0A to 1E hex).
    Reboot and you should be set.

Pages:
Jump to: