-
sjorgetsoome which sha512 util did you use? I keep getting cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e loader.efi for the binary you need the output from
-
sjorgeThat's with shasum -a 512 <file>
-
tsoomedigest -a sha512 :)
-
tsoomehm, but I get the same result from both digest and shasum
-
sjorgeFound the issue, coudln't safe it to FAT32 for some reason it always ended up corrupt
-
sjorgeI got you the output from a SM X11 platform
-
sjorgeSomething different, anybody well versed in bhyve pci passthru and GPU
-
sjorge
-
sjorgeI think I did it right, but there is not ppt device for the HDA device
-
sjorgeJust using ppt6 makes the GPU show up in the VM and nvidia-smi seems happy *crosses fingers*
-
sjorgeHmm ffmpeg doesn't want to use it though, it just segfaults
-
sjorgeLunch break over now thouygh
-
sjorgeOh for completeness, I do not want to use it as a display just CUDA which AFAIK should work
-
sjorgehmm seems
-
sjorgefor nvenc/nvdec it needs the HDA one too, then one were i cant get ppt to attach too, at least according to some threads
-
yuripvisn't that just a function on the same device?
-
sjorgeOh that's fun
-
sjorgeI just said grab EVERY thing with these PCI,dev IDs and now it works
-
sjorgethe path listed in pptadm list is not the same as the one pciadm was showing
-
sjorge@0,1 seems to have gotten truced somehwere in the pciadm output
-
sjorgePassing in the hda drive seems to have made nvenc/nvdec not crash so al lgood