-
Posts
10027 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
I guess you meant Turbo boost, not "overclocking". If Turbo boost, you need to generate your own CPU-specific SSDT with Pike R Alpha's well-known generator. The generator comes preset with support for a very big range of Intel Core CPUs. Identify your exact model of i7 CPU, then run the tool. http://ark.intel.com/products/codename/38530/Broadwell#@Mobile
-
Dell E6x20 laptops run Clover with BIOS in legacy mode... Go on, try it!
-
BIOS Security would be configured from... BIOS settings I guess. For the rest, no idea.
-
Actually I believe we have Dell mobile Precision workstation fitted with Quadro K2100M that run OS X with full graphics support. https://osxlatitude.com/index.php?/topic/8593-precision-m4800-brightness-slider-need-help/ Intel i7-4810MQ is indeed a Haswell CPU, so kernel power management patching is required. What's the error reported when you boot your USB installer?
-
Acer v15 nitro intel HD 4600 Apple boot logo problem garble
Hervé replied to hoanglongvu's topic in The Archive
To obtain graphics acceleration with your mobile HD4600, whether with Yosemite or El Capitan, here's my recommendation: use Rehabman's FakePCIID + FakePCIID_Intel_Graphics kexts. You can inject those by i) placing them in Clover/kexts/10.xx folder or ii) cache them by placing them in /Library/Extensions + repair permissions + rebuild cache. Presumably, you'll want FakePCIID_Intel_HDMI_Audio too in order to obtain audio through HDMI output via patched AppleHDA. If you're using VoodooHDA, then you have no HDMI audio so this kext does not apply. inject desktop HD 4600 id 0x0412 either through DSDT or through Clover config. OS X has no support for mobile HD 4600 0x0416. inject the appropriate Azul Framebuffer id either through DSDT or through Clover config (you can try Azul FB #12 0x0a260006 to begin with) If you opt for the DSDT patch, you need to add a DSM method to your IGPU device section (the device may be called differently) found at integrated GPU address 0x00020000. The patch should look similar to this (there are variants of course): Device (IGPU) { Name (_ADR, 0x00020000) Method (_DSM, 4, NotSerialized) /* DSM method to inject HD4600 data */ { Store (Package (0x06) { "device-id", Buffer (0x04) { 0x12, 0x04, 0x00, 0x00 /* Injects desktop id 0x0412 */ }, "AAPL,ig-platform-id", Buffer (0x04) { 0x06, 0x00, 0x26, 0x0A /* Injects Azul FrameBuffer #12 */ }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } ` For the final stage boot glitch, you need to patch the IOGraphicsFamily kext, either directly through direct binary kext patching or on-the-fly with Clover. The patch differs between Yosemite and El Capitan. Yosemite 10.10.2 and later -> replace 4188C4EB11 by 4188C4EB31 El Capitan 10.11.xx -> replace 0100007517 by 010000EB17 (works for my E6440 with HD4600). Afaik, replacement by 0100007417 was for 10.11 DP/DB versions. You can look these up on the web, there are literally tons of posts about these issues. Please search before posting next time. -
Good, it pays to do one's own research... and come to the same conclusion: not a Hackintosh-related issue.
-
Is this a genuine Dell Battery? Cheap alternative/replacement models are too often of poor quality and of very short life. Imo, this is not a Hackintosh-related issue.
-
I still don't see what makes you say your patched DSDT is not loading. You've not supplied much info on anything but I'll take your word for it. Good luck.
-
@efjoco: There is no problem with Chameleon as long as you use the Enoch branch (r2705 is current release and works perfectly). With that Enoch Branch, it's best to use the recommended kernel.plist that'll allow you to use or bypass kexts placed in /E/E: KernelBooter_kexts option that you set to Yes or No. If set to Yes, kexts placed in /E/E will be loaded at boot time, but not cached. This is same idea as kexts placed in kexts/10.xx with Clover. You'll need patched AICPUPM kext(s) to avoid KP at boot time, otherwise you need to use NullCPUPM. Copies of patched AICPUPM are available under the Support -> Mac OS X forum sub-section. Use NullCPUPM to start with and until you've: 1) installed the patched the AICPUPM kext 2) generated your CPU-specific power management SSDT with Pike R Alpha's well-known generator script. Chameleon is al ot less complicated to setup than Clover is. Then again it does not provide all those rich add-on features that Clover brings such as on-the-fly patching. Look up my D630 El Capitan guide for instructions. They're the same for all Hackintoshes, except you use the specific computer pack of course, not the D630's!
-
You can look up the AGPM tuning thread in the R&D forum sub-section. It covers the nVidia GPU of some models but the principles remain the same for IGPU. Compare the settings as configured for the models you mentioned, then feel free to experiment with the thresholds.
-
If the command: kextcache -Boot -U / gives errors, then command: sudo kextcache -system-prelinked-kernel should work without failure.
-
You mean you put the computer to sleep and wake it to gain Turbo boost again? I'd say this is ACPI, i.e. DSDT or ACPIBatteryManager related... Which version of the kext do you use?
-
I'd love to help but I've never kept a copy of all the bootpacks. Clearly, packs for the E6400/6500 are missing from the site, so you'll have to ask EmlyDinesh. He maintains the database and took everything offline all those months ago for a ("quick") revamp... Failing that, search for a pack in the existing threads. Sorry, can't do more on that front...
-
Look up for the model's bootpack. If it's missing, contact EmlyDinesh.
-
-> Topic moved to its own thread (nVidia model is different from Intel HD 3000's). Load BIOS default settings, then set HDD mode to AHCI.
-
CsrActiveConfig=3 is Ok. Indeed, it's absolutely necessary with El Capitan to prelink/cache unsigned (=non-Apple) kexts since that's only possible once SIP is disabled.
-
I had missed an important DSDT patch in Method _INI that is necessary to activate USB3.0 capability... * Before: Method (_INI, 0, NotSerialized) { Store (0x07D0, OSYS) If (CondRefOf (\_OSI, Local0)) { [...] If (_OSI ("Windows 2006")) { Store (0x07D6, OSYS) } [...] * After: Method (_INI, 0, NotSerialized) { Store (0x07D0, OSYS) If (CondRefOf (\_OSI, Local0)) { [...] If (LOr (_OSI ("Darwin"), _OSI ("Windows 2006"))) /* Simulates Win Vista mode in OS X */ { Store (0x07D6, OSYS) } [...] ` USB3.0 XHCI controller cannot be activated in I/O without this patch and will not register in IOReg @14! The patch applies to all OS X versions. All ports working at USB3.0/USB2.0 speed afterwards with USBInjector. No generic XHCI kext required. The ports work OOB, so to speak, with the right injector. E6440_DSDT_USB_patched.aml.zip E6440_EHCI-XHCI_USB_Injector.kext.zip
-
Some Latitude E Series (like the E6440) require a 90W adapter. Check whether this applies to the E6520. Nothing wrong with your kexts or config.plist. At this stage, on the basis that you're getting POST messages about it, I'd suspect your adapter is not suitable...
-
Raw (uncompiled) ACPI code should be in files with a .dsl extension. Compiled ACPI code is contained in .aml files.
-
A few questions... What makes you think your patched DSDT is not loading? Which bootloader are you using? -> Chameleon/Enoch will always expect a file called "DSDT.aml" (or "dsdt.aml") in /Extra by default; that can of course be manually overwritten whether manually by interrupting the bootstrap or specific entry in o.c.B.plist file. -> Clover will always expect a file called "DSDT.aml" (or "dsdt.aml") in /CLOVER/ACPI/patched by default; again this can be overwritten through menu item of specific entry in config.plist file.
-
Maybe it's not DSDT related then. Can you please post the list of kexts you're using and detail of your SMBIOS + boot plist (whether Chameleon boot plist or Clover config.plist)? What kind of power adapter is it by the way? 45W, 65W or 90W ?
-
Text files for DSDT patches should be created or edited with a basic editor such as TextEdit or vi (from command line); this is to ensure that no application specific format is added to the file.
-
Yup, all details here.
-
There you are. That one should fix your AGPM throttling issue. Let us know. FakeSMC_AGPM-for-NVS-140M.kext.zip