Hervé

GTX 1060 is a Pascal GPU and is therefore unsupported under Mojave. This is why it'll need disabling (through SSDT patching) more than ever. Generally speaking, dGPUs need disabling in Hackintosh laptops because Optimus technology (dual graphics) is not supported by OS X/macOS. Your Qualcomm wireless card is unsupported too and will require to be replaced by a compatible model. Alternatively, you'll have to use a compatible USB adapter. Check out non-exhaustive inventory available in R&D->Wirleess section to that affect. With regards to your IOReg (which you extracted properly with the provided app), I can see that the nVidia dGPU remains enabled whilst the Intel HD630 iGPU is not active. This is where we need to concentrate.

What Broadcom wireless card do you have in place? Did you inject or install CodecCommander along AppleALC when using audio layout 11?

Hi, you may refer to the following threads: BIOS settings for the D630 Bootpacks for the D630 The best method for those laptops is to use myHack app for installation. Snow Leopard requires myHack version v3.1.2, available here. myHack requires you to have: access to a Hack or a Mac a copy of Snow Leopard retail DVD or a USB key with retail SL image restored to it a copy of the bootpack (the Extra folder) applicable to your computer myHack can then be used to: create the USB installer that you'll use to install SL on your D630 tune up your D630 in the post-installation phase If you don't have access to a Hack or a Mac, you can still install SL with Nawcom's modCD. It's a bootable CD that will allow you to install SL on your D630 provided you have the SL retail DVD or a USB key with the SL retail image restored to it. The installation will not be perfect because you will not be able to use our provided bootpack (the Extra folder) but you'll be able to have SL installed with minimal functionalities. From there on, you can either complete the post-installation tuning where you'll add our bootpack and finalise your SL installation or create a new myHack USB installer with our bootpack that'll get you SL fully installed directly. I started with Nawcom's modCD all those years ago since I did not have access to a existing Hack or Mac... Those old D Series laptops are a bit long on the tooth these days but they made excellent platforms as Hackintoshes and are close to full support on the hardware side. You'll need to pay particular attention to the wireless card you have as it may require tuning or replacement. Check our FAQ section for details. The GMA X3100-based version that you have supports OS X up to Lion 10.7.5. Mountain Lion is possible with the old MLPF trick which reverts the kernel and kexts back to 32/64bit versions of DP1. It works but it's not bug-free...

Dell Latitude 7490 with Micron 1100M M.2 2280 512GB SATA SSD (SATA-III connection @6Gb/s)

As mentioned by @jpz4085, it would appear any BIOS can be used without the infamous screen garble if patching the Capri framebuffer kext in order to modify the FB memory size from 16MB to 8MB. See details here. Binary patch is as follows (implement through Clover or actual kext binary mod.) for Capri layout 0x01660003: Name: AppleIntelFramebufferCapri \/\/ Find: 03006601 01020402 00000004 00000001 Replace: 03006601 01020402 00000004 00008000 /\/\ Explanation: 0000 0001 represents the (default) FB memory size in Bytes. 0000 0001 means 0x01000000 in hex, i.e. 16777216 in decimal which, when divided by 1024*1024 (to convert in MegaBytes), equates to 16MB. 0000 8000 means 0x00800000 in hex, i.e. 8388608 in decimal which, when divided by 1024*1024 (to convert in MegaBytes), equates to 8MB. When injecting properties against the iGPU @2 -i.e. PciRoot(0x0)/Pci(0x2,0x0)- in the bootloader config, this is done with: framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00008000 DATA

Please post your system's specs.

If you need 3 x antennas on a low-profile adapter, look for products from Ableconn: http://www.ableconn.com/products_1.php?bgid=12#PCIe to M.2 / mPCIe Adapter They require to acquire the antennas separately.

That's off-topic on this "Card reader" thread...

I don't have garbled screen with my patched A19 DSDT. I would get a garbled screen if I update to BIOS A12 or higher and run DSDT from an earlier BIOS version (could be from A11, could be from before). All I get with my patched A19 DSDT is a screen corruption at the point where desktop shuts down after initiating a restart or a shutdown. It does not bother me the slightest. I won't get that if I revert to BIOS A11. It only comes with BIOS versions starting at A12. Nevetherless, I tried the patches you posted and only the binary mod. of the Capri FB kext did the business: Find: 03006601 01020402 00000004 00000001 Replace: 03006601 01020402 00000004 00008000 Thanks for the info! 2nd DSDT patch alongside Latest Lilu + WEG changed nothing at all.

Refer to my guide for the Latitude 7490 which has identical specs. Clover pack was built from JakeLo's for a 5590 I think. You should have HDMI audio OOB if you install latest AppleALC + Lilu and inject layout 11 which you're not right now. No expected improvements for TouchPad for the time being, I2C interface oblige... Realtek RTS525A card reader is also a dead-end at the moment. Your Clover config would gain from a little clean-up, especially the removal of those ATI + Nvidia properties injection...

Conti appear to have stopped all MyHack development after v3.3.1 in 2013. myHack last supports Mavericks, nothing later. From Yosemite onwards, you have to use the (now) well-known manual method. You'll find it referenced in all recent installation guides.

Don't waste your time and change the card.

Subsys 1028:081c on the Latitude 7490. Same behaviour as reported by @philstopford, whether injecting using Sinetek's kexts available at IM or the above. This being said, subsystem id can be faked through DSDT patching or Clover injection, as well as full compatibility values 'wondering if we could not fake RTS5227 which was supposed to be supported and working...

Most probably, yes. As I said, no-one ever managed to get this Realtek card reader to work.

It's been said dozens of times before and it's clearly indicated in the inventory Jake linked you to: those AR946x, AR9485, AR9565 cards are poorly supported to plain unsupported in High Sierra and Mojave. Replace yours with a fully supported card or use a supported USB dongle. I can recommend DW1820A, Jake would recommend DW1560, both M.2 2230. D1830 may not fit since it's M.2 3030 (wider).

Because you're not injecting a PS2 kext or not the right one...

You'd probably have to re-patch its DSDT in order to get rid of the graphics corruption that affects all BIOS > A11, so you may not want to bother. Do you feel you'd have much to gain from that BIOS update? You feel at risk from a security point of view? I had to repatch raw DSDT of BIOS A19 to be able to use it...

Is it the device shown in the IOReg output you posted here? Vendor id=0x0bda, i.e. Realtek USB Device id=0x0139, i.e. RTS5139 Card Reader Many people have tried to get this card reader working for many years without any success... You could try to add an entry in FakeSMC's Info.plist to inject a new device profile into AppleUSBCardReader kext (PlugIn of AppleStorageDrivers kext) as described here. Copy/paste an existing profile from the PlugIn that you'll then modify in order to specify the above Ven id and Dev id converted from hex to decimal. If, as I expect, the above mod. is unsuccessful, you may try and overwrite some of the fields of the USB descriptor shown in IOReg for your card reader, specifically the following ones: bDeviceClass bDeviceSubClass bDeviceProtocol and set them to 0; yous are all set to 255 (0xff). See here for detailed information on USB descriptors. This what my Vostro200 desktop shows for its USB-internal TEAC CA-200 card reader and I think that's what macOS uses to hook the device and load drivers: You would try to set those values through Clover's properties injection. Use Clover Configurator to that effect. You already know that the card reader is located @1a14,0. /!\ No guarantee any of this will work at all of course...

You'll find several such adapters that convert mini-PCIe or M.2 to PCIe x1, for instance if you type "mini-PCIe to PCIe wireless adapter" in a well-know auction site... If at all possible, opt for something that carries a degree of adaptability in terms of cards or antennas, like support for full or half size mini-PCIe cards. Also opt for an adapter that supports Bluetooth through USB connection and provides the necessary cable. I can recommend the following Fenvi adapters: Fenvi FV101 for half-size mini-PCIe to PCIe x1 + Bluetooth Fenvi FV102 for M.2 2230 to PCIe x1 + Bluetooth Both come with a high-profile and low-profile rear bracket and a USB cable. They're limited to the size of cards listed above and 2 x antennas (like most if not all other adapters). A cover comes to protect the wireless card and antenna connectors once in situ. I currently use a FV101 adapter in my SFF Dell Vostro 200 in which I fitted a DW1520 card. There are other (unbranded?) adapters that provide very similar features but support full-size and 1/2-size mini-PCIe card. Eg: For M.2 adapters, pay special attention to the Key, knowing that wireless cards usually are Key A+E (slot with Key A supports cards with Key A+E, not cards with Key E since these are missing the A notch). M.2 wireless cards usually are 2230, only a few are 3030 (wider), so no worries on that front (all should fit). Just note that 2230 cards usually have 2 x antenna connectors whilst 3030 cards usually have 3.

Which version of Clover are you using. Try with the latest r4919. https://github.com/Dids/clover-builder/releases

Afaik, nothing you can do apart from developping the code for ALPS V7... Try and contact DrHurt directly maybe. He visits this forum and InsanelyMac's too.

AfaiK, the kext never handled those late ALPS Touchpad versions very well. It's been stated by Dr Hurt himself in previous pages. Last compiled version (by Bronxteck, available on p1) supports TouchPad & TrackPoint for the V3 ALPS hardware fitted to my Latitude E6440: V3 Rushmore Touchpad with ID: E7=0x73 0x03 0x0a, EC=0x88 0x08 0x22

You can proceed with 10.14.4.

I had no issue with my E6220 when it ran on 4GB RAM. I upgraded it to 8GB to minimise the graphics glitches. But certainly no freeze.

You've not specified what you did in terms of changes/patches so we cannot guess... This being said, I notice that you've modified the _INI method of that SSDT table from: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (Zero, \_SB.PCI0.RP05.PEGP._ADR) NBAK () } to: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (Zero, \_SB.PCI0.RP05.PEGP._ADR) _OFF () } Assuming you've not modified anything else, try this instead: Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (Zero, \_SB.PCI0.RP05.PEGP._ADR) NBAK () _OFF () } It would also help if you would post your entire set of raw tables saved in ACPI/origin folder. A copy of your saved IOReg from IORegistryExplorer would be very useful too.