By default for Haswell HDAU, the kext injects RM,device-id= (0x0a0c). This kext, AppleHDAController, loads by PCI class, so you normally would not inject device-id for it, but to allow FakePCIID to work, you may need to inject RM,device-id (one of the supported IDs). The other two 8086:0d0c, and 8086:0a0c are supported. The purpose is to provide support for unsupported HDAU (native B0D3) or unsuppored HDEF (100-series, 200-series, 300-series) ) devices which provide HDMI-audio on Haswell(+) systems. 8086:0412 is the native device-id for HD4600 desktop.īy injecting 0412, AppleIntelFramebufferAzul and AppleIntelHD5000Graphics will load.Īnd since, FakePCIID will also be attached to these devices, it will successfully fool both kexts that the device an Intel HD4600 Desktop IGPU (0412).įor P4000 support, inject device-id 0166 (HD4000).įor P530 support, inject device-id 1912 (HD530).įor P6300 support, inject device-id 1622 (HD6200)įor HD620 KabyLake-R, inject device-id 5916 (HD620)įor UHD630 CoffeeLake, inject device-id 3e92 (UHD630) 8086:3e91 is UHD630 CoffeLake (typical 3e91 with i3 or other low-end CPUs)įor HD4600, normally fake device-id of 8086:0412 will be injected for Yosemite, as Yosemite does not natively recognize 8086:0416.
Some CPUs (i3-5005U for example), must spoof as 0x1626 to avoid hang at boot
#Fake cpu for osx install#
In order to cause the kext to be loaded against a particular device, you must also install the appropriate FakePCIID injector kext.
#Fake cpu for osx full#
To be used with AirportBrcmFixup.kext as replacement for FakePCIID_Broadcom_WiFi.kext (both will work, but with AirportBrcmFixup.kext, full functionality of FakePCIID.kext is not needed)
#Fake cpu for osx zip#
The separate folder 'injectors' in the distribution zip contains two extra codeless kexts:ĪppleIntelKBLGraphicsFramebufferInjector_3e9x.kext: Used for spoofing unsupported CoffeeLake as KabyLakeīroadcomWiFiInjector.kext: Used to load the native Broadcom WiFi kexts for unsupported devices. For troubleshooting, the Debug build can be used. It has a minimum of output to system.log. The Release build should be used for normal installs. In all cases, FakePCIID.kext must be installed with a kext installer (such as Kext Wizard). The properties must be present on the PCIDevice that is being hooked (the direct parent of FakePCIID).
The properties used by FakePCIID are described later in this post. In any case, a DSDT patch, FakeID configuration (Clover), or FakeProperties dictionary in the injector's ist will be required to inject the properties that FakePCIID can read on the IOPCIDevice. Note: FakePCIID_Intel_HD_Graphics.kext works for HD4400 mobile, HD4600 mobile, HD4200 mobile, and HD4600 desktop. Custom injector kexts can be created for other devices. The distribution ZIP provide has four such injector kexts, which are described below. The FakePCIID.kext ist has no built-in IOKitPersonalities, as it is generic and not built to suit a specific purpose. In order to attach FakePCIID to a given IOPCIDevice, an injector kext must be built that IOKit can use to match against. This technique can be used instead of patching binaries that may check for supported device-ids (or other PCI IDs) in their IOService::probe or IOService::start method.
#Fake cpu for osx driver#
The purpose of this kext is to attach to any IOPCIDevice so it can provide alternate PCI ID when another driver attached to the same device requests them.
0 kommentar(er)
