Jump to content

Jake Lo

Moderators
  • Posts

    14365
  • Joined

  • Last visited

  • Days Won

    868

Everything posted by Jake Lo

  1. After installing Clover, did you copy the EFI from USB to the HDD? You could try adding a new boot option in BIOS pointing to /EFI/Clover/cloverx64.efi and move it to the top
  2. What version of BIOS are you on? When using the bootpack from this site, make sure you combine it with the Generic EFI and replace it to your EFI partition. Reason it's not seeing your drive is because it's missing HFSPlus.efi in /EFI/Clover/driver64UEFI which is included in generic EFI.
  3. Format an USB or SDcard to Fat32. Create a folder name EFI on the root, then place the above Boot folder with the Bootx64.efi inside the EFI folder. Alternatively, just add lilu.kext and IntelGraphicsDVMTFixup.kext to /EFI/Clover/kexts/Other
  4. If your USB is UEFI and you have Legacy set in the Bios, you'll see the USB twice. Under UEFI and under Legacy. What you could try is add a boot option under UEFI pointing to EFI\Clover\cloverx64.efi. Move the new boot option to the top and save. Reboot with verbose mode
  5. Shouldn't be under Legacy but on UEFI on top.
  6. Check your BIOS settings. If needed. Reset to default first. Then set to UEFI and AHCI
  7. what kext are you using on your Asus? If your system has Elantech Touchpad, then switch to ApplePS2SmartTouchPad.kext.
  8. All credits go to alexandred https://github.com/alexandred/VoodooI2C https://github.com/alexandred/VoodooI2C/wiki/DSDT-Edits https://github.com/alexandred/VoodooI2C/releases Try this DSDT, see if touchpad work DSDT.aml.zip
  9. Did you install AsusNBFnKeys.kext with the "Must have" DSDT patch? Method (_Q0E, 0, NotSerialized) { If (ATKP) { \_SB.ATKD.IANE (0x20) } } Method (_Q0F, 0, NotSerialized) { If (ATKP) { \_SB.ATKD.IANE (0x10) } }
  10. Boot with verbose mode to see the KP error. Boot to Clover, hit the spacebar. Select verbose mode from the drop down.
  11. Replace with this DSDT and then load the kext manually add Rehabman's latest VoodooPS2Controller for keyboard I2C.zip
  12. what's the keyboard look like, try karabiner-element.app. see my guide under post install remapping keyboard keys.
  13. I think this system has I2C connection. Try loading this kext. If it doesn't cause KP, then you could add it to /e/c/k/Other cd to directory where you have VoodooI2c.kext sudo chown -R root:wheel VoodooI2C.kext sudo kextutil -V VoodooI2C.kext VoodooI2C.kext.zip
  14. Replace with this DSDT, keep the rest DSDT.aml.zip
  15. Replace attached file and folders to /EFi/Clover Added patched DSDT/SSDT and updated Config.plist HP2337_v2.zip
  16. had you done this? 11. Make sure to disable hibernation as it's a prerequisite to get sleep & wake to work Ok on a Hackintosh: sudo pmset hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo pmset hibernatefile /dev/null
  17. Just did a clean install on 6430u (1366x768) with the Sierra bootpack, no popup issue as you'd encountered.
  18. Better check your BIOS settings. Select Load Default, hit apply. Then change to: UEFI AHCI Legacy Option ROMS disabled Secure Boot disabled TPM disabled Apply and reboot Note: You'll need to redo the DVMT again after BIOS reset
  19. Here, replace with these files in /EFI/Clover/ACPI/Patched Using the E7x70 v1.17.5 bootpack E7270_sleepFix.zip
  20. Use the "More Reply Options" on the lower right to attach the file I'm unable to open the link above No need to quote my reply
  21. Boot with the USB installer or the internal drive Go into Options when you see the Clover GUI, use the right arrow to navigate Select ACPI patching-> Tables Dropping-> Go all the way down and deselect Drop all OEM SSDT Check all the Drop "SSDT-xx" below that Select Return Change DSDT name: BIOS.aml Select Return, Return Now back on the main Clover screen, tap F4 on the keyboard Hold Cntrl+Alt+Delete to reboot Clover Boot into OSX Mount the EFI partition (USB installer or internal drive, whatever you used to boot in step 1) Compress and attach /EFI/Clover/ACPI/Origin folder here. I'll patch it for you. Could be a different BIOS setting or hardware you have on your system that's causing this issue.
×
×
  • Create New...