Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 11/25/19 in all areas

  1. OpenCore - Catalina -> Monterey Installation: Download MacOS Monterey / Big Sur / Catalina app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Note: Replace Config.plist with Config-IntelWifi.plist if you have an Intel combo card Special note: E7270 OC 0.7.4 includes Alps V7 kext by Skyrilhd that enables multitouch. Sorry, some E7270 has Alps V8, then it won't work. OC 0.7.8 includes latest Alps by SkyrilHD, supports Alps v7/8 Updated to 0.8.3 - Supports Monterey 12.5.1 E7270_OC_0.8.3.zip E7470_OC_0.8.3.zip E7270_OC_0.7.9.zip E7470_OC_0.7.9.zip E7270_OC_0.7.4.zip E7470_OC_0.7.4.zip E7270_OC_0.7.0.zip E7470_OC_0.7.0.zip E7270_OC_0.6.3.zip E7470_OC_0.6.3.zip
    16 points
  2. OPENCORE Supports Mojave to Monterey Follow BIOS Configuration above Installation: Download macOS Monterey / Big Sur / Catalina / Mojave app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Resources: https://dortania.github.io/OpenCore-Install-Guide/ https://github.com/VoodooSMBus/VoodooRMI https://github.com/OpenIntelWireless/itlwm https://github.com/cholonam/Sinetek-rtsx https://github.com/0xFireWolf/RealtekCardReader/releases Updated to OC 0.8.5 Note: Config is set for Broadcom DW1830 If you have Intel, rename Config-IntelWifi to Config.plist Multiboot from OC picker is also working! Note2: When using OC 0.7.4/0.7.6 bootpack, if disk is not detected Set in Config file under UEFI/APFS MinDate=20200306 and MinVersion=1412101001000000 for Catalina Set in Config file under UEFI/AFPS MinDate=20190820 and MinVersion=945275007000000 for Mojave For OC 0.7.6, if you're booting Catalina, you'll need to replace Lilu.kext with v1.5.7, v1.5.9 causes dependency for RealtekCardReaderFriend.kext HP840G3_OC_0.8.5.zip HP840G3_OC_0.7.9.zipHP840G3_OC_0.7.6.zipHP840G3_OC_0.7.4.zip HP840G3_OC_0.6.8.zip HP840G3_OC_0.6.3.zip
    15 points
  3. Dec. 2010-Dec. 2020 It's hard to believe that it's been 10 years already! What a road since the early days of Snow Leopard on the Latitude D430! To celebrate this, we've undertaken a small forum clean-up, implemented some optimisation on the hosting server side, upgraded the community board and splashed out on a new forum Theme. We hope you'll all enjoy it and thank you for your loyalty to OSXLatitude. OSXL Crew
    12 points
  4. OpenCore Working: HD 4400 Full QE/CI DP/HDMI Video / Audio Webcam Sleep / Wake USB 2.0 / 3.0 ( not tested for speed) Speakers / Headphone SD Card Reader Fn+Up and Down Arrow for Brightness Control Audio control buttons Installation: Download macOS Monterey / Big Sur / Catalina app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Download alc_fix_BS.zip Open terminal and run the following commands: sudo spctl --master-disable cd ~/Downloads/alc_fix sudo ./install Note: Replace Config.plist with Config-IntelWifi.plist if you have an Intel combo card Boot Chime: I don't really care for it, but for those that like to have it, here's what you need. 1) AudioDxe.efi in /EFI/OC/Drivers; make sure it's added in Config file under UEFI/Drivers 2) OCEFIAudio_VoiceOver_Boot.wav in /EFI/OC/Resources/Audio //attached below OCEFIAudio_VoiceOver_Boot.wav.zip 3) In config file under UEFI->Audio, set the following settings That's it, reboot and you should hear a loud chime when you boot to the OC Picker! Updated to 0.8.3 - Supports Monterey 12.5.1 - to enable chime during boot, change in config file under UEFI/Audio >AudioSupport = Yes >PlayChime = Enabled Updated to 0.8.0 - to support Monterey 12.4 - to enable chime during boot, change in config file under UEFI/Audio >AudioSupport = Yes >PlayChime = Enabled Updated to 0.7.8 - Supports Montery 12.2.1 and Big Sur Updated to 0.7.4 If you're upgrading from older OC version, you might have to delete OpenCore from BIOS Boot Option and create a new one pointing to /EFI/OC/OpenCore.efi I've include 3 different versions of kexts for touchpad, disable / enable one that works for your system in the Config file Tested on MacOS 11.6 and 12.2.1 E7440_OC_0.8.4.zipE7440_OC_0.8.0.zip E7440_OC_0.7.8.zip E7440_OC_0.7.4.zip E7440_OC_0.6.9.zip E7440_OC_0.6.6.zip E7440_OC_0.6.3.zip HeliPort.app.zip alc_fix_BS.zip
    10 points
  5. OpenCore Installation: Download MacOS Monterey / Big Sur / Catalina app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Note: Config is set for Broadcom DW1560 If you have Intel Wifi, rename Config-IntelWifi to Config.plist Updated to OC 0.6.9 If keyboard/touchpad does not work, replace VoodooPS2Controller-Alps with VoodooPS2Controller-R6 (not included, you should be able to find in forum) Multiboot from OC picker is also working! Updated to OC 0.7.5 Supports Monterey Special note: Added PS2 kext by SkyrilHD that supports multi gestures Updated to OC 0.7.9 Support Monterey 12.3.1 Updated to OC 0.8.7 Add IntelBTPatcher Replaced SkyrilHD's voodoo with Dortania's VoodooPS2Controller which has SkyrilHD's code added E7450_OC_0.8.7.zip E7450_OC_0.7.9.zip E7450_OC_0.7.5.zip E7450_OC_0.6.9.zip E7450_OC_0.6.6.zip E7450_OC_0.6.4.zip E7450_OC_0.6.3.zip
    9 points
  6. CLOVER Specifications: Intel 6th generation Core i5-6200U 2.3 GHz, up to 2.8 GHz with Intel Turbo Boost Technology, 3 MB cache, 2 cores Integrated Intel HD Graphics 520 Non touch 35.6 cm (14 in) diagonal LED backlight FHD Slim eDP SVA Anti-glare (1920 x 1080) with camera System can be configured with a hard drive and M.2 SSD drive / NVMe 8192 MB total system memory (8192 MB x 1) Up to 32 GB - DDR4 PC4-17000 (Transfer rates up to 2133 MT/s) Intel Wireless-AC 3165 802.11 a/b/g/n/ac (1 x 1) WiFi and Bluetooth 4.0 combo (non-vPro) HP Module with NXP NFC Controller NPC100 Intel Ethernet Connection I219-V 10/100/1000 Ethernet Synaptics Touchpad Audiio Conexant CX20724 - VendorID: 0x14f150f4 Integrated HD Webcam (1) USB 3.1 Gen 1 charging (1) USB 3.1 Gen 1 (1) USB Basic Type-C (1) DisplayPort (1) VGA (1) RJ-45/Ethernet (1) Docking connector (1) Headphone/microphone combo (1) AC (1) External SIM (1) SD media card reader, supports SD, SDHC, SDXC Working: full graphics acceleration on Intel HD520 iGPU, including brightness control (F5 and F6) multi-display with DisplayPort OOB, VGA audio, microphone input and headset output (F8 and F9) - Mute button not working GigEthernet LAN connection wireless and bluetooth with any compatible card (a DW1560 in my case, no Whitelisting) left and right USB ports including USB Type-C integrated webcam (OOB) CPU power management sleep (Lid, Energy Saver settings, Apple menu, PWR button) & wake (Lid, PWR button) battery management (with SMCBatteryManager v1.0) keyboard and touchpad (with VoodooPS2Controller v1.9.2) keyboard backlight (Fn + F3) touchpad including tap-to-click, scrolling, mouse buttons (can be disable with prt scr key) Partially working: RTS522a microSD card reader (read-only mode) - after sleep, need to eject and reinsert New updated kext allow read and write Not working: TrackStick Finger Print reader Wifi button Mute button (grayed out) Fixed with AppleALC version 1.6.1 by Human7900 BIOS Settings: Installation: Follow the standard UEFI Clover guide Replace contents to /EFI/Clover after installing Clover HP840_G3.zip Updates: Added VoodooSMBUS for better touchpad experience, most gestures work! HP840G3_BetterTouchpad.zip Add HPFanReset.efi to /EFI/Clover/drivers/UEFI HPFanReset.efi.zip Post install: Install CsmVideoDxe.efi to fix stretched Clover boot screen using Clover Configurator. The version from Clover installer does not work. Change BIOS settings for Secure Boot Configuration Configure Legacy Support and Secure Boot = Legacy Support Disable and Secure Boot Disable Note: Files tested on Catalina, Mojave, High Sierra, El Capitan ( Just need to add boot arg -no_compat_check) Credits: Rehabman for hot patched files Sinetek /Cholonam for Sinetek-rtsx (SD Card reader) Leo-laps / 1Revenger1 for VoodooSMBUS & VoodooRMI
    6 points
  7. /!\ Refreshed Jan 2023 /!\ Target macOS release: Big Sur 11.x This is a Clover-based installation using the standard vanilla method detailed below: Working: full graphics acceleration on Intel HD4000 graphics (with Lilu v1.6.x + WEG v1.6.x) multi-display with HDMI OOB audio, including jack microphone input and headset output (with AppleALC v1.6.x & layout 12 + CodecCommander v2.7.x) HDMI audio (with Capri Framebuffer properties injection) built-in GigEthernet LAN connection (with AppleIntelE1000e v3.1.0 or latest IntelMausiEthernet kext) wireless and bluetooth with any compatible card integrated webcam (OOB) full CPU power management, including Turbo boost (with CPU-specific generated ssdt) sleep (Lid, Energy Saver settings, Apple menu, Fn-F1, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) SD card reader (with DSDT patch or property injection, for compatibility with Apple's default card reader) keyboard (with Dr Hurt's VoodooPS2Controller R6 + DSDT patch for brightness control) touchpad including tap-to-click (with Dr Hurt's VoodooPS2Controller R6) left combo eSATA/USB2.0 + right USB3.0 ports (with Hackintool's generated USBPorts; optional FakePCIID kexts for multiplexing) ExpressCard slot OOB Not working: VGA output unsupported Not tested: SmartCard reader fingerprint scanner GeekBench v4.4.x (64bit) results: 1) 11.x USB installer creation Using a USB key of 16GB minimum, create a Big Sur USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Big Sur installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_16GB) The process will take several minutes. Once completed: install Clover boot loader on the USB installer with the following customised settings: Clover for UEFI booting only Install Clover in the ESP UEFI drivers Recommended drivers FSInject SMCHelper Human Interface Devices (optional) PS2MouseDxe USBMouseDxe FileSystem Drivers ApfsDriverLoader Memory fix drivers OpenRuntime Additional Drivers (optional) PartitionDxe Themes (optional) Install Clover Preference Pane (optional) you may use version r5144 attached below Clover_r5144.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip add the (unzipped) HFSPlus driver attached below to the EFI/CLOVER/drivers/UEFI folder HFSPlus.efi.zip open the EFI partition and transfer the files and folders from the Latitude E6230 Big Sur Clover pack below to the EFI/CLOVER folder Clover_Pack_E6230_BigSur.zip /!\ If your E6230 is fitted with a different CPU than the i7-3540M, please remove the Power Management SSDT of the pack until you replace it by one applicable to your model (whether an existing SSDT or your own generated one) in the post-install phase. 2) 11.x installation boot the Big Sur USB installer at the Clover main menu, go to the "Options->configs" menu and select the "config_MBP11,1" config file. This is required to install (and later update as/when required) Big Sur on a supported Mac model. Press [ESC] twice to return to Clover main menu. at the Clover main menu, select the "Install macOS Big Sur" partition and press [ENTER] at Big Sur main installation screen, select Disk Utility to create & format APFS the target Big Sur disk/partition/volume. Note that installation won't work if target disk/partition/volume is formatted HFS+ exit DU and return to Big Sur main installation screen, then proceed with installation the installation process will reboot a temporary macOS installer partition to complete the installation. repeat this until the temporary partition is replaced by a final <Big Sur partition name> on Preboot entry. Each time, reboot via your USB installer and make sure to select the "config_MBP11,1" config file. when the partition <Big Sur partition name> on Preboot is displayed at Clover main menu, no need to call on the "config_MBP11,1" config file, the default one will do (MBP10,2 SMBIOS + -no_compat_check boot arg). 3) Post-installation tuning Once the finalised Big Sur installation has booted, complete the 1st boot configuration tuning Once at the desktop, mount the EFI partition of your Big Sur disk Copy the EFI folder of the E6230 Big Sur Clover pack to the mounted EFI partition You may then modify your SMBIOS info using Clover Configurator app and ensure you have unique numbers or unique combination of numbers (MLB, ROM, SystemSerialNumber and SystemUUID). Please note that, with MBP10,2 SMBIOS, Big Sur will not offer any updates because it'll be running on an unsupported platform. You'll only get updated offered if you boot with the MBP11,1 config file, MacBookPro11,1 being a supported model.
    6 points
  8. NB: This is a revival of the article I had initially published at InsanelyMac to answer recurring questions that had been raised in the Opencore thread that lives there. Posted October 2, 2021 The Dortania documentation refers to the DVMT pre-allocated memory or "stolen memory" when they mention "memory reserved for the iGPU". Years ago, @Firewolf described in details the relationship between stolen memory and DVMT pre-allocated memory on his blog: https://www.firewolf.science/2015/04/guide-intel-hd-graphics-5500-on-os-x-yosemite-10-10-3/ There's a more recent thread from him here: https://www.insanelymac.com/forum/topic/345377-surface-pro-patch-the-framebuffer-properly-to-get-rid-of-the-dvmt-assertion-patch/ It can be difficult to understand and differentiate DVMT pre-allocated memory, stolen memory, framebuffer memory, cursor memory, framebuffer size, cursor bytes, etc. And all of these have got nothing to do with VRAM of course... Some of us are familiar with the information provided by @Pike R Alpha many moons ago, the WhateverGreen User Manual or the Hackintool app though none of those clearly define what the various memory instances are. Several years ago, @Rehabman also attempted to explain this and his writings somehow collided with most people's comprehension of things. For instance, when @Pike, WhateverGreen or Hackintool refer to stolenmem and fbmem, @Rehabman spoke of framebuffer memory size and cursor bytes. In the case of the Haswell Azul framebuffer layouts, @Rehabman also spoke of the DVMT pre-alloc requirements when the others speak of stolenmem. Inevitably, this can lead to confusion... Definitions: See wikipedia and Google searches. VRAM = Video RAM. Common definition is that it stores the pixels and other graphics data rendered on a computer screen. DVMT = Dynamic Video Memory Technology. A technology used by Intel to dynamically allocate system memory to use as video memory to handle graphics. DVMT pre-allocated memory is the minimum amount, in multiples of 32MB, that will be allocated to the iGPU for handling graphics. By far and large, manufacturers set this to 32MB by default in BIOS (or certainly used to). Framebuffer = a memory buffer held in RAM and containing a bitmap of a video frame, i.e. all the data related to the pixels of an image to be displayed on screen (eg: colours, resolution, etc.). Stolen memory = basically, this is the same as the DVMT pre-allocated memory. As far as Apple's framebuffer drivers/kexts are concerned: framebuffer size (aka stolenmem for WhateverGreen*) = the size, in bytes, of a framebuffer layout (it may change according to image characteristics), as defined in the driver/kext. cursor bytes (aka fbmem for WhateverGreen*) = the size, in bytes, of a framebuffer layout's overlay used for handling mouse cursor (without modifying the framebuffer's data), as defined in the driver/kext. framebuffer VRAM (aka unifiedmem for WhateverGreen) = the max. amount, in bytes, of VRAM allocated by a framebuffer layout, as defined in the driver/kext (since Haswell and Yosemite, this usually is 1536MB). * As stated above, I believe that Whatevergreen only got it right for Haswell Azul framebuffer layouts with which stolenmem, fbmem and cursormem match their target. Thereafter, I'm of the opinion that WhateverGreen used incorrect names where stolenmem means the actual framebuffer size and fbmem means the actual cursor bytes (size), as stated by @Rehabman. Mac OS X/OS X/macOS graphics framebuffers: Let's start by looking at a few examples as illustrated in the WhateverGreen User Manual. 1) Haswell Azul mobile framebuffer 0x0a260006 (used for HD4200/HD4400/HD4600 iGPUs on laptops): ID: 0A260006, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP [2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 If we look inside the binary code of the Haswell Azul framebuffer kext, we'll find: 0600260A 01030303 00000002 00003001 00006000 00000060 D90A0000 D90A0000 00000000 00000000 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 which translates to: 0600260A -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00000002 -> 32MB stolen mem (framebuffer-stolenmem) // Rehabman's DVMT-prealloc requirement 00003001 -> 19MB FB mem (framebuffer-fbmem) // Rehabman's framebuffer size 00006000 -> 6MB Cursor mem (framebuffer-cursormem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) D90A0000 -> Backlight freq 2777MHz D90A0000 -> Max. backlight freq 2777MHz 00000000 00000000 00000800 02000000 30000000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 30020000 01050900 00040000 87000000 -> port #2/FB@1: index 01, busid 05, pipe 0900, type 00040000=DP (framebuffer-con1-type), flags 87000000 02040900 00040000 87000000 -> port #3/FB@2: index 02, busid 04, pipe 0900, type 00040000=DP (framebuffer-con2-type), flags 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 2) Broadwell BDW mobile framebuffer 0x1626006 (used for HD5300/HD5500/HD5600 iGPUs on laptops): ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - ConnectorLVDS [1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - ConnectorDP [2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - ConnectorDP 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 If we look inside the binary code of the Broadwell BDW framebuffer kext, we'll find: 06002616 01030303 00002002 00005001 00000060 D90A0000 D90A0000 00000000 00000000 00000000 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 which translates to: 06002616 -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00002002 -> 34MB stolen mem (framebuffer-stolenmem) // Rehabman's framebuffer size 00005001 -> 21MB FB mem (framebuffer-fbmem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) D90A0000 -> Backlight freq 2777MHz D90A0000 -> Max. backlight freq 2777MHz 00000000 00000000 00000000 00000800 02000000 30020000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 30020000 01050B00 00040000 07050000 -> port #2/FB@1: index 01, busid 05, pipe 0B00, type 00040000=DP (framebuffer-con1-type), flags 07050000 02040B00 00040000 07050000 -> port #3/FB@2: index 02, busid 04, pipe 0B00, type 00040000=DP (framebuffer-con2-type), flags 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 3) Skylake SKL mobile framebuffer 0x19160000 (used for HD520/HD530/HD540 iGPU on laptops): ID: 19160000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000090F TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Model name: Intel HD Graphics SKL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 We can't look at the binary code of the Skylake SKL framebuffer because Apple changed the way things are coded inside but it basically translates as follows: 00001619 -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00002002 -> 34MB stolen mem (framebuffer-stolenmem) // Rehabman's framebuffer size 00005001 -> 21MB FB mem (framebuffer-fbmem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) 6C050000 -> Backlight freq 1388MHz 6C050000 -> Max. backlight freq 1388MHz 00000800 02000000 98000000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 98000000 01050900 00040000 87010000 -> port #2/FB@1: index 01, busid 05, pipe 0900, type 00040000=DP (framebuffer-con1-type), flags 87010000 02040a00 00040000 87010000 -> port #3/FB@2: index 02, busid 04, pipe 0a00, type 00040000=DP (framebuffer-con2-type), flags 87010000 With the exception of the Haswell Azul framebuffer, we can see that Broadwell BDW and Skylake SKL framebuffers define framebuffer size (WEG's stolenmem) and cursor bytes (WEG's fbmem) characteristics and no DVMT pre-allocated memory (i.e. proper stolen memory). This extends to Kaby Lake KBL framebuffers and later. In my opinion, it's fair to say that @Rehabman's description and wording are the most appropriate/best ones when the WEG view of things got somehow misled by following through on the Haswell framebuffer decoding. To me, there was some mixup, leading to confusion and the said confusion has remained ever since... Confusion... why? Because of several things: 1) the observation that the Haswell Azul framebuffers used on Hacks (0x0D220003 for desktops and 0x0A260006 for laptops) defined: a DVMT pre-allocated memory (= Stolen memory) size of 32MB a framebuffer size of 19MB a cursor bytes of 0MB (desktops) and 6MB (laptops; required to be increased to 9MB to fix a minor graphics glitch on some systems) 2) the observation that the Broadwell BDW framebuffers used on Hacks (0x16220007 for desktops and 0x16160006 for laptops) defined: no DVMT pre-allocated memory requirement at all framebuffer sizes of 38MB and 34MB respectively cursor bytes of 38MB and 21MB respectively 3) the observation that the sum of framebuffer size + cursor bytes must be lower than the size of the DVMT pre-allocated memory, failing which a KP occurs at graphics initialisation during startup/boot. 4) In the case of the Haswell Azul framebuffers: DVMT pre-allocated memory requirement is set at 32MB framebuffer size + cursor bytes = 19+0 | 19+6 (or 19+9) = 19MB | 25MB (or 28MB) which is lower than DVMT pre-allocated memory 32MB -> All is Ok by default. 5) In the case of the Broadwell BDW framebuffers: framebuffer size + cursor bytes for desktops = 38+38 = 76MB which is greater than the usual/default 32MB DVMT pre-allocated memory of most desktops, unless adjusted in BIOS framebuffer size + cursor bytes for laptops = 34+21 = 55MB which is greater than the usual/default 32MB DVMT pre-allocated memory of most laptops, unless adjusted in BIOS -> Not Ok by default, Kernel Panic (KP) encountered. 6) And the story is the same with subsequent Skylake, Kaby Lake, etc. framebuffers. Solution: 2 x solutions were engineered to address the issue of KP at graphics initialisation. increase the DVMT pre-allocated memory set in BIOS. Could be complicated and tricky for PCs that do not offer this in BIOS Setup but made easy with Grub Shell if DVMT pre-allocated memory can be identified in BIOS. This method is usually required to gain 4K output. patch the Broadwell, Skylake, Kaby Lake, etc. framebuffer layouts to reduce framebuffer size and cursor bytes so that the sum of them totals less than the usual default DVMT pre-allocated memory of 32MB. This solution does not usually support 4K output. Although some people do opt for the 1st solution, most people just adopt the 2nd one. How were the framebuffer patches derived? If we look at the framebuffer patches that are commonly and generally used, we can observe that they set: WEG's framebuffer-stolenmem property , i.e. framebuffer size to 0x01300000 = 19MB (DATA type set to 00003001) WEG's framebuffer-fbmem property, i.e. cursor bytes to 0x00900000 = 9MB (DATA type set to 00009000) i.e. the values typically used on laptops with Haswell iGPUs, this simply because 19+9=28MB which is < 32MB. This is where it all appears to come from. Is this correct? By far and large, it is. But the need to apply such framebuffer patches depends entirely on the host PC's default DVMT pre-allocated memory. On desktop and laptop PCs where DVMT pre-allocated memory can be adjusted in BIOS setup, the patches are unnecessary as long as the DVMT value that is set exceeds the total of the framebuffer size + cursor bytes of the selected/target graphics framebuffer. Typically, a value of 64MB or 96MB takes care of things perfectly, including 4K. Of course, those PCs manufactured with default DVMT pre-allocated memory set to 64MB or more are unlikely to encounter any issue at all. The framebuffer patches are also unnecessary if the default DVMT pre-allocated memory is increased either though BIOS binmod (difficult and risky) or through Grub shell mod (easy and quickly reversible). This is well illustrated on @Firewolf's blog, linked above (there are other places too such as @Jake Lo's FAQ item here). To give an example, on some Dell laptops (eg. Broadwell Latitude E7x50 or Skylake Latitude E7x70), DVMT pre-allocated memory can be increased by booting a Grub shell and entering the following command: setup_var 0x432 0x3 This sets DVMT pre-allocated memory parameter located at offset 0x432 to 96MB (0x1 for 32MB, 0x2 for 64MB, 0x3 for 96MB, etc.), the default setting for the laptop in this example being 32MB. This setting will remain valid/in place until BIOS is reset to default settings. It's required to obtain 4K output out of DP/HDMI. Of course, different computers will have different locations/offsets for DVMT pre-allocated memory. What should I do then? As stated above, the framebuffer patches apply to most if not all cases. But not for 4K output. Those who feel adventurous or who are computing-literate may opt for the BIOS adjustment alternative. In all cases, the 1st thing to do is to look at the default framebuffer size and cursor bytes settings of the targeted graphics framebuffer, then decide if the sum of them both fits or not in 32MB or any other value set in BIOS for DVMT pre-allocated memory. Can I use different values? Absolutely! As long as the golden rule is respected: framebuffer size + cursor bytes < DVMT pre-alloc mem or, in WEG's conventions, stolenmem + fbmem < DVMT pre-alloc mem. To give a practical example, I experimented on my Skylake/HD520 Dell Latitude E7270 Hackintosh laptop: default DVMT pre-allocated memory value set in BIOS: 32MB target SKL framebuffer layout: 0x19160000 default framebuffer size: 34MB default cursor bytes: 21MB sum of framebuffer size + cursor bytes: 55MB (i.e. > 32MB) Booting with default DVMT pre-alloc mem + no framebuffer patches -> KP/freeze Booting with default DVMT pre-alloc mem + framebuffer size 20MB + cursor bytes 12MB -> KP Booting with default DVMT pre-alloc mem + framebuffer size 19MB + cursor bytes 9MB -> Ok, full graphics acceleration, no 4K output Booting with default DVMT pre-alloc mem + framebuffer size 20MB + cursor bytes 10MB -> Ok, full graphics acceleration, no 4K output Booting with DVMT pre-alloc mem set to 64MB (Grub shell) + no framebuffer patches -> Ok, full graphics acceleration + 4K output Booting with DVMT pre-alloc mem set to 96MB (Grub shell) + no framebuffer patches -> Ok, full graphics acceleration + 4K output
    5 points
  9. OPENCORE - Ventura Supports Ventura Follow BIOS Configuration above Working: full graphics acceleration on Intel HD520 iGPU, including brightness control (F5 and F6) multi-display with DisplayPort (Video & Audio) audio, microphone input and headset output (F8 and F9) Mute button IS working by Human7900 GigEthernet LAN connection wireless and bluetooth with any compatible card (a DW1560 in my case, no Whitelisting) left and right USB ports including USB Type-C integrated webcam CPU power management sleep (Lid, Energy Saver settings, Apple menu, PWR button) & wake (Lid, PWR button) battery management keyboard and touchpad keyboard backlight (Fn + F3) touchpad with gestures, mouse buttons (can be disable with PrtScr key) RTS522a microSD card reader Not working: Trackpoint and mouse buttons Finger Print reader Wifi button Installation: Download macOS Ventura app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Resources: https://dortania.github.io/OpenCore-Install-Guide/ https://github.com/VoodooSMBus/VoodooRMI https://github.com/OpenIntelWireless/itlwm https://github.com/cholonam/Sinetek-rtsx https://github.com/0xFireWolf/RealtekCardReader/releases Updated to OC 0.9.5 Note: Config is set for Broadcom DW1830 If you have Intel, rename Config-IntelWifi to Config.plist Multiboot from OC picker is also working! HP840G3_OC_0.9.5.zip HP840G3_OC_0.8.5_Ventura.zip
    5 points
  10. Ventura - OpenCore Installation: Download MacOS Ventura app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Note: Replace Config.plist with Config-IntelWifi.plist if you have an Intel combo card (not tested) SMBIOS, ig-platform-id, device-id, USBPorts kext set to MacBookPro14,1 to support Ventura OC 0.8.5 includes latest Alps by SkyrilHD, supports Alps v7/8 for multi touch Updated to 0.8.5 - Supports Ventura only, won't boot for Monterey and below E7270_OC_0.8.5.zip E7470_OC_0.8.5.zip
    5 points
  11. I thought long about making a post about an unfinished driver. But here we go. This ALPS driver is a more updated version from Dr. Hurt's kext. It allows using VoodooInput which is a Magic Trackpad II emulator. This means one can use all native gestures in macOS. I've never had a MacBook with multitouch support, so the gesture thing was a new thing to me. But after using these gestures, I cannot tell how impressed I am. Since Dr. Hurt's last contribution was around the beginning of 2017, I decided to port VoodooInput to ALPS, as the driver is, at this point, very out of date and the calculation in the kext is not the best (I always had weird issues with it). The reason is also that I want to learn C++. After trial-and-erroring, I managed to get VoodooInput to work (thanks to usr-sse2) on my E7250 with V7. This was mainly done as a "proof of concept" to show that it was possible. But doing so, I learned so much that I decided to maintain the kext for a while. This is the beginning of the driver. There is still more to be done. Since the kext is very old, the VoodooPS2Controller kext lacks the improvements that are available in the acidanthera repo. I will try merging the VoodooPS2 improvements from acidanthera with the ALPS driver and go on from there. But the limitation comes with an inexperienced C++ developer :P. Any developer is welcome to improve the driver even more. V1-V6 have partial support and need testing. Any contribution to the project would be great! Current plans: - As I said, I want to merge the VoodooPS2 kext from acidanthera with the current driver and after the driver is finished merge it again with acidanthera to make it more uniform. - I want to support more trackpads (Currently I'm trying to get V8 working as it never worked with Dr. Hurt's kext). Features: - supports V1, V2 and V6 as a normal mouse - supports V3, V4 and V5 (not tested yet) - supports V7 (Everything works, three finger drag is a bit unstable though) - supports V8 - supports all native gestures - synced with the latest acidanthera VoodooPS2 repo - compatible from 10.11 Other versions: For other unsupported versions of ALPS, I've published a kext that has improved scrolling (thanks to 1Revenger1 and icedman): https://github.com/SkyrilHD/VoodooPS2-ALPS/releases/tag/1.0.0 Source code: https://github.com/SkyrilHD/VoodooPS2-ALPS Latest release: https://github.com/SkyrilHD/VoodooPS2-ALPS/releases Credits: - Dr. Hurt (for the initial driver) - 1Revenger1 (for updating VoodooPS2-ALPS) - usr-sse2 (for the Synaptics code which the ALPS driver uses) - acidanthera team (for further improvements to the driver) Hopefully, I did not forget anything to mention.
    5 points
  12. Hi All, I am happy to be writing you to say thank you from my newest machine, Monterey 12.2.1 built on a Dell Latitude 7490 booting with Opencore 0.78. I recently learned about Hackintoshes and it has been fun and frustrating to learn about. I referred to so many pages on this site that I wanted to offer a general thank you--seriously thank you! I also just wanted to say that I am happy to share with anyone with this setup (or one similar) access to the EFI and/or other configuration files. I am not sure about the protocol for this forum, but if anyone is interested, please let me know. In the meantime, best of luck! With sincere thanks, Jake
    5 points
  13. Dell Optiplex 3070 Micro Form Factor 100% working EFI. Dell Optiplex 3070 Micro 100 Percent Working.zip Thanks Jake for the support.
    5 points
  14. In case the above Google link becomes unavailable... Dell_Precision-M6800_Jul2019.zip
    5 points
  15. 'working on my Clover setup and manage to significantly reduce the freezes though not entirely. Sometimes, system still freezes a few seconds after reaching desktop. But it seems to run pretty stable most of the time. Graphics acceleration is acceptable at this stage though not bug free: occasional slow movements on screen and some contents leftovers after closing a window for instance. Or unrecoverable limping system of complete freeze after attempting to watch a Youtube video in Safari. But, hey, what can we expect out of a KBL framebuffer on a Skylake system? Other than than, everything appears to work properly on the E7270: graphics acceleration: Ok with some defects and reduced/degraded performance brightness control: Ok touchscreen: Ok HDMI output: Ok mini-DP output: Ok audio (incl. DP audio): Ok LAN: Ok wireless & Bluetooth (BCM9460CS2): Ok touchPad: Ok USB ports: Ok sleep & wake: Ok SD card reader: Ok Whether this ends up sustainable in the long run for Skylake laptops remains to be seen but you never know... Is it usable for the time being? Clearly not. Edit: Instant wake issue on sleep and HDMI output now sorted. EFI_Clover_r5146_E7270_13.0.b1.zip EFI_Clover_r5146_E7270_13.0.b1_v2.zip EFI_Clover_r5146_E7270_13.0.b1_v3.zip EFI_Clover_r5146_E7270_13.0.b1_v4.zip
    4 points
  16. As suggested by @aben at IM, I experimented with KBL framebuffer settings on my Skylake/HD520 Latitude E7270. I also updated all add-on kexts to latest versions (Lily & PlugIns) and replaced good old ACPIBatteryManager + FakeSMC by their VirtualSMC equivalent. This allowed me to boot Ventura b1, complete 1st boot setup and reach desktop; the laptop still freezes shortly afterwards so something's still iffy but at least I can boot and with apparent full graphics acceleration: I don't know about older generations but there seems to be hope for Skylake laptops.
    4 points
  17. Last update: 17 Sep 2017 UPDATE: 17 - 09 - 2017 Just wanted to clear few things about my commitments to community, and development on my projects which has been going slow due to my personal life as I have been hit really hard since an year, and I am trying to sort out personal things still. So decided to take timeout on my commitments to my projects and put my attention on personal life first. Don't expect any regular updates on this project and others projects of mine till end of this year 2017. It does not mean I will not be working, and it is just that I won't post any update or respond to you all unless I have something worth to share. I know many of you are disappointed with me and some of my choices/decisions for the last one year, but believe me I had no other option and good reason for that. So your patience will be rewarded properly once I have started releasing updates as I have big plans and willing to commit myself to long term development, and I apologize for not keeping up with promises so far. In case I fail to keep up like I promised above, then I will give up and release all of my work to others to continue. Hope you understand and support me with beta tests when I need them Thanks Hi everyone, This is a multitouch driver for ELAN, FocalTech and Synaptics touchpad for Mac OS X based on the documentations available and some ideas from VoodooPS2, ApplePS2 and Linux open source code. I have successfully accomplished everything so far and added many new features to take advantage the touchpad completely to make it close to Apple touchpad in every way. Also my driver is implemented with my own universal logic for all the features, so it can be adapted to all touchpads easily and I'm still improving these to achieve even better results. My driver supports every hardware version of ELAN touchpads except version 1 (which is too old and can't find in existing notebooks will support that if i get some testers), mostly all available FocalTech touchpads and Synaptics touchpads (still experimental) with firmware version v7.5+. NOTE: For Synaptics, it was developed based on my touchpad hardware i have, so support is limited to touchpad with firmware version 7.5+ only, but will try to improve support other hardwares also if users interested in my features and help me with beta testing. FOR BUG REPORTING: Please read the below threads which explain the features after installing the driver, so you can understand and learn how to use every feature. If anyone still have doubts/issues then PM me to get help from myself (or) post them in other thread about issues so others can help you. I will respond to you mostly during weekends only for some time. FEATURES DETAILS: (UPDATED FOR v4.6) Touchpad features: Click here to learn Keyboard features: Click here to learn Supports OS X version 10.6 or later (10.6 support is only from v4.4) For Prefpane, try to install the version from this link, and add the prefpane to start up items: http://www.hackintosh.zone/file/997-correct-preference-pane-trackpad-macos-sierra/ UPDATE: 06-06-17 Hi everyone, It has been long time since I have given you all an update on my development. The reason for this was I had a pretty rough personal life and busy time in my job last few months, so I was really under big stress and had busy days which did not allow me to do any progress on my projects. Good news is that I was able to sort some of my issues, and find some time to continue my projects again. I have already done some analysis on my project, and figured that I had to do some major code rewrite (most of the code was depending around work arounds which are not optimized well for the time being back then) in order to better support future hardwares and also improve features with ease. My plan is Setup a way to support and track bugs from users Setup a way to gather feedback from users Re-build the project from the scratch with good design for cross-platform support in mind, to support multiple touchpad vendors and interfaces (thinking about I2C) as universal driver Refactor the project code with as much clean code (so when I make it open others can understand) as possible of mine from the scratch Finish basic features (Keyboard and Mouse emulation) Integrate basic vendor specific features Develop and Integrate basic prefpane of mine Release first beta to test Integrate and implement my old driver features one by one for better stability Update prefpane for new features and release another beta Update and improve support for newer hardware based on linux and other sources Finish integrating all the features of old driver by reviewing each one with community feedback Add new features and improve it's stability and performance I have big list of TODO's, but I promise this time that I will try to finish each of them as soon as possible with a beta release happening very soon before the end of this month in best case. Understand your patience is really needed here, as I do not want to rush and have limited time of mine. Also, I am gonna give weekly update on my progress if possible when I have finished my milestones. I will try to respond to your PM during weekends, and if you want to be beta tester then send me your skype ids with GMT time via PM. One more thing, current version of my driver is deprecated and so will not be continuing this. But, I will try to give you some support if there is a need before I finish my new version of driver for any issues which are not big enough for time being. Thanks for your support and co-operation. PS: Sorry for those who want my project to be open sourced now, as I cannot do that until I finish above TODO's. Hope you understand, and support me as I really worked hard on this project. I have worries to get this open right now, and understand that with more people development can progress faster but opening this right now might create issues and end myself supporting to the development in the long run due to fragmentation. I would request you to go through plist editing for controlling the features (as I have a lot of them and its important users to know about those details, because it will allow the driver to be tweaked as you want and my default values are not going to be best for every touchpad or user) for now (will make my own prefpane very soon within 3 months, and its a promise). Going to update my thread which details the features every week one after another for keeping it updated with latest version. Version v4.7 beta 5 (10 - 12 - 2016) (work in progress, available to try from attachments). Added back feature multi finger drag due to users request (can be dragged using 1-3f, Note: This drag wont be as smooth as 1f because the data is not as good as 1f in 2-3f which is why I stopped working on this long time ago, but currently it works nicely and usable in my touchpad. So its usage varies to each touchpad). You have to hold fingers for 2-3 sec at fixed position and move to trigger drag. Improved support for Sierra Support for new style prefpane (most of the features wont control my feature, but I will fix them by next weekend to match them) [Drag, scroll, double click speed can be controlled inside Accessibility Settings->Mouse & Trackpad] [Experimental] USB mouse can now stop trackpad if you enable Accessibility setting of Ignore Trackpad [Works only in 10.10 or lower (?). Will find a way for new OS X versions asp] Improved scroll inertia with more control options in Plist to choose Fixed Sierra Caps Lock bug using a workaround Fixed a bug with some new ELAN touchpads which have issues with virtual buttons acting weird if pointing was enabled at button area, so added option to diable/enable this in plist Fixed sierra OS X functions like Launchpad, Dashboard, Mission control etc., which are not working by redirecting to new keyboard shortcuts. (Needs to be configured at Keyboard shortcuts) Updated support for Asus keyboard backlight with two levels Several minor bug fixes and improvements And more to come as am still looking at improving others things that are buggy and also using feedback from users Version v4.6.5 Released Major code optimizations Updated support for 10.12 (Still some Fn keys wont work, will try to fix close to release) Added plist options to control Apple Trackpad prefpane values for 10.12 Several bug fixes and improvements Version v4.6 Fixed CapsLock key change plist option Fixed a firmware bug in ELAN v3 hardware Updated driver to accept new revisions of ELAN Touchpad to be recognized as Version 4 Added plist option to disable the touchpad when LID id closed (Enable back auto when its opened)) which will stop strange behavior from touchpad when using HDMI in some systems. Pointer acceleration enhancements (new plist options to control) Partial support for the extra buttons and track point from Synaptics trackpad Improved support for synaptics Updated documentation for features Several minor bug fixes and optimizations Version v4.5 Added new plist option to control touchpad edges dead zone Added plist option to change 2f and 3f tap default actions Added option to tweak pointing acceleration Added 4f pinch gesture and plist option (ELAN and Focaltech) Updated plist options to better organize Improved 2f dragging in clickpads Improved edge swipes Fixed synaptic touchpad sleep issue seen in some systems Fixed some keyboard bugs Several improvements, minor bug fixes and optimizations Version v4.4.5 : Improved support for Synaptics touchpads (Clickpad working fine now) Updated support for new ELAN touchpads Improved edge swipes Fixed a bug with Karabiner app to allow mapping Several bug fixes and optimizations Version v4.4 : Released (For Asus keyboard backlight auto off, use updated DSDT patch and v2.5 Fn keys kext) Improved support for Synaptics touchpad (Clickpad still have some issues so i need beta testers) Improved support for some new ELAN and Focaltech touchpads Improved pointer acceleration Reworked scrolling Improved Swipes, Zoom and Rotations Added more plist options to tweak the gestures and option to control delay after sleep Added GIGABYTE Fn key mode layout Added support for 10.6 (32bit build) Fixed several bugs in both keyboard and Touchpad Optimizations Version v4.3 : Added support for Synaptics touchpads (Firmware v7.5+) found in new laptops but still its experimental for others as it has not been tested on many laptops. (Tested only on Lenovo Z50-70 and G400) Added support for unsupported touchpads to work in enhanced mouse mode without multi touch Improved support for Focaltech and ELAN touchpad (especially ELAN v2) Improved pointing and scroll with new smoothing features and other improvements which can be controlled in plist Improvements and optimizations for all features Added plist option for keyboard to make Num Lock into clear instead of soft controlled num lock mode Added Fn keys mode layout for Lenovo Added support for ACPI brightness controls from EC calls (You have to use DSDT patch) Fixed many bugs For the complete change log of all the updates follow this thread: https://osxlatitude.com/index.php?/topic/1966-elan-touchpad-driver-issues/ FEATURES OF ELAN v4 HARDWARE, FOCALTECH and SYNAPTICS: (Supports up to five fingers touch) Mouse mode with Virtual Buttons Left, Right and Middle Tapping - Up to 5 fingers Clicking - Up to 5 fingers Dragging : Tap to release and Finger Lift ⃠Left Button Drag, Double Tap Drag, Single Tap Drag and Click Drag Corner Tapping Scrolling - Single finger Edge and Two Fingers swipe Continuous, Linear, Sling and Inertial scroll effects Finger Press - Up to 5 fingers Swiping - Edge, Three and Four Fingers Zoom - Two fingers pinch zoom, OSX Zoom with Keyboard 4 (Elan, Focaltech) & 5 fingers Pinch gesture Rotations - Arc and Swipe Rotations Accidental Input/Palm check when typing Fn Keys Mode Features Toggle Full customization FEATURES OF ELAN v2 and v3 HARDWARE: (Supports up to three fingers touch) Mouse mode with Buttons Left, Right and Virtual Middle Tapping - Up to 3 fingers Dragging - Tap to release and Finger Lift ⃠Left Button Drag, Double Tap Drag and Single Tap Drag Corner Tapping Scrolling - Edge Scroll and Two Fingers Continuous, Linear, Sling, Circular and Inertial scroll effects Finger Press - Up to 3 fingers Swiping - Edge and Three Fingers Zoom - Two fingers pinch zoom, OSX Zoom with Keyboard Rotations - Arc, Circular and Swipe Rotations Accidental Input/Palm check when typing Fn Keys Mode Features Toggle Full customization HOW TO INSTALL: Remove any existing "ApplePS2Controller, VoodooPS2Controller, AppleACPIPS2Nub, ApplePS2Keyboard and old Elan Touchpad" kexts if you have already installed from the HDD '/System/Library/Extensions ', '/Extra/Extensions', and '/System/Extensions/Library/myHack.kext/Contents/Plugins/' (if you used myHack USB installer for OSX). If you use USB installer to boot (used to install OSX), then you have to remove the above kexts from USB '/Extra/Extensions'. Install the Kexts (Recommended to use Kext utility for installing) inside the attached zip file using any kext installing methods (In clover, some systems may have problems with kext injection, so try to install them to System/Library/Extensions in that case). 
 ​ NOTE: From v3.3, there is only one kext as my driver in the attached zip file. For Support PM me or POST here . I may respond slowly sometimes due to busy life. NOTE: Please don't mirror my files at other places, let the people know about this thread for the latest version and support. NOTE: I've worked very hard on this driver (especially ELAN v2, 4 and Focaltech without hardware) and will try to continue support in future. I do the development everyday with some time dedicated to this and many other projects. But i need your support so i can get more time to spend on these projects for improvements. Also we maintain this website without ads for all of you and it costs a bit for us to host. IF POSSIBLE PLEASE MAKE A DONATION BY CLICKING BELOW PAYPAL DONATE BUTTON FOR ME Paypal: FOR WEBSITE DONATE HERE: http://www.osxlatitude.com/donate/ THANKS FOR YOUR SUPPORT I would like to thank following people for beta testing the driver and providing valuable feedback: Leon, Ramalxlama, Shin zon, Sherlocks, Dragon, Ðнтошка, Thomas benhamou,68x, Eli and many others. SOURCE: Project source code: https://github.com/E...Touchpad-Driver I am still doing some major work with beta testers to improve the features and stability, so I cannot update my git until its done, because it may allow others to modify and distribute their own version which can miss my changes and also worried about something else too which I do not want to mention here. I want to support this project for very long time and did spend hundreds of hours so far with testers (without hardware) and implemented many of the features myself from the scratch. So, I deserve and have rights to not to update my project source until I feel confident. The base of the Apple PS2 open sources I have used for my project are pretty much same which you find in the source from my above git link and rest of the changes from that are based on documentation and my own ideas. CREDITS: ELAN - Arjan Opmeer for ELAN linux documentation/source FocalTech - mgottschlag (github) for linux source Synaptics - Synaptics official documentation and linux source I would like to thank the VoodooPS2 team (Slice, King, rehabman and many others who contributed to the VoodooPS2) for ideas, Apple for their PS2 open sources which i've used as base for my driver and linux sources for the touchpad initialization and packet info. SmoothMouse 1.0.5.zip mouseaccelerationpref11d.zip Apple Keyboard Layout ID.rtf ElanTouchpad_v2.8.3.zip ELAN_v3.8.5_Final_Upd.zip ELAN_v4.0.5.zip SmartTouchPad_v4.2_Final.zip SmartTouchPad_v4.3_Final.zip SmartTouchPad_v4.4_Final_64bit.zip SmartTouchPad_v4.4_Final_32_64bit.zip SmartTouchpad_v4.4.5_32_64bit.zip SmartTouchpad_v4.4.5_64bit.zip SmartTouchPad_v4.5_Final_64bit.zip SmartTouchPad_v4.6.zip SmartTouchPad_v4.6.5.zip SmartTouchPad_v4.7 beta 3.zip SmartTouchpad v4.7 beta 5.zip
    4 points
  18. Dell Latitude E5550: Intel Broadwell i3-5010U @2.10GHz Intel HD5500 graphics 8GB DDR3L RAM Intel I218V LAN Intel AC 7265 Wireless OpenCore 0.7.3 and Clover r5138 with up-to-date kexts at time of writing. Updated: Dell Latitude E5550.zip Working: Full graphics acceleration HDMI output Wifi and Bluetooth LAN Audio (speakers, headphones & HDMI) Sleep with lid off and  > Sleep Brightness control Multimedia button Keyboard and touchpad (ALPS) SD card reader USB2.0 & USB3.0 ports (USB remapping required macOS installation because my laptop doesn't have camera so I've not remapped yet) Battery Indicator and charger Not working: VGA output (unsupported)
    4 points
  19. Lenovo T14 Gen1 (Type 20S0/20S1) - OpenCore !Warning! Warning! Warning! Follow guide at your own risk, neither I nor OSXL will take responsibility if the process bricks your system. Specification: Bios: 1.32 CPU: Intel Core i5-10310u (Comet Lake) @ 1.70GHz Memory: 1x 8GB DDR4 2666Mhz (Soldered + 1 open slot) Harddrive: 1x 256 PCIeNVMeOPAL (PM981) //Needs to be replaced Display: 14" non-touch 1920x1080 IPS, anti-glare GPU: Intel UHD 620 Camera: 1x IR Camera & RGB 720p HD Camera & Mic with Thinkpad Privacy Shutter WLAN: Intel Wi-Fi 6 AX201 802.11ax 2x2 with BT5.2 (Soldered on) Battery: Integrate Li-Polymer 50Wh internal battery - Up to 16.5 hours* Touchpad: Synaptics Audio: Realtek HDA ALC257 (aka ALC3287) 2 x USB 3.2 Gen 1** (one Always On) 1 x USB 3.2 Gen 1 Type-C (Power Delivery, DisplayPort, Data transfer) 1 x USB 3.2 Gen 2 Type-C / Intel Thunderbolt 3 (Power Delivery, DisplayPort, Data transfer) MicroSD card reader (Realtek RTL522a) Headphone / mic combo Micro-SIM slot HDMI 1.4b RJ45 Gigabit Ethernet I219-LM BIOS Settings: Working: Keyboard (including all Fn keys) Trackpad with gestures / Trackstick Battery indicator Display auto brightness Audio (Internal and headphone jack) Microphone Ethernet GPU acceleration Camera Intel Wireless / Bluetooth (soldered in so can't be replaced) Sleep / Wake Native CPU power management MicroSD card reader HDMI video and audio USB-C to HDMI Video and audio works USB-C to USB-C Video but no audio Note: For dual external display to work, you need to connect to HDMI display 1st before USB-C to USB-C Not Tested: Thunderbolt Installation: Download MacOS Monterey / Big Sur / Catalina app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Install ThinkpadAssistant.app (attached), set it to Launch at Login Note bootpack include AirportItlwm for Intel wifi but won't work with hidden networks Use Itlwm.kext + Heliport.app instead if you connect to hidden network Thinkpad Assistant Features: Resources: https://dortania.github.io/OpenCore-Install-Guide/ https://github.com/yusifsalam/t490-macos https://github.com/MSzturc/ThinkpadAssistant https://github.com/VoodooSMBus/VoodooRMI https://github.com/OpenIntelWireless/itlwm https://github.com/cholonam/Sinetek-rtsx https://github.com/0xFireWolf/RealtekCardReader/releases Updated to OC 0.9.4 - To support Ventura / Monterey / Big Sur T14_OC_0.9.4.zip T14_OC_0.8.5.zip T14_OC_0.7.9.zip T14_OC_0.6.9.zip ThinkpadAsssistant
    4 points
  20. Specifications: BIOS Version: 1.16 (Latest) (needs SATA in AHCI mode, not Intel Optane or disk won't be seen) Intel 8th gen i5 8265U, 1.6GHz CPU Integrated Intel UHD620 15" 1366x768 HD non-touch LCD 16 DDR4-2400 RAM (Up to 32GB) M.2 2280 PCIe Gen3x4 256GB RTL8111 Gigabit Ethernet Realtek ALC255 WiFi Card - Originally came with a Qualcomm Atheros QCA9377A-5, but this model it's not supported by macOS, so it was replaced by a DW1820A - CN-0VW3T3 card (Key A/E, size 2230) 802.11ac combo wireless card + Bluetooth 4.1. Integrated HD User Facing Chicony Electronics, webcam (USB internal) Integrated Realtek Card Reader RTL8411B (PCI ven id 0x10ec, dev id 0x5287) 1 x 3.5mm universal jack (combo audio) 1 x USB 3.1 gen1 port Type-A (with PowerShare) 1x USB Type C port 3.1 2x USB 2.0 ports 1 x HDMI port Working: All the components!! UPDATE: Bluetooth working now using masking 5 pins of the card, I did exactly what this user did: Post with photo - By @Naidis Methods used: To install macOS: Hackintosh Guide - Install MacOS with Olarila Image, Step by Step, Install and Post Install, Windows or Mac To activate my WiFi: Broadcom BCM4350 cards under High Sierra/Mojave/Catalina Full DSDT patches: DSDT patch requests Screenshots: Credits: @Hervé he gave me the WiFi card (T77H649) and helped me to active it. @MaLd0n he as always helpd me with the DSDT and keep my Hack stable as a real Mac! And I'm thank all the community to get this machice working, the Clover guys, @headkaze with his awesome Hackintool app also. Your hard work guys, will be always appreciate by me. My EFIs folders with Full DSDT patched OpenCore 0.7.1 OC 0.7.1.zip Clover 5136 Clover - 5136.zip
    4 points
  21. Hi, In the light of celebrating the 10th year anniversary of OSXL - I decided to dig through the waybackmachine. Check it out! Back in 2011 when we launched our first official page, it was with a clear vision of creating a new forum, free of ads, fast and reliable - To some, OSXL was just a nerdy bunch who put together something called EDP that for the most part.. worked.. but as EDP grew so did OSXL. In 2012 iMick took charge of the design and pushed OSXL to a brand new direction - shiny and nice - wordpress was still on the front but the backend is now IPboard (and have been ever since) The year is 2013 and a new design saw the light of day - it was a a nice refresh and brought a more "flat design" - between us, i never liked the "flatness" of things - keep that in mind when you think about the 2020 design - "Return of the angry dane" 2014 brought more updates to the site - among other, the compat. chart for EDP which actually used the database build into EDP - behind the scenes it was some cool shit there. The 2014 design lived with us for a long time with only minor changes along the way... but 2017/2018 brought a new design - sticking to the "flatness". ... and here we are in 2020 - a new fresh design - still running IPboard - still the same vision, a free place on the internet for macOS nerds to hangout, meet and hack the hell out of their machines. I would like to take a minute to say thank you to all of the users of OSXL who have made this journey worth it - but also to the outstanding crew of OSXL - you guys are amazing! Ps. Back in 2010 when OSXL was founded - one of the first machines that was hacked up was a "Dell Latitude D430" - here is the very first screenshot I ever uploaded from that machine.
    4 points
  22. Hello all! Here my configuration. Maybe someone will need it. Dell Latitude e7440 (no Fingerprint version) CPU: Haswell Intel Core i7-4600u dual core 4th gen IGPU: Intel Graphics HD 4400 Ram: 16GB DDR3 SSD M-SATA: 256GB Bios: A28 Mac Os: Catalina 10.15.4 Working: full graphics acceleration on Intel HD4400 iGPU, including brightness control (Fn+F3 Brightness up Fn+↓ Brightness up) (with Lilu v1.4.2 + Whatevergreen v1.3.7) multi-display with HDMI audio, including HDMI, (no microphone input) and headset output (with AppleALC v1.4.7 & No Inject audio) GigEthernet LAN connection (with IntelMausiEthernet 2.5.0 kext) wireless and bluetooth with any compatible card (a BCM94352HMB with Airportbrcmfixup.kext v2.0.6, BrcmBluetoothInjector.kext 2.5.1, BrcmFirmwareData.kext 2.2.10, BrcmFirmwareRepo.kext 2.5.1, BrcmPatchRAM3.kext 2.5.1, FakePCIID_Broadcom_WiFi.kext 1.3.15, FakePCIID.kext 1.3.15) All USB ports (3.0) integrated webcam sleep & wake battery management (with ACPIBatteryManager v1.90.1) keyboard and touchpad, max 2 finger multitouch(with VoodooPS2ControllerR6 v6.0.0) SD Card reader Not working: Nothing For Bios settings follow this perfect guide by Hervè (set like this all option that you can find) For create bootable usb/Installation/Post Installation follow this perfect guide by Hervè (just download latest Catalina 10.15.4 from Apple Store) Is better to use the latest clover release, for download it click here You can also follow these steps, starting from the installation of the clover in the usb stick (after the media creation tool process in terminal is done) : Run Clover r51xx.pkg and select USB (Install Mac Os Catalina) as destination Just flag in true on Clover for UEFI booting only, Install Clover in the ESP, UEFI Drivers - Racommended drivers - Install Open terminal and paste: diskutil list Choose your usb EFI partition and type (for example disk1s2): sudo diskutil mount disk1s2 Open Finder and open mounted EFI Replace the EFI folder with this: EFI 10.15.4 e7440 V2.zip Boot from USB and install Mac OS For post-installation repeat the same steps with these differences: Run Clover r51xx.pkg and select your SSD/HHD as destination Just flag in true on Clover for UEFI booting only, Install Clover in the ESP, UEFI Drivers - Recommended drivers - Install Remove all usb sticks and others disk (leave only the target Mac Os disk) and just type : sudo diskutil mount EFI Open Finder and open mounted EFI Replace the EFI folder with the USB EFI Change your serial number in clover configurator SMBIOS section Enjoy your hack! Clover Configurator.app.zip
    4 points
  23. I was contacted by member @plastikman about a potential universal fix for the troublesome DW1820a cards. Hugotai posted again at Voldemort's place early december 2019 about a property injection that apparently fixed the stability issues encountered with so many DW1820a on so many laptops. Said property is pci-aspm-default and the value to inject is 0. Hugotai explained that he derived the solution from this guide he found on the Net and in which the author explained that, in order to use the DW1820A card, he had disabled PCIe ASPM power in BIOS. A quick search on the Net revealed to me that ASPM means Active-State Power Management and relates to PCIe devices. Basically it's a protocol that offers dynamic power management through different possible states ranging from idle to powersave or performance. I also understand there is a default state which usually means power is controlled by BIOS, not the OS/kernel. This is totally unknown territory until I read more about it but setting ASPM default state to 0 probably means ASPM is disabled. On reading a little further, I came across writings that mentioned potential conflicts between idle timers or that ASPM compliance varied according to device. So, the troubles experienced by so many people may indeed come from that. Anyway, I tried the property injection with the other 2 x DW1820a/BCM4350 cards I still possess and that did not properly work in my Latitude 7490: the 096JNT model (subsystem 1028:0021) and the T77H649 (subsystem 17aa:075a). Results were as follows: 096JNT: Without injection of ASPM property CPU load up to the roof after a few minutes, system freeze as expected and experienced before. IOReg reveals pci-aspm-default parameter natively set to 0x102 under the wireless card's ACPI device. With injection of ASPM defaut set to 0 All Ok, was able to use the laptop without any issue, performance degradation of wifi problems for well over 1hr. IOReg confirms pci-aspm-default parameter set to 0 under the wireless card's ACPI device. T77H649: Without injection of ASPM property CPU load up to the roof after a few minutes, system freeze as expected and experienced before. IOReg reveals pci-aspm-default parameter natively set to 0x102 under the wireless card's ACPI device. With injection of ASPM defaut set to 0 All Ok, was able to use the laptop without any issue, performance degradation of wifi problems for well over 1hr. IOReg confirms pci-aspm-default parameter set to 0 under the wireless card's ACPI device. I remind everyone that all I use, in order to declare compatibility with Broadcom chips 14e4:4331 or 14e4:4353, is the Clover property injection detailed in post #2; no AirportBrcmFixup plugin kext, no bcrmfx-driver boot argument and no pin masking. So, it would seem we now have a definitive solution for DW1820A/BCM4350-based cards. I've updated the above posts to reflect on the good news. All credits to the author of this guide that caught the attention of Hugotai who derived the property to inject as a fix.
    4 points
  24. Catalina Catalina Guide Bootpack Replace into /EFI/Clover after you install Clover E7470_Catalina.zip E7270_Catalina.zip - For Discrete Model Also add this to /EFI/Clover/ACPI/Patched SSDT-Disable-DGPU.aml FYI, kexts in bootpack might be outdated Make sure to 1st upgrade kexts found under /EFI/CLOVER/kexts/Other if you encounter issue Common links for new kexts: https://github.com/vit9696/Lilu/releases https://github.com/vit9696/Lilu/blob/master/KnownPlugins.md https://bitbucket.org/RehabMan/ Note: 1) Post Install: Copy kexts in /EFI/Clover/kexts/Other/CopyToLE to /Library/Extensions. Repair permissions and rebuild cache 2) Enable this patch in Config.plist under KextsToPatch if you have: LiteOn, Plextor, or Hynix NVMe Hynix NVMe patch 10.13.x (Bit swap block size 0x10) -Syscl Finally we have support for SD Card reader (Realtek RTS525a). See here for more info and link to kext UPDATES
    4 points
  25. Dell Latitude/Inspiron/Precision/Vostro/XPS - Clover Guide Up to Sierra Only High Sierra Guide below Mojave Guide Catalina Guide Warning: Follow guide at your own risk, I hold no responsibility if you brick your system or destroy all data during the process. If you're creating the installer from a real Mac, make sure you don't accidentally select the real Mac drive when installing Clover loader. It may cause your Mac to not boot again. You've been warned! BIOS: Set to Default, apply, then set SATA Operations to AHCI, set Boot List Option to UEFI Disable Secure Boot, Disable Wake on LAN/WWAN/WLAN, Disable TPM (optional) Enable Legacy Options ROMs for Broadwell system and below Requirements: 1. A downloaded OS X El Capitan / Sierra Application from the Mac App Store 2. USB flash drive (16GB minimum) 3. Clover Configurator (Included in Hack_Tools attached below - might not be the latest) 4. Clover Loader 5. ShowHiddenFiles.app (Included in Hack_Tools attached below) 6. A system running OS X to create the USB Installer 7. A supported Wireless card, Intel wireless are NOT supported Overview 1. Prepare a Bootable USB Drive (8GB minimum) 2. Install OS X El Capitan / Sierra 3. Post Installation 1: Prepare Bootable USB Drive This step extracts the OS X Installer contents, then installs Clover bootloader to the USB stick. 1. Insert the USB drive on a running OS X system 2. Open /Applications/Utilities/Disk Utility 3. Highlight the USB drive in left column 4. Click on the Partition tab 5. Click Current and choose 1 Partition 6. Click Options... 7. Choose GUID Partition Table 8. Under Name: type USB (You can rename it later) 9. Under Format: choose Mac OS Extended (Journaled) 10. Click Apply then Partition 11. Go to Applications, right click on Install OS X El Capitan / Sierra =>Show Package Contents=>Contents=> SharedSupport 12. Mount InstallESD.dmg 13. Launch ShowHiddenFiles and select Show Special Files ( app attached at the end of guide) 14. Mount BaseSystem.dmg (hidden) from OS X Install ESD 15. Use Disk Utility to restore OS X Base System to USB (see image below) 16. After restore is complete, USB is now renamed to OS X Base System. Go ahead and rename it to Install OS X El Capitan 17. Go to Install OS X El Capitan/ Sierra=>System=>Installation and delete the alias Packages 18. Copy Packages from root of OS X Install ESD to Install OS X El Capitan/Sierra=>System=>Installation 19. Copy BaseSystem.dmg and BaseSystem.chunklist (hidden files) from OS X Install ESD to root of Install OS X El Capitan/Sierra 20. Launch ShowHiddenFiles and select Hide Special Files 21. Download Clover 22. Launch Clover package installer 23. Hit Continue, Continue, Change Install Location... 25. Choose Install OS X El Capitan/Sierra 26. Hit Continue, then hit Customize. Select these items: Install for UEFI booting only Install Clover in the ESP UEFI Drivers\Recommended Drivers ApfsDriverLoader AptioMemoryFix AudioDxe DataHubDxe FSInject HFSPlus SMCHelper (leave off if you have VirtualSMC.kext in bootpack) Additional drivers PartitionDxe Themes (Optional) Note: For non UEFI BIOS, see Note1 of post #2 27. Click Install 28. After installation of Clover, the hidden EFI Partition will appear on the Desktop 29. Download the Generic EFI + Bootpack for your model in post #2, replace the contents to the root of the EFI partition, replacing the existing folders ( Boot and Clover folders - not merge) Note: Make sure to check the Update section in Post #4 for updated file if any 30. You are now ready to install OS X El Capitan/Sierra Note: Make a directory in the USB Installer and copy Hack_Tools, Clover package and EFI folder to it for easy access in Step 3 2: Install OS X El Capitan/Sierra 1. Turn on the computer with the USB Installer connected 2. Press F2 to configure the BIOS Sata Operaton -> AHCI Secure Boot -> Disabled Boot List Option -> UEFI. Enable Legacy Option ROMs (Disabled for Skylake and above) Apply and Exit 3. Hit F12 during boot, choose under UEFI Boot: 4. When Clover boot screen appears, choose Install OS X El Capitan/Sierra 5. The system will then boot into the OS X Installer 6. Choose your language and hit -> to continue 7. For a new installation of OS X, you MUST erase and format the destination drive according to the following steps before continuing. *If you are upgrading from Lion, Mountain Lion, Mavericks, or Yosemite and you want to keep your files and apps, skip steps a-i. a. From the menu bar, click Utilities -> Choose Disk Utility b. Highlight your target hard drive for the El Capitan installation in left column. c. Click Erase tab d. Under Scheme: GUID Partition Map e. Under Name: type Macintosh SSD (You can rename it later) f. Under Format: choose Mac OS Extended (Journaled) g. Click Erase h. Click on Partition Tab to add more partition if you prefer i. Close Disk Utility 8. Click Continue, Continue, Agree 9. Select Macintosh SSD, or name of your existing drive, where you want to install El Capitan and click Continue 10. Upon completion, system will restart 11. Press the F12 to choose boot device 12. Choose under UEFI Boot: 13. When Clover boot screen appears, choose Macintosh SSD or name of your existing drive The system will boot into the new drive, and complete the installation: 14. Launch the terminal and enter the following command diskutil list Note: If you see the following, then follow steps in Post #3 Under Core Storage before proceeding /dev/disk1 (internal, virtual): 3: Post-Installation Install Clover loader to Macintosh SSD 1. Launch Clover package installer 2. Hit Continue, Continue, Change Install Location... 3. Choose Macintosh SSD 4. Hit Continue, then hit Customize. Select these items: Install for UEFI booting only Install Clover in the ESP UEFI Drivers\Recommended Drivers ApfsDriverLoader AptioMemoryFix AudioDxe DataHubDxe FSInject HFSPlus SMCHelper (leave off if you have VirtualSMC.kext in bootpack) Additional drivers PartitionDxe Themes (Optional) Install Clover Preference Pane (Optional) Note: For non UEFI BIOS, see Note1 of post #2 5. Launch ESP Mounter Pro, select the disk you have OS X installed on (ie. disk0s1) - app in Hack_Tools 6. Copy the EFI folder from the USB installer to EFI partition of Macintosh SSD (replace not merge) 7. Copy kexts from /EFI/Clover/Kexts/Other/CopytoLE to /Library/Extensions of Macintosh SSD Note: Ignore warning/error messages and click OK, then run commands below. 8. Repair permission and rebuild cache. Run command from terminal (or run permission.sh found in Hack_Tools) sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / 9. Go to System Preferences Enable Clicking for Trackpad Allow apps downloaded from: Anywhere for Security & Privacy (optional) Note: For Sierra and up, run this in terminal instead: sudo spctl --master-disable 10. Generate own SMBios and SSDT.aml (For Haswell and up, you can enable PluginType in Config instead) Launch /EFI/Clover/Config.plist with Clover Configurator (Included in Hack_Tools attached below) On the left, click on SMBIOS Click on the Up/Down arrow on the right Select the model most suited for your system or use same model included in bootpack, generate a new serial Close Clover Config and save the file. Execute ssdtPRGen.sh from terminal (Included in Hack_Tools attached below) Place generated SSDT.aml in /EFI/Clover/ACPI/Patched Please use beta version of ssdPRGen.sh to generate SSDT.aml for newer system 11. Make sure to disable hibernation as it's a prerequisite to get sleep & wake to work properly on a Hackintosh: sudo pmset hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo pmset hibernatefile /dev/null 12. Congratulations! You are done! Hack_Tools.zip When posting for HELP, please include full system specs and attach debug files. If you're not able to start the installer, then attach the Clover folder and include screenshot(s) of the error / KP by booting with verbose + debug 0x100 mode Credits: All apps, kexts and DSDT patches used in creating this guide go to the developers that created them. I take no credit other than putting this guide and bootpacks together.
    4 points
  26. Hello everyone Thank you very much for your wonderful and useful forum I want share with you after long search and fixes my final EFI Partition for Dell Precision WS M6800 & M4800 and will work 99 % on any similar Model All files , Kexts , ACPI , Guide are all included in zip file linked below This my final EFI with alots of fixes and tweaks works for both High Sierra and Mojave only you will need Nvidia web drivers and Cuda to get fully working machine for graphic designing , video editing and 3D ... - Fully working everything , audio , Bluetooth, Brightness slider , card reader , mSata , ethernet , Wifi , Camera ,all USB 3 Ports and many more you will explore it yourself ...... - Bios Reset issue fixed - Optimus Graphic enabled - Use Intel HD only or Intel HD + Nvidia (if you want Nvidia only then disable Optimus in bios) - External Monitor use Nvidia - No black Screen when external monitor is connected - What is missing and doesn't work !!!! You will tell me - all fixes files and instructions are included ************************* UPDATED 30 JUN 2019 ************************ - Alots of Tweaks has been added to ACPI , config.plist and IntelFrameBuffer - USB 3 all ports fixed natively - KEXTS has been updated -Clover bootloader has been updated - Fans has been adapted by ACPIPoller.kexts and SSDT for more cooling and less noise - CPU and RAM Tweaks - No more Kernel Panic with release or security update - Clean DSDT , SSDT , plist - Alots of work, search and tests to get this result with this Laptop - Ready for Catalina ( wait for the official release and Hacks developers final fixes to be ready ) All Updated Files are here ( 50 MB) ; https://drive.google.com/file/d/107_34arPRYoiObJUCH9l7TG_tZsK2FOD/view Thank You ********************* 30 Nov 2018 Fix OLD .zip If you need any help or have any questions or issue please let me know in the Support section of the forum and I will reply as soon as possible Cheers
    4 points
  27. 30-06-2019 Update Attached Files in First Post ( Google Drive Link 50 MB ) This instructions is for Dell Precision m6800 (and similar Dell Precision Models - Experimental) Before you start Please note that : I am using Dell Precision m6800 with these SPEC : Intel I7 4900MQ 2.8 Mhz - Intel HD Haswell 4600 32 GB RAM Nvidia Quadro K3100M 4GB Samsung EVO 250 GB Dell DW 1560 WiFi and BT Adapter BIOS A25 ( Latest 30 Oct 2018 ) This Process has been successfully tested with High Sierra and Mojave 10.14.5 Both IGPU and DGPU are Working Together Correctly like a Desktop No Bios reset issue when reboot , Works with Dual Boot ( Win + OSX ) ******* Step By Step ******** 1- Reset BIOS to its default and Update it to A25 2- Modify BIOS setting ( Press F12 to see Options ) * Advanced Boot Options = Enable Legacy * Integrated NIC = Enable * Parallel Ports = AT * Serial Ports = Disabled ( If you are using Dock station then Enable it - Expermental ) * Sata Operation = AHCI * Drivers = Check all * Switchable Graphics = Enable Switchable Graphics * Secure Boot = Disabled * Virtualization = Disable 3- Create your OSX Installation USB ( Search How , its not my Topic ) * Then I recommend to install Clover bootloader to create EFI Folder on your USB (UEFI Method) 4- Once you create OSX Installation USB ; mount USB EFI PARTITION and DELETE EFI Folder 5- Decompress my attached files 6- On my attched files ; Find ( install Folder ) Copy EFI Folder and Paste it in your USB EFI PARTITION ( instead of deleted one in step 4) 7- Now you are ready to Install OSX for Dell Precision M6800 * Power On your PC * Press F12 to see Options * Select BOOT from ( your USB ) * Start Installation Process ( it will reboot several time during installation so press F12 each time to boot from your USB ) - search Youtube videos to see the installation process 8- Once installation done and you reach your OSX desktop *Copy my attached files to your Desktop and Eject USB * Mount your OSX Drive EFI PARTITION and delete ( EFI Folder if existed ) * On my attached files Find ( Boot Disk EFI ); copy EFI Folder and Paste it in your Drive EFI PARTITION instead of deleted one "same as step 6" 9- Now the last step ( very Important ) - on my attached files Find (L/E Folder) - use any method or tool to install ALL KEXTS to Library/Extensions - Rebuild kextcache and repair permissions - I recommend using Hackintool by @headkaze to install kexts and rebuild kextcache 10- Reboot your PC and check everything is working correctly ( Audio , Bluetooth , WiFi , Internet , USB 3 , Trim ... ) IF you are using Mojave ; No Cuda drivers available till now but Nvidia GPU works with 4k External Monitor via DP Fully Accelerated Qi-Ci , also you can Disable Bios graphics Optimus to disable Intel HD GPU and use only Nvidia GPU - The same thing with High Sierra except that Nvidia Web Drivers are available and Cuda are ready - I use this PC all time with 4k external monitor while laptop led screen is closen using external mouse and Keyboard for Graphic design and video editing; H264 with hardware acceleration is working but no H265 hardware acceleration I think due to Haswell limitation - also I've found useful app to disable CPU turbo boost . I use it sometimes to reduce CPU temp ( search google ) Note : in case you have booting troubles ; Try to change SMBIOS in config.plist to diffrent model as MacbookPro 10.1, MacBookPro 11.2, MacBookPro 13.1 also you can try iMac 14.2 ( works nicely with me I don't know why ) Little Tweak for CPU and RAM : go to CPU section in config.plist using clover configurator and add values to this sections according to your CPU frequency (Be careful) For example: - Add 2800 to "frequency mhz" if your CPU base is 2.8 mhz ( 2700 if 2.7 and 2100 if 2.1 , ...) - Add 99790 to "Bus speed khz" - Add 47 to "TDP" ( Look intel CPU spec page for your model to know more info about your CPU and TDP value for your CPU ) For example in my case https://ark.intel.com/content/www/us/en/ark/products/75131/intel-core-i7-4900mq-processor-8m-cache-up-to-3-80-ghz.html GPU Power Management: Delete my dAGPM.kext from clover/Kexts/Others and make your own Kext according to your SMBios ID to get the correct power management There is a tool developed by @pavo to generate your Kext and another method by @toleda search forum and google to know more about that Disable Nvidia GPU: If you want to disable dGPU and use only Intel HD 4600 drop SSDT-4600.aml to clover/ACPI/Patched . But in this case no external monitor will be working only internal Disable Intel HD GPU : If you like to use only Nvidia GPU so disable Optimus Graphics in Bios and you can use internal and external monitor USB 3 Ports Fixes : Please Modify The Info.Plist inside USBPorts.Kext to Match Your SMBIOS Find and change this text (iMac 14.2) change to (Your Model) every where in plist For Example (iMac 14.2) To (MacBookPro 11.2) Now All Your USB 3 Ports And Camera Will Work Correctly Have Fun Franckenstien 30 Jun 2019 SSDT-4600.aml.zip
    4 points
  28. Last update: 28th Jan 2020 Dell DW1820A: Ok Ok Ok DW1820A is a pretty good combo card providing 2.4/5GHz 802.11ac wireless at 867Mbps + Bluetooth 4.1. As stated at Wikidevi, there appears to be a few different models of the card. Whilst they all carry the same Broadcom id 14e4:43a3, they each carry a different subsystem id/part #: 1028:0021 (part # CN-0VW3T3) -> 100% Ok with ASPM disabled (originally tested 100% Ok on my Latitude 7490 without ASPM tuning) 1028:0021 (part # CN-096JNT) -> 100% Ok with APSM disabled 1028:0022 (part # CN-096JNT) -> 100% Ok with APSM disabled 1028:0023 (part # CN-0VW3T3) -> 100% Ok with APSM disabled 1028:0023 (part # CN-08PKF4) -> 100% Ok with APSM disabled I acquired a Dell DW1820A a few months ago and was able to play with that card on a Latitude 7490 laptop (fitted with an M.2 2230 Key A+E WLAN slot) that I targeted for Mojave. The model I received was CN-0VW3T3. Before it was later established that not all DW1820A were equal, I purchased a 2nd one and, as it turned out to be, was lucky to receive another 0VW3T3 model. /!\ The 1st thing I want to report is that I encountered difficulties booting my Mojave USB installer and installing macOS with the card plugged in. I had to disable wireless in BIOS to be able to install Mojave. Once it was installed, booting Mojave with wireless enabled in BIOS would cause quite severe lag and performance degradation once at the desktop, as if the card just clogged up CPU ressources. This was because I had not applied any particular tuning for the card and, of course, this was resolved once I implemented the necessary fix detailed below. /!\ Searching through the Web for that DW1820A/BCM4350, I came accross a few forum posts/threads that mentionned: rolling back the Yosemite IO80211Family kext to get the card to work, although with instability and regular KPs removing AirPortBrcmNIC plugin kext from IO80211Family kext, patching AirPortBrcm4360 plugin kext with the id of the DW1820A and installing AirportBrcmFixup kext with a couple of parameters (Credits to Hugotai, cf. his post @Voldemort's place, 2nd Dec 2018) Whilst I did not really contemplate doing the 1st thing, I did envisage the 2nd one and started to look at the differences between Yosemite's version of IO80211Family kext and Mojave's. The main difference I had already noticed was that device id 14e4:43a3 was handled by AirPortBrcm4360 up to Sierra 10.12 and by AirPortBrcmNIC since High Sierra 10.13. Further reading and experimenting showed me that AirPortBrcmNIC kext was the root cause of the problem. Building on Hugotai's success, I seeked to work out an easier solution to bypassing AirPortBrcmNIC kext that would not require kext removal and Info.plist patching but, instead, something that could be implemented through hardware properties injection, either through DSDT/SSDT patching or bootloader (Clover or OpenCore) configuration. Once Hugotai's solution was verified and confirmed, I worked out the following Clover-based solution (because that's what I was using) for HighSierra/Mojave: identify the IOReg/ACPI device to which the DW1820A card is attached (use IORegistryExplorer app to that effect). Eg: RP0n@xx,yy->PXSX@0. in the absence of individual ACPI device entry under the PCI bridge for the card, select "FixAirport" ACPI Fix in Clover. That'll create a device "ARPT" @0 under the bridge and that's what you'll inject properties to. This may also require to select "AddDTGP" ACPI Clover fix if your DSDT does not possess any DTGP method. If running with Clover, use Clover Configurator app to that effect. inject the following properties either in DSDT or through bootloader config (latter recommended): compatibility of the card with Broadcom chips 14e4:4353 or 14e4:4331 that are handled by IO80211Family's PlugIn kext AirPortBrcm4360 ASPM disabling (required for most cards to avoid CPU clogging and system freeze) optionally, add SysProfiler's cosmetic info such as PCIe Slot, card's make and model, etc. and that's it ! Nothing to do to IO80211Family kext or its PlugIns which all remain untouched/unmodified/full vanilla in /S/L/E. It really could not be simpler... NB: if your card's country code absolutely requires to be changed, say for full 5GHz/80MHz operations, add the following steps: install AirportBrcmFixup kext in /L/E + repair permissions + rebuild your cache or inject it through Clover's EFI/CLOVER/kexts/Other add boot argument brcmfx-country=XX (where XX is the target value, eg: US, FR, #a, etc.) to the Boot section of your Clover config but, beware, I found that using AirportBrcmFixup (v1.1.9 at time of writing) with country code other than default's US setting of the card impacted my wireless performance (fluctuating and reduced RX/TX rate). For instance, with country code set to FR (for France), I would not connect at 80MHz on my 5GHz Wireless network, only at 40MHz which resulted in a local wireless connection limited to 400Mbps (vs. 867Mbps) and reduced my overall Internet RX rate by about 60% and TX rate by about 10%: with country code set to #a (to get full 80MHz connection), I could not obtain DFS channel mode to my local router and I noticed fluctuating/unstable RX/TX rates: without AirportBrmfixup, my wireless connection runs solid at 867Mbps and SpeedTest returns a solid TX and RX rates at 300Mbps (i.e. the maximum speed of my Internet connection). Properties injection through DSDT: On my laptop, the DW1820A was found attached to device RP03.PXSX located at IO address 0x001C0002, i.e. 1C,2. The DSDT patch required to inject properties could look like this (devices names will differ from one computer to another of course!): Device (RP03) // PCIe Root Bridge { name (_ADR, 0x001C0002) [...] [...] [...] Device (PXSX) // DW1820A card attached to this device (FixAirport Clover ACPI fix required if such device is missing) { Name (_ADR, Zero) [...] [...] [...] Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "AAPL,slot-name", // Optional Buffer () { "WLAN" }, "device_type", // Optional Buffer () { "Airport Extreme" }, "name", // Optional Buffer () { "Airport" }, "model", // Optional Buffer () { "Dell DW1820A 802.11ac wireless" }, "compatible", // Mandatory Buffer () { "pci14e4,4353" // Declares compatibility with BCM43224; "pci14e4:4331" for BCM94331 may also be used }, "pci-aspm-default", // Mandatory for most cards Buffer (One) { 0x00 // Disables ASPM for PCIe device } }) } } } Properties injection through bootloader config: An easier alternative is to inject those properties in bootloader config (for Clover via Clover Configurator app for instance). This can be done within the Devices properties section by injecting the desired properties in the Properties sub-section: In the left part, add the PCIe address of the targeted device in the form PciRoot(0x0)/Pci(<root device address>)/Pci(<actual device address>) In the right part, add the above properties in single lines and with the right types (String, Data, Number) For instance, in the case of my laptop booting with Clover, the target device will be PciRoot (0x0)/Pci(0x1C,0x02)/Pci(0x0,0x0) for PCI0@0->RP03@1C,2->PXSX@0. Then, properties will be injected as lines of keys of 3 x possible types: strings, hex data blocks or numbers. For instance, to declare compatibility with 14e4:4353, the line will consist of Property Key set to compatible, Key Value set to pci14e4,4353 and Key Type set to STRING. The complete properties injection will be: Device = PciRoot(0x0)/Pci(0x1c,0x02)/Pci(0x0,0x0) Key = compatible | Value = pci14e4,4353 | Type = STRING Key = pci-aspm-default | Value = 0 | Type = NUMBER Key = AAPL,slot-name | Value = WLAN | Type = STRING (optional) Key = device_type | Value = Airport Extreme | Type = STRING (optional) Key = name | Value = Airport | Type = STRING (optional) Key = model | Value = Dell DW1820 (BCM4350) 802.11ac wireless | Type = STRING (optional) Once the device properties are injected in bootloader config or DSDT, there's nothing left to do but reboot the computer. The DW1820A card will then be fully active and able to connect to 2.4/5GHz networks at full speed. Results: On the Bluetooth side, once the usual Broadcom firmware patching kexts are installed (eg: Rehabman's BrcmFirmwareRepo + BrcmPatchRAM2 for instance), the BT4.1 module will be fully operational and capable of supporting AirDrop and Handoff! Links: Clover Configurator app Rehabman's Broadcom Firmware patching kexts Acidanthera AirportBrcmFixup kext - - - - - - - - - - Edit: 06 Jan 2020 Updated with freshly found ASPM disabling property injection that fixes all outstanding stability issues. DW1820A #096JNT and Foxconn T77H649 now tested 100% Ok. DW1820A #08PKF4 should be just the same. - - - - - - - - - - Edit: 28 Jan 2020 Finally got to test a DW1820A #08PKF4 and it's also 100% Ok with ASPM disabled.
    4 points
  29. Last update: 6th Jan 2020 Questions around this Broadcom BCM4350 chipset (in particular the Dell DW1820A) have resurfaced again so I digged into the matter since most people reported it did not work. Outside the model fitted to Apple MacBooks (subsystem id 106b:0131, rev. 05), Wikidevi lists a few cards cards for this chipset, including: Dell DW1820A (several models with different part numbers) Foxconn T77H649.00 (Lenovo part number 00JT494) Lite-on WCBN808B (Lenovo part number 00JT493) All those cards carry PCI id 14e4:43a3 and normally offer high speed 802.11ac wireless + Bluetooth 4.1 services. Broadcom BCM4350 chipset is supported since Yosemite 10.10 and its hardware id is listed in the Info.plist file of IO80211Family's PlugIn kext AirPortBrcm4360 up to macOS Sierra 10.12, then AirPortBrcmNIC since macOS High Sierra 10.13: <key>Broadcom 802.11 PCI</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AirPort.BrcmNIC</string> <key>IOClass</key> <string>AirPort_BrcmNIC</string> <key>IOMatchCategory</key> <string>IODefaultMatchCategory</string> <key>IONameMatch</key> <array> <string>pci14e4,43ba</string> <string>pci14e4,43a3</string> <string>pci14e4,43a0</string> </array> <key>IOProbeScore</key> <integer>1241</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>TruePowerOff</key> <true/> </dict> - - - - - - - - - - Edit: 06 Jan 2020 Removed the warning about DW1820/BCM4350 cards following tests confirming that disabling ASPM does fix the stability issues previously encountered by most users.
    3 points
  30. Laptop Specs: Intel Core i5 7300U RAM: 16 GB 2133 MHz DDR4 Graphics: Intel HD Graphics 620 SSD: 1Tb (macOS) SMBIOS: MacbookPro 15,1 Working: Graphic acceleration Brightness control Keyboard brightness control Wifi and Bluetooth: Intel Bluetooth and intel AirportItlwm All USB-C and USB3 (type-A) ports Video over USB-C Audio, incl. integrated microphone Sleep Ethernet HDMI output Touchpad Integrated camera Card reader MacBook Pro 15,1.ioreg WARNING: Generate your own SMBIOS EFI zip part 1: EFI_Sonoma_7280 2.zip to extract add to de file format .001 (EFI_Sonoma_7280_2.zip.001) EFI zip part 2: EFI_Sonoma_7280 2.zip to extract add to the file format .002 (EFI_Sonoma_7280_2.zip.002) I couldn't upload the full EFI here because the file is too large but you can download it here: https://mega.nz/file/xlhjlTjb#zCu_C5_k1pR6zqOXnVERUHdJjqHSA_JxYpvTOke5yn4 Enjoy! EFI_Sonoma_7280_1.zip
    3 points
  31. 1. Download the appropriate version from the Releases and extract the zip file. Let’s assume that you downloaded “ALCPlugFix-Swift-RELEASE-1.5.zip” to download folder, and extracted the zip file in the same place (by double-clicking). You would have a new folder “ALCPlugFix-Swift-RELEASE-1.5” created. Right-Mouse-Click on the new folder icon -> Services -> New Terminal at Folder. A new terminal window would be opened at the current folder path: /Users/YOURNAME/Downloads/ALCPlugFix-Swift-RELEASE-1.5 (You can type “pwd” to verify it) 2. Copy the edited sample.plist file (in this case: ALC295-DELL7400.plist) to somewhere safe. I placed it in “Monterey HD\users\shared”, where Monterey HD is the name for my macOS drive. You may have a different name. 3. At the terminal (opened in step 1), type: ./install.sh Follow the instruction. When it asked for .plist file, drag “ALC295-DELL7400.plist” icon to the terminal, from the location you stored in step 2 above (in my case, it is from “Monterey HD\users\shared\”). You may encounter message like "ALCPlugFix is from unknown source” (1st time install) , just ignore it. After install is completed, go to folder: /usr/local/bin (this is where ALCPlugFix is installed). Right-Mouse-Click on ALCPlugFix icon -> Open, then Open again to allow it to run. This would give it the permission to run. Add "alcverbs=1 alcid=77" to the boot args. Reboot.
    3 points
  32. This appears to have the right method. I added "alcverbs=1" to boot args and used alcid=77, this brought me closer to make the audio fully working. Based on comment I learnt from another forum, issuing "alc-verb 0x19 0x707 0x20" successfully made the headphone port working. All I need to do is make ALCFPluFix doing the same automatically on Connect/Wake events (may be more), but I am not sure how to convert "0x19 0x707 0x20" to equivalent format for ALCPlugFIx. The author provided no details. May be someone here can help. Update (2/23): I got it working. All I needed to do was to modify the "param" value to "0x20", and set "On Connect" & "On Wake" to TRUE. The verb command "SET_PIN_WIDGET_CONTROL" is actually "0x707" in hex. I've attached my modified sample.plist bellow. Just follow the install instruction. During the install, it would complain that "ALCPlugFix" is from Unknown source, just ignore it. After install, I went to install directory (/usr/local/bin), and run it once manually, by granting the needed permission. ALC295-DELL7400.plist.zip
    3 points
  33. OPENCORE - High Sierra -> Monterey Specification: BIOS 1.21.3 Intel Core i7-6920HQ Quad Core 2.90GHz, 3.80GHz Turbo, 8MB 45W 4 DIMM slots: Up to 32GB DDR4 2667MHz SuperSpeed memory Nvidia Quadro M2000M with 4GB GDDR5 dedicated memory Intel® HD Graphics 530 15.6" FHD (1920x1080) Anti-Glare LED-backlit (45% color gamut) Support for two storage devices: one M.2 PCIe solid state drive and one M.2 PCIe/2.5” SATA drive: Dell Fast Response Free Fall Sensor standard Solid State Drive (SSD): 256GB, 512GB, 512GB SED, 1TB 2.5” SATA 6Gb/s M.2 PCIe NVMe Solid State Drive (M.2 SSD): 256GB, 512GB, 512GB SED, 1TB SSD Integrated Intel 82580 10/100/1000 Gigabit Ethernet Intel® 8260 Dual-Band 2x2 802.11 ac (Miracast) Bluetooth® 4.1 Dual integrated high quality speakers Optional integrated light sensitive HD video webcam 1 x SD Card Reader (SD, SDHC, SDXC, supporting up to 64GB) 1 x Thunderbolt® 3 (optional) 4 x USB3.0 with PowerShare 1 x mDP 1 x HDMI 1 x Headphone and microphone combo jack 1 x SmartCard Reader (optional) Chassis lock slot support Working: Full HD530 Graphics Acceleration Internal speaker / Headphone / Autoswitch (ALC293) Keyboard / Touchpad with VoodooPS2Controller (scrolling, left and right mouse button...etc) Wireless /Bluetooth - replaced Intel with DW1560 / DW1830 / DW1820A Brightness Slider with Fn+F11 / Fn+F12 HDMI / mDP / USB-C - Video / Audio 3 Displays (Internal + HDMI + mDP or USB-C to HDMI or mDP adapters) Internal USB ports HD Webcam USB-C to HDMI / mDP Display USB-C to USB-C Display Sleep / Wake with LID close / Open SD Card Reader Not Working: NVIDIA Quadro M2000M disabled via SSDT patching ThunderBolt (not tested) Installation: Download macOS Monterey / Big Sur / Catalina / Mojave / HS Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID To Enable track stick scrolling, install Smart Scroll.app NOTE: Rename config-IntelWifi to config.plist if you're using an Intel Wireless / BT combo (not tested) 7510_OC_0.8.5.zip 7510_OC_0.7.5.zip 7510_OC_0.6.7.zip
    3 points
  34. As stated and shown at Applelife & InsanelyMac, works with OpenCore + AvoidRuntimeDefrag=No. Not sure about the need to add -lilubetaall boot arg. Boot loop with Clover (r5142) for the moment on my E7270 Skylake laptop with same config as used for Big Sur and Monterey, only SMBIOS changed to MBP14,1. I confirm that support for Haswell, Broadwell and Skylake iGPU is dropped, the only graphics framebuffers available in /S/L/E being KBL, CFL and ICL ones. For AMD, all GPUs older than Polaris generation are dropped. AppleIntelCPUPowerManagement is dropped too, something we still required on good old C2D, C2Q, 1st gen Core, Sandy Bridge and Ivy Bridge platforms so that could add a few nails in their coffin.
    3 points
  35. Welcome to the new (also probably the last) release, and I am happy to announce that 1.0.6 has been released! This release includes many fixes and support for Force Touch (more on that later)... First I created a pull request for the acidanthera repo as my goal was to make the whole VoodooPS2 thing more unified. So if all goes well, it will be merged soon. Second, thanks to @Jake Lo's testing, V8 is now more stable and won't break after a few hours of use. Also, the trackpoint speed is now a third compared to 1.0.5. Third, I removed VoodooInput support for V1, V2, and V6 touchpads due to hardware limitations. However, they still work like a regular mouse. Fourth, notification centre on V7 touchpads has now been fixed! Also, Rushmore V3 now loads properly. Last but not least, Force Touch support. This is a bit complicated and can lead to confusion. The table in my README should give a good overview of which Force Touch modes are supported: https://github.com/SkyrilHD/VoodooPS2-ALPS#force-touch I want to thank you again for helping me debug to fix VoodooInput on other versions of ALPS touchpads! It was a fun ride
    3 points
  36. Hi after reading this Forum and others, I am happy with my Dell 7040 this is my EFI Folder for my Optiplex 7040 with Monterey 12.1 Beta 4, OC 0.7.6 i5 6500, IntelHD 530, 1 Monitor to DP and 1 on HDMI Optiplex_7040.zip
    3 points
  37. Give this a try, updated to OC 0.7.5 Updated kexts and replaced a few as well Just rename it as EFI and replace it Latitude 7490 - OC0.7.5.zip
    3 points
  38. OC 0.7.4 update. Fixed trackpoint and trackpad stop working after sleep. Fixed issues with CMOS (RTC) error after restart - Thanks to Baio77 EFI.zip
    3 points
  39. Hello Elan PS/2 touchpad users! SmartTouchpad kext was decent until Voodoo came with Magic Touchpad integration. Since then our friends with Synaptics PS/2 and I2C touchpads had much better support for their touchpads. Therefore, I have ported Elan support from Linux kernel into VoodooPS2 so that now Elan PS/2 touchpad can also emulate magic touchpad and it means it can support all native macOS gestures, including tools like BetterTouchTool! Why this is not included in VoodooPS2? Because the kext has to be tested first. It works well for me (asus laptop), but I would like to hear feedback from more users, from more devices. Both if it works and if it doesn't. Once it is confirmed the kext works well, it might be merged into VoodooPS2 main project. What should work? Actually, everything. Basic touch, two finger scroll, multitouch, three and more fingers gestures, apple touchpad settings panel - everything. How to install: Just like normal VoodooPS2 controller - just copy the kext to Clover/OC (and add appropriate entries to OC config in case you use OpenCore). If you already have VoodooPS2 controller - just replace the file with this release. Download: https://github.com/BAndysc/VoodooPS2/releases Special thanks to: Kishor Prins and whole Voodoo Input team Please leave feedback even if it works, it will help me to merge it into official Voodoo PS2.
    3 points
  40. It's still a recurring topic on the fourm, understandably so, so I thought I'd write a little recap about it. Brightness keys patch has been subject to discussion and queries for many years and much has been written on the matter. Among others, Rehabman did some extensive research work on this several years go and provided substantial information and debugging material to work out fixes. The brightness keys patch for many -if not most- Dell laptops since, at least, Ivy Bridge generations can be applied through DSDT patching or through pure SSDT patching. A DSDT patch for E6230 was 1st mentioned at OSXL by @jpz4085 in our old Dr Hurt's VoodooPS2Controller kext thread; the work derived from Rehabman's research and publications. I found that the patch was fully reusable on other models of the E Series (except E6x20) and I fully detailed the DSDT patch code in my E6230, E7250 or 7490 guides. Unless I'm mistaken (happy to be corrected if required), the SSDT patch was derived from the DSDT patch by @Jake Lo and provided in various threads of his that I can't specifically remember. To successfully apply the required SSDT patch, given that a little tuning may be required depending on the target platform, it's most useful to understand that brightness keys of Dell laptops usually operate at ACPI level and according to the following reversed engineered process: brightness keys operation is handled through BRT6 method. BRT6 method is attached to IGPU device but there can be a 2nd BRT6 method under GFX0 (or whatever other name) if the laptop is fitted with a dGPU too. BRT6 is usually called from EV5 method. EV5 method is usually called from SMEE method on the condition that a call to OSID method returns a value greater or equal to 32 (0x20). OSID method returns the value set in ACOS parameter (integer). ACOS is set to different values according to the nature of the Operating System. It is set to 32 (0x20) for Win Vista, 64 (0x40) for Linux or 128 (0x80) for Win7/8/8.1. Value is under 32 for Windows versions older than Vista. I'll pass on the upstream process _Q66->NEVT->SMIE->SMEE which is of no specific interest in the context of this brightness keys patch description. Sample methods grabbed from Latitude E7270's extracted DSDT: BRT6 Method Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) // 1st arg=1 for brightness increase { Notify (LCD, 0x86) } If (And (Arg0, 0x02)) // 1st arg=2 for brigthness decrease { Notify (LCD, 0x87) } } EV5 method Method (EV5, 2, NotSerialized) { \_SB.PCI0.IGPU.BRT6 (Arg0, Arg1) // Call to BRT6 with 2 arguments } SMEE method Method (SMEE, 1, NotSerialized) { Store (Arg0, Local0) Store (GENS (0x11, Zero, Zero), Local0) If (LGreaterEqual (\_SB.OSID (), 0x20)) // If OSID returns a value >= 32 { If (And (Local0, 0x04)) { EV5 (One, Zero) // Call to EV5 with 1st arg set to 1 } If (And (Local0, 0x02)) { EV5 (0x02, Zero) // Call to EV5 with 1st arg set to 2 } } If (And (Local0, 0x08)) { Store (GENS (0x1D, Zero, Zero), Local0) EV17 (Local0, Zero) } } OSID method Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) // Check if ACOS lower or equal to 0 { Store (One, ACOS) // Initialises ACOS to 1 Store (Zero, ACSE) If (CondRefOf (\_OSI, Local0)) // Engages in tests according to OS identification { If (_OSI (WXP)) { Store (0x10, ACOS) // Sets ACOS to 16 if Win XP } If (_OSI (WLG)) { Store (0x20, ACOS) // Sets ACOS to 32 if Win Vista } If (_OSI (WIN7)) { Store (0x80, ACOS) // Sets ACOS to 128 if Win7 } If (_OSI (WIN8)) { Store (0x80, ACOS) // Sets ACOS to 128 if Win8 Store (One, ACSE) } If (_OSI (WN81)) { Store (0x80, ACOS) // Sets ACOS to 128 if Win8.1 Store (0x02, ACSE) } If (_OSI (LINX)) { Store (0x40, ACOS) // Sets ACOS to 64 if Linux } } Else { If (STRE (_OS, W98S)) { Store (0x02, ACOS) // Sets ACOS to 2 if Win98 } If (STRE (_OS, WINM)) { Store (0x04, ACOS) // Sets ACOS to 4 if Win ME } If (STRE (_OS, NT5S)) { Store (0x08, ACOS) // Sets ACOS to 8 if Win NT } } } Return (ACOS) // Value returned by OSID method } It should also be noted that, brightness keys patching only appears to work with VoodooPS2Controller kext, not with ApplePS2Controller (at least for me and the platforms I tested). To enable brightness control through the brightness keys of Dell laptops, 2 x things must be done: ensure that OSID returns a value greater or equal to 32 (0x20) for "Darwin" OS (i.e. OS X/macOS) ensure the correct key stroke codes are captured in BRT6 method (by default, BRT6 usually only operates for key stroke codes 0x86 and 0x87) 1) DSDT patch method: This is most probably the simplest of the 2 x methods because it involves very basic and very easy patching of the DSDT: 1st part of the patch is to insert a reference to Darwin OS as one of the tests used to set ACOS parameter to, at least, 32 (0x20). 2nd part of the patch is to insert the relevant key stroke codes in BRT6 method as keyboard event notifications. One code for brightness increase and another one for brightness decrease. Rehabman's ACPI debugging tools have allowed to identify various key codes, depending on laptops: brightness increase: key codes 0x10, 0x206, 0x286, 0x366, 0x0406 brightness decrease: key codes 0x20, 0x205, 0x285, 0x365, 0x0405 I have found that key codes 0x0365 and 0x0366 applied to the Latitude E6x20, E6x30, E6x40, E7x50, E7x70 or other 7x90. @Jake Lo found that codes 0x0405 and 0x0406 applied to other models such as the Precision 5510 or 7510. The DSDT patch can then be applied in the trend of the following code: OSID method Before: Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) { [...] If (CondRefOf (\_OSI, Local0)) { [...] If (_OSI (WIN7)) { Store (0x80, ACOS) } [...] } [...] } Return (ACOS) } After: Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) { [...] If (CondRefOf (\_OSI, Local0)) { [...] If (LOr (_OSI ("Darwin"), _OSI (WIN7))) // Changes test from Win7-only to Darwin or Win7 { Store (0x80, ACOS) // Thereby setting ACOS to 128 for Darwin, i.e. OS X/macOS } [...] } [...] } Return (ACOS) } BRT6 method Before: Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) } } After: Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x0366) // Add capture of brightness-up key stroke } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x0365) // Add capture of brightness-down key stroke } } and that's it! 2) SSDT patch method: Over the last few years, DSDT patching has gradually and increasingly become less fashionable within the Hackintosh community in favour of alternatives in the form of dedicated and specific SSDTs, something which is considered far more efficient because: it's based on on-the-fly ACPI objects renaming in bootloaders. it's based on injection of new ACPI code through small and targeted SSDT tables that are meant for that very supplemental purpose (SSDT means Secondary System Description Table). it avoids extracting, fixing, patching, recompiling and replacing the system's original ACPI tables and most notably the DSDT, something that can be quite arduous at times. However, the process involved is a much more complicated because: it requires to have a minimum and non-negligeable skillset in ACPI coding. it requires to analyse the code of the original ACPI tables and often work out sections of code to bypass/replace (no duplicates allowed or code is useless) So, given that this method makes no change to the DSDT, it must: bypass the DSDT's BRT6 method. replace it by a new method that will include the desired keyboard notification codes; this will be done in a dedicated SSDT that can be called SSDT-BRT6. with regards to OSID and the requirement to make it return a value greater or equal to 32, there are 2 x possibilities that can be considered: as per BRT6, bypass the DSDT's OSID method and replace it by a new method that will set ACOS parameter according to "Darwin" OS replace calls to the _OSI method, that performs tests on the type of OS, by an alternative method that simulates Windows for Darwin. This allows to have the contents of the OSID method executed sequentially and set ACOS according to the last test in the list; as it stands, this happens to be the test on Linux which sets ACOS to 64, i.e. a value greater than 32 which is the minimum required. In order to replace the DSDT's BRT6 method by an alternative one, particular caution must be exercised because only the method must be replaced, not the call to it from EV5; so a little creativity is required here... To achieve this, ACPI renaming can be applied in the boot loader config to replace "BRT6,2" (as per contents of the method's definition) by "BRTX,2" rather than replace just "BRT6". This is achieved by configuring the following on-the-fly DSDT patch in the boot loader's config (the exact Hexadecimal string is found by opening the extracted DSDT in a Hex editor): Find (HEX): 4252543602 // Hexadecimal sequence for "BRT6, 2" when opening DSDT with a Hex editor Replace (HEX): 4252545802 // Hexadecimal sequence for "BRTX, 2" as replacement The replacement BRT6 method can then be defined in the dedicated SSDT-BRT6 patched table with the following code: DefinitionBlock ("", "SSDT", 2, "hack", "BRT6", 0x00000000) { External (_SB_.PCI0.IGPU, DeviceObj) // (from opcode) External (_SB_.PCI0.IGPU.LCD_, DeviceObj) // (from opcode) External (_SB_.PCI0.LPCB.PS2K, DeviceObj) // (from opcode) Scope (_SB.PCI0.IGPU) { Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x0366) // Capture of brightness-up key stroke } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x0365) // Capture of brightness-down key stroke } } } } As far as the OSID method is concerned, the trick is simply to rename it to XSID, rename _OSI method to XOSI and inject (Rehabman's ?) pre-existing and publicly available SSDT-XOSI that simulates Win7 or greater for Darwin (it basically returns true to the OS tests). This is achieved by configuring the following on-the-fly DSDT patches in the boot loader's config: Find (HEX): 4F534944 // OSID in Hexadecimal Replace (HEX): 58534944 // XSID in Hexadecimal Find (HEX): 5F4F5349 // _OSI in Hexadecimal Replace (HEX): 584F5349 // XOSI in Hexadecimal Contents of the SSDT-XOSI patched table is as per documented by Rehabman: DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000) { Method (XOSI, 1, NotSerialized) { Store (Package (0x0A) { "Windows", "Windows 2001", "Windows 2001 SP2", "Windows 2006", "Windows 2006 SP1", "Windows 2006.1", "Windows 2009", "Windows 2012", "Windows 2013", "Windows 2015" }, Local0) Return (LNotEqual (Ones, Match (Local0, MEQ, Arg0, MTR, Zero, Zero))) } } And that's it too!
    3 points
  41. Updated pack for OC 0.6.7 below: 7480_OC_0.6.7.zip
    3 points
  42. Ok, just got got Big Sur 11.0.1 (20B29) installed on the E6230 with OC 0.6.3. So far all appears to run Ok. Full acceleration on HD4000. Kept the MBP10,2 SMBIOS with -no_compat_check boot arg.
    3 points
  43. @ten2pwr6 Can you try adding this SSDT to the patched folder and see if it fixed the issue. Worked for @acquarius.13 's 450 G5 SSDT-AWAC.aml.zip
    3 points
  44. While the EM7430 works with my kext. (I guess the product ID needs to be adjusted still). The EM7455 seems not. What I did: Wrote the kext for DW5811e / EM7411 according to the correct PID & VID attached above. Which after it appears on WANN section (location id show xxxxxxxx / 0 as others also have in their screen). Then with the correct APN the error shows: So I updated the firmware and all config settings using LIVE UBUNTU CD 18.04 with: https://github.com/danielewood/sierra-wireless-modems His autoscript is perfect for updating FW, configuring the whole card according to our needs & sets the PID/VID to generic to bypass any vendor locks. Whilst I updated the kext to reflect all MC/EM7455 cards PID/VID (Lenovo / DELL / Generic). Still the error "Network Connection ... " shows. Please also see the location difference: NOTE the firmware: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53 While at!priid? shows the updated firmware: SWI9X30C_02.33.03.00_00_00_GENRIC So I manually check the connection using COM port: screen /dev/tty.wwan 115200 screen /dev/tty.wwan 115200 Which after I'm able to manually connect using at commands. Any ideas where to look? Perhaps it is the interface mapping? <key>InterfaceMapping</key> <dict> <key>0</key> <dict> <key>name</key> <string>wwanDM</string> </dict> <key>2</key> <dict> <key>name</key> <string>wwanGPS</string> </dict> <key>3</key> <dict> <key>name</key> <string>wwan</string> </dict> </dict>
    3 points
  45. Kind donations contribute to the running costs of OSXLatitude.com: server hosting, high-speed Internet line, forum licences, etc. Thank you.
    3 points
  46. Farewell old girl.... she was the last bastion of our original "D" series that started the whole OSXL endeavors..
    3 points
  47. Last update: 17 Jun 2020 Target macOS release: Catalina 10.15.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration on Intel UHD620 iGPU, including brightness control (with Lilu v1.3.8 + WEG v1.3.2) multi-display with HDMI OOB, including HDMI-to-DVI adaptation (HDMI-to-VGA not successful) and VGA/DP over USB Type-C audio, including HDMI, microphone input and headset output (with AppleALC v1.3.9 & layout 11 + CodecCommander v2.7.1) GigEthernet LAN connection (with IntelMausiEthernet 2.4.0 kext) wireless and bluetooth with any compatible card (a DW1820A in my case) left and right USB ports (with Hackintool-generated USBPorts), including USB Type-C integrated webcam (OOB) CPU power management sleep (Lid, Energy Saver settings, Apple menu, Fn-Insert, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) keyboard (with VoodooPS2Controller v1.9.2) touchpad (with VoodooI2C v2.1.4 + VoodooI2CHID v1.0), including tap-to-click (mandatory in PrefPane settings), scroll & zoom, rotate or other multi-finger gestures. On occasions, won't work until system is rebooted one or several times. RTS525a microSD card reader (Performance limited to 5MB/s) Not working: Touchpad buttons TrackPoint 1) 10.15 USB installer creation Using a USB key of 8GB minimum, create a Catalina USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Catalina installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Clover for UEFI booting only Install Clover in the ESP UEFI Drivers Recommended drivers ApfsDriverLoader AptioMemoryFix AudioDxe DataHubDxe FSInject HFSPlus SMCHelper Human Interface Devices Ps2MouseDxe UsbMoueDxe File system Drivers Fat Additional Drivers NvmExpressDxe PartitionDxe Themes (optional) Install Clover Preference Pane (optional) you may use version r5093 attached below: Clover_v2.5k_r5093.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer/copy the files & folders from the Latitude 7490 Catalina Clover pack below to the EFI/Clover folder: 7490_Catalina_Clover_Pack.zip 7490_Catalina_Clover_Pack_#2.zip 7490_Catalina_Clover_Pack_#3.zip 2) 10.15 installation boot the Catalina USB installer at the Clover main menu, select the "Install macOS Catalina" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target Catalina installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Catalina partition>" repeat this until this partition is no longer offered and only the target Catalina partition is left to boot Reboot the target Catalina partition via your USB installer 3) Post-installation tuning Once the target Catalina partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Catalina partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Catalina partition/disk Open this EFI partition and transfer the files & folders from the above Latitude 7490 Catalina Clover pack to the EFI/Clover folder You may then reboot and verify that Catalina boots off your disk through Clover Edit: 02 Nov 2019: - - - - - - - - - - - - - Revised Clover pack #2: DW1820A properties injection commented out (only required for those who have such a card, in which case, remove the # character) Edit: 20 Apr 2020: - - - - - - - - - - - - - Added a note about solution for Realtek RTS525a SD card reader. Edit: 17 Jun 2020: - - - - - - - - - - - - - Revised Clover pack #3: Moved patched DSDT out of ACPI/patched folder since it's causing KP for most people. It was only patched to support brightness control through Fn-F11/Fn-F12. Jake Lo has provided SSDT alternatives in other guides/threads so it's best to use that. I'll try them asap on the 7490 and update accordingly.
    3 points
  48. Nawcom disappeared from the Hackintosh scene long ago but tribute can still be paid to him and his great tools. It sure is dated today but it did the business back in the days and greatly so. These may still be useful for those novices who want to setup a Hackintosh on a platform capable to run Snow Leopard but have no access to a Mac or an existing Hack. Snow Leopard remains the Mac OS X version from which many platforms can upgrade to subsequent OS X/macOS versions as long as their profile (SMBIOS) meets the requirements. Provided one has the Snow Leopard retail DVD or a USB key with retail SL restored to it, Nawcom's modCD or modUSB can be very useful to setup a temporary basic SL installation to work from. It does not have to be fully tuned up... Nawcom's tools are hard to find on the Net today, so here are copies it. I hope (and think) Nawcom would not mind... OSX86_ModCD-032311-151021.zip -> rename from .zip to .iso and burn the image to a CD/DVD (can be done from Windows or Linux) OSX86_ModUSB.pkg.zip -> unzip this Mac app and run from OS X to create a bootable USB installer (cannot be used in Windows/Linux) For those who wish to know more about the tools, here's a recap written by the man himself back in 2010: Nawcom_tuto.pdf.zip
    3 points
  49. Note: This bootpack should also be compatible with any supported 4th Gen Intel CPU on H81 Intel Chipset Motherboard. Hi all, Just built my first budget desktop hackintosh and pleased to share the bootpack. Specification Gigabyte H81M DS2 4th Gen 3.5 GHz i3-4330 8 GB DDR3 1600 MHz Memory AMD Radeon RX560 (Supported natively by Mac OS Ventura) Intel Graphics HD 4600 (Working natively up to Mac OS Monterey but unusable. See notes below. Not tested yet on Mac OS Ventura) AMD Radeon 7750 1GB (Supported natively up to Mac OS Monterey) (See other post here : https://osxlatitude.com/forums/topic/11048-amd-radeon-hd-7750-supported-by-mac-os-mojave-catalina/) OpenCore Bootpack The OpenCore bootpack can be downloaded from the following link:- macOS Ventura 13.0 (OpenCore 0.8.5):- OpenCore-13.0-0.8.5.zip Looks like OpenCore can still boot Ventura using Mac Mini 18 smbios. However, supported GPU need to be used e.g. AMD RX 560 in my current case. Updated all kexts to latest versions macOS Monterey 12.6 (OpenCore 0.8.4):- OpenCore-12.6-0.8.4.zip Updated all kexts to latest versions macOS Monterey 12.4 (OpenCore 0.8.1):- OpenCore-12.4-0.8.1.zip Updated all kexts to latest versions macOS Monterey 12.3.1 (OpenCore 0.8.0):- OpenCore-12.3.1-0.8.0.zip Updated all kexts to latest versions macOS Monterey 12.2.1 (OpenCore 0.7.8):- OpenCore-12.2.1-0.7.8.zip Updated all kexts to latest versions macOS Monterey 12.1 (OpenCore 0.7.6):- OpenCore-12.1-0.7.6.zip Updated all kexts to latest versions macOS Monterey 12.0.1 (OpenCore 0.7.4):- OpenCore-12.0.1-0.7.4.zip macOS Monterey 12 Beta 9(OpenCore 0.7.4):- OpenCore-11.6-0.7.4.zip Updated OpenCore and all kexts to latest versions Changed SMBIOS to iMac Late 2015 for installer to work macOS Monterey 12 Beta (21A5248p) (OpenCore 0.7.0):- OpenCore-12-Beta-0.7.0.zip Updated all kexts to latest versions Changed SMBIOS to Mac Mini Late 2014 as Intel 4th Gen Haswell iMacs no longer supported macOS Big Sur 11.6 (OpenCore 0.7.4):- OpenCore-11.6-0.7.4.zip Updated opencore & all kexts to latest versions macOS Big Sur 11.3 & 11.3.1 (OpenCore 0.6.9):- OpenCore-11.3-0.6.9.zip So far everything should work Updated all kexts to latest versions macOS Big Sur 11.0.1 (OpenCore 0.6.4):- OpenCore-11.0.1-0.6.4.zip Updated all kexts to latest versions This bootpack is able to boot Mac OS Big Sur Beta 10. However, it is still getting issue where installer will exit prematurely after starting. If anyone managed to resolve this issue do give me a buzz. Found the cause of installer exiting prematurely after start. Its a hard disk issue. Also had issue similar issue when installing windows on the same hard disk. So far everything should works except sleep. integrated graphics need to be disabled in bios in order for sleep to work (i.e. no desktop freeze after wake). macOS Big Sur 11.0.1 (OpenCore 0.6.3):- OpenCore-11.0.1.zip macOS Big Sur Beta 10 (OpenCore 0.6.3):- OpenCore-11.0-Beta10.zip macOS Big Sur Beta 4 (20A5343i) (OpenCore 0.6.0):- OpenCore-11.0-Beta-20A5343i.zip So far everything works except sleep. System freezes after wake. This bootpack is based on latest OC and lilu & friends kext release based on OC 0.6.0 macOS Big Sur Beta 2 (20A4300b) (OpenCore 0.6.0):- OpenCore-11.0-Beta -20A4300b.zip So far everything works except sleep. System freezes after wake. This bootpack allow both updating of existing beta 1 to beta 2 and installing new hard drive by running the installer app from an existing Mac OS system. USB installer created from createmediainstall still cannot be booted. Resolved. As @Jake Lo advise, with latest lilu we can omit "-lilubetaall vsmcgen=1 booter-fileset-kernel booter-fileset-basesystem" stuff. Make sure to reset nvram on first OC boot and boot the usb installer on reboot. However, looks like "booter-fileset-kernel & booter-fileset-basesystem" need to be remove when booting usb only and 1st stage installation. 2nd stage looks like it still need those to boot. macOS Big Sur Beta 1 (20A4299v) (OpenCore 0.6.0) :- OpenCore-11.0-Beta-20A4299v.zip USB installer still cannot be booted using clover or opencore. Big Sur need to be cloned from existing real mac disk image. So far everything works except for sleep. Downloaded the real mac disk image and followed installation guide from here: https://www.olarila.com/topic/8977-guide-installrestore-bigsur-with-opencore/. Initial bootpack for OpenCore obtained from here: https://www.reddit.com/r/hackintosh/comments/fuf6z7/open_core_056_catalina_10154_gaz87mxd3h_i74770/. Updated network card kext from my clover bootpack and updated OpenCore to version 0.6.0. (Note: These bootpacks can also be used to boot macOS Catalina) Clover Bootpack The Clover bootpack can be downloaded from the following link:- Mac OS Monterey 12.1 (Clover v5142) CLOVER-12.1.zip Updated all kexts to latest versions too Mac OS Monterey 12.0.1 (Clover v5141) CLOVER-12.0.1.zip Mac OS Monterey 12 Beta 10 (Clover v5140) CLOVER-11.6.zip Working for Beta 10 with preferred Mac Mini Late 2014 smbios Mac OS Monterey 12 Beta (21A5248p) (Clover v5135) CLOVER-11.3.1.zip Working for Beta 1 to Beta 7 with Mac Mini Late 2014 smbios Working for Beta 8 but need to change smbios to iMac Late 2015 Not Working for Beta 9 at the moment. Getting boot loop. Mac OS Big Sur 11.6 (Clover v5140) CLOVER-11.6.zip Updated clover & all kexts to latest versions Mac OS Big Sur 11.3.1 (Clover v5135) CLOVER-11.3.1.zip So far everything should work Updated all kexts to latest version. Mac OS Catalina 10.15.7 (Clover v5126) CLOVER-10.5.7.zip Updated Clover and kexts to latest versions. Clover is already using the Quirks features which are normally required for Intel 4th Haswell desktops. Clover bootpack is able to boot Mac OS Big Sur 11.0.1 after it has been installed. Still not able to boot installer. Mac OS Catalina 10.15.4 (Clover v5116) :- CLOVER10.15.4.zip Updated Clover, Lilu.kext, VirtualSMC.kexts & Whatevergreen.kext to latest versions. Mac OS Catalina 10.15.1 (Clover v5070) :- CLOVER-10.15.1.zip Whatevergreen.kext updated to 1.3.4 to resolve blank screen after boot. Mac OS Catalina 10.15 (Clover v5070) :- CLOVER-10.15.zip Mac OS Mojave 10.14.4 (Clover v4910) :- CLOVER-10.14.4.zip Mac OS Sierra 10.12.6 / Mac OS High Sierra 10.13 (Clover v4241) :- CLOVER.zip So far, everything works including sleep with power nap! So far this motherboard is very compatible with Mac OS and patched DSDT / SSDT is not required. Credits goes to Jake Lo, Bronx Teck & Herve Notes on Integrated HD4600 GPU Although the integrated HD4600 GPU can be enabled by simply injecting intel from clover, the GPU cannot be utilized since my motherboard does not have a HDMI output! Using dedicated GPU such as RX 560 while the integrated HD4600 GPU is enabled may cause video playback in chrome to be jibrish and iTunes video playback to freeze the desktop. The integrated GPU need to be disabled from bios to resolve this. Let me know if the clover bootpack works for you. Cheers! OpenCore-13.0-0.8.5.zip
    3 points
  50. Hi all, Specifications Dell Vostro 5568 7th Gen i7-7500U @2.7GHz 8GB DDR4 2400 MHz Memory Intel Graphics HD620 / NVIDIA® GeForce® 940MX 4GB GDDR5 15.6" screen (1920 x 1080) OpenCore Bootpacks Mac 0S Ventura 13.4.1 (OpenCore 0.9.3) OC-13.4.1..zip Updated OC and kexts to latest version. So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Mac 0S Ventura 13.0 (OpenCore 0.8.5) OC-13.zip Updated OC and kexts to latest version. So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN (Crashes when trying to connect. Need to look for updated kexts later) Mac 0S Monterey 12.4 (OpenCore 0.8.1) OC-12.4.zip Updated OC and kexts to latest version. So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Headphone jack is not working Trackpad is not working Mac 0S Monterey 12.0.1 (OpenCore 0.7.6) OC-12.0.1.zip Updated OC and kexts to latest version. So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Headphone jack is not working Trackpad is having issues with clicks. Resolving this issue atm. Mac OS Big Sur 11.3.1 (OpenCore 0.6.9) OC-11.3.1.zip Updated OC and kexts to latest version. So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Can refer to this:- https://openintelwireless.github.io). I have replaced my wifi card before these kext were available so I can't test them myself). Headphone jack is not working. Mac OS Big Sur 11.0.1 (OpenCore 0.6.3) OC-11.0.1 Rev A.zip (AppleHDA.kext for audio) OC-11.0.1.zip (VoodooHDA.kext for audio) So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS) Headphone jack not working when fully inserted. Got some audio when halfway inserted. I am very pleased that sleep works and both hdmi and vga ports are working. Two monitors can be connected to the laptop! LOL OpenCore guide and credits mainly to here : OpenCore Install Guide for Kaby Lake Laptop Kexts & ACPI patch files credits mainly to my dear friend @Jake Lo. I migrated these from Clover bootloader. Mac OS Catalina 10.15.7 (OpenCore 0.6.3) OC-10.15.7.zip So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) This bootpack is able to boot Mac OS Big Sur 11.0.1 but so far its stuck at "waiting for.. boot-uuid-media...". If anyone managed to resolve this do let me know! @Jake Lo correctly highlighted that Big Sur removed some ports. Using Catalina AHCIPort.kext resolved this issue. Cheers! Clover Bootpacks Credits goes to Bronx Teck, Herve & Jake Lo Mac OS Catalina 10.15.5 (Clover V5119) :- CLOVER-10.15.5.zip Graphics Platform ID injected in order to resolve screen flickering and to get hdmi to work in Mac OS Catalina 10.15.5 Everything works except for the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) Sleeps does not work at the moment. Each time attempting to sleep the screen just wakes up. HDMI works. However, during boot up it does not detect the hdmi is connected. Need to manual unplug and replug the hdmi to get mac os to detect it again. Mac OS Catalina 10.15.4 (Clover V5118) :- CLOVER-10.15.4.zip Everything works except for the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) This bootpack does not inject any graphics platform-id. Seems to resolve the screen flickering after wake from sleep issue. Using the usual graphics platform-id of 59160000 will cause major screen flickering issue after waking from sleep. HDMI does not work without any graphics platform-id injected. However, with platform-id injected, I have yet to resolve my screen going blank or system hang issues when I connect external monitor to hdmi. Further, injecting the usual platform-id will cause flickering issue after sleep wake. So for now I rather live with no HDMI output so that it can sleep without any screen flickering after wake LOL. Mac OS High Sierra 10.13.6 (Clover V4643) :- CLOVER V3.zip Updated Lilu.kext and all Intel graphics kexts to the latest (these are the final intel graphics specific lilu plugins as whatevergreen will integrate all these plugins for 10.14 onwards) Added 10.13.6 USB port limit patch (By Jake Lo) Disabled eDP port patch which was previously enabled as not needed (By Jake Lo) Added EDID entries (disabled by default) as potential solution to screen flicker after wake. @woaiba15 was able to solve this issue with this injection but I could not replicate it. Enable EDID injection to test it. Mac OS High Sierra 10.13.1 (Clover v4289) :- CLOVER V2.zip Mac OS Sierra 10.12.6 / High Sierra 10.13 (Clover v4241) :- CLOVER.zip Added DellSMBIOSPatch in config.plist to show correct Model Identifier. Some software uses Model Identifier to check hardware compatibility such as AutoCAD 2016 LT (P/s: Thanks Jake for highlighting this just in time when I had problem installing it!) (26 Aug 2017) Fixed distorted sound from headphones on Mac OS Sierra 10.12.6 (31 Aug 2017) Kernel Extension (Kext) in "/Library/Extensions" Folder:- KEXT-10.13.zip (Note: Your will need to repair permission and rebuild cache for /Library/Extensions) Everything works except for the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) Sleep (Screen flickers after waking from sleep for 10.12.6 and screen blanks after waking from sleep for 10.13) Disconnecting HDMI out cable causes blank screen Last Remarks Let me know if the above bootpack works for you. If you managed to get some of the remaining issues resolved, do let me know so that I can update this thread. Cheers!
    3 points
×
×
  • Create New...