Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 140. (Read 1153691 times)
I just prefer if a new version comes out that makes compressed private keys (compressed public keys); the ones that start with L or K instead of 5.
Give me a link to a working version, I'll look at it, it shouldn't be too difficult to change 
So you can find your preferred address, your vanity one. You keep trying and trying until you find a match. The faster you generate keys, the faster you can chance upon your vanity address.
I just prefer if a new version comes out that makes compressed private keys (compressed public keys); the ones that start with L or K instead of 5.
I just prefer if a new version comes out that makes compressed private keys (compressed public keys); the ones that start with L or K instead of 5.
Am I reading this right, that it generates 23k addresses per second? And this particular address was found after 80,000?
Why do you want to create so many addresses per second?
Even with that file in the directory I don't get anything. I'm running Windows 8, by the way.
Seems like curl does not load cacert.pem under windows for some reason, I'll try to fix & rebuild once i'll get access to windows machine. On linux it seems to work, though:
Code:
# ./catalystwrap ./oclvanityminer -v -d 0:1 -u https://vanitypool.appspot.com/ -a 14kCFssNkH8SsXdCu8aW7AuLusQwrBDsk2
./oclvanityminer: /usr/lib/libOpenCL.so.1: no version information available (required by ./oclvanityminer)
* About to connect() to vanitypool.appspot.com port 443 (#0)
* Trying 173.194.70.141...
* Connected to vanitypool.appspot.com (173.194.70.141) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
* SSL connection using ECDHE-RSA-RC4-SHA
* Server certificate:
* subject: C=US; ST=California; L=Mountain View; O=Google Inc; CN=*.appspot.com
* start date: 2013-03-27 13:24:05 GMT
* expire date: 2013-12-31 15:58:50 GMT
* subjectAltName: vanitypool.appspot.com matched
* issuer: C=US; O=Google Inc; CN=Google Internet Authority
* SSL certificate verify ok.
> GET /getWork HTTP/1.1
Host: vanitypool.appspot.com
Accept: */*
< HTTP/1.1 200 OK
< Content-Type: text/html; charset=utf-8
< Date: Mon, 15 Apr 2013 13:24:19 GMT
< Server: Google Frontend
< Cache-Control: private
< Transfer-Encoding: chunked
<
* Connection #0 to host vanitypool.appspot.com left intact
Device: Scrapper
Vendor: Advanced Micro Devices, Inc. (1002)
Driver: 1016.4
Profile: FULL_PROFILE
Version: OpenCL 1.2 AMD-APP (1016.4)
Max compute units: 2
Max workgroup size: 256
Global memory: 268435456
Max allocation: 134217728
OpenCL compiler flags: -DDEEP_PREPROC_UNROLL -DVERY_EXPENSIVE_BRANCHES -DDEEP_VLIW -DAMD_BFI_INT -DCATALYST_WORKAROUND
Loading kernel binary dd8ff274de8e0f156d9062519e8ab3ba.oclbin
Grid size: 1024x512
Modular inverse: 512 threads, 1024 ops each
Available bounties:
Pattern: "1XXXXXXX" Reward: 0.088063 Value: 0.000002 BTC/Gkey
Pattern: "1Fizzisist" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Satan666" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1kArLMaRx" Reward: 1.600000 Value: 0.000001 BTC/Gkey
Pattern: "1111Wish" Reward: 0.320000 Value: 0.000000 BTC/Gkey
Pattern: "123456789" Reward: 0.008800 Value: 0.000000 BTC/Gkey
Pattern: "1ALiCECiLA" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1AUSTRALiA" Reward: 0.720000 Value: 0.000000 BTC/Gkey
Pattern: "1Anonymous" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1BrownFox" Reward: 0.008800 Value: 0.000000 BTC/Gkey
Pattern: "1Casascius" Reward: 0.720000 Value: 0.000000 BTC/Gkey
Pattern: "1Konichiwa" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1LazyDog1" Reward: 0.008800 Value: 0.000000 BTC/Gkey
Pattern: "1Mercedes" Reward: 0.008000 Value: 0.000000 BTC/Gkey
Pattern: "1Porsche1" Reward: 0.008000 Value: 0.000000 BTC/Gkey
Pattern: "1Rastafari" Reward: 0.480000 Value: 0.000000 BTC/Gkey
Pattern: "1RedCross" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1RedQueen" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1STEELERS" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1SatoshiNak" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Saturday" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1SiLkRoAd" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1SkRRJyTC" Reward: 0.160000 Value: 0.000000 BTC/Gkey
Pattern: "1SoDesuNe" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1TeraVPS" Reward: 0.016000 Value: 0.000000 BTC/Gkey
Pattern: "1ThankYou" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Thousand" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Thursday" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Universe" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Washing1" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1Wednesday" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1WiKiLEAKS" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1ZhouTong" Reward: 0.480000 Value: 0.000000 BTC/Gkey
Pattern: "1currency" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1qwertyuiop" Reward: 1.200000 Value: 0.000000 BTC/Gkey
Batch of 31, total value: 0.000002 BTC/Gkey
Pattern: "1STEQUALD" Reward: 0.080000 Value: 0.000000 BTC/Gkey
Pattern: "1BitSnitch" Reward: 0.040000 Value: 0.000000 BTC/Gkey
Pattern: "123456789" Reward: 0.118493 Value: 0.000002 BTC/Gkey
Pattern: "1gSiLVER" Reward: 0.223200 Value: 0.000004 BTC/Gkey
Pattern: "1TheDoctor" Reward: 0.400000 Value: 0.000000 BTC/Gkey
Pattern: "1Casascius" Reward: 3.200000 Value: 0.000001 BTC/Gkey
Pattern: "1swhitt7" Reward: 0.086400 Value: 0.000002 BTC/Gkey
Pattern: "1Coinbets" Reward: 0.080000 Value: 0.000002 BTC/Gkey
Pattern: "1MrCoinMan" Reward: 0.160000 Value: 0.000000 BTC/Gkey
Pattern: "1ThePiachu" Reward: 0.800000 Value: 0.000000 BTC/Gkey
Pattern: "1burrito" Reward: 0.120000 Value: 0.000002 BTC/Gkey
Pattern: "17Strykes" Reward: 0.064000 Value: 0.000001 BTC/Gkey
Pattern: "1whisker" Reward: 0.008000 Value: 0.000000 BTC/Gkey
Pattern: "1aantonop" Reward: 0.600000 Value: 0.000000 BTC/Gkey
Pattern: "1bitpoin" Reward: 0.012000 Value: 0.000000 BTC/Gkey
Pattern: "1AntjeDahm" Reward: 0.320000 Value: 0.000000 BTC/Gkey
Pattern: "1MoLeCuLaR" Reward: 0.120000 Value: 0.000000 BTC/Gkey
Pattern: "1DanieLRH" Reward: 0.088680 Value: 0.000002 BTC/Gkey
Pattern: "1tigereye" Reward: 0.880000 Value: 0.000000 BTC/Gkey
Pattern: "1Satoshi" Reward: 0.080000 Value: 0.000002 BTC/Gkey
Searching for pattern: "1gSiLVER" Reward: 0.223200 Value: 0.000004 BTC/Gkey
Prefix difficulty: 51529903411245 1gSiLVER
Difficulty: 51529903411245
Total value for current work: 0.000004 BTC/Gkey
Using OpenCL prefix matcher
[1.27 Mkey/s][total 31981568][Prob 0.0%][50% in 325.9d]
It is probably looking for the ca file on some weird path, you can try using http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx to figure out the place where it is looking (if at all).
For now, you can use only the standalone ocl miner on windows.
Even with that file in the directory I don't get anything. I'm running Windows 8, by the way.
I get a "Peer certificate cannot be validated with given CA certificates" error. Help?
HTTPS vanitypool i suppose. You need http://curl.haxx.se/ca/cacert.pem in a working directory where you launch the oclvanityminer.
I get a "Peer certificate cannot be validated with given CA certificates" error. Help?
That's awesome! Original oclvanitygen.exe ended with APPCRASH for me but your oclvanitygen64.exe works very well! I went from 950 Kkey/s to 26.11 Mkey/s (Radeon HD 7970) and 22.1 Mkey/s (Radeon HD 7950).
My platform: Windows 7 Pro SP1 64-bit, AMD Catalyst 13.2.
My platform: Windows 7 Pro SP1 64-bit, AMD Catalyst 13.2.
Good to hear it works on actual graphic cards! (I've tested only on AMD A4-3400 APU).
Could someone please test on OSX, I dont have access to Apple machine.
Ok. win32 second try, fully rebuilt:
https://www.dropbox.com/s/ikm9307wsx0ydqt/vanitygen_catalyst.zip
To build from source code:
download https://github.com/wyuzhe/vanitygen/archive/master.zip, setup dependencies, nmake -f Makefile.win32/win64 etc.
Once you'we built all the binaries (8 in total), you can wrap the result with AMD APP SDK 2.8 compiler which seems to produce correct code in case you're getting compute errors.
Beware that to get correct version of the compiler you need to download the whole SDK (200MB).
Test it against beta catalyst driver on system. In case you get a crash/your card is frozen, try removing some or all the dlls of compiler wrapper in 32/ or 64/ directory.
Wrapped version, when running with -v, should report:
Newer compiler versions produce incorrect results (block mining indeed unaffected - vanitygen kernel is nontrivial compared to simple sha256 one).
Detailed reports welcome as always.
https://www.dropbox.com/s/ikm9307wsx0ydqt/vanitygen_catalyst.zip
To build from source code:
download https://github.com/wyuzhe/vanitygen/archive/master.zip, setup dependencies, nmake -f Makefile.win32/win64 etc.
Once you'we built all the binaries (8 in total), you can wrap the result with AMD APP SDK 2.8 compiler which seems to produce correct code in case you're getting compute errors.
Beware that to get correct version of the compiler you need to download the whole SDK (200MB).
Test it against beta catalyst driver on system. In case you get a crash/your card is frozen, try removing some or all the dlls of compiler wrapper in 32/ or 64/ directory.
Wrapped version, when running with -v, should report:
Code:
Version: OpenCL 1.2 AMD-APP (1016.4)
Newer compiler versions produce incorrect results (block mining indeed unaffected - vanitygen kernel is nontrivial compared to simple sha256 one).
Detailed reports welcome as always.
That's awesome! Original oclvanitygen.exe ended with APPCRASH for me but your oclvanitygen64.exe works very well! I went from 950 Kkey/s to 26.11 Mkey/s (Radeon HD 7970) and 22.1 Mkey/s (Radeon HD 7950).
My platform: Windows 7 Pro SP1 64-bit, AMD Catalyst 13.2.
Ok. win32 second try, fully rebuilt:
https://www.dropbox.com/s/ikm9307wsx0ydqt/vanitygen_catalyst.zip
To build from source code:
download https://github.com/wyuzhe/vanitygen/archive/master.zip, setup dependencies, nmake -f Makefile.win32/win64 etc.
Once you'we built all the binaries (8 in total), you can wrap the result with AMD APP SDK 2.8 compiler which seems to produce correct code in case you're getting compute errors.
Beware that to get correct version of the compiler you need to download the whole SDK (200MB).
Test it against beta catalyst driver on system. In case you get a crash/your card is frozen, try removing some or all the dlls of compiler wrapper in 32/ or 64/ directory.
Wrapped version, when running with -v, should report:
Newer compiler versions produce incorrect results (block mining indeed unaffected - vanitygen kernel is nontrivial compared to simple sha256 one).
Detailed reports welcome as always.
https://www.dropbox.com/s/ikm9307wsx0ydqt/vanitygen_catalyst.zip
To build from source code:
download https://github.com/wyuzhe/vanitygen/archive/master.zip, setup dependencies, nmake -f Makefile.win32/win64 etc.
Once you'we built all the binaries (8 in total), you can wrap the result with AMD APP SDK 2.8 compiler which seems to produce correct code in case you're getting compute errors.
Beware that to get correct version of the compiler you need to download the whole SDK (200MB).
Test it against beta catalyst driver on system. In case you get a crash/your card is frozen, try removing some or all the dlls of compiler wrapper in 32/ or 64/ directory.
Wrapped version, when running with -v, should report:
Code:
Version: OpenCL 1.2 AMD-APP (1016.4)
Newer compiler versions produce incorrect results (block mining indeed unaffected - vanitygen kernel is nontrivial compared to simple sha256 one).
Detailed reports welcome as always.
Thanks for the guide, I will try with the newer drivers.
The drivers I have now are best for my gaming & TV & mining needs, so am I am hesitant to change my config.
In the meantime I was able to find the Addresses I was looking for with vanitygen64 on my CPU (was amazingly quite fast for 5 letters).
Thanks again...
The drivers I have now are best for my gaming & TV & mining needs, so am I am hesitant to change my config.
In the meantime I was able to find the Addresses I was looking for with vanitygen64 on my CPU (was amazingly quite fast for 5 letters).
Thanks again...
Any ideas?
Yes, install Catalyst v11.11.BTW, a yearly repost?...:
If you are just trying to use vanitygen, here's a Windows binary HOWTO:
Installation:
- If GPU acceleration is desired, install ATI Drivers v11.10-v11.11 (with SDK 2.5) or latest Nvidia driver, test that OpenCL is working with GPU miner software. If drivers with SDK >2.5 have been installed, files may need to be manually removed.
- Download and unzip vanitygen-0.22-win.zip to it's own directory.
- To interact with the program, you need to open a terminal/shell/command prompt in the program's directory. In Windows Vista/Win7 Explorer, hold down the shift key on the keyboard while right-clicking the folder where vanitygen was extracted, and choose Open command window here.
- Test CPU operation. This command line will generate a Bitcoin addresses beginning with 1ABCD in around a minute or less:
>vanitygen 1ABCD - Test GPU operation. This command line will generate a Bitcoin addresses beginning with 1ABCDE in around a minute, using the first OpenCL device in your system:
>oclvanitygen -d 0 1ABCDE
OpenCL GPU device configuration:
OpenCL is the language used for talking to a GPU, and is installed with the video card driver. If the above GPU command didn't run correctly, generating over 1Mkey/s, then you should examine your OpenCL configuration. Remove the -d 0 option ("use device #0") from the command line above and run it again, which will list available OpenCL devices. Here's mine:
>oclvanitygen 1ABCD
Available OpenCL platforms:
0: [Advanced Micro Devices, Inc.] AMD Accelerated Parallel Processing
0: [Advanced Micro Devices, Inc.] Juniper
1: [GenuineIntel] Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Both a GPU and the system CPU are available in my system; on yours, the GPU may not be the first listed. "Juniper" is this AMD GPU's code name.
The first line is the platform number, the second two lines are the available devices under that platform. Change the -d 0 line in the example above to the GPU desired. If no GPU is shown, the video card driver or OpenCL is not installed properly. If you have multiple OpenCL SDKs or implementations installed, more than one platform may be shown, specify the correct one (e.g. -p 1 for the second platform if shown.)
Example command lines (oclvanitygen, device 0, default platform):
- Search for exact prefix 1ABCDE, keep searching after first match is found (-k):
>oclvanitygen -d 0 -k 1ABCDE - Search for prefix 1ABCDE in any combination of upper or lower case (-i):
>oclvanitygen -d 0 -i 1ABCDE - Search for ABCD anywhere in address (only supported on CPU vanitygen) (-r):
>vanitygen -r ABCD - Search for prefix 1ABCDE, use a seed file to make address generation more secure and random (-s):
>oclvanitygen -d 0 -s RandomSeedFile.txt 1ABCDE - Search for prefix 1ABCDE, keep searching after first match is found, and save all found address to a file:
>oclvanitygen -d 0 -k -o GeneratedAddresses.txt 1ABCDE - Search for many prefixes at once using a text file listing them (newline after each prefix including last):
>oclvanitygen -d 0 -k -f PrefixList.txt - Use all options above including case-insensitive search, and turn on verbose mode for more information:
>oclvanitygen -d 0 -v -i -k -f PrefixList.txt -o GeneratedAddresses.txt -s RandomSeedFile.txt
When specifying a case-sensitive address prefix on the command line or in a text file list, you must only use valid Base58 characters. This means you must only use lower-case i or o, and only upper-case L, or you will get an error.
- Bad: 1celeron, 1CELERON
- Good: 1ceLeron, 1CELERoN
I found an address, now what?
Vanitygen finds an address that matches your search parameters, and provides the private key for that address. The private key is never shown to you in the Bitcoin client; it is used behind the scenes, and is the secret part of your address that you should never give to anyone.
The mainline Bitcoin client does not have the ability to use private keys directly, but you can do other things to use bitcoins sent to your new address:
- In Bitcoin-qt: Help -> Debug window -> Console. Type importprivkey 5Jxxxxxxxxxxx "my vanity addr"
- Use the "redeem private key" option on MtGox, and input the private key you found. Any Bitcoins sent to the address will now be automatically withdrawn to your MtGox account. This is permanent, there is no option to remove or cancel a private key once it is added to your MtGox account,
- Use an alternate Bitcoin client, such as Armory, that has an "import private key" feature,
Somehow I cannot get the GPU gen to work.
CPU OCL works fine.
5870 Catalyst 10.10
CLInfo Output:
When I try to run anything on device 1 I get a gpu driver crash and Windows reset my GFX card.
I tried with -S, same thing.
When I try to run it with -V I get tons of these, but no crash:
Mining with poclbm or bfgminer works fine.
Also when I try to run it again I get this:
I can only try again when I delete the 4.4MB (-S) or 6MB .bin file and recompile.
Any ideas?
CPU OCL works fine.
5870 Catalyst 10.10
CLInfo Output:
Code:
Number of platforms: 1
Platform Profile: FULL_PROFILE
Platform Version: OpenCL 1.0 ATI-Stream-v2.1 (145
)
Platform Name: ATI Stream
Platform Vendor: Advanced Micro Devices, Inc.
Platform Extensions: cl_khr_icd
Platform Name: ATI Stream
Number of devices: 2
Device Type: CL_DEVICE_TYPE_CPU
Device ID: 4098
Max compute units: 4
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 1024
Preferred vector width char: 16
Preferred vector width short: 8
Preferred vector width int: 4
Preferred vector width long: 2
Preferred vector width float: 4
Preferred vector width double: 0
Max clock frequency: 3400Mhz
Address bits: 32
Max memory allocation: 536870912
Image support: No
Max size of kernel argument: 4096
Alignment (bits) of base address: 1024
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: Yes
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: No
Round to +ve and infinity: No
IEEE754-2008 fused multiply-add: No
Cache type: Read/Write
Cache line size: 64
Cache size: 65536
Global memory size: 1073741824
Constant buffer size: 65536
Max number of constant args: 8
Local memory type: Global
Local memory size: 32768
Profiling timer resolution: 1
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue properties:
Out-of-Order: No
Profiling : Yes
Platform ID: 0287946C
Name: AMD Phenom(tm) II X4 965 Proces
sor
Vendor: AuthenticAMD
Driver version: 1.1
Profile: FULL_PROFILE
Version: OpenCL 1.0 ATI-Stream-v2.1 (145
)
Extensions: cl_khr_icd cl_amd_fp64 cl_khr_g
lobal_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32
_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store
cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_pri
ntf
Device Type: CL_DEVICE_TYPE_GPU
Device ID: 4098
Max compute units: 20
Max work items dimensions: 3
Max work items[0]: 256
Max work items[1]: 256
Max work items[2]: 256
Max work group size: 256
Preferred vector width char: 16
Preferred vector width short: 8
Preferred vector width int: 4
Preferred vector width long: 2
Preferred vector width float: 4
Preferred vector width double: 0
Max clock frequency: 850Mhz
Address bits: 32
Max memory allocation: 268435456
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 8
Max image 2D width: 8192
Max image 2D height: 8192
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 32768
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: No
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: No
Round to +ve and infinity: No
IEEE754-2008 fused multiply-add: No
Cache type: None
Cache line size: 0
Cache size: 0
Global memory size: 268435456
Constant buffer size: 65536
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 32768
Profiling timer resolution: 1
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue properties:
Out-of-Order: No
Profiling : Yes
Platform ID: 0287946C
Name: Cypress
Vendor: Advanced Micro Devices, Inc.
Driver version: CAL 1.4.838
Profile: FULL_PROFILE
Version: OpenCL 1.0 ATI-Stream-v2.1 (145
)
Extensions: cl_khr_icd cl_amd_fp64 cl_khr_g
lobal_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32
_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store
cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_media_ops cl_amd_d3d9_sha
ring
Passed!
When I try to run anything on device 1 I get a gpu driver crash and Windows reset my GFX card.
I tried with -S, same thing.
When I try to run it with -V I get tons of these, but no crash:
Code:
Difficulty: 77178
Compiling kernel, can take minutes...done!
WARNING: AMD BFI_INT patching failed
WARNING: Hardware verification mode enabled
[...]
Mismatch for kernel 0, offset 11625 (36,105)
Column X: 8D011A19FFCFC83765E7C9183F54C0102F225F99CE4D731E199D2DE132B57E1C
Column Y: B9C0EDDF879CACB24F5EF8F9CF8A94ECAB3528D5DD39D0901E107FCA3A108CC0
Expect X: 742AB35209A5091F55C7DDC1327C8E4CFE9023E2DA5AC21D368BF1A10959C535
Device X: DA285113C8858A679E8E6A0A1714EF7A132DF2C3DAC2859FD62614B88D8D311B
Expect Y: DAFF5A375AC83B2E8015478FFB6856DDCC801A41CC1DAC95BE9586D26AA3DB4B
Device Y: 01B17D502CFEE55704471C06CD865D2F69A5B4FC2816CF334D1E6C3CF9C68766
Expect Z: C0891F0B609392CBBB0029BE61367114C1E6A4AB8C1EA33D45BD74D8F3DA243A
Device Z: C0891F0B609392CBBB0029BE61367114C1E6A4AB8C1EA33D45BD74D9F3DA280B
Mismatch for kernel 0, offset 11626 (36,106)
Column X: 9AAF63EDBB1CBEAACAA1D4ED1C1CAEDCBF7BA3628678C90AA8A29B4392A58DBF
Column Y: CED1A461034FFF6CBAD66D4B9CF0BF7310739FA13747E6A08496FAD18E2894D2
Expect X: 84D9CF31D4935E89ECB2BD170EADD4B4553DBF0CD44D18055B42C1EFC8F80B26
Device X: D4F975DE6A472C15F24183407CB8523E233291548F3915C676AC29F63D5237C4
Expect Y: 784A6CBC4D099AC31ABC48798637DFB0A8CF4524C61AAE628A5D2E9DED0D9BB6
Device Y: 02A001D8EC30A6615C9B30E9B93B9487EFE115CCF8EABFE7691EDD66DB0D2B11
Expect Z: CE3768DF1BE0893F1FBA35933DFE5FE1523FE8744449F929D4C2E23B53CA33DD
Device Z: CE3768DF1BE0893F1FBA35933DFE5FE1523FE8744449F929D4C2E23C53CA37AE
Mismatch for kernel 0, offset 11627 (36,107)
Column X: B86846D0C9947C6DEFA57847CC92405BC404D1D1B4679CB8FD85C466E882ECE6
Column Y: 943902D74BDEF9CDA7B43C4636CB07DA7B1E840433EAE28E755061B3EAF3C03F
Expect X: D529B0EC71633FE3FFA9C6AA374F0F6F25F1F792877931E39E78EF5A1C50DAF4
Device X: 90A3E29BEA6862DD96A1D4833CF237987FBF717A27B9C915CAF997BA3F0E58FD
Expect Y: E77E104F5785407C43C6449C671EAE4E4ECC8BD4A0920C359215CA5E337C96D8
Device Y: 7AE89D45A28DFCA1580549B496AAF4CD5B6358F7326ED9E153BBE2474D5C92A9
Expect Z: EBF04BC22A58470244BDD8EDEE73F16056C916E37238CCD829A60B5EA9A79304
Device Z: EBF04BC22A58470244BDD8EDEE73F16056C916E37238CCD829A60B5FA9A796D5
Mismatch for kernel 0, offset 11628 (36,108)
Column X: AFA7B6FAAA16DCADDB318BD949F6E83BBB292BB0DED76691D963022D7AA48D1C
Column Y: 17395092C294991462F47326345F0B8C6B0C8850E28BBF74B9B2CC66157DCE96
Expect X: 6CA63CFA145CDA7D2A6340D36521D0E332A3E99CCB004D9E6DCF90FC15377FDE
Device X: F6E32772D966B45947E0DE5EB53CB1F435A6A44C30B6FCE14367D72C95C9914D
Expect Y: B1090B7BEA33676216CF297FA2AB58A609F55AB2AA2BB04C2A91BE8D66E76889
Device Y: 6D12B6382085773B9E84F02B0810B41BF0794070843B62E434838089EE3A2948
Expect Z: E32FBBEC0ADAA7423049EC7F6BD899404DED70C29CA896B1058349253BC9333A
Device Z: E32FBBEC0ADAA7423049EC7F6BD899404DED70C29CA896B1058349263BC9370B
Mismatch for kernel 0, offset 11629 (36,109)
Column X: C371146B49AE9B54A788F83C1F83F9CCBF12B293158D3D29FB35712A007BA30B
Column Y: 880564D427E1D723F705A524086290EF7E86D44B140FD8F86D61D973BA2653A2
Expect X: 16F953ED21ED79E02270E4A21140E64DA7D864110EDFF8ED704210D56B5D3E90
Device X: 7A46981014C96F3593ADF300C8426DE9BEBB4BFEBA4EF6055B21EB24BB88F328
Expect Y: 287595676FD3932D55DB02CA42CAEFEA4693D41B6F9BC81F8F72C9B7D5A582F9
Device Y: 7E3FB7508B7DAE6FD381453F9DBB64D33AAF4B98B8B076DD5A5B250FC2280A8A
Expect Z: F6F9195CAA7265E8FCA158E24165AAD151D6F7A4D35E6D492755B821C1A04929
Device Z: ^C
Mining with poclbm or bfgminer works fine.
Also when I try to run it again I get this:
Code:
Prefix difficulty: 77178 1xxx
Difficulty: 77178
Device: Cypress
Vendor: Advanced Micro Devices, Inc. (1002)
Driver: CAL 1.4.838
Profile: FULL_PROFILE
Version: OpenCL 1.0 ATI-Stream-v2.1 (145)
Max compute units: 20
Max workgroup size: 256
Global memory: 268435456
Max allocation: 268435456
OpenCL compiler flags:
Loading kernel binary 139fc8f28e6d8bac745374976f86bdef.oclbin
clBuildProgram: CL_BUILD_PROGRAM_FAILURE
Build log:
Internal error: Link failed.
Make sure the system setup is correct.
Available OpenCL platforms:
0: [Advanced Micro Devices, Inc.] ATI Stream
0: [AuthenticAMD] AMD Phenom(tm) II X4 965 Processor
1: [Advanced Micro Devices, Inc.] Cypress
I can only try again when I delete the 4.4MB (-S) or 6MB .bin file and recompile.
Any ideas?
The fix does not work, I compiled from source, updated CL kernel. I used APP SDK's OpenCL.dll and and amdocl64.dll files, but unfortunately the program hangs before it even prints "Compiling kernel". It doesn't crash, it just hangs with these DLLs and huge CPU usage, but nothing.
Thanks for the feedback, AppSDK 2.8 i presume. I'll try to get windows installed on my radeon machine tomorrow (thats why win32 is now just a wild guess) and take a look. Till then, consider only the linux version.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
The fix does not work, I compiled from source, updated CL kernel. I used APP SDK's OpenCL.dll and and amdocl64.dll files, but unfortunately the program hangs before it even prints "Compiling kernel". It doesn't crash, it just hangs with these DLLs and huge CPU usage, but nothing.
Warning, the link has binaries and no source. The file dates were not changed so this is likely virused up, not recompiled.
Actually, the vanitygen binaries are verbatim from official zip, plus just opencl dlls stitched in the archive. Naturally you should test on untrusted machine, as every binary code posted on forums.
For paranoid users, i'd recommend to use the linux version.
Then why does the github https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbe show that "the fix" is modified calc_addrs.cl, oclengine.c, oclvanitygen, etc which would indicate new binaries?
win32 is just downgrade of opencl compiler - no further changes made at this point.
I'll provide script to build resulting archive to avoid further implications.
I'n the meantime, I'd like to offer you 1BTC for factual evidence aforementioned archive is "virused up" - since it was created on a linux workstation, it is higly unlikely but I'd prefer to be on the safe side - I'm certainly no expert in that area. I've removed the link from my post, in case your accusation is proven to be true.
Warning, the link has binaries and no source. The file dates were not changed so this is likely virused up, not recompiled.
Actually, the vanitygen binaries are verbatim from official zip, plus just opencl dlls stitched in the archive. Naturally you should test on untrusted machine, as every binary code posted on forums.
For paranoid users, i'd recommend to use the linux version.
Then why does the github https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbe show that "the fix" is modified calc_addrs.cl, oclengine.c, oclvanitygen, etc which would indicate new binaries?
Warning, the link has binaries and no source. The file dates were not changed so this is likely virused up, not recompiled.
Actually, the vanitygen binaries are verbatim from official zip, plus just opencl dlls stitched in the archive. Naturally you should test on untrusted machine, as every binary code posted on forums.
For paranoid users, i'd recommend to use the linux version.
Hello,
I've created workaround for buggy 13.x catalyst driver, needs some testing though (especially the miner and win32).
For the impatient:
linux:
In case you get odd output like:
It means the compiler backend is still outputting broken code (although it compiles). To fix that try:
win32 binaries are available at:
https://www.dropbox.com/s/lddvyiyl58uhgio/vanitygen-0.22-catalystmod.zip
However received little to no testing, so comments are welcome.
The gory details:
https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbe
In short, ATI LLVM-IR backend miscompiles stuff like:
The boolean result of (a < b) is expressed as byte (u8 in crash report), but VLIW architectures know no such thing. Workaround is using artificially complex expressions which cannot be readily expressed as setcc in llvm ir (but will be optimized away during R600 lowering anyway).
I've created workaround for buggy 13.x catalyst driver, needs some testing though (especially the miner and win32).
For the impatient:
linux:
Code:
$ git clone https://github.com/wyuzhe/vanitygen.git
$ cd vanitygen
$ make oclvanitygen
$ ./oclvanitygen -vv -D x:y 1Blah
$ cd vanitygen
$ make oclvanitygen
$ ./oclvanitygen -vv -D x:y 1Blah
In case you get odd output like:
Code:
Match idx: 0
CPU hash: 0ecfec41290a506e784a4521597213398abf9a98
GPU hash: 08e030855f47c3141a5808d8767a89562ec5c655
Found delta: 497669 Start delta: 1
CPU hash: 0ecfec41290a506e784a4521597213398abf9a98
GPU hash: 08e030855f47c3141a5808d8767a89562ec5c655
Found delta: 497669 Start delta: 1
It means the compiler backend is still outputting broken code (although it compiles). To fix that try:
Code:
./catalystwrap ./oclvanitygen -vv -D 0:0 1ov
win32 binaries are available at:
https://www.dropbox.com/s/lddvyiyl58uhgio/vanitygen-0.22-catalystmod.zip
However received little to no testing, so comments are welcome.
The gory details:
https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbe
In short, ATI LLVM-IR backend miscompiles stuff like:
Code:
uint x, b, c;
uint x += (a < b)
uint x += (a < b)
The boolean result of (a < b) is expressed as byte (u8 in crash report), but VLIW architectures know no such thing. Workaround is using artificially complex expressions which cannot be readily expressed as setcc in llvm ir (but will be optimized away during R600 lowering anyway).
Warning, the link has binaries and no source. The file dates were not changed so this is likely virused up, not recompiled.
Jump to: