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-

  • 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

              • tuskerM
                1·
                1 year ago

                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

                • Dark_Armadill0OP
                  1·
                  1 year ago

                  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 _

                  • tuskerM
                    1·
                    1 year ago

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