Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    [Dev] NeoScrypt GPU Miner - Public Beta Test

    Technical Development
    52
    802
    574829
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      daimyo last edited by

      alright, got it finally but no ping from the pool.ftc-c.com

      lets try it for pxc

      update:

      Working fine with morehash.pw NOMP pool. Pulling out the same hashrate 8.35khs out of GT 550M only now not getting the graphics driver unresponsive upon shutting down the miner.

      1 Reply Last reply Reply Quote 0
      • lizhi
        lizhi last edited by

        Here it is for one of my oldest mining rigs. Two HD6750 (the same to HD5750) + one HD5870. Catalyst 11.12 + APP SDK v2.6. The drivers cannot be updated any further because AMD have disregarded the OpenCL support for Windows XP and 2003 since spring of 2012. These cards deliver 2x 200KH/s + 380KH/s in Scrypt using the standard (ckolivas) kernel. If we make it running there, the other cards and platforms will be also compatible most likely. The general idea is to make the kernel compatible with the largest possible selection of computer hardware.

        [spoiler]

        Number of platforms: 2

        Platform Profile: FULL_PROFILE

        Platform Version: OpenCL 1.1 AMD-APP (831.4)

        Platform Name: AMD Accelerated Parallel Processing

        Platform Vendor: Advanced Micro Devices, Inc.

        Platform Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices

        Platform Profile: FULL_PROFILE

        Platform Version: OpenCL 1.1 CUDA 4.1.1

        Platform Name: NVIDIA CUDA

        Platform Vendor: NVIDIA Corporation

        Platform Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll

        Platform Name: AMD Accelerated Parallel Processing

        Number of devices: 4

        Device Type: CL_DEVICE_TYPE_GPU

        Device ID: 4098

        Board name: AMD Radeon HD 6700 Series

        Max compute units: 9

        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

        Native vector width char: 16

        Native vector width short: 8

        Native vector width int: 4

        Native vector width long: 2

        Native vector width float: 4

        Native vector width double: 0

        Max clock frequency: 925Mhz

        Address bits: 32

        Max memory allocation: 536870912

        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: 2048

        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: Yes

        Round to +ve and infinity: Yes

        IEEE754-2008 fused multiply-add: Yes

        Cache type: None

        Cache line size: 0

        Cache size: 0

        Global memory size: 536870912

        Constant buffer size: 65536

        Max number of constant args: 8

        Local memory type: Scratchpad

        Local memory size: 32768

        Kernel Preferred work group size multiple: 64

        Error correction support: 0

        Unified memory for Host and Device: 0

        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: 000000000164C9C8

        Name: Juniper

        Vendor: Advanced Micro Devices, Inc.

        Device OpenCL C version: OpenCL C 1.1

        Driver version: CAL 1.4.1646

        Profile: FULL_PROFILE

        Version: OpenCL 1.1 AMD-APP (831.4)

        Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt

        Device Type: CL_DEVICE_TYPE_GPU

        Device ID: 4098

        Board name: AMD Radeon HD 6700 Series

        Max compute units: 9

        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

        Native vector width char: 16

        Native vector width short: 8

        Native vector width int: 4

        Native vector width long: 2

        Native vector width float: 4

        Native vector width double: 0

        Max clock frequency: 925Mhz

        Address bits: 32

        Max memory allocation: 536870912

        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: 2048

        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: Yes

        Round to +ve and infinity: Yes

        IEEE754-2008 fused multiply-add: Yes

        Cache type: None

        Cache line size: 0

        Cache size: 0

        Global memory size: 536870912

        Constant buffer size: 65536

        Max number of constant args: 8

        Local memory type: Scratchpad

        Local memory size: 32768

        Kernel Preferred work group size multiple: 64

        Error correction support: 0

        Unified memory for Host and Device: 0

        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: 000000000164C9C8

        Name: Juniper

        Vendor: Advanced Micro Devices, Inc.

        Device OpenCL C version: OpenCL C 1.1

        Driver version: CAL 1.4.1646

        Profile: FULL_PROFILE

        Version: OpenCL 1.1 AMD-APP (831.4)

        Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt

        Device Type: CL_DEVICE_TYPE_GPU

        Device ID: 4098

        Board name: ATI Radeon HD 5800 Series

        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: 2

        Native vector width char: 16

        Native vector width short: 8

        Native vector width int: 4

        Native vector width long: 2

        Native vector width float: 4

        Native vector width double: 2

        Max clock frequency: 925Mhz

        Address bits: 32

        Max memory allocation: 536870912

        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: 2048

        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: Yes

        Round to +ve and infinity: Yes

        IEEE754-2008 fused multiply-add: Yes

        Cache type: None

        Cache line size: 0

        Cache size: 0

        Global memory size: 536870912

        Constant buffer size: 65536

        Max number of constant args: 8

        Local memory type: Scratchpad

        Local memory size: 32768

        Kernel Preferred work group size multiple: 64

        Error correction support: 0

        Unified memory for Host and Device: 0

        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: 000000000164C9C8

        Name: Cypress

        Vendor: Advanced Micro Devices, Inc.

        Device OpenCL C version: OpenCL C 1.1

        Driver version: CAL 1.4.1646

        Profile: FULL_PROFILE

        Version: OpenCL 1.1 AMD-APP (831.4)

        Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt

        Device Type: CL_DEVICE_TYPE_CPU

        Device ID: 4098

        Board name:

        Max compute units: 12

        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

        Native vector width char: 16

        Native vector width short: 8

        Native vector width int: 4

        Native vector width long: 2

        Native vector width float: 4

        Native vector width double: 0

        Max clock frequency: 2926Mhz

        Address bits: 64

        Max memory allocation: 2147483648

        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: 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: Yes

        Round to +ve and infinity: Yes

        IEEE754-2008 fused multiply-add: Yes

        Cache type: Read/Write

        Cache line size: 64

        Cache size: 32768

        Global memory size: 4285317120

        Constant buffer size: 65536

        Max number of constant args: 8

        Local memory type: Global

        Local memory size: 32768

        Kernel Preferred work group size multiple: 1

        Error correction support: 0

        Unified memory for Host and Device: 1

        Profiling timer resolution: 0

        Device endianess: Little

        Available: Yes

        Compiler available: Yes

        Execution capabilities:

        Execute OpenCL kernels: Yes

        Execute native function: Yes

        Queue properties:

        Out-of-Order: No

        Profiling : Yes

        Platform ID: 000000000164C9C8

        Name: Genuine Intel® CPU 000 @ 2.13GHz

        Vendor: GenuineIntel

        Device OpenCL C version: OpenCL C 1.1

        Driver version: 2.0

        Profile: FULL_PROFILE

        Version: OpenCL 1.1 AMD-APP (831.4)

        Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt

        Platform Name: NVIDIA CUDA

        Number of devices: 1

        Device Type: CL_DEVICE_TYPE_GPU

        Device ID: 4318

        Max compute units: 4

        Max work items dimensions: 3

        Max work items[0]: 512

        Max work items[1]: 512

        Max work items[2]: 64

        Max work group size: 512

        Preferred vector width char: 1

        Preferred vector width short: 1

        Preferred vector width int: 1

        Preferred vector width long: 1

        Preferred vector width float: 1

        Preferred vector width double: 0

        Native vector width char: 1

        Native vector width short: 1

        Native vector width int: 1

        Native vector width long: 1

        Native vector width float: 1

        Native vector width double: 0

        Max clock frequency: 1400Mhz

        Address bits: 32

        Max memory allocation: 268353536

        Image support: Yes

        Max number of images read arguments: 128

        Max number of images write arguments: 8

        Max image 2D width: 4096

        Max image 2D height: 16383

        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: 4352

        Alignment (bits) of base address: 2048

        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: Yes

        Round to +ve and infinity: Yes

        IEEE754-2008 fused multiply-add: Yes

        Cache type: None

        Cache line size: 0

        Cache size: 0

        Global memory size: 1073414144

        Constant buffer size: 65536

        Max number of constant args: 9

        Local memory type: Scratchpad

        Local memory size: 16384

        Kernel Preferred work group size multiple: 32

        Error correction support: 0

        Unified memory for Host and Device: 0

        Profiling timer resolution: 1000

        Device endianess: Little

        Available: Yes

        Compiler available: Yes

        Execution capabilities:

        Execute OpenCL kernels: Yes

        Execute native function: No

        Queue properties:

        Out-of-Order: Yes

        Profiling : Yes

        Platform ID: 00000000062BB030

        Name: GeForce 9500 GT

        Vendor: NVIDIA Corporation

        Device OpenCL C version: OpenCL C 1.0

        Driver version: 296.10

        Profile: FULL_PROFILE

        Version: OpenCL 1.0 CUDA

        Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics

        [/spoiler]

        cl_khr_byte_addressable_store supported by all devices.

        How to get “clinfo” for these card ?

        I think AMD 7800 series cards still have a issue with AMD 13.12 Catalyst + SDK 2.9. They are very low hashrate.

        1 Reply Last reply Reply Quote 0
        • T
          tmuir12 Regular Member last edited by

          alright, got it finally but no ping from the pool.ftc-c.com

          lets try it for pxc

          update:

          Working fine with morehash.pw NOMP pool. Pulling out the same hashrate 8.35khs out of GT 550M only now not getting the graphics driver unresponsive upon shutting down the miner.

          Yes, pretty sure it wont work for FTC yet as its for Neoscrypt and we haven’t swapped over yet, but does work for PXC

          1 Reply Last reply Reply Quote 0
          • ghostlander
            ghostlander Regular Member last edited by

            How to get [background=#ffffff] “clinfo” for these card ?[/background]

            Type “clinfo > somefile.txt” in your console.

            1 Reply Last reply Reply Quote 0
            • lizhi
              lizhi last edited by

              This is my AMD card clinfo. AMD HD6850 ,HD6870,HD6770 and AMD HD7850, HD7950 in attach files.

              1 Reply Last reply Reply Quote 0
              • ChekaZ
                ChekaZ last edited by

                Reuploaded: https://dl.dropboxusercontent.com/u/31024229/GpuMinerNeoScrypt.rar

                BTC: 1Ges1taJ69W7eEMbQLcmNGnUZenBkCnn45
                FTC: 6sxjM96KMZ7t4AmDTUKDZdq82Nj931VQvY

                1 Reply Last reply Reply Quote 0
                • D
                  daimyo last edited by

                  Folks, does that mean that in order for the gpu miner to work best, you first need to have it optimized for every particular video card?

                  1 Reply Last reply Reply Quote 0
                  • V
                    vehre last edited by

                    Of course not. I do have an Nvidia card only. I need access to an AMD one to do some tests and figure what the issue here is.

                    1 Reply Last reply Reply Quote 0
                    • D
                      daimyo last edited by

                      Of course not. I do have an Nvidia card only. I need access to an AMD one to do some tests and figure what the issue here is.

                      Great. I hope this time the nVidia graphics are gonna have the advantage :)

                      1 Reply Last reply Reply Quote 0
                      • Bushstar
                        Bushstar last edited by

                        People’s experience of NeoScrypt is going to be based on the GPU miner. We could not launch without a GPU miner as the trolls would have a field day and who ever did come up with a GPU miner might not have released it, however we could not launch with a buggy miner either as people’s experience would be too poor.

                        Then again it is said if you wait until the software is perfect then you have waited too long. Considering this I suggest we set the fork date, Ruth said she spotted a rough date given by someone and I intend to aim for that date after conferring with a few others. I expect to have forked to NeoScrypt by the end of October.

                        There is a Feathercoin testnet running NeoScrypt but this was to check that the fork works as expected, to test NeoScrypt it is best to mine on Phoenixcoin and earn some real coins while you are at it. As the Feathercoin testnet successfully forked to NeoScrypt on the testnet we have confirmed that the code is complete and we have seen Phoenixcoin successfully fork to it as well. We know it is safe to move the network to NeoScrypt and have auto checkpointing in place to prevent any abuse of low hash power during the change over. I would not like to fork from one algo to another without some sort of protection, especially considering how much we have been bullied over the last year and five months.

                        Feathercoin is committed to longevity and to explorer new solutions outside of the status quo that Bitcoin has to operate within, this is why we exist.

                        We really have been waiting on NeoScrypt for such a long time and I look forward to a fresh burst of energy once we can get on to the other side of this technical change. After we move we should cherry pick ideas and discuss them to pick the bad from the good.

                        Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

                        1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User last edited by

                          Feathercoin is committed to longevity and to explorer new solutions outside of the status quo that Bitcoin has to operate within, this is why we exist.

                          +13 ≤ N* ≤ N’…

                          1 Reply Last reply Reply Quote 0
                          • V
                            vehre last edited by

                            Sorry daimyo,

                            not any longer. I just aquired a Sapphire HD6870. Just have to wait for delivery. For figuring what is wrong in the CL-kernel that one should be sufficient.

                            For the nvidia vs. ATI battle: I do not favour any of the two. Both are evil, not participating on the Linux kernel. But to get OpenCL enabled Intel-HW my funds are too limited. A Xeon Phi would be marvelous, if anyone wants to donate :)

                            1 Reply Last reply Reply Quote 0
                            • D
                              daimyo last edited by

                              Sorry daimyo,

                              not any longer. I just aquired a Sapphire HD6870. Just have to wait for delivery. For figuring what is wrong in the CL-kernel that one should be sufficient.

                              For the nvidia vs. ATI battle: I do not favour any of the two. Both are evil, not participating on the Linux kernel. But to get OpenCL enabled Intel-HW my funds are too limited. A Xeon Phi would be marvelous, if anyone wants to donate :)

                              Andre, is that what you mean https://www.youtube.com/watch?v=iYWzMvlj2RQ :D

                              1 Reply Last reply Reply Quote 0
                              • MrWyrm
                                MrWyrm administrators last edited by

                                not participating on the Linux kernel.

                                I suspect Valve will help force their hand on this issue.

                                Like what I do: 6uuy6isbrW1SBF191Bzgui1gWxPdNKx2PB

                                1 Reply Last reply Reply Quote 0
                                • V
                                  vehre last edited by

                                  That’s the rather rude opinion of Linus. :)

                                  1 Reply Last reply Reply Quote 0
                                  • ?
                                    A Former User last edited by

                                    Does anyone want to edit the main post here?

                                    I have no idea what’s involved to get up and running on the testnet etc so I can’t really write it.

                                    We need all the links to precompiled and uncompiled versions, all github links and a noobie walkthrough for the precompiled ones.

                                    1 Reply Last reply Reply Quote 0
                                    • lizhi
                                      lizhi last edited by

                                      We had finish early test, Results in line with expectations.

                                      I builde a p2pool for neoscrypt , Today It can work normal. It support stratum. :)

                                      cgminer.exe --neoscrypt -I 13 -o stratum+tcp://pool.ftc-c.com:10554 -u Pm9nMjHhgH7stU4qcAZHXS1dHj6bVEGhrx -p x 
                                      

                                      I use the lasted version (3.7.4exp), my AMD 7850 card have about 20K/s hashrate.

                                      gpu_miner_1.jpg

                                      gpu_miner_2.jpg

                                      1 Reply Last reply Reply Quote 0
                                      • A
                                        Alpha Wolf last edited by

                                        Is this only working for pool mining right now? I can get Lizhi command line to work but for some reason can’t get solo mining working on my 560M.

                                        Not yet tested on my ATI cards. I’ve had no problem with solo config for the CPU miner. I’ve try many different ways with the command line but no

                                        luck in the past hour or so getting it working for solo. Here are a few things I’ve tried. Maybe someone can see something I’m doing wrong or not adding in. I have a live network -server going plus setup for local host as well, both have worked well with the CPU. This was just for a quick setup then I will tweak it as I go along. Thanks for any input in advance.

                                        Edit: I was going to setup a account here: http://pool.ftc-c.com/index.php and just mine there for a while,

                                        but doesn’t seem to be a English version of all the pages.

                                        Edit2: Worked my way threw the pages and have my 560M working at that pool now.

                                        Luck I have setup on this type of pool layout many times so it all came back to me what goes where. lol

                                        Its just for testing anyways.

                                        cgminer.exe --neoscrypt -o 192.168.1.107:3333 -u phoenixcoinpc -p x
                                        
                                        #--neoscrypt -o localhost:9554 -u phoenixcoinpc -p x
                                        
                                        #--neoscrypt -o 192.168.1.107:3333 -u Pn18tqfzFNPUcFjJRq1GRYdYDJjKTBNGpq -p x
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • Wellenreiter
                                          Wellenreiter Moderators last edited by

                                          If you need an english pool, there are two that work with gpuminer:

                                          p2pool.neoscrypt.de:10554 located im Germany

                                          pool20.neoscrypt.de:10554 located in the Netherlands

                                          Could you extract the gpuminer related log entries in the phoenixcoind log for the solo mining?

                                          the location of the logfile is ~/.phoenixcoin/debug.log for Linux

                                          and (I believe)

                                          %datadir%\phoenixcoin\debug.log for windows.

                                          Feathercoin development donation address: 6p8u3wtct7uxRGmvWr2xvPxqRzbpbcd82A
                                          Openpgp key: 0x385C34E77F0D74D7 (at keyserver.ubuntu.com)/fingerprint: C7B4 E9EA 17E1 3D12 07AB 1FDB 385C 34E7 7F0D 74D7

                                          1 Reply Last reply Reply Quote 0
                                          • A
                                            Alpha Wolf last edited by

                                            At the moment I’m working in W7 64bit OS, data dir is: D:\Phoenixcoin\data http://s000.tinyupload.com/index.php?file_id=11113781956684070159

                                            Sorry for the delay had to find a file host. Edit: fixed link with better DL source.

                                            GPU Nvidia 560M seemed to work but never got any status at the pool on its work so I closed it and quit working there.

                                            GPU_miner1.jpg

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post