Hervé

Ever thought of checking the FAQ section? ...

'probably needs a patch of the Azul FB kext to set your DP-associated display port to DP or HDMI connector-type...

And apply the patch for the final stage boot glitch (your last attachment):

It's pretty obvious that all HD3000 are affected one way or the other by these graphics glitches. Increasing RAM (from 4 to 8GB for instance) reduces the issue to some degree as does HD3000 kexts patching. But it's quite clear that there is no definitive fix and the glitches remain no matter what, unless you wish to downgrade to Yosemite or earlier of course...

I have not looked at it but does your patched DSDT inject "Darwin" OS at all? It should have something similar to this: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (0x07D0, OSYS) If (CondRefOf (\_OSI, Local0)) { If (_OSI ("Windows 2001")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP1")) { Store (0x07D1, OSYS) } If (_OSI ("Windows 2001 SP2")) { Store (0x07D2, OSYS) } If (_OSI ("Windows 2001.1")) { Store (0x07D3, OSYS) } If (LOr (_OSI ("Darwin"), _OSI ("Windows 2006"))) { Store (0x07D6, OSYS) } If (_OSI ("Windows 2009")) { Store (0x07D9, OSYS) } } The original DSDT only has this: [...] If (_OSI ("Windows 2006")) { Store (0x07D6, OSYS) } [...] If your DSDT does not inject "Darwin", you'll see something like this in SysProfiler: Once "Darwin" is injected, you should see something like this: If your DSDT already carries this patch, I'd try and remove those XHC patches you have in Clover. I've noticed that you're also using MBP10,1 SMBIOS. Did you give MBP9,2 any try?

I always wondered about the BIOS version-related graphics corruption on our E6x30 laptops, especially as, in the case of the E6230, the video OROM carries the same version 2.1.3.7 between BIOS A11 and latest version A19. So, I upgraded to A19 and re-patched A19's raw DSDT table. The E6230 boots without any graphics corruption and the laptop works as great as before and without any graphics issues so far. The well-known graphics corruption is only seen on closing screen when restarting or shutting down OS X/macOS. DSDT_A19.aml.zip I'd have to check if the same applies to post-A11 versions like A12 or A13 to see if the issue can be isolated to re-using a patched DSDT from an earlier version...

I noticed that, after upgrading BIOS to latest version A19, if the E6230 booted to black screen and then went rapidly into sleep, I had no graphics corruption on wake. I therefore extracted A19's raw BIOS tables and re-patched the DSDT. I'm pleased to say that my E6230 can now boot without issue with the latest BIOS version. Copy attached below. DSDT_A19.aml.zip Patches applied: iGPU device renaming from VID to IGPU + injection of _DSM method for layout-id injection of PNLF device injection of AC device injection of IMEI device renaming of SD card reader device to SDXC + injection of compatibility with Apple's own reader renaming of WLAN mini-PCIe device to ARPT injection of _DSM methods in GLAN + EHCx + XHC devices injection of _DSM_method to HDEF device for codec id injection of power settings to EHCx and XHC devices injection of "Darwin" OS to _INI method to support USB3.0 injection of IRQ NoFlags to HPET device revamping of _PWR methods to USB devices (EHC, XHC, USB)

Make sure you've installed the following kexts: FakePCIID.kext FakePCIID_XHCIMux My recommendation is to install those in /L/E, repair permissions to /L/E and rebuild your cache.

Do you know what a whitelist is? In case you do not, as an opposite to a blacklist which defines a set of rejected/denied items, a whitelist defines a restricted list of authorized/supported hardware. On a computer, it's invisibly embedded in BIOS and, in the case of wireless cards, it's a set/list of models that will be supported, anything else being unsupported. If you install an unsupported wireless card, you computer won't pass POST and won't boot. If you have a wireless card flying around, try it and see if it's accepted. If you do not have anything look for your HP model's spare parts list/catalog on HP's web site. The only alternative to whitelists are patched/hacked BIOS in which they've been removed.

As I said, you either look that up on HP's web site or on the Net. Look up for specs and/or spare parts. Can't do better than that.

I've no idea whether your HP model has a BIOS whitelist or not; you have to check that out on HP's website and/or on the Net.

Most probably if it has a Broadcom chip (it'll be listed under SysProfiler->USB). You'll need to apply/install the usual patches/kexts. But know that you'll not have all the BT features as a real Mac. https://github.com/RehabMan/OS-X-BrcmPatchRAM

Topic is about Wireless/wifi only as its title implies, it does not cover Bluetooth capabilities and eventual support, even if listed cards are combo. Cards support under OS X bears no relation to the computer model. Cards support on given computer models may be subject to whitelisting (eg: HP, Lenovo). You'll have to check that out yourself.

https://www.insanelymac.com/forum/topic/284989-what-does-oob-mean/

The initial specs posted yesterday, before the post was edited, did indicated HD4000 + nVidia NVS GPU...

Moved to the correct forum section... As for the guide:

Which is why the code as formatted in my post #3 is useful and avoids such typos...

DPCIManager actually clearly shows Realtek audio codec ALC235 (10EC:0235). So you need to either patch AppleHDA for ALC235 or install AppleALC + inject correct layout-id. https://github.com/vit9696/AppleALC/wiki/Supported-codecs

A pre-patched version of the AICPUPM kext is provided in the bootpack posted in the guide. It's located in Chameleon/Enoch's usual folder for add-on kexts: /Extra/Extensions. Make sure you've installed that bootpack on your USB installer. Normally, the o.c.B.plist is configured with KernelBooter_kexts parameter set to yes (to load kexts from /E/E) and-f flag (to boot without cache), so you should be able to boot without issues. You may overwrite these by interrupting the Enoch bootloader through F8 when you see the circular character in top left corner of the screen and typing KernelBooter_kexts=Yes -f -v. Thereafter, once you've installed and updated Sierra as/if required to latest version of 10.12.6, you may then install the latest pre-patched version of AICPUPM kext, though I don't believe it's ever evolved throughout the various Sierra updates. You'll find all versions here: I also suggest you set your E6220 BIOS settings as per the recommended settings detailed here: Unlike other computers, my E6220 has all built-in USB2.0 ports fully operationnal without any USB injector kext. Hence absence of such kext in my bootpack.

Laptop with Optimus then... What did you do re: nVidia dGPU?

Looking again at Kali's IOReg, I guess you're right Jake. I just got confused by this: which would not work on the vanilla kext but he's clearly using a non-vanilla one; we don't know what's inside that kext, so even that patch may be useless... I guess it would be most useful to know what the OP's done in terms of graphics and audio kexts mods (replacement and/or patching).

Try removing layout injection from your DSDT HDAU device... I take it that, in your audio PrefPane, you don't have any HDMI audio output that you can switch to, right? This being said: your Clover config shows Azul FB on-the-fly patches whilst, at the same time, your kextcache log shows you're not running on the vanilla Azul FB kext (i.e. you've patched or replaced the vanilla kext). This is highly likely to be incorrect and you should only do one or the other, not both. according to your kextstat log, you appear to be running High Sierra 10.13.4 with Azul FB kext v10.2.5 which is from an older OS X/macOS version... I highly recommend you revert to 10.13.4's vanilla kext (v10.32.48). To be honest, I'm surprised High Sierra loads the Azul Framebebuffer from an older version of the OS. you said you patched ports #6 (0204) and #7 (0306) but you use the expected/correct layout 0x0a260006 for your mobile HD4600. By default, that layout carries no port #7, only ports #0 (0000), #5 (0105) and #6 (0204). When you have HDMI display plugged in, start by identifying the connected iGPU FB/port in IOReg. Once that is done, revisit your Azul FB kext patch according to my patching guide. I could be wrong of course, but I'm ready to bet your HDMI display actually runs off port #5, which is usually the norm. HDMI audio may also depend on the manner in which you get audio working, i.e. patched AppleHDA + dummy codec kext + HDEF layout x or vanilla AppleHDA + AppleALC + HDEF layout y. Let's look at my Haswell/HD4600 Latitude E6440 with ALC292 codec... AppleALC wiki states that, for this codec, the following layouts apply: But if I go the AppleALC route, the results I get are as follows: HDEF layout-id 12 + AppleALC kext + vanilla AppleHDA -> audio Ok but no HDMI audio offered/listed in PrefPane when HDMI TV is plugged in HDEF layout-id 18 + AppleALC kext + vanilla AppleHDA -> audio Ok but no HDMI audio offered/listed in PrefPane when HDMI TV is plugged in HDEF layout-id 28 + AppleALC kext + vanilla AppleHDA -> audio Ok but no HDMI audio offered/listed in PrefPane when HDMI TV is plugged in I will only get HDMI audio output if I run with good old patched AppleHDA: HDEF layout-id 1 + dummy ALC292 kext + patched AppleHDA -> audio Ok, including HDMI audio (offered/listed in Audio PrefPane) NB: HDEF layout-id 1 + vanilla AppleHDA + AppleALC kext -> no audio whatsoever Please note that I still run with Enoch bootloader and no particular parameter in the bootloader for HDMI audio. All I have is the HDEF layout injected in DSDT (with no layout under HDAU device). According to your Clover config, your laptop is fitted with ALC269 audio codec. If you're using the AppleALC method: you may try a different HDEF layout id according to the recommended values: or you may switch back to good old patched AppleHDA (which is my recommendation) Looking at your kextcache/kextstat logs, I could not make it clear how you obtain working audio: I did not see any AppleALC kext nor any dummy kext. All I saw was what appears to be a non-vanilla AppleHDA kext with a version 999-something so I can only assume you run with an AppleHDA kext patched to inject ALC269 layouts. Please clarify all this so that, in turn, we might be of assistance. You've dispersed things all over the place: non-vanilla kexts + on-the-fly kext binary patches, Clover injections + DSDT injections; this makes it really hard to follow... I think you should be Ok running on-the-fly patched AppleHDA (i.e. full vanilla kext in /S/L/E) + dummy ALC269 kext + with HDEF layout-id 1 (as per Toleda's old info posted here). So, set that in your DSDT and remove any audio layout id from your Clover config (you should always avoid duplicating stuff in various places). If things are injected in DSDT, they don't need to be injected in the Clover config too. Unlike kids, computers don't need to be told twice (or more) what to do.

There is no brightness control for this old system under OS X. You can only apply BIOS controlled brightness adjustments through Fn-UP/Fn-DOWN keys. That's the end of it. I would remove whatever change you applied to get the (non-functioning) slider bar in the Display PrefPane. BIOS levels do not get reset on my D630 laptops; make sure you've either applied the AppleRTC patch through Clover or installed a pre-patched kext.

Have you installed the Logitech layouts from the penultimate version of Ukulele?