ich777

@Nogami & @jeffreywhunter & @Per771 & @unRaiderX & @anthony0030 & @djtodd: I've rebuilt the driver once more, if you are already on the new beta please remove the plugin, install it again, select the 580.x driver version and reboot. If you are back on stable then please just upgrade and it should work right out of the box, granted you've selected driver version 580.x in the plugin.

Sorry but this was my mistake as I explained in this post: https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/226/#findComment-1616114 The existing driver will be kept if the 580.x driver version is selected but the driver was never compiled because Nvidia didn't update their documentation as explained above.

Just to double check, on your machine everything is working correct?

Can you please post Diagnostics? Cool, why wouldn't you post Diagnostics when you have issues? Is is pretty hard to troubleshoot if nothing is provided.

Sorry but please read the post one above your post. :D

Sorry for the inconvenience with the Nvidia Legacy Driver (580.x) and the new Unraid builds but it seems that Nvidia didn't update their page for the Legacy branch where the version numbers are pulled from and therefore the driver was never built for the new beta versions: However I've implemented a fix so that the correct driver versions are pulled now. The compilation just started and the drivers will be available in the next 30 minutes for the new Unraid beta, please switch the driver version manually if you are already affected from this (upgrades from this point on won't have that issue).

I think this is more of an issue with TVHeadend or the configuration since the card is detected and in a working state, otherwise it wouldn't be detected at all, however you can post your Diagnostics and I look through the files if there is something missing but even if there would be something missing the card wouldn't be detected usually. I also can't help with ISDB-T since we don't have that standard over here, however as said, it seems like some other configuration issue or an issue with TVHeadend.

No, that's not how it works. The plugin has a fallback in it's routine that if a 580.x driver is selected that it checks if a 580.x driver is available and downloads that driver. That should not happen, however what did your notifications say before you rebooted? Did you see the notifications, if yes which driver was downloaded? The notifications look something like this but in the case for the Nvidia driver it will actually show the version. That should be in there, however if the download was interrupted while upgrading the driver download to the latest version is always in place and will do it's job, do you have Diagnostics from where you upgraded? Before upgrade and after?

What driver is installed, please always post your Diagnostics so that I can see what's going on.

Not sure if that's so easy since every game or better speaking each container has it's own little modifications so that the games will properly run, so to speak you most certainly will need to create containers yourself since it is very unlikely you get dedicated servers running with the generic container.

No, please check your local credentials store for Docker, maybe you have set credentials or wrong credentials set: https://github.com/ich777/docker-steamcmd-server/pkgs/container/steamcmd/325499627?tag=projectzomboid There where already 9 downloads today.

I can't answer why, I didn't do it.

Sorry about that but as said, this seems like a hardware issue and nothing the driver can solve.

You can use both, both will work fine with your card.

Please always post your Diagnostics.

Yeah, a lot of things: Mar 28 02:37:29 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884) Mar 28 02:37:29 craZyTower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Mar 28 02:37:41 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884) Mar 28 02:37:41 craZyTower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Mar 28 02:38:09 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884) Mar 28 02:38:09 craZyTower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884) Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884) Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884) Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Mar 28 02:38:27 craZyTower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)Do you have somewhere a dashboard open or something that calls nvidia-smi repeatedly? However as said, this seems more like a hardware issue.

Try to remove it entirely for now and see if that helps. However please don't forget that hardware degrades over time and you actually have a Kernel Panic this time: Mar 27 21:51:34 craZyTower kernel: NVRM: GPU at PCI:0000:01:00: GPU-9b9953bb-c437-09fa-c7a0-cb535d0b6baa Mar 27 21:51:34 craZyTower kernel: NVRM: Xid (PCI:0000:01:00): 79, pid=369925, name=ffmpeg, GPU has fallen off the bus. Mar 27 21:51:34 craZyTower kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus. Mar 27 21:51:34 craZyTower kernel: NVRM: GPU0 GSP RPC buffer contains function 78 (DUMP_PROTOBUF_COMPONENT) sequence 314407 and data 0x0000000000000000 0x0000000000000000. Mar 27 21:51:34 craZyTower kernel: NVRM: GPU0 RPC history (CPU -> GSP): Mar 27 21:51:34 craZyTower kernel: NVRM: entry function sequence data0 data1 ts_start ts_end duration actively_polling Mar 27 21:51:34 craZyTower kernel: NVRM: 0 103 GSP_RM_ALLOC 314382 0x000000000000c7b5 0x0000000000000008 0x00064e008ab1e719 0x0000000000000000 y Mar 27 21:51:34 craZyTower kernel: NVRM: -1 103 GSP_RM_ALLOC 314381 0x000000000000c9c0 0x0000000000000010 0x00064e008ab1e5c9 0x00064e008ab1e6fe 309us Mar 27 21:51:34 craZyTower kernel: NVRM: -2 103 GSP_RM_ALLOC 314380 0x000000000000c56f 0x0000000000000170 0x00064e008ab1e3ea 0x00064e008ab1e5a8 446us Mar 27 21:51:34 craZyTower kernel: NVRM: -3 103 GSP_RM_ALLOC 314379 0x000000000000c7b5 0x0000000000000008 0x00064e008ab1e267 0x00064e008ab1e341 218us Mar 27 21:51:34 craZyTower kernel: NVRM: -4 103 GSP_RM_ALLOC 314378 0x000000000000c9c0 0x0000000000000010 0x00064e008ab1e10e 0x00064e008ab1e24c 318us Mar 27 21:51:34 craZyTower kernel: NVRM: -5 103 GSP_RM_ALLOC 314377 0x000000000000c56f 0x0000000000000170 0x00064e008ab1ded4 0x00064e008ab1e0e5 529us Mar 27 21:51:34 craZyTower kernel: NVRM: -6 103 GSP_RM_ALLOC 314376 0x000000000000c7b5 0x0000000000000008 0x00064e008ab1db4e 0x00064e008ab1dc2b 221us Mar 27 21:51:34 craZyTower kernel: NVRM: -7 103 GSP_RM_ALLOC 314375 0x000000000000c9c0 0x0000000000000010 0x00064e008ab1d9ea 0x00064e008ab1db28 318us Mar 27 21:51:34 craZyTower kernel: NVRM: GPU0 RPC event history (CPU <- GSP): Mar 27 21:51:34 craZyTower kernel: NVRM: entry function sequence data0 data1 ts_start ts_end duration during_incomplete_rpc Mar 27 21:51:34 craZyTower kernel: NVRM: 0 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e907f52 0x00064dff6e907f5b 9us Mar 27 21:51:34 craZyTower kernel: NVRM: -1 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e81385b 0x00064dff6e813864 9us Mar 27 21:51:34 craZyTower kernel: NVRM: -2 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e536981 0x00064dff6e53698a 9us Mar 27 21:51:34 craZyTower kernel: NVRM: -3 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e44219d 0x00064dff6e4421a6 9us Mar 27 21:51:34 craZyTower kernel: NVRM: -4 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e34da34 0x00064dff6e34da3d 9us Mar 27 21:51:34 craZyTower kernel: NVRM: -5 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e2592a2 0x00064dff6e2592ab 9us Mar 27 21:51:34 craZyTower kernel: NVRM: -6 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e164ae6 0x00064dff6e164aee 8us Mar 27 21:51:34 craZyTower kernel: NVRM: -7 4099 POST_EVENT 0 0x00000000000000a2 0x0000000000000000 0x00064dff6e0702d3 0x00064dff6e0702dc 9us Mar 27 21:51:34 craZyTower kernel: CPU: 7 UID: 99 PID: 369925 Comm: ffmpeg Tainted: P O 6.12.54-Unraid #1 Mar 27 21:51:34 craZyTower kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Mar 27 21:51:34 craZyTower kernel: Hardware name: System manufacturer System Product Name/Z170 PRO GAMING, BIOS 3805 05/16/2018 Mar 27 21:51:34 craZyTower kernel: Call Trace: Mar 27 21:51:34 craZyTower kernel: <TASK> Mar 27 21:51:34 craZyTower kernel: dump_stack_lvl+0x47/0x70 Mar 27 21:51:34 craZyTower kernel: _nv013654rm+0x81c/0xd20 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv013558rm+0xe5/0x880 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv051028rm+0x156/0x390 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv052169rm+0x424/0xab0 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv052167rm+0x264/0x4b0 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv050395rm+0x171/0x300 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv050396rm+0x5c/0x90 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv000593rm+0x6b/0x80 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? _nv000739rm+0xa36/0xd00 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? rm_ioctl+0x7f/0x400 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? nvidia_unlocked_ioctl+0x72e/0x7b0 [nvidia] Mar 27 21:51:34 craZyTower kernel: ? vfs_ioctl+0x20/0x40 Mar 27 21:51:34 craZyTower kernel: ? __do_sys_ioctl+0x53/0x70 Mar 27 21:51:34 craZyTower kernel: ? do_syscall_64+0x68/0xe0 Mar 27 21:51:34 craZyTower kernel: ? entry_SYSCALL_64_after_hwframe+0x76/0x7e Mar 27 21:51:34 craZyTower kernel: </TASK> Mar 27 21:51:34 craZyTower kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x2 (Node Reboot Required) Mar 27 21:51:34 craZyTower kernel: ------------[ cut here ]------------ Mar 27 21:51:34 craZyTower kernel: WARNING: CPU: 1 PID: 369926 at /tmp/makeself.9LJqJdNd/NVIDIA-Linux-x86_64-595.58.03/kernel/nvidia/nv.c:5250 nvidia_dev_put_uuid+0x33/0x50 [nvidia] Mar 27 21:51:34 craZyTower kernel: Modules linked in: nft_ct cmac cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver nft_masq nft_chain_nat algif_rng af_alg nvidia_uvm(PO) br_netfilter xt_nat nf_conntrack_netlink veth xfrm_user xfrm_algo xt_addrtype xt_connmark xt_conntrack ip6table_mangle iptable_mangle xt_MASQUERADE xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag i915 drm_buddy i2c_algo_bit drm_display_helper intel_gtt nct6775 nct6775_core hwmon_vid jc42 regmap_i2c ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel mei_pxp mei_hdcp nvidia(PO) kvm drm_ttm_helper crct10dif_pclmul crc32_pclmul ttm crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 drm_kms_helper aesni_intel crypto_simd cryptd rapl intel_cstate drm intel_uncore i2c_i801 Mar 27 21:51:34 craZyTower kernel: wmi_bmof mxm_wmi e1000e agpgart i2c_smbus mei_me mei i2c_core thermal fan video wmi backlight acpi_pad button Mar 27 21:51:34 craZyTower kernel: CPU: 1 UID: 99 PID: 369926 Comm: cuda00001400006 Tainted: P O 6.12.54-Unraid #1 Mar 27 21:51:34 craZyTower kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Mar 27 21:51:34 craZyTower kernel: Hardware name: System manufacturer System Product Name/Z170 PRO GAMING, BIOS 3805 05/16/2018 Mar 27 21:51:34 craZyTower kernel: RIP: 0010:nvidia_dev_put_uuid+0x33/0x50 [nvidia] Mar 27 21:51:34 craZyTower kernel: Code: 53 e8 01 c7 ff ff 48 85 c0 74 2f 48 89 c3 48 89 c7 48 89 ee e8 6e d7 ff ff 31 d2 48 89 de 48 89 ef e8 a1 9b c3 00 85 c0 74 02 <0f> 0b 48 8d bb b8 06 00 00 5b 5d e9 8d 99 5e e1 5b 5d c3 cc cc cc Mar 27 21:51:34 craZyTower kernel: RSP: 0018:ffffc900016dfbc8 EFLAGS: 00010202 Mar 27 21:51:34 craZyTower kernel: RAX: 0000000000000026 RBX: ffff88816ac18000 RCX: 0000000000000001 Mar 27 21:51:34 craZyTower kernel: RDX: 0000000000000000 RSI: 0000000000000246 RDI: ffffc900016dfaf8 Mar 27 21:51:34 craZyTower kernel: RBP: ffff88801e1cb000 R08: 0000000000000000 R09: 0000000000000000 Mar 27 21:51:34 craZyTower kernel: R10: ffffc900016dfb70 R11: 0000000000000080 R12: ffff8881786ea000 Mar 27 21:51:34 craZyTower kernel: R13: ffffc9000b38b078 R14: ffffc9000b38c0f0 R15: 0000000000000000 Mar 27 21:51:34 craZyTower kernel: FS: 0000000000000000(0000) GS:ffff888816c40000(0000) knlGS:0000000000000000 Mar 27 21:51:34 craZyTower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 27 21:51:34 craZyTower kernel: CR2: 00001551ac088000 CR3: 0000000005618004 CR4: 00000000003726f0 Mar 27 21:51:34 craZyTower kernel: Call Trace: Mar 27 21:51:34 craZyTower kernel: <TASK> Mar 27 21:51:34 craZyTower kernel: nvUvmInterfaceUnregisterGpu+0x28/0x30 [nvidia] Mar 27 21:51:34 craZyTower kernel: uvm_gpu_release_locked+0x27/0x40 [nvidia_uvm] Mar 27 21:51:34 craZyTower kernel: uvm_va_space_destroy+0x365/0x3c0 [nvidia_uvm] Mar 27 21:51:34 craZyTower kernel: uvm_release.isra.0+0x8d/0x140 [nvidia_uvm] Mar 27 21:51:34 craZyTower kernel: uvm_release_entry.part.0.isra.0+0x47/0x80 [nvidia_uvm] Mar 27 21:51:34 craZyTower kernel: ? task_work_run+0x68/0x80 Mar 27 21:51:34 craZyTower kernel: uvm_release_entry+0x21/0x30 [nvidia_uvm] Mar 27 21:51:34 craZyTower kernel: __fput+0x10a/0x1d0 Mar 27 21:51:34 craZyTower kernel: task_work_run+0x68/0x80 Mar 27 21:51:34 craZyTower kernel: do_exit+0x36f/0x8d0 Mar 27 21:51:34 craZyTower kernel: do_group_exit+0x79/0x80 Mar 27 21:51:34 craZyTower kernel: get_signal+0x617/0x660 Mar 27 21:51:34 craZyTower kernel: ? __seccomp_filter+0x85/0x370 Mar 27 21:51:34 craZyTower kernel: ? vfs_read+0x159/0x1c0 Mar 27 21:51:34 craZyTower kernel: arch_do_signal_or_restart+0x28/0x1d0 Mar 27 21:51:34 craZyTower kernel: syscall_exit_to_user_mode+0x4f/0x80 Mar 27 21:51:34 craZyTower kernel: do_syscall_64+0x82/0xe0 Mar 27 21:51:34 craZyTower kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Mar 27 21:51:34 craZyTower kernel: RIP: 0033:0x148092bea4fd Mar 27 21:51:34 craZyTower kernel: Code: Unable to access opcode bytes at 0x148092bea4d3. Mar 27 21:51:34 craZyTower kernel: RSP: 002b:0000148085a1a900 EFLAGS: 00000293 ORIG_RAX: 0000000000000007 Mar 27 21:51:34 craZyTower kernel: RAX: fffffffffffffdfc RBX: 0000000000000000 RCX: 0000148092bea4fd Mar 27 21:51:34 craZyTower kernel: RDX: 00000000ffffffff RSI: 0000000000000003 RDI: 000055d89b64ec00 Mar 27 21:51:34 craZyTower kernel: RBP: 0000148085a1a920 R08: 0000000000000000 R09: 0000000000000007 Mar 27 21:51:34 craZyTower kernel: R10: 000055d89b68cfe0 R11: 0000000000000293 R12: 0000000000000000 Mar 27 21:51:34 craZyTower kernel: R13: 000055d89b688180 R14: 000055d89b64ec00 R15: 000055d89b688040 Mar 27 21:51:34 craZyTower kernel: </TASK> Mar 27 21:51:34 craZyTower kernel: ---[ end trace 0000000000000000 ]--- Something is definitely crashing the driver.

You don't have to add anything if you post the Diagnostics, I see almost everything you have posted there, however you have an Xid error in your log: Mar 27 18:22:47 craZyTower kernel: NVRM: GPU at PCI:0000:01:00: GPU-9b9953bb-c437-09fa-c7a0-cb535d0b6baa Mar 27 18:22:47 craZyTower kernel: NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus. Mar 27 18:22:47 craZyTower kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus. Mar 27 18:22:47 craZyTower kernel: NVRM: A GPU crash dump has been created. If possible, please run Mar 27 18:22:47 craZyTower kernel: NVRM: nvidia-bug-report.sh as root to collect this data before Mar 27 18:22:47 craZyTower kernel: NVRM: the NVIDIA kernel module is unloaded. Mar 27 18:22:47 craZyTower kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required) You can see the full list of Xid errors here, you have #79 However this is a pretty bad issue to troubleshoot since it could be pretty much everything, however I would recommend that you do the following: Since you are on the latest BIOS version, try to reset your BIOS settings to defaults Try to connect a monitor and let it connected Try to add nvidia-persistenced at the very end to your go file

Do you have Diagnostics or anything after the GPU dropped? Without Diagnostics it's really hard to say anything. Most of the times it has to do with either a Power Supply which is not up to the task anymore or PCIe Bus issues or even BIOS settings set wrong, sometimes plugging in a Monitor or a HDMI Dummy plug helps and in some cases even PowerTop or Power Saving scripts are being to aggressive or enabling nvidia-persistenced.

@Putz.Jimmy please change the variable RUNTIME_NAME in your template to jre25 after that it should it download the new Java Version and be able to start. You'll find the Variable under the show more section in your Docker template.

Only Intel GPU TOP is supported by GPU Statistics and Intel GPU TOP doesn't support Battlemage IIRC. NVTOP doesn't support outputting values via json so therefore NVTOP is not supported in GPU Statistics, it's a CLI only tool for now.

I look into that ASAP.

I assume you are talking about Terraria? Please go to the template and look at the variable GAME_VERSION IIRC.

Maybe look into something newer like a Nvida T400 or similar since these cards are future proof, at least until Nvidia deprecates them again but I don't think that this will happen soon since this card for example is based on Turing.

No since the older drivers won't compile against newer Kernels and therefore you can't select an older driver, please also see the pinned post: https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/193/#findComment-1551263