Author

Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 159. (Read 1153383 times)

vip
Activity: 574
Merit: 500
Don't send me a pm unless you gpg encrypt it.
I've got an OpenCL error running oclvanitygen on a Mac (NVIDIA Geforce GT 120):

A "Failed to wait for events" error; is this an OSX-specific OpenCL error, or have others run into this? How can I diagnose what is going wrong here?
My guess is that the kernel is only for AMD and the NVIDIA architecture isn't ideal for this kind of thing.

Aye.
hero member
Activity: 560
Merit: 500
I am the one who knocks
I've got an OpenCL error running oclvanitygen on a Mac (NVIDIA Geforce GT 120):

A "Failed to wait for events" error; is this an OSX-specific OpenCL error, or have others run into this? How can I diagnose what is going wrong here?
My guess is that the kernel is only for AMD and the NVIDIA architecture isn't ideal for this kind of thing.
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Are there going to be addresses that start with a 3?

Will the new version of vanitygen generate addresses that start with a 3 ?
member
Activity: 68
Merit: 10
I've got an OpenCL error running oclvanitygen on a Mac (NVIDIA Geforce GT 120):

Code:
vg_ocl_context_callback error: [CL_OUT_OF_RESOURCES] : OpenCL Error : Failed to wait for events! Event 0 in waitlist failed. Out of resources
vg_ocl_context_callback error: [CL_INVALID_KERNEL] : OpenCL Error : Failed to wait for events! Event 0 in waitlist failed. Invalid kernel object
vg_ocl_context_callback error: [CL_INVALID_KERNEL] : OpenCL Error : Failed to wait for events! Event 0 in waitlist failed. Invalid kernel object
vg_ocl_context_callback error: [CL_INVALID_COMMAND_QUEUE] : OpenCL Fatal Error : Finish caused an error that invalidated the queue (0x100321550). This may be  due to a resource allocation failure at execution time.
vg_ocl_context_callback error: [CL_INVALID_COMMAND_QUEUE] : OpenCL Error : clCommandDispatch failed: flushing queue for blocking call.
vg_ocl_context_callback error: [CL_INVALID_COMMAND_QUEUE] : OpenCL Error : clEnqueueMapBuffer failed: Invalid command queue
clEnqueueMapBuffer(0): CL_INVALID_COMMAND_QUEUE
Device: GeForce GT 120
Vendor: NVIDIA (1022600)
Driver: CLH 1.0
Profile: FULL_PROFILE
vg_ocl_context_callback error: [CL_INVALID_COMMAND_QUEUE] : OpenCL Error : clEnqueueNDRangeKernel failed: queue (0x100321550) has been invalidated.
Version: OpenCL 1.0
clEnqueueNDRange(0): CL_INVALID_COMMAND_QUEUE
Max compute units: 140733193388036
Device: GeForce GT 120
Max workgroup size: 512
Vendor: NVIDIA (1022600)
Global memory: 536870912
Driver: CLH 1.0
Max allocation: 134217728
Profile: FULL_PROFILE
Segmentation fault

A "Failed to wait for events" error; is this an OSX-specific OpenCL error, or have others run into this? How can I diagnose what is going wrong here?
sr. member
Activity: 466
Merit: 250
Previous versions worked but 0.19 seems to crash everytime. It actually crashed the whole computer once.

This is what I'm using

oclvanitygen -d 0 1bitcoin

Using 6970 with stock settings on windows 7 64bit. Help, anyone Cheesy

Could be a problem with my GPU since CPU works perfectly?
I don't know, GPU mines normally with cgminer.
sr. member
Activity: 266
Merit: 250
Could we possibly get a version for bbqcoin?
#bbqcoin on freenode
foo
sr. member
Activity: 409
Merit: 250
Version 0.19 seems to always crash when using the -X option.

Code:
% ./vanitygen -X
Segmentation fault
legendary
Activity: 1512
Merit: 1036
It's been a while since vanitygen has been updated.  I went through the earlier posts on this thread, and have tried to summarize the most common issues and feature requests:
...
The FAQ could certainly do a better job of explaining how to launch vanitygen.  Deepceleron, I really liked your earlier post, it has instructions that are very clear and concise.  If it's okay with you, I'd like to merge that into the FAQ.
Congrats on your return. You can use or re-purpose anything I wrote, with or without attribution. Thanks for your software!

Anything else?

When specifying a case-insensitive address prefix on the command line or in a text file list, you must still 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

This could be fixed so that if a case-insensitive search is being done, the user doesn't have to use correct case as input.
legendary
Activity: 1014
Merit: 1001
thats a roundabout way
legendary
Activity: 1014
Merit: 1001
It would make it easier if the output format of vanitygen would be:
1Abcdefffffffffffffffffffffffff:5efghijjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
legendary
Activity: 1014
Merit: 1001
Thats right, if you have lots of keys generated, the copy/paste method is not very straight forward.
sr. member
Activity: 457
Merit: 251
Just export the keys to a txt file and from there you can copy/paste anywhere.

If I export them to a file from within vanitygen, the output I get is:
Quote
Pattern: 1
Pattern: 1
Address: 19d7BcmUojcjbZCQdgyyMdF6vkcr1Uptp4
Privkey: 5K31RbWA1cSvzffFQs3RZ5FjkGVrPBMFeH5JWeMPYdaXxPoKcWW
Pattern: 1
Address: 135Q1BZoGJwPDRDu86e4FGHMf1M5DzXsH4
Privkey: 5JXaoFt6nnEJtBHckbv7TmckxnkjM755YwxEmKiaMC3vpdP8BUA
Pattern: 1
Address: 18vWN5SH6PD4ZDs328gyajYfFpW7yVpAd9
Privkey: 5JGMh8xTMEbb1BfooVLAzb4kwaQvKLephs9cqxjt7R5KGB7zBoF
Pattern: 1
Address: 1LuoA362xB8disiwgV6Vah9PshF1tX8rm3
Privkey: 5Jz5D1Qth7P1XiwDTqwcBUwANzHVRhGzPw5i9tXFoJntxW3m4hk
Pattern: 1
Address: 16NuvRiSWcfURCQH9kf6XoWNy6VvFgmQH6
Privkey: 5JWZf1N4Vwoecatuxtoi9nnc1cAsrSdTWXpPZdHDp2zpLRn3ijf

and so on and so on. I don't think I can directly use those for importing, but instead I would have to individually copy and paste each privkey. And that is difficult Tongue
Perhaps I've used the wrong setting? (-o ./found.txt)
sr. member
Activity: 457
Merit: 251
I compared 0.17 to 0.19 but i see no speed difference.

Apparently, no speed improvements or performance-oriented changes to the kernels within the changelog.

Quote
Version 0.17, released August 8, 2011:
   - Bugfix for private key encoder, could create encodings not
     accepted by showwallet branch bitcoin
   - Remove oclvanitygen #pragma unroll by default, enable for NVIDIA
     (General performance improvement, hopeful resolution for crashing)
   - Oclvanitygen work size configuration tweak for smaller GPUs
   - New oclvanitygen add/subtract/compare functions for AMD Radeon
   - Add support for AMD BFI_INT instruction in oclvanitygen hash functions
   - Minor source code reorganization

Version 0.18, released July 4, 2012:
   - Support additive base public keys for outsourced address generation.
   - New oclvanityminer program, organized address miner for use with
     bounty pools, like ThePiachu's Vanity Pool.
   - New keyconv program for converting bitcoin private keys between
     wallet import format, password-protected format, and PKCS#8.
   - Support generation of simple P2SH (type-3) addresses.
   - Mac OS X makefile merged with Linux Makefile.

Version 0.19, released July 4, 2012:
   - Fix a potentially serious crash.
   - Remove oclvanitygen "-r" option.
legendary
Activity: 1014
Merit: 1001
Just export the keys to a txt file and from there you can copy/paste anywhere.

I compared 0.17 to 0.19 but i see no speed difference.
sr. member
Activity: 457
Merit: 251
Is it possible (for you) to add a feature similar to how the vanitygen exports to a file, but with only the privkeys, so that it could be easily mass-imported into Armory or using pywallet?
legendary
Activity: 1014
Merit: 1001
Thanks, it works now.
full member
Activity: 140
Merit: 430
Firstbits: 1samr7
where can i download it?

There, the front page is fixed.  Binaries are here.
legendary
Activity: 1014
Merit: 1001
I figured it out.  Sorry folks.

Version 0.19 is out now.  Hope this one lasts more than nine hours.
where can i download it?
legendary
Activity: 916
Merit: 1003
Wow I wonder why mine worked.
Jump to: