Topic: XMRIG for MacOS working for CPU and AMD GPUs (Read 458 times)

Thanks for the tip.  I'll look into the difficulty!  Yeah, i know about the throttling, but the fans aren't even kicking onto high gear!  When it gets too hot the damn thing sounds like a jet about to take off!  I have yet to hear that when mining KawPow algo.  GPU is sitting at a stable 65C, which as far as GPUs go, isn't too bad.  My desktop, which I leave mining 24x7 on an rx580 hovers in the low to mid 70's.  I will never understand how MacOS works!  Personally, i'd rather  not even have the damn thing...but i needed it for iOS dev work...so there ya go!

First, mining with a laptop is a bad idea. It can't handle the heat of continuous full load.

That leads to the second point, throttling. It's throttling because it's too hot. There isn't much
you can do about it because it's a small enclosed space.

The hashrate reported by the pool is based on submitted shares. You aren't submitting shares
regularly enough to calculate a stable hash rate. Set a lower difficulty if you can, check pool
instructions for how.

Created an account to say thanks!!!!

Got this up and running on a 2019 macbook pro with Radeon Pro 5300M 4GB.

KawPow seems to fluctuate wildly between a reported hashrate of 0MH/S and 16MH/S on Unmineable, though the cmd output shows a constant 3.5mh/s

Have never noticed my fan kick on overdrive, so i'm not sure if it could get higher, and the system is doing something to pre-emptively throttle it.  Any thoughts?

I had previously had it mining on Prohashing using their ethereum-lite ethash, and was getting right around 14mh/s on that, and i'd hear the fans spin up quite frequently.


in Pools, i set "algo": "kawpow"

and in kawpow, i set "index" : 1, because otherwise it tried to use the integrated gpu as well.

Thanks again!

There are 2 config files in the github https://github.com/ganzocrypt/xmrig-macos/releases/tag/v6.13.0-dev-macos

I used KawPow on unminable and I played a bit with Intensity:

"kawpow": [
            {
                "index": 0,
                "intensity": 36864,
                "worksize": 256,
                "threads": [-1]
            }
        ],

So you can check that in the OpenCL section of the config. Start with a low number and increase it. The above was for a 580 8gb

Good luck with that, there aren't many MAC miners to share their experience.

Tuning is important but it's not likely to solve your fluctuation problem. Tuning helps in the best
case but doesn't help the worst case. You need to troubleshoot to find out what's really going on.

Nothing is on the monitor.  I cant disconnect but im not using this mac pro for anything just letting it mine.  I susepct its thermal cycling due to being all in one 27” i mac pro.

What i can use is help with optimizing the parameters for it in the config file.

GPU hashrate could vary depending on display activity. It does on Windows with certain algos.
I've seen up to 40% faster when the monitor goes to sleep.

The cpu miningis fine its the gpu mining thats all over the place.
I can get around 10khs out of cpu on monero.  But want to use the gpu in the unit.  its a nice beast.

@miner29

Thanks a lot will update the release note!

My guess is a CPU affinity problem, which is OS specific and likely not implemented for MACOS.
Without it the OS will schedule the mining threads wherever it wants instead of assigning each
thread to a specific CPU core. If MACOS has process monitoring tools you can probably prove it.

ganzocrypt,

Yes sure its a 2017 mac pro 3.0ghz Xeon 10core 64gb ram unit
GPU is the Radeon Pro 64 16gb unit.
ive stuck it on rvn and going from 5-17mhs (i think itmay be thermal throttling)

Ive had no real luck tuning the setting for the gpu.  Everything ive tried lowers or doesnt seem to affect its speed.

OSx 10.15.7

@miner29 did you had a chance to test it?

can you share coin / card / cpu / macOS version so I can add to the list

any issues?

thx

I recompiled xmrig with latest libs.
No feature changes so just get the one on the github.

Please report any issues, or success with algo and card so that I can update the list.

Download binary from here: https://github.com/ganzocrypt/xmrig-macos/releases

@miner29

Oh cool, great to know that is working, let me know if there are any issue.
So you are mining on rx/0 on GPU, which coin?
Also will update the list of Cards and Algo that is supporting as people using the miner can give some feedback ( it's like trial and error).

Will probably update it soon since I recompiled bunch of libraries that needed to be update it in brew.

Ok RVN needs more memory, great to know!

You can play with intensity and worksize to increase hashrate, just keep in mind that at certain point you might have issues with the miner.
At that point just lower the values.

I tested on RX580 8Gb, getting around 7Mhs and I have the following:
"kawpow": [
            {
                "index": 0,
                "intensity": 36864,
                "worksize": 256,
                "threads": [-1]
            }
        ],

Finally got time to get it installed.  Working now on gpu on randomx.  Didnt change any parameters yet except pool/wallet/algo.
Getting 5mhs on it...but will look at how parameters are set up.  Its on a Radeon Pro Vega 64.  

FYI 2gb is too small for RVN.  Currently 3gb works but not for much longer due to dag growth.

Maybe can get CCX (cn/gpu) working as it does work on 2gb cards.

@BenhurMarcel

You should mine those 2 coins with the CPU.
Only KawPow is supported for GPU mining at this stage

You should have only one thread per card. I posted 2 config files samples.
Can you post the OpenCL section of your config file?

There are still issues in supporting some algos for AMD cards as you might know OpenCL is not supported anymore by Apple.

NOTE: Updated the tested Algo, if you test a different algo and it IS/NOT working please let me know. https://github.com/ganzocrypt/xmrig-macos/releases/tag/v6.13.0-dev-macos

A suggestions, you can mine with your CPU Keva or Monero and with your 2 GPUs (if GPU memory is enough, since 2Gb is low) you can mine RVN coin.
If you want to try this, you need to have 2 instances of xmrig with 2 different configs.
So you launch on 2 different terminal:
./xmrig -c configCPU.json
./xmrig -c configGPU.json

Hello,

I tested this new XMRig version with my Mac Pro (2013) with 2 AMD Radeon FirePro D300 (2x2Gb) cards, but it seems that it is not running with the OpenGL library.
I tested with the KEVA coin and MONERO coin, same error.
You can find below the error displayed by XMrig using the OpenGL option :
* OPENCL       #0 Apple/OpenCL 1.2 (May  8 2021 03:14:28)
 * OPENCL GPU   #0 n/a AMD Radeon HD - FirePro D300 Compute Engine 850 MHz cu:20 mem:512/2048 MB
 * OPENCL GPU   #1 n/a AMD Radeon HD - FirePro D300 Compute Engine 850 MHz cu:20 mem:512/2048 MB
 * CUDA         disabled
[2021-05-28 08:46:05.982]  net      use pool kevacoin.herominers.com:10140  78.47.127.170
[2021-05-28 08:46:05.982]  net      new job from kevacoin.herominers.com:10140 diff 50000 algo rx/keva height 331722
[2021-05-28 08:46:05.982]  cpu      use argon2 implementation SSSE3
[2021-05-28 08:46:05.982]  randomx  init dataset algo rx/keva (8 threads) seed d0fe845b8de9c7bd...
[2021-05-28 08:46:07.394]  randomx  allocated 2336 MB (2080+256) huge pages 0% 0/1168 +JIT (1412 ms)
[2021-05-28 08:46:13.803]  randomx  dataset ready (6410 ms)
[2021-05-28 08:46:13.803]  cpu      use profile  rx/wow  (2 threads) scratchpad 1024 KB
[2021-05-28 08:46:13.810]  cpu      READY threads 2/2 (2) huge pages 100% 2/2 memory 2048 KB (6 ms)
[2021-05-28 08:46:13.810]  opencl   use profile  rx  (4 threads) scratchpad 1024 KB
|  # | GPU |  BUS ID | INTENSITY | WSIZE | MEMORY | NAME
|  0 |   0 |     n/a |       320 |     8 |    320 | AMD Radeon HD - FirePro D300 Compute Engine
|  1 |   0 |     n/a |       320 |     8 |    320 | AMD Radeon HD - FirePro D300 Compute Engine
|  2 |   1 |     n/a |       320 |     8 |    320 | AMD Radeon HD - FirePro D300 Compute Engine
|  3 |   1 |     n/a |       320 |     8 |    320 | AMD Radeon HD - FirePro D300 Compute Engine
[2021-05-28 08:46:13.810]  opencl   error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer with buffer size 2181038080
[2021-05-28 08:46:13.810]  opencl   error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer with buffer size 2181038080
[2021-05-28 08:46:13.810]  opencl   error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer with buffer size 2181038080
[2021-05-28 08:46:13.810]  opencl   error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer with buffer size 2181038080
[2021-05-28 08:46:13.811]  opencl   thread #2 failed with error RandomX dataset is not available
[2021-05-28 08:46:13.811]  opencl   thread #0 failed with error RandomX dataset is not available
[2021-05-28 08:46:13.812]  opencl   thread #3 failed with error RandomX dataset is not available
[2021-05-28 08:46:13.812]  opencl   thread #1 failed with error RandomX dataset is not available
[2021-05-28 08:46:13.812]  opencl   thread #2 self-test failed
[2021-05-28 08:46:13.812]  opencl   thread #3 self-test failed
[2021-05-28 08:46:13.812]  opencl   thread #0 self-test failed
[2021-05-28 08:46:13.813]  opencl   thread #1 self-test failed
[2021-05-28 08:46:13.813]  opencl   disabled (failed to start threads)

Thank you in advance for your feedback.
Regards

Let me know if there are any issues and if you need help with the config file.

I will attempt a test on imac pro with Pro Vega 64 from Apple.  Will advise.
Ive been able to make it work before on xmr but got about 25% errors on share submitted.

Yeah I know.

The issue is that macos OpenCL is basically not supported and OLD, like version 1.2.
So some dev made the miner but it does not work on all combination since libraries mismatch.

I helped to test and recompile the xmr code.
It was a real pain !
I had to use homebrew, recompiled bunch of libraries.
Modify some make scripts and finally worked.
I tested on KawPow, so you can use unminable or other auto-switching pools service to mine bunch of other algos too.

I know there are a lot of people with hackintosh and AMD cards who can use this miner if they want to.
Looking to see if there are any issues (which probably there are) with other AMD cards, I tested on RX 580 and someone tested on Radeon Pro 5300