---
layout:
'hcl'
type:
'Notebook'
hvm:
'yes'
iommu:
'yes'
slat:
'yes'
tpm:
'2.0'
remap:
'yes'
brand: |
LENOVO
model: |
21RQCTO1WW
bios: |
N4FET29W (1.10 )
cpu: |
Intel(R) Core(TM) Ultra 9 275HX
cpu-short: |
FIXME
chipset: |
Intel Corporation Arrow Lake-HX 8p+16e cores Host Bridge [8086:7d1c] (rev 01)
chipset-short: |
Intel Corporation 800 Series Chipset [WM880]
gpu: |
Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] (rev 06) (prog-if 00 [VGA controller])
NVIDIA Corporation GB207GLM [RTX PRO 1000 Blackwell Generation Laptop GPU] [10de:2db8] (rev a1) (prog-if 00 [VGA contro
ller])
Intel Corporation Device [8086:7f2f] (rev 10)
gpu-short: |
FIXME
network: |
Intel Corporation Wi-Fi 7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2 [8086:272b] (rev 1a)
Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04)
memory: |
97716
scsi: |
usb: |
5
certified:
'no'
versions:
- works:
no
qubes: |
R4.3-rc3
xen: |
4.19.3
kernel: |
6.17.4-1
remark: |
USB Controller is not able to be passed to sys-usb. Audio does not work neither and cannot be passed to a sys-audio (same error)
credit: |
bertrand
link: |
FIXLINK
Remarks
USB Controller is not able to be passed to sys-usb.
Audio does not work neither and cannot be passed to a sys-audio (same error).
If you leave USB controllers in dom0, they seem to work.
For your first question, the internal audio does not work. I did not yet investigate on this as my other problem is of more importance for me. You cannot make a PCI passthrough of the internal audio device to a sys-audio qubes, as the PCI device has the same issue as the usb controller. I did not test the audio devices coming with the nvidia graphic card.
For your second question, from memory (I cannot test it right now), I think it worked with an USB-C to DisplayPort adapter. And this was with a standard installation and the nouveau driver.
I have seen several threads where you mention the patch from @Bloged
Am I correct that it is (apparently) a failure to recognise a secondary PCI root device?
If it is a general problem, then maybe it could be useful to change the title of your issue report so that it better describes the underlying problem.
Also to link to any other forum posts where it is diagnosed to be the same issue. It could make it more visible.
I did not find another issue that mentions such problem of root at 0x80, or any other… but I am not sure I am searching for correct terms, and I do not really understand the matter.
It is correct that currently it fails to correctly identify the secondary PCI root device; this current implementation is hacky but seem to work on multiple systems.
The problem is that it wasn’t a pre-defined plan to tackle this problem in this way therefor the information now is spread over multiple topics and/or posts. But feel free to write a community guide that explain how to do this in detail and in one central place.