Hervé

I don't think you should be using that SSDT-PNLFCFL on a Haswell laptop. Given that you rename GFX0 to iGPU in your OC config, I'd have used the regular SSDT-PNLF table, as is, i.e. with references to GFX0. NB: I note that you've not disabled the nVidia dGPU; is that normal?

Brightness control restored in 11.3 on my E6230 after removing device PNLF from the patched DSDT (it was a very old patch of mine) and adding SSDT-PNLF table (from Dortania). @draskostar watch out with your ACPI settings with regards to iGPU: if you have renamed GFX0 to IGPU in your patched DSDT rather than through bootloader's ACPI device renaming, you'll also have to rename GFX0 to IGPU in SSDT-PNLF too.

That's one of them (Slice's). I use this one (old versions by Rehabman forked off Kozlek's work): https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/

Maybe VirtualSMC and its sensors are not appropriate for iStats Menus app; you could try to switch to FakeSMC and its sensor PlugIns to compare behaviour. I've just tried v5.32 on my old C2D Vostro200 desktop (all my Hacks run with FakeSMC) and the usual CPU, thermal or other fan and SSD sensors were reported and shown.

Must be a local error on your side; just tried from a Win10 PC with Edge and no issues at all. Whether logged in or not.

Lost brightness control too on my E6230. I have PNLF device built into the patched DSDT; it was something I had added years and years ago; need to remove that and opt for SSDT-PNLF table as posted on, say, Dortania. This may fix the brightness issue.

@Sadhiq please try and use the forum Search facility in the future... Thank you.

@Leonardo.schellenberg Mieze just posted a new version v2.4.2. https://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/page/63/?tab=comments#comment-2756300

Try and follow the Dortania documentation for OpenCore: https://dortania.github.io/OpenCore-Post-Install/#how-to-follow-this-guide https://dortania.github.io/OpenCore-Post-Install/misc/nvram.html#cleaning-out-the-clover-gunk

ACPI tables: You already have the SSDT-PNLF in your OC ACPI folder, so all is covered. You need to remove SSDT-PLUG though and disable it in your OC config. Graphics/Capri framebuffer properties: All suitable/necessary properties are already injected in your patched DSDT (see _DSM Method under IGPU device). Kexts: Remove VoodooHDA and replace with AppleALC (its' a Lilu plugin). Audio will then work with alcid 12. You shouldn't use USBInjectAll alongside USBPorts. Latter is usually generated having initially booted with the former. So try without USBInjectAll to begin with. I invite you to consult my E6230 guides for details of the kexts I've used and what they do. Versioning is also detailed in case you need to update those that may be old. It's important that you get NVRAM working as this will ensure active/selected screen brightness is retained throughout reboots or sleep/wake cycles.

Backlight should work OOB with the right settings in place: Capri framebuffer usual patching + SSDT-PNLF. TouchPad should also work OOB with the VoodooPS2Controller available in my E6230 guides; the kext works 100% in all E6x30 models of the range. Maybe yours is faulty or possibly disconnected; check that out. Latest BIOS are Ok to use for sure as long as you apply the FBMem patch that reduces memory from 16MB to 8MB (glitchy graphics otherwise).

A few things to bear in mind to avoid all possible confusion: in section #3, the EFI partition may not exist on the USB key selected to make the USB installer and Clover may not be installed on that USB key either. to cater for this, section #2 should have stipulated the important step of installing Clover on the USB installer. This is done by running the (previously downloaded) Clover installation package and targeting the USB key. It's an absolutely mandatory pre-requisite. Clover installation settings/options should ideally be provided here too. in the same respect, section #5 completely missed 2 x essential steps to make the HDD/SSD bootable: install Clover on it (kind of obvious but it's not even mentioned) copy the contents of the provided Clover pack into the Clover EFI folder of the HDD/SSD's EFI mounted partition (also kind of obvious but missing) Without those key steps, neither the USB installer, not the target HDD/SSD will be able to boot Clover and the macOS installer or the installed macOS partition. Also note that (hidden) EFI partitions can be mounted through other tools or methods such as: Clover Configurator tool Terminal command sudo diskutil mount <diskNsM> where <diskNsM> is the identifier of the EFI partition shown by command diskutil list

With a mechanical HDD, boot time should be around 1min, knowing that APFS has never been fast on legacy HDD and is really meant for SSDs.

Partition scheme of the USB installer makes no difference. You have to make sure you have a retail copy of Snow Leopard. Try and boot with -f -v boot flags. We have a fully tunable Search facility on the forum, don't hesitate to use it.

As stated in that other thread: you need to set ACOS to 0x80 for Darwin (same as WIN7) in OSID method or any value > 19 because EV5 method (which calls BRT6) is only called if OSID>=20 (it's clearly shown in the script of that other thread) you ought to try values 0x366 and 0x365 in your BRT6 patch rather than 0x406 and 0x406 See my E6220 / E6230 / E7250 / 7490 guides for details.

It's indeed a D620 with nVidia graphics. Can't remember if the D620 10.6.8 packs will work with 10.6(.0) but, from memory, it should. We have copies of myHack v3.1.2 and v3.3.1 here and they're fully kosher so no need to get those off Web archives. Make sure you use a retail version of SL 10.6(.0) as only the retail copies have the full installation files that are required. Retail copies existed for 10.6(.0), 10.6.3 and 10.6.8. The other versions exist as recovery sets only and are no good for fresh installations. As you wrote yourself, CoreDuo means SL only, not Lion. Ideally, you may want to consider replacing your current CPU by a high-end FSB667 Merom Core2Duo T7x00 (T7200, T7400 or T7600). It's old stuff but these cost pennies today on the 2nd hand market and would allow you run run Lion (or MLPF'ed ML if you were game). Make sure you've configured your BIOS as per the recommended settings posted in the dedicated thread in this very section. MBR patch is only of any use if you try or want to install SL on a disk with MBR partition scheme. If SL is the only OS you intend to run, just reformat it from your USB installer as GPT/HFS+ (Mac OS Extended) using Disk Utility once you reach the main installer screen. I'm no longer 100% on this (it's old stuff and too many years have passed) but it may well be that the DW1397 or DW1395 (BCM4312 wireless card) in that D620 are causing trouble so you may want to try and disable Wireless in BIOS until you've actually installed SL. Good luck! NB: lspci -nn is more useful command than lspci -vv.

It's the fbmem patch that prevents the graphics glitches and defects as explained in our HD4000 patching guide; so make sure you implement it. You do not modify/patch memory count, pipe count, port count or stolenmem with LoRes/4-port layout 0x01660003, only with HiRes/1-port layout 0x01660004. Therefore, your framebuffer patch for iGPU@2 should set the following parameters to the following values: ig-platform-id -> 03006601 // LoRes/4-port Capri mobile layout framebuffer-patch-enable -> 1 // enables framebuffer patching framebuffer-fbmem -> 00008000 // reduces framebuffer memory from default 16MB to 8MB framebuffer-conX-enable -> 1 // enables conX patching, where X is your identified connector for HDMI output port framebuffer-conX-type -> 00080000 // sets conX to HDMI type, where X is your identified connector for HDMI output port hda-gfx -> onboard-1 // for HDMI-audio and nothing else. Target connector will most probably be con1. In the future, please post system's specs (add those in signature!) and copy of your bootloader config so that it can be properly read with the relevant tools, rather then leave people use Base64 to Hex/Text converter to decode your patches... Here, we assessed it was a Clover config but also specify this sort of things. For a complete and detailed set of information on framebuffer patching, I invite you to consult the Whatevergreen user manual: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

Not that it'll help you much but I prefer to advise you that, afaik, no Hackintosh laptop ever got its Wifi LED to lit when running OS X/macOS. It's something that appears universally unsupported.

You have to properly create your Big Sur installer with the usual createinstallmedia command. Process is explained on Apple's web site and in most of our published guides so look it up. OC will then offer you the option to boot this Big Sur installer. You can't just copy the macOS installation package on the USB key, that will do absolutely nothing.

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.3.0/2.4.0. You'd also read this in the comments left for this driver posted in the Download->kexts->LAN & Wireless section at IM.

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.

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.

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).

[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 Apple’s latest SMC list. Having noted some CPU + graphics performance issues under Mountain Lion on his D630 nVidia (Intel T9300 2.5GHz FSB800 CPU, nVidia Quadro NVS 135M GPU), Mario was initially looking at pushing up the GPU clocking to fix video juttering and getting SpeedStep to run better. I joined him in the testing phase and we were able to obtain native SpeedStep operation + improved GPU clocking (and therefore improved graphics/video performance) on our respective D630 nVidia (ML 10.8.3) which, by chance, run on the same Penryn T9300 CPU. Our tests were only conducted under ML, i.e. in 64bit mode. By default, EDP uses FakeSMC v4.0 and MB3,1/MBP3,1 SMBIOS for the D630 laptops. Mario and I had already changed SMBIOS from MBP3,1 to MBP4,1 using Chameleon Wizard, but after thorough testing, video/graphics performance was found not to be 100% optimal and some juttering could be observed when watching video or switching rapidly between desktop screens through key-strokes such as Ctrl-UP, Ctrl-DOWN or Ctrl-LEFT. Looking at Apple’s latest support page for EFI and SMC Firmware updates for Intel-based Macs that provides version details, Mario installed FakeSMC v5.1.59 and edited the kext plist to try different SMC versions. In addition, Mario was not entirely satisfied with EDP’s emulated SpeedStep facility (VoodooPState kext + PStateMenu app) which was required to obtain CPU throttling: without it, the T9300 CPU would only run at its lowest multiplier/frequency (x3 / 600MHz!) and with it, he found frequency changes a bit lagging. After some trials, we found that editing FakeSMC plist to use SMC versions of MBP5,1 and loading MBP5,1 SMBIOS plist gave us excellent graphics/video performance with nVidia GPU core/memory clocking efficiently between 275/300 and 400/594MHz during video playouts, thereby rendering an extremely smooth video and leading to an excellent quality of experience. As an added bonus, we also found that SpeedStep was now natively operating and that CPU stepping appeared much more rapid than with emulated SpeedStep. Mario also reckons the battery lasts a little longer. Naturally, emulated SpeedStep has to be removed in order to verify native SpeedStep operation, so if you have emulated SpeedStep installed, remove VoodooPState.kext from /Extra/Extensions (remember this will require a subsequent myFix (full) to rebuild kext cache) and remove PStateMenu.plist from /Library/LaunchAgents. The same applies to IntelCPUMonitor kext which goes with older FakeSMC version (v4.0 for instance) and now has to be removed. Note that systems based on Intel 945GM/PM chipset must keep VoodooTSCSync kext, whilst other systems can get rid of it. All in all, this has made for a substantial performance optimisation of our D630 nVidia Hackintoshes and something really worthy of a trial on other systems. Here are details of things to do: 1/ make a precautionary backup of your existing FakeSMC kext (found at usual location in /E/E folder) 2/ download a copy of FakeSMC kext v5.1.59 (64bit only) to your desktop 3/ download a copy of Plist Editor Pro 4/ lookup for the Apple Mac model that best matches your own Hackintosh at EveryMac.com (you may also look at the various profiles available in the Chameleon Wizard SMBIOS tab) 5/ in Apple’s EFI and SMC list, identify the SMC version most likely to match your system specifications and take good note of it. This is the information required to be used subsequently. 6/ open up the FakeSMC kext package and, using Plist Editor Pro, open up the Contents/info.plist file 7/ in the upper part of the editor, open down IOKitPersonalities->SMC Device Emulator->Configuration->Keys 8/ At the bottom of the Keys list, open down REV, RVBF and RVUF. By default, FakeSMC is using SMC version 1.30f3 which is displayed in Data field as 01300F00 0003. 9/ in order to modify FakeSMC to a different SMC version, all of these 3 keys have to be modified. This is done by double clicking on the 6bytes value and replacing it by the targeted SMC value. 10/ Once this is done, close Plist Editor Pro, move or copy the modified FakeSMC kext to /E/E, run myFix (full) to repair permissions and rebuild cache. Then, with Chameleon Wizard, change your SMBIOS plist to the new targeted version. 11/ download HWMonitor tool v2.3.7 and run it (close and remove any other or previous version you might have been using). This particular version supports the enhanced features of the newer FakeSMC kext such as GPU/memory frequencies, thereby providing improved monitoring capabilities. Click on the associated menu bar icon and configure it to display your desired items (eg: CPU T°, GPU T°, GPU/mem frequency) and to run automatically. 12/ Your Hackintosh can now be rebooted. BIOS IDA settings may be re-enabled, depending on CPU model. In the case of our D630 laptops with T9300 CPU and nVidia Quadro NVS 135M, Mario and I tried the SMC version listed for the 15″ MacBookPro5,1 -> 1.33f8 (SMC 1.2). This translated to 6bytes Data 01330F00 0008. On reboot, video play out was extremely smooth (even whilst doing desktop screens swaps) and GPU core/memory frequencies could be seen switching between 275/300 and 400/594MHz. The frequencies showed idling at 168/100MHz. These basically matched the expected/documented specifications of the nVidia Quadro NVS 135M whereas, when using the MPB4,1 profile, the GPU frequencies did not seem to go beyond 275/300MHz. On removing emulated SpeedStep (by removing VoodooPState kext from /E/E and PStateMenu plist from /L/LaunchAgents), HWMonitor also allowed us to see that SpeedStep was natively running as CPU clock stepping could clearly be observed. We even noticed that IDA could be re-enabled in the BIOS without impacting the FSB. Perfect! The only little bug I noticed with HWMonitor 2.3.7 is that reported GPU/memory frequencies tend to get stuck at highest values after a while. However, the reported GPU T° tends to indicate that it is not the case… Using same MBP5,1 settings, similar results were observed on D830 nVidia 135M with T7250/T7500 CPUs under ML 10.8.3. Compared to the D630, the differences were lower GPU memory frequencies (whilst GPU core clockings were identical) and no IDA support with that CPU family (re-enabling IDA caused FSB to drop from 200 to 182MHz, thereby lowering all CPU clockings by approximately 10%). So, to your keyboards lads and good tuning! And, once again, thank you Mario for the research work. NB: most of this derives from Prasys’ own work. EDIT: Kozlek has updated these FakeSMC kexts & plugins since this article was 1st published. One major change for us is the ability to compile the code in 32bit mode and apply this tuning to our Hackintoshes that run 32bit kernel only: I’m now getting native SpeedStep on a D630 Intel X3100 with a 2.2GHz T7500 under Lion 10.7.5 (no IDA support). EDIT #2: Aug 2013 New tests were conducted with Kozlek’s FakeSMC v5.2.678 in 32/64bit mode. All Ok on numerous systems that we’ve tested. Don’t hesitate to use and try by yourself. More recent versions of HWMonitor also provide more information, so I’d recommend to use HWMonitor 5.2.678 too. Tests were also done with 5.2.755, but not all systems seemed to support that version. View full article