search

niiknow / Hackintosh-Latitude-7390

Dell Latitude 7390 Hackintosh
MIT License
9 stars 2 forks source link

Add branch for Dell Latitude 7390 2-in-1 users #2

Open superguyadi opened 4 years ago

superguyadi commented 4 years ago

Tried this build on my Dell Latitude 7390 2-in-1.

Add SSDT-PNLF in ACPI folder for brightness control.

Choose alcid/audio-layout as 28(tested),30,33 for ALC 3253(ALC 225)

For Intel Wi-Fi(Tried with Intel 8265 Wi-fi): Add the following Kexts: itlwm.kext IntelBluetoothFirmware.kext IntelBluetoothInjector.kext Note: itlwm is in development stage. I got 45 Mbps speed only on 5G and 2.4G.

Remove all the BRCM/Broadcom kexts as there is no Broadcom wifi chip. Remove IntelMausi as there is no Ethernet port.

Update config.plist

What's not working: Touchscreen USB-C Hotplugging

PurpleCrumpets commented 3 years ago

I managed to get my touchscreen working using the latest version of VoodooI2C and VoodooI2CHID, but can't for the life of me get my trackpad to work. @superguyadi, did you manage to get the trackpad working?

superguyadi commented 3 years ago

@PurpleCrumpets I got it to work by switching VoodooI2C to some other voodoo file, I think it was voodoops2(take it with a grain of salt) but the crux is: Either your touchscreen will work or trackpad would work; I couldn't get them to work together, so I turned to use trakpad as touchscreen is less important. Use the voodoo files from @swung0x48 or the surname variations available to get the tapas working. But it will break your touchscreen.

https://github.com/Swung0x48/Dell-Latitude-7390-7490-Hackintosh-EFI

PurpleCrumpets commented 3 years ago

@superguyadi I'll give it a shot without the touchscreen-enabled when I have the chance, thanks for the advice! Is your EFI file basically the same as Swung0x48's and/or niiknow's (as you mentioned above)? Swung appears to use both VoodooI2C and VoodooPS2... I assume by surname variations you mean PS2 vs I2C etc.?

superguyadi commented 3 years ago

Give it a shot: https://github.com/acidanthera/VoodooPS2 use these voodoo kexts, I believe HID, keyboard and trackpad will be needed. Remove all the VooDoo kexts before adding any new files. And be prepared, while you do the hit n trial method, keep all the files handy. It may even break your keyboard, but you can quickly recover by restoring a working kexts backup.

PurpleCrumpets commented 3 years ago

@superguyadi Managed to get both my trackpad and my touchscreen (and pen with palm rejection) to work correctly! I ended up using the EFI file posted by muttonhead411 here and working from there. The downside is that I'm fairly sure I can't use OpenCore to boot Windows, but if it means that my touchscreen and touchpad work as expected, then I think it is a fine tradeoff.

superguyadi commented 3 years ago

@PurpleCrumpets wow! Good job! Can you upload your opencore/ boot folder here?

superguyadi commented 3 years ago

@PurpleCrumpets maybe start a new repo, and I'll download it from there? There are a lot of 7390 2 in 1 users. Also you're using itlwm.kext right?

Swung0x48 commented 3 years ago

@superguyadi Managed to get both my trackpad and my touchscreen (and pen with palm rejection) to work correctly! I ended up using the EFI file posted by muttonhead411 here and working from there. The downside is that I'm fairly sure I can't use OpenCore to boot Windows, but if it means that my touchscreen and touchpad work as expected, then I think it is a fine tradeoff.

You should be able to use OpenCore to boot Windows if you got all your SSDT patches wrapped by If (_OSI ("Darwin")) statements.

PurpleCrumpets commented 3 years ago

@Swung0x48 What about renaming patches (ACPI -> Patch)?

@superguyadi Created a repo for the 7390 2-in-1 here! I didn't use itlwm.kext, just Airportitlm.kext which appears to work for my needs (I don't have an iPhone so I can't test any Apple-ecosystem specific things yet). Let me know if it is useful for you/anything you managed to get working that I didn't (specifically audio on wake)!

Swung0x48 commented 3 years ago

@Swung0x48 What about renaming patches (ACPI -> Patch)?

They serve different purposes. An ACPI renaming patch is applied when there is some device or identifier in your System DSDT that got the same name as your newly written SSDT. (SSDT, secondary system description table, serve as a compliment to DSDT) So that you should rename apply renaming patch to get your SSDT work. It should not be used without aim.

superguyadi commented 3 years ago

@PurpleCrumpets Thanks! What speed are you getting on airportitlm? Does airportitlm needs heliport app too? I got a maximum of 45 Mbps on both 2.4G and 5G WiFi(my connection is 100 Mbps and get 100mbps in Windows).

PurpleCrumpets commented 3 years ago

@superguyadi Not a massively scientific test given that other people are using the network at the same time, but I get 57.1 Mbps down and 18.8 Mbps up on my hackintosh and 66.8 Mbps and 20.2 Mbps down in Windows. I'm not downloading that much on my Mac so the network speed difference is not that important to me.

You don't need heliport when using airportitlm as far as I can tell.

Just found a new sleep issue where my sound stops working after the laptop is woken from sleep. Is this something that happens for you?

@Swung0x48 So to check my understanding, the ACPI renaming patches renames something in the DSDT such that the SSDT doesn't conflict with it? If that is the case, can the renaming patches be 'turned off' in the case of booting Windows (preventing issues like the one that can occur here)?