Hervé

Pentium P6100 is Arrandale generation so its (1st gen) Intel HD iGPU may only be supported if it carries id 8086:0042 or 8086:0046. Then, support will depend on the video connector used for your laptop: eDP or LVDS. You'll have to consult the bible on the matter at InsanelyMac. If the Intel HD iGPU of this Arrandale Pentium is not supported, you'd have no support for graphics and you'd therefore have to forget about OS X on this platform. Also note that, this Pentium P6100 not being SSE4 capable, at best you'd be limited to El Capitan 10.11 if at all possible. All in all and this applies to your Ethernet and Wifi cards too, you're going to have to identify your hardware a little better than that site provides in terms of specs. You can either look at each main hardware component individually through Windows Device Manager and look at the hardware id information available in the driver's tabs. Failing that, use well-known tools such as CPU-Z or Aida64 to create a full report on your laptop's components. Alternatively, now that you run Yosemite (albeit in limping mode), you may: run IOregistryExplorer app, save its output, compress it and attach it here open up your SysProfiler (Apple menu->System Information), save its output, compress it and attach it here These should provide us with your full system's specs.

No, it's either: SSDT-UIAC table + USBInjectAll kext or USBPorts kext on its own (without SSDT-UIAC table) NB: I don't know which guide you followed to install High Sierra on your E6330 but I doubt it's one we published here because you're missing quite a few kexts... I would have expected you to have most of those you'll see listed with green tags in the screenshots of my 1st reply. And your ACPI/patched folder contains irrelevant tables too. I would suggest you consult these guides: https://osxlatitude.com/forums/topic/8883-dell-latitude-e6230-with-i5-3340mi7-3540m-hd4000-and-1366x768-lcd-mavericksyosemiteel-capitansierrahigh-sierramojave/ https://osxlatitude.com/forums/topic/8506-dell-latitude-inspiron-precision-vostro-xps-clover-guide/?tab=comments#comment-74275 Post a zipped copy of your Clover EFI folder, I'll try and fix it for you.

As explained above: Remove all instances of USBPorts Reinstate USBInjectAll (and rebuild your cache if you're caching it but I suspect you're injecting it instead) Reboot Run Hackintool app and, in the USB tab, regenerate SSDT-UIAC table + USBPorts kext Retain SSDT-UIAC table with USBInjectAll kext or use (i.e. inject or cache) only USBPorts kext TrackPad PrefPane should then be back.

Which High Sierra build are you running? And what about kexts you could be injecting from Clover? I assume you're doing that, aren't you? If so, no need to cache the kext from /L/E. This being said, I was just offered to install High Sierra Security Update 2019-005 on the E6220, which I did (build 17G8037)... and TrackPad PrefPane subsequently disappeared (familiar message "no TrackPad detected" reported in PrefPane)! I've identified that the problem was due to USBPorts kext. After reinstating USBInjectAll and re-generating SSDT-UIAC table + USBPorts kext, the TrackPad PrefPane is back with SSDT-UIAC + USBInjectAll or USBPorts only.

Well there you are: you're duplicating kexts and installing kexts in /S/L/E AND /L/E; best recipe for troubles! Never install add-on kexts to /S/L/E unless absolutely necessary (on very rare occasions), only in /L/E. It's often repeated.

Check that you've not installed any other PS2 kext anywhere that would interfere with DrHurt's VoodooPS2Controller R6 (which is the correct kext to use on all E6x30). The kext worked perfectly on my E6220/E6230/E6440 under High Sierra and continues to do so on my E6230 under Mojave and Catalina. And I have the TouchPad PrefPane present too. E6220 under High Sierra 10.13.6: E6230 under Mojave 10.14.6 and Catalina GM (no longer runs HiSie): Various gestures work properly, can't say they all do, especially as I have 2 left hands and big heavy fingers, but many do (show desktop, LaunchPad, Swipe between pages, ...).

You're probably not using the correct version. Try the attached: IORegistryExplorer.zip Apart from that, things are looking pretty good in your SysProfiler, congrats...

Can't you just post an IOReg output from IOREgistryExplorer app rather than. a text version that's really difficult to read? Add a saved output from About this Mac->System Information too please. This being said: you're using really old versions of Lilu + WEG kexts; update to latest versions you've installed FakeSMC AND VirtualSMC! That's wrong. You only use one of the other for battery management, you use ACPIBatteryManager with FakeSMC or SMCBatteryManager with VirtualSMC your Clover config contains several incorrect settings and is missing SMBIOS definition CPU power management settings being incorrect, I doubt you have CPU SpeedStep working and by, extension, sleep & wake no DVMT settings/properties injection in your Clover config -> your HD630 iGPU is clearly not being used I'm pretty sure that if you have graphics running, these are on the NVIDIA dGPU (with nVidia web driver) AppleBacklightFixup is defunct/obsolete now and would be of no use on your nVidia dGPU anyway; it really was for Intel iGPUs Try this config instead: config.plist.zip

Tried firmware v5974 but couldn't make it connect to my BT mouse even though it detects it Ok. Now, I simply cannot connect to it at all when it previously used to work Ok and quite sustainably so as detailed on p5. I think I'll just stop on this DW1820A non-sense.

Fixed an issue of corrupted picture on HDMI output reported here + loss of HDMI audio due to default DP connector type being applied to iGPU FB@1. Fixed with following HDMI properties injection: -> included in revised pack #8.

Spot on Jake. With HDMI connector-type properties injection, HDMI output is back to normal and HDMI-audio recovered. I've updated the bootpack of my Latitude 7490 guide to that affect.

HDMI issue moved to its own thread now (and fixed).

Yup, that what it seems to be: IOReg shows DP connector type when it should be HDMI; could be the reason and there certainly can be no harm trying to inject HDMI properties again.

I've tried several mods of layout ids (ig-platform-id) and/or SMBIOS without success. At the same time, I no longer have any HDMI audio output available so it's like HDMI is not recognised per sé. Time to look up the IOReg.

May be you should consider rebuilding your cache to fix it rather than boot without it... Details are available in our FAQ section.

You extract the firmware from Windows: simply run the .exe and opt to extract the files or, if you like like more complicated, open the .exe file with, say, Winzip and extract the files. The .hex firmware files are located in the BT subfolders... I'm currently running with firmware v5799 and will try this v5974 that you've posted.

I've updated Lilu + WEG to latest versions (I was using older ones) and no change; we can therefore rule those out...

I too reproduce this HDMI issue. Picture on my HDMI TV is like covered with a veil and can't be removed even when playing with display colour settings. Tried 3 x different cables to no avail. HDMI output with said cables from my Ivy Bridge laptop is perfectly Ok. So, it's clearly the HDMI output from the UHD620. A little weird because I had no HDMI output issue when I 1st installed Mojave as shown in my guide. Must be something resulting from the subsequent Mojave updates or else in the Clover config. Oh well, something new to fix I guess...

-f ? That's no longer a valid Clover flag afaik... Unless you use a very old Clover version for old Mavericks of course. Why don't you run with Mojave or Catalina (supposed to be released today)?

You should try and cache CodecComander from /L/E (and do the same for all your other add-on kexts) rather than inject it through Clover.

AirPortBrcm4360 is indeed a PlugIn kext of IO80211Family kext (hence why you "don't have it alone"...). Now that you have identified the I/O location of your card, all you need to do is follow the in instructions detailed in the guide, keeping in mind that it may not work properly/reliably on your own laptop.

You may want to refer to this recent guide which provides details of all steps, including Clover installation...

I guess you mean DW1560, right? Like any BCM4352 cards, DW1560 does not work OOB and requires patches. Did you do that, knowing that such patches are detailed in this Wireless & BT forum section? If there's anything to provide it's: 1) a zipped copy of your Clover EFI folder (with only ACPI + kexts folders & config.plist) 2) a zipped saved output from IORegistryExplorer

read our forum rules consult our FAQ section; we created it on purpose not by mistake... we have a Search facility on the forum; please use it. Thank you.

There's probably quite a lot to do here... What "instructions" did you follow? Kexts: The add-on kexts you inject are very outdated. You need to update them to the latest versions. You should not need any of those FakePCIID kexts either, just use latest Lilu + WEG kexts. Clover config, lots to do here... Use Clover Configurator app to modify your config: 1/ ACPI section: Your Skylake laptop does not appear to have any USB2.0 controllers, as such, your renaming of EHCx devices to EH0x is irrelevant and unecessary. Do you really need all those tables in your patched folder (especially SSDT.aml which is not present in the folder!) ? Are all of these patched??? I somehow doubt it. I would have removed "Drop OEM" and added "PluginType" + "FixHeaders" 2/ Boot section: Get rid of -xcpm + kext-dev-mode=1 boot options. These are defunct and useless now. 3/ Devices section: You're not injecting any properties for your iGPU in order to adjust DVMT settings. I don't believe you'll be able to boot your system until you do that. You can grab that from any existing Skylake system guide 4/ Graphics section: No need to "Inject Intel" + inject ig-platform-id 0x191b0000 once you use latest Lilu + WEG kexts. Furthermore, these were already injected in your patched DSDT... You can look it up under DSDT device IGPU. 5/ Kernel & Kexts Patches section: Wow! Where do I start? ... Get rid of all those AppleHDA patches. Remove them. Your audio should be handled by AppleALC these days, it's a Lilu Plugin. Get rid of the IOGraphicsFamily patch. Obsolete and irrelevant now. WEG will take car of that. Get rid of the IOAHCIBlockStorage trim patch. It's likely to cause issues with your Samsung 970 NVME SSD. You should not require the AppleBacklight patch either. Do you have a BCM4352 wireless card? If you don't get rid of those AirPortBrcm4360 patches that will be irrelevant to you. You should not require the AppleAHCIPort patch. I'm doubtful you'll ever need the AppleUSBXHCIPCI patch. If you need, make sure you use the patch relevant to Mojave. 6/ SMBIOS section: Select a different SMBIOS profile, then relect MacBookPro13,1 in order to generate all the necessary values that are missing 7/ System Parameters Generate a new "Custom UUID" number 8/ RT Variables section: Generate a new ROM number (from SMBIOS) Copy MLB value displayed in "Info" black box and paste it to the MLB field And, of course, make sure you use a Clover version not older than r4911.