Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Make sure to select 'Reset NVRam' at OC picker after the changes.
  3. @Jake Lo HE HAS RESPONDED I'm using VoodoOS2Controller-R6, as linked in the trackpad part of this site.
  4. What do you mean by No Luck after just adding the files and replacing the Config?
  5. @Jake Lo I need the man, the myth, the legend himself on this case.
  6. @Jake Lo i replaced the kext and acpi folder with the ones you gave however after replacing system gets stuck at apple logo and then restarts . i even tried adding only the contents of acpi and kexts folders that you gave into already existent folder but no luck
  7. Hey, it's been a while. The RAM in my Dell Latitude E5450 recently died, so I had to replace it. This is the only bug I know of in my Hackintosh. Basically, my two finger touch scroll on my E5450's trackpad has an odd bounce-back effect.
  8. Last week
  9. hey did you get it working? Insert other media
  10. sorry for the late response. i already change my hardware to lenovo m720q since i got the i7 version in cheap price, so cannot provide the bios config. last time i checked the sleep, i'm still using the DP cable. i tried to sleep & wake by pressing the keyboard. i don't have the issue. no testing with the HDMI cable one. in my lenovo i have wake issue too, but fixed by doing this. https://dortania.github.io/OpenCore-Post-Install/universal/sleep.html#fixing-gpus
  11. @PrabhuR Sincerely, I didn't test it and I will not test it in that machine. On the other hand, I tried to boot my internal win10 (on another pc) through external hard drive with opencore. The result is a continuous bootloop from the very beginning. I suppose this behaviour is related to the way opencore treats windows: as a bootcamp partition. I will not modify my internal windows partition so I will try to do this (and I recommend you to do the same): create a partition on the external hard drive suitable for your windows partition, clone the internal win10 partition to the external (using CCC, for example) and follow the dortania guide about multiboot (chameleon, stolen and rebranded) systems. Then, try to boot the external win10 partition using opencore. I hope I explained it properly and sufficiently clear. I hope..
  12. If your DSDT is patched properly then yes, otherwise you''ll need boot from BIOS.
  13. I will upload my EFI file later today... All seems to be working now...
  14. That worked... will test the drive read write shortly i was able to format and partition
  15. try setting bios legacy enable secure boot disable
  16. @MrTony99Have you DGPU Nvidia or AMD???? My Laptop Dell have only IGPU , in config add bot arg -wegnoegpu , if you find it useful post photos of the Bios . I am working on new SSDT, where I introduce DSM methods, to increase compatibility with MacOS, as soon as I finish and test everything I will put it on my Github EFI.zip test This Add DSM , example for HDEF intro Layout
  17. I am having this problem after booting mac os 10.15.6 please help me
  18. Following BIOS update to v1.16.0, I revisited the patched DSDT since it was (finally) also causing a reset to me. I dumped all tables from BIOS and came to realise I had applied the brightness keys patch to a Clover pre-patched DSDT! I therefore re-applied the patch to the raw DSDT. My 7490 now boots Catalina without reset and brightness keys are fully operational. I've also updated the patch code above to return those Clover pre-patched lines to full vanilla code (XOSI returned to _OSI and XSID returned to OSID). Patched_DSDT_Lat7490_BIOS-1.16.0.aml.zip I invite Latitude 7490 users to test this revised patched DSDT and feedback to me by PM so that I can update the bootpacks accordingly. In case of issues (system reset), select BIOS.aml DSDT table in Options->ACPI patching->Dsdt name at Clover main boot menu to load the raw DSDT at macOS startup.
  19. Try adding this patch to Kernel patching, works for Catalina, not sure still for Big Sur Identifier = com.apple.driver.AppleAHCIPort Find = 40600200 Replace = 00000000 Comment = Patch Hotplug / Caddy
  1. Load more activity
  • Popular Contributors

  • Member Statistics

    • Total Members
    • Most Online

    Newest Member
  • Our picks

    • Released July 15th, 2020.
      Build 19G73.
      This is most probably the last major update for Catalina with only Supplemental Updates or Security Updates to follow. Safe to install on our Hacks without specific issues or surprises to expect. Blessing issue remains for those of us who experience it since 10.15.5 and this requires a reset of NVRAM to avoid. Failing that, 10.16.5 still installs Ok but the temp update partition remains until the macOS Install Data folder located in /System/Volumes/Data is manually deleted.



      Security updates 2020-004 for High Sierra (17G14019) and Mojave (18G6020) released at the same time.
      • 0 replies
    • A few of us with old C2D/C2Q platforms (mostly desktop) experienced CMOS reset since updating to 10.15.4.
      During troubleshooting, the issue was pinpointed to 10.15.4's new boot.efi file (located in /S/L/CoreServices) which, as many of us noticed, was displaying some new info when booting in verbose mode.
      Initially, replacing 10.15.4's boot.efi file with that of an earlier Catalina release or even an earlier macOS version was found to get rid of the problem without adverse affect on booting Catalina 10.15.4. However, this only worked for Hackintosh systems running Clover, not for systems running OpenCore.
      File ownership needs to be re-adjusted to root:wheel upon replacement:
      sudo chown 0:0 /S*/L*/CoreServices/boot.efi  
      Following further troubleshooting with vit9696, telepati and a few others, vit9696 worked out a temporary workaround for OpenCore in the form of a 5-bytes NVRAM variable wake-failure set to 00 00 00 00 00. All details and explanations are available here.
      For Clover users, this workaround alternative to replacing boot.efi can implemented as follows in Terminal:
      sudo nvram wake-failure=%00%00%00%00%00 Of course, this needs NVRAM to be working properly on the target Hack. For Hacks with no natively-supported NVRAM, it is required to install EMUVariableUEFI.efi Clover module + RC scripts on the Catalina boot volume. Once the variable is set and the system rebooted to take it into account, no more CMOS reset on rebooting from 10.15.4.
        • Thanks
        • Like
      • 0 replies
    • Bronxteck recently reminded us of links Apple publish in relation to creating bootable installers for OS X and macOS from El Capitan 10.11, so here's a link to the related main page:
      Very useful as a replacement to the old AppStore method that allowed registered users to re-download an OS X/macOS installation package if they had already done so in the past.
      12GB required for USB keys/flash disks.
      Whilst the information is obviously meant for Apple Mac computers, it's nevertheless 100% relevant to the 1st phase of creating USB installers for Hackintosh computers, the 2nd phase being the necessary installation of the bootloader (Enoch, Clover or otherwise).
        • Like
      • 1 reply
    • A few things are required to successfully run macOS Catalina on a Hackintosh, whether through a new/fresh installation of a direct upgrade from a previous OS X/macOS version/release.
      1/ Laptops Embedded Controller:
      Since beta #5, macOS Catalina requires Embedded Controller (EC)-related patching for many laptops. It's therefore important to check your Embedded Controller device (aka "PNP0C09" id) in DSDT/ACPI and apply the mandatory device renaming to "EC" in Clover's config (or directly in DSDT), failing what, Catalina will never boot.
      Most Dell laptops since the era of the Latitude E4x00/E5x00/E6x00 range have an Embedded Controller device called "ECDV" in DSDT; in Clover, the necessary ACPI device renaming is as follows:
      Description: Changes ECDV to ECFind:  45434456Replace: 45435F5F Other known names for the Embedded Controller include "H_EC" or "EC0". If you find no Embedded Controller device in ACPI, this patch is not necessary.
      2/ Clover:
      Clover needs to be at a minimum version supporting Catalina. Versions r503x, r504x and r505x are generally Ok. At the date of general release of Catalina, we recommend using Clover r5093 as the minimum version. Clover versions are available off Dids' Github repo.
      3/ Add-on kexts:
      Lilu and associated plugins also need to be at versions updated for Catalina. At time of writing, we recommend the following minimum versions, all available off Acidanthera's Github repos:
      Lilu v1.3.8 Whatevergreen v1.3.3 AppleALC v1.4.2  
        • Thanks
        • Like
      • 0 replies
  • Create New...