All Activity

@Slice So the only reason that the TMR, RTC and PIC IRQ ACPI patches don't affect Windows is because they are unnecessary? As I mentioned, I stopped applying IRQ patches after I started disabling HPET (which Apple did, I think starting with Mac Models in 2018).

@Slice We need to Write MBR ; See Script Clover_Duet Anyone want to use Clover-LegacyDuet # Clone the repository git clone https://github.com/CloverHackyColor/Clover-LegacyDuet.git # Put your Clover (EFI folder) on Clover-LegacyDuet repository # Run Clover_Duet.command Result You don't know how to use Clover Duet 🚫 Do not use this program on a disk where Clover or OpenCore is already installed!

so I've tried copying HP-EliteBook-840-G4>Packages>OC-EFI>EFI over to my EFI and when booting it never gets passed all the coding. I've tried making OC from HP-EliteBook-840-G4>Create_App.command and when booting it never gets passed all the coding. I've tried making OC from HP-EliteBook-840-G4>Packages>OC-Package and when booting it never gets passed all the coding. I can only boot from my original EFI folder that was successful making Big Sur.

The EFI for Open Core is still experimental, having some issues with USB mounting, DVD Drive etc. Keep in mind, I changed the EDID for the AOU FullHD Screen mod. If you use stock screen, use the stock EDID in Tlucks package. Bear in mind I'm using an i7-2720QM CPU so maybe CpuPM is not working properly. EFI T420 V1 Tluck.zip

Show your ioreg for this situation.

Good!

It's a pity Alder Lake iGPU has no chances in macOS. May be you can get to desktop in VESA mode. ig-platform-id = 0x12345678

TMR is obsolete device not needed by macOS nor by Windows. It just occupies IRQ.

well guys i tried ALL day till now to get weg and nblue working on my laptop, i cant do it. I tried all versions listed here, none worked, no device property numbers listed have worked, nothing. Im beyond frustrated, i've done ALL options here, im just beyond frustrated and ready to admit defeat and grab my win11 usb and forget it without one of us facetiming me and helping me. I've reached that lvl of difficulty.

After disconnect internally DVD this issue about errCode = 0xe0030005 during booting since Ventura 13.3.1 disappeared !

@MaLd0n Another way that OC can break Windows is with ACPI patches that unconditionally change ACPI. I do the IRQ fixes with SSDTs instead of OC ACPI patches (e.g., I don't use config.plist > ACPI > Patch for IRQ fixes) so that I can condition them on _OSI("Darwin"). Why don't the ACPI patches like "TMR IRQ 0 Fix" affect Windows? Just asking, because I don't know - not challenging your wisdom. Thank you. EDIT: Although, after I started disabling HPET, I no longer needed IRQ fixes.

EFI MorenoAv.zip

Hi, I'm also encountering ACPI errors and unable to boot macOS on my i5-1235U Alder Lake laptop with Iris Xe. I've experimented with Ventura and Sonoma. I can also help test the kext.

I've taken the liberty and updated the OC version and kext files within the attached EFI Folder. To give you the choice to try it on a spare USB Drive. You will have to furnish the config.plist with your machine data. I noticed from the 'Read Me' within, the OP did not use OCLP but the other alternative for wifi but that is easily remedied. ASUS-TUF-Z390M-Pro-Gaming-Hackintosh-Updated-OpenCore-Ventura.zip

I found this EFI Folder here - https://github.com/alienator88/ASUS-TUF-Z390M-Pro-Gaming-Hackintosh-OpenCore - on GitHub. I think the specs are not far off your own although I suspect the files and OC within are slightly outdated. Looking inside the ACPI Folder the owner is using SSDT files oppose to an all in one DSDT. Maybe doing a comparison to your own will give an insight to what your problem is/was??? Also it may encourage you to forgo the DSDT File and use SSDT Files like the attached EFI instead which I think will offer more scope and control of your rig. At the end of the day, whatever you choose to do good luck. Cheers. ASUS-TUF-Z390M-Pro-Gaming-Hackintosh-OpenCore-Ventura.zip

Well in my limited understanding of OC I don't know what breaks the windows, but I'll ask, if it is the DSDT that breaks the windows why with OC MOD the same DSDT don't break the windows, because of the no ACPI? Me too I don't know why that has happened bit when I have time I'll find it, comparing the others EFi with this one until I find the culprit...

@Slice I make a Package Clover-LegacyDuet It can install boot6 or boot7 Working also in Linux Work like a charm, testing by me on my Legacy machine DELL Optiplex 790 Do you think I should put it in the CloverHackyColor repository? See video in spoiler ⬇︎

@MorenoAv I would like you to understand that it is not the official OC that breaks Windows but the DSDT ( if this were the case we should all use OC Mod ) If you have ways to build the official OC and disable the DSDT as mentioned above you will see that Windows boot without problems ( maybe something like this is missing !? "If (_OSI("Darwin")) ... " but my skills are not enough for this ) As for the Wi-Fi, I honestly didn't quite understand where the problem was...probably as identified by deeveedee's long eye on an old ioskywalk. kext... However, it is important that you solved it

No worries man, use what work best for you but I think you should still try to learn what goes on under the hood. I suppose it's easy for me to say as I have loads of time on my hands after leaving the Rat Race behind and found a past time of Tinkering. If the truth be known, Tinkering caused me to have more crashes than Ayrton Senna but I always learned to have a bootable backup and not to do that thing I tried again. Trust me man, I have pulled many all nighters along the way causing me to sleep in the spare bedroom at times by a disgruntled wife.

@eSaF, @deeveedee, @Anto65, First I want to say that I use OC Mod because I used break all my Windows with the OC Official, I don't have a preference in what OC I use, I only want fewer problems with my OS. For that reason I am able to make EFI That worked following the guide for dortania and with SSDT's pre built I did it on several occasions, before trying the SSDT.aml from @MaLd0n. After asking @MaLd0n to make me a ssdt.aml I stayed with it, and it works almost all the time. None the less my problems with Wii were in macOS in Windows the Wifi worked. I hope to have explained all

I suppose OC Mod is useful for problematic systems but I am curious if our friend @MorenoAv could build his OC EFI the official way using the method in the Dortania Guide. Including trying the recommended prebuilt SSDT files or try building his own and see what result he gets. There is nothing wrong with getting someone to build an EFI Folder or specialised files for you but at least try and understand what the process entailed so that you can help your self with future problems. Sooner or later you will need to figure out what has gone wrong as you can't keep running to your original helper each time. In the past I too seeked help from @MaLd0n but as I built/upgrade machines, I learned to understand as much as I could by reading Guides and other members' posts and applying the same methods. Sometimes they worked and sometimes they didn't but I learned what worked and what didn't.

@MorenoAv Congrats. When you return with your explanation, I'd love to know whether the problem you reported was with Windows or macOS. I now realize I need to add another question to my repertoire: "You said Wi-Fi is not working on your hackintosh. Did you mean your hackintosh when running Windows or your hackintosh when running macOS?" To be honest, that question never occurred to me before. 🤣

I'm back and with one more re install and now I have WIFI, I remembered that o had an working EFI in my installation usb and now it works again... Thanks all you for your inputs and help, I'll be back and explain all

@eSaF agree that it is a good concept. I remember briefly following the OC MOD project (never using) and providing a suggestion that OC MOD include a feature which allows easily toggling between multiple versions of config.plist. But nothing that compelled me to abandon the official version (and now nothing that compels me to abandon the official released version of OC). My days of regularly building my own OC from a GitHub branch are over.

Mine is the official OpenCore, I did use the OC MOD when it was previously introduced by (can't quite remember the name without research) which was then abandoned by him because of criticism/ ridicule from certain quarters. This lead to others taking up the project, but I stopped using it as the updates at that time after was quite slow compared to the official OC. To be quite honest, the concept was/is quite useful as it is structured to negate dual booting with Windows by not interfering or influencing that install as far as I understood the idea.