Jump to content

Bronxteck

Administrators
  • Posts

    5778
  • Joined

  • Last visited

  • Days Won

    124

Everything posted by Bronxteck

  1. -64 is just a leftover from when clover was 32 bit compatible so it is just a naming convention means nothing any more. as long as the file name ends in .efi you should be good.
  2. we had a few projects on this forum in the past i dont know if this one is still valid in 2019 but you can try it
  3. aircard watcher is ancient. it was ment to run on OSX 10.4 and 10.5 i would not expect it to work on 10.14.x but i guess you can try this https://kb.netgear.com/22853/How-do-I-install-or-upgrade-my-AirCard-Watcher-software-in-Mac-OS-X
  4. it will probably wipe out your EFI partition so just back it up to a bootable usb. if it does wipe out your EFI then you can safley boot off of the USB then transfer it back to your efi partition once you are back in the OS. run a test boot first off of the usb after backing up just to be double safe.
  5. seems that you have to manually compile clover with the option to enable secure boot then you have to digitally sign the binary's you compiled. should probably be done with official clover branch.
  6. did you try using your other EFI files. maybe that was the one you where using beforehand?
  7. try adding different PS2 kexts or maybe not use beast as an installer as you do not know what it is doing to help or not help you during install.
  8. have you checked if there is maybe another wifi card being injected through dsdt
  9. i have had that exact issue before. i do not recall my solution though. audio would show in Hebrew. i think it had to do with the audio patches. like find replace.
  10. you can always try connecting a usb keyboard and mouse and finish your install. at least then you can figure out your issues on a running os.
  11. maybe this info might help https://github.com/alexandred/VoodooI2C/issues/145#issuecomment-483464663 also https://github.com/acidanthera/VoodooPS2 looks like they might have added some I2c code and some alps code in the last few months looking at commits made.
  12. from what i remember he no longer has the hardware to develop with. moved on.
  13. that was the solution james90. he expects you to try follow his instructions. that's your next step.
  14. they should be ok to try but try them from usb first just in case or at least have a way to recover your current install.
  15. are they the most recent released versions?
  16. try adding whatevergreen kext and lilu kext to your clover other kext folder.
  17. you can try latest clover build. you can usually find them here https://github.com/Dids/clover-builder/releases
  18. i believe Viking1304 no longer hacks. that may be why your not getting responses.
  19. when was the last time you have cleaned out the dust from inside the machine? also maybe it needs new thermal paste on the cpu / gpu heatsinks.
  20. the solution is usually to stop restarting from windows and do a shutdown instead. then turn it back on and boot OSX.
  21. https://sourceforge.net/p/cloverefiboot/code/commit_browser you can look there for the changes between your old version and the changes made to the newer versions to determine if clover had something changed to impact your results. i would guess if they updated something in graphics detection then maybe thats why it works?
  22. " using DETECT mode in the clover, which let the OSX to load Kexts from the L/E first. " That is not completely correct. "Detect" will only work for detecting fakesmc in L/E and if so then load. clover is hard coded to first pull from "Other" folder best option is to use "Inject"
  23. try adding FAT-64.efi and partitiondxe.efi to your clover drivers folder
×
×
  • Create New...