Hervé

Afaik, you're indeed out of luck but you can always Google this out...

Folks, again I regret to be forced to remind everyone that these inventory threads are exactly just that: inventories. As such, no support requests to be made here and any such request will be systematically deleted without any notice. Anyone needing support on any given wireless card is expected to create a new thread as/if required or necessary.

Obviously, it's a DSDT patch. Also obviously, you insert the patch code in the DSDT sections that are indicated... This very classic patching script is meant to be applied from iASL tools such as goold old DSDTEditor (a bit obsolete these days) or MaciASL. You may consult my E6220, E6230, E7250 or 7490 guides where I've detailed and explained exact same patches (albeit with different values). An alternative, details of which were posted by @Jake Lo, you could implement equivalent changes through a dedicated SSDT.

Be a little creative: try without "Inject Edid"... obtain your screen's EDID from Windows, then inject the whole Hex chain in Clover...

Then look into injecting the screen's EDID info.

You may try and contact the author about this; but Dinesh has not been around for a year...Consider this project also abandoned.

So totally different specs from an Ivy Bridge E6x30! And its Haswell HD4400 graphics, not i915 graphics (which equates to GMA900 of Pentium M era 15 years ago!)... Also ALC3226 audio normally is ALC292 codec (same as in Haswell E6x40 Series). You can now either re-install from scratch or apply a new set of kexts, ACPI patched tables, Clover config, etc. You'll need a full cache rebuild too of course.

-> moved to the D6x0 Support section. Guides sections clearly state "no support here" so please make every effort to post in the correct and relevant sections in the future... Now, to begin with, make sure you use the correct version of myHack. Latest v3.3.1 cannot be used for SL due to a bug. The correct version for SL (v3.1.2) is provided in the myHack section where things are clearly explained. All you need for SL is a genuine copy of a retail DVD or retail image (10.6, 10.6.3 or 10.6.8). Then, you download the D620 GMA950 SL pack and select the provided DSDT that matches your LCD screen resolution (LoRes DSDT for 1280x800 or HiRes DSDT for 1440x900). Then, pick up a USB key (8GB should do) and format it FAT32. You can then create your USB installer with myHack. All you have to do is follow the process and point to your downloaded boot pack (i.e. "Extra" folder) when prompted to do so. myHack includes the Chameleon bootloader installation so you normally cannot go wrong on that front. NB: I don't know what you mean by "using a .toast file". May be you can explain and post a picture.

-> This is not related to a Latitude E6xxx so moving to more appropriate forum. Please make sure to post in the relevant forum sections. Obviously, you need to adjust this Sierra build (i.e. Clover setup or otherwise) so that it matches the new system specs. You just can't expect to take out the macOS disk from one machine and simply boot it in another one. Here you were lucky but it's hardly the case.

It means that if you try and use any of the following layouts: 0x01660000 0x01660001 0x01660002 0x01660008 0x01660009 you may also have to try them with the Clover on-the-fly patch detailed above (applicable to AppleIntelFramebufferCapri kext). Altogether, that's 10 x tests to make potentially (each layout with and without the patch).

I've seen some people reporting issues with Sleep/Wake, yes. But I didn't take much note of it so can't give you pointers...

Everything looks fine except 1 x aspect of your Clover config: you've opted for PluginType with regards to CPU power management so remove the dropping of SSDT CpuPm and Cpu0Ist.

Well, 10.15.4 seems to break away from what we had all gotten accustomed to for years now: straight forward/troublesome updates.

I had a couple of issues on wake on my old C2D Vostro desktop after the 10.15.4 update but, other than that, all is Ok. To be monitored in the coming days and weeks... Usual things to check: hibernation settings presence of sleepimage Energy Saver PrefPane settings darkwake boot parameter (optional)

This is a recurring question from many people who want to create an OS X/macOS USB installer but neither have a Mac nor a Hack to do this. They only have Windows and a VM can be a little daunting or not successful. Thankfully, there are tools that can be used from Windows to obtain the desired Graal! We can recommend the 2 x following tools: 1) TransMac https://www.acutesystems.com/scrtm.htm 2) Boot Disk Utility http://cvad-mac.narod.ru/index/bootdiskutility_exe/0-5 See this thread also: https://osxlatitude.com/forums/topic/10494-how-to-create-mac-installation-usb-from-windows Those who know how to use Google may look up for tutos. Example: https://www.wikigain.com/create-macos-high-sierra-bootable-usb-installer-windows-10/

Those (old) cards are 2.4GHz & 802.11b/g/n only. They work OOB (or not) in OS X/macOS as per stated in our inventories. Obviously, you need to do the needful if you attempt to use those in macOS versions that officially dropped Atheros... I can vouch for this, I still have a couple lying around so they were tested. Those cards are Wifi only.

If it behaves anything like my Latitude 7490, behaviour is erratic and it may take a few reboots for touchpad to work again. I'm nearly exclusively using an external mouse so it's never bothered my that much and never worked to fix it. On the ToDo list...

Have a look at my E6230 Catalina guide. Don't re-use the DSDT and SSDT of course (use your own) but most, if not all, of the settings (Clover config, kexts) should be re-usable for your E6430 if it's the model with HD4000 only, not dual HD4000/NVS 5200M graphics. This being said, why don't you post details of what you currently use (Clover version, EFI folder, etc.)???

Basically, AppleHDA_ALC292 was an injector to be used in conjunction with a binary patched AppleHDA; totally useless on its own with vanilla AppleHDA and obsolete now that Lilu + AppleALC kexts take care of things with vanilla AppleHDA.

If black screen using layout 0x01660004, try other mobile layouts shown on p1 such as 0x01660009. You may then need to apply the following LVDS patch to the Capri framebuffer: \/\/ Find: 010000000200000030000000 --> vanilla LVDS outpout layout 0x016600 00/01/02/08/09 Replace: 050300000200000030000000 --> patched LVDS output /\/\ Did you use DualLink with layout 0x01660004? I forgot to add it in the config I provided. Anyway, just conduct your own experiments/tryouts with the various Capri layouts. You should get there eventually.

2nd config remains incorrect since it still contains wrong properties injection for device PciRoot(0)/Pci(0x2, 0), i.e. the HD4000 iGPU: And you've not provided the rest of your Clover EFI folder so God only knows what may lie there too... Here, try this config. Call it from Clover main menu->Options->configs. config_RV.plist.zip You'll also need to generate your CPU-specific power management SSDT using Pike R Alpha's well-known generator tool/script.

Intel i5-3220M mobile CPU is fitted with mobile HD4000 iGPU which carries the usual id 0x0166. There is no need to fake anything for that iGPU. With Lilu + WEG kexts, there should be no need to add Inject Intel nor any ig-layout-id in Clover config. Injecting desktop layout 0x016600a seems incorrect to me when it should be HiRes mobile layout 0x01660004. With regards to Darwin injection, it'd be better to select Darwin for Win7 if the computer has USB3.0 ports/controller. Otherwise, there won't be any USB3. KernelPm patch is irrelevant, it's for Haswell and beyond, AICPUPM patch is what's required for Ivy Bridge. The Capri patches found inside the Clover config are probably useless and may contribute to your problems of completing the boot process and reaching the macOS desktop. They should be removed/disabled. Again, details of the patch for HiRes layout 0x01660004 are provided in our HD4000 patching guide in the R&D->Graphics section if required.

In the Guides section!

With HD4000 iGPU, you can install latest macOS version (Catalina 10.15.4 at time of writing). You'll find it works extremely well on those E6x30 with all hardware elements fully supported, apart from the dGPU of course.

nv_disable boot parameter does not actually disable the dGPU like a DSDT patch or a dedicated SSDT will (by powering it off), it just signals the OS to ignore it and not load drivers so that OS X/macOS will run graphics in VESA mode only. Please use the forum Search tool/facility to seek the SSDT table that disables NVS 5200M dGPU in Latitude E6x30 laptops.