ich777

I don't know, you have a patch script in place which I don't support and which could be the culprit from your issue. Maybe a user script? The iGPU from your CPU should be more than be capable of such a task. Above 4G decoding needs to be enabled in your BIOS including Resizable BAR Support <- this is also a setting in your BIOS. You can define a User Script which runs on boot with the contents: nvidia-persistenced This will ensure that your card is constantly in a low power state (at least when it's not in use) and hopefully not fail to initialize. Your iGPU on the CPU is dedicated from the CPU and the CPU will be not impacted or better speaking will not be affected by the load from transcoding if you use the iGPU. Oh, please also check your Power Supply, they degrade over time and if a power spike happens because a HDD spins up and transcoding starts it is possible that they fail to deliver "enough" power and such issues can happen.

First of all, why: Dec 17 14:55:33 NAS emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/Nvidia Patch/script" >/dev/null 2>&1 Please read the first post and especially the red text, you are modifying the driver and I can't give support for that and in reality how much concurrent streams do you have which need to be transcoded? This is the real issue: Dec 24 00:06:15 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584) Dec 24 00:06:15 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Dec 24 00:06:17 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584) Dec 24 00:06:17 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Dec 24 00:06:19 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584) Dec 24 00:06:19 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Dec 24 00:06:21 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584) Dec 24 00:06:21 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 I can't tell you why that is caused (maybe because of your patch script) however I would recommend that you do the following: Check if your BIOS is up to date Check if you have Above 4G Decoding enabled Check if you have Resizable BAR support enabled Use that as your startup script instead of patching the driver: nvidia-persistenced However I really don't see why you are using a Nvidia for transcoding, you have a Intel iGPU in your system which is probably well enough for you to transcode (Intel has no hard limit of simultaneous transcodes BTW).

Sorry, but first of all this is the wrong support thread, secondly I can't help with that since I don't know how this dedicated server is working/starting in general and I don't know/own the game.

Please do the following: Stop the container Delete the folder runtime and bin from the main directory for Portfolio Performance Start the container (will take a bit longer) After that everything should work again.

What is the exact issue, do you have any logs? On what hardware do you run PZ?

Not possible, the maintainer made it a few times clear that he don't want to have 3rd party's to be able to add premium. I think he has a dedicated Docker container where you cann add the license.

Did you read the answer that I gave? Anyways, Diagnostics are missing. Please also note that the user has two issue, downloads not working and the driver not working.

The size of the modules? I think we are talking about a 100% increase so to speak double the size or even more. I have already done that in the past to test that since you are not the first one who is requesting this feature. Usually not (I also speak German but never heard of "Schwuppdizität" :P ). I don't think so, but please remember having bigger modules does mean a significant bigger Unraid release, more RAM usage and so on. I don't understand that question TBH, sure some users would benefit from that since you would be able to run Falcon and other monitoring software (which is usually paid only). Since this is a significant change and also will possibly change the hardware requirements from Unraid, since more space on the flash drive is necessary and to an extent also more RAM is required. As said, I think this feature is planned but I don't have an ETA for when it's implemented.

Please read this post: https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/211/#comment-1593815 Is it possible that you have those two lines on your plugins settings page like in this post: https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/178/#findComment-1487703 If yes please read the next post to fix your issue. If you don't have those two lines in your plugins settings page then please make sure that nothing is blocking access to GitHub and also make sure to disable AdBlocking if you have it in place, your server needs exclusive access to the Internet without any AdBlocking. If you have Unifi Network gear please also check the logs if it's blocking access to GitHub for your server.

Please do keep in mind that this has not strictly speaking something to do with Unraid, I was suffering from the same issues on my Linux Desktop PC with an RTX3080Ti and the ultimate issue was a wrongly set BIOS setting, at least in my case. The GSP error could also be a hardware defect. From what I see the card is listed as supported in the Supported Products tab here: NVIDIADriver Details | NVIDIADownload the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

Most of the times hardware incompatibility, outdated BIOS or wrong set BIOS setting. Please try: Updating the BIOS to the latest available version Enable Above 4G Decoding in the BIOS Enable Resizable BAR Support Put the line nvidia-persistenced in your go file (put it at the very end of /boot/config/go )

Why would you do that? If you can get it for cheap or at least for a reasonable price I would always stick to the newer cards. If you are choosing a 5060 you have no other choice to go with the Open Source driver, but as said above, that always depends on your hardware and you didn't mention yet what hardware that you have nor uploaded Diagnostics, but even then I really can't tell if it works or not. But I would see it the other way around, the open source driver for 7.2.2 (and 7.2.3) where already downloaded about 1.800 times and only a few people postet here that it won't work and to add to that, most of the issues where solved (mentioned above the issues and solutions), here are the exact downlaod numbers: name: 6.12.54-Unraid, name: nvidia-575.64.05-6.12.54-Unraid-1.txz, download_count: 829, name: nvidia-580.105.08-6.12.54-Unraid-1.txz, download_count: 17538, name: nvidia-580.119.02-6.12.54-Unraid-1.txz, download_count: 1064, name: nvidia-580.65.06-6.12.54-Unraid-1.txz, download_count: 132, name: nvidia-580.95.05-6.12.54-Unraid-1.txz, download_count: 9402, name: nvidia-590.44.01-6.12.54-Unraid-1.txz, download_count: 10457, name: nvidia-590.48.01-6.12.54-Unraid-1.txz, download_count: 3420, name: nvos-580.95.05-6.12.54-Unraid-1.txz, download_count: 1776, As said, I wouldn't do it. No, there is none and the reason is simple, the proprietary driver is closed source, so no one knows what's exactly different except Nvidia, however Nvidia recommends to use the Open Source driver anyways and there you can see how it works since the Kernel module is Open Source, the libraries are still closed source: GitHubGitHub - NVIDIA/open-gpu-kernel-modules: NVIDIA Linux ope...NVIDIA Linux open GPU kernel module source. Contribute to NVIDIA/open-gpu-kernel-modules development by creating an account on GitHub.

Maybe, depends on your hardware and you BIOS settings. Most issues are caused because pairing outdated hardware with 50 series cards, outdated BIOS versions, wrong settings in the BIOS. Irrelevant since 50 series only supports the Open Source driver. The Proprietary driver doesn't support 50 series and that has nothing to do with Unraid since this is a limitation from Nvidia.

That's not entirely true, since if you enable this option, the Kernel modules would blow up in size (almost double the size IIRC) and therefore that would mean much bigger releases. IIRC this was the main reason why it wasn't enabled yet.

This indicates that your server can't download the steamcmd binary. Do you have any AdBlocking somewhere in your network or Unifi network gear? Please make sure that your Server has full access to the Internet and is not behind any AdBlocking software. To be more precise the file that the container want's to download is this file: http://media.steampowered.com/client/steamcmd_linux.tar.gz I would recommend that you start over: Delete the container Delete the folder for the container and also for steamcmd from your appdata directory Make sure that nothing is preventing the container from downloading that file Pull a fresh copy from CA

Maybe @Mainfrezzer can help.

The container is self maintaining and there is nothing that needs to be updated. On each start/restart the container checks for updates and pulls new updates, if the container doesn't do that, please see this recommended post: https://forums.unraid.net/topic/79530-support-ich777-gameserver-dockers/page/459/#findComment-1501323

Similar yes, but the old way of doing that and will be eventually be deprecated by Nvidia, please use nvidia-persistenced <- you can also put that in a User Script that runs on boot.

I really don't know why you did that, that is not necessary, the plugin manages all on it's own, just select the driver you want to have, wait for the download to finish and reboot. ...and as always the AI is mostly wrong with that answer anyways, I really don't understand why you trust a AI agent more than the plugin author. :D You don't need to do any custom commands or anything, the plugin is designed to be easy to use without any user intervention. This will survive a reboot, I really don't understand why it shouldn't? Please don't do anything with custom commands or anything, the plugin manages everything on it's own.

Just reboot as the driver says. You haven't answered a single question, you install the packages manually correct? After inspecting your Diagnostics from a previous post, you have both packages installed: ... -rw-r--r-- 1 root root 12777 Dec 16 00:01 nvidia-580.119.02-6.12.54-Unraid-1 ... -rw-r--r-- 1 root root 12710 Dec 16 00:01 nvos-580.95.05-6.12.54-Unraid-1 ... which is something the plugin won't even attempt to do. The plugin will only install one driver and even when changing the driver version the only driver that will be installed is the one which was installed and the new driver will be installed on next reboot, the plugin even tells you to reboot after you changed driver versions, except if you change the driver version to the current installed one. You don't have to delete anything, just switch to the driver version you want to use in the plugin, wait for the download to finish and reboot after that, as the plugin tells you to.

Two question, do you reboot when switching versions? Do you install the package manually? Sorry but I really can't tell what's wrong since nobody else seem to have that issue and the drivers for Unraid 7.2.2 are downloaded a lot, here are the numbers from GitHub: name: 6.12.54-Unraid, name: nvidia-575.64.05-6.12.54-Unraid-1.txz, download_count: 795, name: nvidia-580.105.08-6.12.54-Unraid-1.txz, download_count: 17521, name: nvidia-580.119.02-6.12.54-Unraid-1.txz, download_count: 424, name: nvidia-580.65.06-6.12.54-Unraid-1.txz, download_count: 124, name: nvidia-580.95.05-6.12.54-Unraid-1.txz, download_count: 9395, name: nvidia-590.44.01-6.12.54-Unraid-1.txz, download_count: 10315, name: nvos-580.95.05-6.12.54-Unraid-1.txz, download_count: 1671, I just downloaded the open source driver package for version 580.95.05 and every library is consistned and has only 580.95.05 in them. I also downloaded the driver package for version 580.119.02 and there are only the libraries for driver 580.119.02 in it. Then I did the same for the driver package for version 590.44.01 and the libraries match the driver version. So to speak, I really don't know what the issue on your system is, everything is in the correct spot. You'll find the packages here if you want to take a look at them yourself: https://github.com/unraid/unraid-nvidia-driver/releases/tag/6.12.54-Unraid I really don't know what's going on on your system.

That's really strange to me since I always compile from the official driver package and all files should be the same driver version because it's the package from Nvidia and TBH others would have the same issue as you, so my assumption was something is replacing the nvidia-smi library or other libraries on your system.

I'll look into this but this will take a few days weeks since my PC is currently not working.

No, it works just fine. Please see this recommended post:

Maybe but please keep in mind that most of my templates are customized for the specific dedicated server because each individual server has it's own little requirements.