Hervé

Did you install any 10.11 update such as 10.11.4 or 10.11.5? Boot in verbose mode and post what you obtain.

I've no personal experience with the E6500 nVidia but I guess that, yes, HDMI and/or DP should work too. You'll find out soon enough.

Your laptop is fitted with a high-end Penryn mobile C2D CPU + nVidia NVS 160M GPU. It should run decently enough with all latest OS X version from Mavericks to El Capitan. My D630 nVidia is of slightly lower specs and runs perfectly under Mav/Yos/EC. It's no power beast by today's standards of course but perfectly usable daily for general desktop activity, browsing, music or videos. You'll have to replace your DW1397 wireless card by another model as it won't be supported in recent OS X versions. https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/

No, why would you do that? You'd only modify the FB kext to gain VGA/DVI/HDMI output if not natively supported. You cannot modify the FB to make your internal LCD recognised as such. You have to get graphics supported under a mobile HD4x00 layout. Try them all and see how it goes. I believe you'll never get anywhere with a desktop layout. Your Clover config.plist also showed a custom EDID, did you try without it?

The Extra folder you posted some time ago shows an incorrect SMBIOS: MacBookPro5,1. That's a Core2Duo model, not a SandyBridge-based model with integrated HD3000. Make sure you use a suitable profile such as MacBookPro8,1/8,2/8,3. Use Chameleon Wizard to select such a profile and save the SMBIOS plist in your /Extra folder. With Clover, you'll have to use the Clover configuration tool. If you're still not getting any joy, then I would again say that this basic version of SandyBridge Intel HD is not supported and you will never get graphics acceleration (as with HD2000). Overall, this Packard Bell laptop is quite a poor/limited system anyway. It was a cheap low-spec system when commercialised... In that case, my advise is to forget running OS X on it. El Capitan, Yosemite or otherwise, it makes no difference; if this SB GPU is unsupported, that is across the board. You can't even change the CPU for a Core i model due to chipset, so you're kind of stuck with what you got. NB: Capri framebuffer is for Ivy Bridge systems, so not applicable here. Don't confuse things.

When the built-in LCD is not detected as such, the fix usually consists of patching the PNLF device in DSDT and/or adding boot display info to the IGPU device @0x00020000. The patched DSDT I upload previously included this. But I think you're not using the correct config for your graphics/display. You have a laptop with HD4200 graphics and, as such, you should be using a mobile layout such as 0x0a260006, not a desktop one like you currently do with 0x0d220003. Desktops don't have built-in LCD per se... To me, that's where your issue is.

Indeed, this has been extensively discussed on the forum before. You can use the forum Search facility or browse the R&D/Hardware/Wifi section.

Just to clarify things regarding framebuffers: HD3000 graphics of Sandy Bridge CPUs i3/i5/i7 2xxx CPUs is handled by SNB frame buffer kext HD4000 graphics of Ivy Bridge CPUs i3/i5/i7 3xxx CPUs is handled by Capri frame buffer kext HD4x00/5000 + Iris 5x00 graphics of Haswell CPUs i3/i5/i7 4xxx CPUs is handled by Azul frame buffer kext You have an Ivy Bridge i5-3317U CPU with integrated HD4000 graphics so the Capri FB is the only one of concern on your laptop.

If you have a myHack-based installation, kexts are meant to be placed in /E/E then you run myFix (quick).

More likely to be an issue with DSDT battery device. Rehabman's repo has a number of patches for that.

It's nv_disable=1 (all in lower case). You must respect the syntax as provided by Jake.

I've mentioned this before here but cannot track the post... You may be in the presence of a 2.4Ghz and 5GHz wireless networks using the same SSID and/or encryption key. I've been in that situation before and encountered disconnection issues such as yours. I've detailed the deployed fix here. It's an easy one... You may also take Dell's info on the matter into account.

What kind of patch do you have in mind? I'd say this Sandy Bridge Intel HD graphics is also unsupported, after all, it's based on HD2000.

I would not know what to do with that dump, sorry... Here's a revised DSDT that injects mobile HD 3000 id 0x0126. It needs to be used with restored vanilla graphics kexts. DSDT.zip

Well, you're going to have to explain your installation build and how you install kexts.

Try and repair kexts permissions then rebuild your cache.

AppleIntelBDWFramebuffer.kext is for 5th gen Broadwell IGPUs. I just cannot see the relevance of that kext in your specific SandyBridge context. You should revert to plain vanilla graphics kexts throughout. Patching of SNB kexts is not usually required to reach OS X desktop. Usually, it's only necessary to obtain specific display output such as DP, DVI or HDMI. Try to fake HD3000 by injecting mobile HD3000's id 0x0126 in your DSDT as opposed to mobile (SNB) Intel HD's 0x0106. The patch will then look exactly as posted above.

Hmm, did you ever adjust your PS2 keyboard kext as detailed here?

If you have no USB-related issue, then you're probably in the presence of an unsupported model and there's little you can do about it. But it's difficult to say much really since you've provided no info on webcam model, no IOReg output and no SysProfiler output. So, basically, we just don't know what you have...

I cannot understand why you'd binmod your Azul FB kext in such a way. You should never overwrite replace an existing layout by the id of another existing one! You end up with a Azul FB kext where there are 2 x entries for layout id 0a260006. That is just wrong to me. Afaik, playing with port number will not change anything regarding backlight control. It's the display type recognition that's key here. Issue such as yours are usually encountered on dual GPU system but yours was not listed as such... Go back to the vanilla kext and try to use the other layout-ids until you hopefully find the one that matters (there are 15 or 17 layouts for Azul).

Try the attached patched DSDT. DSDT_meng_patched.zip Updates I've done: 1) add desktop HD4600 device id 0412 + Azul FB #12 layout id 0x0a260006 + hda-gfx entry to IGPU device @0x00020000 2) remove _HID name from LCD device 3) remove _ADR name + _BCL/_BCM/_BQC__DOS methods from PNLF device This DSDT should be used in conjunction with vanilla graphics kexts (restore those if required) and Rehabman's fake PCIID kexts: FakePCIID FakePCIID_Intel_HD_Graphics FakePCIID_Intel_HDMI_Audio Try this and report back.

It's not worth the effort. This laptop is fitted with an unsupported eDP display connector and cannot enjoy full graphics acceleration. As such, OS X will always run poorly on this machine.

As I said, you have a Sandy Bridge Intel HD graphics integrated to that Celeron CPU, not an HD 2000 which is unsupported. Don't do anything with any kexts until you've patched your DSDT. That's the 1st thing you have to do. Reinstate all vanilla kexts and then try the attached patched DSDT. DSDT.aml.zip

Use the audio kexts found in the D630 nVidia 10.9.5 pack posted in the D6xx section.

Which "hd graphics guide and kexts" would that be? If you're referring to the 1st gen Intel HD graphics guide at InsanelyMac, I'm afraid you're on the wrong track. Intel Celeron B830 is Sandy Bridge family, i.e. 2nd gen and the integrated Intel HD graphics device id 0x0106 you noted yourself should be a sufficient hint... Did you check the CPU on Intel ARK site? 2nd generation (Sandy Bridge) Intel HD graphics (detailed list here) include: HD graphics (Desktop=0102, Mobile=0106) -> most likely unsupported under OS X HD 2000 graphics (Desktop=0112, Mobile=0116)-> unsupported under OS X HD 3000 graphics (Desktop=0122, Mobile=0126)-> supported OOB under OS X (fitted to several Mac models) HD P3000 graphics (id=010A, Xeon CPUs) -> supported/unsupported under OS X ? As long as you've kept all your Intel SandyBridge (SNB) vanilla kexts in place, you can try and experiment with the SNB framebuffer. I've checked the kext and it does contain a reference to 2nd gen mobile Intel HD graphics id 0x0106: <key>AppleIntelSNBGraphicsFB</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleIntelSNBGraphicsFB</string> [...] [...] [...] <key>IOClass</key> <string>AppleIntelSNBGraphicsFB</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IOPCIClassMatch</key> <string>0x03000000&0xff000000</string> <key>IOPCIPrimaryMatch</key> <string>0x01068086 0x11068086 0x16018086 01168086 01268086</string> [...] [...] [...] </dict> ` In Clover, you can specify/adjust the value in the Graphics config menu. With Enoch, you may be able to pass the values as boot parameter via InjectIntel-ig=xxxx. In the end, assuming this basic/low-end version of Sandy Bridge HD graphics can be supported in a similar manner as HD 3000, what you'd need is a patch of the DSDT integrated graphics device located at address 0x00020000 (it may or may not be called IGPU). Here's a sample of such a patch for HD 3000 (dev id 0x0126): Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "device-id", Buffer (0x04) { 0x26, 0x01, 0x00, 0x00 /* HD 3000 graphics */ }, "model", Buffer (0x18) { "Intel HD Graphics 3000" }, "AAPL,snb-platform-id", Buffer (0x04) { 0x00, 0x00, 0x01, 0x00 /* Laptop/mobile layout */ }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } The key parameter is the SNB platform id but, of course, you'd have to modify the device id too unless you'd need to possibly fake HD 3000 id (but highly unlikely to work). I invite you to consult RampageDev's Intel HD guides for reference. Looking at your extracted DSDT files, your integrated GPU is defined as GFX0 and already bears a _DSM method which you'd have to adjust. Please post an IOReg output. That may help towards an eventual DSDT patch. All this being said, you have to prepare yourself to the eventuality of having an unsupported 2nd gen Intel HD graphics chip as per HD 2000... In such a case, if the CPU is not soldered on the motherboard and if your EasyNote laptop can support this, you may consider swapping out your Celeron B830 with a SandyBridge Core i3/i5/i7 model integrating the HD 3000 graphics. That'll depend on the chipset which you need to identify. If Intel HM70, that won't be an option.