lnxd

Members
  • Posts

    154
  • Joined

  • Last visited

Everything posted by lnxd

  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 isn't using your GPU. All PhoenixMiner containers should be stopped, then run: ps -u $USER | grep -i phoenixminer And make sure there is no output. If there is, PhoenixMiner must be running in the background somewhere.
  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 or anyone else have any issues after the update please let me know 😅
  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 use the -powlim argument to set a negative power limit (ie. start with -powlim -50) until you hit a comfortable power draw with a reasonable hash rate. Hopefully once the underlying issue is resolved you'll be able to increase your hash rate using the OC arguments with nvidia cards while maintaining a lower power draw. Heads up though, if you have never used these arguments previously, they might not result as well as you are hoping due to the memory timings set in the default BIOS so you might need to play around a bit to get everything perfect. I have an RX580 and had fun with this previously. Can you please also run the container for 5 minutes with the 21.10 drivers selected and share your logs in a .txt file?
  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, press Check For Updates, after a few moments you will see Update Now, that's why it shows no mention of Nvidia and you still get the NVML message. You can also set the driver version in the template to 0 to remove the AMD drivers entirely. Alternatively to check for updates you can also force an update by turning on Advanced Mode in the top right corner of the Docker page and pressing Force Update next to the container. For anyone else who has this problem, switching over to SSL usually works too, eg. SSL://asia1.ethermine.org:5555. Some ISPs seem to block mining traffic, and sometimes the ports are just coincidentally blocked.
  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 so: Hopefully this might trigger your card to re-tune and allow it to start mining. You're the second person to report this issue to me with this version of PhoenixMiner so there might be something up with this version of the binary released by the developers. You can try with an older version of PhoenixMiner and see if it generates a hash rate by using a tag such as lnxd/phoenixminer:latest-18.20 but please note that this tag does not contain the latest updates and OC options will not work with Nvidia cards.
  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, if you want to get it working with separate containers with Nvidia cards you'll need to use both GPU UUIDs or card IDs as @ich777 mentioned above in each container + the -gpus argument in each container to allocate just the GPU you want to use. Otherwise you will likely run into issues where not all cards are visible every time the container is started, and if you start another one it might not have enough available memory. To rephrase in case this isn't clear, all PhoenixMiner containers need all GPU UUIDs of the cards you plan to use with any container, and to also be told which GPU to mine on using the -gpus argument. Maybe the upcoming NVML fix might stop this problem though.
  16. That image works yeah, and I am thinking of pulling the updates I've made to PhoenixMiner into the lolminer repo and releasing it too with autobuild for updates. When I first started working on this container, the PM binary was on mega.nz, then it moved to GitHub, and now it's on a private server hosted by the devs, it's turning into a bit of a nightmare following them around and doing updates manually. There's also phoenixminer.org but strangely it seems like it's not run by the original developers so I can't trust the Binaries from there even though the checksums usually match. The only thing for me is, without OC, PM gets marginally higher hash rate. So yup it's definitely part of the game plan. As soon as work calms down a bit I'll be releasing it.
  17. Sorry @MorphiousGX! I just saw this. Taking a look now.
  18. I'm currently trying to isolate the cause of this issue. Looks like it might be something to do with the in-tree drivers that Unraid is actually using to talk to the card not supporting the features that the amdgpu-pro drivers in the container support. This means there's no errors, because as far as PhoenixMiner thinks it's controlling things just fine, but the host just can't seem to do it. There's a few workarounds I'm contemplating but it's a little messy. This is exactly what I was thinking. @Kvo1087 if you could please share what GPU you have along with the vendor, your diagnostics and container config I can take a thorough look. Feel free to PM me the data too if you'd prefer EDIT: In case someone else comes across this, looks like PhoenixMiner didn't like @Kvo1087's card, they're getting a hashrate with my testing version of lolMiner. I've been having some weird issues since PM's latest update too so fingers crossed it's just temporary.
  19. 😅 I think a lot of people have older hardware than they realise, but you can still possibly get an acceptable hash rate. The latest-18.20 tag could still work but looks like something has broken in the installation of the 18.20 drivers on latest (Ubuntu 20.04 base) since I went away, I'll take a look when I get a chance and patch it.
  20. No worries! I had a look into the reinstalling every time by the way, looks like with the CUDA driver it does so I'll patch that. I think setting a volume on the host to install to will require multiple volumes, I could get around this using symbolic links but it's a little hacky so I'll think about it for a while before implementing it. I'll @guillelopez you when I've worked out a way to do it and implemented it
  21. Hey, sadly probably not supported. You can try the 18.20 drivers (check out OP), if it still doesn’t work you can try the latest-18.20 tag. If it doesn’t work on that we won’t be able to get it going via Docker, earlier driver versions don’t work with the PhoenixMiner binary.
  22. Hello @letrain, @lenny7474, @truthfulie, @captaincu, @joshallen2k, @ptrang, @Maldar, @braydination, @BioHazardous, @melbatoast_355 So I went on holiday expecting to have an internet connection, but I didn't. So I'm very sorry for the delay. Anyway, here goes with my answers to everyone's queries. Sorry if I missed some details there was a lot to read through Looks like you've done the right thing. I get around 29.5 on my RX 580 8GB, can you please share the arguments you're trying to use it with? EDIT: Also your issue possibly ties in with @truthfulie, @captaincu and @Maldar's. Please share your diagnostics.zip if you can. --------------------------------------- Definitely the problem yup. Sadly I don't have an NVIDIA card to test (yet). What version of the Nvidia drivers are you using on your Unraid host? Looks like it's a problem with some of the newer driver versions. --------------------------------------- Do you guys mind terribly sharing your diagnostics.zip? I'll need to get more info on this one to work out what's going on with specific configs. --------------------------------------- Looks like PhoenixMiner can't work out what you want to mine, can you please share the start of the logs and also some screenshots of your config: --------------------------------------- You mean a beta version like this one right? Sorry I have no idea, @ich777 is a genius with these things though. This thread is probably a good place to start. Looks like they're possibly supported out of the box with that plugin but I might be wrong. --------------------------------------- Yup the -powlim argument will do this: -powlim <n> Set GPU power limit in % (from -75 to 75, 0 for default) --------------------------------------- Can you please share some screenshots of your config and the advanced page? --------------------------------------- @BioHazardous thanks for letting me know I was needed over here! And well done working out your first two issues. You're spot on with the SSL config, etc. Sorry I wasn't around to save you some time. Haha I was just writing to ask if you have the GPU statistics plugin installed before I re-read your post and realised you do. With AMD cards, that can conflict with PhoenixMiner being able to get the Fan Speed of whichever GPU it's set to. I don't think it should conflict with the temperature as well but it might with Nvidia hardware, I'm not certain. If you have another GPU, can you please try temporarily setting the stats to a GPU that's not used by the container, or removing the plugin temporarily?
  23. Big thanks to those who helped out in my absence (@creativity404). I went on holiday and was expecting to have a connection to the internet, but I didn't. @Creativity404 Are you still having trouble yourself, or did you get to the bottom of it? Sadly the XMRig data folder is tiny, if you don't want to increase your docker image size, what I can do is install the drivers and use a utility like ncdu to find what locations are suitable to create volumes for. What driver version are you trying to use? Nvidia right? The container is already based on Ubuntu, but the CUDA installation is HUGE which is why I've made it optional. To put it into perspective, the XMRig developers opted to leave out CUDA support in the main release because it the library is like 30mb when built, the 10gb or so you're seeing is quite accurate. I still need to go through and see if there's anything I can strip out of it. It shouldn't redownload every time it restarts no, but it will restart if the docker container is pruned. Can you please share a screenshot of your config and also your logs, I'm happy to take a look too.
  24. 🤔 This is odd. Can you please force an update to the container to make sure you are on a version that handles sigterm, and then please share your diagnostics.zip when the container is unresponsive? Also, are you running the latest-root tag or latest? When it is unresponsive, do the logs not load via docker logs XMRig -f as well as the Unraid WebUI or just the WebUI? And does the first command output something and then not continue, or output nothing at all? Also, when you say a clean shut down do you mean of the container or does it hang your whole server during a shutdown? Because when you shut down, Unraid will try stopping the docker daemon, which tells docker to send sigterm to all running containers, and after about 10 seconds it will send sigkill to them. A couple of things to try: docker exec -ti XMRig apt-get install -y htop && htop When it is frozen, can you please run docker stop ----time=60 XMRig, see if it takes the full minute to stop. If it does, this means sigterm is failing. This shouldn't happen, but your diagnostics.zip could explain why it does.
  25. I think @trig229 is having trouble with a Sapphire RX 6800 XT 16 GB Nitro+ from their logs. Yes I did! And I tried to get it working again today, but still no luck. But it's okay, I don't need to use it with linux anymore. I got it to use with tuya-convert, but I ended up using an Arduino Uno to flash the chips directly anyway. At least it works with my Windows VM so it's not a complete waste 🤷‍♂️.