Hervé

You can of course open up the compiled file directly. From memory, the E6x20's DSDT are not affected by the Intel iASL bug.

There is renewed development on the matter of Realtek's RTS52xx SD card reader building on Sinetek's initial work : https://www.insanelymac.com/forum/topic/321080-sineteks-driver-for-realtek-rtsx-sdhc-card-readers/?do=findComment&comment=2713476 https://github.com/cholonam/Sinetek-rtsx I've tried out Cholonam's Sinetek-rtsx kext v1.0 on my Latitude 7490 and it's now possible to read (and only read) an SD card once inserted in the reader. It can be ejected and re-inserted at will; it's just a little slow to mount (~10s) and Read-Only. Works after wake too. Supported models appear to include: RTS5209 / RTS5227 / RTS5229 /RTS522a / RTS5249 / RTS5286 / RTS5287 / RTS5289 / RTS525a

No, audio control normally works OOB with keyboard buttons on those E6x20 models.

That's exactly what I meant. 1) In method _Q66, add this code between the 2 x lines NEVT () and Return (Zero): ^^^^AMW0.WED0 (One) Mid (^^^^AMW0._WED (0xD0), Zero, 0x06, Local2) If (LEqual (Local2, Buffer (0x06) { 0x02, 0x00, 0x10, 0x00, 0x50, 0x00 })) { Notify (PS2K, 0x0365) } If (LEqual (Local2, Buffer (0x06) { 0x02, 0x00, 0x10, 0x00, 0x48, 0x00 })) { Notify (PS2K, 0x0366) } 2) In method _BCM of IGPU->LCD device , add this code before the Name (BRT3, ...) line: If (LGreater (OSID (), 0x10)){} 3) in method BRT6, all the 2 x LPVB.PS2K notifications under the LCD notifications as follows : Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x0366) and Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x0365) That should do it.

The DSDT Patch required to get brightness control out of the legacy BIOS E6x20 is available in my E6220 High Sierra guide. Have a look.

You misunderstood, RTCMemoryFixup is for BIOS/CMOS resets (on some computers), not for KP at shutdown/restart.

Using those same drivers on my Lat 7490 and I've not experienced any trouble with Sleep/Wake since upgrading to 10.15.4. I guess this issue was indeed specific to your own build.

It's called a "no entry" sign... .

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...