I've found several guides for getting HDMI audio working with my nvidia 10 series in High Sierra, however invariably they involve mounting the EFI partition and adding files. In one case to EFI/CLOVER/Kexts/Other In another case to EFI/CLOVER/ACPI/patched as well. However, neither of those locations exist inside the CLOVER directory. Manually adding them and dropping the files in them does not enable the devices. I'm not sure where I should be going from here, or in general what I should be doing in these situations. I wouldn't think the system logs (if I knew where they were) would be helpful, since the module seems to fail to load in the UEFI. I'm not sure if this could be related, but I have an AMD Zen generation CPU, and am loading a patched kernel. I'm hoping there is something simple missing in clover that I can simply add or turn on. Thanks for reading.
Thanks for the response. Could you elaborate? It's not clear what youre referring to in that excerpt of my op that you quoted. If it's with respect to methods of installing the driver, here's a popular thread from this forum that instructs how: https://www.tonymacx86.com/threads/clover-hdmi-audio-for-nvidia-amd-cards-easy-way.145399/ It also seemingly expects the directory "kexts" to exist and contain "other"
You have a defective Clover installer. or You are looking in the wrong place. Installing in Legacy mode but looking on the EFI partition. If you have a Q35 chipset as shown in your profile then you probably have installed in Legacy mode which means that the /EFI/CLOVER folder will be on your system drive and not in the EFI partition.
Q35 is just one of the chipsets that Qemu can emulate, and the one that is recommended for GPU passthrough. I can't be using legacy boot, because (I don't think) passthrough would work using the OVMF method. I'm not sure how I got it working, but I did. I just dd'ed my install EFI to my OS disk's EFI again. It may not even have been that. I rebooted the host and it was working. (It's still very mysterious to me) If I had to bet the farm, I'd say it was the host reboot that did it, not the re-dd, but I can't be sure, and so I just accept the mystery.
Did you ever get your HDMI working? I'm running into a similar problem, and none of the popular solutions for bare metal work.
Yeah, but I only recall that I started the bios building part of the docs again, and this time had the correct directories in UEFI dir appeared
