• Content Count

  • Joined

  • Last visited

Community Reputation

36 Good

About lnxd

  • Rank

Recent Profile Visitors

590 profile views
  1. Hey @joshallen2k, to get around the Mining Unknown error you could force it to use an algorithm. But sadly your card only has 4gb of VRAM which isn't enough to mine Eth efficiently as it's below the current DAG size. It won't be as profitable, but if you want to mine with this card you'll have to mine something else.
  2. Awesome to see! So the logs show your card is being detected now which means driver installation worked, and the output of that command confirms that there is another instance running which is why it is not generating a DAG file (as there's already one) and it's failing probably because there's not enough resources available. Maybe restarting your server again will fix it, but clear your image cache first: docker image prune -a Reboot your server, then change back to lnxd/phoenixminer:latest
  3. Damn, how about with 20.45 also on the testing-21.10 tag? This is the oldest driver version that should support your card. Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers! If that fails again please share the full logs, the difference I'm looking for is whether it recognises the model of your GPU. Your logs last time just showed the PCI-E device ID. EDIT: Also before running the container please ensure another instance
  4. Damn, I've updated the driver installer and it's on a testing tag. If you could please jump across to that and let me know how you go: lnxd/phoenixminer:testing-21.10
  5. Perfect. Also stick to 21.10 for now, I think (according to the PhoenixMiner changelog) it should be the best for your GPU. Too old and you will get Segmentation Errors, if you try to get fancy and use a driver version not specifically listed by the PM devs as having support your your GPU it usually either fails or is just super unreliable.
  6. This is likely one of two things: 1. Your GPU is stuck unable to reset (unlikely), 2. The drivers aren't installed properly (likely). If restarting isn't much of an issue to you, please restart and try again. If you're reluctant to restart or that doesn't fix it, bare with me, I'm going to push out a quick build that hopefully lets the drivers install properly.
  7. No worries! Sorry I'm a little slow at support, bit of a poor work/life balance at the moment leaving me with insufficient free time to help out. Can you please share the output from running the user script for me? Also if you don't mind sharing your diagnostics.zip after the container has been running for about 5 minutes that'd be appreciated. @MorphiousGX are you still having this issue? I tried testing this out but wasn't able to replicate it. @guillelopez I just updated the container, the installation should be significantly faster than before. If you o
  8. Can you please run the container for 5 minutes and share the logs it generates in a .txt file? Thanks! Hey @C0bra_2056 I'm getting closer to a possible solution for this issue. It appears the in-tree amdgpu drivers (the ones that Unraid use) don't support most of the OC functions PhoenixMiner supplies, it doesn't give an error because the drivers in my container do so it thinks it's working. This doesn't happen with Nvidia cards because of @ich777's Nvidia Driver Plugin and driver install script that this container relies on. For now to reduce your power draw you'll want to
  9. Looks like the install was mostly successful but it still gave some errors, I'll need to work on it. 20.45 should have installed successfully though. Did the other command suggest the container can see your cards?
  10. That's okay, you shouldn't need to change either haha. Does this mean it's working? You can also hardcode a value here, eg. http://[IP]:[PORT:5449]. Honestly you could even set the WebUI for PhoenixMiner to your stats page on Ethermine, eg. https://ethermine.org/miners/436ac5D704e99Cfa0Ee8048dD2FA4cD394dF6f76/dashboard
  11. Damn What's your output from: docker exec -ti PhoenixMiner apt install lshw > /dev/null; docker exec -ti PhoenixMiner lshw -C display Make sure you change PhoenixMiner to your container name if you set it to something different. Also please attach the install logs as a .txt file for 21.10, maybe it's failing to install.
  12. Might be a bug in the xml file, but you can edit the webUI port by turning on Advanced in the top right
  13. I don't but try the 21.10 drivers if that is the only card you want to mine with: Added support for AMD Linux drivers 21.10-1244864-ubuntu-18.04, 21.10-1247438-ubuntu-20.04, and 20.50.x. Use this drivers only if you have Polaris or older GPUs, or the latest RX6x000 GPUs. WARNING: Vega, Radeon VII, and Navi GPUs won't work with these drivers! In case anyone is interested I now have an Asus 5500 XT, an Asus RX580 and two GTX1060 cards from different vendors. I'm glad to hear @JhonScript! Heads up you are still on the old version. If you go to the WebUI > Docker page
  14. Good catch @ich777, @JhonScript -gt 15 is what the card is tuned to and it might not be suitable. This also doesn't usually appear in the logs unless you are in an interactive session. Strange that this would appear so early as well without having it set manually. Auto tuning usually takes some time to complete, a solid ~10 minutes for most of my cards depending on the OC options I have set. But your logs indicate it was appearing within 5 minutes of starting. Please make sure you have updated the container to the latest version, then add the argument -resetoc to Additional Arguments like
  15. @guillelopez Sorry not yet! I plan to integrate it with the API for a couple of mining pools so that stats are all visible from one place. Being that it's a larger project I intend to make this possible at the same time. @JhonScript looks like @ich777 kindly gave the answers you were looking for 😅 he's also kindly supplied a fix for the error you described "Unable to load NVML", so that should be available for everyone soon. The one thing to note in case anyone else arrives here with the same question, is that while you don't need to use two separate containers, i