ich777

Hab den Post mal in den Deutschen Bereich verschoben. Freut mich das du es schon gelöst hast.

I would recommend for both of you that you consult the Issue tracker on GitHub from which the plugins is based on: Click Search for something like "Parsec" or "The host encoder failed"... ...and please always remember what the README.md from the repository says:

If you have reported that early I could have fixed that since the container simply wasn't ready and now it is, another user reported that and I fixed that almost imideatley. This was fixed a few weeks ago, you can now either select if you want to download the stable or beta version from Thunderbird: This is not a bug, simply clear your browser cache. Please make also sure that you are on the latest version from the Docker container itself. EDIT: I'm running my Thunderbird container as my main Mail client with about 20k Mails spread across 5 Mailboxes in it and everything is working fine over here (even the upgrade from the older version to the new went without a hitch) : Please report if you have an issue immediately otherwise I or any other maintainer can't fix them (...and this will save you also a lot of trouble from what I read above).

Usually not. This happens on some systems don‘t worry too much about it, if it runs fine in x86 mode than it‘s fine too.

Please post screenshots form you Docker template. Please disable validation if you have set it to 'true'.

Not posting your Diagnostics...

If you are already on Unraid 6.12.4 try this: Execute this from a Unraid Terminal: mkdir -p /boot/config/plugins/i915-sriov/packages/6.1.49/ Copy the two files from the above post in the folder: /boot/config/plugins/i915-sriov/packages/6.1.49/ Install the SR-IOV plugin Execute this from a Unraid Terminal: sed -i '/ modprobe i915 enable_guc=7/ s/.*/ modprobe i915 enable_guc=3 max_vfs=7/' /boot/config/plugins/i915-sriov.plg echo "# disable autoload old i915 module on boot blacklist i915" > /boot/config/modprobe.d/i915-sriov.conf Reboot

Please delete the file i915.conf from your /boot/config/modprobe.d/ folder and leave the i915-sriov.conf untouched <- I can't do anything about the second file since strictly speaking it is not necessary to have it in there but you have to leave it in place because otherwise the plugin won't work properly or better speaking it can lead to issues again.

To be on the safe side can you post your Diagnostics please? I've edited my post above. I added above this command to be on the safe side: echo "# disable autoload old i915 module on boot blacklist i915" > /boot/config/modprobe.d/i915-sriov.conf (but please post your Diagnostics first and then issue this command) I've edited your post from above.

@domrockt please execute this command once from the command line: sed -i '/ modprobe i915 enable_guc=7/ s/.*/ modprobe i915 enable_guc=3 max_vfs=7/' /boot/config/plugins/i915-sriov.plg and reboot after that. If that also does not work please post your Diagnostics.

Wait, I have found the cause of the issue, give me a few minutes. The activation from the module changed slightly.

I've took a more in depth look and it should work the way that I posted above.

Step 4 shouldn't be necessary. BTW does it work as expected, I had to create a PR to the SR-IOV GitHub that it compiles against Kernel 6.1.49 which Unraid 6.12.4 uses.

For all who are in need of a plugin package for Unraid 6.12.4 here it is: i915-sriov-6.1.49-Unraid.txz i915-sriov-6.1.49-Unraid.txz.md5 To install them do the following: Make sure that you are on Unraid 6.12.3 and that you have the SR-IOV plugin from @zhtengw installed Execute these commands from a terminal (just copy/past them in one go) : mkdir -p /boot/config/plugins/i915-sriov/packages/6.1.49/ sed -i '/ modprobe i915 enable_guc=7/ s/.*/ modprobe i915 enable_guc=3 max_vfs=7/' /boot/config/plugins/i915-sriov.plg echo "# disable autoload old i915 module on boot blacklist i915" > /boot/config/modprobe.d/i915-sriov.conf Copy the two files from above in the folder: /boot/config/plugins/i915-sriov/packages/6.1.49/ Trigger the upgrade process to 6.12.4 from the Update OS page Reboot This is a pretty manual process but it should work. EDIT: If you are already on 6.12.4 please look at this post:

If you bind it to VFIO (which is is visible in your screenshot) the plugin can‘t see the card because it‘s reserved for use in the VM. Please uncheck the two boxes, reboot and it should show up on the plugin page.

This should only be necessary on older CPUs. Battleeye should work OOB without any modification IIRC, it's been a bit of time since I've made this container and I'm not too familiar with mods but it should be pretty straight forward.

Please check if your have stored a key/config on your local PC: You can connect to your server with no key but you actually can't connect to any client because the keys don't match or is non existent in this example on the client (this screenshot basically says that the keys doesn't match) : Even if I connect two clients to my server without any keys they can't connect. Yes: (this is a screenshot without my key/config in appdata) Here is also a screenshot when I connect to my Debian Notebook from my local Windows PC when the key from both clients match my servers key: Here is also a screenshot where you can see that I have a key in my appdata: (I'm one version behind on this PC, but this makes no difference)

I don‘t see any bugs on my system and many people have upgraded without issues. Are you sure that there will be two more versions?

Maybe because you didn‘t look into it like you do now. Transcoding always depends if you need to transcode audio too, in this case for your phone it looks like it is necessary (audio transcoding is of course done on the CPU). For a Nvidia Shield you don‘t have to transcode in most situations because it can play almost all formats regardless of video or audio. Also keep in mind that Plex can‘t handle subtitles well at times IIRC and that can also be a big hit on your CPU.

The log is looking fine to me. Are you sure that the connection is sufficient? Maybe try to tweak the quality and compression sliders, the quality slider will affect the bandwidth and the compressions slider will affect CPU utilization: Basically how my container works is that it puts the main application alongside with the profiles folder in /thunderbird in the Docker container and that's it. For example if you want to transition to another system or even local Thunderbird instance, you only have to pull the profiles folder and import that to the other system. As said above the container is running perfectly fine over here, since I still use the container on a daily basis (EDIT: Just for your information I have about 20.000 mails across 4 mailboxes in my Thunderbird instance). I can only assume that it has something to do with the connection or the remote system in general.

Are you sure that it was from Simon? I think @SimonF has a test server where he has three cards selected and everything is working fine. I also have a server with Intel and AMD selected and one with Intel and Nvidia selected.

Are you sure that you where using the latest version from GPU Statistics?

Maybe, but I can't tell for sure. I use the container almost the same but I use --key _ but that shouldn't make a difference since it does the same. Are you sure that you've specified your key in your client. What you are describing is not possible usually. However IIRC if you tried it first without a key and after that create a key and then connect to the server then it is possible that the client that tries to connect is cached on the server <- but I'm not sure anymore about that since it was a long time ago since I've set up my server/clients. EDIT: I just tried to connect to my server without keys and the connection is immediately rejected (connections with my key are of course possible).

@heroic-barstool8121 please use the support thread from your containers (click on the icon from the container on the Docker page and select Support).

Please describe what you‘ve did exactly and please send screenshits from your template.