1812 Posted March 13, 2022 Share Posted March 13, 2022 On 3/12/2022 at 6:24 AM, ich777 said: Those two posts are now also deprecated because it's part of Unraid itself. the second will be listed as de[recated once the stable version comes out, thanks to you! 1 Quote Link to comment
dhstsw Posted March 13, 2022 Share Posted March 13, 2022 3 hours ago, ich777 said: But you don,t have to switch it, or why do you want to switch it? You can also buy a HDMI Dummy plug for the iGPU. The VM will start fine if you‘ve assigned the dGPU wirhout switching the HDMI cable. Yes, i know, but when/if i need to go to bios again i'll have to switch. Beside that, the idea is that with iGPU active it will work? Or is it for debugging? thanks. Quote Link to comment
ich777 Posted March 13, 2022 Author Share Posted March 13, 2022 7 minutes ago, dhstsw said: Yes, i know, but when/if i need to go to bios again i'll have to switch. Yes exactly, but keep in mind it is always recommended that you have one display output for the console for Unraid. 8 minutes ago, dhstsw said: Beside that, the idea is that with iGPU active it will work? Yes, exactly, it is always recommended to use a second GPU for the console output from Unraid and not to use the same card/GPU for console output and a VM because this can/will always cause some trouble. Quote Link to comment
dhstsw Posted March 13, 2022 Share Posted March 13, 2022 25 minutes ago, ich777 said: Yes exactly, but keep in mind it is always recommended that you have one display output for the console for Unraid. Yes, exactly, it is always recommended to use a second GPU for the console output from Unraid and not to use the same card/GPU for console output and a VM because this can/will always cause some trouble. So, i followed your instructions: enabled iGPU in bios and set it as primary video out. Before (when i did the report) i had Unraid freezing up as i tried to run a VM using the Radeon (AFTER another one was closed - basically, at every second VM using the radeon was started). With your solution (so far) this isn't anymore, but at the second (or third) instead i get this: So, again, it's basically unusable. Attacched, diagnostics for this setup. I'm going back to RC2 and with previous bios settings (iGPU disabled), since it was working absolutely fine, until anything comes up regarding this issue. Thanks. C. incubus-diagnostics-20220313-1844.zip Quote Link to comment
ich777 Posted March 13, 2022 Author Share Posted March 13, 2022 2 minutes ago, dhstsw said: I'm going back to RC2 and with previous bios settings (iGPU disabled), since it was working absolutely fine, until anything comes up regarding this issue. I would strongly recommend that you leave the iGPU enabled so that Unraid cannuse the iGPU for the console output. Quote Link to comment
Micro553 Posted March 15, 2022 Share Posted March 15, 2022 Did try to install Radeon Top and GPU statistics todag and missed the part about setting model vendor. So after deleing both apps from the usb im able to access the GUI again. The problem was that I could not access the webgui at all. Then I read the following from the text about the plugin "no editis to the 'go' file or creation of other files are necessary (please not that this plugin only enables the 'amdgpu' Kernel module and not the 'radeon' Kernel module)." so this got me thinking because I have this (have been there long time) in my syslinux append initrd=/bzroot video=efifb:off So how would I do to make this work? 1. Install GPU statistics 2. Install Radeon TOP 3 Remove enything from syslinux? 4. Chooce model vendor where? 5 Reboot server I have a AMD RX 6900 XT GPU passed to my win11 VM if that matters. Quote Link to comment
snidera Posted March 15, 2022 Share Posted March 15, 2022 I'm trying to use a RX460 that I had semi-working previously with a win10 VM. It had the reset bug & would not reboot without a power cycle. I grabbed a GT1030 & solved that problem. I have a fresh win10 VM running & updated via VNC. Added the GPU, mouse & keyboard after it was running & stable for a day or 2. It took a couple of tries & I'm not sure what I changed to make it work, but it is now working & will survive windows reboot with GPU. However, sometime between 4PM 3/14 & 11AM 3/15, the VM went into a 'paused' mode & will not resume. I have to force stop, then restart. No GPU, but it boots to windows via VNC. If I power cycle the server, it will come back up. I can't find the error in logs (but I'm not an expert by any means). This is my backup unraid server, the MB has always been a little wonky, the cache keep throwing UDMA errors. I will try a different port as time permits. Do you have any suggestions? Up to & including starting from scratch on this server, I'd rather not re-copy 7.5TB, but that's not out of the question. I've read this thread & googled 'reset bug' a lot (as well as in the past when I gave up grabbed an nVidia). The only thing I haven't figured out is how to use the iGPU as console. Monitor connected to GPU displays console during boot until the card is grabbed by VFIO. I've always had blank from iGPU when passing through anything. ich777, Thanks in advance for any support you can provide. Also, thanks for making this possible & relatively painless - it's really great work. backup-diagnostics-20220315-1137.zip Quote Link to comment
ich777 Posted March 15, 2022 Author Share Posted March 15, 2022 1 hour ago, Micro553 said: So how would I do to make this work? That's basically it. It may be possible that your card isn't fully supported fully if you are on 6.9.2 For what do you want to use the card? Can you post your Diagnostics? Quote Link to comment
ich777 Posted March 15, 2022 Author Share Posted March 15, 2022 1 hour ago, snidera said: I'm trying to use a RX460 that I had semi-working previously with a win10 VM. It had the reset bug & would not reboot without a power cycle. Also if you install the AMD Vendor Reset plugin? From what I see you are booting in Legacy (CSM) mode, that should be the common way. What machine type do you use for the VM? 1 hour ago, snidera said: It took a couple of tries & I'm not sure what I changed to make it work, but it is now working & will survive windows reboot with GPU. The AMD Vendor Reset plugin is more a workaround to a real solution, it can happen that on certain VM reboots the card doesn't reset quiet right... 1 hour ago, snidera said: However, sometime between 4PM 3/14 & 11AM 3/15, the VM went into a 'paused' mode & will not resume. Have you disabled Sleep and Hibernation in the Power settings from the VM? 1 hour ago, snidera said: This is my backup unraid server, the MB has always been a little wonky, the cache keep throwing UDMA errors. I will try a different port as time permits. UDMA errors often caused by the SATA cables itself or like you've mentioned by a faulty connector, as long as they don't go up further. 1 hour ago, snidera said: I've always had blank from iGPU when passing through anything. Maybe try to set the iGPU to the primary display in the BIOS and also pluging in a Monitor or a HDMI Dummy plug. Quote Link to comment
snidera Posted March 15, 2022 Share Posted March 15, 2022 2 hours ago, ich777 said: What machine type do you use for the VM? The AMD Vendor Reset plugin is more a workaround to a real solution, it can happen that on certain VM reboots the card doesn't reset quiet right... VM is Q35-6.1 If it resets 50% of reboots, I'm fine with that. Previously, I had downloaders & media library management on VM, so it was a pain to find out it had tried to update & been shut down for days due to no reboot. AMD Vendor Reset, Radeon Top, Intel GPU Top & Intel GVT-g are all installed. Plex docker can use iGPU to transcode. Quote Have you disabled Sleep and Hibernation in the Power settings from the VM? Yes, but it has still paused 1-2 times since. Quote UDMA errors often caused by the SATA cables itself or like you've mentioned by a faulty connector, as long as they don't go up further. Just after typing the previous, UnRaid stopped responding & I had to hard reset. I think the Sata3_0 port causing my issues with the cache & possibly the VM, crossing fingers. It is shared with a m.2 & this MB has always had some odd issues. I moved the cache to the last SATA port, other controller. We'll see Quote Maybe try to set the iGPU to the primary display in the BIOS and also pluging in a Monitor or a HDMI Dummy plug. I haven't tried with this hardware, but previously my other server would not put console on iGPU & let me pass through the RX460. If the parity check goes through tonight, I will test with another monitor 1 Quote Link to comment
Micro553 Posted March 16, 2022 Share Posted March 16, 2022 On 3/15/2022 at 6:12 PM, ich777 said: That's basically it. It may be possible that your card isn't fully supported fully if you are on 6.9.2 For what do you want to use the card? Can you post your Diagnostics? Here are my diagnostics from yesterday Thanks. unraid-diagnostics-20220315-1307.zip Quote Link to comment
ich777 Posted March 16, 2022 Author Share Posted March 16, 2022 12 minutes ago, Micro553 said: Here are my diagnostics from yesterday I think the amdgpu driver that is included with 6.9.2 is not fully compatible with your card: Mar 15 12:52:10 Unraid kernel: [drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported Mar 15 12:52:10 Unraid kernel: amdgpu 0000:11:00.0: amdgpu: amdgpu: finishing device. Mar 15 12:52:10 Unraid kernel: [drm] free PSP TMR buffer Mar 15 12:52:10 Unraid kernel: general protection fault, probably for non-canonical address 0x15ff006e69622e: 0000 [#1] SMP NOPTI Mar 15 12:52:10 Unraid kernel: CPU: 15 PID: 12870 Comm: daemon-init Not tainted 5.10.28-Unraid #1 Mar 15 12:52:10 Unraid kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 3604 04/14/2021 Mar 15 12:52:10 Unraid kernel: RIP: 0010:do_raw_spin_lock+0x7/0x12 Mar 15 12:52:10 Unraid kernel: Code: c3 b8 00 fe ff ff f0 0f c1 07 c3 31 c0 48 81 ff 68 d3 6b 81 72 0c 31 c0 48 81 ff 10 d5 6b 81 0f 92 c0 c3 31 c0 ba 01 00 00 00 <f0> 0f b1 17 74 04 89 c6 eb bb c3 8b 07 45 31 c0 85 c0 75 11 ba 01 Mar 15 12:52:10 Unraid kernel: RSP: 0018:ffffc90000d1bd08 EFLAGS: 00010246 Mar 15 12:52:10 Unraid kernel: RAX: 0000000000000000 RBX: ffff88813d000000 RCX: 0000000080800079 Mar 15 12:52:10 Unraid kernel: RDX: 0000000000000001 RSI: 0000000000210d00 RDI: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: RBP: ffff88810213c640 R08: 0000000000000001 R09: ffffffffa04287ce Mar 15 12:52:10 Unraid kernel: R10: ffffea0004d43f00 R11: ffff88810213c620 R12: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: R13: ffff88813d016d28 R14: 000000000000000c R15: ffff888166f39210 Mar 15 12:52:10 Unraid kernel: FS: 000014a602632700(0000) GS:ffff888feebc0000(0000) knlGS:0000000000000000 Mar 15 12:52:10 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 15 12:52:10 Unraid kernel: CR2: 0000153c1c73c000 CR3: 000000016c886000 CR4: 0000000000750ee0 Mar 15 12:52:10 Unraid kernel: PKRU: 55555554 Mar 15 12:52:10 Unraid kernel: Call Trace: Mar 15 12:52:10 Unraid kernel: free_fw_priv+0x12/0x91 Mar 15 12:52:10 Unraid kernel: release_firmware+0x49/0x4b Mar 15 12:52:10 Unraid kernel: psp_sw_fini+0x6e/0x9c [amdgpu] Mar 15 12:52:10 Unraid kernel: amdgpu_device_fini+0x285/0x43c [amdgpu] Mar 15 12:52:10 Unraid kernel: amdgpu_pci_remove+0x31/0x47 [amdgpu] Mar 15 12:52:10 Unraid kernel: pci_device_remove+0x36/0x8e Mar 15 12:52:10 Unraid kernel: device_release_driver_internal+0xed/0x194 Mar 15 12:52:10 Unraid kernel: unbind_store+0x51/0x6f Mar 15 12:52:10 Unraid kernel: kernfs_fop_write_iter+0x10f/0x152 Mar 15 12:52:10 Unraid kernel: new_sync_write+0x7a/0xb2 Mar 15 12:52:10 Unraid kernel: vfs_write+0xd7/0x121 Mar 15 12:52:10 Unraid kernel: ksys_write+0x71/0xba Mar 15 12:52:10 Unraid kernel: do_syscall_64+0x5d/0x6a Mar 15 12:52:10 Unraid kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 15 12:52:10 Unraid kernel: RIP: 0033:0x14a609f6848f Mar 15 12:52:10 Unraid kernel: Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 49 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 7c fd ff ff 48 Mar 15 12:52:10 Unraid kernel: RSP: 002b:000014a602631590 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Mar 15 12:52:10 Unraid kernel: RAX: ffffffffffffffda RBX: 000000000000000c RCX: 000014a609f6848f Mar 15 12:52:10 Unraid kernel: RDX: 000000000000000c RSI: 000014a5c005fe20 RDI: 000000000000001b Mar 15 12:52:10 Unraid kernel: RBP: 000014a5c005fe20 R08: 0000000000000000 R09: 0000000000000000 Mar 15 12:52:10 Unraid kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000001b Mar 15 12:52:10 Unraid kernel: R13: 000000000000001b R14: 0000000000000000 R15: 000014a5c011fd00 Mar 15 12:52:10 Unraid kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod amdgpu gpu_sched drm_kms_helper ttm drm backlight agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel igb aesni_intel crypto_simd wmi_bmof i2c_piix4 cryptd ahci i2c_algo_bit mxm_wmi i2c_core libahci glue_helper ch341 usbserial cdc_acm ccp rapl k10temp wmi button acpi_cpufreq nvme nvme_core Mar 15 12:52:10 Unraid kernel: ---[ end trace 6a4dd67cf38c3cbb ]--- Mar 15 12:52:10 Unraid kernel: RIP: 0010:do_raw_spin_lock+0x7/0x12 Mar 15 12:52:10 Unraid kernel: Code: c3 b8 00 fe ff ff f0 0f c1 07 c3 31 c0 48 81 ff 68 d3 6b 81 72 0c 31 c0 48 81 ff 10 d5 6b 81 0f 92 c0 c3 31 c0 ba 01 00 00 00 <f0> 0f b1 17 74 04 89 c6 eb bb c3 8b 07 45 31 c0 85 c0 75 11 ba 01 Mar 15 12:52:10 Unraid kernel: RSP: 0018:ffffc90000d1bd08 EFLAGS: 00010246 Mar 15 12:52:10 Unraid kernel: RAX: 0000000000000000 RBX: ffff88813d000000 RCX: 0000000080800079 Mar 15 12:52:10 Unraid kernel: RDX: 0000000000000001 RSI: 0000000000210d00 RDI: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: RBP: ffff88810213c640 R08: 0000000000000001 R09: ffffffffa04287ce Mar 15 12:52:10 Unraid kernel: R10: ffffea0004d43f00 R11: ffff88810213c620 R12: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: R13: ffff88813d016d28 R14: 000000000000000c R15: ffff888166f39210 Mar 15 12:52:10 Unraid kernel: FS: 000014a602632700(0000) GS:ffff888feebc0000(0000) knlGS:0000000000000000 Mar 15 12:52:10 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 15 12:52:10 Unraid kernel: CR2: 0000153c1c73c000 CR3: 000000016c886000 CR4: 0000000000750ee0 Mar 15 12:52:10 Unraid kernel: PKRU: 55555554 The driver was basically loaded but after a while you got a module error and it got unloaded. You can try a RC version from Unraid but no guarantee that it works... Quote Link to comment
Micro553 Posted March 16, 2022 Share Posted March 16, 2022 29 minutes ago, ich777 said: I think the amdgpu driver that is included with 6.9.2 is not fully compatible with your card: Mar 15 12:52:10 Unraid kernel: [drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported Mar 15 12:52:10 Unraid kernel: amdgpu 0000:11:00.0: amdgpu: amdgpu: finishing device. Mar 15 12:52:10 Unraid kernel: [drm] free PSP TMR buffer Mar 15 12:52:10 Unraid kernel: general protection fault, probably for non-canonical address 0x15ff006e69622e: 0000 [#1] SMP NOPTI Mar 15 12:52:10 Unraid kernel: CPU: 15 PID: 12870 Comm: daemon-init Not tainted 5.10.28-Unraid #1 Mar 15 12:52:10 Unraid kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 3604 04/14/2021 Mar 15 12:52:10 Unraid kernel: RIP: 0010:do_raw_spin_lock+0x7/0x12 Mar 15 12:52:10 Unraid kernel: Code: c3 b8 00 fe ff ff f0 0f c1 07 c3 31 c0 48 81 ff 68 d3 6b 81 72 0c 31 c0 48 81 ff 10 d5 6b 81 0f 92 c0 c3 31 c0 ba 01 00 00 00 <f0> 0f b1 17 74 04 89 c6 eb bb c3 8b 07 45 31 c0 85 c0 75 11 ba 01 Mar 15 12:52:10 Unraid kernel: RSP: 0018:ffffc90000d1bd08 EFLAGS: 00010246 Mar 15 12:52:10 Unraid kernel: RAX: 0000000000000000 RBX: ffff88813d000000 RCX: 0000000080800079 Mar 15 12:52:10 Unraid kernel: RDX: 0000000000000001 RSI: 0000000000210d00 RDI: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: RBP: ffff88810213c640 R08: 0000000000000001 R09: ffffffffa04287ce Mar 15 12:52:10 Unraid kernel: R10: ffffea0004d43f00 R11: ffff88810213c620 R12: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: R13: ffff88813d016d28 R14: 000000000000000c R15: ffff888166f39210 Mar 15 12:52:10 Unraid kernel: FS: 000014a602632700(0000) GS:ffff888feebc0000(0000) knlGS:0000000000000000 Mar 15 12:52:10 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 15 12:52:10 Unraid kernel: CR2: 0000153c1c73c000 CR3: 000000016c886000 CR4: 0000000000750ee0 Mar 15 12:52:10 Unraid kernel: PKRU: 55555554 Mar 15 12:52:10 Unraid kernel: Call Trace: Mar 15 12:52:10 Unraid kernel: free_fw_priv+0x12/0x91 Mar 15 12:52:10 Unraid kernel: release_firmware+0x49/0x4b Mar 15 12:52:10 Unraid kernel: psp_sw_fini+0x6e/0x9c [amdgpu] Mar 15 12:52:10 Unraid kernel: amdgpu_device_fini+0x285/0x43c [amdgpu] Mar 15 12:52:10 Unraid kernel: amdgpu_pci_remove+0x31/0x47 [amdgpu] Mar 15 12:52:10 Unraid kernel: pci_device_remove+0x36/0x8e Mar 15 12:52:10 Unraid kernel: device_release_driver_internal+0xed/0x194 Mar 15 12:52:10 Unraid kernel: unbind_store+0x51/0x6f Mar 15 12:52:10 Unraid kernel: kernfs_fop_write_iter+0x10f/0x152 Mar 15 12:52:10 Unraid kernel: new_sync_write+0x7a/0xb2 Mar 15 12:52:10 Unraid kernel: vfs_write+0xd7/0x121 Mar 15 12:52:10 Unraid kernel: ksys_write+0x71/0xba Mar 15 12:52:10 Unraid kernel: do_syscall_64+0x5d/0x6a Mar 15 12:52:10 Unraid kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 15 12:52:10 Unraid kernel: RIP: 0033:0x14a609f6848f Mar 15 12:52:10 Unraid kernel: Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 49 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 7c fd ff ff 48 Mar 15 12:52:10 Unraid kernel: RSP: 002b:000014a602631590 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Mar 15 12:52:10 Unraid kernel: RAX: ffffffffffffffda RBX: 000000000000000c RCX: 000014a609f6848f Mar 15 12:52:10 Unraid kernel: RDX: 000000000000000c RSI: 000014a5c005fe20 RDI: 000000000000001b Mar 15 12:52:10 Unraid kernel: RBP: 000014a5c005fe20 R08: 0000000000000000 R09: 0000000000000000 Mar 15 12:52:10 Unraid kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000001b Mar 15 12:52:10 Unraid kernel: R13: 000000000000001b R14: 0000000000000000 R15: 000014a5c011fd00 Mar 15 12:52:10 Unraid kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod amdgpu gpu_sched drm_kms_helper ttm drm backlight agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel igb aesni_intel crypto_simd wmi_bmof i2c_piix4 cryptd ahci i2c_algo_bit mxm_wmi i2c_core libahci glue_helper ch341 usbserial cdc_acm ccp rapl k10temp wmi button acpi_cpufreq nvme nvme_core Mar 15 12:52:10 Unraid kernel: ---[ end trace 6a4dd67cf38c3cbb ]--- Mar 15 12:52:10 Unraid kernel: RIP: 0010:do_raw_spin_lock+0x7/0x12 Mar 15 12:52:10 Unraid kernel: Code: c3 b8 00 fe ff ff f0 0f c1 07 c3 31 c0 48 81 ff 68 d3 6b 81 72 0c 31 c0 48 81 ff 10 d5 6b 81 0f 92 c0 c3 31 c0 ba 01 00 00 00 <f0> 0f b1 17 74 04 89 c6 eb bb c3 8b 07 45 31 c0 85 c0 75 11 ba 01 Mar 15 12:52:10 Unraid kernel: RSP: 0018:ffffc90000d1bd08 EFLAGS: 00010246 Mar 15 12:52:10 Unraid kernel: RAX: 0000000000000000 RBX: ffff88813d000000 RCX: 0000000080800079 Mar 15 12:52:10 Unraid kernel: RDX: 0000000000000001 RSI: 0000000000210d00 RDI: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: RBP: ffff88810213c640 R08: 0000000000000001 R09: ffffffffa04287ce Mar 15 12:52:10 Unraid kernel: R10: ffffea0004d43f00 R11: ffff88810213c620 R12: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: R13: ffff88813d016d28 R14: 000000000000000c R15: ffff888166f39210 Mar 15 12:52:10 Unraid kernel: FS: 000014a602632700(0000) GS:ffff888feebc0000(0000) knlGS:0000000000000000 Mar 15 12:52:10 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 15 12:52:10 Unraid kernel: CR2: 0000153c1c73c000 CR3: 000000016c886000 CR4: 0000000000750ee0 Mar 15 12:52:10 Unraid kernel: PKRU: 55555554 The driver was basically loaded but after a while you got a module error and it got unloaded. You can try a RC version from Unraid but no guarantee that it works... Thanks. I’m having some issues with my win11 vm and my Amd adrenaline software / driver. Basically I’m on a version that does not allow u to check updates from the gui. So in hope to fix this I have tried a lot of adrenaline versions. Even Amd cleanup tool BUT every time when the “checking your graphics hardaware screen” comes up it freezes the server. Sometimes it reboots just the VM sometimes it reboots the whole server. I’m now running a memtest but doubt that is the problem. you say that my driver gets loaded and then unloaded. Could that be the cause for my problem with not being able to update my Amd adrenaline software and drivers? So maybe newest RC will help me? Quote Link to comment
ich777 Posted March 16, 2022 Author Share Posted March 16, 2022 2 hours ago, Micro553 said: you say that my driver gets loaded and then unloaded. Could that be the cause for my problem with not being able to update my Amd adrenaline software and drivers? You have Windows 11 installed on 6.9.2? Do you have a modified version from Windows without TPM? TPM support was first built into Unraid with 6.10.0-RC2 Do you want to use the card in a VM? If yes I would strongly recommend that you bind it to VFIO. The driver from Unraid has nothing to do with Windows, keep in mind that no driver should be loaded on the Host when you try to use the card in a Guest system. Also if you want to use the card mainly in a VM this questions would be better suited in the VM subforums. Quote Link to comment
Micro553 Posted March 17, 2022 Share Posted March 17, 2022 9 hours ago, ich777 said: You have Windows 11 installed on 6.9.2? Do you have a modified version from Windows without TPM? TPM support was first built into Unraid with 6.10.0-RC2 Do you want to use the card in a VM? If yes I would strongly recommend that you bind it to VFIO. The driver from Unraid has nothing to do with Windows, keep in mind that no driver should be loaded on the Host when you try to use the card in a Guest system. Also if you want to use the card mainly in a VM this questions would be better suited in the VM subforums. I have 6.9.2 yes. I did run the script thing to run win11 without TPM etc. I use and want to use the gpu in my win11 VM. Just to be clear. My win11 works but im unable to uninstall or install newer adrenaline softeware. Im not sure if I have bonded it to vfio. Will have to check. Now I’m running memtest and it looks good so far. my plan is to update to rc3 and then boot VM without gpu and try to uninstall the current adrenaline. Then pass the gpu and see if newest version will install. thabks for all help. so if I understand - I can’t run your plugin and a vm at the same time with the same gpu? Quote Link to comment
ich777 Posted March 17, 2022 Author Share Posted March 17, 2022 13 minutes ago, Micro553 said: I did run the script thing to run win11 without TPM etc. 13 minutes ago, Micro553 said: my plan is to update to rc3 and then boot VM You know that since Unraid 6.10.0-rc2 TPM is supported and emulated? You can also change your existing VM to use the built in TPM function in Unraid (as long as you are using as BIOS type OVMF): Click 18 minutes ago, Micro553 said: so if I understand - I can’t run your plugin and a vm at the same time with the same gpu? Exactly, you can use the GPU only in a VM (Guest) or on Unraid (Host). I would recommend that you are bind the card to VFIO in your System Devices page, reboot and try it again. If you have any further questions I would recommend that you post in the VM subforums since these are VM related questions. Quote Link to comment
dhstsw Posted March 17, 2022 Share Posted March 17, 2022 2 hours ago, Micro553 said: my plan is to update to rc3 and then boot VM without gpu and try to uninstall the current adrenaline. Then pass the gpu and see if newest version will install. On my system it works flawlessy with RC2 but not with RC3. Also, you can't install adrenaline without the Radeon GPU passed to the VM (adrenaline installer will complain that there's no radeon card in the system). C. Quote Link to comment
ich777 Posted March 17, 2022 Author Share Posted March 17, 2022 8 minutes ago, dhstsw said: Also, you can't install adrenaline without the Radeon GPU passed to the VM (adrenaline installer will complain that there's no radeon card in the system). But what's the benefit if you do so? Installing a driver for a non "installed" card? Quote Link to comment
dhstsw Posted March 17, 2022 Share Posted March 17, 2022 1 hour ago, ich777 said: But what's the benefit if you do so? Installing a driver for a non "installed" card? He wants to try to install them without the card because he can't with the card (card no recognized). His idea is to install it without the card and THEN install the card (and, as said, it won't work). 1 Quote Link to comment
snidera Posted March 17, 2022 Share Posted March 17, 2022 6 hours ago, ich777 said: 6 hours ago, Micro553 said: so if I understand - I can’t run your plugin and a vm at the same time with the same gpu? Exactly, you can use the GPU only in a VM (Guest) or on Unraid (Host). I would recommend that you are bind the card to VFIO in your System Devices page, reboot and try it again. Please clarify: Is it suggested to *not* have "AMD Vendor Reset" and "Radeon Top" plugins installed together for a GPU that will be passed through to VM? I realize Radeon Top isn't needed, but will it cause issues once VFIO grabs the GPU? Quote Link to comment
ich777 Posted March 17, 2022 Author Share Posted March 17, 2022 44 minutes ago, snidera said: Please clarify If you've bound your card to VFIO grabs the "card" early in the boot process and Radeon TOP isn't even able to see it. There could be some issues when you don't bind the card to VFIO. Keep in mind newer Unraid version (currently the RC versions and 6.10.0+) will load the driver anyways regardless if Radeon TOP is installed or not. So I would highly recommend to bind the card to VFIO if you want to use it in a VM. However you can install both the AMD Vendor Reset plugin and Radeon TOP plugins together. For example if you bind one dGPU (like a 5600XT with the Reset Bug) to VIFO that you want to use in a VM and a iGPU (something like a 3400G) for the Unraid console output and for HW transcoding in Jellyfin or something similar, then it makes actually sense to install both plugins. If you only have one card and you plan only to use it in a VM then it doesn't make sense to me to install the Radeon TOP plugin, because it's for the Host (Unraid). Hope this makes sense to you. Quote Link to comment
Micro553 Posted March 17, 2022 Share Posted March 17, 2022 1 hour ago, ich777 said: If you've bound your card to VFIO grabs the "card" early in the boot process and Radeon TOP isn't even able to see it. There could be some issues when you don't bind the card to VFIO. Keep in mind newer Unraid version (currently the RC versions and 6.10.0+) will load the driver anyways regardless if Radeon TOP is installed or not. So I would highly recommend to bind the card to VFIO if you want to use it in a VM. However you can install both the AMD Vendor Reset plugin and Radeon TOP plugins together. For example if you bind one dGPU (like a 5600XT with the Reset Bug) to VIFO that you want to use in a VM and a iGPU (something like a 3400G) for the Unraid console output and for HW transcoding in Jellyfin or something similar, then it makes actually sense to install both plugins. If you only have one card and you plan only to use it in a VM then it doesn't make sense to me to install the Radeon TOP plugin, because it's for the Host (Unraid). Hope this makes sense to you. Hi. I did look and I have not bind the gpu and gpu audio in vfio. Will try that now to see if it helps. I just want to use my card in my win11 Vm. I have updated to RC3 and all works well as far as I can see. Except my problem with driver update. I have this in syslinux video=efifb:off is this not needed anymore? I did put it in a long time ago because I had trouble with my last gpu a Rx 5700 xt Quote Link to comment
ich777 Posted March 17, 2022 Author Share Posted March 17, 2022 15 minutes ago, Micro553 said: I have this in syslinux video=efifb:off is this not needed anymore? I did put it in a long time ago because I had trouble with my last gpu a Rx 5700 xt These are all questions for the VM sub forums… TBH I really can‘t give much help for VMs because I really don‘t know much about it since I‘m running not a single VM with a GPU passed trough, the poeple over in the VMs sub forums have more knwledge about that. Quote Link to comment
Micro553 Posted March 17, 2022 Share Posted March 17, 2022 19 minutes ago, ich777 said: These are all questions for the VM sub forums… TBH I really can‘t give much help for VMs because I really don‘t know much about it since I‘m running not a single VM with a GPU passed trough, the poeple over in the VMs sub forums have more knwledge about that. I understand and I’m sorry to be in the wrong place. I will post in vm part. Thanks for the help with everything. Have a good one! 1 Quote Link to comment
Hanzzen Posted March 20, 2022 Share Posted March 20, 2022 Anyone got the vendor reset plugin working with RC4 yet? It stopped working on RC3 for me. Upgraded to RC4 today and still facing the same issue. I get the same "Unknown PCI Header Type '127' for device" error as @dhstsw if I try to start up a VM after powering it of. Doing a reboot just makes it stuck on the Tiano Core splash screen. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.