Leoyzen

@MortalMonkey Have you read the comments below the post? The attachment at first floor is fine for downloading.

@MortalMonkeyAccording to some people's feedback, the kernel should work.Just download it and put it into your usb stick.

@ghost82 Yes, you can find your vendor or others who have the same board to find the specific layoutid first.

@ghost82 AppleALC correctly found the audio device according to your log. You should set Audio layoutid and select "ResetHDA" and test again.

@ghost82 That quite likely. Post you log witb -liludbg and -alcdbg. My board is x570 and currently can't passthrough the audio onboard. I'm not familar with audio (I'm using HDMI audio now) but maybe audio should in some specific APCI node like HDEF/HDAF (I don't know but I guess maybe related), you may should add ssdt to see.

I will try.But I lost my compute recently so it will take some time

@ghost82According to the log everything works fine. You should know that kext inject to the "cache" not the origin "kext", so when you made some change it is safe to "rebuild kernel/kext cache" before reboot.

@ghost82 Post your clover boot log

@ghost82That's absolutely insane....

I compiled a new Lilu and update QEMU vendor-id, then Lilu and WEG work now! You guys can just download this Lilu and using latest WEG from github then WEG will works now in hackintosh VM, no ssdt and no patches any more.Lilu-1.3.8-DEBUG.zip Edit: Lilu master update the code, so wait Lilu 1.3.9 will add QEMU support.

Yeah, I can confirm Lilu/WEG not work at all in my hackintosh vm, I just boot direct from disk without QEMU and Lilu/WEG works. So I think it's maybe ACPI or QEMU related problem to avoid Lilu get correct graphic. Lilu/WEG is so important for those who have some problem with Grahpics, though we can use ssdt or clover patch, we lost many features of automatic works maked by WEG. Edit: I found that Lilu didn't work with QEMU/kvm by digging Lilu log and code that Lilu doesn't recognize QEMU pci-bridge vendor-id so it continues then can't get graphic device at all, WEG then not work property. It shocks me because every tutourial told us that it should use Lilu/WEG to help recogenize graphic in kvm but it doesn't work at all!! God damned. I just submit an issue to Lilu developers. Here is link.

I'm not seeing any proof (via log or effects) Lilu/WEG actually works for my hackintosh(neither blackscreen fix nor acpi rename etc).So there is definately something wrong may related to AMD build or Graphic Version or qemu(most likely WEG not suit for QEMU ACPI I think). Does anyone actually seeing anything useful by using WEG?

Which bug do you mean? 127 type error of GPU? I can build a custom kernel if someone really need (actually I am using custom build kernel with custom drivers of using 6.8 RC1).

This is why I'm switch from vmxnet3 to e1000. VirtIO-NET or dedilicate nic passthrough maybe a good choice.

@Zer0Nin3r I have similar problem before,but lagness dismissed after I got a metal support/enabled graphics.Or you should not passthrough the graphics at all.

No, we do not have much options to map memory slots. To use virtio net, you have to do two thing: 1. hotplug virtio ethernet instead of predefined 2. boot args with debug=0x100 and keepsyms=1

Which graphics do you use?Do you use HDMI instead of DP?HDMI do not work with 4k@60hz but DP does.

1. make sure the video and audio are in same bus as I mentioned a few page ago 2. select 'Fix DTGP' and 'Fix display' in clover 3. select 'AMD RXxx blackscreen patch' in clover 4. use iMacPro1,1 instead of iMac17,1 because you don't have iGPU or use my clover qcow2 file I post

Adding more than one ethernet sometimes breaks the acpi layout, you have to make sure the graphics location is under gfx0.

@tpruszin did you follow my instruction above to make sure the graphics and audio are in same bus?What is your graphics?Upload your log. Someone already said before,it is amd reset bug related issues, so you have no certain procedure to avoid it, you have to try something and see it helps.I face the same problem and the procedure I posted work for me, you can just try and feedback if it work or not work, otherwise we can't give more help.

When the unraid first booted, put the machine into s3 sleep(the sleep button in the action page), wakeup, start hackintosh vm later, that's what I do to avoid the reset bug.

I have the same card but I don't use it for now.... The card is strange after flash rx560 bios....I don't know if the card or rx460 work or not....My rx460(flashed rx560 BIOS) works fine for now.

What version unraid do you have? The kernel only works for unRaid 6.7.2.

Finally get native Discrete Card Power Manager works....Will see if there is any problems. Fan speed finally get spins and works....Let's see if there any performance gains. Edit: After all, we finally get a nearly bare metal performance, I'm very happy with that. I will go on vocation for about 2 weeks.After that I will make a turtorial about all these days works. TO BE CONTINUE! Edit: The attachment is my opencore efi qcow2 image, works properly both mojave and catalina. All you have to do is make sure your graphics is under ACPI S08 and make sure SMBIos changes to yours. If not under S08, you have to modify the SSDT-1.aml to your graphics location. Have fun! opencore.release.qcow2.zip

I mention before, please to that post. Or using my clover.qcow2 to see if it works(maybe you will get HW acceralation OOB) smbios is definately import for those who want GPU acceralation works. For Hackintosh VM (which don't have iGPU), the MacPro7,1 and iMacPro1,1 is best choices. you need clover patch to avoid black screen for amd graphics(see the post before) you need select "Add DTGP" and "Fix dispaly" to make sure you graphics is under GFX0 position of ACPI, this will make HW Acceralation happened. WEG won't work fine in VM, because the ACPI is different compared to Native MB. Check you graphic position using IORegistryExplorer If not under GFX0, the HEVC will not work. If something wrong, then Lilu and WEG is needed. Yeah, I'm not familar to opencore too and my efi is not a final working version, so I don't want posting it here to avoid misleading someone. @david279I have no issues upgrading to the latest Mojave, everything works fine for me.