ich777

Exactly, it is as simple as @alturismo posted. Also remember you have to customize the ports in your container that you pass it through too.

This is not really a mod, this is a guide on how to set up the server AFAIK. Anyways, I think what you are after is the Mods and I would recommend to you that you start here: Click It is also as simple as the guide describes... Navigate to your appdata share and then in the appropriate sub directory that the tutorial mentions for Insurgency and create the files, this is even possible through SMB.

Modding is usually always up to the user and I only provide the basic functionality but I try to help where I can… Can you link me to this mod or where do you get it from? Do you maybe have also a link on how to install it?

I would recommend to put this lines in the go file after emhttp to enable P8 on boot: # Enable nvidia-persistenced nvidia-persistenced

Don't do that, I've gone through the code and this will even cause issues on your existing Debian mirror...

If it was a simple apt-mirror then the name would be APT-Mirror, I thought the name should imply that it is a Debian mirror. Yes, but it will take maybe some time because I have to deal with a lot of things in real life currently. Even if Ubuntu has the answer and is even more popular I prefer Debian over it all the time because I've had to deal with a lot of issues with Ubuntu and Debian just works and has the latest fixes too. But the distribution choice is always up to the individual user and preference.

Maybe you've edited the mirror.list and after that the cron job executed and the files for Ubuntu where fetched. Yes, that won't work, I've also said it the other way around, that you should add it to your existing Debian mirror container. Anyways, I've gone through the code and that isn't a good idea either because it won't show up in the web server but the data would be there. No, as said before this container is designed for Debian and not for Ubuntu. I have to create a new container to support Ubuntu properly, this won't work properly until it is customized for Ubuntu because I've designed this specific container (Debian-APT-Mirror) only for Debian.

Have you had maybe a left over debian mirror in the mirrors list by accident? Well, because as the name implies (and also the icon for the container) it's a Debian mirror and was never designed for another distribution, however if I think again about it, have you already tried to add a Ubuntu mirror in your Debian container mirror.list? This could actually work because then the debian folder is found and the ubuntu folder should be created along side with the debian folder in one directory, this shouldn't cause any issues whatsoever. Yes and no, you have to modify the mirror.list file and the paths a bit, not sure if this can work. I'm currently not at the PC so that I can look into this...

And this is where the issue starts, I‘m searching for „debian“ and not for „Ubuntu“, maybe when I got time I can create a second container which is compatible with Ubuntu if that would be a possible solution for you…

I don't think that's an issue with the PCIe card in any way, this seems like a pure hardware combination issue or at least that something is wrong with the BIOS because it can't allocate/find the address in RAM for the device. Are you really sure that this won't solve the issue? I would at least try it, resizable BAR or even BAR support on most Gigabyte motherboards is a mess, at least from my personal experience with them... Have you yet tried to boot with Legacy (CSM) instead of UEFI? Sorry for the late response, I've somehow missed that comment, luckily I've seen it today...

This shouldn't be an issue because I'm using also http URLs for my Debian mirror. The size is pretty normal, depending on what you are mirroring... I'm almost at 3 TB... I think you should find them here: https://www.linuxtechi.com/setup-local-apt-repository-server-ubuntu/ The issue is that I search for a "debian" directory as the mirror directory because it's mainly a debian and not a ubuntu mirror... Anyways, this is really strange because it was never designed to be a Ubuntu mirror in any way, can you give me the file structure of the mirror directory please?

Click on the container icon and click on Console, that's basically the terminal from the container.

Kannst du in der syslinux.config machen mit: pcie_aspm=force EDIT: Ich hab vergessen dazuzuschreiben das dieser Befehl mit Vorsicht zu genießen ist da du evtl. so dein System zerschießt und das System nicht sauber booted bzw. hängen bleibt falls du Geräte hast die ASPM nicht unterstützen (muss aber nicht sein), du müsstest dann den Eintrag manuell vom USB Stick entfernen. bzw. du kannst den aktuellen Status auslesen mit: cat /sys/module/pcie_aspm/parameters/policy sollte der Output dann so aussehen ca: [default] performance powersave powersupersave (in dem fall ist "default" aktiv) Wenn du umschalten willst kannst du zB: echo 'powersave' > /sys/module/pcie_aspm/parameters/policy machen und dann nochmal mit: cat /sys/module/pcie_aspm/parameters/policy überprüfen ob er übernommen wurde.

Warum? Das macht doch keinen Sinn eine ältere Version sprich 2.8 zu nehemn statt 2.15, wobei ich sagen muss das 2.15 eigentlich ohne Probleme laufen sollte wobei 2.8 schon Probleme machen kann unter den neueren Unraid versionen bzw. dann gar nicht funktioniert. Dein Problem liegt sicher nicht an PowerTop und @Towatai müsste mir das auch erklären warum er meint das PowerTop 2.8 besser funktioniert...

Please don‘t double posts!!! I‘m already responded in the ZFS Support Thread.

I/O wait üblicherweise, das wird in htop nicht angezeigt (was eigentlich überlichweise angezeigt werden sollte). Das auf dem Dashboard ist nur generell ein „Richtwert“ es kann auch zB passieren das wenn du Kerne isolierst das dort aktivität angezeigt wird obwohl dort gar nichts ist. Liegt daran wie sich das errechnet bzw. wie es ermittelt wird und ist stand der Dinge.

That's a thing that you have to ask on the PhotoPrism GitHub Issue tracker over here: Click or even better ask on the issue tracker from that repo that you've linked: Click The template that is available in the CA App is the official PhotoPrism container, I've only created it and I can nothing do about how it works. I don't think that the API for PhotoPrism is missing in the PhotoPrism container, otherwise PhotoPrism itself won't work... I don't know because I don't maintain this app, I would recommend that you ask by clicking the Support link from the container (which actually points also to a GitHub Issue tracker over here: Click)

Your ZFS plugin is not installed properly... Please run the following command from a Unraid terminal and then download the ZFS plugin again from the CA App: rm -rf /boot/config/plugins/unRAID6-ZFS

You don't need nvidia-persistenced strictly speaking, this is just to put it in a lower power state and is recommended by most users. Do you left the P2000 in your server or did you took it out? If you left it in your server it is also safe to leave nvidia-persistenced enabled.

This will do the job just fine: sed -i '/nvidia-persistenced/d' /boot/config/go Set the iGPU as primary graphics card. Yes. You can leave the other two variables NVIDIA_VISIBLE_DEVICES and NVIDIA_DRIVER_CAPABILITIES in, they don't do anything if you remove --runtime=nvidia But anyways, if you are having troubles I would recommend posting in the General forums about that since this has strictly speaking nothing to do with my plugin.

It is fairly simple... You can also get in the BIOS by using the dGPU... You have to try what GPU is activated but I think in your case it's the dGPU and you have to plug in the monitor to this GPU anyways... If you switch in the BIOS over to the iGPU as primary GPU you have to attach the HDMI monitor back to the iGPU, that's all.

First of all, if you want to switch then delete this line in your go file: nvidia-persistenced The next thing is that you have to set your iGPU as the primary display device otherwise it will be disable if you have a dGPU (like in your case the P2000) still in your system <- I see no Intel iGPU visible at your system devices and that's probably the reason.

Please post your Diagnostics.

Please open up a issue on GitHub for this if you really need it.

Please don't run it with that flag because the output (when you install gdb in the container) doesn't help anyone, at least over here, any further because it is meant to be sent to Valve for further help. I will look into that shortly and trying to fix the container.