Jump to content

taotien

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by taotien

  1. 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.

  2. 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?

  3. 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]

    Quote

    solved by adding the following kernel boot parameter: xhci_hcd.quirks=270336 This activates the following quirks:

    XHCI_SPURIOUS_REBOOT

    XHCI_SPURIOUS_WAKEUP

     

    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


  4. 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~

  5. 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~

×
×
  • Create New...