Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gupax not loading #89

Open
STUKguy opened this issue Mar 31, 2024 · 6 comments
Open

Gupax not loading #89

STUKguy opened this issue Mar 31, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@STUKguy
Copy link

STUKguy commented Mar 31, 2024

OS & Version:

Windows 10

Bug

Installed a freasher W10 install, the ran Gupax (Added expection in antivirus) worked fine. Powered off machine disconnected monitor and then started machine up and logged in via RDP Gupax will not start. Powered of machine tried monitor on machine directly Gupax wont start again, did another fresh install of W10 same thing all over again.

@STUKguy STUKguy added the bug Something isn't working label Mar 31, 2024
@Cyrix126
Copy link

Cyrix126 commented Apr 4, 2024

Hello can you try my fork ? specially for windows it is using a different backend for rendering (glow instead of wgpu) and it's using more up to date deps. I want to know if it is working for you.

@STUKguy
Copy link
Author

STUKguy commented Apr 4, 2024

Hello can you try my fork ? specially for windows it is using a different backend for rendering (glow instead of wgpu) and it's using more up to date deps. I want to know if it is working for you.

Hey, Thank you for your reply. I managed to get the orignal Gupax running after the 4th install of Windows. i need to how ever redo this because i mistaken installed on a 2TB which i need for something. When i get around to this i will try your version and see how i get on.

@STUKguy
Copy link
Author

STUKguy commented Apr 4, 2024

Hello can you try my fork ? specially for windows it is using a different backend for rendering (glow instead of wgpu) and it's using more up to date deps. I want to know if it is working for you.

Hey, Just had the issue happen again. I found if i remote into the computer and try and run either Orignal Gupax or your fork it wont run but if connect up a monitor and physically start either on the machine not via remote desktop it works fine and then afterwards i can remote in as normal.

This however this going to cause me problems as i was hoping to run the machine headless and just remote into now and again to make sure it is running, the reason i choose Windows was it was the easiest option. What i will try over the weekend is see if i can Ubuntu or Debian to work via Windows RDP and see if i have the same issue. Unless you have heard of the Windows issue before?

@Cyrix126
Copy link

Cyrix126 commented Apr 5, 2024

What you would need is an option added to gupax/x like --headless to be launched without UI.
But you can still just watch with witch arguments gupax launch xmrig and p2pool, and launch them with exactly the same arguments. With htop on linux you would quickly see which args are used.

@STUKguy
Copy link
Author

STUKguy commented Apr 11, 2024

What you would need is an option added to gupax/x like --headless to be launched without UI. But you can still just watch with witch arguments gupax launch xmrig and p2pool, and launch them with exactly the same arguments. With htop on linux you would quickly see which args are used.

Hey, Thank you for you advice. I ended up soing with Linux version. Random thought is there away for me to get notified if it stops mining? I am currently using your version on 1 machine and the orginal on another machine. Going to test the both for a month and see which one give me better results but i dont want have to remote in everyday to check if its mining.

@Cyrix126
Copy link

Going to test the both for a month and see which one give me better results

In term of hashrate there will be virtually no difference.
They are both using xmrig behind the hood.
See DIFFERENCES
Gupax/x takes about <1% of cpu, desktop should take <1% too if passive (depending of hardware and which type of desktop of course) and xmrig gives 1% donation to dev unless you compile it yourself after setting donation to 0.
So you could maybe gain 1 to 3% HR if you use CLI only (without Gupaxx) and disable xmrig donation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants