Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Hervé last won the day on April 6

Hervé had the most liked content!

Community Reputation

1099 Excellent

About Hervé

  • Rank
    Admin, Chief tester & Technical writer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Did you verify your cable was Ok? LAN card set to auto-neg or some fixed 10/100/1000Mbps settings? MAC address of your card sure is listed in IOReg. Or maybe version 2.3.0 of the kext is inadequate for Big Sur. Try version v2.4.0 posted by Mieze on her Github repo and at InsanelyMac. Also check the latest info posted on the dedicated RTL8111 thread at IM. That's where Mieze discusses her development work on the driver and where people report on their experiments. If v2.3.0 or v2.4.0 do not work, try the previous versions; I've seen people reporting issues such as yours with version
  2. Realtek RTL8111 driver is clearly loaded and Ethernet card appears functional. What's not working of course is the Qualcomm Atheros QCA6174 WLAN card; that's unsupported under OS X/macOS and will need to be replaced.
  3. For screen brightness, add the SSDT-PNLF.aml table; it's missing. Please note that you should: not use 2 x SSDT EC tables, only one to keep things clean and avoid confusion. in the same respect, review the ACPI renaming patches you've configured in your OC config file; for instance, I see at least 3 x patches for EC device and I guess only one applies. Same goes for USB or audio devices. Of course, those that do not apply make no harm but it's a little messy.
  4. Big Sur is not known to run slower than its predecessor so I'd say that you've either lost CPU SpeedStep/power management (and laptop runs at LFM) or you've lost graphics acceleration. You should be able to verify CPU operational status through apps such as HWMonitor (if you've installed FakeSMC's PlugIns or VirtualSMC PlugIns) or Intel's Power Gadget tools and graphics acceleration through the normal checkups (About this Mac, LaunchPad, Finder's bar & Dock translucency, etc.). Ideally, post your debug files or at least IOReg extract and zipped EFI folder (Clover or OpenCore).
  5. [Recovered backup of old article from 5th May, 2013] So, you got Mac OS X running on your favourite PC and you want to optimise performance? A bit of fine-tuning might be possible with FakeSMC kext and SMBIOS plist. Your Hackintosh needs to be running on native CPU power management of course (with P & C States set in Chameleon boot plist), not under null management. Our R&D top man Mario (aka. Bronxteck) recently played around on the matter. Moving away from our EDP-provided FakeSMC, he used one of the latest FakeSMC versions and started editing it according to
  6. You're gonna need to be a little more forthcoming with info if you expect assistance. Please post: system's specs zipped OC EFI folder debug info such as a zipped copy of an IOReg extract
  7. There is no such pack posted here afaik but feel free to start on the matter. You could start by looking into the existing stuff posted in this very section for the Inspiron 5559.
  8. Jake Lo gave you a link that leads to what's pretty much a step-by-step guide and a very recent one too; all you have to do is follow it. You'll gain experience with OC by experimenting and it is really not that hard to grasp. As a beginner, I found it easier to understand OpenCore than Clover.
  9. Very old and totally obsolete stuff nowadays but you can make your USB installer with myHack tool/app (available on this forum) and the relevant D620 bootpack (also available on the forum in this very section). myHack Requires an existing Mac, Hack or VM running SL 10.6, L 10.7, ML 10.8 or Mav 10.9. It's not supported on pre-SL and post-Mavericks versions. Make your USB installer and then install Mac OS X by following the on-screen guidance. The bootpack consists of the full Extra folder that you will need to point to and install when prompted so by myHack. If you're not prompted f
  10. Well, obviously, it could not have been done properly, so you need to revisit the steps you followed. You must have missed something along the way, maybe the boot file.
  11. You need a lot more than that to update OpenCore. You need to download the whole package and replace the various drivers you use, modify or suppress bootstrap, update resources, etc. Please refer to the OpenCore documentation on the matter. The packs posted here usually only contain the specifics for the target model, not the entire OpenCore arrangements.
  12. Bluetooth is USB-based and so should work once you sort out your USB ports problems.
  13. Try and cache CodecCommander kext from /L/E. I'm not sure it'll inject successfully from OC kexts folder, but you can always try.
  14. @kcmok Please note that hexadecimal values specified as DATA in properties injection must be entered in reverse byte order. So, if you want/need to inject graphics framebuffer layout 0x59160000, you must enter value 00001659. It is read byte by byte, from right to left: 59-16-00-00.
  15. Check your drivers settings; you appear to call on AudioDxe.efi which is reporting missing. So either you add it to your driver folder or you remove its reference from your OC config. OpenCore has zero tolerance for that sort of things and its the same for kexts and their order (re: PlugIns). One thing wrong and your boot fails.
  • Create New...