ich777

And who is buying me this game...

The classic thread is really outdated since modprobe isn't needed anymore or any modification to the go file, I really wouldn't recommend to send people to this thread...

Can you share a bit more information please? What does not work exactly? Please share your Diagnostics if possible.

Are you sure that you've set all options correct in the in game server list? This list is a mess from my perspective because if you have set one option wrong it will prevent the server from showing up. Also keep in mind that it can take a bit until it shows up in the in game server list. Are you sure that hair pin NAT is working correctly? Have you yet tried to connect from a computer from outside your LAN? Are you also sure that you are not behind a CG-NAT? Please double check the port forwarding and only forward the ports with the appropriate protocol as listed in the template, if a port is listed as only UDP then forward only UDP and not TCP/UDP same goes for TCP ports. There is none, the game will show up by default in the public server list by default if everything is forwarded correctly and it is actually reachable from the Internet.

I would recommend that you change the name in the screenshot to something like: "Intel GPU" and remove the description because it's not really needed anyways and could confuse users so that they maybe believe the have to put in the description. Maybe also add a note at the end if a user has multiple GPUs installed like mentioned in the post over here (at the end from this post): Because you can't specify which card Plex has to use you have to maybe map it to a different card/render-device.

Please don't do it that way, it would be better to remove the lines from the go file, execute these commands from a Unraid terminal and reboot afterwards: mkdir -p /boot/config/modprobe.d echo "options i915 enable_fbc=1 enable_guc=3" > /boot/config/modprobe.d/i915.conf With that you ensure that the module is loaded with these options without any messing around with the module when it's already loaded.

I think there is something missing on your Target but I even don't know what software that is from where you posted a screenshot. Are you sure that the Initiator name is in the ACL from the Target? From my perspective it can be only a little miss configuration since even the Target shows that your Initiator (Unraid) is connected.

That's a thing I can't answer... I've now pulled a fresh copy from the CA App and have no issue that the server is showing up in the Steam Server Browser: Have both of you just yet tried to run a complete vanilla version from the container without changing anything in the template and/or config files? I've attached also the log from the first start up from the container itself: ark.log

Did it work OOB? There was a reason why I wrote that you should tell me if it works without doing the modprobe or with the modprobe because I want to add this module to the plugin and I have to maybe edit the plugin if you had to do the manual modprobe.

Sorry but I really can't help with your issue, I'm simply out of ideas what to try next and why it isn't working for you because I simply can't reproduce this on my end...

This is none of my containers... As said above, I don't expose ports in the Docker file because it can lead to more confusion. Just imagine you are changing the port in the template and nothing changes on the WebGUI, btw try it on the binhex container, it won't change anything and will still show the ports from the screenshot and even if you change the ports in the template while using br0 this won't work because as said above all ports are exposed. With that little information that you've share so far no one can help... Please share at least a screenshot from your Docker template, did you change anything to the server or the files? How do you search the game? Did you yet tried to add the IP and PORT to the Steam Server Browser favorites an clicked Refresh? One side question why are you not using the default bridge network? I wouldn't recommend br0 but it's up to you anyways.

Really, can you tell me which? It is really unlikely that the both use the same layer because I have my own base image (which is based on Debian Bullseye slim), I also have my own Dockerfile and SteamCMD is not included in those layers. Do you maybe have another container installed from me since all my images are basically based on the same custom base image or have you dangling images on your system (turn on advanced view and look at the bottom).

It is also working for Ark. As @Nodiaque said, br0 will open all ports to the specified IP in the docker template, you can think of it as being a dedicated computer on your network. It simply doesn't show any ports because I don't specify ports in my Dockerfile which can cause even more confusion... Nothing to worry about.

I really don‘t know but look into Paragon Linux Filesystem, it‘s a paid software and it works really well but I don‘t know if it will work with encryped drives… you can try at least, they have a 30 day trail I think.

Please do the following: Make sure that you have installed @SimonF's plugin "USB Manager Serial Options addon" Download the attached txz and txz.md5 package from this post Navigate through SMB or your favorite SCP software to /boot/config/plugins/Usb_manager_serial_options_addon/packages/5.19.17/ Delete the existing txz and txz.md5 in this folder Place the downloaded files from the attachment in the above mentioned folder Reboot After that the module should be available and hopefully should be loaded automatically. Please let me know if it is loaded automatically, so to speak if the device is found automatically and the driver is loaded or if you have to do a manually with: modprobe usb-serial-simple Please note that the this attached packages will only work on Unraid 6.11.5! Keep me updated and I can add it to the plugin. usbserial-20230219-5.19.17-Unraid-1.txz usbserial-20230219-5.19.17-Unraid-1.txz.md5

You have to only replace the bz* files and the changes.txt file if you want to upgrade… Exactly, but since I‘m only testing whats currently possible with ARC I don‘t have to do this currently. This is also not entirely true… have you compiled the Kernel yourself? Maybe something went wrong there since I have no issue usig the card with Emby. I‘m not too sure about Plex because I don‘t know if they are using QuickSync (which is not ready yet for ARC) but if they are using the VA-API it should be no issue at all but I can also imagine if you have a second card installed which actually uses /dev/dri/renderD128 and your ARC card is /dev/dri/renderD129 in the system this will cause issues and you need to map it from the host to the container with something like that in the template: --device=/dev/dri/renderD129:/dev/dri/renderD128 And you also have to map the card from 1 to 0 like: --device=/dev/dri/card1:/dev/dri/card0 This should work for Plex too if they are using VA-API instead of QuickSync.

Du hast deinen letzten Post als Report an die Mods geschickt, bitte poste nochmal hier, ich lösche den Report.

Can you post your Diagnostics with the device attached, I‘m mostly interested in the vendor and device ID.

May i ask if you use this in combination with software? I will keep you updated about that (will take me a bit because I‘m currently mot at home), have to look into it what other modules it pulls in.

Can you please explain what this is and maybe a link to it? I will have a look at that, I‘m assuming you are on 6.11.5 correct?

As far as I can tell you are connected to the Target: Feb 17 16:37:30 Server kernel: scsi host8: iSCSI Initiator over TCP/IP Feb 17 16:37:30 Server root: Logging in to [iface: default, target: iqn.2004-04.com.qnap:ts-433:iscsi.backup.634ac9, portal: 192.168.0.7,3260] Feb 17 16:37:30 Server root: Login to [iface: default, target: iqn.2004-04.com.qnap:ts-433:iscsi.backup.634ac9, portal: 192.168.0.7,3260] successful. Feb 17 16:37:30 Server iscsid: Connection1:0 to [target: iqn.2004-04.com.qnap:ts-433:iscsi.backup.634ac9, portal: 192.168.0.7,3260] through [iface: default] is operational now Are you sure that you've assigned a disk on the Target to the LUN and configured everything properly on the Target? At least the connection seems to be working fine. However I would recommend that you install the plugin Unassigned Devices and check if you see the the disk afterwards there.

There is already the plugin USB Serial in the CA App from @SimonF please try it and see if it is working (reboot required after installation). I don‘t know what this device and I don‘t know if the plugin does handle this device too, please keep me updated if it is working for you. If not I can look into it what‘s needed to add it to the plugin.

This is almost the same as NTFS, use a Linux file system…

And there is your problem, the container has no network anymore and you have to specify which network the container should use and that is simply missing in your configuration. Please read the description from the OpenVPN container again, you have to have a parameter in the first Extra Paramerts entry (only visible with the advanced view enabled). I would also recommend that you delete the port entry from the Chromium container to avoid further issues.

Yes, because NTFS can‘t save all the properties from Linux file systems and that‘s why they are different.