Hervé

Your Clover VID-to-IGPU ACPI patch seems irrelevant since the patched DSDT found in ACPI/Patched folder already includes this mod.

Only the models with nVidia NVS 160M graphics fully support OS X/macOS. Those with Intel GMA 4500 graphics are of no use because the iGPU chip bears no support whatsoever under OS X/macOS. Afaik, the nVidia model supports all screens without any specific settings according to resolution.

Moved to correct support E6xxx section!

You have a laptop fitted with mobile HD4600 (id 0x0416). The usual Azul framebuffer required for this kind of platform is #12 0x0a260006, not 0x0d220003 which is normally used on Desktops. Of course, graphics acceleration on mobile HD4600 requires that the choice of Azul FB is accompanied by mandatory faking of desktop HD4600 id 0x0412, the injection of Rehabman's FakePCIID kexts (FakePCIID + FakePCIID_Intel_HD_Graphics at a minimum) and the right SMBIOS profile (should be MacBookPro11,1 or similar). Then, even with these correct settings, you may still require to inject a correct EDID for your built-in screen but start with the correct basic settings 1st... I could not find where you inject fake desktop id 0412 from: I saw this in your IOReg output but it's not in your Clover config file and I could not find this injected your patched DSDT either... NB: I don't think you should need those kexts you currently inject via Clover: it's not in your Clover config file and I could not see it in your patched DSDT either... AppleBacklightInjector IntelGraphicsDVMTFixup IntelGraphicsFixup

In principle, any recent PC or workstation is Hackintoshable as long as it bears hardware compatible with OS X/macOS. We're talking CPUs, chipset, graphics card to name the most critical parts. The rest (audio, LAN, wireless, etc. ) can always be supported through add-on devices. Xeon E5-2630 v3 is Haswell-EP generation & Intel X99 chipset so should be supported OOB or without too much bother. Maybe you'll need the VoodooTSCSync to properly handle all the CPU cores. Other than that, I cannot imagine any issues. Have a look at RampageDev's X99 dmg section of the forum if necessary. AMD FirePro W4100 (Cape Verde chip) is also understood to be compatible though you'll probably have to fake a Radeon HD 7xxx id and install add-on kexts such as Verde or WhateverGreen that are required to support AMD 7xxx graphics. https://github.com/vit9696/WhateverGreen You can Google for all of this.

Indeed, the source code on Github is not available beyond v1.7.2 of Sept 2013, knowing that the latest version offered vas v2.6 in Aug 2016. You'll have to contact the author; I suggest by PM or email... Thank you.

You can Google for this. There are ways to create an OSX/macOS USB installer from Windows. The links elude me but there are defintely guides at InsanelyMac for instance.

There's no Bluetooth device listed so it's probably disabled in BIOS or the card is in a WLAN slot, not a WWAN one. Combo cards must be installed in combo mini-PCIe/USB slots such as WWAN for the BT module to operate. Once you've done the needful, you'll see that the listed BT module is of Broadcom BCM2070 (BT3.0 I think) nature which is normally supported under OS X/macOS. You may require Rehabman's firmware-related add-on kexts to get BT working properly, albeit with some limitations in terms of application support (since it's not BT4.0 or higher). https://github.com/RehabMan/OS-X-BrcmPatchRAM All in all, you'd have much to gain by simply replacing this card by a fully supported and more modern card (DW1701 is 9yrs old, as is BT3.0+HS technology).

The correct connector-type for DP is normally 0004 0000. 0008 0000 is for HDMI. Maybe you should patch your particular framebuffer@2 to adjust the connector type value.

Again... Posting your PCI list is of no use for USB-based Bluetooth! You'll have to tell us what you see under SysProfiler->USB to identify the eventual BT chip in place and give us its displayed PCI ids. Is it a DW1701 card?

Check your SysProfiler for an eventual Bluetooth device under USB. If the card is combo indeed, the Bluetooh module should be listed there, whether it works or not.

That behaviour is quite common on Dell laptops. My E6440 does the same: no audio on hot rebooting into OS X/macOS from Windows. Ok after a cold reboot/shutdown.

No need to be an electronic engineer... Simply put a small and narrow piece of cellotape (or any other type of self-attaching masking tape) over the entire pin 20 of your card to entirely isolate it. Do you follow? You can Google for pin 20 if you need further illustration. It would be quite a challenge to place the properly-sized piece of masking tape over pin20 only, so apply wider-than-required piece of tape on your card, then use a small cutter to remove the excess parts.

Indeed, the table shows the W_DISABLE_N input line attached pin 20 (that pin again), so if it's taped, no assertion signal can normally be received on the modem to disable RF module. This is actually stated on p34 of that document: This being said, we'd need to confirm that MC8805 follows the same pinout (which is highly likely) though there can be no harm in trying masking pin20 anyway. It's not as if it could burst the hosting laptop to flames. Or is it? I've not managed to find a copy of the AirPrime MC8805 Product Technical Specification Document & Customer Design Guidelines. @wojciech679, yes you should be able to Terminal to access the device associated to the USB modem once you've identified it. Other tools such as putty would probably be easier to use in order to issue the relevant AT commands.

In the 1st case, kexts are injected at boot time but sometimes won't load properly, in the 2nd, they're cached so it's quicker to load and loading is guaranteed. In a nutshell, it's much better to cache kexts than inject them. Injection can of course be used for testing, upon which I would recommend to cache kexts.

See posts #7 and #8 on p1. Basically, the modem needs this so-called magic "DMS Set FCC Auth" command to be set online. => https://sigquit.wordpress.com/2015/02/09/dell-branded-sierra-wireless-3g4g-modem-not-online/ => https://cgit.freedesktop.org/libqmi/commit/?id=22628a69dad6a1c4b0400dacf1c13c48425faf69 As stated in the above articles as well as others you may encounter on the web, there appears to be no other alternative to setting the card to online mode (in Windows, the driver does it transparently). You'll find that several people chose to replace this MC8805-based card by other and less troublesome models. You'll find useful details on the MC8805 chip here. In particular, you'll probably find more meaningful to know that low power mode = Airplane mode. Now, if you look at table 2-1 on p9, you'll notice references to AT commands related to setting the modem in low power mode. It may well be that setting the values to 1 rather than 0 puts the modem back online:

If you're not offered the "install High Sierra from ..." partition, I would say the update process has not run properly or you've hidden partitions from the boot loader in its config file. If you then reboot the original non-upgraded HiSie installation, you'll of course be offered to upgrade again. That's perfectly normal.

Reinstall in HFS mode.

https://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/ https://www.insanelymac.com/forum/files/file/208-1st-gen-intel-hd-graphics-kexts/ https://osxlatitude.com/index.php?/topic/10136-short-guide-install-high-sierra-on-lenovo-x201-i5-520m/

You could try to move the add-on kexts to /L/E, repair permissions and rebuild your cache. Don't subsequently keep the add-on kexts in the Clover EFI folder.

There are several guides for Sierra. Here or here for instance. For High Sierra, you'll need Clover because Chameleon/Enoch do not support 10.13's temporary-partition installation. Same for the updates. But Chameleon/Enoch do boot and run High Sierra without issues. that's how I run it and I use my Clover USB installer whenever there's a High Sierra update to install. Other than that, installation is the same as per previous OS X/macOS versions. Here's the Clover EFI folder I use on my 10.13.1 USB installer set with Clover r4081. BIOS runs in legacy mode. EFI_E6220.zip No problem updating to 10.13.3 and booting the temporary update-completion partition with that same USB installer.

True, those Atheros cards such as the AR9462 have poor support under OS X/macOS and are often not compatible with High Sierra. As such, it's indeed better to replace them. However, HP laptops are infamous for hardware whitelisting, meaning you cannot install any card compatible with macOS. You have to look at HP's own documentation (usually the spare parts catalog) for the list of cards officially supported by HP, then check if any of those are OS X/macOS compatible. The catalog for your ProBook 650 G1 is available here. The trouble is that this catalog lists the following cards as spare parts: 690019-001 = Atheros AR9565 and that will bring the same problems as with AR9462 730668-001 = Broadcom BCM43228 and that's not compatible with OS X/macOS There would appear to be another non-Bluetooth Atheros card but I've not identified it But the ProBook 650 G1 may not be subject to hardware whitelisting. In fact, you'll find messages on the Net about Azurewave AW-NB290H working in the 650 G1; that card is based on Broadcom BCM43225 and that's fully compatible with OSX/macOS. Give it a go, these cards are available for less than $10/10€... Other than a compatible mini-PCIe card, the only alternatives are: a modified BIOS where whitelisting has been removed (difficult thing, hard to find) a USB dongle

If you have a Penryn CPU, yes, absolutely. And you can of course use Clover; in fact it's necessary for installation and updates because Chameleon/Enoch does not fully support those (it can boot High Sierra after installation and updates though). Give this Clover EFI folder a go if you wish; it's what I used to install Sierra & High Sierra on my D630. EFI_D630.zip

Everything is explained in details in this thread... https://osxlatitude.com/index.php?/topic/10401-dw5570-how-can-i-use-the-wwan-under-high-sierra/

To reset nvram and delete all variables, use the following Terminal command: sudo nvram -c ` To obtain more info on the command, type: man nvram