Jump to content

ButterMeWaffle

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by ButterMeWaffle

  1. 5 minutes ago, ButterMeWaffle said:

    gotcha, I will keep looking into the docker container and see if I can figure it out

    solved it! in the github it mentions that is you have cuda 10 you need to specify it, but it only mentions it for to. Figured I would try using ptrfrll/nv-docker-trex:cuda11 and it worked! 

    • Like 1
  2. 8 minutes ago, ich777 said:

    From what I read so far, everything is uncommon and not related to this.

     

    Diagnostics? Very uncommon that this driver caused this.

     

    Seems this is an issue with the container and has nothing to do with the driver on the host (this plugin).

     

    Sure thing, install Jellyfin add some files to it and let it transcode, you will see that this driver is working, I have tested it, because I test all custom drivers and this one is working just fine... ;)

     

    You have to reboot not just simply turn on and off Docker, turning on and off Docker is only for the first installation.

    gotcha, I will keep looking into the docker container and see if I can figure it out

  3. things have become very odd since installing that driver. Now my AMD GPU cant be seen by pheonix miner and t-rex is saying it cant find CUDA but the nvidia plugin is seeing the nvidia GPU without issues. I wonder if that specific driver version is bad? I wish there was a way for me to test this on my own

     

    edit - I also want to mention that when I turned off docker, as instructed by the plugin, and turned it back on, docker refused to start and I had to restart the entire rig to get it back

     

    edit - Also nvidia-smi works

     

    edit - managed to fix the AMD gpu issue but im still not sure whats going on with the nvidia driver

  4. 6 hours ago, ich777 said:

    This list is only used so that the plugin can determine which are the latest versions from the driver so that it can display the latest versions correctly.

     

    Exactly, because my toolchain only compiles the latest production, new feature branch, legacy 470.x.x driver and if a beta driver is available.

    Each driver has to be compiled for the individual Unraid version…

     

    Can you name a specific version so that I can trigger the build?

    oh man thanks a bunch! 510.73.05 should do, from what I know t-rex just requires a 510 build so I assume the newest should work.

  5. Hello, I was wondering if the newest version of unraid (kernal 5.15.46-Unraid, according to the plugin) would get support for nvidia driver 510.xx.xx? its required for t-rex miner so I imagine im not the only one who needs it.

     

    I did try to edit the config and input a specific driver version but it says it cant be found. I looked through some of the code and found that its getting its list of versions from https://raw.githubusercontent.com/ich777/versions/master/nvidia_versions which obv doesnt include any of the 510 versions. I tried to do some manual editing to force it but its pulling too much from http for me to do it without a ton of work.

     

    I hope im just missing something oblivious! 

×
×
  • Create New...