Hello my fellow deviants. It is I, Dark_Armadill0. I made the switch to Gupax, and although I love it (and am finally seeing payouts), I’m a little underwhelmed with a few things. Ahem:

Formerly I ran XMRig standalone and experienced the following:

  • With plain XMRig I was netting 18,000 H/s.
  • With plain XMRig, I had 1GB Pages Enabled.
  • With plain XMRig, I had Huge Pages 100% enabled.

Now under Gupax, I have the following:

  • Hashrate has dropped to 13000 H/s (can run [h] command on XMRig tab to get this value)
  • 1GB Pages are NOW ENABLED.
  • Huge Pages are at 100% enabled.
  • STATUS Page of Gupax is not correctly showing/pullling information.

Thank you in advance, and stay devious _ Dark_Armadill0-

You are viewing a single thread.
View all comments View context
1 point

your command line arguments are most likely malformed

just put everything you need into the config and do not use any other command line options besides --config config.json

permalink
report
parent
reply
1 point

Even more confusing is my Linux OS truly thinks 1GB Pages are running. If I run in a Terminal sudo cat /proc/cpuinfo | egrep -o pdpe1gb | head -n 1 result is: pdpe1gb

But the only Command Argument declared is --config config.json

permalink
report
parent
reply
1 point
*

this does not mean they are running, just mans the cpu supports it

once you have everything you need in the config and properly formatted it should work, assuming you have enough ram

permalink
report
parent
reply
1 point

Would it be too much to ask for you to share your config.json (without your wallet address, ofc) ? Feels like I need to wipe everything from my config.json and start with known working code.

I just made a backup of the config.json to config.json.old so I can safely delete the “corrupted” config.json . I’d truly appreciate it, if you shared yours _

permalink
report
parent
reply

Community stats

  • 27

    Monthly active users

  • 68

    Posts

  • 199

    Comments