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-

  • monerobull
    3·
    1 year ago

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

  • Dark_Armadill0OP
    1·
    1 year ago

    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:

    • tuskerM
      1·
      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.

  • tuskerM
    1·
    1 year ago

    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

    • Dark_Armadill0OP
      1·
      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:

      • tuskerM
        1·
        1 year ago

        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

              • tuskerM
                1·
                1 year ago

                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

                • Dark_Armadill0OP
                  1·
                  1 year ago

                  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

    • Dark_Armadill0OP
      1·
      1 year ago

      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!

      • SNeedlewoods
        1·
        1 year ago

        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.

        • Dark_Armadill0OP
          2·
          1 year ago

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