Hervé

And if layout 13 does not work, do try layout 3.

Please refer to the Wireless & Bluetooth forum section. DW1560 is based on BCM4352 chipset which is not supported OOB and requires patching.

Mojave runs on Sandy Bridge Ok; you just have to apply a few tricks like patched PlatformSupport.plist (ideally) and installation of SNB graphics kexts from, say, HS 10.13.6. It's long been explained/detailed how... For the rest, it's just as usual. I would never recommend Mojave on an HD3000 laptop since that old iGPU has been prone to buggy graphics since El Capitan. It can only get worse with a macOS version that bears no support for it.

You must patch the FB/display connector that HDMI output is attached to. It should be FB@1 (connector 0x0105) and the priority must be changed from 0x09 to 0x12 with connector-type changed to HMDI, i.e. 0x00080000. Full details are available here:

Graphics acceleration is not due to FakePCIID_Intel_HD kext which is actually not required at all. Graphics acceleration is obtained through "Inject Intel" + suitable Capri layout-id injection OR Lilu + WEG kexts. SD card reader -> please post specs (PCI ids) and consult our R&D->Card reader section Sleep -> Probably due to unpatched USB ports. You'd normally have to inject power properties as per on a real Mac TouchPad -> try and identify your TouchPad model. If Alps, yoiu should be Ok with Dr Hurt's VoodooPS2Controller R6 as compiled & posted by Bronxteck. Look it up in Dr Hurt's dedicated theread in R&D->kexts section.

Arf, there's simply no timeout in the o.c.B.plist of the Sierra bootpack, that's all. I take it you did not know that, when the Chameleon/Enoch little rotating character appears in top left corner of the screen, you can press [F8] to interrupt timed/auto startup and be able to enter boot options/boot flags like -v.

Each guide has got the right bootpack and kexts. Kexts have been tuned to the SMBIOS that fits the hardware and OS X/macOS version requirements. It's specified in the Sierra guide. Again, in the case of Sierra, if you're getting a "Waiting for root device" error message, unplug the USB installer and try it in the 3 x other USB ports.

Oh yes, I think I had that too. Try unplugging but replugging into another USB port. If you change SMBIOS profile, you have to modify FakeSMC + USB injector accordingly!

@RamiTrainFan, for goodness sake, RTFM and use the Search facilities! Anything else you need asistance with?

Where does your Sierra installer hang? What does it say on screen?

Single-user mode, if you manage to partially boot the system that way...

Did you check our FAQ section?

If you run with latest lilu + WEG, make sure you do not inject any Intel graphics properties in your Clover config.

Intel i5-5250U CPU is Broadwell generation and integrates Intel HD 6000 graphics indeed. As such, I was quite surprised to see a reference to Haswell graphics Azul framebuffer kext in your posted KP. Obviously, something must be wrong on your configuration... Looking at your Clover configuration, I could see: Devices section: injection of some ATI + nVidia properties as well as quite a lot of properties for audio, HDMI audio and Intel graphics properties Graphics section: Inject ATI + Inject nVidia enabled SMBIOS section: incomplete MPB12,1 entry I'd say your issues come from those device properties you chose to inject, knowing that: you should not inject any ATI and nVidia properties if you intend to run on HD6000 graphics you should not enable any ATI and nVidia injection in your Graphics section if you load latest lilu + WEG kexts which seems to be the case Did you come up with this particular config by yourself or did you just get it from somewhere without knowing what it does?

Replace the platform support plist by the patched version and revert to MBP8,1 SMBIOS? You should always install your add-on kexts in /L/E rather than /S/L/E unless you absolutely have to. I take it that you've already added all necessary SNB graphics kexts from a previous macOS version, right?

Erm... "Save as" option in IORegistryExplorer maybe... 'needs to be zipped before upload. We'll then see whether you use layout 0x16160002 or not and if you patches are effective or not. I'd also ask that you explain/detail how you applied the patches.

@flexrac, if DW1830 is not M.2, I don't know what M.2 is... @jean512, I have to re-install OS X/macOS on the Toshiba laptop that I have at home. Should be done over the week-end. I've already fitted the DW1820A in it.

Using Clover Configurator, modify your Clover config as follows: ACPI section: enable FixHeaders uncheck PluginType (you use patched AICPUPM + generated SSDT)

You can always try, knowing that support for these cards is poor and that Apple dropped support for Atheros cards in Mojave so the patched Atheros40 kext is required more than ever.

If you look at layout 0x16160002 in the BDW framebuffer kext, you'll see something like: 02001616 01030303 00002002 00005001 00000060 6C050000 6C050000 00000000 00000000 00000000 00000800 02000000 30020000 01050900 00040000 07050000 02040A00 00040000 07050000 FF000000 01000000 40000000 024B0000 05050600 02000000 04000000 80DF1710 00000000 78050000 D2050000 40060000 00000000 00000000 C8000000 i.e. a layout that supports the following 3 x output ports: 00000800 02000000 30020000 // FB@0, port #0, LVDS (built-in LCD) 01050900 00040000 07050000 // FB@1, port #5, DP 02040A00 00040000 07050000 // FB@2, port #6, DP If you want support for DVI output alongside DP output, you have to patch one of the above output ports for it. Since you already got DP out of port #6, you could expect the patch to be: \/\/ \/ Find: 01050900 00040000 07050000 Replace: 03060900 00020000 07050000 /\/\ /\ ` Try that, knowing that you may have to experiment according to those principles I detailed in my guide for Haswell/4th gen graphics.

What you need to do is identify which framebuffer port relates to each docking station physical display output (DP, DVI, etc.). I expect that you'll then need to patch your specific BDW framebuffer layout, at least for DVI, in a similar fashion as I detailed for HD4600 in the R&D->Graphics forum subsection.

Install CodecCommander kext to /L/E, repair permissions and rebuild your cache.

Please consult our FAQ or non-exhaustive wireless card inventory posted in the R&D->Wireless forum sub-section where you'll find all your answers.

I run with v1.90.1 and it works fine, mostly. It's erratic but my battery is on its way out so I know the battery manager cannot be expected to be reliable.

On 2nd thoughts... it's probably not for you.