Do you have and use a Thunderbolt dock with this laptop? I tried a different ThinkPad and using the (ThinkPad) Thunderbolt dock killed all input including the built-in keyboard and trackpoint, rendering the laptop unusable. If Thunderbolt works on this laptop with Qubes I might pick one up.
At work I’m using a monitor with Thunderbold. At home I’m using a small Thunderbold adapter with HDMI, USB-A which works fine. Using the build-in HDMI just gives me 16:9 resolutions. Using the Thunderbold adapter 32:10 works out of the box.
So, from my point of view Thunderbold works great with this ThinkPad under Qubes OS.
VIDEO:
Working GPU SRIOV with patched kernel intel module, working DRM on VM-s witch debian-13-template. Playing 8K videos and games like 0ad. OBS Studio working nice
NETWORKING:
Work with kernel-latest and new intel-firmwers
SLEEP:
No S3 support. S0ix only (Lenovo what are you doing!). After some modyfications 1-3W in sleep state
Intel NPU:
Working great after upgrading new firmwer files from intel site. ONNYX/pytorch working nice.
External Monitor wokrs stable over HDMI port or USB-C
I hope there will be a guide on how to replicate setup like that. (specially how to get SR-IOV working in qubes os)
Each of the following successes deserves a guide on how to replicate it.
How to get intel sr-iov working on Qubes OS?
How to passthrough intel NPU to a VM so it can be used and get it to work correctly. (I currently have novacustom v54 laptop, witch have the same generation of CPU, and I file to get the driver for NPU to work corectly)
How do you disable Intel ME on lenovo laptops? Did you make a custom bios somehow? (I do not thing this laptop is suported by coreboot and default lenovo bios definitively does not have thet feature)
NPU works out of the box after some modification. (Firmware files in on the Intel site). I dont too much time testing Pytorch or ONNX. But backgrond remover in obs studio working great.
No. I didint write a BIOS. Simply. Dump flash and set HAP bit. Write flash.
I need your help, @1x3n1x. So far you’re the only person that I’ve seen successfully configure Intel SR-IOV support inside of Xen / Qubes. So having your guidance will greatly help the community.
A couple of questions:
Are you compiling the kernel module inside of dom0 or are you compiling it on a guest VM and then copying it back over to dom0?
Are you using DKMS?
Do you have have to change any kernel flags prior to compiling DKMS? What patch are you applying in order to get it working?
Yes. I will using it witch NPU+GPU in AppVM for AI purposes or games like 0ad. Or in another sys-ai to share model to all vms. Xorg qubes-dummy + intel GPU
In my free time I write a manual and how I did it step by step. I experimented a lot with the code and I have to put it into one coherent whole. It is mainly used for Intel Meteor Lake. I compiled the kernel module directly in dom0 patch+official intel source code. For now I experiment a lot with it but initially the SR-IOV performance with NPU+GPU is comparable to the installation from Ubuntu 22 for llama or ollama.
Sharing this with the community would be extremely helpful. Based on the feedback I have received from the core developers, experiments with that driver and SR-IOV resulted in frequent crashes. Since Intel stopped developing SR-IOV in i915 driver and focused on xe driver instead which did not have full SR-IOV at the time of testing. There was a commit enabling it for Panther Lake chips which isn’t available yet.
At the moment. I am testing the settings in my laptop (T14 gen5) and intensive work with GPU + NPU. The only problem is that s0ix is not fully supported. I have never had any stability issues with the GPU in MeteorLake. When I intensively use OBS Studio as a virtual camera + MS Teams, nothing has ever hung. I talk for a few hours and at the moment I am rubbing my eyes in amazement. Perhaps when switching from x230 I have been hit by a technological abyss. Qubes 4.2 still has xen in version 4.17 and lack of full CPU support. For now I am testing 4.2 but I want to move it to 4.3 due to new versions of xorg and mesa. At the moment both xe and i915 do not have full GPU support in dom0. I will transfer everything to Qubes 4.3 and maybe the big problem is fedora37 with which I do not have much experience.
In free time I will create a github account and try to send as much information from tests as possible. Maybe the programmers will help to clarify a few issues. I got stuck with the MeteorLake system documentation. I also had a lot of problems with putting the i915 to sleep with SR-IOV enabled. The main advantage of SR-IOV is definitely the GPU performance in AppVM compared to GVTg. In fact, when sharing GPUs on AppVM, GVTg is much easier. For now I want to transfer everything to Qubes 4.3 unless someone suggests how to force dom0 to update to 4.3