Jump to content
You are a guest user Click to join the site

Recommended Posts

If any of you have time and desire to read I have explained here what I understood about my USB controllers and how they are managed by Proxmox. I hope for an answer that will enlighten us in understanding some small parts that are missing to have a more capillary control over the Proxmox / OSX coupling

 

https://forum.proxmox.com/threads/trx40-amd-usb-controllers-question.70504/

Share this post


Link to post
Share on other sites

 

 

This is my last schema.

I can pass more stuff but all usb in my motherboard are owned by 46:00 controller...ah also audio is in there
VM OS system limit USB3 detection (High Sierra)

Catalina and Windows 64 have a better USB management (their drivers allow to see USB 3 devices if connected .

So to a clean installation in my MSI TRX40 Pro 10G I do not use any FLR patch (no need to passthrough 23:00.3, 4:00.3 USB Controllers or 23:00.4 audio controller

it is also mandatory to pass 4:00.3 and 23:00.3 (FLR Patch 148c)  (do not pass 23:00:4 audio controller)

All I need is 46:00, 4:00.3 and 23:00.3 controllers which I can passthrough in two different way:

Hostpci5: 46:00

or

hostpci6: 46:00.1

hostpci7: 46:00.3

then

hostpci7: 04:00.3

hostpci7: 23:00.3

 

 

schema_MB.jpg.c69df875ef58b440caf0197c7ac1c744.jpg

 

I think also for you should be the same (you have also to find your main USB controller and your exact groups).

Interesting is also to check this schematic picture, inside USB/audio/chipset connections with AMD CPU:

 1649437803_Schermata2020-05-29alle3_49_03PM.png.eb5cd242273387382028afec35592323.png

 

 

 

  • Like 1

Share this post


Link to post
Share on other sites
13 hours ago, iGPU said:

In follow up, I transferred the 3970X to a new MSI Creator. Things looked really good (although, this is my first MSI product and BIOS rather different than ASUS and GB and ASRock). But after 30 min, the same error codes began. Exact same error codes and then it crashed.

 

So I have a bad CPU. Interestingly, it started out okay, but then gradually got worse and worse. Fortunately, I had 3 days left to do an exchange, so I'll get a replacement 3970X next week.

 

I am wondering if you have a heat problem with your CPU. My cooler is the Thermaltake Floe Riing 360 TR4, which has issues, especially if you are not running windows. Their software that controls fan speed only runs when Windows is running (and not REAL TIME). You can tell if this is the issue if the FAN speed stays constant. You should hear the FAN speed going up and down as you do different things. My solution was to rewire the fans so that the motherboard controls the fan speed. I still used the Thermaltake controller for powering the  LEDs and for visualizing the fan speed when running windows. BE SURE TO CUT THE BLUE WIRE (PWM) GOING TO THE CONTROLLER!!!! 

We want the motherboard to control the PWM signal. I apologize for my very rough drawings.

 

Floe Connector.png

Floe Wiring.png

  • Like 1

Share this post


Link to post
Share on other sites

I came across some interesting stuff on USB ports / mapping for different TRX40 boards, maybe something we can use for our USB challenges: https://forums.unraid.net/topic/85811-trx40-motherboards/

 

Also, I can confirm that IF I pass any of the two (or both) USB controllers (47:00.0 / 47:00.1 / 47:00.3) my system will freeze after shutdown in MacOS and then restarting the VM (even with the GPU reset hook script)

 

I have now removed the passthrough of the USB controllers completely (only use the USB-C rear) and everything works prefect. Also the GPU reset script now works fine so stop-start VM works fine.

 

Screenshot 2020-05-29 at 16.54.19.png

Edited by Rox67er
Added screenshot of VM config
  • +1 1

Share this post


Link to post
Share on other sites

I've been running UnRAID (not a successful macOS VM, but I can run a Win10 VM). If I study the log files, all looks good until the end of the log (see spoiler; only shows ~ last 5% of the log). UnRAID is being run from a different drive (a smaller 256GB NVMe; UnRAID boots from a USB stick, so the combo is used). This eliminates a concern I had regarding the Samsung SSD SATA drive used to store Proxmox. The drive is most likely just fine.

 

Basically, the UnRAID log shows the same error at the same CPU positions: 17 and 49. This suggests that Linux is picking up on a consistent error at a consistent location within the CPU.

 

UnRAID, unlike Windows 10 which I ran as bare metal, crashed. So same behavior with Linux-based UnRAID and Proxmox.

 

WIndows 10 does not report, to my knowledge, any CPU anomalies. I've checked GPU-Z in Windows and it seems to report all is okay.

 

So two Linux systems report CPU problems; one crashes. It seems there is a problem with the CPU.

 

Spoiler

May 29 07:37:17 Tower webGUI: Successful login user root from 192.168.1.55
May 29 07:41:40 Tower kernel: mce: [Hardware Error]: Machine check events logged
May 29 07:41:40 Tower kernel: [Hardware Error]: Corrected error, no action required.
May 29 07:41:40 Tower kernel: [Hardware Error]: CPU:49 (17:31:0) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000030151
May 29 07:41:40 Tower kernel: [Hardware Error]: Error Addr: 0x0000003f3e8fe820
May 29 07:41:40 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000001a030202
May 29 07:41:40 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 3
May 29 07:41:40 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC data array parity.
May 29 07:41:40 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD
May 29 07:41:40 Tower kernel: mce: [Hardware Error]: Machine check events logged
May 29 07:41:40 Tower kernel: [Hardware Error]: Corrected error, no action required.
May 29 07:41:40 Tower kernel: [Hardware Error]: CPU:17 (17:31:0) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000030151
May 29 07:41:40 Tower kernel: [Hardware Error]: Error Addr: 0x0000003f3eab3820
May 29 07:41:40 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000001a030202
May 29 07:41:40 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 3
May 29 07:41:40 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC data array parity.
May 29 07:41:40 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD
May 29 07:41:43 Tower ntpd[3237]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
May 29 07:47:08 Tower kernel: mce: [Hardware Error]: Machine check events logged
May 29 07:47:08 Tower kernel: [Hardware Error]: Corrected error, no action required.
May 29 07:47:08 Tower kernel: [Hardware Error]: CPU:49 (17:31:0) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000030151
May 29 07:47:08 Tower kernel: [Hardware Error]: Error Addr: 0x00000000054f4820
May 29 07:47:08 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000001a030202
May 29 07:47:08 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 3
May 29 07:47:08 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC data array parity.
May 29 07:47:08 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD
May 29 07:47:08 Tower kernel: mce: [Hardware Error]: Machine check events logged
May 29 07:47:08 Tower kernel: [Hardware Error]: Corrected error, no action required.
May 29 07:47:08 Tower kernel: [Hardware Error]: CPU:17 (17:31:0) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000030151
May 29 07:47:08 Tower kernel: [Hardware Error]: Error Addr: 0x0000000005018820
May 29 07:47:08 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000001a030302
May 29 07:47:08 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 3
May 29 07:47:08 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC data array parity.
May 29 07:47:08 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD
May 29 07:52:36 Tower kernel: mce: [Hardware Error]: Machine check events logged
May 29 07:52:36 Tower kernel: [Hardware Error]: Corrected error, no action required.
May 29 07:52:36 Tower kernel: [Hardware Error]: CPU:17 (17:31:0) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000030151
May 29 07:52:36 Tower kernel: [Hardware Error]: Error Addr: 0x00000000054bb820
May 29 07:52:36 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000001a030302
May 29 07:52:36 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 3
May 29 07:52:36 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC data array parity.
May 29 07:52:36 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD
May 29 07:52:36 Tower kernel: mce: [Hardware Error]: Machine check events logged
May 29 07:52:36 Tower kernel: [Hardware Error]: Corrected error, no action required.
May 29 07:52:36 Tower kernel: [Hardware Error]: CPU:49 (17:31:0) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000030151
May 29 07:52:36 Tower kernel: [Hardware Error]: Error Addr: 0x00000000054f4820
May 29 07:52:36 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000001a030302
May 29 07:52:36 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 3
May 29 07:52:36 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC data array parity.
May 29 07:52:36 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD

 

 

Edited by iGPU
Both UnRAID and Proxmox crash.
  • Sad 1

Share this post


Link to post
Share on other sites
8 hours ago, fabiosun said:

@cj750 welcome here

I will happy you also partecipate with your point of view. It is interesting to see also newbie (in this task) experience..because maybe we are doing the same errors 🙂

If you have time put your rig in signature so we can see better motherboard and cpu you use 🙂

Thank you

 

Hello Fabiosun,


I cant say i started yet, but I'm about too. It's really Rox67er who pushed me down this path. Well i cant say pushed but I followed. Now I'm sitting back and learning and reading. Soon I will be more evolved in this project. Once I understand more about Prox/OSX.  So i can add my ups and downs. But i don't want to clutter this forum with useless information until I have something useful to add. Everyone keep up the good work. This USB issue is very important to me. Because I will be using my Dangerous Music Convert-2 thru USB also for the uplink feature. But i know soon all of you will out smart this USB pass thru issue.

 

O and thank you for using english in this area.   I used google translate to read the other posts. Which was enjoyable. But I appreciate  you having an english area. Since it my first language.

 

ci sentiamo

Share this post


Link to post
Share on other sites
2 hours ago, Rox67er said:

I can confirm that IF I pass any of the two (or both) USB controllers (47:00.0 / 47:00.1 / 47:00.3) my system will freeze after shutdown in MacOS and then restarting the VM (even with the GPU reset hook script)

 

I have now removed the passthrough of the USB controllers completely (only use the USB-C rear) and everything works prefect. Also the GPU reset script now works fine so stop-start VM works fine.

 

I suspected that I might have to do this the other day when talking to Pavo. But after talking, I decided first to get the rear ASMedia USB controller passed through on 44:00 so I was able to use the rear 3.2 gen 2 port - couldn't use it before I passed it which is strange. So are you saying if you remove ALL USB controllers that the rear 3.2 gen 2 USB C connector works without passthrough? Ive actually ordered a Qnap TR4 NAS/Singles USB-C 3.2 gen 1box to stick my spinners in, which is 10Gbs. They also have this https://www.qnap.com/en-uk/product/tl-d800c coming out imminently giving support for USB 3.2 gen 2x2 speeds (20Gbs 8 drive box).

 

So I might try and go back and un-passthrough the USB controllers/ports in my current config. And use the rear USB C too.

Also I've got plenty of USB-C multi-port adapters from my MBP lappie so all is cool.

Good confirmation, thanks Rox67er.

Edited by Driftwood

Share this post


Link to post
Share on other sites
2 hours ago, iGPU said:

It seems there is a problem with the CPU

You obviously check you had the right amount of cpu thermal grease on it?

Edited by Driftwood

Share this post


Link to post
Share on other sites
2 hours ago, Rox67er said:

I came across some interesting stuff on USB ports / mapping for different TRX40 boards, maybe something we can use for our USB challenges: https://forums.unraid.net/topic/85811-trx40-motherboards/

 

Also, I can confirm that IF I pass any of the two (or both) USB controllers (47:00.0 / 47:00.1 / 47:00.3) my system will freeze after shutdown in MacOS and then restarting the VM (even with the GPU reset hook script)

 

I have now removed the passthrough of the USB controllers completely (only use the USB-C rear) and everything works prefect. Also the GPU reset script now works fine so stop-start VM works fine.

 

Screenshot 2020-05-29 at 16.54.19.png

 

Hi, maybe I am missing something...are you sure of this picture above?

In your pdf on your GitHub there are differences.. 🙂and as it is should not boot (gfx is not there)

with our trx40 is better to pass entire usb controllers and not single device..single device may loose many functionality

 

387289014_Schermata2020-05-29alle7_38_40PM.png.fe761cb8e19c37c793db08a98e896e6a.png

Share this post


Link to post
Share on other sites

@Rox67er The two ASRock Creator SATA controllers (8 x SATA3 6.0 Gb/s) which, out of the two FCH address - 48:00 & 49:00 - is the first four?

 

The reason I ask is I forget if you are booting proxmox from a SATA port or USB? 

 

I currently have Proxmox booting off SATA port 1 on a SSD.

 

 Im tempted to go USB (as @fabiosun has successfully done)  but would prefer to boot with SATA from inside the box like Im doing. I currently don't passthrough either of the SATA controllers. I don't mind losing half the controllers to proxmox ssd, but which controller is using which IDs? Is 48:00 ports 1 - 4 ? And 49:00 Ports 5 - 8?

 

I could do with using one of the controllers I guess.

 

ASRock TRX40 Creator Mobo.png

Edited by Driftwood

Share this post


Link to post
Share on other sites
3 hours ago, Rocket88 said:

 

I am wondering if you have a heat problem with your CPU. My cooler is the Thermaltake Floe Riing 360 TR4, which has issues, especially if you are not running windows. Their software that controls fan speed only runs when Windows is running (and not REAL TIME). You can tell if this is the issue if the FAN speed stays constant. You should hear the FAN speed going up and down as you do different things. My solution was to rewire the fans so that the motherboard controls the fan speed. I still used the Thermaltake controller for powering the  LEDs and for visualizing the fan speed when running windows. BE SURE TO CUT THE BLUE WIRE (PWM) GOING TO THE CONTROLLER!!!! 

We want the motherboard to control the PWM signal. I apologize for my very rough drawings.

 

 

 

Thanks but no heat problem. I've monitored  build initially in Windows and typical temps at idle are 35 to 40°C. I'm using (as in Signature), an Enermax Liqtch 360 which has a plate designed for Threadripper. They have a bad rep, so on purchase, I completely dismantled, flushed the radiator, smoothed the innards of the motor housing (due to burrs) and re-filled with anti-corrosion fluid.

 

Then I lapped the base of the copper plate as it was far from flat. It took me almost 90 min of wet-sanding to get it flat. So I think I have great heat transfer.

 

So my temps are really good. I've adjusted fans speeds in BIOS, which ramp up after 60°C. This gives me an audible indicator of temps. Everything goes to 100% (loud) above 85°C.

  • +1 1

Share this post


Link to post
Share on other sites

More on USB Mapping. UnRAID has a good tool (plugin) called VFIO-PCI CFG. When run, it isolates IOMMU groups and allows you to click on a given group to create a pass-through, then after saving the selections, it creates the pass-through file for you, which is then available after a re-boot.

 

VFIO Plugin

Spoiler

VFIO-CONF.jpg.2ae4bbb081297676cb7b3cc610473cdd.jpg

 

When I plug different devices into the MSI Creator mobo, I find there is a 'blending' of USB controllers. This may explain the erratic behavior based on what is passed.

 

The spoilers below allowed me to create the rear panel annotation at bottom. I think we're starting to see a pattern of what is passed. The audio USB connectors are Matisse USB from 48:00.x. But notice how, on my mobo, that 48:00.1 is shared with the USB-3 below the Aquantia port as well as those in the middle stack of USB ports.

 

Meanwhile, 48:00.3 is used for the internal USB-3 connectors (often for front panel use), along with supplying USB power for the BT (I swapped out the BT/Wifi module).

 

Surprisingly, the USB-C is ASMedia at 44:00.0, while the USB ports at the left (which I use for keyboard and mouse) come from 25:00.3.

 

To make things more confusing, if you look at the spoiler below, at Matisse at 48:00, you'll see there is a blending of ASMedia High Speed. (Highlighted green in spoiler for 48:00.1.) This mix appears associated with drives to 48:00.3 and the ASMedia port 44:00.0.

 

Bottom line for this mobo, is that to have full USB functionality, 25:00.3, 48:00.1, 48:00.3 and 44:00.0 must be passed. (I think 4:00.3 are the ports beneath I211, but I need to re-check this.)

 

Spoiler

4-00-3.jpg.de32d8f7bf82c0772a2718b3e8316596.jpg

 

25-00-3.jpg.494335b581270b885dfd5b07be03b2ec.jpg

 

44-00.jpg.f309af162f8bd9dffc5620ed7071cb41.jpg

 

48-00-1-1.jpg.a9db681ba82ca13016ae4a2056e21aa1.jpg

48-00-3.jpg.e8f3a30816b8d6e64d3712baf0bcfb05.jpg

 

MSI TRX40 Creator:

MSI-Creator-RearPanel-annotated.jpg.3363e3daca11d41c0337621f4b09285b.jpg

 

lspci -nnk

Spoiler

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
        Subsystem: Micro-Star International Co., Ltd. [MSI] FCH SMBus Controller [1462:7c59]
        Kernel driver in use: piix4_smbus
        Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
        Subsystem: Micro-Star International Co., Ltd. [MSI] FCH LPC Bridge [1462:7c59]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0 [1022:1490]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1 [1022:1491]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2 [1022:1492]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3 [1022:1493]
        Kernel driver in use: k10temp
        Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4 [1022:1494]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5 [1022:1495]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6 [1022:1496]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7 [1022:1497]
01:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01)
        Subsystem: Phison Electronics Corporation Device [1987:5016]
        Kernel driver in use: nvme
02:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
        Subsystem: Phison Electronics Corporation E12 NVMe Controller [1987:5012]
        Kernel driver in use: nvme
03:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
04:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c]
        Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c59]
        Kernel driver in use: xhci_hcd
20:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
20:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
20:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
20:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
20:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
20:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
21:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:14a0] (rev c1)
        Kernel driver in use: pcieport
22:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:14a1]
        Kernel driver in use: pcieport
23:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
23:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
24:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
25:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
25:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
        Kernel driver in use: ccp
        Kernel modules: ccp
25:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c]
        Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c59]
        Kernel driver in use: xhci_hcd
25:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]
        Subsystem: Micro-Star International Co., Ltd. [MSI] Starship/Matisse HD Audio Controller [1462:cb59]
        Kernel modules: snd_hda_intel
40:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
40:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
40:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
        Kernel driver in use: pcieport
40:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
40:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
40:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
41:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57ad]
        Kernel driver in use: pcieport
42:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a3]
        Kernel driver in use: pcieport
42:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4]
        Kernel driver in use: pcieport
42:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4]
        Kernel driver in use: pcieport
42:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4]
        Kernel driver in use: pcieport
43:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD [15b7:5002]
        Subsystem: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD [15b7:5002]
        Kernel driver in use: nvme
44:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242]
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7c59]
        Kernel driver in use: xhci_hcd
45:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02)
        Subsystem: Micro-Star International Co., Ltd. [MSI] AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1462:7c59]
        Kernel driver in use: atlantic
        Kernel modules: atlantic
46:00.0 Network controller [0280]: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
        Subsystem: Lenovo BCM4352 802.11ac Wireless Network Adapter [17aa:0623]
        Kernel driver in use: bcma-pci-bridge
        Kernel modules: bcma
47:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
        Subsystem: Micro-Star International Co., Ltd. [MSI] I211 Gigabit Network Connection [1462:7c59]
        Kernel driver in use: igb
        Kernel modules: igb
48:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
48:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486]
        Kernel driver in use: xhci_hcd
48:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c]
        Kernel driver in use: xhci_hcd
49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
        Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]
        Kernel driver in use: ahci
        Kernel modules: ahci
4a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
        Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]
        Kernel driver in use: ahci
        Kernel modules: ahci
4b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
4c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
60:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
60:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
60:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
60:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
60:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
        Kernel driver in use: pcieport
61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]

 

 

Edited by iGPU
Added -lspci -nnk

Share this post


Link to post
Share on other sites

@iGPU could you post lspci -nnk output of this msi board? I would like to check because iommu seems to be weird

 

Share this post


Link to post
Share on other sites
2 minutes ago, fabiosun said:

@iGPU could you post lspci -nnk output of this msi board? I would like to check because iommu seems to be weird

 

 

Done. I added to same post at bottom.

Share this post


Link to post
Share on other sites

Thanks @iGPU

it is similar to mine

04:00.3

25:00.3

could be passed with flr patch (148c)

48:00.1 and 48:00.3 pass as is without patch

44 is asmedia..i do not pass it because i have proxmox on it

i do not consider any additional device you can have but msi creator has pretty similar group

also @pavo has one and he is achieving the same my result

 

Share this post


Link to post
Share on other sites

On image you write asmedia 48:00.1 and this for me is not so

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.