Just realized I'm actually able to post I been waiting to leave my Newbie status on here for awhile (this is my real first post). I been going crazy here I can't figure this out I been waiting to post this question for a month. I have the same problem as this post quoted. I get outputs like this when I use opencl.
Difficulty: 1353
Match idx: 0
CPU hash: a4900f3de57df3ea62654b295b1a92048ddc994d
GPU hash: 3d0f90a4eaf37de5294b656204921a5b4d99dc8d
Found delta: 1919 Start delta: 1
[151.19 Kkey/s][total 2048][Prob 78.0%][80% in 0.0s]
I think its the real output because the first time I tried it I got a output like that after 5 hours. I didn't think to test it before hand it took 5 hours just to get CPU hash - GPU hash output like this. If I pick a easier address I get outputs like this scrolling down. If I use a CPU generator I get a private key output the correct way it is only happening with opencl.
I tried oclvanitygen today, and discovered that it produces output like the following, instead of private keys.
Match idx: 0
CPU hash: 93b30d0ad99f8133a0bc3c4793a27dbad5a0961f
GPU hash: 0a0db39333819fd9473cbca0ba7da2931f96a0d5
Found delta: 1919 Start delta: 1
Am I doing it wrong?
What hardware/OS/drivers are you guys using?
When oclvanitygen does this, it means:
- The OpenCL code reported having found a matching address
- The address was re-calculated using the CPU
- The address calculated by the CPU did not match what was calculated by the GPU, or any patterns in the pattern list
Unfortunately, I have a small variety of hardware to test with, and don't have a platform that can reproduce this type of problem with current code.
Some folks in the past have reported this type of problem using AMD hardware with Catalyst drivers. Some of them had reported that the problem went away after upgrading to Catalyst 11.11. Certain older versions of NVIDIA drivers will cause failures too, but tend to cause oclvanitygen to crash, rather than hash mismatches like we're seeing here.
One way to detect this type of problem quickly is to use OpenCL verification mode (-V). This causes oclvanitygen to run the normal address generation procedure, but to verify results at every step of the way. It runs much slower, but if there is misbehavior on the OpenCL side, it will find it quickly, and will isolate the kernel that is producing incorrect results.
I think I had that same issue trying to gpu-mine with self-compiled code on linux. I just gave up and use Windows.
Interesting, was this with AMD hardware? Do you remember which driver you were using on Linux?
, so I have few questions:
