Trouble with PCIe USB controller


Recommended Posts

I'm been wrestling with getting my new Ryzen server trying to get VMs working. I have a two-part issue.

 

1. I'm having an issue passing through my USB controller "Fresco Logic". When starting my Windows 10 vm, I receive the "Execution error" attached. How do I ungroup the controller from iommu group 13 (see attached)? The vfio APP does not appear in my APPs to separate iommu groups. 

 

20200710_130128.jpg20200710_163036.jpg

20200710_130230.jpg

 

 

2. When I unplug the USB controller I am able to start my Windows 10 VM passing through my Nvidia 770 using a vbios which I downloaded from techpowerup.com. I made sure it was from the same exact gpu and removed the header using a hex editor per Spaceinvader One's instructions. When I boot I get the following graphic glitch with a Windows crash screen. Is this a vbios issue or something else? Thanks

 

 

20200630_160119.jpg

20200630_160127.jpg

tower-diagnostics-20200710-1601.zip

Edited by bubbleman441
Link to comment

To pass through any pcie device, like the USB adapter, it must either be in its on iommu group, or you must pass through all the devices in the group.

 

its not clear what you mean when you say Vito manager is not in your apps. Did you install it from community applications?

 

wed need to see your iommu groupings to help  on this, but you should certainly see if there are iommu settings in your bios, and investigate acs override settings in unRAID.

 

for the GPU issue, it’s unclear what machine type and bios you have set for the vm. If you don’t pass a gpu rom file, what happens?

Link to comment
1 minute ago, meep said:

Choose one of the options, reboot and see what impact it has on your setup. We cannot tell you which to chose as the result will be different for various motherboards.

Ok I will give that a try. As for the GPU ROM BIOS, I tried to boot the VM without it and it runs with nothing on the screen. I'm very confused and ready to return my new hardware.

Link to comment
1 minute ago, bubbleman441 said:

Ok I will give that a try. As for the GPU ROM BIOS, I tried to boot the VM without it and it runs with nothing on the screen. I'm very confused and ready to return my new hardware.

A little perseverance and you’ll overcome these issues. Once you develop an understanding of what’s going on, you’ll be spinning up VMs like a pro.

 

for gpu issue, what is the machine type and bios you have configured for the vm? Seabios usually works best for gpu passthroug, and switching between q35 and i440 machine types often solves a lot of problems.

Link to comment

I appreciate your help. I had my VMs up and running on my Intel build but it's been a struggle since upgrading to my Ryzen 3700x chipset. 

 

1. I changed the ACS override to Override and it didn't help I'll keep going down the list.

 

2. I booted with VNC and I'm having the same issue booting. I switched back to my old hardware last week and this Windows 10 VM started fine. Here are some of the VM settings:

 Machine: i440fx-5.0

BIOS: OVMF (This is greyed out. Could it be something I need to change with in my chipset bios?)

 

Link to comment

You cannot change  the bios for an existing vm. You need to create a new vm with the changed settings. Since you have the same boot issue in vnc, that rules out the gpu as the source of the problem. It’s very difficult to read the specific windows error your encountering,, but if this runs on different hardware, it’s likely something to do with part of your vm config that’s specific to your old system.

 

starting fresh with a new vm on this new hardware should point you in the right direction.

 

for iommu, have you checked your system bios to be sure there’s no configuration there that you need to turn on to enable iommu?

 

 

 

Link to comment
19 minutes ago, meep said:

You cannot change  the bios for an existing vm. You need to create a new vm with the changed settings. Since you have the same boot issue in vnc, that rules out the gpu as the source of the problem. It’s very difficult to read the specific windows error your encountering,, but if this runs on different hardware, it’s likely something to do with part of your vm config that’s specific to your old system.

 

starting fresh with a new vm on this new hardware should point you in the right direction.

 

for iommu, have you checked your system bios to be sure there’s no configuration there that you need to turn on to enable iommu?

 

 

 

First off, thanks so much for helping! I solved the iommu grouping by setting ACS Override to Multi-function.

 

I created a new VM for Win 10 and tried SeaBIOS.. I'm booted with i440fx-5.0 and SeaBios and got the following screen. I'm not sure what needs to change for SeaBIOS to work.

20200710_173458.jpg

Link to comment
7 hours ago, meep said:

Great news on the iommu groups!

 

You don’t have an os install image defined.

 

as you are setting up the vm afresh, you need to point to an install iso to get the os installed

 

 

I pointed the VM to the Win iso and it just gives me the Windows blue screen "Your PC ran into a problem and needs to restart. We'll restart for you." It's a constant loop. I've tried using both Q35 and i440.

 

On second glance, my GPU VGA and audio are in two separate IOMMU groups. They need to be in the same group correct?

 

Also my Fresco Logic USB controller says "This controller is bound to vfio, connected USB devices are not visible." I tested my Linux VM and the mouse and keyboard won't work plugged into this usb controller. I guess I don't really understand the vfio thing.

 

IOMMU group 0:[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 1:[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 2:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 3:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 4:[1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 5:[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 6:[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 7:[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 8:[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 9:[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 10:[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 11:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)

[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)

IOMMU group 12:[1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0

[1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1

[1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2

[1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3

[1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4

[1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5

[1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6

[1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7

IOMMU group 13:[1022:43ee] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43ee

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller

Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

Bus 001 Device 005: ID 0781:556b SanDisk Corp. Cruzer Edge

Bus 001 Device 006: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub

Bus 001 Device 007: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse

Bus 001 Device 008: ID 04d9:a1df Holtek Semiconductor, Inc.

Bus 001 Device 009: ID 046d:0821 Logitech, Inc. HD Webcam C910

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

IOMMU group 14:[1022:43eb] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43eb

[1:0:0:0] disk ATA ST4000VN008-2DR1 SC60 /dev/sdb 4.00TB

[2:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sdc 250GB

[3:0:0:0] disk ATA ST4000VN008-2DR1 SC60 /dev/sdd 4.00TB

[4:0:0:0] disk ATA ST4000VN008-2DR1 SC60 /dev/sde 4.00TB

[6:0:0:0] disk ATA Samsung SSD 860 2B6Q /dev/sdf 500GB

IOMMU group 15:[1022:43e9] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43e9

IOMMU group 16:[1022:43ea] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea

IOMMU group 17:[1022:43ea] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea

IOMMU group 18:[1022:43ea] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea

IOMMU group 19:[1022:43ea] 02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea

IOMMU group 20:[1b73:1100] 05:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)

This controller is bound to vfio, connected USB devices are not visible.

IOMMU group 21:[8086:15f3] 06:00.0 Ethernet controller: Intel Corporation Intel(R) Ethernet Controller I225-V (rev 02)

IOMMU group 22:[10de:1184] 07:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 770] (rev a1)

IOMMU group 23:[10de:0e0a] 07:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)

IOMMU group 24:[1022:148a] 08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

IOMMU group 25:[1022:1485] 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

IOMMU group 26:[1022:1486] 09:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP

IOMMU group 27:[1022:149c] 09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

IOMMU group 28:[1022:1487] 09:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

Edited by bubbleman441
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.