You are not logged in.
I followed the wiki to try and pass through my Quadro to a windows VM, before giving up after much trouble with error 43 (optimus laptop). To do that I added my vendor-device ID's to /etc/modprobe.d/vfio.conf and added a few vfio related modules to /etc/mkinitcpio.conf. In retrospect, I don't think I needed to do that because I had passed the kernel parameter in the command line with
vfio-pci.ids=10de:13c2,10de:0fbb (replacing those values with my hardware's). I've deleted the file at /etc/modprobe.d/vfio.conf and removed the modules from /etc/mkinitcpio.conf, but the output of lspci -nnk -d still says that the vfio driver is in use.
So, neither grub, modprobe or mkinitcpio have anything in them and all have been regenerated, but vfio continues to claim the device. How do I undo the parameter I passed via the command line? I'm sorry to ask but I'm obviously being a fool and can't figure this out on my own any more, so I'd appreciate any help if somebody knows what to do. For reference,
cat /proc/cmdline returns nothing related to vfio either.
Any help would be much appreciated!
Last edited by drossbox (2019-12-04 16:44:34)
Offline
You did reboot after making those changes, right ?
post dmesg and/or journalclt -b please.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline