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

[email protected]

1GB Pages ENABLED in Gupax!!!! But now... the Status Page is fubar. (monero.town)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

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-

top 23 comments

sorted by: hot top controversial new old

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

I just wanted to comment on how great this entire thread is, you're all awesome!

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

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

OKAY! I decided to completely wipe the Gupax from my system. Restarted. Downloaded 1.3.1 again. With a fresh clean slate, I edited the config.json with my settings, and voila:

Now onto the next issue that reared its ugly head: the Status tab in Gupax isn't working right. Here's what I mean:

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

You have to make sure the xmrig http api is running and gupax knows about it. You will have to edit the conf.json to get this working.

You may need to ask the gupax dev on github as to how exactly it needs to be configured. Or better yet open an issue on there as to why 1GB pages don't work unless you use the config. Maybe it would be a feature add in the UI.

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

miner speed 10s/60s/15m 12534.0 12390.0 12427.7 H/s max 13773.9 H/s

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (3 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 (1 children)

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 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

And if I delete the Command Arguments:

XMRig starts, no error.

[–] [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

Okay, made your edits. Restarted Gupax. Waited for P2Pool to sync (go green). Then I kicked on XMRig with command argument: –config config.json Here's the error I get:

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

HEY TUSKER! So good of you to chime in! Love your help.

So, curious, are you also running Huge Pages, and if so, did you leave the config.json set to a value of "true", or did you specify an actual value?

Here's the relevant portion of my config.json for Huge Pages:

"cpu": { "enabled": true, "huge-pages": 32768,

I'll make your changes then restart Gupax. Thanks so much!

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

yeah, set it to true

"huge-pages": true,

I can't help with your other issues though, because never used gupax. Just be patient, I'm sure someone in here can help you.

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

Thanks for chiming in! And I'm all about patience ^_^ "Hurry up and wait" is my motto. Love this community!