RYTD74

i just now seeing this message from You Maldon. I Studied ACPI under your wing brother, them other people i dont pay any attention to anything they are talking about! We called them out years ago on that bullshit! Slow boot times my ass lol. Shit one of my rigs pops off at literally 5 seconds boot time--Done -- back on Desktop! DSDT 100% And one that i constructed from scratch, OEM SSDTs for USB IGPU Dropped Etc. i know what im doing, and my foundation is solid, its roots are with You man! Thanks for all that by the way, for taking the time to help me when not even knowing who the hell I wa! I wont ever forget it!

No it doesnt matter if you use Clover or OCC or whatever. The numbers i listed as ones you use they are examples . Get you a invalid serial numer make sure your smbios matches your hardware as close as possible.. STEP 1 (SN#C0256YQRDDQV STEP 2 (BoardSerialNumber)C0256YQRDDQV now add 5 diguts random your choice to the end of your Board Serial Number Above it will be a total of 17 digits all together. STEP 3 (SYSTEM UUID) a0b5b7c6-1318-441c-b0c9-fe695eaf949b Act like thats your UUID Hypothetically, Now take the Last 12 Digits of it and copy paste that in your ROM. So in this case your ROM Would like this ROM FE69REAF-949B ------------------Recap------------------------ Serial # C0256YQRDDQV BioardSerial # C0256YQRDDQVHELLO SystemUUID -a0b5b7c6-1318-441c-b0c9-fe695eaf949b ROM# FE695EAF-949B Hope This Helps. If You are still having problems hit me up

try this for your wifi and see if it works EFI 4.zip

What kind of wifi Card is it

Possible Issues #1 (Not Sure That You Need these for Desktop) And Your "PC Hierarchy" is your default already named (PCI0)-? Or is it named by default (PC00) -? On Desktop from my experiece they are usually (PC00) AND if Yours IS THEN THESE SHOULD BE IF NEEDED "\_SB.PC00.SBRG" ETC \_SB.PCI0.SBRG { Device (HPET) { Name (_HID, EisaId ("PNP0103") /* HPET System Timer */) // _HID: Hardware ID Name (_CID, EisaId ("PNP0C01") /* System Board */) // _CID: Compatible ID Name (BUFX, ResourceTemplate () { IRQNoFlags () {0} IRQNoFlags () {8} IRQNoFlags () {11} Memory32Fixed (ReadWrite, 0xFED00000, 0x00000400, ) }) Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings { If ((_OSI ("Darwin") || CondRefOf (\_SB.PCI0.SBRG.HPET.XCRS))) { Return (BUFX) /* \_SB_.PCI0.SBRG.HPET.BUFX */ } Return (\_SB.PCI0.SBRG.HPET.XCRS ()) } Methoa (_STA, 0, NotSerialized) // _STA: Status { If ((_OSI ("Darwin") || !CondRefOF (\_SB.PCI0.SBRG.HPET.XSTA))) { Return (0x0F) } Return (\_SB.PCI0.SBRG.HPET.XSTA ()) } } Device (PMCR) { Name (_HID, EisaId ("APP9876")) // _HID: Hardware ID Name (_STA, 0x0B) // _STA: Status Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings { Memory32Fixed (ReadWrite, 0x00FE0000, 0x00010000, ) }) } ----------------------------------------------------------------------------- Issues other than the above You have 1) USBX Referenced A TOTAL OF THREE TIMES. It is located in all three AML FILES in your ACPI Folder. You only need "One Reference" Usually Located at (\_SB) { Device (USBX) } } 2)And the ("EC") Device You have Listed 2 Times in Two AML Files In your ACPI Folder (\_AMDesk.aml) & in (Maldon.aml) You only need one referencefor it also which is in (Maldon.aml) under (\_SB.EC) etc NOTE: "The EC Device normally is in \_SB.PC00.LPC0, AMD/oR \_SB.PCI0.LPCB, /AND/Or \_SB.PCI0.SBRG AND/Or ("I get that") It is better however for booting purposes to have it purposely placed outsidd the scope of the Low Pin Count Section (aka-LPC0, LPCB,SBRG Etc) to avoid collissions during the boot process cause all thats needed is the presence of ("EC") so tat the OS From Catalina onward can attach itself to that Device EC and not the real EC DEvice being a host of differnt names (EC0_, ECDV, H_EC, Etc) which are usually inthe (\_SB.PCI0.LPCB) {\_SB.PCI0.SBRG) (\_SB.PC00.LPC0) Area so to apeak. So (\_SB.EC) seems to always be more efficient in having Zero issues versus the other ------------------------------------------------------------------------------------------------------- So Remove "AMDesk.aml and SSDT-USBX.aml" And have only this is Your ACPI Folder MaLdOn.aml ----------------------------------------- Also inside Maldon.aml (The Reference to the (_SB.PR00) Has that been edited ? the reason i ask is that usually thereis a reference for only this and not the above labeling all 15 PR00 - PR15 Scope (\_SB.PR00) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "plugin-type", One }) } } And if Your Processor Is Named Something other than (\_SB.PR00) such as mine is on a x299 Desktop (\_SB.SCK0.CP00) Then You will need to rename Yours To the Correct Name. I dont know everything so if im incorrect on something point it out. I Hope this helps with your trouble, other than that Fix Your ACPI Folder with uSing only the Maldon.aml and continue with his recommendation for updating the "Kernel Patches" Peace-- RYTD

Supercool Brother! I just downloaded it. What ever happen to the Olarila Coffe Cups? They still available?

i have one of these machInes Maldon. Great Hackintosh like You said!. Its very fast and smooth but not enough parameters for me to tweak. I dont know about anyone else but mine has 8 GB RAM That comes soldered to the motherboard and has one empty RAM Slot which makes it only upgradeable to 24 GB RAM which is what mine is at. I used the KBL Refresh framebuffer with THE CO87 AAPL,Platform ID With those results and also i switched it over to a Coffee Lake Platform ID and it worked really well to. My processor is a i3-8130u I think anyways. I got too many computers and too many hacks to remember. Lol. Anyway hope all is well my friend! Peace

Wow! Two questions and a third party answers in with a statement not relevent to question 1 or question 2 ol. I am entry #4. I would be glad to help ifts still needed! Just let me know

I read about this on Pikers Blog alongtime ago. But YOUR TUTORIAL HERE is very easy to understand and well laid out. I had absolutely no problem understanding everything you are talking about here. Awsome Guide and Thank You very much my friend! Also: Up to this point The way I have had to approach this without mapping was to add inside the DSDT the values Taken from IOReg under EHC1 EHC2 XHC1 etc inside the ports of each. Such as Below this was on My DELL XPS L521X IvyBridge and Thats what i was having to do to avoid USB Mapping. I am most certainly going to utilize the method That You have described here "GUPC TUPC UPC and implement it into all of my hacks as it simplifies things universally wheras my method above i cant say that it will work on all because it will not. Your method will however work on everything "So Props Maldon to You" Its Intels Shit but so what--You pieced it together and put it into this tutorisl for everyone who is interested to be able to use it so credits should go to You!. Anyway I included the actual custom stripped DSDT that i wrote out for that particular Laptop below DSDT.aml.zip Just as example of what i was referring to. Scope (PCI0) { Device (EHC1) { Name (_ADR, 0x001D0000) // _ADR: Address Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "device-id", Buffer (0x04) { 0x26, 0x1E, 0x00, 0x00 // -... }, "kUSBSleepPowerSupply", 0x13EC, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834 }) } } Device (EHC2) { Name (_ADR, 0x001A0000) // _ADR: Address Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "device-id", Buffer (0x04) { 0x2D, 0x1E, 0x00, 0x00 // &... }, "kUSBSleepPowerSupply", 0x13EC, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834 }) } } } Scope (PCI0) { Device (XHC) { Name (_ADR, 0x00140000) // _ADR: Address OperationRegion (XPRT, PCI_Config, 0x74, 0x6C) Field (XPRT, DWordAcc, NoLock, Preserve) { Offset (0x01), PMEE, 1, , 6, PMES, 1, Offset (0x5C), PR2, 32, PR2M, 32, PR3, 32, PR3M, 32 } Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Local0 = Package (0x0B) { "device-id", Buffer (0x04) { 0x31, 0x1E, 0x00, 0x00 // 1... }, "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0A8C, "AAPL,current-extra-in-sleep", 0x0A8C, "AAPL,max-port-current-in-sleep", 0x0834, Buffer (One) { 0x00 // . } } DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Device (RHUB) { Name (_ADR, Zero) // _ADR: Address Device (HS01) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (HS02) { Name (_ADR, 0x02) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (HS03) { Name (_ADR, 0x03) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (HS04) { Name (_ADR, 0x04) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (SS01) { Name (_ADR, 0x05) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } Device (SS02) { Name (_ADR, 0x06) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } Device (SS03) { Name (_ADR, 0x07) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } Device (SS04) { Name (_ADR, 0x08) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } } }

Sounds Like You Have a few interesting Configurations going on there my Brother! The iMessage is very simple. If You have a Apple ID already that you have logged in with somewhere then you should have no problem. If You have to create a "new Apple ID" then use the way i do it and try. Back in the day I sat here for about two days straight trying to figure out why this wasnt working for me. But anyways its very simple just follow instructions and Enjoy! If you have any issues or problems just let me know and Ill be glad to help You brother!. Peace

I have that same system Slice The E6430 with NVIDIA 5200. Do You actually have that working the NVS 5200M alongside the HD4000? Im curious because i was about to attempt doing that. I just got the NVIDIA GEForce GT640M kicked on on the DELL XPS L521X Id go more into detail but it is too much too text Lol!. It shows up in the system in hackintool as IONDRVFramebuffer Ports 5 Intel HD 4000 Ports 4 Im using a SMBIOS MacBookPro 10,1 the frambuffer for that device is 02006601 on the real mac, im using 04006601 because the other i get a black screen no matter what so i ditvhed it fir te 04006601 which works great. Custom DSDT I wrote it out from scratch it matches up to the real SMBIOS From the genuine MacBookPro10,1 with a few adjustments and the directorys i structured a little bit differently. Works great (Let me revive that system as i crashed it earlier tinkering around with it and ill drop a link to the file here and u can check it out if you want. On the E6430 I was curious on your approach on the NVS 5200M, That machine is less forgiving as the XPS is LOL! Its very "fickle". Mine is the i7-3540 Intel E6430. I also have a dnag E6540 Haswell laying around that has the AMD 8700M in it . Im gonna try that brightness keys patch because on the XPS I Got the brightness keys slider showing up and its movable and all just doesnt do anything.

IvyBridge is good as is. I have several at home hacks that are IvyBridge. 1) Dell XPS L521X running macOS Catalina on a internal M2 SSD Drive and also MacOS BigSur on a internal SATA SSD Drive on the same machine. All i did was copy my original EFI to the EFI Partition on the SATA SSD that was formatted APFS. Then i changed the SMBIOS on the Big Sur EFI Partition To a iMac14,4 then clicked the installer and it started up and began the install of big sur onto the other drive. And it completed the install all by itself using the my original EFI that i copied over to te second drive. No problems whatsoever. What was really interesting was that my catalina install that i did all this from Im using a custom DSDT so the BigSur Install was insatlled using a DSDT with SSDT-PMPM Alongside of it for Power Management. Everything working right out of the Box Only thing I had to adjust was the "WIFI", I had to go get the Airportitlwm.kext that was for BigSur and swap it out with the one that was on there which was for catalina on the other drive and all works good. Im ging to try to name the DSDT.aml to DSDT1.aml for the catalina and then DSDT2.aml fot the BigSur and see if that will keep the loading of the right DSDT for each individual install. Summary: IvyBridge is good. For older system it is still good. Install initially using SSDTs, what I described above is just inhome tinkering its not a way to try a proper install. Install using SSDTS Suited for your system hardware mainly for Ivy this will consist of 1)SSDT-IMEI.aml 2).SSDT-PNLF.aml (for backlight) 3).SSDT-EC.aml (Embedded Controller) For PowerManagement: SSDT-PMPM is generated after install. Im sure You knw all this im just clarifying incase someone else reads the post and might use as a reference . 2)After install you need your DSDT Patched to accomadate your hardware. So there is the DSDT Patch requests here on olarila that you can ask for that to be done. Maldon is very quick in getting back to you . I can do them myself also but out of respect brother i say ask Maldon first Because this is his website and thats his speciality , one of many! So grab you a EFI Folder for the IVY BRIDGE from the olarila efi archive for all chisets and hit maldon For a DSDT Patch and i bet your system might surprise you on the capability of it. I woud personally ditch the VMWare install and just go direct on it. Hit me up if you got any other questions or if you need some help.

Yeah give it try and let me know what happens if you having trouble and i can try and help you with it if needed question: how come you using VM- PERFORMANCE IS NIGHT AND DAY BETTER WITH PC! At least with that VM your speaking of. Proxmox I hear is good. Im learning about it some. Seems ok . Seems inticate though GPU Passthourgh and all these new "uncharted Waters" lol. Hit me up if yo u run into problems

Ok I see. I understand now! Thanks for clarifying that Slice I appreciate that! Hope all is going well for you and taht your doing allright considering all the mess thats going on in the world today! But is Good to hear from You! Peace my Brother with Respect!