also, what is the host OS and kernel version?
Thankfully I did a lspci before and after I installed the 6600 xt, so no need to unplug one. The 40 is from the 0a through 0c are completely absent for some reason. Either way, given the IOMMU number, the 40 one is from the 6400, the 17 one is from 6600 xt. I will pass both GPUs, one for Linux, one for Windows.
Unfortunately now I am stuck at generating the initramfs, dracut doesnāt have the vfio module and I have 0 clue on how to enable it.
Seems like it was not
add_dracutmodules+=" vfio "
, but actually
Dang it! lsinitrd now shows vfio loaded. This is bs, but ok, as long as it worksā¦
I want to go back to my elementaryOS install, however I have a problem. I am currently playing tarkov. Iām not exactly enjoying it, but practice makes perfect.
I remember some shit about running it in a vm, and basically all you needed was to get a separate drive controller to run the game off of. I doāt care for cheating, but most will recognize this sorta shit from hack videos. Personally I just wanna play my game.
If I used an nvme drive would that count as its own thing and not have a vm bitch? Should I just dual boot? I donāt wanna do thatā¦
Yes, passing PCI-E or SATA controller or even single SATA ports, is what you are looking for. I used to have a dual-boot, but I basically never booted into Windows. I passed the GPU, PCI-E USB controller and the sata1 (sata ssd) to the VM and I was booting the VM from the SSD.
The lsinitrd does not show the /etc/modprobe.d/vfio.conf file 
lsinitrd |grep vfio
-rwxr-xr-x 1 root root 205 Aug 15 02:42 usr/bin/vfio-pci-override.sh
drwxr-xr-x 3 root root 0 Aug 15 02:42 usr/lib/modules/5.18.17_1/kernel/drivers/vfio
drwxr-xr-x 2 root root 0 Aug 15 02:42 usr/lib/modules/5.18.17_1/kernel/drivers/vfio/pci
-rw-r--r-- 1 root root 44807 Aug 12 16:53 usr/lib/modules/5.18.17_1/kernel/drivers/vfio/pci/vfio-pci-core.ko.gz
-rw-r--r-- 1 root root 12658 Aug 12 16:53 usr/lib/modules/5.18.17_1/kernel/drivers/vfio/pci/vfio-pci.ko.gz
-rw-r--r-- 1 root root 26687 Aug 12 16:53 usr/lib/modules/5.18.17_1/kernel/drivers/vfio/vfio.ko.gz
-rw-r--r-- 1 root root 26396 Aug 12 16:53 usr/lib/modules/5.18.17_1/kernel/drivers/vfio/vfio_iommu_type1.ko.gz
-rw-r--r-- 1 root root 6537 Aug 12 16:53 usr/lib/modules/5.18.17_1/kernel/drivers/vfio/vfio_virqfd.ko.gz
vs
What the heck even is this under dmesg?
[ 1.062297] VFIO - User Level meta-driver version: 0.3
[ 3.807832] [drm] amdgpu kernel modesetting enabled.
[ 3.807924] amdgpu: Ignoring ACPI CRAT on non-APU system
[ 3.807927] amdgpu: Virtual CRAT table created for CPU
[ 3.807936] amdgpu: Topology: Add CPU node
[ 3.808038] checking generic (80000000 e10000) vs hw (c0000000 10000000)
[ 3.808179] amdgpu 0000:0a:00.0: enabling device (0000 -> 0003)
[ 3.808241] [drm] initializing kernel modesetting (DIMGREY_CAVEFISH 0x1002:0x73FF 0x148C:0x2412 0xC1).
[ 3.808245] amdgpu 0000:0a:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[ 12.164579] [drm:amdgpu_dm_init.isra.0.cold [amdgpu]] *ERROR* Failed to register vline0 irq 30!
Why would amdgpu even loadā¦
Managed to get passed this by adding the file to the /etc/dracut.d/vfio.conf
Seems like I get the ASRock logo on the display. But the vfio-pci driver is loaded. I passed the 6400, then when I started the windows VM, I got the hostās output on the screen, with some rubbish kvm messages āignored wrmsrā and āignored rdmsr.ā Windows updates are downloading, and I see it detected AMD display drivers to install. I hope all goes well, but given that I see the hostās output there, I am slightly doubtful.
Is this the dreaded reset bug? Would I need my monitor turned off when the host boots and only turned on after itās on? I donāt know what Iām supposed to doā¦ 
I think the reset bug is that GPU never goes back to the default driver- it stays with VFIO. This might be OK for some situations, but if you want to use it for something else, it will be an issue and require a reboot.
I donāt care if it stays with vfio in the host, because Iām passing it through. But I do not know if that means it stays with vfio in the VM too and does not load the windows driver. That would suck big time. I saw that gnif has a āvendor-resetā project going on. Navi 10 XL, 21, 23 and 24 donāt show up in the repo though. Big OFF if I need that.
Heh, would anybody expect code 43 on AMD? lul
The display reset and then turned off. Probably need a VM reboot. I donāt know if just a rando driver install thing, or if it was due to the reset bug. I never saw it, so idkā¦ anyway, after a VM reboot once updates install, Iāll try an entire host reboot, hopefully I can get the 6400 to work. Then Iāll have to remove it from this VM, I just want the coupon, the 6400 will go to the linux VM. Windows gets the 6600.
Made it work after a host reboot. So, I started the host with monitor powered off, then started the monitor, it was black of course, then powered on the VM and windows came right up. I need to pass it a USB port, then I can use my monitorās built-in KVM to switch between VMs. Iāll need a usb-c to DP+USB adapter though.
I need to pass an independant storage controller or battleye sees its a vm and bans the acct
You probably will want to follow the nvidia guides for passthroughs, so that you can lie to your vm and let it think itās a physical host too.
Link? I am horrible at google, thats why I ask so much stuff on here.
when you have a bad shut down and your vpn was activeā¦
check the resolver.conf in /etc/ and make sure its still not pointing to the vpnā¦
symptom: internet connection that will only allow ipās not resolved names.
fix: change the resolver.conf to point to 8.8.8.8 or 1.1.1.1
it might save you installing your o.s again
2 Likes
A Haikuā¦
6 Likes
Erā¦ I was taught in school that haiku were 5, 7, 5 so that would be better
It's not DNS
There's no way it's DNS
It was DNS
4 Likes
Wait, so its not the fireball thingy in punching game arcades?
1 Like
honestly i thought you just sneezed before making a random quote 
3 Likes