ich777

For what would you use it with the legacy drivers? This card isn't even capable of transcoding most of the things out there today. Also the legacy drivers won't work properly with Docker container in general. I can recommend you to get a Nvidia T400 you can get them brand new for about $130,- (2GB Turing card).

I'm very sorry but the driver reports this: Jan 3 18:37:33 Tower kernel: NVRM: The NVIDIA GeForce GT 730 GPU installed in this system is Jan 3 18:37:33 Tower kernel: NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please Jan 3 18:37:33 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Jan 3 18:37:33 Tower kernel: NVRM: information. The 470.94 NVIDIA driver will ignore Jan 3 18:37:33 Tower kernel: NVRM: this GPU. Continuing probe... Jan 3 18:37:33 Tower kernel: NVRM: No NVIDIA GPU found. From what I've found online there are a few cards out there who are not compatible, is it this card: Click If yes, you are may be out of luck. There are "old" and "new" GT 730's out there and only the "new" ones are supported.

Please post your Diagnostics.

This is now deprecated, the last version that I support is 6.9.2 Exactly, I deprecated the Kernel Helper because nearly everything can now be integrated to unRAID via plugins.

Wait, you are trying to connect over the internet from what I see, is NAT reflection working or did you try this from your local network? Have you yet tried to connect through your LAN? I would also recommend that you double check the port forwarding and the protocols.

Can you send over a screenshot from the message? I've now tried it on a fresh copy pulled from the CA App and it works flawlessly: Have you also created and fille in the 'serverSteamAccount' like described in the GAME_PARAMS variable? I will also push an update to the container itself shortly to update the base. DONE This is what a full startup looks on my server: theforest.log

This should be the correct syntax: enablecheats ADMINPASSWORD Have you set the admin password in the GameUserSettings.ini file or in the template, I would strongly recommend to set it in the template.

This warnings are pretty normal and are produced by WINE. I will install the dedicated server on my server to try it on my own and report back. Server runs just fine, see 2 posts below.

That is really strange since I've also run an instance with Valheim+ and I have no issue whatsoever with a lot of changes. Have you changed anything in the template itself, if possible post a screenshot. With what editor are you editing the file? Is the world saved or is it also wiped after you've restart the server? As said above everything working fine here, even after an update from Valheim.

If you want the AMD Vendor Reset Patch you have to be at least on 6.10.0 to find it in the CA App. The Kernel-Helper is deprecated with v6.10.0 you only see it because you're on 6.9.2.

Kannst du mal versuchen nicht mit UEFI zu booten sondern mit Legacy? Bitte änder doch den Titel vom Thread, du hast laut Diagnostics ein B560M PRO-VDH kein B650M PRO-VDH

Maybe try to create a dedicated share that is only allowed to write on disk2 and point it to there like: '/mnt/disk2/gameservers/arma2', also don't forget to set the profiles path at the bottom to this location with the 'profiles' extension.

Bitte deinstallier mal das GVT-g Plugin bitte und versuch mal den Governor auf 'powersave' zu stellen, spart bei meinem i5-10600 nochmal 10Watt ca. ein. Brauchst du das GVT-g Plugin, sieht auf jeden fall so aus als crasht das i915 modul und nimt noch einige andere sachen mit. Probier nur das GVT-g Plugin zu deinstallieren, reboote, dann lad nochmal die Diagnostics runter und lade sie hier hoch.

To what is your appdata folder set? To disk2 only? I think this is some kind of configuration error... It will also work if you set it to disk2, at least in theory, because this is the real path, maybe some files are moved over to disk1 and that's why it's segfaulilng.

Bitte die Diagnostics posten.

It is always recommended to stay on the latest version from unRAID, you always have to think about the security perspective too!

To what path did you set it? Do you set it to /mnt/user/...?

This is really interesting, have you installed a Cache drive? Can you please post your Diagnostics? Have you changed anything in the template in terms of the path?

Mach einen neuen Port im Template der ca. so aussieht: Danach kannst du dich mit so ziemlich jedem beliebigen VNC Client, wie in diesem Beispiel, auf Port 5990 verbinden. Vergiss aber bitte nicht das der Host Port immer ein anderer sein muss und der Continer Port muss immer 5900 sein, nur so als Zusatzinfo ich verwende in diesem Beispiel 5990 und das hat genau den Grund weil auch unRAID für die VNC Verbindung zu den VMs Ports 5900 und so weiter verwendet und einen Konflikt zu vermeinden.

I also now tried it and it works flawlessly, here is the log output from a fresh downloaded copy from the CA App: arma3.log (running unRAID 6.10.0) Do you have a Cache drive installed? If yes, make sure that you've set the appdata share to use Cache "Only" or "Prefer" in the Share settings. Have you entered your Steam credentials and have the Authenticator enabled? If yes this might be the issue, I recommend you to create a dedicated account for the Arma 3 server where the Authenticator is disabled only for running that server (this is also recommended by Steam), the second account actually don't need to own the game but you this account has to have at least one game about $ 5,- to be fully activated. Maybe start over again by doing the following: Delete the container Delete the folder for arma3 from your appdata directory Pull a fresh copy from the CA App

Is CA Backup maybe the solution here in combination with luckyBackup or any other sync application for you other important data?

Can you please try to upgrade to 6.9.2, I think that should resolve the issue because the Valheim container got updated and it is related to the way older Kernel version from 6.8.2

Can you please verify that the card is working in another computer, also try to install the drivers for the card and put a 3D load on it for about 5 to 10 minutes and see if you got no artifacts. Usually this is caused when the card is defective but in your case this can also be an issue with the Passthrough itself but I would at least verify that it works in another computer (without the enclosure).

They do the same things and have both a "schedule" engine where DirSyncPro is a little more advanced in managing everything through the GUI but is more resource hungry when syncing lots of data (sometimes 5 to 6 GB) where luckyBackup is not that far in terms of managing "everything" through the GUI but is a lot more efficient, uses very little resources has built in SSH support for SFTP file transfers but also comes with some caveats when using the "schedule" engine (only console mode is working properly and you have to restart the container to see the last synchronizations in the logs from luckyBackup).

Ja genau, aber das ist eher mit vorsicht zu genießen da dies nicht auf jeder Distribution funktioniert soweit ich weiß, hier würde 'tail -f access.log' Beispielsweise angebrachter sein.