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

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:

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!

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

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

And if I delete the Command Arguments:

XMRig starts, no error.

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

Ah. Just ran it, XMRig throws an error.

--config config.json

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:

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!

So I pasted it (with and without your quotes) and the XMRig failed to initialize for both attempts. This was in the “Command Arguments” input field of the XMRig tab under Gupax. It looks like it allows adding arguments, but this suggestion didn’t work for me sighs Thanks for your suggestion, keep 'em coming ^_

Thanks so much MoneroBull! So good to see you! I have enormous respect and admiration for ya, you’re a great person, and such a jewel in the community! I’m trying to find an EPUB or something to learn the in’s and out’s of mining Monero. I’m also walking through SerHack’s “Mastering Monero”… do you know if mining broken down in it? I’m only on Chapter 1 at present.

Oh my Gucci- I just got a payout with the Monero GUI local node + miner, using P2Pool Mini! This is the first fruit of my labor! Seizure for Jesus, I finally did it!

Thanks!

I’ll have to reattempt gupax. I fumbled my way around it, couldn’t get it to work right. I’ll have to dedicate an evening, relax and take a systemic approach to get it squared away. I’m sure I messed something up that’s trivial, but I got disheartened and just went back to XMRig. Gotta try harder next time. Good suggestion, from what I read, Gupax is stupid easy to get going. I don’t know where I went wrong.

^This was my sentiment regarding Gupax . I’m sure if I just slowly go at it I can overcome my lackluster mining experience and make it work.

I’m happy to support the network, I know I’m playing the long-game when it comes to ROI. I splurged on this machine to retire a 2011 build, and although I mainly use it for general computing, I’m mining 24/7 and this bad boy just won’t slow down. I’m ecstatic.