ich777

I even don‘t know what this container is used for. You can try to install it in a LXC container and see if this is working.

No, not anymore, the issue was solved by adding cgroupv2 to Unraid. Do you run the container with in provileged mode? But I don‘t think that this will help bor that this is a good idea. Sorry but I even don‘t know what this container is…

What does the logs say? Without then I can‘t tell much. Please stop the container, click on the container icon and then select logs.

Reboot afterwards, this should also be displayed in the plugin removal window.

Maybe it will work but I really can't tell for sure because it's not officially listed but I've got reports about Tesla P4 cards working with the desktop driver and even some K series cards, you can try it and if it doesn't work then please post your Diagnostics and I will take a look into it. But in general the plugin only supports consumer cards.

Yes, why not. You even can build the Kernel inside a Docker container.

I will look into that but I'll maybe drop some features from the plugin anyways. Can you try to uninstall the plugin, reboot, reinstall the plugin and see if that helps?

I've already updated the container now use the new repository from ValheimPlus from over here. You can now also change the repository to your preference. I think even if mods are marked as incompatible with ValheimPlus I don't think that is going to be the case since ValheimPlus also uses BepInEx as the Backend. Is that an issue at all? I have to say that I'm not familiar with r2modman but wouldn't it be possible to place the executable in the Valheim folder and run it from there and let it do it's thing or can you maybe specify a directory where the Valheim files are located? Please note that I'm not planing to implement any mod manager into the container itself since this would be a huge pain. ValheimPlus and BepInEx where also only added because of many user requests, usually I don't implement such things because modding is always up to the user itself.

No, I think Zabbix Proxy is based on sqlite IIRC. Sorry I don't use Zabbix anymore and I've stopped creating templates for containers that I don't use/maintain.

The notification should mention that you should reboot or am I wrong? The notification text should be: Or do you mean that a new version from the plugin is available? A new version from the plugin doesn‘t mean that a new driver package is available… If you want to update the driver package itself, go to the plugin page. But you really don‘t have to update the driver if you are using the card for transcoding, a new driver will not speed up the transcodes. No, even if you do it manually the notification should tell you to reboot. The message should be something like that: I really couldn't do more then writing to reboot in the notification.

I would recommend that you create a bug report for that over here, I don't have any issues on RC5. Also attach the Diagnostics from RC5 where you have the issue.

Please uninstall the SRIOV plugin, reboot and it will work. SRIOV is in a experimental state and not officially supported by the Kernel: Source: https://github.com/strongtz/i915-sriov-dkms/blob/master/README.md

Are you using the SRIOV plugin? Someone reported this over on GitHub: Click The Diagnostics from your systems would be really helpful and what is not working exactly.

Puh, du bist aber mutig, du weißt schon das man in so einen Treiber Backdoors und noch viel schönere sachen einbauen kann... Ohne sourcecode ist das mutig und vor allem weil man das als plugin lösen könnte und nicht die bz files austauschen müsste in denen man noch viel schönere sachen einbauen kann. BTW, das hat auch weniger mit Unraid zu tuhen, das hat mehr mit dem Linux Kernel und der Firma Realtek zu tuhen.

Also zuerst mal muss ich sagen deinen eigenen Thread als Solutin markieren finde ich nicht in Ordnung vor allem weils keinen Lösung gibt... Zunächst ein mal muss hier nichts falsch sein da Realtek es, sagen wir mal, nicht so genau nimt und gerne mal einen anderen Treiberer für mehrere Chips verwendet, siehe hier für deinen Speziellen Chip (Realtek RTL8125B): Der richtige Treiber wäre in deinem Fall der r8152 jedoch muss das nicht heißen das dieser auch der richtige ist da Realtek es eher nicht wirklich genau nimt mit Treiber updates für Linux wie du schon sehen kannst da die up to Kernel 5.17 unterstützen (Unraid 6.12.0-rc5 benutzt derzeit 6.1.27) und es eigentlich dem Kernel Team und der Comminity überlässt die Treiber zu pflegen, good job Realtek... Sorry ich muss mal meine Frust über die auslassen. Der r8169 Treiber ist auch komplett der richtige Treiber wenn du den Kernel In Tree Treiber verwendest jedoch ist es auch bekannt das dieser nicht so funktioniert wie der proprietäre jedoch nicht in dem Ausmaß. 1,6 - 1,9 Gbit/s sollten mit dem in Tree-Treiber möglich sein, den Unraid auch verwendet. Da könntest du recht haben da er direkt auf einen share schreibt und nicht auf die Disk selbst @rene54321 hast du schon mal versucht direkt auf die Disk zu schreiben, sprich einen Disk share zu machen? shfs bremst manchmal, aber so extrem habe ich es bis jetzt noch nie gesehen. Schalt bitte auch mal bonding aus, du hast doch nur eine Netzwerkkarte oder? Hast du irgendwas getuned irgendwo in den settings? Deine Netzwerkkarte reported das Auto-negotiation aus ist.

Can you try to upgrade to the next branch from Unraid, please keep in mind that you are on bleeding edge hardware and the Kernel from 6.11.5 maybe doesn‘t support your iGPU. Bleeding edge hardware and Linux is most of the time not a good combination.

May I ask why? You iGPU should be as capable as the 3060... Just saying... Hmmm, it would be really interesting if HW transcoding is working, can you maybe try to install the official Jellyfin container and pass through /dev/dri and see if this is working?

This is really strange and I can only assume that it has something to do with your 13th Gen CPU but I really can't tell for sure. Do you run Emby/Jellyfin/Plex too on your server? If yes is HW transcoding working there?

This is perfectly fine. Please keep me updated on this...

Now that I see it, how do you added the GPU to the template? Have you done it like mentioned in the second post from this thread? Please note that the flag: --gpus all causes issues on many systems is not recommended by me...

May I ask if you can try it with the official container from over here?

I don't think that's possible but I could be wrong about that...

@supawiz6991, @Draco1544 & @ezhik please update the plugin to version 2023.05.02 and see if the issue is fixed.

First of all I would recommend that you first clean your /boot/extra directory: -rw------- 1 root root 53828 Oct 10 2022 axel-2.17.11-x86_64-3_SBo.txz -rw------- 1 root root 53828 Oct 21 2022 axel-2.17.11-x86_64-3_SBo_nerdtools.txz -rw------- 1 root root 44160 Oct 6 2022 axel-2.4-x86_64-2_slonly_nerdtools.txz -rw------- 1 root root 115844 Oct 24 2022 bc-1.07.1-x86_64-5_nerdtools.txz -rw------- 1 root root 4169268 Oct 6 2022 borgbackup-1.1.15-x86_64-1_nerdtools.txz -rw------- 1 root root 448876 Mar 30 00:30 btop-1.2.13-x86_64-1_SBo_UES_nerdtools.txz -rw------- 1 root root 112024 Oct 10 2022 ddrescue-1.26-x86_64-1.txz -rw------- 1 root root 112024 Oct 21 2022 ddrescue-1.26-x86_64-1_nerdtools.txz -rw------- 1 root root 113520 Mar 6 08:02 ddrescue-1.27-x86_64-1_nerdtools.txz -rw------- 1 root root 3514580 Oct 10 2022 exiftool-12.47-noarch-1_SBo.txz -rw------- 1 root root 3514580 Oct 21 2022 exiftool-12.47-noarch-1_SBo_nerdtools.txz -rw------- 1 root root 17484 Oct 6 2022 fdupes-1.51-x86_64-3_slack_nerdtools.txz -rw------- 1 root root 901728 Oct 6 2022 fzf-0.20.0-x86_64-3_slonly_nerdtools.txz -rw------- 1 root root 1030892 Oct 24 2022 gpgme-1.16.0-x86_64-3_nerdtools.txz -rw------- 1 root root 1058892 Mar 6 08:02 gpgme-1.18.0-x86_64-1_nerdtools.txz -rw------- 1 root root 40252 Oct 10 2022 iftop-1.0pre4-x86_64-4.txz -rw------- 1 root root 40252 Oct 21 2022 iftop-1.0pre4-x86_64-4_nerdtools.txz -rw------- 1 root root 41872 Oct 10 2022 iotop-0.6-x86_64-2_SBo.txz -rw------- 1 root root 41872 Oct 21 2022 iotop-0.6-x86_64-2_SBo_nerdtools.txz -rw------- 1 root root 408544 Oct 21 2022 ipmitool-1.8.18-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 654900 Oct 6 2022 irssi-1.2.3-x86_64-2_nerdtools.txz -rw------- 1 root root 681604 Mar 6 08:02 irssi-1.4.3-x86_64-1_nerdtools.txz -rw------- 1 root root 46324 Oct 6 2022 jdupes-1.21.0-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 906912 Oct 10 2022 lftp-4.9.2-x86_64-3.txz -rw------- 1 root root 906912 Oct 21 2022 lftp-4.9.2-x86_64-3_nerdtools.txz -rw------- 1 root root 121496 Oct 24 2022 libassuan-2.5.5-x86_64-1_nerdtools.txz -rw------- 1 root root 48060 Mar 6 08:02 libffi-3.4.4-x86_64-1_nerdtools.txz -rw------- 1 root root 2553328 Oct 6 2022 libmediainfo-22.06-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 169616 Oct 6 2022 libsodium-1.0.18-x86_64-3_nerdtools.txz -rw------- 1 root root 375968 Oct 6 2022 libzen-0.4.39-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 221744 Oct 10 2022 llfuse-1.4.2-x86_64-1_SBo.txz -rw------- 1 root root 221744 Oct 21 2022 llfuse-1.4.2-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 58460 Oct 24 2022 lzlib-1.13-x86_64-1_nerdtools.txz -rw------- 1 root root 67296 Oct 6 2022 mediainfo-22.06-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 18116 Oct 6 2022 mktorrent-1.1-x86_64-1_nerdtools.txz -rw------- 1 root root 106260 Oct 21 2022 mlocate-0.26-x86_64-4_nerdtools.txz -rw------- 1 root root 47188 Oct 6 2022 ncdu-1.17-x86_64-1gds_nerdtools.txz -rw------- 1 root root 89584 Oct 6 2022 neofetch-20211210-noarch-1_nerdtools.txz -rw------- 1 root root 59996 Oct 6 2022 nload-0.7.4-x86_64-1_slack_nerdtools.txz -rw------- 1 root root 2359896 Oct 6 2022 p7zip-17.04-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 70484 Oct 21 2022 pigz-2.7-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 49279388 Oct 24 2022 powershell-7.2.7-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 206868 Oct 10 2022 powertop-2.13-x86_64-3.txz -rw------- 1 root root 206868 Oct 21 2022 powertop-2.13-x86_64-3_nerdtools.txz -rw------- 1 root root 200264 Mar 6 08:02 powertop-2.15-x86_64-1_nerdtools.txz -rw------- 1 root root 1809344 Oct 6 2022 python-pip-21.3.1-x86_64-2_nerdtools.txz -rw------- 1 root root 2199428 Mar 6 08:03 python-pip-22.2.2-x86_64-1_nerdtools.txz -rw------- 1 root root 673896 Oct 6 2022 python-setuptools-57.4.0-x86_64-1_nerdtools.txz -rw------- 1 root root 674240 Oct 10 2022 python-setuptools-57.5.0-x86_64-2.txz -rw------- 1 root root 674240 Oct 21 2022 python-setuptools-57.5.0-x86_64-2_nerdtools.txz -rw------- 1 root root 914672 Mar 6 08:03 python-setuptools-65.1.1-x86_64-1_nerdtools.txz -rw------- 1 root root 13018740 Oct 6 2022 python2-2.7.18-x86_64-4_nerdtools.txz -rw------- 1 root root 18538524 Oct 6 2022 python3-3.9.10-x86_64-1_nerdtools.txz -rw------- 1 root root 19193916 Mar 6 08:02 python3-3.9.16-x86_64-1_nerdtools.txz -rw------- 1 root root 314872 Oct 6 2022 rar-6.12-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 6331588 Mar 30 00:31 restic-0.15.1-x86_64-1_SBo_UES_nerdtools.txz -rw------- 1 root root 113464 Oct 10 2022 rsnapshot-1.4.4-x86_64-1_SBo.txz -rw------- 1 root root 113464 Oct 21 2022 rsnapshot-1.4.4-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 9117740 Mar 30 00:31 ruby-3.2.1-x86_64-2_nerdtools.txz -rw------- 1 root root 550196 Oct 6 2022 screen-4.9.0-x86_64-1_nerdtools.txz -rw------- 1 root root 43440 Oct 21 2022 sshfs-3.7.2-x86_64-1_nerdtools.txz -rw------- 1 root root 43944 Mar 6 08:03 sshfs-3.7.3-x86_64-1_nerdtools.txz -rw------- 1 root root 3023368 Oct 24 2022 tcl-8.6.12-x86_64-1_nerdtools.txz -rw------- 1 root root 3057248 Mar 6 08:03 tcl-8.6.13-x86_64-1_nerdtools.txz -rw------- 1 root root 3865148 Oct 24 2022 tcllib-1.21-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 366896 Oct 6 2022 tmux-3.2-x86_64-1_nerdtools.txz -rw------- 1 root root 388528 Mar 6 08:03 tmux-3.3a-x86_64-1_nerdtools.txz -rw------- 1 root root 356128 Oct 6 2022 unrar-6.12-x86_64-1_SBo_nerdtools.txz -rw------- 1 root root 63420 Oct 6 2022 utf8proc-2.7.0-x86_64-1_nerdtools.txz -rw------- 1 root root 63600 Mar 6 08:03 utf8proc-2.8.0-x86_64-1_nerdtools.txz -rw------- 1 root root 8472744 Oct 6 2022 vim-9.0.0623-x86_64-1_nerdtools.txz -rw------- 1 root root 8582980 Mar 6 08:03 vim-9.0.1362-x86_64-1_nerdtools.txz -rw------- 1 root root 8584956 Mar 30 00:31 vim-9.0.1418-x86_64-1_nerdtools.txz -rw------- 1 root root 715608 Oct 24 2022 wget2-2.0.0-x86_64-2_nerdtools.txz -rw------- 1 root root 531312 Mar 6 08:03 wget2-2.0.1-x86_64-1_nerdtools.txz -rw------- 1 root root 3056824 Oct 6 2022 zsh-5.8-x86_64-3_nerdtools.txz -rw------- 1 root root 3156392 Mar 6 08:03 zsh-5.9-x86_64-1_nerdtools.txz You have many packages twice or even three times in there, why? I also can't tell for sure if there is a package in there which actually causes the incompatibility. Do you need all those packages? The next thing that you can try is to boot in Legacy mode and not in UEFI. I can't also see the call trace, can you maybe post a diagnostics file after the call trace happened?

This is not how you use the UUID, these are environment variables, please look at the second post.