ich777

Please post in the correct support thread for the Nvidia Driver plugin.

Oh okay, so it was something with DNS or similar? Anyways, glad that you've figured it out. ;)

No, please don't get me wrong but I can't compile all the various driver version for all Unraid versions since the compilation takes about 6-10 minutes for each Nvidia driver, actually not the compilation is the part that takes the longest it's actually archiving the driver because it's semi multi core so to speak most of the time single core. This is really time consuming and please do keep in mind that in the worst case there will be four drivers be compiled for each Unraid version. Please also don't forget that some drivers even do not compile against newer Kernel versions. As @alturismo already said, if you are choosing a driver form the list that is listed below the latest, prduction/new feature/open source branch you should be good to go as long as the selected driver version is also available for the new Unraid version so to speak in your case for both versions 570.144 is a version that is available for both your linked versions: Please do keep in mind if you are compiling your drivers on your own you have to come up with your own solution how to install them since the driver plugin could support it but you have to set the version in the configuration file manually, place the files manually and on top you also have to place the new files before the reboot in a specific directory. However, wouldn't it be better that you simply write a bash script that checks the installed driver from the host or keeps track of the releases in the GitHub repository for the current running Kernel version and makes then sure to install the latest or the driver that you've possibly selected, even easier you could mount a symlink into the container from the Nvidia Driver settings file into your LXC container and from there you could determine which driver version is installed compare it against the current running Kernel version and upgrade the driver inside the container <- this would be way easier in my opinion.

More information would be good, what files, are you running luckyBackup in root mode, do you have any exceptions or inclusions defined in your task, to what type of medium are you running the backup to?

Nothing changed how the plugin works also I can't imagine that a Kernel update or similar is the cause of the issue and it is definitely working for most people since otherwise more people would comment here. The plugin relies on pure bash script language and nothing changed there.

Done.

It's all open source: https://github.com/ich777/unraid_kernel https://github.com/unraid/unraid-nvidia-driver Just look into the source folder from the Nvidia-Driver repo. Sure, don't set it to latest and set a static version in the plugin settings.

Nope, not yet since this requires almost a complete rewrite from the plugin.

Open source drivers are compiled once when a new Unraid version is released, you can upgrade to 7.1.3 and there you should have the driver.

What situation? On what Unraid version are you on?

This is a known issue and it seems Valve wont fix the issue, sorry but this is another container that I have to deprecate.

I'll deprecate the container since it only gives troubles lately. Sorry for not having better news.

Do both of you use Unifi gear by any chance? If yes please check your IDS/IPS rules and logs if there are any hints in there. The driver is pulled from GitHub making a GitHub API Call and then the download from GitHub is initiated, there is nothing more to it. However what I noticed lately that GitHub Downloads can be at times, from certain regions in the World, be very unreliable. I'm not sure what causes this but these are the main reasons what could cause the download to fail: No left GitHub API calls for your IP (60 per hour) Unreliable Download from GitHub Insufficient disk space on your USB Boot Device

Please see this post:

Probably the i2c modules since the first one even does nothing.

Doesn‘t compile against the latest Kernel.

Can you please give me a few screenshots or do you know the exact message? Diagnostics would also help. If we are talking about the automatic update because you are on the latest branch then this even won't bork your system because it would simply remove the new driver which failed to download and the old driver will be still be running, you always have to reboot to switch drivers, the plugin on it's own never does a update from the drive when it's running. Diagnostics after the error message would maybe help or the exact error message itself.

Sorry I don't maintain the OpenRGB container, maybe try to post on their Discord or directly in the OpenRGB Gitlab. However the other user responded with Thanks so I was assuming it is working.

Ups sorry yes, that‘s it, you only have to change the RFB port when you have two noVNC container from me in one container network.

Inside the container? Yes: RFB_PORT

Your ARC Card is bound to VFIO so to speak your Host can't see it. 03:00.0 VGA compatible controller [0300]: Intel Corporation DG2 [Arc A750] [8086:56a1] (rev 08) Subsystem: Intel Corporation Device [8086:1021] Kernel driver in use: vfio-pci Kernel modules: i915, xe 04:00.0 Audio device [0403]: Intel Corporation DG2 Audio Controller [8086:4f90] Subsystem: Intel Corporation Device [8086:1021]Please unbind the card from VFIO, reboot and it should show up. For the crashing I can't help since this is probably related to your system in general, try to set up a syslog server and create a post in the General Subforums.

Yes, the official container: https://hub.docker.com/r/inspircd/inspircd-docker

Sorry, InspIRCd server is now deprecated, I forgot to remove it from CA.

Sorry forgot to reply... Running a different container through my default SteamCMD container is not possible since the start up scripts are all customized to work with the various game servers.

Did you enable console mode as described in the Description from the container for the cron job?