MSI TRX40 PRO 10G - AMD 3970x

fabiosun

New Member
Mar 22, 2020
22
3
3
HI,
when I start latest Proxmox Ve I have a bunch of ACPI errors and before reaching shell cursor I have this:
9.849840] usb 7-5: cannot get Ctl value:reg = 0x83, wValue = 0xc00, wIndex = 0x1300, type = 4
9.849849] usb 7-5: cannot get min/max values for control 12 (id 19)
I have this problem with all available BIOS for my motherboard
If I disable HD Audio in bios section I have not this message above in the spoiler

/sys/kernel/iommu_groups/55/devices/0000:49:00.0
/sys/kernel/iommu_groups/17/devices/0000:04:00.3
/sys/kernel/iommu_groups/45/devices/0000:41:00.0
/sys/kernel/iommu_groups/35/devices/0000:40:01.1
/sys/kernel/iommu_groups/7/devices/0000:00:07.0
/sys/kernel/iommu_groups/63/devices/0000:60:07.0
/sys/kernel/iommu_groups/25/devices/0000:20:07.1
/sys/kernel/iommu_groups/53/devices/0000:44:00.0
/sys/kernel/iommu_groups/15/devices/0000:03:00.0
/sys/kernel/iommu_groups/43/devices/0000:40:08.0
/sys/kernel/iommu_groups/33/devices/0000:23:00.4
/sys/kernel/iommu_groups/5/devices/0000:00:04.0
/sys/kernel/iommu_groups/61/devices/0000:60:04.0
/sys/kernel/iommu_groups/23/devices/0000:20:05.0
/sys/kernel/iommu_groups/51/devices/0000:48:00.0
/sys/kernel/iommu_groups/51/devices/0000:42:0a.0
/sys/kernel/iommu_groups/13/devices/0000:01:00.0
/sys/kernel/iommu_groups/41/devices/0000:40:07.0
/sys/kernel/iommu_groups/31/devices/0000:23:00.1
/sys/kernel/iommu_groups/3/devices/0000:00:02.0
/sys/kernel/iommu_groups/21/devices/0000:20:03.1
/sys/kernel/iommu_groups/11/devices/0000:00:14.3
/sys/kernel/iommu_groups/11/devices/0000:00:14.0
/sys/kernel/iommu_groups/68/devices/0000:62:00.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.1
/sys/kernel/iommu_groups/58/devices/0000:60:01.0
/sys/kernel/iommu_groups/48/devices/0000:42:05.0
/sys/kernel/iommu_groups/38/devices/0000:40:03.0
/sys/kernel/iommu_groups/66/devices/0000:60:08.1
/sys/kernel/iommu_groups/28/devices/0000:21:00.1
/sys/kernel/iommu_groups/28/devices/0000:21:00.0
/sys/kernel/iommu_groups/56/devices/0000:4a:00.0
/sys/kernel/iommu_groups/18/devices/0000:20:01.0
/sys/kernel/iommu_groups/46/devices/0000:42:02.0
/sys/kernel/iommu_groups/36/devices/0000:40:01.3
/sys/kernel/iommu_groups/8/devices/0000:00:07.1
/sys/kernel/iommu_groups/64/devices/0000:60:07.1
/sys/kernel/iommu_groups/26/devices/0000:20:08.0
/sys/kernel/iommu_groups/54/devices/0000:45:00.0
/sys/kernel/iommu_groups/16/devices/0000:04:00.0
/sys/kernel/iommu_groups/44/devices/0000:40:08.1
/sys/kernel/iommu_groups/34/devices/0000:40:01.0
/sys/kernel/iommu_groups/6/devices/0000:00:05.0
/sys/kernel/iommu_groups/62/devices/0000:60:05.0
/sys/kernel/iommu_groups/24/devices/0000:20:07.0
/sys/kernel/iommu_groups/52/devices/0000:43:00.0
/sys/kernel/iommu_groups/14/devices/0000:02:00.0
/sys/kernel/iommu_groups/42/devices/0000:40:07.1
/sys/kernel/iommu_groups/32/devices/0000:23:00.3
/sys/kernel/iommu_groups/4/devices/0000:00:03.0
/sys/kernel/iommu_groups/60/devices/0000:60:03.0
/sys/kernel/iommu_groups/22/devices/0000:20:04.0
/sys/kernel/iommu_groups/50/devices/0000:47:00.0
/sys/kernel/iommu_groups/50/devices/0000:42:09.0
/sys/kernel/iommu_groups/12/devices/0000:00:18.3
/sys/kernel/iommu_groups/12/devices/0000:00:18.1
/sys/kernel/iommu_groups/12/devices/0000:00:18.6
/sys/kernel/iommu_groups/12/devices/0000:00:18.4
/sys/kernel/iommu_groups/12/devices/0000:00:18.2
/sys/kernel/iommu_groups/12/devices/0000:00:18.0
/sys/kernel/iommu_groups/12/devices/0000:00:18.7
/sys/kernel/iommu_groups/12/devices/0000:00:18.5
/sys/kernel/iommu_groups/40/devices/0000:40:05.0
/sys/kernel/iommu_groups/30/devices/0000:23:00.0
/sys/kernel/iommu_groups/2/devices/0000:00:01.2
/sys/kernel/iommu_groups/59/devices/0000:60:02.0
/sys/kernel/iommu_groups/20/devices/0000:20:03.0
/sys/kernel/iommu_groups/49/devices/0000:46:00.3
/sys/kernel/iommu_groups/49/devices/0000:46:00.1
/sys/kernel/iommu_groups/49/devices/0000:46:00.0
/sys/kernel/iommu_groups/49/devices/0000:42:08.0
/sys/kernel/iommu_groups/10/devices/0000:00:08.1
/sys/kernel/iommu_groups/39/devices/0000:40:04.0
/sys/kernel/iommu_groups/67/devices/0000:61:00.0
/sys/kernel/iommu_groups/29/devices/0000:22:00.0
/sys/kernel/iommu_groups/0/devices/0000:00:01.0
/sys/kernel/iommu_groups/57/devices/0000:4b:00.0
/sys/kernel/iommu_groups/19/devices/0000:20:02.0
/sys/kernel/iommu_groups/47/devices/0000:42:04.0
/sys/kernel/iommu_groups/37/devices/0000:40:02.0
/sys/kernel/iommu_groups/9/devices/0000:00:08.0
/sys/kernel/iommu_groups/65/devices/0000:60:08.0
/sys/kernel/iommu_groups/27/devices/0000:20:08.1

agent: 1
args: -smbios type=2 -cpu host,vendor=GenuineIntel,+invtsc
bios: ovmf
boot: d
cores: 64
cpu: host
efidisk0: local-lvm:vm-100-disk-1,size=128K
hostpci0: 21:00,pcie=1,x-vga=1
hostpci1: 02:00.0
hostpci10: 00:14.0
hostpci2: 44:00
hostpci3: 46:00.1
hostpci4: 46:00.3
hostpci5: 47:00
hostpci6: 48:00
hostpci7: 01:00.0
hostpci8: 45:00
hostpci9: 23:00.4
machine: q35
memory: 119808
name: sierra
net0: vmxnet3=12:83:7D:28:45:26,bridge=vmbr0,firewall=1
numa: 1
ostype: other
scsihw: virtio-scsi-pci
smbios1: uuid=43051c32-3e2e-4f80-b7cc-d50def662b0b
sockets: 1
startup: down=20
tablet: 0
vga: none
vmgenid: 284011f9-380c-4bdf-b57f-08eda8f03bb9

as side note I cannot passthrough these two usb controllers:
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:7c60]
Kernel driver in use: xhci_hcd
23: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:7c60]
Kernel driver in use: xhci_hcd

Thank for any help to figure out this
 
Last edited:
HI,
when I start latest Proxmox Ve I have a bunch of ACPI errors
The ACPI warnings should be harmless, most recent AMD processor seem to get these.

and before reaching shell cursor I have this:
[...]
I have this problem with all available BIOS for my motherboard
If I disable HD Audio in bios section I have not this message above in the spoiler

This is a known bug that has been very recently fixed in the upstream kernel (commit). Does this affect functionality you need? Otherwise you can safely ignore the warnings as well.

as side note I cannot passthrough these two usb controllers:

Passthrough for the Starship/Matisee USB controllers is not supported in current kernels (yet?). If you're feeling experimental, here's a discussion on the Level1Techs forum about a kernel patch potentially providing a workaround - you'd need to compile you're own kernel though, for that also checkout our git.

Basically, you're experiencing the joy of working with the bleeding edge of hardware :)
 
First of all thank you for your answer!

This is a known bug that has been very recently fixed in the upstream kernel (commit). Does this affect functionality you need? Otherwise you can safely ignore the warnings as well.

Yes I have a weird problem on audio inside my OSX VM (latest high Sierra )

Audio passed with my Nvidia card is perfect (DP/HDMI) internal audio is choppy, is also choppy any usb audio I use with USB audio card

Passthrough for the Starship/Matisee USB controllers is not supported in current kernels (yet?). If you're feeling experimental, here's a discussion on the Level1Techs forum about a kernel patch potentially providing a workaround - you'd need to compile you're own kernel though, for that also checkout our git.

Basically, you're experiencing the joy of working with the bleeding edge of hardware :)
Indeed I have passed different USB controller:

46: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: vfio-pci
46: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: vfio-pci

But I miss one which seems connected to Usb internal audio (23:00.3)

It seems to my basic knowledge all group are well separated..but I could be wrong here

I would like also to say that with Proxmox Ve is possible to build a perfect working OSX system with newest AMD CPU..only few problems to solve
but it is working at its full performance for CPU and GPU
yes..it is a great joy to experiment with the bleeding edge of hardware and OSX working on it :) :) Proxmox help me so much in this task
Thank Proxmox team ;)
 
Last edited:
  • Like
Reactions: Stefan_R
Yes I have a weird problem on audio inside my OSX VM (latest high Sierra )

Audio passed with my Nvidia card is perfect (DP/HDMI) internal audio is choppy, is also choppy any usb audio I use with USB audio card

That seems unrelated to the messages you mentioned though. Audio is generally a bit tricky in VMs, how exactly are you assigning the audio devices? PCIe or USB passthrough?

Indeed I have passed different USB controller:

The ones you are posted are the ones mentioned to be broken. I can personally vouch that the issue happens with all Starship/Matisse (i.e. TRX40-based) USB controllers, not just the ones mentioned exactly in the Level1Techs post. If you want stable USB passthrough you either have to try your luck with the kernel patch or use a seperate PCIe USB controller.
 
  • Like
Reactions: fabiosun
That seems unrelated to the messages you mentioned though. Audio is generally a bit tricky in VMs, how exactly are you assigning the audio devices? PCIe or USB passthrough?

I use both method in different tries I have done. always same problem .
Screen Shot 2020-05-07 at 13.58.20.png
Screen Shot 2020-05-07 at 13.57.41.png

I see a weird audio device here, I think passed by default by Proxmox:

Screen Shot 2020-05-07 at 14.02.22.png

I do not know how to not have this loaded.

The ones you are posted are the ones mentioned to be broken. I can personally vouch that the issue happens with all Starship/Matisse (i.e. TRX40-based) USB controllers, not just the ones mentioned exactly in the Level1Techs post. If you want stable USB passthrough you either have to try your luck with the kernel patch or use a seperate PCIe USB controller.

I can confirm on my MSI TRX40 Pro 10G I can pass easily some usb controllers not all. I can Pass also Asmedia USB controller (43:00)

I will try to compile kernel patch as you indicated me..I have to study "how to.."
I have also to understand if some default passed devices by default by ProxMox could create this problem (It seems like an interference when using internal audio)
However Nvidia dp audio is fine (it uses Nvidia Web driver and works perfectly)

Thank you again
 
Last edited:
......
If you want stable USB passthrough you either have to try your luck with the kernel patch or use a seperate PCIe USB controller.
Hi
inLevel1Techs post they say it is possible to pass to kernel:
pcie_no_flr=1022:149c,1022:1487
as boot parameter kernel command
I have tried to update my grub.cfg with it without success.
Where I have to insert exactly that line?
I have inserted it here:
linux /boot/vmlinuz-5.4.30-1-pve root=/dev/mapper/pve-root ro quiet iommu=pt amd_iommu=on pcie_no_flr=1022:149c,1022:1487
but it seems to affect nothing if I pass my "defective" usb controllers
thank you again
 
Last edited:
I think the patch is necessary, I couldn't find any reference to 'pcie_no_flr' in the kernel source on a glance...

For reference, here is our documentation about changing the kernel command line, to verify you can check /proc/cmdline to get the currently booted one.
 
  • Like
Reactions: fabiosun
Thank you again @Stefan_R very appreciate
Yep kernel line is there so it is mandatory to patch kernel(as you said) because that line it has no effect in my case
Now I can pass also
23: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:cb60]
Kernel driver in use: vfio-pci
but audio is not good
I have used:
+/* FLR causes Ryzen 3000s built-in HD Audio & USB Controllers to hang on VFIO passthrough */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_intel_no_flr);

maybe to pass these one:
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:7c60]

23: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:7c60]
Kernel driver in use: xhci_hcd

I have to use:
+/* FLR causes Ryzen 3000s built-in HD Audio & USB Controllers to hang on VFIO passthrough */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_intel_no_flr);
?
or it is unrelated in your opinion to bad internal audio?

thank you
 
Good to here that the kernel patch fixed your initial issue. Here's to hoping it (or something less hacky) gets upstream soon :)

If the audio works but just sounds bad I suspect a different issue at play. Maybe try an external sound card (USB, PCIe, whatever) or look into alternative solutions like scream (I use that one personally and it works really well). Keep in mind that this is getting into unsupported territory (well, technically as is the kernel patch, but whatever), so I can't really help you set that up for your specific system.
 
The "unsupported territory" as you said it is more unsupported one because I am using Proxmox VE for an OSX VM environment and maybe it could be OSX driver related.
In windows VM I have perfect audio only passing Realtek USB audio (internal) with Proxmox Ve web interface port passthrough...
Thank you again @Stefan_R
I understand well you can't help in this specific system
Passing audio controller is possible using that patch, but it not solves bad audio I have also without passing it
My next goal is to pass also 23:00.3 usb controller and see if it is related to 23:00.4 (audio matisse controller)
 
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 308f744393eb..9806bff34b9b 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -4999,6 +4999,9 @@ static void quirk_intel_no_flr(struct pci_dev *dev)
DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_intel_no_flr);
DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_intel_no_flr);

+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_intel_no_flr);
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_intel_no_flr);
+
static void quirk_no_ext_tags(struct pci_dev *pdev)
{
struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus);
--
2.24.1
compiling this patch TRX40 users have the chance to pass all problematic controllers (in passthrough entire controllers without hang VM)
It is possible to achieve this:
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:7c60]
Kernel driver in use: vfio-pci
Kernel modules: xhci_pci
23: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:7c60]
Kernel driver in use: vfio-pci
Kernel modules: xhci_pci
46: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: vfio-pci
Kernel modules: xhci_pci
46: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: vfio-pci
However Problems with bad Audio remains in OSX High Sierra
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!