Jump to content

Hervé

Administrators
  • Posts

    10027
  • Joined

  • Last visited

  • Days Won

    561

Everything posted by Hervé

  1. Strange request... Without proper CPU power management in place, you CPU should operate at LFM (800MHz or 1.2GHz, I don't know) and HFM (2.7GHz), i.e. switch between them two with no intermediate speeds and no Turbo boost. You'd experience reduced performance because of this, a much slower system and probably reduced battery usage; it's not the recommended way to run your Hackintosh. But if that's what you want, simply remove your generated SSDT from your EFI/Clover/ACPI/Patched folder.
  2. Please try and post in the correct sections. You keyboard and Touchpad will work wih Dr Hurt's recent ALPS TouchPad controller kext. Versions R4, R5 or R6. They're available in his dedicated thread of the R&D->Kernel Extensions subsection.
  3. Is it a DW1502 or DW1702? What do tools such as DPCIManager or lspci -nn Terminal command show? A card based on Atheros AR9285 (168c,2b) works under OS X with the DSDT patch that declares it compatible with AR9380 168c,30 for instance. The card is 2.4GHz only so it won't detect 5GHz networks by the way...
  4. Don't waste your time on this model. It uses an eDP connector for the LCD screen and that's not supported on 1st gen Intel HD graphics. As such, the best you can get is partial graphics acceleration which leads to poor system performance.
  5. You need to get your Ethernet card declared as en0. You can check that out through Terminal command ifconfig. If your wireless is en0 and your LAN en1, then remove all interfaces from the Network PrefPane, then go to /Library/Preferences/SystemConfiguration and remove all network plists. You should then be Ok after reboot.
  6. That's not how I would have patched the ARPT device. If Jake's DSDT does not bring the card to life, try the attached revised version. 'goes with the vanilla AirPortAtheros40 / IO80211Family kexts. DSDT.aml.zip
  7. No, it does not work that way. Sorry. That card reader may just be unsupported.
  8. Please post a zipped copy of a saved IOregistryExplorer output + your DSDT. I'll patch it. You can learn how to patch a DSDT on the side.
  9. Be extremely cautious with pre-patched kexts because if they bear a lower or identical version than the vanilla kext of /S/L/E, they won't load from /L/E. You can easily verify that by replacing the vanilla copy located as a PlugIn of IO80211Family kext. The DSDT patch is provided in the inventory thread linked in post #2. That's what you should use as a permanent and sustainable solution. The kext patch would likely be required after any update or upgrade. You can trust me on this, I had an AR9285 card in the recent past.
  10. Quite the contrary actually, the patch only works on PCIe devices but it's for O2 Micro readers. There are no DSDT devices for USB components and USB card readers usually work OOB or not at all. @giang_asl_8, I'm afraid the O2 Micro patch is not suitable for the Realtek RTS525A card reader which remains incompatible with OS X/macOS. VoodooSDHC does not bring it to life either.
  11. The E6220 is one of the best laptops in terms of compatibility with OS X/macOS, have no doubt about that. There's obviously something very wrong with your setup or USB installer but I cannot say what. Maybe you're not using a genuine copy of El Capitan installation app. I've never encountered or heard of the message you reported: "no task-access server configured! The system will not get very far".
  12. What did you create your USB installer from? Are you sure you followed every single step of the guide without sidetracking?
  13. To avoid any confusion on the matter, only apply the MBR patch if attempting installation on a HDD with MBR partition scheme. This is obviously not applicable if you install on a HDD with a GUID scheme.
  14. And please post in the E5xxx Support section, not the EDP Guides one. Thanks.
  15. There's a thread listing all the BIOS recommended settings in this very section. Please read it. With a bit of attention you normally can't miss it, it's the 3rd one down the list... Re: SSDT, I think you got it all wrong. Indeed, you start with no SSDT. Look up Pike R Alpha's blog for the CPU power management SSDT generator, it has a full set of instructions re: usage.
  16. Is your BIOS configured as per recommended settings? You have a different CPU than fitted to my own E6220 but my guide does stipulate that it's not a problem, you just have to generate your own CPU-specific SSDT using Pike R Alpha's well known generator script (you'll find it with a Google search). As such, make sure you have NullCPUPowerManagement in /E/E when you boot your USB installer. If you use the pack I posted, you should normally boot in verbose mode and without cache. So you should see everything that happens being displayed on screen.
  17. Whether you want to dance around your chair at the same time with feathers in your hair and singing wouhou is up to you.
  18. That's not the correct way to install it and that's not going to work. I assume you use a myHack USB installer and you need to run myHack to install the Extra folder on the key. It's the only way kexts will be taken into account and the old ones removed. NB: there's no need to quote every single message you directly reply to.
  19. So you used the pack I had posted in post #11 of that thread you linked? How did you install it on your USB installer? You could probably upgrade your BIOS to the latest version A10. Make sure it's configured as per the D620 recommended settings provided here.
  20. Restart and when Chameleon kicks in, press any key to interrupt the bootloader and manually add -f -v flags; this should then show you where it hangs. You did not say so I'll ask: do you have the GM950 model or the nVidia?
  21. Well go through the file and list your various hardware components in a similar fashion to those posted here for Dell E6220 or here for HP 8560W for instance. There are sites on the Web that'll help you identify hardware by PCI ids and vice-versa.
  22. The overall process used for those laptops is fully applicable to your HP laptop, not the bootpacks. Those bootpacks contains BIOS tables specific to the models + drivers (kexts) specific to the hardware components fitted to them, so you cannot reuse them. Only some drivers may be re-used if you have the same hardware. Other than your IDT 92HD81 (codec 7605) HDA audio (different from what is fitted to the E6x20 or E5x20) and your unsupported Intel wireless card, you've not listed the rest of your hardware specs; maybe you can start with that: LAN, bluetooth, USB, card reader, video outputs, trackpad, etc. List the exact model specs, ideally the vendor + device PCI ids. Example: Intel 82579LM GigEthernet, O2 Micro 0Z600GJ0 SD card reader, ALPS V3 Rushmore TrackPad. Please note that your HP laptop will probably require the lapic patch to avoid a lapic KP. Can be applied on the fly through Enoch or Clover or by limiting CPU to 1 single core (not the desired long term/permanent option).
  23. Lookup existing guides for SandyBridge/HD3000 laptops in our EDP->Guides section. Obviously the DSDT/SSDT specific parts won't be applicable to you at this stage. You'll have to extract and patch or get your tables patched in due course. You will need to mess with your laptop (it's the only way to learn and you will fail several times before you succeed) but you can't break or damage anything. I suggest you experiment using a dedicated hard drive.
  24. Well anything related to wireless and bluetooth obviously! I cannot guess what you may have done in that respect with your Clover configuration, what kexts you might be injecting through Clover or what kexts you might have added to /S/L/E or /L/E. I've no crystal ball...
×
×
  • Create New...