lnxd

Members
  • Posts

    156
  • Joined

  • Last visited

Recent Profile Visitors

1111 profile views

lnxd's Achievements

Apprentice

Apprentice (3/14)

42

Reputation

  1. Hey everyone, sorry for my long absence. As I mentioned on my PhoenixMiner thread, I've had a lot of things going on and not enough free time. If I've missed any important posts please feel free to reply to this again and I'll revisit. I do plan on it assuming it's compatible and not a massive amount of work. Problem is I've forgotten the password for my build VM which is where I stored all my build files, and they're not backed up of course. I'm going to have to make another VM and mount the image over there to get them out. Time is still a massive issue for me, so this will likely happen over the next few days to weeks as I get back on top of things. Had never heard of this until now haha. See my reply to @daemon_of_chaos above though. I think the latest update introduces support for it so yeah, it's probably coming down the line. If you still want this let me know, it shouldn't be a massive amount of work to add it to this container as it's just an xmrig fork, but for simplicity's sake I wouldn't have the three different dev fee options for it. Check out the container logs to get updates, etc. I usually look at the graphs generated by the pool I'm mining to in order to monitor progress as they're way prettier and have come a long way, but you *can* view the docker logs over http / ssh, or access the API directly as @Koldo has provided steps for above. While the binary is interactive in that you can watch the output and use keyboard commands to exert very basic control over it, as you found it's usually controlled by a config file. This container doesn't rely on that config file though, it uses variables which can be set in the edit container page. Your question was so long ago though that I'm assuming you worked it out shortly after posting. It is possible and quite easy to get an interactive session from this container and have it running over SSH in terminal. I used it for testing while I was developing this, but it goes slightly against the way docker was integrated into Unraid so I designed the container to rely on the environment variables instead.
  2. Hey everyone, sorry for my long absence. Have a lot of things going on and not enough free time. If I've missed any important posts please feel free to reply to this again and I'll revisit. I don't currently use this container due to lower profitability since I moved house and my energy price has gone up; and while I've still been maintaining it to the best of my ability, updates will be slow unless I find a way to automate them with new releases from the PhoenixMiner devs. (That's the excuse I'm going with in my head, I really just haven't had enough time to connect my rig back to my server and I'll probably end up selling most of my cards to pay bills anyway 😂) In addition to that, AMD released version 21.40.1 of their drivers in an entirely different format (that they should have been using from the start) so it's going to take a chunk of time to get that working, which is time I don't have right now unfortunately. This container works with most versions between 18.20 and 21.30 at the moment (and semi-secretly has for a few months). When I get a spare few hours I'll see if I can get it going again. I also need to update OP and the readme on Docker Hub. For now the best source of accurate info is the Github readme. Back on the 14th of Sept with @sonic6's help I was able to confirm that version 5.7b and earlier of the PhoenixMiner binary weren't compatible with this card. I've since updated it to 5.9d now that it's available and it may (probably) work now, I haven't got a 6600xt available to test it with. By memory we determined that this card wasn't compatible, and with the direction the container ended up taking it's less likely to be compatible now than it was when @pronto was trying. Basically when hardware crosses that line where it basically becomes 'vintage', chances of getting it working with things like this container that rely on cutting edge software compatibility are slim. I did my best to get it working but even with a really old Ubuntu base image that supported compatible drivers it just wasn't working. I've always thought that message looked a bit strange haha. It's coded into the binary though which I can't change, I can filter the output but it's better if the PhoenixMiner developers just fix it. Something is either misconfigured or malfunctioning, the AMD drivers should only be installed when the container is first run after being created / recreated (eg. after an update, or manually). Like I mentioned above, at present I don't use this container but I've just tested the functionality and it works on my server whereby if the drivers are already installed they don't get reinstalled unless the container is recreated. Please make sure you're up to date (I updated it the other day and it should show PhoenixMiner 5.9d in the logs) and have enough free space available for docker / aren't running a prune on cron/schedule. I wish it was possible to have the AMD drivers work like the Nvidia ones, it would have saved me a lot of work 😅. It's not actually so much a 'people don't use them for that enough so it hasn't been done yet' issue, but an issue where AMD just designed their drivers with blinkers on and have gradually been playing catchup. So unfortunately it's just the way they designed it, the Nvidia drivers are just a more suitable design for purposes such as docker. EDIT: Just introduced support for AMD drivers version 21.40.1, anyone who uses this container with AMD GPUs should take note of the driver version they are currently using and then try updating to this version of the drivers. If it works, stick to 21.40.1 as it's the most widely compatible and up to date version. If it doesn't, go back to the version you were on.
  3. 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.
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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.
  9. 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 😅
  10. 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?
  11. 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?
  12. 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
  13. 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.
  14. Might be a bug in the xml file, but you can edit the webUI port by turning on Advanced in the top right
  15. 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.