Search results

It’s the way it was implemented. From my experience some AMD systems needed a separate SSDT-EC and SSDT-USBX, and also added a SSDT-PLUG, SSDT-SBUS-MCHC & SSDT-XOSI. Also GenericUSBXHCI was not enabled and we used @daliansky’s existing USBPorts map. We added those plus some new kernel patches...

I believe he wants to know if his laptop (called the MechRevo Code 01, also known as the XMG VIA Schenker (PRO)) could be made into a hackintosh. 我相信他想知道他的筆記本電腦（稱為 MechRevo Code 01，也稱為 XMG VIA Schenker (PRO)）是否可以被製作成黑蘋果. @SummerWithYou, To answer your question, no not yet. However if you have...

No mine is not a MSI motherboard but a Gigabyte - B550 Vision D with 5900X to be exact. The build is confirmed working with Monterey 12.3+ and is rock solid.

Alright @daliansky, try this new EFI. I've made all the needed changes including the kernel patch and updated SSDT-CPUR.

@daliansky, Okay. Could you do a DSDT dump of your BIOS? It would be good to check that out.

Okay @daliansky, So I've had a look at your EFI this past hour. It looks like you had quite a number of things missing in the config file for the system to boot. One of the biggest was you were missing a handful of required SSDTs such as SSDT-HPET, SSDT-SBUS-MCHC and SSDT-XOSI. The other thing...

Welcome @daliansky! I'd heard/read a bit about you/your tech blog before sometime ago and hadn't had the chance to say hello. Your efforts to improve the knowledge of hackintoshes is highly commendable to say the very least!

You'll also notice in the above screen that a device using IONDRVFramebuffer remains active. I can tell you this is actually used by the AMD IGPU. How do I know this? Because this is exactly the same framebuffer setting I have for my Atari VCS which has a Ryzen 1606G Picasso APU. Despite not...

I think it is more than that. Let me show you something. This is a screengrab of the PCI specs of the current Mac Pro: As you can see the slots are defined as Gen 3 PCIe. Since Apple doesn’t have a PCIe 4 based product (and doesn’t use PCIe in the new Apple Silicon designs afaik) that leaves...

Yes it should be. ALC4080 normally requires use of AppleALCU (U for USB). Have you tried doing that @PoMpIs? However I think there's an extra issue here - it sounds like it may be the audio from both the IGPU and/or dGPU are interfering somehow with the system. Not sure if we need to submit to...

You have to use that in conjunction with e1000=0

Not typo error. Because that’s the device values I used to set mine for I-225V LAN under Monterey (without extra drivers). Some earlier versions of macOS pre 12 could get away using F2150000 or even F3150000 but not with the setups needed now.

Looks like according to the above address the settings should be this: and the PCIRoot path is this - PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/Pci(0x5,0x0)/Pci(0x0,0x0) I am using F2158680 because that should be the one to use. F315 is for a secondary LAN port only.

Have you tried enabling AppleI2xx.kext?

Maybe the PCIRoot path set for the I-225V is wrong? We could have a look at what shows up in the PCI list in Hackintools and compare.

I use a few Gigabyte boards myself (B550 Vision D, Z590I Vision D, Z490 Aorus Xtreme, Z170N-WiFi) and I will say that they generally are very good. Their UEFI BIOS has always been very flexible and I've rarely had any major issues so I'd expect any 670E boards they produce should be good for...

Okay @eduard0, it looks like you're missing a fair amount of necessary SSDTs in your build, namely: SSDT-CPUR.aml SSDT-EC.aml How does your USB ports fair? If they're not working fully you may also need SSDT-XHC0-TO-XHC or PTXH-TO-XHC2-NO-PO9-10-11 renames. I also noticed you never installed...

@PoMpIs, It's great to hear you got the Monterey up and running! Is it stable? If so I'd love to see how the GB5 compares. But honestly great work man great work! 👏👏👏 As for the LAN/WiFi that's easy to resolve. Just add e1000=0, remove any existing LAN kexts and add the following into your...

I believe the Apple support posts have mentioned the cause of this issue is basicallty bad RAM. Try to perform a Memtest on the RAM in your system and see how it fairs. In addition if you use XMP profiles, to try to reduce your RAM speeds down a notch if it runs high and see if the problem is...

@PoMpIs, Yes sure! If it helps you could add swd_panic=1 into the boot-arg to try and stop the rebooting.