Bitcoin Forum
December 05, 2016, 08:52:18 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 [35] 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 ... 155 »
  Print  
Author Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22]  (Read 808656 times)
samr7
Full Member
***
Offline Offline

Activity: 140

Firstbits: 1samr7


View Profile
August 18, 2012, 07:28:10 AM
 #681

Grids of 256x256, 128x128, and 32x32 all segfault in the same way as the original:

So that didn't work, but at least now we can feel confident that it's not simply trying to allocate too much global memory.  Yet something certainly seems to be broken with resource allocation and clEnqueueMapBuffer().

I made some improvements to the error handling code in the git repository.  Please pull and try again.  It shouldn't segfault any more, and should give a more useful message at the end.

There are two other boilerplate things you can try: Safe mode (-S) and OpenCL verification mode (-V).

Code:
./oclvanitygen -d0 -v -S -b 128 -g 256x256 -i 1test

This doesn't work for vanitygen-0.19-win

It crashes on a DLL.

Perhaps I will try the LINUX version Smiley Thank you for the help!

Interesting, which DLL does it complain about?  Did you ever get it to work on Windows?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
samr7
Full Member
***
Offline Offline

Activity: 140

Firstbits: 1samr7


View Profile
August 18, 2012, 07:59:28 AM
 #682

Version 0.20 has been released.  Improvements include:

  • Oclvanitygen and oclvanityminer are now able to control multiple GPUs.
    This makes it simpler to manage oclvanitygen on systems with multiple GPUs.  To do this, you must use the new -D command line option, once for each GPU, and must specify the OpenCL platform ID and device ID for each GPU.  Example, for a mining system with three GPUs:
Code:
$ ./oclvanitygen -D 0:0 -D 0:1 -D 0:2 1MuLtiGPU
On a system with multiple GPUs, running oclvanitygen 1 or otherwise not specifying a device will cause it to display a list of OpenCL devices.  This list can be used to find the platform/device IDs.
  • Multiple pattern input files supported
    It's now possible to search for case-sensitive and case-insensitive prefixes concurrently.  Put each type in a separate file, and do something like:
    Code:
    $ ./vanitygen -f casesensitive.txt -i -f caseinsensitive.txt
    • Bug fixes
      Crash in vanitygen with -X option (thanks forum user foo)
      Case-insensitive search for prefixes containing I, O, and l should work now (thanks deepceleron)
      Oclvanitygen should now display the address correctly with -X option
      Oclvanityminer can now follow HTTP redirections
    • Oclvanityminer is now able to group together bounties by public key.
      This will be important in the future, when vanity pool gets more attention.  Bounties with the same public key are now processed concurrently, just like specifying multiple prefixes to oclvanitygen.  The economics of this are also taken into account when choosing a bounty or set of bounties.
    doca
    Jr. Member
    *
    Offline Offline

    Activity: 34


    View Profile WWW
    August 21, 2012, 03:52:21 AM
     #683

    Testing version 0.20 on CPU Xeon E5603 @1.60GHz with 2x GPU Nvidia Quadro NVS 295 .

    Running on first GPU oclvanitygen.exe -v -D 0:0 1doca
    Code:
    oclvanitygen.exe -v -D 0:0 1doca
    Prefix difficulty:            264104224 1doca
    Difficulty: 264104224
    Device: Quadro NVS 295
    Vendor: NVIDIA Corporation (10de)
    Driver: 301.32
    Profile: FULL_PROFILE
    Version: OpenCL 1.0 CUDA
    Max compute units: 1
    Max workgroup size: 512
    Global memory: 268435456
    Max allocation: 134217728
    OpenCL compiler flags: -DPRAGMA_UNROLL -cl-nv-verbose
    Loading kernel binary 326dd0c36930c6bea7602a3270b8186c.oclbin
    Grid size: 1024x512
    Modular inverse: 512 threads, 1024 ops each
    Using OpenCL prefix matcher
    GPU idle: 14.39%
    [136.18 Kkey/s][total 130023424][Prob 38.9%][50% in 6.5min]

    Running on second GPU (must be the one connected to display)
    Code:
    oclvanitygen.exe -v -D 0:1 1doca
    Prefix difficulty:            264104224 1doca
    Difficulty: 264104224
    Device: Quadro NVS 295
    Vendor: NVIDIA Corporation (10de)
    Driver: 301.32
    Profile: FULL_PROFILE
    Version: OpenCL 1.0 CUDA
    Max compute units: 1
    Max workgroup size: 512
    Global memory: 268435456
    Max allocation: 134217728
    OpenCL compiler flags: -DPRAGMA_UNROLL -cl-nv-verbose
    Loading kernel binary 326dd0c36930c6bea7602a3270b8186c.oclbin
    Grid size: 1024x512
    Modular inverse: 512 threads, 1024 ops each
    Using OpenCL prefix matcher
    GPU idle: 13.61%
    [115.99 Kkey/s][total 2097152][Prob 0.8%][50% in 26.0min]                      c
    lEnqueueUnmapMemObject(4): CL_INVALID_COMMAND_QUEUE
    clEnqueueMapBuffer(0): CL_INVALID_COMMAND_QUEUE
    clWaitForEvents(NDRange,0): CL_OUT_OF_RESOURCES
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_INVALID_COMMAND_QUEUE error executing CL_COMMAND_UNMAP_MEM_OBJECT on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).
    vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on Quadro NVS 295 (Device 0).

    Running on CPU vanitygen64
    Code:
    vanitygen64.exe -v 1doca
    Prefix difficulty:            264104224 1doca
    Difficulty: 264104224
    Using 4 worker thread(s)
    [431.31 Kkey/s][total 5718272][Prob 2.1%][50% in 6.9min]

    Running on CPU vanitygen
    Code:
    vanitygen.exe -v 1doca
    Prefix difficulty:            264104224 1doca
    Difficulty: 264104224
    Using 4 worker thread(s)
    [291.27 Kkey/s][total 7392256][Prob 2.8%][50% in 10.1min]

    I was not expecting that Quadro NVS 295 would be so slow: 130 Kkeys/s on GPU vs. 430 Kkeys/s on CPU.

    Any ideas why I got that crash on second GPU?

    samr7
    Full Member
    ***
    Offline Offline

    Activity: 140

    Firstbits: 1samr7


    View Profile
    August 21, 2012, 06:57:42 AM
     #684

    Testing version 0.20 on CPU Xeon E5603 @1.60GHz with 2x GPU Nvidia Quadro NVS 295 .

    Running on first GPU oclvanitygen.exe -v -D 0:0 1doca
    Code:
    ...

    Running on second GPU (must be the one connected to display)
    Code:
    ...
    Running on CPU vanitygen64
    Code:
    vanitygen64.exe -v 1doca
    Prefix difficulty:            264104224 1doca
    Difficulty: 264104224
    Using 4 worker thread(s)
    [431.31 Kkey/s][total 5718272][Prob 2.1%][50% in 6.9min]

    Running on CPU vanitygen
    Code:
    vanitygen.exe -v 1doca
    Prefix difficulty:            264104224 1doca
    Difficulty: 264104224
    Using 4 worker thread(s)
    [291.27 Kkey/s][total 7392256][Prob 2.8%][50% in 10.1min]

    I was not expecting that Quadro NVS 295 would be so slow: 130 Kkeys/s on GPU vs. 430 Kkeys/s on CPU.

    Any ideas why I got that crash on second GPU?

    Hi doca,

    Quadro NVS huh?  You must have a fancy multi-monitor stock broker setup.

    The performance you're getting from the GPU isn't too far off from what one might expect.  According to the Wikipedia article, the Quadro NVS 295 is based on G98 and has 8 CUDA cores with shader clock @ 1300 MHz.

    The simple formula for NVIDIA G90/GT200 devices is:

    Key/s = (CUDA cores) x (Shader clock MHz) x 17

    For the NVS 295, it's 177 Kkey/s, which means oclvanitygen is probably underperforming, and would benefit from tweaking.

    The failure is probably because oclvanitygen is trying to allocate too much GPU memory.  Try the following on your active GPU:

    Code:
    oclvanitygen -v -D 0:1,grid=128x128,invsize=512 1doca

    To tweak performance, change the invsize value to some larger or smaller power of two.  As long as the grid is large enough, there is a sweet spot for this parameter that will provide the best performance, and oclvanitygen might not be smart enough to choose it automatically.
    BkkCoins
    Hero Member
    *****
    Offline Offline

    Activity: 784


    firstbits:1MinerQ


    View Profile WWW
    August 21, 2012, 11:27:25 AM
     #685

    samr7,
    Is it possible for you to comment a little on what the difficulty number represents and how it's calculated. I tried looking thru the code and figuring it out but BN math and probability is definitely not my forte. I ended up being pretty confused.

    I'd like to be able to estimate the probability for a prefix pattern in my own code without running vanitygen - if not perfect mathematically then a rough time estimate would work.

    samr7
    Full Member
    ***
    Offline Offline

    Activity: 140

    Firstbits: 1samr7


    View Profile
    August 22, 2012, 12:51:59 AM
     #686

    samr7,
    Is it possible for you to comment a little on what the difficulty number represents and how it's calculated. I tried looking thru the code and figuring it out but BN math and probability is definitely not my forte. I ended up being pretty confused.

    I'd like to be able to estimate the probability for a prefix pattern in my own code without running vanitygen - if not perfect mathematically then a rough time estimate would work.

    Hi BkkCoins,

    Difficulty is the number of keys that have to be checked, on average, to find a match.

    The simplest way to do this is to have a table of prefix difficulties, and for each character after the beginning of the prefix, multiply by 58.  For this, you'd have something like:

    11 = 256
    12-1P = 22
    1Q = 65
    1R-1z = 1353

    So, 1Abc = 22 x 58 x 58 = 74008, and 1egg = 1353 x 58 x 58 = 4551492, which are very close to the exact difficulties.  This scheme wouldn't be very accurate for multiple leading 1s, and certain suffixes of 1Q, without special handling of those cases.


    The exact, but more complicated way to do this is to follow the formula:

    Difficulty = (Total addresses) / (Matching addresses)

    The tricky part is figuring out the number of matching addresses.  If your keys were 10-digit base-10 numbers, and you wanted to find everything with a prefix of 12345, with no leading 0s, then:

    Total keys = 10000000000
    Matches = 1234500000 ... 1234599999 = 100000 total matches
    Difficulty = 10000000000 / 100000 = 100000, or 1:100000 keys

    It's more complex to do this for base-58, but as in the example, the task is to convert a base-58 prefix into ranges of numbers that result in matches.  If you're interested, I will post more about this.
    BkkCoins
    Hero Member
    *****
    Offline Offline

    Activity: 784


    firstbits:1MinerQ


    View Profile WWW
    August 22, 2012, 01:32:53 AM
     #687

    The simplest way to do this is to have a table of prefix difficulties, and for each character after the beginning of the prefix, multiply by 58.  For this, you'd have something like:

    11 = 256
    12-1P = 22
    1Q = 65
    1R-1z = 1353

    So, 1Abc = 22 x 58 x 58 = 74008, and 1egg = 1353 x 58 x 58 = 4551492, which are very close to the exact difficulties.  This scheme wouldn't be very accurate for multiple leading 1s, and certain suffixes of 1Q, without special handling of those cases.
    Thank you. This is exactly what I need. Simple, if not 100% accurate. Difficulty is what I thought but wasn't sure about. Are those numbers good to use or just examples? My intention is to come up with a rough time estimate based on current MKeys/s. It doesn't matter if it's out somewhat as I will fudge the result with a safety factor based on past results (and any single run is random anyway).

    Thx again. I expect to send a donation your way if my project works out.

    axus
    Full Member
    ***
    Offline Offline

    Activity: 130


    View Profile
    August 22, 2012, 04:01:13 AM
     #688

    I try to use MinGW to compile on my Windows box, I had a little trouble compiling vanitygen here.  I got it working after including winglue.o in the objects and pasting code into winglue.c:

    http://fossies.org/dox/R-2.15.1/glpi_8h_source.html
    doca
    Jr. Member
    *
    Offline Offline

    Activity: 34


    View Profile WWW
    August 22, 2012, 04:25:57 AM
     #689

    Hi samr7!

    Quadro NVS huh?  You must have a fancy multi-monitor stock broker setup.
    I wish I have a Metastock with BTC trade feed! No, just 2 cards, no monitors at all.

    The performance you're getting from the GPU isn't too far off from what one might expect.  According to the Wikipedia article, the Quadro NVS 295 is based on G98 and has 8 CUDA cores with shader clock @ 1300 MHz.

    The simple formula for NVIDIA G90/GT200 devices is:

    Key/s = (CUDA cores) x (Shader clock MHz) x 17

    For the NVS 295, it's 177 Kkey/s, which means oclvanitygen is probably underperforming, and would benefit from tweaking.

    The failure is probably because oclvanitygen is trying to allocate too much GPU memory.  Try the following on your active GPU:

    Code:
    oclvanitygen -v -D 0:1,grid=128x128,invsize=512 1doca

    To tweak performance, change the invsize value to some larger or smaller power of two.  As long as the grid is large enough, there is a sweet spot for this parameter that will provide the best performance, and oclvanitygen might not be smart enough to choose it automatically.
    Thanks! Very interesting!

    Now second card runs smooth! Thanks!
    Code:
    oclvanitygen -D 0:1,grid=128x128,invsize=512 1doca
    Difficulty: 264104224
    [94.62 Kkey/s][total 2621440][Prob 1.0%][50% in 31.8min]

    Two card running same time:
    Code:
    oclvanitygen -D 0:0 -D 0:1,grid=128x128,invsize=512 1doca
    Difficulty: 264104224
    [229.34 Kkey/s][total 16072704][Prob 5.9%][50% in 12.1min]

    Gee! I have so much fun!

    doca
    Jr. Member
    *
    Offline Offline

    Activity: 34


    View Profile WWW
    August 22, 2012, 04:38:09 AM
     #690

    More tests:

    oclvanitygen -v -D 0:0 1BitcoinMX - runs fine.

    oclvanitygen -v -S -D 0:0 1BitcoinMX - dies:
    Code:
    oclvanitygen -v -S -D 0:0 1BitcoinMX
    Prefix difficulty:     2938077882634386 1BitcoinMX
    Difficulty: 2938077882634386
    Device: Quadro NVS 295
    Vendor: NVIDIA Corporation (10de)
    Driver: 301.32
    Profile: FULL_PROFILE
    Version: OpenCL 1.0 CUDA
    Max compute units: 1
    Max workgroup size: 512
    Global memory: 268435456
    Max allocation: 134217728
    OpenCL compiler flags: -cl-nv-verbose
    Loading kernel binary 582f54c79b215f43c3960bbd6fd612d0.oclbin
    Grid size: 1024x512
    Modular inverse: 512 threads, 1024 ops each
    Using OpenCL prefix matcher
    clWaitForEvents(NDRange,e): CL_OUT_OF_RESOURCES
    GPU idle: 9.72%
    Halting...done!

    jasinlee
    Hero Member
    *****
    Offline Offline

    Activity: 742


    Its as easy as 0, 1, 1, 2, 3


    View Profile
    August 22, 2012, 05:21:21 AM
     #691

    Is there a way to have the txt file its populating only fill in the private key or only the vanity key or just the 2? I am using command line and cant figure a method.

    BTC 1JASiNZxmAN1WBS4dmGEDoPpzN3GV7dnjX DVC 1CxxZzqcy7YEVXfCn5KvgRxjeWvPpniK3                     Earn Devcoins Devtome.com
    BkkCoins
    Hero Member
    *****
    Offline Offline

    Activity: 784


    firstbits:1MinerQ


    View Profile WWW
    August 22, 2012, 08:47:39 AM
     #692

    Is there a way to have the txt file its populating only fill in the private key or only the vanity key or just the 2? I am using command line and cant figure a method.
    I don't think there is that option in the program but it's trivial to do after at the command line.

    eg. make file with addresses,

    grep Address outfile > addrfile

    or keys,

    grep Privkey outfile > keyfile

    or convert addresses to sql statements to populate db,

    grep Address outfile |awk '{print "insert into addr set address=\""$2"\";"}' > addrfile.sql

    UNOE
    Sr. Member
    ****
    Offline Offline

    Activity: 259



    View Profile
    August 22, 2012, 08:57:57 AM
     #693

    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 got similar problem as The00Dustin (quoted below). I think it is an issue with BFI_INT feature. It seems that sometimes it is detected when it is not supported. I commented out detection and it started to work.
    Code:
    if (vg_ocl_device_gettype(vocp->voc_ocldid) &
        CL_DEVICE_TYPE_GPU) {
    quirks |= VG_OCL_EXPENSIVE_BRANCHES;
    quirks |= VG_OCL_DEEP_VLIW;
    dvn = vg_ocl_device_getstr(vocp->voc_ocldid,
       CL_DEVICE_EXTENSIONS);
    #if 0
    if (dvn && strstr(dvn, "cl_amd_media_ops"))
    quirks |= VG_OCL_AMD_BFI_INT;
    #endif

    dvn = vg_ocl_device_getstr(vocp->voc_ocldid,
       CL_DEVICE_NAME);
    if (!strcmp(dvn, "ATI RV710")) {
    quirks &= ~VG_OCL_OPTIMIZATIONS;
    quirks |= VG_OCL_NO_BINARIES;
    }
    }

    [...]There was nothing wrong with libdl-*.**.so, however, for whatever reason, ld wasn't using it.  I had to add it directly to the LIBS variable.  This is what finally got me building:
    Code:
    LIBS=-L/usr/src/ati-stream-sdk-v2.1-lnx64/lib/x86_64 -L/usr/local/ssl/lib /lib64/libdl.so.2 -lpcre -lcrypto -lm -lpthread
    CFLAGS=-I/usr/src/ati-stream-sdk-v2.1-lnx64/include -I/usr/local/ssl/include -I/usr/include -ggdb -O3 -Wall
    Note that the ATI SDK is in a funny place because that's just where I happened to download it to.  I have never had to list a library directly in libs like that before (/lib64/libdl.so.2 with no leading parameter), but it worked.  Unfortunately, now I'm getting odd output in oclvanitygen compared to what I see in vanitygen:
    Code:
    $ ./vanitygen -i 1s
    Difficulty: 1353
    Pattern: 1s
    Address: 1sWTv45ThMSacEG9TwLXAECycSj5ybrQm
    Privkey: 5HxV9CtT43oXoH4ZrWrbi57UJih88KgAxpVtLss992S12XiqHX2
    $ ./oclvanitygen -i 1s
    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]                           Match idx: 0
    CPU hash: 5fb13b13d1b464cfa6f2c53d81d7333483d0ec38
    GPU hash: 133bb15fcf64b4d13dc5f2a63433d78138ecd083
    Found delta: 1918 Start delta: 1
    Match idx: 0
    CPU hash: 93b30d0ad99f8133a0bc3c4793a27dbad5a0961f
    GPU hash: 0a0db39333819fd9473cbca0ba7da2931f96a0d5
    Found delta: 1919 Start delta: 1
    Match idx: 0
    CPU hash: 8030c41b205cf1c395f79223acc4731c8138e2eb
    GPU hash: 1bc43080c3f15c202392f7951c73c4acebe23881
    Found delta: 1918 Start delta: 1
    Match idx: 0
    CPU hash: aa8c368c9663f1f15929f4f745d04039fa3403e1
    GPU hash: 8c368caaf1f16396f7f429593940d045e10334fa
    Found delta: 1918 Start delta: 1
    Match idx: 0
    CPU hash: a58e04ee7573ae115fed373b0a316c99227de01d
    GPU hash: ee048ea511ae73753b37ed5f996c310a1de07d22
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: c968065a9670c24c3654930612e70821f5a37082
    GPU hash: 5a0668c94cc27096069354362108e7128270a3f5
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: 7652fe86bd2a45e82ce111d91ea3a3e8e9e55ab7
    GPU hash: 86fe5276e8452abdd911e12ce8a3a31eb75ae5e9
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: 757327d079aace35e53aa1cfcf614c552050198f
    GPU hash: d027737535ceaa79cfa13ae5554c61cf8f195020
    Found delta: 1662 Start delta: 1
    Match idx: 0
    CPU hash: 5af81f2dc428a8be30f05bb23023bce81553d1ec
    GPU hash: 2d1ff85abea828c4b25bf030e8bc2330ecd15315
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: 6fa912748c64f7773a1a6acd8d71058e8684abba
    GPU hash: 7412a96f77f7648ccd6a1a3a8e05718dbaab8486
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: 9f6eab09f51fe0d2ab7ef29ca6176060275c41e4
    GPU hash: 09ab6e9fd2e01ff59cf27eab606017a6e4415c27
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: 76f461d52e6767dc1295a3c00d7f28509cc08894
    GPU hash: d561f476dc67672ec0a3951250287f0d9488c09c
    Found delta: 1789 Start delta: 1
    Match idx: 0
    CPU hash: 623bc0be24cdb542e5005d99850fed085446efee
    GPU hash: bec03b6242b5cd24995d00e508ed0f85eeef4654
    Found delta: 1919 Start delta: 1
    Match idx: 0
    CPU hash: 9503160dcca12038ac91bce298c6c19cd90416f5
    GPU hash: 0d1603953820a1cce2bc91ac9cc1c698f51604d9
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: 63dab8e0ea34d295b5b1c89e0ca3eaddbbb61b8e
    GPU hash: e0b8da6395d234ea9ec8b1b5ddeaa30c8e1bb6bb
    Found delta: 1661 Start delta: 1
    Match idx: 0
    CPU hash: b46a27a9fbfcc13da644dcb0306c194f518c3e0c
    GPU hash: a9276ab43dc1fcfbb0dc44a64f196c300c3e8c51
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: cc1b6bffbb824d51af3283aeafd4b6fd920b6d7d
    GPU hash: ff6b1bcc514d82bbae8332affdb6d4af7d6d0b92
    Found delta: 1919 Start delta: 1
    Match idx: 0
    CPU hash: 89d906b7e85d7de50b5ed49f1e17394e5b8ee641
    GPU hash: b706d989e57d5de89fd45e0b4e39171e41e68e5b
    Found delta: 1791 Start delta: 1
    Match idx: 0
    CPU hash: a853bf32a17a879e53d5a853bbc34d17df85b3ef
    GPU hash: 32bf53a89e877aa153a8d553174dc3bbefb385df
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: acf951a982fed9f51b06435194b520dbc3922043
    GPU hash: a951f9acf5d9fe825143061bdb20b594432092c3
    Found delta: 1660 Start delta: 1
    Match idx: 0
    CPU hash: 574b20f25084db069658757cc2c4deb3413f3ed2
    GPU hash: f2204b5706db84507c755896b3dec4c2d23e3f41
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: 55947ac666958b1183d8a2707856b6f19bd9faa7
    GPU hash: c67a9455118b956670a2d883f1b65678a7fad99b
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: a934e3675124d3f9ddc3ea5a7e4819c6114eb1bf
    GPU hash: 67e334a9f9d324515aeac3ddc619487ebfb14e11
    Found delta: 1918 Start delta: 1
    Match idx: 0
    CPU hash: 72b549d5733b52c7525cbba4b51930567b3f9b6d
    GPU hash: d549b572c7523b73a4bb5c52563019b56d9b3f7b
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: b904cbfd46e83da6bbe15ef8755db40220c0beaa
    GPU hash: fdcb04b9a63de846f85ee1bb02b45d75aabec020
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: 81c411b505bc4fe0f4c2d4ffb5a5b17e51f8e2c9
    GPU hash: b511c481e04fbc05ffd4c2f47eb1a5b5c9e2f851
    Found delta: 1789 Start delta: 1
    Match idx: 0
    CPU hash: 5e5e3718b26724de3d92922b977ddce417f4f8e8
    GPU hash: 18375e5ede2467b22b92923de4dc7d97e8f8f417
    Found delta: 1791 Start delta: 1
    Match idx: 0
    CPU hash: cbeb1025944ab7139b3bbc29923617e137efb1c4
    GPU hash: 2510ebcb13b74a9429bc3b9be1173692c4b1ef37
    Found delta: 1791 Start delta: 1
    Match idx: 0
    CPU hash: 6c176e5f44008808fa6cadfb7cb429bf2315f9fc
    GPU hash: 5f6e176c08880044fbad6cfabf29b47cfcf91523
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: a98813ecdde88513abd56cb716655b5d937eb183
    GPU hash: ec1388a91385e8ddb76cd5ab5d5b651683b17e93
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 9e930230116b77ea0051e81de1ab018f4f351ef0
    GPU hash: 3002939eea776b111de851008f01abe1f01e354f
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: 595e56866c2098b493968260ce50ab0eaa4f5c4a
    GPU hash: 86565e59b498206c608296930eab50ce4a5c4faa
    Found delta: 1791 Start delta: 1
    Match idx: 0
    CPU hash: a998337cf7fa5c66aaf969d7ab7e19b4b28b9660
    GPU hash: 7c3398a9665cfaf7d769f9aab4197eab60968bb2
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: c45cd65b2abf95e42ef5a6bab972c1f6e2c19b00
    GPU hash: 5bd65cc4e495bf2abaa6f52ef6c172b9009bc1e2
    Found delta: 1784 Start delta: 1
    Match idx: 0
    CPU hash: 6faa2cd4489758678fcf13f213ecc31f9160e5e7
    GPU hash: d42caa6f67589748f213cf8f1fc3ec13e7e56091
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 7282c8273e79b01838bbf6130d57db9c80c81c4b
    GPU hash: 27c8827218b0793e13f6bb389cdb570d4b1cc880
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 92261bbb216416166f7d6223f1bbd4328828da64
    GPU hash: bb1b26921616642123627d6f32d4bbf164da2888
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 6f09ca0b54527e56bd1f0a602a4d4b9d9eea36dd
    GPU hash: 0bca096f567e5254600a1fbd9d4b4d2add36ea9e
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 7265677be9bd57042182aa05212ef1e422514a4e
    GPU hash: 7b6765720457bde905aa8221e4f12e214e4a5122
    Found delta: 1791 Start delta: 1
    Match idx: 0
    CPU hash: a100c4db9def04e45734f7b9adf98c8c5b83a47c
    GPU hash: dbc400a1e404ef9db9f734578c8cf9ad7ca4835b
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 6b366d5d394cb6afc2f4a55b2297145ca6472751
    GPU hash: 5d6d366bafb64c395ba5f4c25c149722512747a6
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: aa7a26f736df1668c8eeda86fa273181dfa734bc
    GPU hash: f7267aaa6816df3686daeec8813127fabc34a7df
    Found delta: 1791 Start delta: 1
    Match idx: 0
    CPU hash: a570a96b24dc5e6ba1af9e1eb97aab12353ae21b
    GPU hash: 6ba970a56b5edc241e9eafa112ab7ab91be23a35
    Found delta: 1790 Start delta: 1
    Match idx: 0
    CPU hash: 95a32b74df1473c406f246f531922f048604bcb4
    GPU hash: 742ba395c47314dff546f206042f9231b4bc0486
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: c8699cbc61465825e1cf9020d450f6d5a85c5a63
    GPU hash: bc9c69c8255846612090cfe1d5f650d4635a5ca8
    Found delta: 1918 Start delta: 1
    Match idx: 0
    CPU hash: 8ef42dbbae1b15194deff71edfe23e78b0dae0f4
    GPU hash: bb2df48e19151bae1ef7ef4d783ee2dff4e0dab0
    Found delta: 1663 Start delta: 1
    Match idx: 0
    CPU hash: b9b16349b60b4fd9de74dff4807aabd947e98630
    GPU hash: 4963b1b9d94f0bb6f4df74ded9ab7a803086e947
    Found delta: 2047 Start delta: 1
    Match idx: 0
    CPU hash: 715c26f488c6cd2a2aa4b5d88318e7328d6fdd8c
    GPU hash: f4265c712acdc688d8b5a42a32e718838cdd6f8d
    Found delta: 2047 Start delta: 1
    ^C
    Is that output normal?  Seems I can clean it up by doing this:
    Code:
    ./oclvanitygen -i 1s 2> /dev/null | grep e
    [181.98 Kkey/s][total 2048][Prob 78.0%][80% in 0.0s]
    [153.17 Kkey/s][total 184320]
    [154.25 Kkey/s][total 337920]
    [154.82 Kkey/s][total 493568]
    [154.60 Kkey/s][total 649216]
    [154.86 Kkey/s][total 804864]
    [155.35 Kkey/s][total 960512]
    [155.05 Kkey/s][total 1116160]
    [155.53 Kkey/s][total 1271808]
    since e will include "key/s", "Address", and "Privkey", but still get a lot more unnecessary data onscreen, and as you can see here, no addresses or privkeys are displayed in either of the oclvanitygen ouputs even though it should still find a match almost instantly ("[80% in 0.0s]").  This makes me wonder if something is broken in my setup.

    I then discovered that running oclvanitygen with no parameters returns help info, so it looks like if this output is normal, I'll just have it write keys to a file since some searching shows other people using grep with regular expressions to filter output on oclvanitygen (assuming there's not something broken about the fact that it didn't find any keys).  However, the speed is slower than vanitygen, so I thought it must be using the CPU instead of the GPU, searched the thread and found the -d option, which confirms this:
    Code:
    ./oclvanitygen -d 2 -i 1ssss | grep e
    Difficulty: 17606948
    Available OpenCL platforms:
    0: [Advanced Micro Devices, Inc.] ATI Stream
      0: [GenuineIntel] Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
      This machine is mining fine with cgminer compiling using the SDK links I listed in the LIBS & CFLAGS variables.  Am I missing something completely obvious?

    EDIT:  I just realized that when I run oclvanitygen on Windows, the output looks the same as my compiled vanitygen on F15, so I don't know if that means my oclvanitygen output on F15 is odd or not.  I also tried a lot more LIBS and CFLAGS stuff trying to make sure it was linking the right files, but none of that made any difference, and then I realized my last output above does say "0: [Advanced Micro Devices, Inc.] ATI Stream" which implies the right files were used anyway.  Then the obvious clicked, regarding the card not being found, I wasn't using DISPLAY=:0 (duh...).  So now I'm just curious about the extraneous output on oclvanitygen as I compiled it vs vanitygen as I compiled it and oclvanitygen on Windows.

    EDIT2:  ACK!  The kernel compiled and ran once, but was still really slow and now I get this:
    Code:
    $ DISPLAY=:0 ./oclvanitygen -d 1 -i 1ssss | grep e
    Difficulty: 17606948
    clBuildProgram: CL_BUILD_PROGRAM_FAILURE
    Build log:
    Internal error: Link failed.
    Make sure the system setup is correct.
    Device: Cypress
    Vendor: Advanced Micro Devices, Inc. (1002)
    Driver: CAL 1.4.1417
    Profile: FULL_PROFILE
    Version: OpenCL 1.0 ATI-Stream-v2.1 (145)
    Max compute units: 14
    Max workgroup size: 256
    Global memory: 268435456
    Max allocation: 268435456
    $

    Math Man
    Full Member
    ***
    Offline Offline

    Activity: 150


    View Profile
    August 25, 2012, 06:12:56 AM
     #694

    AMD GCN, NVIDIA Fermi/Kepler: Please contribute some numbers!

    I'm getting 31.5 Mkey/s on a GTX 680 (Kepler) with 1300 MHz core clock and 29.25 Mkey/s at 1162 MHz core.
    Ferroh
    Full Member
    ***
    Offline Offline

    Activity: 141



    View Profile WWW
    August 28, 2012, 01:58:12 AM
     #695

    I tried oclvanitygen today, and discovered that it produces output like the following, instead of private keys.

    Code:
    Match idx: 0
    CPU hash: 93b30d0ad99f8133a0bc3c4793a27dbad5a0961f
    GPU hash: 0a0db39333819fd9473cbca0ba7da2931f96a0d5
    Found delta: 1919 Start delta: 1

    Am I doing it wrong?
    fcmatt
    Legendary
    *
    Offline Offline

    Activity: 1106


    View Profile
    August 28, 2012, 02:49:13 AM
     #696

    what is the most creative/long vanity address found to date?
    doca
    Jr. Member
    *
    Offline Offline

    Activity: 34


    View Profile WWW
    August 28, 2012, 03:29:57 AM
     #697

    I saw this one - http://www.blockchain.info/fb/1Bitcoin (the web site is dowwn for maintenance now).

    stevegee58
    Hero Member
    *****
    Offline Offline

    Activity: 783



    View Profile
    August 28, 2012, 10:49:23 AM
     #698

    I tried oclvanitygen today, and discovered that it produces output like the following, instead of private keys.

    Code:
    Match idx: 0
    CPU hash: 93b30d0ad99f8133a0bc3c4793a27dbad5a0961f
    GPU hash: 0a0db39333819fd9473cbca0ba7da2931f96a0d5
    Found delta: 1919 Start delta: 1

    Am I doing it wrong?

    What's your command line?

    You are in a maze of twisty little passages, all alike.
    runlinux
    Hero Member
    *****
    Offline Offline

    Activity: 567



    View Profile WWW
    August 28, 2012, 12:42:06 PM
     #699

    I get the same output with

    Code:
    oclvanitygen.exe -d 0 -i 1Test

    He's not the only one with the issue.

    The00Dustin
    Hero Member
    *****
    Offline Offline

    Activity: 806


    View Profile
    August 28, 2012, 02:01:22 PM
     #700

    He's not the only one with the issue.
    I think I had that same issue trying to gpu-mine with self-compiled code on linux.  I just gave up and use Windows.
    Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 [35] 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 ... 155 »
      Print  
     
    Jump to:  

    Sponsored by , a Bitcoin-accepting VPN.
    Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!