How To Fix Akitio Node Lite With Gtx 1050ti
@T0a Thank for the respond and your considerations, really appreciate that .
I start saying i'g not a super linux expert , i saw that, with lspci, if i disconnect the TB3 enclosure information technology even so showed while with proxmox it disappear, maybe there are different things under the hood, not only KVM related?
Considering i did the same things, passed the GPU on both system, merely UNRAID doesn't manage the plug&play feature, while proxmox it does the chore done quite well.
I saw that the the TB3 enclosure use also xhci_hcd driver, since it has 2 TB3 ports, and i don't know if that can conflict with the build in USB controller, that has some result, like can't use an external HDD sharing only the USB port, i have to share all the controller, but that has result also. This with USB from 00:14.0 USB controller.
I mitigate the problem, on proxmox, sharing the whole 08:00.0 id, using a usb-c to USB3 adapter and that's quite fine, this is my pci list:
root@proxmox:~# lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation eighth Gen Core Processor Host Bridge/DRAM Registers [8086:3ed0] (rev 08) Subsystem: Intel Corporation eighth Gen Core Processor Host Span/DRAM Registers [8086:2074] Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] Kernel driver in utilize: i915 Kernel modules: i915 00:08.0 Arrangement peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Cadre Processor Gaussian Mixture Model [8086:2074] 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Point-LP Thermal Controller [8086:9df9] (rev thirty) Subsystem: Intel Corporation Cannon Point-LP Thermal Controller [8086:2074] Kernel driver in apply: intel_pch_thermal Kernel modules: intel_pch_thermal 00:14.0 USB controller [0c03]: Intel Corporation Cannon Bespeak-LP USB 3.1 xHCI Controller [8086:9ded] (rev 30) Subsystem: Intel Corporation Cannon Betoken-LP USB 3.1 xHCI Controller [8086:2074] Kernel driver in use: xhci_hcd 00:14.two RAM memory [0500]: Intel Corporation Cannon Indicate-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Intel Corporation Cannon Point-LP Shared SRAM [8086:2074] 00:14.3 Network controller [0280]: Intel Corporation Cannon Bespeak-LP CNVi [Wireless-AC] [8086:9df0] (rev thirty) Subsystem: Intel Corporation Cannon Signal-LP CNVi [Wireless-Air conditioning] [8086:0034] Kernel driver in employ: iwlwifi Kernel modules: iwlwifi 00:16.0 Communication controller [0780]: Intel Corporation Cannon Bespeak-LP MEI Controller [8086:9de0] (rev 30) Subsystem: Intel Corporation Cannon Signal-LP MEI Controller [8086:2074] Kernel driver in apply: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Cannon Point-LP SATA Controller [AHCI Way] [8086:9dd3] (rev 30) Subsystem: Intel Corporation Cannon Point-LP SATA Controller [AHCI Mode] [8086:2074] Kernel driver in apply: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Point-LP PCI Express Root Port [8086:9db8] (rev f0) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation Cannon Point-LP PCI Express Root Port [8086:9dbc] (rev f0) Kernel commuter in employ: pcieport 00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Signal-LP PCI Limited Root Port [8086:9db0] (rev f0) Kernel driver in use: pcieport 00:1d.6 PCI bridge [0604]: Intel Corporation Cannon Betoken-LP PCI Express Root Port [8086:9db6] (rev f0) Kernel commuter in use: pcieport 00:1f.0 ISA span [0601]: Intel Corporation Cannon Point-LP LPC Controller [8086:9d84] (rev thirty) Subsystem: Intel Corporation Cannon Point-LP LPC Controller [8086:2074] 00:1f.3 Audio device [0403]: Intel Corporation Cannon Point-LP High Definition Sound Controller [8086:9dc8] (rev 30) Subsystem: Intel Corporation Cannon Point-LP High Definition Audio Controller [8086:2074] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci 00:1f.iv SMBus [0c05]: Intel Corporation Cannon Point-LP SMBus Controller [8086:9da3] (rev 30) Subsystem: Intel Corporation Cannon Point-LP SMBus Controller [8086:2074] Kernel commuter in use: i801_smbus Kernel modules: i2c_i801 00:1f.5 Series autobus controller [0c80]: Intel Corporation Cannon Betoken-LP SPI Controller [8086:9da4] (rev 30) Subsystem: Intel Corporation Cannon Signal-LP SPI Controller [8086:2074] 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (6) I219-V [8086:15be] (rev 30) Subsystem: Intel Corporation Ethernet Connection (6) I219-V [8086:2074] Kernel commuter in apply: e1000e Kernel modules: e1000e 02:00.0 PCI span [0604]: Intel Corporation JHL6340 Thunderbolt iii Bridge (C step) [Tall Ridge 2C 2016] [8086:15da] (rev 02) Kernel driver in use: pcieport 03:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt three Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev 02) Kernel driver in utilise: pcieport 03:01.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C pace) [Tall Ridge 2C 2016] [8086:15da] (rev 02) Kernel driver in employ: pcieport 03:02.0 PCI span [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev 02) Kernel driver in use: pcieport 04:00.0 System peripheral [0880]: Intel Corporation JHL6340 Thunderbolt 3 NHI (C pace) [Tall Ridge 2C 2016] [8086:15d9] (rev 02) Subsystem: Intel Corporation JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016] [8086:2074] Kernel commuter in use: thunderbolt Kernel modules: thunderbolt 05:00.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C footstep) [Tall Ridge 4C 2016] [8086:15d3] (rev 02) Kernel driver in apply: pcieport 06:01.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02) Kernel commuter in use: pcieport 06:04.0 PCI span [0604]: Intel Corporation JHL6540 Thunderbolt three Bridge (C stride) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02) Kernel driver in apply: pcieport 07:00.0 VGA uniform controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3746] Kernel driver in apply: vfio-pci Kernel modules: nvidiafb, nouveau 07:00.ane Audio device [0403]: NVIDIA Corporation GP107GL High Definition Audio Controller [10de:0fb9] (rev a1) Subsystem: Gigabyte Technology Co., Ltd GP107GL High Definition Audio Controller [1458:3746] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 08:00.0 USB controller [0c03]: Intel Corporation JHL6540 Thunderbolt iii USB Controller (C footstep) [Alpine Ridge 4C 2016] [8086:15d4] (rev 02) Subsystem: Akitio JHL6540 Thunderbolt three USB Controller (C step) [Tall Ridge 4C 2016] [1cf0:030d] Kernel driver in utilize: vfio-pci 6c:00.0 USB controller [0c03]: Intel Corporation JHL6340 Thunderbolt 3 USB iii.1 Controller (C pace) [Alpine Ridge 2C 2016] [8086:15db] (rev 02) Subsystem: Intel Corporation JHL6340 Thunderbolt 3 USB 3.one Controller (C step) [Alpine Ridge 2C 2016] [8086:2074] Kernel commuter in use: xhci_hcd 6d:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 [144d:a808] Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 [144d:a801] Kernel driver in use: nvme 6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Bill of fare Reader [10ec:522a] (rev 01) Subsystem: Intel Corporation RTS522A PCI Express Menu Reader [8086:2074] Kernel commuter in use: rtsx_pci Kernel modules: rtsx_pci
Returning to UNRAID :
16 hours ago, T0a said:
When yous kickoff the VM then, it will attempt to observe the device (which is turned off) and throw an error. I think this is expected behaviour.
When i start the VM the TB3 enclosure is ON and connected to the NUC. Mayhap i said something incorrect, my steps to produce the error is:
- kicking with TB3 on and connected to the NUC
- start Win10 VM
- finish Win10 VM
- disconnect TB3 cable from eGPU enclosure and NUC
- reconnect the TB3 cable ( same port on the enclosure )
- get-go Win10 VM: ERROR.
While with proxmox this is not happening, it starts fine again. Just i can't accost where the issue is located.
sixteen hours agone, T0a said:
Thunderbold back up tin can yet be considered as experimental in Unraid. Personally, I'thou likewise interested in eGPU support
eGPU works fine, for what i tested, equally before long as you don't disconnect the cablevision or turn off the power to the enclosure, and then you are messed
The only way to starting time the VM again with eGPU is to reboot the host.
16 hours ago, T0a said:
A solution might be passing through the Thunderbold controller to the the VM.
This could be a smashing solution, merely how to reach this?
Does information technology pass the GPU correctly then?
Is there a guide or something?
I didn't run into that ability when passing the devices to the VM, merely perchance i'thou blind😅
Another problem is: if i disconnect information technology, and the reconnect it...will UNRAID detect information technology again or i will end up with same effect?
For what i saw the probably answer for the last question will be yes, but if i notice how to pass the whole controller i tin can do a test without problems.
16 hours ago, T0a said:
You would be one of the start Unraid users experimenting with thunderbold passthrough.
That's interesting, and a bit scaring, i was thinking a NUC + eGPU was non a and then strange setup.
Edited by Malaga
How To Fix Akitio Node Lite With Gtx 1050ti,
Source: https://forums.unraid.net/topic/92522-thunderbolt-3-egpu-with-windows-10/
Posted by: jamesfiect1953.blogspot.com
0 Response to "How To Fix Akitio Node Lite With Gtx 1050ti"
Post a Comment