ich777

Looks like everything is showing up correctly, have you passed through /dev/dvb to the Plex container? The only thing that I can imagine is that the newer driver version from my plugin is messing up something in Plex... Can you try to download TVHeadend and see if the cards are recognized there (don't forget to pass through /dev/dvb)?

I don't know what to say... Was it working before? The thread is from 2018... I still can't reproduce this error in my case it is just working, I will update the plugin soon so there will be a timeout if the VM or computer isn't started at the time when starting the plugin. @alturismo do you know eventually what's the problem here, eventually a wrong version from MSI Afterburner Server?

Can you attach your Diagnostics (Tools -> Diagnostics -> Download -> drop the downloaded zip file here in the text box) please? What Plex container are you using? The official one? Is the card showing up on the plugin page? Which package are you using?

Please attach the Diagnostics again.

Don't know how you did it in the first place but go to Tools -> System Devices and you should see ticked check boxes if I'm not mistaken, remove those at the P2000, click on Apply and reboot your server. Also I assume that you have enabled Autostart for your VM enabled or started it manually since the plugin finds your RTX4000 and loads the driver for the card (after you start a VM the plugin also can't see the card anymore): Jul 26 18:11:36 HouseofGivens kernel: nvidia 0000:81:00.0: enabling device (0000 -> 0003) Jul 26 18:11:36 HouseofGivens kernel: nvidia 0000:81:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none Jul 26 18:11:37 HouseofGivens kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). Jul 26 18:11:37 HouseofGivens kernel: NVRM: This can occur when a driver such as: Jul 26 18:11:37 HouseofGivens kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv Jul 26 18:11:37 HouseofGivens kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s). Jul 26 18:11:37 HouseofGivens kernel: NVRM: Try unloading the conflicting kernel module (and/or Jul 26 18:11:37 HouseofGivens kernel: NVRM: reconfigure your kernel without the conflicting Jul 26 18:11:37 HouseofGivens kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Jul 26 18:11:37 HouseofGivens kernel: NVRM: again. Jul 26 18:11:37 HouseofGivens kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 Jul 26 18:11:37 HouseofGivens kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 470.57.02 Tue Jul 13 16:06:24 UTC 2021 Jul 26 18:11:37 HouseofGivens kernel: [drm] [nvidia-drm] [GPU ID 0x00008100] Loading driver Jul 26 18:11:37 HouseofGivens kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:81:00.0 on minor 0

From what I see in your Diagnostics you have bound these devices: BIND=c1:00.0 45:00.0 to VFIO where one of them is the P2000 (c1:00.x): c1:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106GL [Quadro P2200] [10de:1c31] (rev a1) Subsystem: NVIDIA Corporation Device [10de:131b] Kernel driver in use: vfio-pci Kernel modules: nvidia_drm, nvidia c1:00.1 Audio device [0403]: NVIDIA Corporation GP106 High Definition Audio Controller [10de:10f1] (rev a1) Subsystem: NVIDIA Corporation GP106 High Definition Audio Controller [10de:131b] You have to unbind the P2000 from VFIO so that the plugin actually can see the P2000, if you bind it to VFIO the plugin can't see the card because the card is reserved for exclusive use in a VM.

Have you tried to start from scratch? Is the share that the game is on set to Use Cache "Only" or "Prefer"?

These errors are just normal, a dedicated sever has no volumeteic lighting because it has no display output and you see on a few dedicated server such errors related to the graphics engine because of the above mentioned reason and they can be safely ignored. Yes and no, actually I try to avoid making the console available through for example a webgui/webterminal because this can lead to other various problems... You should be also able to issue commands from ingame on your server if you are a admin on the server.

Please attach your Diagnostics.

Sorry I really can't help here, on some motherboards/hardware combinations it seems to cause issues, but I haven't found out what it is or what causes this.

Have you got a spare disk that is not assigned to the Array or to a Cache Pool? If not that's the problem.

Can you please reset your BIOS, somethings seems wrong, also make sure that you've boot into Legacy mode. Are you sure that your PCIe port delivers enough power, but it seems like it should since you've said you've used the card in a VM before.

What command do you exactly run? I will try to setup a server so that is visible from outside when I got time so you can connect and test, only have tried it like the method mentioned above.

I'm really not sure if this will work because you have to change a few things in the extra parameters from the template...

Anyways, you can also try Bullseye but keep in mind that I update the container after a few days after the official release from Bullseye to be on the latest packages. EDIT: Maybe I'm releasing a Bullseye container with KDE Plasma, don't know if it's worth it because I like function over looks...

I leave some containers long at a Beta state because they never fell really finished to me... You can safely use it, I use it on a daily basis and also have writen many containers and plugins in it... I think so, I'm not really familiar how this application works. Buster = Debian 10 based | Bullseye = Debian 11 based (since it's not really released it's really a beta, from what I know the official release is on 18th August)

From what I see this is a Sandy Bridge system C200 series chipset. Please make sure that you've enabled above 4G decoding in the BIOS. Have you also installed the GPU Statistics Plugin on your system?

Are you booting with UEFI or Legacy? If you are booting with UEFI (looks like you are booting in UEFI mode) try to boot with Legacy mode.

Works just fine in my Debian Bullseye container, but I recommend doing it with my Debian Buster container: Of course you have to install python3, all dependencies manually and afterwards install tartube with dpgk (to gain root privileges in my container you have to type in "su" and then the specified password for your root user). Since tartube creates a directory for all the files in ~/.config/tartube, the config from tartube is persistant. The only thing that I would do is to create a user.sh like @Ford Prefect mentioned above so that the container checks on every start/restart if tartube is actually installed and the needed dependencies. You can of course add another directory to the template where you store your downloads from YT. Looks like it's working perfectly fine:

From in game you should be able to issue commands to the server if you are registered as admin. Is this something that is really needed? I think many people install Oxidemod to RUST from what I know and if that's installed you have other ways to connect to the console if I'm not mistaken.

I don't think you will see this natively on unRAID since this violates the EULA from Nvidia.

Du musst danach neu starten, der befehl erstellt lediglich eine Datei am USB stick das unRAID weiß das es den treiber beim booten laden soll, alternativ mach: modprobe i915 Da bekommst du dann auch keinen output aber das lädt den treiber.

Sometimes host access won't work after a reboot, the solution to this is to restart the Docker service.

Ich hab mir nicht genau angesehen welche generation das ist aber ab Broadwell funktioniert GVT-g. Wenn entweder Intel-GPU-TOP oder Intel-GVT-g Plugins drauf sind nicht da das die Plugins erledigen aber Grundsätzlich ja.

You can map the key inputs to the controler, this should work for now, also this works better than expected from my testing in Dirt Rally back in the days. I will release a updated version from the container with Debian Bullseye but no ETA on that yet and look again into controller support. Sadly enough this also won't work...