Hervé

Ok, 1st time for me I deal with external declarations and a separate SSDT for GPUs. Anyway, here are patched DSDT + SSDT-6 tables. Try to rename them as DSDT.aml and SSDT.aml and place them in EFI/CLOVER/ACPI/patched folder. DSDT_ALW.aml.zip SSDT-6_ALW.aml.zip You can 1st try with only your integrated Intel HD4400: in the "Graphics injector menu" mentioned before, simply activate "Inject Intel". The SSDT table contains the device id + default Azul framebuffer/ig-platform-id 0600260a. You may try to experiment with other framebuffer values if you do not get graphics acceleration with the HD4400. There are about 15 different values but many are for mobile versions of the GPU. If you want to try the PCIe Geforce GTX 745, I guess you'd simply have to activate "Inject nVidia". Again, the SSDT table contains the usual details for injecting an nVidia card, though I have not specified the amount of Video RAM it has on-board as I did not see that reported in the IOReg. You may have to enable or disable the nVidia card in BIOS where it may be referenced as PEG for PCI Express Graphics. Good luck. Can't guarantee it'll work.

I'll try and patch the DSDT for you, then you'll have to try the various Azul framebuffer/layout-id as I explained above in post #3.

Ok, so: PCI root id is 0, so that's cleared out of the way HD4000 is GFX0@2 with id 041e; ideally, should be renamed IGPU in a patched DSDT. No visible layout-id, so you must enter one out of the 15 or so possible value. You may try them one by one until you hot the correct one. GTX745 is PEGP@0 under PEG0@1 with vendor id 10de (nVidia) and device id 1382; ideally, should be renamed GFX0 in a patched DSDT. The graphics devices are defined in SSDT-6 raw table, not in the raw DSDT.

To edit a DSDT, you must 1st identify the relevant section of the table that corresponds to your hardware. To do that, use IORegistryExplorer and look at the whole list of devices. Hopefully, you'll find some data or text that leads you to the touchscreen. Once you've done that, you'll be able to identify the DSDT section you may eventually modify. Of course you would need to know what to modify and that's another story... There are several ways to modify (i.e. patch) a DSDT: you can decompile the .aml file using Chameleon Wizard app, then use a standard text editor (such as TextEdit) to modify the .dsl source file. You can then recompile the .dsl file with Cham Wizard again. You may also use a tool such as DSDTEditor or MaciASL to modify the .aml file directly and recompile the table.

Yep, that'll be fine.

Try the attached kext in /L/E to fix your "HD unsupported" matter in DVDPlayer. IOAHCISerialATAPI_Injector.kext.zip How do you get full graphics acceleration on your HD4400 with Clover? Can you restate the native device-id of your HD4400 and the AzulFB/ig-platform-id you use? Are faking desktop id 0412 and or using FakePCIID kext at all?

MBR method in my guide??? I think you're mistaken... When I mention "MBR", that was in relation to the way you installed Clover in your USB installer: there are options in the Clover installer to install the boot loader and, from memory, one of them is to install Clover in the MBR. That's what I was referring to. If you've now gone for Chameleon, make sure to use a version like r2401 or r2468 for instance, I can vouch for those. Those versions will look for the kernel in /System/Library/Kernels under the name of "kernel". Previous OS X version ran their kernel from partition root under the name of "mach_kernel", then it changed with Yosemite. You need to follow the guide closely, then you really can't go wrong.

Download IORegistryExplorer and post us the saved full output. Specify the version of the app you used as there are 2 versions on the go. Then, try and extract your raw DSDT with an app like Chameleon Wizard or DSDTEditor and post it too. We can then try to patch your DSDT with the IOREg info and hopefully get your GTX745 supported in Yosemite. As with all high-end Dell desktop PCs, we may find that the default PCI root is set at 4. We can modify this back to 0. With Chameleon, you could specify boot option PciRoot=4 and that could get your card up and running. Don't know how you'd do that in Clover I'm afraid...

A bit of a difficult one this time, mostly due to a combination of mobile HD4600 GPU and boot loaders that modified the GPU mobile version id to desktop version id 0412. Using the now well-known Yosemite method, there is no issue building the USB installer using the DB installation app. El Capitan DB can then be installed either with Clover bootloader (r3224 and above) or Enoch bootloader (r2725 and above). There was no issue updating from DB to DB4, then tune the system to: get full QE/CI by patching the AzulFB + HD5000Graphics kexts to reflect on mobile HD4600 id 0416 instead of desktop id 0412 (patch of Info.plist file + hex mod of binary file in MacOS subfolder) support HDMI connection by patching the AzulFB kext remove 2nd stage boot screen corruption by patching IOGraphicsFamily kext get all USB ports + Intel Bluetooth to work by removal of AppleHPET kext in /S/L/E get full audio by replacing AppleHDA by patched version When it comes to DB5 and as I wrote in the E6220 10.11 DB thread, things get much more awkward and difficult, especially on this E6440 laptop. Even though I boot with rootless=0 option to disable SIP, SLE folder remains fully protected so removing the AppleHPET kext for instance is a thankless task (I actually had to remove the kext from Yos!). Same with replacing AppleHDA. So, as I also wrote in the E6220 thread, El Capitan DB5 is probably best avoided for the time being, until such time as the SIP protection can be more easily bypassed. In time, we'll see. Other than than, everything seems to work just as in previous versions such as Mavericks or Yosemite, except USB port on the left side which is now dead because there's no USB3.0 support any more (was Ok up to DB4 as far as I can recall). Nothing new in terms of kext, but the DSDT might require new tuning to sort out the USB ports again. RAM is incorrectly reported too, showing 9,12Go of RAM when I have 8Go! Recommended boot loader for 10.11 DB5 seems to be Clover v3251 at the moment and all kexts must go to /Library/Extensions (/E/E no longer supported and SLE fully protected). I'm a strong Chameleon fan so I use Enoch branch r2725 and above can boot 10.11. Trouble: bootloader includes replacement of mobile HD4600 id 0416 by desktop HD4600 id 0412. I've never been able to obtain graphics acceleration with desktop id 0412 so I had to request a source code mod of the Enoch branch to remove that id replacement. I did try to mod and recompile the code myself but, whilst it worked Ok with Mav and Yos, it would not boot 10.11 and I got instant reset instead. At the moment, I using a test/unreleased Enoch boot file, which is not bug free, but boots Mav, Yos and El Capitan successfully and retains mobile HD4600 id 0416. So, things are looking good with 10.11 Beta on the E6440 at the moment, but there's still more work to do... Regarding graphics kext patching, everything can be derived from this thread and the main E6440 Mav/Yos guide. There really is nothing new but I recommend sticking to DB4 for ease of use. DB5 is kind of complicated. You've been warned. Haswell-patched kernels are available here.

Ok, so that's Vendor 0x0c45 / Device 0x6433, i.e. the Sonix HD Webcam as in my E6320 guide. If you could extract your raw DSDT + raw IOReg and post them, we might be able to get that webcam to work. Which DSDT are you using right now?

Touchscreen can be difficult. This might be resolved by a patch; could be done through DSDT or possibly Clover. Clearly a USB device but can't say more than that. Try and boot in safe mode to see if that makes any difference. You might then be able to take a DSDT extract + an IOReg extract. The 1st important thing is to identify the exact hardware model of that touch screen (vendor id + device id).

Boot loop is indeed probably due to missing but necessary Haswell patch. At Clover main screen, go to "options", then to "binaries patching menu" and select "Kernel PM patch". You may unselect "AppleIntelCPUPM patch" as that does no apply to your Haswell CPU though it won't do any harm. Power management for Haswell CPUs has been handled in kernel for some time now (since ML if I'm not mistaken). Regarding Intel HD 4400 support, well, try as suggested by Jake. Again, in "options" menu, go to "Graphics Injector menu", select "InjectIntel" and add your chosen Azul framebuffer layout-id in "FBConfig". You must enter the value in reverse order, i.e. for layout-id 0x0a260006, type "0600260a". If that does not lead you to full graphics acceleration (you'll notice a slow system response and screen glitches), you may experience with other Azul frame buffer layout-ids. RampageDev has listed them on his blog, though I think some of the last entries to be incorrect but I think they're for mobile models.

What made you think a Windows driver could have anything to do with your OS X boot problem? A Windows driver belongs to Windows and that's all there is to it. Don't delete it!

It's probably the way you installed Clover on that key. I recommend installing in the MBR.

Or try with Chameleon; it works fine with versions such as r2401 or 2468. Just needs a bit more work with AICPUPM to avoid KP...

In your case: Azul framebuffer + HD5000Graphics kexts if you've patched them to obtain graphics acceleration. Add AppleHDA to the list if you've replaced it in the past to get audio running. The update will (re)install vanilla kexts... And anything else you might have patched on your side and we don't know about.

Same thing with the combo eSATA/USB2.0 port on the left side?

Re: webcam, I never got to the bottom of this as I'm relying on E6320 owners feedback on hardware device ids. If you could provide your webcam ids (visible in the Sys Profiler), that'd be appreciated.

Can't help you unless you get specific... What version of Clover are you using? Where did you copy the DSDT? Where did you copy the kexts? List all the files and kexts you've used along with folders where you placed them. Also, tell us what the KP says or post a picture of it. Re: bootloader, it's entirely up to you, but if you're a Hackintosh beginner, I strongly suggest you stick to Chameleon (use a not too recent version like r2401 for instance)

I suggest you retry installing the full pack linked above.

Here goes (AGPM included just in case, though it's not normally modded). Vanilla_10.10.4_HD4x00_kexts.zip

Sorry but you're not specific enough. What exactly did you do when you say "I just added the yosemite bootpack to the bootloader" ? Did you just simply the Extra folder to your USB installer and that's it? Which bootpack by the way, the one I posted in my recent D630 bootpacks thread? With Chameleon boot loader, you must repair permissions and rebuild kextcache everytime you modify/add/remove kexts. See the D630 Yosemite guide I had posted in the research section or any other Yosemite guides I posted in the EDP->Supported Models with Guides section. The entire USB installer creation process is detailed in there.

Basically, you need the patched Intel SNB frame buffer (for Intel HD 3000 graphics) as that got overwritten by the 10.10.4 update. You need to repatch the kext after each update (or retrieve the patched kext from somewhere and replace the vanilla kext). https://github.com/toleda/graphics_Intel_framebuffers The patched kexts are available in my E6220 guide.

Which version of FakeSMC and plugins are you using?

DB5 quickly followed DB4 but might be best avoided at the moment. It seems to implement new safety measures that prevent "untrusted" kexts (i.e. our add-on non-Apple unsigned kexts) to be included in the cache, unless it's a major bug of course. What I've observed is that whilst the usual chmod -R 755 of kexts works ok, the chown -R 0:0 of kexts does not and return permissions errors. Consequently, cache cannot be properly rebuilt as all our add-on kexts are declared untrusted and omitted from cache: As a workaround, the flag -f must be added to the chown command. So use the following commands to rebuild kernelcache: sudo chmod -R 755 /System/Library/Extensions sudo chown -Rf 0:0 /System/Library/Extensions sudo touch /System/Library/Extensions sudo kextcache -Boot -U / - To summarise, proceed with caution. You may find that have to reboot in safe mode and/or only with Clover to proceed with post-install 1st reboot and be able to finalise the update. This being said, graphics appear much better/more stable than in DB4 for sure.