ich777

Thaha, Intel really messed up lately with their iGPU drivers. Can you maybe send me the Diagnostics from your system with Kernel 5.18RC5 (I think @thor2002ro creates those builds or am I wrong?).

Not really. This can also be caused by a container but this is only a guess... As said above, tested the driver and transcoding on my Nvidia T400 with three concurrent streams is working just fine.

Have you changed anything in the template? Maybe please post a screenshot. From what I see in your logs it started successful. I think the dedicated server doesn't show up in your local available servers in your Steam Server Browser. Try to add the server in the Steam Server Browser at the Favorites tab and click on Add Server and enter: YOURUNRAIDIP:2457

What issue? Do you have a screenshot, Diagnostics, or anything? I can't diagnose anything without anything, driver version, Kernel panic, Unraid version...? EDIT: @disco4000 & @FEF Tested it now on my test machine and seems like there are no issues whatsoever:

Are you actually using Ferdi-Client? I've deprecated the container because the maintainer abandoned the project or is it back again? I saw that it is back again, updated the container a bit and pushed it already to DockerHub and the GitHub container registry.

This is really odd... Try to set the variable to: -securitytypes VNC and see if that helps.

Not the password but you can set it in your compose file at the "environments" create another entry that looks something like: environment: TURBOVNC_PARAMS: "" Of course your other variables have to go there too like the UID, GID,... Don't forget to first set the password like described in the recommended post in this thread on the top. Where do you have issues, it should work just fine on Portainer too I think or do they not allow empty environment variables? Hope that helps.

Can you please point me to the resources that you are referring to?

My test server has a Nvidia T400 built in and I test HW transcoding for Nvidia there and it is working fine since 6.8.2 up to the latest RC version.

I don‘t understand completely… Do you have a custom Kernel installed on RC5? Keep in mind that Kernel 5.18 is still RC and not stable. As Tom pointed out, Unraid 6.10.x stable will stay on the latest LTS Kernel, which is at time of writing 5.15.38 and 6.11 Unraid 6.11.x will then have the latest stable Kernel which is as time of writing 5.17.6 It is maybe possible that 5.18 has became stable and that 6.11 will have Kernel 5.18+ Intel made a real mess here lately and that‘s why I always recommend to make sure that bleeding edge hardware works on Linux before buying.

Don't know, if the dummy actually doesn't work and you boot the server up you will get a notification (beep codes usually that no VGA is plugged in) and if you are on the Unraid RC versions you can see almost immediately at boot an issue with the i915 module when it initializes... Ah okay, the more you know... Then TrueNAS Scale is basically almost the same Kernel version as Unraid 6.9.2 (5.10.28), do they have a beta channel too with a newer Kernel, something like 5.15.38 (latest LTS Kernel) so that you can check that you don't run in exact the same issues as on Unraid?

Have you a display plugin in to the HDMI for you iGPU constantly? I had a few people so far with crashing servers on the 6.10.0-rc series (of course not 12th Gen because this will be fixed in versions Kernel 5.18+) but when plugging in a HDMI dummy plug or a monitor it solved that crashing. Please keep also in mind that Intel made a huge mess out of his drivers for Linux from Kernel versions starting with 5.10 and up to now from my perspective. Ah wait, TrueNAS is based on BSD or am I wrong?

@RogerWilco486 & @mechmess which container (repo) from Plex are you using on Unraid?

Please update the container, it should now work. Also please set the password first as non root user as instructed in the recommended post and if that is working, or if it is already working for you with non root, then switch over to root.

Please share your Diagnostics. I really can't imagine why it is working fine on my system i5-10600 and on the system from @alturismo i9-10850K just fine (I'm using Emby/Jellyfin and he uses Plex/Emby) wher it isn't on yours, don't know if @sonic6 transcodes that much but he also is running a i3-10400 and it works there too with Plex from what I know. I think a lot of users are runing 10th Gen hardware transcoding without any issues so far also on the latest RC versions. But what is different on TrueNAS than on Unraid? What Kernel version does your TrueNAS box run? I can also imagine that it has something to do that TrueNAS runs Kubernetes instead of Docker/Containerd/Runc

You don't have to use Intel GPU TOP anymore because the iGPU is actiavated on boot by Unraid itself, however you have to use it if you want to use it with the GPU Statistics plugin, otherwise GPU Statistics won't work.

This doesn't seem to be caused by the iGPU. Can you maybe create a issue for this on the bug tracker?

Can you please upload your Diagnostics?

Did you enter only "su" or did you enter "su $USER" (without double quotes)? For what container do you try to setup a VNC password?

? This is the message after installing the plugin for the first time. Do you have any issues? Can you please also post your Diagnostics if you have any kind of issues?

From what I see in your Diagnostics nothing is left over from CoreFreq and also the driver that caused the issue "corefreqk" is also not loaded. Is it maybe possible that you after you've uninstalled CoreFreq that you didn't reboot? That's the only thing I can think of. You actually have to reboot after removing the plugin, the plugin also brings up a message that tells you to reboot at the removal screen.

I have to look into this but this should no issue whatsoever. Give me a bit since I'm currently fighting with a pretty bad cold...

Can you try to remove the container, then remove the openrct2 folder that's located in your appdata directory and then try to pull a fresh copy from the CA App. After that let it fully start, stop it, edit your config, start the container and try to connect. This will make no difference in terms of the password. Yes because you don't did the necessary port forwarding, it will only show up when the master server is actually able to connect back to your server and that's only possible if you did the port forwarding properly. !!!! Please leave this value at null otherwise it won't work properly !!!! As said above I tried this on my server with a fresh pulled copy from the CA App, let it start, stopped it, changed the config (only edited the server name), did the port forwarding and started the container again.

Can you send me your Diagnostics? This is really uncommon or better speaking not possible that CoreFreq is installed after you‘ve uninstalled and rebooted.

Have you rebooted after you‘ve uninstalled the plugin?