ich777

Never heard of that I would recommend that you use something like a Transcend JetFlash 600 USB 2.0 After thinking again about it I think I had that issue oncex The user solved this by changing the USB Boot device IIRC and never had that issue again.

The GT 730 is only supported by the legacy Nvidia 470 series driver. For what do you want to use the card? This card isn‘t even capable of transcoding h265 I would recommend that upgrade to something like a NVIDIA T400, this card doesn‘t need external power, you can get it for about $120,- and it is low power, macimum TDP 35W

I've deprecated this game server because they've introduced a change in the executable so that it was broken.

I seems that it has issues pulling the .md5 file for this driver. What kind of USB Flash drive are you using? Have now tried it and it worked flawlessly: Yes, because it can't find the md5 file on reboot and thinks that the driver isn't valid and so it gets removed. You can circumvent that by simply placing the .md5 file in this directory and it should work that way too.

Something really strange is going on here and really can't tell what the cause of this issue is. Please try this: Remove the plugin Execute: rm -rf /boot/config/plugins/nvidia-driver* Reboot Try to install the plugin again from the CA App - of course wait for the plugin window to display the Done button Reboot again Pull the Diagnostics and post them here

Yes, but you have to reboot too to completely uninstall the plugin, this is also what the pop up tells you to when you remove it.

End firefox properly by not restarting the container, instead click on the menu button and click Exit or Close

Yes, I‘ll update it when I have a computer in reach.

Yes, give me a few hours and I will update the container. With the next update it is integrated.

@RasBe this is still experimental but should work: https://raw.githubusercontent.com/ich777/unraid-sound-driver/master/sound-driver.plg

Why would you do that on the server side… You have to do that on the client. If you have done this the admin commands should work correctly as long as you pass over the -console argument to the client.

Without anything I can't help. Can you please post your Diagnostics?

Ja, aber das ist dann doch sehr umständlich, wirklich umständlich.

Das ist aber ein Problem mit OSX weil OSX die hardware einfach anders handhabt bzw das eigentlich die Firmware macht, deswegen bin ich auch gegen die Virtualisierung von OSX bzw. das ist unter anderem ein Grund.

Das Plugin sollte einfach so funktionieren aber bitte bedenke das es vermutlich oft funktioniert aber dann möglicherweise doch den Server mal crashed weil es eben nur ein workaround ist und keine richtige Lösung des Problems.

Yes, this is the workaround, you can't always prevent it...

I would recommend that you report that to the developers from the module itself, maybe they know what the cause is here and can maybe fix this. There is also another way to hide this message from the syslog but I would rather recommend by reporting it first on their GitHub since this is the real solution to this. Anyways here is the GitHub Issue tracker and they respond usually really quick (within two days), you can of course mark me there by simply typing in '@ich777' (without quotes) so that I can see what the result of this is.

Good boot time… May I ask how often do you reboot your server? I reboot my server very little and even if I do so it is not of a huge deal because I know exactly how long it would take. No, not by default. Also please keep in mind that if you are creating such an image you with the drivers preloaded you should be on the version that you want to create a custom image, then you have to pull down the drivers, maybe some build dependencies, compile everything, pack the image again move it to your USB boot device (, hope everything went well so that your system is able to boot) and revoot afterwards. This process would take about 15 to 20 minutes (<- with recent hardware) depending on the speed of your server. Also keep in mind that the boot will also take longer, not that much longer as if you create a custom image but I think it will be around 20 to 30 seconds more, because the boot image is bogger and takes longer to load. Hope that makes all sense to you.

The driver is about 300MB in terms of size… I think one minute for a driver installation is not bad especially on Linux where you have usually have to reboot twice to install it if use the proprietary driver. Not really, the only way is to not install it. 😅 May I ask why?

This is nothing I can control and was discussed here often times for Valheim and also for V-Rising (both use Unity as the engine). Since these two games are extremely popular so many servers need to be advertised on the main server list that their servers can't keep up and list everything as it should be. You can test this also for yourself and this was confirmed by multiple people by restarting the container and wait a bit, go to the servers list and wait again for a bit until the servers are fetched and search for your server, if it isn't there exit the game entirely, start the game again and go to the servers list again and maybe it will pop up <- this is also an issue that is out of my control... Where does it say that in the description? It only says that you can multiple servers (better speaking game server containers) with only one SteamCMD directory.

This (Above 4G decoding) has nothing to do with the memory size from add on cards, this is only the address space that a add on card can use in RAM.

This is nothing to worry about and there is also nothing I can do about this message because this is caused by the game engine and this message is produced by most dedicated game servers. Do you have any issue with the container? As said above the container is working fine. EDIT: BTW the SteamAPI is definitely working because otherwise you won't find the game server in the Steam Server Browser what is definitely working. You can also install a CS:GO or CS:Source server and the message will be there too but you won't notice it because this message is in between many other lines, the line just pops into the eye because it's the last line that it is output in the Valheim log, where on other game servers as mentioned above this line is somewhere in between.

Please update the container and see if it is working, I have just pushed an update to it, please report back if it is working.

Sadly enough there is no other way currently, you can use this "workaround" or not...

I would rather call this workaround then a FIX since adding this: can lead to system instability, other weird behavior and can in certain cases damage your hardware. You can find a good write up about what this option does here: Click Please also keep in mind that this is only a friendly reminder and nothing that I want to criticize.