Jump to content

Hervé

Administrators
  • Posts

    10027
  • Joined

  • Last visited

  • Days Won

    561

Everything posted by Hervé

  1. If you used a pre-patched AppleHDA, then you'll have to repatch the kext since the update re-instate an unpatched vanilla version. If you use clover on-the-fly patch, then nothing will change but you need to make sure your cache has properly rebuilt (which it should have). This assumes you updated from a previous Sierra version of course, not upgraded from an earlier release. If this is the case, you may have to adjust the on-the-fly patch.
  2. Since Optimus (dual GPU) is not suported on Hackintposhes, I'd say you need to disable Optimus in your BIOS to run only off the iGPU. Then boot in verbose mode to see where the system hangs (if it still does).
  3. I think it depends on what the computer's manufacturer offers by default. I have a BCM94360CD combo Wifi/BT card in my E6220+E6230, both fitted with their own built-in/internal DWxxx bluetooth module. I have to disable Bluetooth option in BIOS to deactivate the built-in/internal DWxxx devices and be able to run Bluetooth off the BCM94360CD cards. Otherwise, the built-in/internal device takes precedence. I have verified that the BIOS option only applies to the built-in/internal device after removing the built-in DWxxx modules: the BT module of the Apple combo card still worked Ok with the BT BIOS option disabled. Of course, what's achieved on a given Dell model may not be applicable/repeatable on another Dell model or even on another brand... There certainly is no visible BT module off my combo cards if they're installed in a PCIe-only slot rather than in a combo PCIe/USB one.
  4. If you read "the Bible" on 1st gen Intel HD, it states that eDP displays can only get Core Image, not Quartz Extreme. Full graphics acceleration used to be referred to "full QE/CI" until a few years ago. You can turn to Google for detailed explanations on Quartz Extreme and Core Image. What this means for your E5410 is that you will not get any support for basic animations like clicking in & out of LaunchPad for instance (it'll be slow and possibly glitchy) or that your Finder's bar will not be translucent. You will only get more basic graphics features such as full screen resolution and resolution change or fixed pictures effects (like visible icons on user accounts PrefPane/login screen or desktop background thumbnails in desktop & screen saver PrefPane). Generally speaking, with partial-only acceleration, your system performance will be quite poor and you'll experience graphics glitches or a regular basis with some graphics apps possibly unusable (DVDPlayer, videos in web browsers, possible unrecoverable borked screen on wake, etc.). I suppose you won't really get the feel for it until you try... Use myHack to install Mavericks if you're up to it (I expect you'll have to delete all 1st gen Intel HD graphics kexts), then follow-up with what "the Bible" says.
  5. Yup. Nothing further for Yosemite and beyond. That's why I said it was a waste of time. Sorry rage75, but you'll have to accept your laptop just is not worthy for Hackintosh purposes. Not all platforms are...
  6. Well, if the laptop cannot enjoy full graphics acceleration, it's a waste of time to pursue any further...
  7. If you run on 1st gen Intel HD (8086:0042 or 8086:0046), please refer to the Bible on the matter. Basically, if your computer has an eDP LCD connector, you won't get full graphics acceleration on your built-in screen; you'll only get it if your built-in LCD has an LVDS connector.
  8. Best thing is to use Clover Configurator app to import the desired theme.
  9. alcheng3344, the card being combo Wifi/BT, you'll only get BT to be recognised/detected if you insert the card into a combo PCIe/USB slot such as a WWAN slot. If your slot is PCIe-only, you'll never get Bluetooth to work. Check your Lenovo user manual.
  10. Your Azul/HD4400 tuning should be visible either in your Clover configuration file (config.plist) and/or the iGPU section of your DSDT (look up for the _DSM method that should be under the iGPU or GFX device located at address 00020000). Regarding the Clover config file, I recommend you open it with Clover Configuration app. Regarding the DSDT, indeed you can open it with MaciASL. If in doubt, post a zipped copy of your EFI folder and we can have a look.
  11. Fn-insert still working? Are you using IntelBacklight kext? Please post a zipped copy of your EFI folder.
  12. Afaik, there should be no need for IntelBacklight kext on your Azul (HD4400) E7440. My Azul (HD4600) E6440 runs 10.12.4 as per any previous OS X version with "just": Azul framebuffer/layout-id 0x0a260006 injection in DSDT Desktop HD4600 id injection in DSDT Rehabman's FakePCIID + FakePCIID_Intel_HD_Graphics kexts After upgrading to 10.12.4 from 10.12.3, I still have the brightness bar in the display PrefPane and I can still increase or decrease brightness with Fn-Insert or Fn-F3.
  13. Impossible to say without indication of chipset. Ask the seller and remember the old adage: "you get what you pay for"...
  14. You have to learn and understand that there are 2 x methods to install and run OS X: one is Clover based, the other is Chameleon/Enoch based. "Extra" folder only applies to Chameleon/Enoch. I invite you to read several guides and learn as much as you can so that you then understand what OS X installation generally involves. If what you're after is more of a step-by-step/idiot's guide, you may look at this type of guidance. You can follow my E6230 guide for your E6430 and re-use the pack but keep in mind the following points: if you have a high resolution built-in LCD (1600x900 or above), find the relevant E6430's DSDT in another guide. The E6230 being low res, its DSDT would result in graphics issue on your E6430 if some of your USB ports do not work, try Rehabman's USBInjectall kext (you can Google for it) the HD4000 Capri framebuffer patch differs between a low res E6x30 and a high res model
  15. 2 issues noticed on my Sandy Bridge E6220 since the update: small graphics glitches on the HD3000 E6220 so I repatched the SNB framebuffer to increased VRAM from 384MB to 512MB and all appears Ok thereafter. Details of the patch are available here. CPU clogging at full speed when running Safari. Kills performance... It's a repeatable behaviour that I cannot reproduce with other browsers such as Chrome.
  16. No difference. The Combo is just an offline method.
  17. Please consult the existing guides in the Guides section. In particular: https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-clover-guide/ The Enoch-based E6230 guide can also be heavily followed from a process perspective and you can re-use most of the bootpack (except DSDT, SSDT and USBInjector for instance). https://osxlatitude.com/index.php?/topic/8883-dell-latitude-e6230-with-i5-3340m-hd4000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/
  18. You're confusing your Ivy Bridge E6330 model with its Sandy Bridge older brothers... Dell Latitude E6xx0 family models are as follows: Latitude E6x10 = 1st gen Core (Arrandale) laptops Latitude E6x20 = 2nd gen Core (Sandy Bridge) laptops Latitude E6x30 = 3rd gen Core (Ivy Bridge) laptops Latitude E6x40 = 4th gen Core (Haswell) laptops Each of those "i" Core CPU families integrate their own GPU: Arrandale = 1st gen Intel HD graphics Sandy Bridge = HD 3000 graphics (+ HD 2000) Ivy Bridge = HD 4000 graphics (+ HD 2500) Haswell = HD 4200/4400/4600/etc. graphics In your particular case, it appears you've confused the drivers used for Sandy Bridge HD3000 and those for Ivy Bridge HD4000. In the OS X world: AppleIntelSNBFB.kext = framebuffer for SaNdy Bridge HD3000 graphics AppleIntelFramebufferCapri = framebuffer for Ivy Bridge HD4000 graphics The E6330 being Ivy Bridge, the SNB/HD3000 framebuffer does not apply and, evidently, won't load. It's the Capri framebuffer that applies to your laptop. As such, patching the SNB framebuffer was useless. Regretfully, HD4000 VGA output is not supported under OS X since ML 10.8.2... You can only patch the Capri framebuffer for HDMI, DP and DVI output. You can refer to the dedicated HD4000 output thread JakeLo linked to (https://osxlatitude.com/index.php?/topic/2945-guide-for-enabling-vga-and-hdmi-in-intel-hd4000-gpu/). If you do not have any HDMI-capable display, I would suggest you invest in a mini-HDMI to VGA or mini-HDMI to DVI adapter to hook your external screen:
  19. No need of a patched kernel on IvyBridge platforms; you only need the AICPUPM patch. If you use Clover, no particular reason why your E6530 would hang post-update. If you use Enoch, things are a little different since you need to re-patch the vanilla AICPUPM kext installed by the upgrade. Provided you kept NullCPUPM kext in /E/E and run a recent version of Enoch such as r2848, you should be able to boot with option & flag: -f KernelBooter_kexts=Yes. Add -v flag to boot in verbose mode and see where the laptop hangs.
  20. I would suggest you install Sierra using a vanilla method, not a distro. We have guides in the EDP->Guides for supported models section.
  21. Best possible cards, imo, are Apple's own Broadcom BCM4360 such as the BCM4360CD with mini-PICe adapter. If you need guidance on hardware elements replacement, download the owner's manual off Dell's web site!
  22. A compatible card maybe? We cannot guess what's fitted to your computer so you'll have to tell us (as always...). We'll assume that: wireless is enabled in BIOS wireless on/off side switch is in ON position If necessary: https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/
  23. What are the laptop specs? If it's dual GPU, you should be able to disable the discrete GPU (dGPU) through a SSDT patch. This assumes your integrated GPU (iGPU) is supported by OS X of course... You'll have to extract your raw ACPI BIOS tables and post them. With Clover, you can do that by pressing F4 at Clover main menu. All extracted tables will then be saved to Clover/ACPI/origin folder of your EFI partition or EFI main folder, depending on your Clover installation.
  24. Seems like you're suffering from the well-known post-10.11.4 VoodooPS2Controller-related KP. Use one of Dr Hurt's revised versions.
×
×
  • Create New...