Hervé

Absolutely no idea, I've never needed to rebrand any of my wireless cards. I tend to favour Atheros to Broadcom. Ask Jake, he's fond of the DW1510.

There is no Mavericks sub-folder in the dists folder, so... http://archive.ubuntu.com/ubuntu/dists/

The nvidia GPU of these D Series always tend to run hot, even when idling. Some people reverted to brand new heatsink to reduce T°. My own GPU never runs below 70/71/72°C and adding a copper shim did not change a thing... Make sure to keep your fan radiator clear of dust clog. You currently run on a Merom [email protected] with only 2Mo L2 cache. That's a low spec C2D model so don't be surprised that's it's having difficulty coping during a stress test. You'd experience a much better performance with a high-end Penryn C2D like the T9300 (2.5GHz, 6Mo L2 cache). When/if you do upgrade, clean off all dust from your entry radiator and renew GPU + CPU thermal paste with a quality one such as AS5.

You 1st need to format the Windows target partition as FAT from Yosemite. You'll then be able to reformat it NTFS from the Windows installer.

Added AzureWave AW-CE123H combo Wifi ac/BT 4.0 1/2 mini-PCIe card.

Can you please post your DSDT + saved SysProfiler + saved IOReg output from, say, IORegistryExplorer?

ALC236... Give the ALC235 a try. You can get it from Mackintosh Vietnam Tools for instance. No guarantee it'd work, but nothing to lose by trying.

Before anything else, open up your laptop and check that your fan and heatink radiator are not clogged by dust; it's very typical after a few months/years... Look-up for the proper way to manage native CPU SpeedStep on Intel's 1st gen "i" Core cpus such Arrandale and/or Clarksfield. It's well covered on this site or at InsanelyMac... As usual, Intel i7-620M specs are available at Intel ARK site.

SandyBridge + IvyBridge CPUs require the AICPUPM patch. With Clover, that means activating the on-the-fly AsusAICPUPM patch whilst with Chameleon/Enoch, it means replacing the vanilla AICPUM kext by the patched version available here. NB: Previous versions of OS X are available through one's AppStore account as long as the installation app was downloaded before from AppStore/AppleWeb site once signed in.

All these are Ok. Favour the T9300 CPU, this Penryn model really makes a difference with its much bigger cache. Copper shim can be a waste of time & money on these nVidia models. I bought one and it's made ZERO difference in terms of GPU T°...

On those models, Fn-F8 has no adverse effect other than screwing output display. You don't necessarily need to restart the system, one can usually recover by putting the system to sleep, then wake it. I guess you probably did not think of that. If you screen looks different that it did before (I assume you meant the Finder's bar icons), I guess you've probably been messing with elements of display rendering in the General PrefPane through more accidental key strokes... You just need to get to learn those Yosemite/El Capitan's functional details a little better. You should easily find the fix...

Those issues have nothing to do with Enoch. Enoch is a boot loader and that's it. The AppleHDA patch is widely available for the IDT 92HD93 codec of the E6430. It's just a matter of searching for it. For USB 3.0, I'd say there's a very good chance that the built-in Intel controller can be natively supported. USBx.0 issues are a "simple" matter of DSDT tuning + USB injector creation for your chosen SMBIOS profile. Again, this is widely documented and can be found through forum searches. Here for instance. Anyway, this is all off-topic, this thread was about HD4000 artefacts and can be closed.

I've found that, in OS X, it's better to distinguish both networks than use the same SSID on both 2.4GHz and 5GHz. I personally had an issue with 2 x 2.4 & 5GHz networks that shared a common SSID... until I used 2 x separate SSIDs. All my troubles then went away and I could connect safely and in a stable manner to one or the other. Symptoms were different from yours though as I was experiencing connection dropouts; doesn't seem to be the case for you, so I'd say the patches Bronxteck linked to are probably required.

After further testing, HD3000 of E6220 is to be able to support the following combinaisons of 2 x concurrent displays: LCD + VGA, LCD + DVI, LCD + HDMI, VGA + HDMI, VGA + DVI, DVI + DVI, etc. Please note that Intel SandyBridge graphics cannot support 3 independant displays. I've updated my E6220 SNB patch to reflect port number and connector types as reported in IOReg: 01 02 04 00 10 07 00 00 10 07 00 00 // vanilla: nb of connectors -> "04" 05 03 00 00 02 00 00 00 30 00 00 00 // vanilla: laptop's own LCD display 02 05 00 00 00 08 00 00 05 00 00 00 // patched: HDMI, display port #5 (built-in port) 06 02 00 00 00 04 00 00 08 00 00 00 // patched: VGA, display port #8, (built-in + docking-station port) 04 06 00 00 00 04 00 00 07 00 00 00 // vanilla: DVI, display port #7, (docking-station port) NB: VGA output is also fully functional with connector type 0001 0000, 0010 0000 or 1000 0000 not just with DVI/DP connector type 0004 0000.

I've spent some additional time on the E6220 and the E-Port replicator K07A002 trying to work out multiple external displays. At 1st, things looked hopeful and promising, but I never reached the targeted goal. Even though OS X did report 3 x displays (LCD + VGA + DVI), only one external display worked, never both... No problem getting 2 x external displays with LID closed though. That works perfectly. Then I found that SandyBridge graphics do not support 3 independant displays, only 2, so that figured! I slightly updated my SNB FB kext's patch to reflect port numbers and connector types as reported in IOReg: FB@0 -> LVDS, port #0, connector-type 0200 0000 FB@1 -> HDMI, port #5, connector-type 0008 0000 FB@2 -> VGA, port #8, connector-type 0004 0000 or 0001 0000 or 0010 0000 or 1000 0000 FB@3 -> DVI, port #7, connector-type 0004 0000 01 02 04 00 10 07 00 00 10 07 00 00 // vanilla: nb of connectors -> "04" 05 03 00 00 02 00 00 00 30 00 00 00 // vanilla: laptop's own LCD display 02 05 00 00 00 08 00 00 05 00 00 00 // patched: HDMI, display port #5 (built-in port) 06 02 00 00 00 04 00 00 08 00 00 00 // patched: VGA, display port #8 (built-in + docking-station port) 04 06 00 00 00 04 00 00 07 00 00 00 // patched: DVI, display port #7 (docking-station port) 10.10.5_Patched_AppleIntelSNBGraphicsFB.kext.zip

Pirolito, really, the boot pack is saved on your desktop in a folder called "ElCapitan_E6430_Pack". What more can I say?... Looking at the recent gusts of new threads and posts re: EC installation of those E6x20/E6x30 with Clover, I'd say stick to (Chameleon) Enoch. Clover really seems difficult to newbies (no offence meant). You can follow the same process I've detailed meticulously for EC on the D630 nVidia. Obviously the pack will change, but you already have it.

These options are already contained in the files provided in the pack (CsrActiveConfig is in the boot plist and KernelBooter_kexts is in kernel plist) so I guess you did not follow some of the steps of the guide… The guide makes a very specific mention to these parameters and their use. You can do all the OS updates you want with your eyes closed. As long as you've placed all add-ons in /L/E, your D630 will keep on working.

Time to make a fresh installation...

Then you've got a corrupt bootpack. Why don't you try Mavericks, Yosemite or El Capitan using more recents guides? https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-intel-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemite/

Try and boot in safe mode and without graphics enabler (-x GraphicsEnabler=No). If you reach the desktop, set OS X back to default OS drivers and remove the nVidia web driver. M4300 works fine with OS X default drivers.

Sorted. Installation had too many defects to mention, 1st one being an incorrect SSDT locking CPU to 800MHz... Installed the correct add-on kexts to /L/E, removed injected kexts from EFI/CLOVER/kexts, replaced AppleHDA with patched Yosemite version from Jake's Yos guides, activated DropSSDT in Clover, regenerated proper SSDT, etc. All is working, though I still can't explain those messages related to the prelinkedkernel that cannot be cached.

I guess you did not follow the guide to the letter, did you? You're either missing the correct permissions for the /L/E folder or not booting with the right boot options. Provided you've got the full pack in /Extra with DSDT + SMBIOS/boot/kernel plists + Extensions folder with all necessary kexts, you should be able to boot with the following flags and options: KernelBooter_kexts=Yes CsrActiveconfig=3 -f -v Once you've booted to EC, you can copy the kexts from /E/E to /L/E, repair permissions, rebuild cache and boot without KernelBooter_kexts option.

Hmm, I would not trust kext wizard for such a rebuild; I'd be scared it screws up the iMac. What I would recommend you do instead is the following: sudo chmod -Rf 755 /Volumes/<HDD partition name>/S*/L*/E* sudo chown -Rf 0:0 /Volumes/<HDD partition name>/S*/L*/E* sudo chmod -Rf 755 /Volumes/<HDD partition name>/L*/E* sudo chown -Rf 0:0 /Volumes/<HDD partition name>/L*/E* sudo touch -f /Volumes/<HDD partition name>/S*/L*/E* sudo touch -f /Volumes/<HDD partition name>/L*/E* /Volumes/<HDD partition name>/usr/sbin/kextcache -Boot -U /Volumes/<HDD partition name>/ -K /Volumes/<HDD partition name>/System/Library/Kernels/kernel

You will only be able to repair permissions and rebuild your cache once you've successfully booted your system (unless you have another partition on your disk that you can boot and perform those tasks from). Once you've deleted all unnecessary kexts from /S/L/E, you should be able to boot if you place all your add-on kexts and patched DSDT to the EFI/CLOVER folders of your EFI partition. Kexts placed in EFI/CLOVER/kexts/10.xx are injected at boot time, not cached.

-> PM