Hi, On July 17, 2025 12:54:28 AM GMT+08:00, Konrad Neuwirth <kon...@fimsch.net> wrote: >Thank you for your help, previously. > >I’ve finally found time to get back to this, and it continues to make me feeel >dumb. > >With the following kernel config > >(kernel-arguments > (append '("vfio-pci.ids=8086.7e40" "iommu=pt" "intel_iommu=on" > "modprobe.blacklist=iwlwifi") > %default-kernel-arguments))
Stupid question, did you reconfigure? I think that for quicker iterations you do not need to modify your config, you can just edit the bootentry in grub with 'e'. There you can see the current arguments to check if they are what you expect, and also add / modify them. Rutherther > >I’m getting to … > >00:14.3 Network controller [0280]: Intel Corporation Meteor Lake PCH CNVi WiFi >[8086:7e40] (rev 20) > DeviceName: Onboard - Ethernet > Subsystem: Intel Corporation Wi-Fi 6E AX211 160MHz [8086:0094] > Flags: fast devsel, IRQ 255, IOMMU group 12 > Memory at 5020314000 (64-bit, non-prefetchable) [disabled] [size=16K] > Capabilities: [c8] Power Management version 3 > Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ > Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00 > Capabilities: [80] MSI-X: Enable- Count=16 Masked- > Capabilities: [100] Latency Tolerance Reporting > Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 > <?> > Kernel modules: iwlwifi > >So it’s /still/ loading iwlwifi. For whatever reason. > >> Am 16.06.2025 um 12:34 schrieb Rutherther <ruthert...@ditigal.xyz>: >> >> >> Hi Konrad, >> >> Konrad Neuwirth <kon...@fimsch.net> writes: >> >>> Hello there, >>> >>> you’re right: I’m trying to have the hardware managed by the OS running >>> within QEMU. All the parts are there, and I can the exact configuration to >>> run when I start the components by hand. But it doesn’t work when I try to >>> get them started at boot. My wanting to not load the iwlwifi driver is >>> because then, I can have the vfio get to that device and pass it on to >>> QEMU. I’m not running Guix in under QEMU, so there’s an OS there that can >>> actually deal with the hardware. And I’m fairly certain it’s a complex >>> problem to get from the QEMU virtual machine back to the Guix install that >>> runs it. >> >> Ahhh. Okay, then I see how that can be working. >> >> >>> (kernel-arguments >>> (append '("vfio-pci.ids=0x8086.0x7e40" "iommu=pt" "intel_iommu=on" >>> "rd.driver.blacklist=iwlwifi") >>> %default-kernel-arguments)) >> >> To get to the iwlwifi issue... I see you used rd.driver.blacklist, >> how did you find out to use it? I've never seen that argument. >> >> To blacklist modules, I think modprobe.blacklist should be used, it's >> even in the guix system manual - >> https://guix.gnu.org/manual/devel/en/html_node/Initial-RAM-Disk.html#index-module_002c-black_002dlisting >> >> Rutherther >>> >>> Thank you, >>> Konrad >>>