taotien

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by taotien

  1. Yeah I have that disabled. I won't be able to turn on Wake-On-Lan otherwise.
  2. I might give up and disable Wake-on-Lan for now, as it's getting to be more trouble than it's worth.
  3. When I have time later I'll also try removing the card to isolate the issue to it in case it's the onboard controller that's causing issues. I will also try finding older versions of BIOS that will let me disable xHCI hand-off, but will that affect the Intel Management Engine compatibility?
  4. Thanks for the suggestions. How would I cut the hardware wakeup signal? The card is an Inateck KT4001 (Fresno Logic FL1100). Under device manager in W10 VM all of the USB controllers have the option to wake the system greyed out. The card's driver details says that PCI S0 Wakeup support is false. My guess was to try to unload the driver for the controller before shutdown, but I didn't know how to search for or go about doing that. Edit: Looks like xhci_hcd is built into the kernel so I can't unload it? But that wouldn't explain why only after running a VM does the issue come up. Installing the Inateck drivers didn't enable the option to wake the system with the card.
  5. This is driving me insane. With the kernel patch the system shuts down properly only if I don't start up any VM's (or at least my single Windows VM) while the system is on. Otherwise, the system boots immediately upon shutdown. Could this be because I have a USB3 addin card? Or is it caused by vfio or enabling pcid acs override downstream, multifunction?
  6. I've already updated to the latest BIOS, which I thought fixed my issue, but actually seemed fixed because I forgot to re-enable WOL. Booting straight into Windows doesn't exhibit the issue either. Also this looks to be an issue with Wake-on-LAN. [Archlinux Wiki: WOL Wake-up on shutdown] I dunno why this issue suddenly cropped up after so long without problems, but the kernel parameter fix helped. I will keep updating this thread if otherwise. Motherboard: ASUS PRIME Z370-A
  7. Guess something was borked in BIOS. Updated it and restored all my settings and it just fixed itself. Still don't understand what went wrong and why the issue was isolated to unRAID.
  8. Howdy, Recently I've been unable to shutdown unRAID without it starting right up again. I've fiddled with all my motherboard's power settings. After booting into my Windows drive natively I can shutdown just fine, so only unRAID has this problem right now. I'm about to try resetting my BIOS just in case there's still a problem there. What other info should I provide? Thanks a lot~
  9. Swapping to the USB 3.0 qemu XHCI emulated drivers fixed the issue for the KB. Will see if the audio is fixed later
  10. Ahh I see. I thought it was more straightforward than that. Would it help to have USB 3.0 selected in the configurator for better speeds on USB disks? Probably also why my USB DAC/amp crackles as well. Thanks for the tips.
  11. Just checking off the KB / using the Hotplug USB plugin. I don't have a usb card yet but I'm planning on one for my pile of usb devices.
  12. My keyboard and mouse lighting effects have a stuttering issue when passed through to my Windows VM (ie. it normally is a smooth 60hz, now it's 30~). I don't have a problem when I'm running Windows barebones. Sometimes my mouse also feels like it has difficulty tracking for a split second, but that may just be because I'm bad.
  13. Following this guide from Spaceinvader One: https://www.youtube.com/watch?v=UilWLtMYd-U&t=192s I passed through my motherboard's ASMedia USB controller to my Win10 VM. This leads to the VM being unable to boot. Normal boot gives this warning: vfio_err_notifier_handler(0000:05:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest But three of these errors show (two of them id 04:00.0) show when the controller is passed through. 05:00.0 is my GPU, 04:00.0 is the USB controller. Not even the UEFI/Tianocore logo is displayed, my monitor just says there is no signal. As for my devices, the controller is in its own IOMMU group: IOMMU group 16 [RESET] 04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller [1b21:2142] I have already added 1b21:2142 it to the vfio-pci.ids list. PCIe ACS Override is set to Both (for passing onboard audio, though I have yet to try just downstream/just multifunction). For some reason devices plugged into the USB ports of the ASMedia controller have also stopped showing up after stubbing it (I think, will update if that's not the case). Can anyone give some pointers as to what I've missed? Thank you and have a nice day~