this post was submitted on 01 Aug 2023
7 points (88.9% liked)

Monero Mining

226 readers
1 users here now

founded 1 year ago
MODERATORS
 

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 comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (17 children)

specify "--config config.json" in the command arguments field and add your other parameters as well there

also change "colors": true to false, in the config

not sure if it is a bug in gupax, but if you use the command line arguments then 1GB pages works for me

[–] [email protected] 1 points 1 year ago (12 children)
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (11 children)

it is --config not -config

just set all needed options in the config then gupax should run xmrig the way you want it and mine to the correct IP and 1GB pages should work as well

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Ah. Just ran it, XMRig throws an error.

--config config.json

[–] [email protected] 1 points 1 year ago (2 children)

what error, that is correct syntax

[–] [email protected] 1 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] [email protected] 1 points 1 year ago (1 children)

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 ^_^

[–] [email protected] 1 points 1 year ago (1 children)

Use default one that comes with the bundle as a starting point.

[–] [email protected] 1 points 1 year ago (1 children)

Ok. Suppose I delete the original config.json file. Then I close out Gupax. Would it recreate a fresh config.json at that point? Then I can make my edits (1gb-pages true, etc) ? Sorry for all the n00b questions, and you've been my hero thus far!

[–] [email protected] 1 points 1 year ago

Don't think so, just download it again.

[–] [email protected] 1 points 1 year ago

And if I delete the Command Arguments:

XMRig starts, no error.

load more comments (9 replies)
load more comments (9 replies)
load more comments (13 replies)