ich777

Because on some systems it caused a Kernel Panic when I created the plugin but that should not happen anymore and that's why it's recommended to stop the Array first (you can actually cancel the Parity check if you get a crash). Nothing to worry about when the Array is Stopped.

Yes, this CPU isn't supported anymore because it's not capable of AVX IIRC or some other instruction set which is needed for the game to run. Someone else already reported the same with a similar CPU who also was not able to run the container (but I can not find the post).

Yes, you have to click test, if that went well you can enable the module on the plugin page.

Sure, I'll trigger the build, the updated drivers should be available in about 15 minutes, I'll update this post when it's done. The drivers are now updated for 6.12.5 @Niklas to install the new driver package remove the plugin, install it again from the CA App and reboot afterwards.

Ja mit dem SR-IOV plugin, mein Plugin aber bitte nehmen. Warum hast du überhaupt Python2 auf Unraid direkt installiert bzw. was hast du alles installiert von NerdTools (oder Pack)?

TBH I'm really not into server hardware anymore unless you have some crazy plans for the system. Most consumer hardware is more than enough for most users. Even for me, you can see my current system here where I compile all plugins, create my containers and so on (addon cards have changed a lot since this post): (it's in German but Google Translate will halb)

Ah, das hat dann vermutlich Squid hinzugefügt. GVT-g bzw. SR-IOV ist für vGPUs für VMs. Nein, bei beiden Plugins nicht, das kann immer auf dem Server bleiben. Das hier lesen: Dann brauchst du es gar nicht, nicht GVT-g und SR-IOV nicht. In welchem container, meistens reicht es die Device /dev/dri durchzureichen.

Danke für den Hinweis, war es aber nicht generell die 980er Serie von Samsung die geplagt war von diversen bugs usw? Ich bin mir auch nicht sicher ob das nicht was mit AMD zu tuhen hat, die hatten doch anfangs relativ große Probleme teilweise mit verschiedensten PCIe Geräten und hatten auch mal eine eher Fragliche implementierung in der Firmware (eine Zeit lang) weiß aber nicht ob das schon gefixt ist.

11th Gen CPUs is a bit of hit and miss since 11th Gen CPUs was the time where the transition from GVT-g to SR-IOV happend and some 11th Gen CPUs support GVT-g, some 11th Gen CPUs support SR-IOV and there are also reported 11th Gen CPUs out there which doesn't support GVT-g nor SR-IOV. Sorry but I don't think that's a good idea because GVT-g also depends on the implementation from the Motherboard manufacturer and if they did a really bad job GVT-g won't work at all (as reported a few times in this thread). I have also conflicting reports here in the thread about CPUs with the suffix U where on some systems it is working and on some it isn't and that's why GVT-g is a bit of hit and miss. I'll check back from time to time on the GVT-g GitHub but I find it really frustrating that no one is even able to tell what's supported and what not so I'm not really interested in changing that because as said above there are too many factors involved, I hope you understand that. (Please also don't forget that it mentions that only 5th to 10th Gen i-Core CPUs are supported and the same goes for the Server Platforms - but you are correct it isn't mentioned there)

Here you can get a full list of compatible generations: Click (this article is in German but Google translate might help ) You can also take a look here which chip uses which iGPU (but keep in mind that the iGPU generation is often not the same as the CPU generation) but as @alturismo said, not every iGPU supports GVT-g/SR-IOV. I took this text from the official Intel GitHub GVT-g documentation (btw, I don't think Intel does a particularly good job with their naming schemes).

Ich vermute du hast diesen Thread schon gelesen @Thomasm: Soweit ich sehe dürfte das ein Hardwarekompatibilitätsproblem sein. Gibt es für die 980er Pro den evtl. ein Firmware update das du irgendwo auf einem anderen Computer/Laptop durchfürhen kannst?

In what system do you try to run the game? Do you have any logs from the new installation? It is possible that your IP got banned from Steam because you‘ve entered Steam credentials. You have to wait a few hours to get unbanned.

Please remove the template alongside with the satisfactory directory which lives in your appdata, after that pull a fresh copy from the CA App and change nothing and wait for the download to finish, this should do the job just fine.

This is not the complete template. Where did you remove the credentials? Why is Validate installation on, please remove true. Delete the container and the directory for the container in your appdata directory and start over, without steam credentials. I would also recommend that you specify the real path instead of the FUSE file path (/mnt/user/...) to the directory where the game files are and make sure that the appdata directory stays on the cache and is not moved over to the Array.

Please remove your Steam credentials from the container template, these are only necessary when they are NOT in the show more settings section and marked with a red asterisk in my templates.

No worries, just wanted to create a quick response...

Because I've never intended to have that many containers/plugins... I got more and more containers over time and now I'm at the point where I have almost 200 apps in the CA App. TBH I also can't imagine creating almost 200 dedicated threads, this would be too much for me...

Maybe never but I'm really not too sure about that, I don't have hardware for that on hand so that I could help people, but as mentioned in the post that you've linked, I would like to give people the chance to still being able to use the plugin, that's why I maintain it now. That's why the support link points to this thread.

Please see the first recommended post on top of this thread.

Oh sorry, I didn't read through the whole message. You actually have to change the ports inside your config from the game itself too if you haven't done that already. The PZWiki has a guide for that over here, actually this is the line which is important for you: So to speak the ports in the .ini file have to reflect the ports that you specify in your template as container and host port. Yes. No, this was the case before version 41.77, mentioned here. This port is not needed anymore. Sorry, I also just saw that my documentation on the GitHub page was also outdated (just updated that), you just need: 16261-16262 UDP 27015 TCP (optional)

Sorry the ports you have in your compose files (the old ones) are the wrong ones, where do you get the compose file from? Please see the run example here.

Please read the second recommended post on top of this thread.

So is it working for you? I saw that you've quoted me but removed it.

Open up a Unraid termina and execute this: wget -O /tmp/lxc_container_template.xml https://github.com/ich777/unraid_lxc_amp/raw/main/lxc_container_template.xml Close the terminal Visit this site on your server: http://YOURSERVERIP/LXCAddTemplate (please change "YOURSERVERIP" to the actual IP from your server) Configure it to your preference Click Create Wait for the window to say DONE (this can take some time depending on your connection speed) Click on the container Icon and select WebUI

Your Kernel Module crashed while the plugin tried to enable it, however it seems related to a MACVLAN issue, please solve this issue first: Nov 26 20:49:30 Brotherman kernel: ------------[ cut here ]------------ Nov 26 20:49:30 Brotherman kernel: WARNING: CPU: 4 PID: 19190 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 26 20:49:30 Brotherman kernel: Modules linked in: wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha tun bluetooth ecdh_generic ecc veth macvlan xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ipmi_devintf nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi gpu_sched drm_buddy kvm_amd i2c_algo_bit drm_ttm_helper ttm drm_display_helper drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd wmi_bmof cryptd agpgart nvme rapl i2c_piix4 syscopyarea Nov 26 20:49:30 Brotherman kernel: i2c_core r8169 nvme_core sysfillrect ccp k10temp joydev sysimgblt ahci fb_sys_fops realtek libahci tpm_crb tpm_tis video tpm_tis_core wmi tpm backlight acpi_cpufreq button unix Nov 26 20:49:30 Brotherman kernel: CPU: 4 PID: 19190 Comm: kworker/u64:2 Tainted: P O 6.1.49-Unraid #1 Nov 26 20:49:30 Brotherman kernel: Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.60 02/07/2023 Nov 26 20:49:30 Brotherman kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Nov 26 20:49:30 Brotherman kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 26 20:49:30 Brotherman kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Nov 26 20:49:30 Brotherman kernel: RSP: 0018:ffffc900002acd98 EFLAGS: 00010202 Nov 26 20:49:30 Brotherman kernel: RAX: 0000000000000001 RBX: ffff88817b7fcf00 RCX: 614dcb50d5e59f96 Nov 26 20:49:30 Brotherman kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88817b7fcf00 Nov 26 20:49:30 Brotherman kernel: RBP: 0000000000000001 R08: 3807721c7df55c84 R09: 26b204f7336a83ad Nov 26 20:49:30 Brotherman kernel: R10: 808473b5991f4ea0 R11: ffffc900002acd60 R12: ffffffff82a11d00 Nov 26 20:49:30 Brotherman kernel: R13: 000000000003f226 R14: ffff888015853500 R15: 0000000000000000 Nov 26 20:49:30 Brotherman kernel: FS: 0000000000000000(0000) GS:ffff88842e100000(0000) knlGS:0000000000000000 Nov 26 20:49:30 Brotherman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 26 20:49:30 Brotherman kernel: CR2: 00007fffb1435084 CR3: 000000018251e000 CR4: 0000000000350ee0 Nov 26 20:49:30 Brotherman kernel: Call Trace: Nov 26 20:49:30 Brotherman kernel: <IRQ> Nov 26 20:49:30 Brotherman kernel: ? __warn+0xab/0x122 Nov 26 20:49:30 Brotherman kernel: ? report_bug+0x109/0x17e Nov 26 20:49:30 Brotherman kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 26 20:49:30 Brotherman kernel: ? handle_bug+0x41/0x6f Nov 26 20:49:30 Brotherman kernel: ? exc_invalid_op+0x13/0x60 Nov 26 20:49:30 Brotherman kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 26 20:49:30 Brotherman kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Nov 26 20:49:30 Brotherman kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Nov 26 20:49:30 Brotherman kernel: ? nf_nat_inet_fn+0x126/0x1a8 [nf_nat] Nov 26 20:49:30 Brotherman kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Nov 26 20:49:30 Brotherman kernel: nf_hook_slow+0x3d/0x96 Nov 26 20:49:30 Brotherman kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Nov 26 20:49:30 Brotherman kernel: NF_HOOK.constprop.0+0x79/0xd9 Nov 26 20:49:30 Brotherman kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Nov 26 20:49:30 Brotherman kernel: __netif_receive_skb_one_core+0x77/0x9c Nov 26 20:49:30 Brotherman kernel: process_backlog+0x8c/0x116 Nov 26 20:49:30 Brotherman kernel: __napi_poll.constprop.0+0x2b/0x124 Nov 26 20:49:30 Brotherman kernel: net_rx_action+0x159/0x24f Nov 26 20:49:30 Brotherman kernel: __do_softirq+0x129/0x288 Nov 26 20:49:30 Brotherman kernel: do_softirq+0x7f/0xab Nov 26 20:49:30 Brotherman kernel: </IRQ> Nov 26 20:49:30 Brotherman kernel: <TASK> Nov 26 20:49:30 Brotherman kernel: __local_bh_enable_ip+0x4c/0x6b Nov 26 20:49:30 Brotherman kernel: netif_rx+0x52/0x5a Nov 26 20:49:30 Brotherman kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Nov 26 20:49:30 Brotherman kernel: ? _raw_spin_unlock+0x14/0x29 Nov 26 20:49:30 Brotherman kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Nov 26 20:49:30 Brotherman kernel: process_one_work+0x1ab/0x295 Nov 26 20:49:30 Brotherman kernel: worker_thread+0x18b/0x244 Nov 26 20:49:30 Brotherman kernel: ? rescuer_thread+0x281/0x281 Nov 26 20:49:30 Brotherman kernel: kthread+0xe7/0xef Nov 26 20:49:30 Brotherman kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 26 20:49:30 Brotherman kernel: ret_from_fork+0x22/0x30 Nov 26 20:49:30 Brotherman kernel: </TASK> Nov 26 20:49:30 Brotherman kernel: ---[ end trace 0000000000000000 ]--- Please either disable the Bridge in your networks settings and make sure to select MACVLAN in the Docker Settings if you need MACVLAN or switch to IPVLAN in your Docker Settings. Please also remove this from your syslinux.config (click on the blue text Flash on your Main page): nomodeset since Unraid should try to enable the GPU first not the plugin.