Re: BitCrack - A tool for brute-forcing private keys
Edit:
Attempts to log, gather more info or whatever, will slow down the program just enough that it *works*.
Prob. the reason it works on older hardware. Its really the speed killing it.
Attempts to log, gather more info or whatever, will slow down the program just enough that it *works*.
Prob. the reason it works on older hardware. Its really the speed killing it.
Maybe the SMs in the GPU have so many threads per block running that they don't have enough time to align all the pointers for Bitcrack. The GPU does a lot of its own things at runtime. I never saw bitcrack do any alignment in the cracking loop, but neither did I check the parts responsible for initialization.
Could the initialization stage be launching kernels with invalid block sizes in a grid? Maybe there's a way to make it launch a 1x1 sized grid so we can see what happens.
Not sure if you can look at what changed between the 452 driver and newer drivers that caused it to stop working on 20xx cards. unless it's a mere cuda runtime thing.
Also, I have noticed in another program that when I try and generate random keys with the 20xx or 30xx, that is when I get the misaligned or memory error, but only when I have a large input list (of addresses). Got me thinking with BitCrack, when you have a large list or the program starts generating all those starting points, that's where error is coming into play. I wonder if you choked down the starting points to say 32, 32, 32, if same error would exist.
When I use straight key to key search, no generation of random points, I have no issues with any series of cards on the other program.
Also, the new Ampere has 4 SMs, 4 x 32. But from what I have seen, it seems like random points, creating many points does something to throw the misaligned address/memory errors. Crazy stuff to say the least.