background

bfgminer starts and dies and starts again in an endless cycle of samsara

Hello, I was hoping I could get some guidance on how to get bfgminer working on my machine. Here are my specs:
OS X 10.10.5
AMD FirePro D500 3072 MB GPU
3 GHz 8-Core Intel Xeon E5 CPU

I think I have CPU Miner working, I'm getting hash rates for each thread in the output terminal. Though it always displays "0 KH" and "Stating..." in the GUI

Comments

  • What's the output of bfgminer when you try to mine? Are you using GPU or ASIC?
  • I'm using GPU. The output I get at first is "bfgminer has started. The primary pool is set to stratum+tcp://stratum.slushpool.com:3333 and the user is set to" my worker id. The output says: "[2017-05-08 13:26:26] Started bfgminer 5.4.2-unknown
    [2017-05-08 13:26:26] Loaded configuration file ../../Library/Application Support/MacMiner/bfgurls.conf
    [2017-05-08 13:26:26] CL Platform 0 vendor: Apple
    [2017-05-08 13:26:26] CL Platform 0 name: Apple
    [2017-05-08 13:26:26] CL Platform 0 version: OpenCL 1.2 (Jan 17 2017 10:00:23)
    [2017-05-08 13:26:26] Platform 0 devices: 2
    [2017-05-08 13:26:26] 0 AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:26] 1 AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:26] Unable to load ati adl library
    [2017-05-08 13:26:26] Probing for an alive pool
    [2017-05-08 13:26:26] Testing pool stratum+tcp://stratum.slushpool.com:3333
    [2017-05-08 13:26:26] Stratum authorisation success for pool 0
    [2017-05-08 13:26:26] Pool 0 stratum+tcp://stratum.slushpool.com:3333 alive
    [2017-05-08 13:26:26] Pool 0 is hiding block contents from us
    [2017-05-08 13:26:26] Network difficulty changed to 522G ( 3.74E)
    [2017-05-08 13:26:26] New block: ...bf13e0d29239642d diff 522G ( 3.74E)
    [2017-05-08 13:26:26] Stratum from pool 0 detected new block
    [2017-05-08 13:26:27] Init GPU thread 0 GPU 0 virtual GPU 0
    [2017-05-08 13:26:27] CL Platform vendor: Apple
    [2017-05-08 13:26:27] CL Platform name: Apple
    [2017-05-08 13:26:27] CL Platform version: OpenCL 1.2 (Jan 17 2017 10:00:23)
    [2017-05-08 13:26:27] List of devices:
    [2017-05-08 13:26:27] 0 AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] 1 AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] Selected 0: AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] initCl() finished. Found AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] Init GPU thread 1 GPU 1 virtual GPU 1
    [2017-05-08 13:26:27] CL Platform vendor: Apple
    [2017-05-08 13:26:27] CL Platform name: Apple
    [2017-05-08 13:26:27] CL Platform version: OpenCL 1.2 (Jan 17 2017 10:00:23)
    [2017-05-08 13:26:27] List of devices:
    [2017-05-08 13:26:27] 0 AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] 1 AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] Selected 1: AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] initCl() finished. Found AMD Radeon HD - FirePro D500 Compute Engine
    [2017-05-08 13:26:27] API running in IP access mode on port 4052
    [2017-05-08 13:26:27] Selecting poclbm kernel
    [2017-05-08 13:26:27] Selecting poclbm kernel"

    Then I get "Settings changed. Your miner was restarted automatically after a sudden stop at 13:27:33."

    Does this help?
  • Hmm, doesn't look as though it's really getting started. Try setting the Intensity very low to see whether that'll let it get started and look around to see what worksize/intensity settings other people are using with the FirePro D500.
  • I ran with a lower intensity and enabled debugging output and here are some errors I got back after tossing out what looked okay:

    [2017-05-10 15:03:10] Unable to load ati adl library

    [2017-05-10 15:03:10] Unable to load ati adl library
    [2017-05-10 15:03:10] Probing for an alive pool

    [2017-05-10 15:03:10] Probing for an alive pool
    [2017-05-10 15:03:10] Testing pool stratum+tcp://stratum.slushpool.com:3333

    [2017-05-10 15:03:10] Testing pool stratum+tcp://stratum.slushpool.com:3333
    [2017-05-10 15:03:10] HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl

    [2017-05-10 15:03:10] HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
    [2017-05-10 15:03:10] Failed to connect in json_rpc_call

    [2017-05-10 15:03:10] Failed to connect in json_rpc_call
    [2017-05-10 15:03:10] initiate_stratum with sockbuf=0x0

    [2017-05-10 15:03:10] initiate_stratum with sockbuf=0x0
    [2017-05-10 15:03:10] Stratum connect failed with TLS to pool 0: Protocol "https" not supported or disabled in libcurl

    [2017-05-10 15:03:10] Stratum connect failed with TLS to pool 0: Protocol "https" not supported or disabled in libcurl

    [2017-05-10 15:03:10] Stratum authorisation success for pool 0
    [2017-05-10 15:03:10] Pool 0 stratum+tcp://stratum.slushpool.com:3333 alive

    [2017-05-10 15:03:10] Pool 0 stratum+tcp://stratum.slushpool.com:3333 alive
    [2017-05-10 15:03:10] Received no-transaction-list response for pool 0 job 1d4d6b

    [2017-05-10 15:03:10] Received no-transaction-list response for pool 0 job 1d4d6b
    [2017-05-10 15:03:10] Pool 0 is hiding block contents from us

    [2017-05-10 15:03:10] Pool 0 is hiding block contents from us

    [2017-05-10 15:03:11] OCL 0: Using kernel poclbm with interface poclbm
    [2017-05-10 15:03:11] OCL 1: Using kernel poclbm with interface poclbm

    [2017-05-10 15:03:11] OCL 1: Using kernel poclbm with interface poclbm
    [2017-05-10 15:03:11] Error -54: Running goffset test kernel (clEnqueueNDRangeKernel)

    [2017-05-10 15:03:11] Error -54: Running goffset test kernel (clEnqueueNDRangeKernel)
    [2017-05-10 15:03:11] Error -54: Running goffset test kernel (clEnqueueNDRangeKernel)

    [2017-05-10 15:03:11] Error -54: Running goffset test kernel (clEnqueueNDRangeKernel)
  • Error -54 is often associated with too high an intensity, you could try minus values… The trashcan Mac Pro probably isn't a great machine to mine with, having a 'thermally constrained' design.
  • Hi,

    How would I be able to tell if it is actually using the usb miner I have plugged in or just the one in my computer?

    Also I see Mh is moving but in the accepted field it stays 0 can someone explain any of this.

    very new to this.

    Thanks
  • Check the log in the miner window and the API Output window for more detailed output. Sometimes 0 accepts means you're not mining fast enough to solves shares which sound like the case if you're mining Bitcoin in Mh rather than Gh/Th

Leave a Comment