Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 10/02/17 in all areas

  1. 11 points
    Dell Latitude/Inspiron/Precision/Vostro/XPS - Clover Guide Up to Sierra Only High Sierra Guide below Mojave 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 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 Drivers64UEFI\DataHubDxe-64 Drivers64UEFI\FSInject-64 Drivers64UEFI\SMCHelper-64 Drivers64UEFI\ApfsDriverLoader-64 Drivers64UEFI\AptioMemoryFix-64 Drivers64UEFI\PartitionDxe-64 Add to Drivers64UEFI\HFSPlus.efi (Not included in Clover installer) 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 Drivers64UEFI\DataHubDxe-64 Drivers64UEFI\FSInject-64 Drivers64UEFI\SMCHelper-64 Drivers64UEFI\ApfsDriverLoader-64 Drivers64UEFI\AptioMemoryFix-64 Drivers64UEFI\PartitionDxe-64 Install Clover Preference Pane Add to Drivers64UEFI\HFSPlus.efi (Not included in Clover installer) 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.
  2. 6 points
    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
  3. 6 points
    Last update: 22 May 2019 Dell DW1820A: Ok Ok-ish NOk ? 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 3 x different models of the card. Whilst they all carry the same Broadcom id 14e4:43a3, they each carry a different subsystem id: 1028:0021 (part # CN-0VW3T3) -> tested 100% with the 3 x cards I possess 1028:0021 (part # CN-096JNT) -> seems to require AirportBrcmFixup kext + brcmfx-driver=1 boot option otherwise, after ~10mins Ok, CPU overloads and system grounds to a halt/freeze 1028:0022 (part # ?) -> not tested, no report to date 1028:0023 (part # CN-08PKF4) -> several reports of issues (5-10mins Ok, then system freeze). To be tested with AirportBrcmFixup kext + brcmfx-driver=1 boot option; may work with those. I acquired a Dell DW1820A a few months ago and was able to play with that card on a 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. Building on Hugotai's success, I seeked to work out an easier solution that would not require kext removal and Info.plist patching but, instead, something that could be implemented through hardware properties injection, either through DSDT patching or Clover configuration. Once Hugotai's solution was verified and confirmed, I worked out the following Clover-based solution 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. Use Clover Configurator app to that effect. inject the following properties either in DSDT or through Clover (latter recommended): compatibility of the card with Broadcom chips 14e4:4331 or 14e4:4353 that are handled by IO80211Family's PlugIn kext AirPortBrcm4360 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, only to 40MHz which resulted in a local wireless connection limited to 400Mbps (vs. 867Mbps) and reduced my overall 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 returns a solid TX and RX rates at 300Mbps. 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 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,4331" // Declares compatibility with BCM94331; "pci14e4:4353" for BCM43224 may also be used } }) } } } Properties injection through Clover config: An easier alternative is to inject those properties in Clover via Clover Configurator app. This can be done within the Devices 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, 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 = 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 Clover or DSDT, there's nothing left to do but reboot the computer. The DW1820A card will then be fully active and capable to connect to 2.4/5GHz networks at full speed. Results: On the Bluetooth side, once the usual Rehabman's Broadcom firmware patching kexts are installed (BrcmFirmwareRepo + BrcmPatchRAM2), 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
  4. 6 points
    Mojave Clover 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! New Installation BIOS: Set to Default, apply, then set SATA Operations to AHCI, set Boot List Option to UEFI, Disable Secure Boot Note: By default, upgrading or new Install of Mojave on an SSD drive, it'll automatically convert to APFS format. (1) Create the USB installer via Terminal with "createinstallmedia" (a minimum of 16GB UFD is needed or an external USB drive) sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/"target_USB" --applicationpath /Applications/Install\ macOS\ Mojave.app --nointeraction Note: target_USB = name of the USB drive you're writing to. When done, USB Drive will automatically renamed to "Install MacOS Mojave" (2) Install Clover with following config, add appropriate Bootpack to /EFI/Clover UEFI: Install for UEFI booting only Install Clover in the ESP Drivers64UEFI\DataHubDxe-64 Drivers64UEFI\FSInject-64 Drivers64UEFI\SMCHelper-64 Drivers64UEFI\ApfsDriverLoader-64 Drivers64UEFI\AptioMemoryFix-64 Drivers64UEFI\PartitionDxe-64 Install Clover Preference Pane Finally add to Drivers64UEFI\HFSPlus.efi (not included in Clover installer) (3) Boot with the USB installer, start Disk Utility and initialize your SSD as an APFS drive, name it "Mojave". You can partition drive now if preferred. Close Disk Utility, select Install MacOS. (4) System will auto reboot after files has been copied (5) Boot with USB installer, select "Boot macOS Install from Mojave". Installation will continue installing and reboot (Might have to do this rebooting a couple of times) (6) Boot with USB installer, finish the customization (7) Follow post install steps from Post # 1 Upgrading to Mojave Before upgrading, do the following: (1) Update to latest Clover (2) Upgrade kexts you're currently using found under /EFI/CLOVER/kexts/Other/ and kexts you have installed to /L/E or /S/L/E Common links for new kexts: https://github.com/vit9696/Lilu/releases https://github.com/vit9696/Lilu/blob/master/KnownPlugins.md https://bitbucket.org/RehabMan/ (3) Make sure it's still bootable with the above 2 updates (4) Follow this guide to update Config file and generate USBPort kext Note: Mojave, Lilu + WhateverGreen You cannot use the Clover's KextsToPatch for framebuffer patching in Mojave for Skylake and above MacOS 10.14.1+ does not work with the USB port limit patch, so best to create the USBPort kext in HS Some Mojave bootpack links: E7x70 (Skylake), might work on similar Skylake systems with some tweaks https://osxlatitude.com/forums/topic/9179-dell-latitude-e7x70-clover-uefi-only/?do=findComment&amp;comment=86790 E7x50 (Broadwell), might work on similar Broadwell system with some tweaks https://osxlatitude.com/forums/topic/8514-dell-latitude-e7450-clover-uefi-only/?do=findComment&amp;comment=86791 E7x40 (Haswell), might work on similar Haswell system with some tweaks https://osxlatitude.com/forums/topic/6472-dell-latitude-e7240e7440/?do=findComment&amp;comment=86943 /!\ 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
  5. 5 points
    So according to @Hervé's guidance, I was able to use my DW1820A. My configs were posted here. After some research, I'm able to use Auto Unlock function now, and still no freeze, after 1 hour of usage. A. Some research. Model Typical Devices Device ID Auto Unlock Supports BCM94331CSAX MBP 2012 14e4:4331 NO BCM943224PCIEBT2 MBA 2011 14e4:4353 NO BCM94360CS MBP 2013 14e4:43a0 YES BCM94360CS2 MBA 2013 14e4:43a0 YES It looks like by faking dw1820a(bcm4350) into 14e4:4353 will make it looks like an 2011 mba card, and won't get Auto Unlock function. BCM433x can't use auto unlock, BCM436x can. DW1820A was BCM4350, in between of 433X and 436X. B. The new config. So instead of faking the card into 14e4:4353, and setting brcmfx-driver=1, I tried 14e4,43a0 and set brcmfx-driver=2. And that's it, nothing else changed, everything's working, including Apple Watch Auto Unlock. (It didn't work in the first place, but worked after disabling and enabling the feature again). C. Some screenshots and terminal outputs. a. kextstat|grep -y brcm b. SysInf Wi-Fi. (firmware version changed, and the Auto Unlock line comes out) c. SysInf BLE.( firmware version changed) D. Some problems. I heard some noise, maybe coil whine, after booting into the system with this new config. The noise disappeared after several minutes. I never noticed such noise before switch to this config.
  6. 5 points
    Last update: 16 Apr 2019 Target macOS release: Mojave 10.14.4 (at time of writing) 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.5 + WEG v1.2.7) multi-display with HDMI OOB, including HDMI-to-DVI adaptation (HDMI-to-VGA not successful) audio, including HDMI, microphone input and headset output (with AppleALC v1.3.6 & 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 (OOB) 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 Not working: RTS525a microSD card reader Touchpad buttons TrackPoint Not tested: DP over USB Type-C display output GeekBench v2.4.3 (32bit) gives a 14200+ rating: 1) 10.14 USB installer creation Using a USB key of 8GB minimum, create a Mojave USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Mojave 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 AudioDxe-64 DataHubDxe-64 FSInject-64 SMCHelper-64 ApfsDriverLoader-64 AppleImageLoader-64 AptioMemoryFix-64 Fat-64 HFSPlus NvmExpressDxe-64 PartitionDxe-64 Ps2MouseDxe-64 UsbKbDxe-64 UsbMouseDxe-64 Themes (optional) Install Clover Preference Pane (optional) you may use version r4919 attached below: Clover_v2.4k_r4919.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 the files & folders from the Latitude 7490 Mojave Clover pack below to the EFI/Clover folder: Clover_Pack_7490.zip Clover_Pack_7490_#2.zip Clover_Pack_7490_#3.zip Clover_Pack_7490_#4.zip Clover_Pack_7490_#5.zip 2) 10.14 installation boot the Mojave USB installer at the Clover main menu, select the "Install macOS Mojave" 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 Mojave installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Mojave partition>" repeat this until this partition is no longer offered and only the target Mojave partition is left to boot Reboot the target Mojave partition via your USB installer 3) Post-installation tuning Once the target Mojave partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Mojave 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 Mojave partition/disk Open this EFI partition and transfer the files & folders from the above Latitude 7490 Mojave Clover pack to the EFI/Clover folder You may then reboot and verify that Mojave boots off your disk through Clover
  7. 5 points
    Mojave Mojave Guide Bootpacks - HD5500 Only Add this to /EFI/Clover replacing the old Exx50_Mojave.zip - For Discrete Model Also add this to /EFI/Clover/ACPI/Patched SSDT-Disable-DGPU.aml.zip Follow Post Install above under Sierra Guide UPDATES Mojave 10.14.1 (18B75) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.2 (18C54) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.3 (18D42) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.4 (18E226) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.5 (18F132) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover / update kexts prior to update
  8. 5 points
    Mojave Mojave Guide Bootpacks Replace into /EFI/Clover after you install Clover E7470_Mojave.zip 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 UPDATES Mojave 10.14.1 (18B75) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.2 (18C54) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.3 (18D42) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.4 (18E226) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Mojave 10.14.5 (18F132) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover/update kexts prior to update
  9. 5 points
    High Sierra Clover 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! New Installation Note: By default, upgrading or new Install of HS on an SSD drive, it'll automatically convert to APFS format. If you want to use APFS format, skip step 4 (1) Create the USB installer via Terminal with "createinstallmedia" (a minimum of 16GB UFD is needed or an external USB drive) sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/"target_USB" --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction Note: target_USB = name of the USB drive you're writing to (2) Install Clover with following config, add appropriate Sierra bootpacks Only + Generic EFI from post #2 above ( See note1 below for updating bootpack for HS if there isn't one for your model in post #2) UEFI: Install for UEFI booting only Install Clover in the ESP Drivers64UEFI\DataHubDxe-64 Drivers64UEFI\FSInject-64 Drivers64UEFI\SMCHelper-64 Drivers64UEFI\ApfsDriverLoader-64 Drivers64UEFI\AptioMemoryFix-64 Drivers64UEFI\PartitionDxe-64 Install Clover Preference Pane Finally add to Drivers64UEFI\HFSPlus.efi (not included in Clover installer) Legacy: Install Clover in the ESP Bootloader/Install boot0af in MBR CloverEFI/CloverEFI 64-bits SATA (3) Boot with the USB installer, start Disk Utility and initialize your SSD as an APFS drive. Close Disk Utility, select Install MacOS. If you DO NOT want APFS, then select HFS+ format instead. Then Close Disk Utility and follow step 4, otherwise continue to Step 5 (4) Open the terminal (on the menu bar click Utility>Terminal), and launch this command /Volumes/"Image Volume"/"install macOS High Sierra.app"/Contents/Resources/startosinstall --volume /Volumes/"HighSierra" --agreetolicense --converttoapfs NO Note: HighSierra = name of the drive you're targeting (5) System will auto reboot after files has been copied (6) Boot with USB installer, select "Boot macOS Install from HighSierra". Installation will continue installing and reboot (Might have to do this rebooting a couple of times) (7) Boot with USB installer, finish the customization (8) Follow post install steps from Post # 1 NOTE1: Updating the Sierra Bootpack to be use for High Sierra unless there's a High Sierra bootpack already 1) Edit config.plist from Sierra Bootpack (I recommend using Clover Configurator 4.59 or newer) and activate FixHeaders option under Acpi: 2) Update USB port limit for High Sierra where applicable, if current Sierra Bootpack doesn't have it, then you don't need this. Either disable 10.12 (Red) and add 10.13 (Green - 9 or 100 Series) or modify 10.12 to 10.13 port limit Update: New USB port Limit patch for 10.13.4(5) and 10.13.6 credits to PMHeart 3) Under SMBIOS, update the definition so that Firmware Features and Firmware Feature Mask is now populated 4) [Recommended] Update the Sierra kexts under /EFI/CLOVER/kexts/Other/ Common links for new kexts: https://github.com/vit9696/Lilu/releases https://github.com/vit9696/Lilu/blob/master/KnownPlugins.md https://bitbucket.org/RehabMan/ Upgrading to High Sierra and keeping HFS+ format If you want to keep HFS+ format, run this command instead of launching the "Install MacOS High Sierra.app" /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --agreetolicense --converttoapfs NO If you want to install or upgrade to a different partition/drive /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/"targetdrive" --agreetolicense --converttoapfs NO Note: Repair permission and rebuild cache if you lost audio after upgrade. You must upgrade Clover, Config.plist and kexts as noted in NOTE1: Updating the Sierra Bootpack to be use for High Sierra 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
  10. 5 points
    Clover Bootpacks I'll be adding more bootpacks when I have them confirmed working by members of this forum... Don't forget to check the Update section below (post #4) for updated files and information!!! Note: Sierra bootpacks already have the updated files listed in post #4 Note: Bootpack (EFI) consists of combining the Generic EFI + the model you're downloading!!! Instruction: 1) Download the Generic EFI folder. Generic EFI Folder EFI_v4961.zip 2) Download model below and add the contents into the Generic /EFI/Clover <- folder Latitude UEFI Only - GUID Scheme - Kabylake (OS X 10.12.6 and Up)- (See Note2 below) Mojave 7480_Mojave.zip For Optimus models, add to /EFI/Clover/ACPI/Patched DisableDiscreteGraphics.zip Sierra / High Sierra 5480_HD620_v1.6.4_HS.zip 5480_HD630-Optimus_HS.zip (BIOS 1.9.3) - Skylake (OS X 10.11.4 and Up)- (See Note2 below) El Capitan E7x70.zip - latest Sierra / High Sierra bootpack here Sierra 5480_BIOSv1.5.2.zip E5470_1.17.3_HS.zip High Sierra E5470_1.18.6_HS.zip - Broadwell - (See Note2 below) El Capitan E7450_update.zip - latest Sierra /High Sierra bootpack here E5450_HD5500.zip E5550.zip Sierra E5550_A15.zip E5550_A15_Disable_GT820M.zip E5450_HD5500_A15.zip 3450_A13.zip High Sierra E5450_HS_A19.zip - Haswell El Capitan E7440.zip E6540.zip E5540.zip E5450_HD4400.zip 3550.zip 3540.zip 3440.zip 3340.zip Sierra E7440_A20.zip E6540_Optimus_A17.zip E6540_HD4600_Only.zip E6440_A14.zip - based off Hervé's work E5540_Sierra.zip E5440_A13.zip 3550_HD4400_A12.zip High Sierra E7440_HS.zip E6440_A14_HS E5440_A21_Disable-Nvidia.zip Mojave E6440_HD4600_Only_Mojave.zip - IvyBridge El Capitan E6230.zip - 1366x768 E6430.zip - 1600x900 and above E5530.zip - Rename Config/DSDT depending on display resolution Sierra E6530_HD4000_Only.zip 6430u_1366x768.zip - BIOS A06 See here for 6430u HiRes (1600x900) file E6430_A12.zip - check Readme.txt inside bootpack E5530_A12.zip E6330_A11.zip - check Readme.txt inside bootpack E6230_A11.zip E6230_HD3000.zip -> this has SandyBridge CPU High Sierra E6230_A11 Legacy - GUID Scheme - See Note1 below - SandyBridge El Capitan E6420.zip - 1600x900 E6x20_NVS.zip E6220.zip - 1366x768 E5420.zip Sierra E6220_A13.zip E5520_A14.zip - check Readme.txt inside bootpack E5420.zip - check Readme.txt inside bootpack E6420_HD3000_A23.zip- check Readme.txt inside ACPI/Patched folder E6420_Optimus_A23.zip - check Readme.txt inside ACPI/Patched folder E6520_Optimus_A19.zip - check Readme.txt inside ACPI/Patched folder High Sierra E6520_Disabled-NVS_HS.zip E6220_A13_HS.zip Inspiron UEFI Only - GUID Scheme - Broadwell - (See Note2 below) El Capitan 5458.zip Inspiron_5548.zip 5558_HD5500_Only.zip 5558_HD5500_DisableNvidia.zip Sierra 3543_A08.zip 5548_HD5500_Only.zip 5548_m270-Disabed_A07.zip 5558_920M-Disabled_A14.zip High Sierra 5558_920M-Disabled_A14_HS.zip - Haswell El Capitan 5558_HD4400.zip 3542.zip Sierra 3542_A12.zip High Sierra 5558_HD4400_HS.zip Precision UEFI Only - GUID Scheme - Skylake (OS X 10.11.4 and Up)- (See Note2 below) El Capitan 5510_HD530_Disabled-Nvidia.zip Sierra 5510_HD530_1.2.25.zip 7510_HD530_1.12.4.zip - (See more info here) Vostro UEFI Only - GUID Scheme - Kabylake Sierra / High Sierra Vostro_3468_Biosv01.07.00_HS.zip Vostro_3468_2.3.0_HS.zip XPS UEFI Only - GUID Scheme - Haswell Sierra / High Sierra XPS 12 9Q33_A07.zip Note1: For Exx20 (SandyBridge models), use Legacy - GUID Scheme. Not UEFI Install Clover with the following settings in 1: Prepare Bootable USB Drive step 26 above: Install Clover in the ESP Bootloader/Install boot0af in MBR CloverEFI/CloverEFI 64-bits SATA Note2: Systems with Broadwell / Skylake / Kabylake CPU such as Latitude E7450 and Inspiron 5548, you'll need to set the DVMT prealloc to 96MB in order to bypass KP and to enable full graphics with full QE/CI. For more info, see here. /!\ New Development: If you don't want to mod the BIOS as it might be difficult for some models, you could skip this step by adding 2 new kexts to /EFI/Clover/kexts/Other Lilu.kext & Whatevergreen Notes3: To prevent artifacts with HD 4000, the following models should not exceed BIOS A11. Downgrade to A02/A03 and then upgrade to A11 if it has exceeded: E6x30, E5x30 Latitude 6340U should stay at A06
  11. 4 points
    Heya! After a lot of playing around with ASUS acpi tables I have finally come up with a SSDT that will work nearly on all ASUS laptops (Haswell or above) for reading FAN RPM, CPU TEMP and also Custom Controlling FAN. I do not have hardware below Haswell so can't test. If someone get's it working using this SSDT on machines prior to haswell. Let me and others know. Background Info: The system FAN is generally controlled by the embedded controller (EC) but there are methods in ACPI that can let you read and control your system FAN. As you might know, ASUS machines are the best for hackintosh as they have the best written ACPI code. Like, if it was HP instead of ASUS you would have to acquire a mutex object. Write a value to the EC and then release the object. But in ASUS machines there is a method that takes arguments and does this job automatically. Still. There are multiple methods in our DSDT that allow us to read and control system FAN. For example to read FAN speed, there are two ways. If you observe, the FAN speed is at offset 0x93 of EC (Use RWEverything to find out) So, when we search for Offset 0x93 in the DSDT we get a result like this: Offset (0x93), TAH0, 16, // TAH0 stands for FAN1 TAH1, 16, // TAH1 stands for FAN2 (in case your laptop has 2 fans) TSTP, 16, // TSTP stores current fan value in some bytes Note: Instead of using RWEverything if you have a look at method TACH you can see that it stores the values in TAH0 and TAH1 depending upon the Args supplied. So, searching for TAH0 or TAH1 we can see that they are located at offset 0x93 So, now we can read the value from these registers in some units and then we will have to use some formula to convert that unit to RPM. In order to find that formula, if you have a look at Method TACH in dsdt, you will see: Method (TACH, 1, Serialized) { Name (_T_0, Zero) If (ECAV ()) { While (One) { _T_0 = Arg0 If ((_T_0 == Zero)) { Local0 = TAH0 Break } ElseIf ((_T_0 == One)) { Local0 = TAH1 Break } Else { Return (Ones) } Break } Local0 *= 0x02 If ((Local0 != Zero)) { Divide (0x0041CDB4, Local0, Local1, Local0) Return (Local0) } Else { Return (Ones) } } Else { Return (Ones) } } So, we know that we have to store the value from TAH0 or TAH1 (depends on Arg0) and then we have to multiply it by 2 and then we have to divide it by 0x0041CDB4 (4312500) to get the value in RPMs. Once we know that, we could write a simple ACPI code to return the value in RPMs like: // GRPM means get RPM Method (GRPM, 0) { // Store value in Local0 Local0 = \_SB.PCI0.LPCB.EC0.TAH0 // If local0 is not equal to 0 If (Local0 != 0){ // Multiply by 2 Local0 = Local0 * 2 // Divide by 4312500 Divide (0x0041CDB4, Local0, Local1, Local0) } // Return the value Return (Local0) } As you can see this is very expensive method. But what we learned here is, If we execute method TACH with Arg0 as 0 (Zero) it will give us the speed in RPM of FAN 1. Similarly, if we use Arg0 as 1 (One) it will return the value in RPM for FAN 2 My laptop only has one FAN so, I can execute method TACH like, \SB.PCI0.LPCB.EC0.TACH(0) // Using Arg0 as Zero for FAN 1 And it will give me FANs RPM, so, instead of reading from EC and converting bits to RPM this is more preferable. Also, EC bytes may change while patching DSDT so it is a good idea to use dynamic methods so that a single SSDT could work for all machines. One such example is, If you use ACPIBatteryManager then you will have to convert 16bits registers to 8bits. And then, to use that "reading RPM from EC method you will have to create a new method to combine 2 8 bits registers to 1 16 bit like, // JEBR = Join 8 bit registers Method (JEBR, 2) { Return ((Arg0 | (Arg1 << 8))) // Arg0 and Arg1 will be 8Bit register 1 and 2 respectively (AH00, AH01) } Now moving to FAN control, If you have a look at method QMOD in DSDT: Method (QMOD, 1, NotSerialized) { If ((Arg0 == Zero)) { Return (Zero) // If arg0 is Zero. Terminate by returning 0 } If ((Arg0 == One)) { ^^PCI0.LPCB.EC0.ST98 (QFAN) // Hmm, ST98 is somewhat related to FAN control } If ((Arg0 == 0x02)) { ^^PCI0.LPCB.EC0.ST98 (0xFF) // Okay, ST98 again.. Something is interesting } Return (One) } Now, if you look at ST98 you can see: Method (ST98, 1, Serialized) { If (ECAV ()) // Checked if EC is available, will you write to it? { Acquire (MU4T, 0xFFFF) // Oh! So you are acquiring a mutex object CMD = 0xFF EDA1 = 0x98 EDA2 = Arg0 // Oh, so you did write Arg0 in EDA2 (Located in EC01 OperationRegion) ECAC () Release (MU4T) // Released it here, you did write something to the EC for sure Return (Zero) } Return (Ones) } Now, we can understand that, method QMOD (Quiet Mode?) Takes 1 argument that could be (0, 1 or 2). We can eliminate 0 as when we pass Arg0 as 0 it simply returns. Interesting are args 1 and 2 When using 1 it passes Arg0 to ST98 as QFAN's value (Hmm.. What is this QFAN) When using 2 it passes Arg0 to ST98 as 0xFF (255) (Oh wait! according to ACPI spec, 255 is max allowed FAN value.) Gotcha! We can use ST98 and pass it an arg ranging between 0x0 (0) to 0xFF (255) where 0 is for FAN off and 255 is for Max allowed or auto. But, why is there a QMOD method then? There might be some good reason for that. So, we will not invoke ST98 directly but will use the modus operandi of method QMOD Like, we will first store that max allowed FAN value in QFAN Then, we will invoke QMOD with Arg0 as 1 (One). Which will invoke ST98 for us hence, setting the max allowed speed for FAN. So, the ACPI code for this would be: Method (SETR, 0) { QFAN = 200 // Suppose we want to use max allowed value as 200 // Now we can call QMOD with Arg0 as 1 QMOD (1) } Now we know what to do. We now just need to write a method that can calculate the CPU temperature and then set FAN RPM accordingly. This is when you will use my SSDT-FAN How to implement: Requirements: FakeSMC kext along with sensors installed at /L/E or /S/L/E (DO NOT INJECT USING CLOVER) ACPIPoller.kext HWMonitor for monitoring CPU Temp and FANS My SSDT-FAN.aml Installation: Place SSDT-FAN.aml to /EFI/CLOVER/ACPI/patched (If using sorted order make sure you add SSDT-FAN to it) Install ACPIPoller to /L/E or /S/L/E (not both and definitely do not inject using CLOVER) Configuration: You can set "Name (UCFC, One)" to "Name (UCFC, Zero)" in my SSDT-FAN in case you want to use default FAN control method as provided by your OEM. My SSDT will only provide FAN RPM reading and CPU Temp reading.Achievements: Default scaling that ASUS provided was from 2200RPM to 2900RPM (Fan spinning fast without use) I managed to bring scale it from 255RPM to 5026RPM (Fan turns off if temp Temp rarely goes above 53˚C (Went up to 68 earlier) Technicalities: As we know know how to implement custom fan control using various methods in our DSDT we can't really use them as is in real life scenarios as FAN will literally be dancing. You might have observed that temperature keeps fluctuating a few degrees every second while you are working on something. Moreover, we need an automated method that can read and set FAN RPM. So, my SSDT calculates average temperature and then also waits for 2 seconds (to handle fluctuation) before increasing the RPM and waits for 5 seconds (to let CPU cool) before lowering RPM. You can edit this timeout by editing "Name (FCTU, 2)" for FanControlTimeoutUp and "Name (FCTD, 5)" for FanControlTimeoutDown. Method to calculate average accredited to RehabMan as he wrote the code first. There is only one known way to calculate average in maths. LOL. If you want to know how it is implemented, read this code: Note: This code is a part of my single optimizer SSDT project for ASUS laptops (Means, I am working on a single SSDT that you could place in your CLOVER/ACPI/patched and will have everything working without patching DSDT. You can customize SSDT using Device ANKD (A Nick's Device) like you can configure this SSDT to use custom FAN control or not). You can have a look at WIP code here // SSDT for FAN readings and custom FAN control for ASUS laptops // Copyright, black.dragon74 <www.osxlatitude.com> // Please configure the options in Device ANKD before compiling this SSDT DefinitionBlock("SSDT-FAN", "SSDT", 2, "Nick", "AsusFan", 0) { // Declare externals External (\_SB.QFAN, FieldUnitObj) External (\_SB.ATKD.QMOD, MethodObj) External (\_SB.PCI0.LPCB.EC0.ECAV, MethodObj) External (\_SB.PCI0.LPCB.EC0.ECPU, FieldUnitObj) External (\_SB.PCI0.LPCB.EC0.ST83, MethodObj) External (\_SB.PCI0.LPCB.EC0.ST98, MethodObj) External (\_SB.PCI0.LPCB.EC0.TACH, MethodObj) // Create a Nick's device to take care of this SSDT's configurations Device (ANKD) { Name (_HID, "ANKD0000") // Required. DO NOT change Name (UCFC, 1) // Set this to 0 if you don't wanna use my custom FAN control } // Create devices required by FakeSMC_ACPISensors Device (SMCD) { Name (_HID, "FAN0000") // Required, DO NOT change // Add tachometer Name (TACH, Package() { "System FAN", "FAN0" }) // Add CPU heatsink Name (TEMP, Package() { "CPU Heatsink", "TCPU" }) // Method to read FAN RPM (tachometer) Method (FAN0, 0) { // Check is EC is ready If (\_SB.PCI0.LPCB.EC0.ECAV()) { // Continue Local0 = \_SB.PCI0.LPCB.EC0.ST83(0) // Method ST83 acquires mutex and writes value to EC. O stands for FAN 1, Use 1 for FAN 2 If (Local0 == 255) { // If ST83 is 0xFF (Max fan speed) terminate by returning FAN RPM Return (Local0) } // Else, Get RPM and store it in Local0 Local0 = \_SB.PCI0.LPCB.EC0.TACH(0) // Method TACH in DSDT returns current FAN RPM in 100s, Arg0 as 0 is for FAN 1, for FAN 2, use Arg0 as 1 } Else { // Terminate, return Zero Local0 = 0 } // Return 255, 0 or Fan RPM based on conditionals above Return (Local0) } // Method to read CPU temp (CPU Heatsink) Method (TCPU, 0) { // Check if EC is ready If (\_SB.PCI0.LPCB.EC0.ECAV()) { // Then Local0 = \_SB.PCI0.LPCB.EC0.ECPU // EC Field storing current CPU temp Local1 = 60 // From DSDT If (Local0 < 128) { Local1 = Local0 } } Else { // Terminate, return Zero Local1 = 0 } // Return final CPU temp. ACPISensors take care of unit conversion. Return (Local1) } // Custom FAN table by black.dragon74 for ASUS laptops based on RehabMan's idea // Quietest fan operation yet coolest CPU. // Scaling from values as low as 255 RPM to values as high as 5026 RPM (That's great!) // Scaling that ASUS provided was from 2200 RPM to 2900 RPM (Duh!) // Temperatures. 0xFF means if temp is above 52C, let bios take control of things(auto). Name(FTA1, Package() { 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 0xFF, }) // Fan speeds. 255(0xFF) is max/auto, 0(0x00) is for fan off Name(FTA2, Package() { 0, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 120, 130, 140, 160, 185, 205, 225, 245, 250, 255 }) // Time out values Name (FCTU, 2) // RPM Up Name (FCTD, 5) // RPM Down // Table to keep track of past temperatures (to track average) Name (FHST, Buffer() { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }) // Size should match the count of above FTA1 and FTA2 package Name (FIDX, 0) // current index in buffer above Name (FNUM, 0) // number of entries in above buffer to count in avg Name (FSUM, 0) // current sum of entries in buffer // Keeps track of last fan speed set, and counter to set new one Name (FLST, 0xFF) // last index for fan control Name (FCNT, 0) // count of times it has been "wrong", 0 means no counter // Method to control FAN wrt TEMP // Name in ACPIPoller.kext's Info.plist should be FCPU with HID FAN0000 Method (FCPU, 0) { // If UCFC is set to 0, terminate If (\ANKD.UCFC == 0) { Return (0) } // If EC is not ready, terminate If (!\_SB.PCI0.LPCB.EC0.ECAV()) { Return (0) } Local5 = \_SB.PCI0.LPCB.EC0.ECPU // Current temperature of the CPU Heatsink If (Local5 < 128) { Local0 = Local5 // Store temperature in Local0 } Else { Local0 = 60 // As per BIOS } // calculate average temperature Local1 = Local0 + FSUM Local2 = FIDX Local1 -= DerefOf(FHST[Local2]) FHST[Local2] = Local0 FSUM = Local1 // Local1 is new sum // adjust current index into temperature history table Local2++ if (Local2 >= SizeOf(FHST)) { Local2 = 0 } FIDX = Local2 // adjust total items collected in temp table Local2 = FNUM if (Local2 != SizeOf(FHST)) { Local2++ FNUM = Local2 } // Local1 is new sum, Local2 is number of entries in sum Local0 = Local1 / Local2 // Local0 is now average temp // table based search (use avg temperature to search) if (Local0 > 255) { Local0 = 255 } Local2 = Match(FTA1, MGE, Local0, MTR, 0, 0) // calculate difference between current and found index if (Local2 > FLST) { Local1 = Local2 - FLST Local4 = FCTU } else { Local1 = FLST - Local2 Local4 = FCTD } // set new fan speed, if necessary if (!Local1) { // no difference, so leave current fan speed and reset count FCNT = 0 } else { // there is a difference, start/continue process of changing fan Local3 = FCNT FCNT++ // how long to wait depends on how big the difference // 20 secs if diff is 2, 5 secs if diff is 4, etc. Local1 = Local4 / Local1 if (Local3 >= Local1) { // timeout expired, so start setting new fan speed FLST = Local2 // Method 1 (Recommended) // Store custom fan value from table in Local5 Local5 = DerefOf(FTA2[Local2]) // Set QFAN value to that of Local5 \_SB.QFAN = Local5 // Execute QMOD with Arg0 as 1(One) to set FAN's max allowed speed to that of \_SB.QFAN \_SB.ATKD.QMOD(1) // End Method 1 // Method 2 (Works but not recommended) Uncomment the line below to use this (remember to comment lines in method 1) // \_SB.PCI0.LPCB.EC0.ST98 (DerefOf(FTA2[Local2])) // End Method 2 // Reset FAN count (Required in either methods) FCNT = 0 } } Return (1) // Return something as this is a requirement of a ACPI Method } } } Moment of joy: Problem Reporting: Attach proper problem reporting files. See How to generate proper problem reporting files Note: If you see FAN RPM = 255 and hear a lot of noise from FAN it means your FAN is running at it's maximum speed. Regards ACPIPoller.zip SSDT-FAN.zip
  12. 4 points
    Last update: 03 Jul 2019 Specifications: BIOS 1.8.0 1.9.3 1.10.0 (needs SATA in AHCI mode, not RAID or disk won't be seen) Intel 8th gen Kaby Lake R quad-core i7-8650U 1.9GHz CPU (Turbo boost up to 3.9GHz for 3 & 4 cores and up 4.2GHz for 1 & 2 cores) integrated Intel UHD620 GPU 300-1150MHz (PCI ven id 0x8086, dev id 0x5917) 14" 1920x1080 FHD non-touch LCD 16Go DDR4-2400 RAM M.2 2280 512GB SATA SSD (in socket M) Intel i219-LM Gigabit Ethernet (PCI ven id 0x8086, dev id 0x15d7) Realtek ALC256 (ALC3246) High Def audio (PCI ven id 0x10ec, dev id 0x0256) Intel Wireless-AC 8265 M.2 combo wireless card (PCI ven id 0x8086, dev id 0x24FD) + Bluetooth 4.2 PCI ven id 0x8087, dev id 0x0a2b) Dell DW1820A M.2 802.11ac combo wireless card (PCI ven id 0x14e4, dev id 0x43a3) + Bluetooth 4.1 (PCI ven id 0x0a5c, dev id 0x6412) integrated Realtek HD webcam (USB internal, PCI ven id 0x0bda, dev id 0x5650) integrated Realtek RTS525A microSD 4.0 card reader (PCI ven id 0x10ec, dev id 0x525a) Alps I2C HID Multi-Touch Touchpad (PCI ven id 0x1028, dev id 0x081c) Alps I2C HID TrackPoint (PCI ven id 0x044e: dev id 0x1212) 1 x M.2 2230 WLAN slot (socket A) 1 x M.2 2242 WWAN slot (socket B ) 1 x 3.5mm universal jack (combo audio) 3 x USB 3.1 gen1 ports Type-A (right port with PowerShare) 1 x HDMI 1.4 port 1 x DisplayPort on USB Type-c Lat7490:~ admin$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21) 00:15.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 [8086:9d62] (rev 21) 00:15.3 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #3 [8086:9d63] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) 00:16.3 Serial controller [0700]: Intel Corporation Sunrise Point-LP Active Management Technology - SOL [8086:9d3d] (rev 21) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) 00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 [8086:9d12] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC Controller/eSPI Controller [8086:9d4e] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-LM [8086:15d7] (rev 21) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4350 802.11ac Wireless Network Adapter [14e4:43a3] (rev 08) NB: The E7490 is able to boot from microSD card in Legacy mode but, unfortunately, the RTS525a is not supported under OS X/macOS.
  13. 4 points
    I got to test the Dell WD15 USB Type-c docking station today. Supported OOB: HDMI, mini-DP and VGA outputs GigEthernet RJ45 port (Realtek RTL8153 USB3-to-Ethernet converter, 0x0bda:0x8153) Rear USB2.0 ports Rear USB3.0 port Front USB3.0 port Front headset jack Unsupported: Rear line-out jack (tried various layouts to no effect) Regarding VGA output: VGA worked OOB as single connected display, laptop booted lid closed. VGA worked as 2nd display only if connected at startup (it's quite usual for VGA not to work if connected after system has started). VGA worked alongside DP and/or HDMI but only in clone mode, not as 2nd or 3rd display. This is something apparently done at docking station level. Dell manual states it's the expected mode in 3 x displays setup but, in my case, this was experienced only with DP connected, laptop's lid closed. Front headset output: VGA output (lid closed): DP/HDMI output (lid closed, with or without VGA): Dual display, built-in LCD + VGA: Dual display, built-in LCD + DP or built-in LCD + HDMI:
  14. 4 points
    Beta1 installs in the exact same manner as High Sierra. The difference is that 10.14 requires Clover r4517 or higher to install successfully. https://github.com/Dids/clover-builder/releases So far, Ok on my Ivy Bridge/HD4000 Latitude E6230 with same EFI/bootpack as High Sierra 10.13 and Clover r4521. I made a quick and basic, not fully tuned, installation: Apple stated that Mojave will only support GPUs compatible with Metal so HD3000 and older 1st gen Intel HD graphics are effectively dropped (and there are no kexts for these). Support for Intel iGPUs now starts at Ivy Bridge HD4000. So, I won't be trying Mojave on my E6220 nor on my ancient D630 (support for nVidia Tesla architecture dropped too)... We'll see if this gets to evolve in the following beta versions but not much of a hope I guess. APFS conversion seems to be mandatory too. Despite my modification of the minstallconfig.xml file of the 1st reboot temporary installation in which I had set the ConvertToAPFS parameter to false, my target Mojave partition ended up converted! Not a problem in itself on my SSD (and APFS is reportedly Ok on mechanical HDD now) but that means a definitive goodbye to Chameleon/Enoch for the time being. Inescapable eventuality I guess... List of officially supported Mac models is as follows (as per /S/L/CoreServices/PlatformSupport.plist) MacPro6,1 iMac17,1 iMac16,2 iMac16,1 iMac15,1 iMac14,4 iMac14,3 iMac14,2 iMac14,1 iMac13,3 iMac13,2 iMac13,1 Macmini7,1 Macmini6,1 Macmini6,2 MacBookPro12,1 MacBookPro11,5 MacBookPro11,4 MacBookPro11,3 MacBookPro11,2 MacBookPro11,1 MacBookPro10,2 MacBookPro10,1 MacBookPro9,2 MacBookPro9,1 MacBook9,1 MacBook8,1 MacBookAir7,2 MacBookAir7,1 MacBookAir6,2 MacBookAir6,1 MacBookAir5,2 MacBookAir5,1
  15. 4 points
    Give this a try, replace into /EFI/Clover E5530_Mojave.zip
  16. 4 points
    Troubleshooting Clover rebooting early If you encounter any of the bullet below and rebooted, make sure that your 1 DIMM be on slot A. OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi Using reloc block: yes, hibernate wake: no +++++++++++++++++++++++++++++++++++++++++++++++ OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi Using reloc block: yes, hibernate wake: no Error allocating 0x#### pages at 0x####... alloc type 2 Error loading kernel cache (0x9) Boot failed, sleeping for 10 seconds before exiting... OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi Using reloc block: yes, hibernate wake: no Error allocating 0x#### pages at 0x####... alloc type 2 Could not allocate runtime area Boot failed, sleeping for 10 seconds before exiting... Core Storage 1) From terminal, enter diskutil list. Note the virtual drive in red. >diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *256.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage Macintosh SSD 63.5 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Macintosh SSD +63.1 GB disk1 Logical Volume on disk0s2 75DADC16-4B7F-4C7D-9660-10A1C2A9FC02 Unencrypted 2) From terminal, run diskutil cs revert /dev/disk1 3) Reboot with USB Installer and select the Installed drive 4) Continue with 3. POST-INSTALLATION Credits to peluko iMessage and FaceTime https://github.com/camielverdult/Ramblings-of-a-hackintosher-High-Sierra/blob/master/iMessage.md
  17. 3 points
    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
  18. 3 points
    Hi all, I am very excited to finally hack this world famous GPU mining motherboard and pleased to share with you all the clover bootpack. Specifications Asrock H81 BTC Pro Ver 2.0 4th Gen 3.5 GHz i3-4330 8 GB DDR3 1600 MHz Memory Intel Graphics HD 4600 HDMI output on 24-inch LED Monitor (1920 x 1080) Clover Bootpacks Catalina Support for Mac OS Catalina 10.15 Beta ((19A471t) (Clover 4945) CLOVER-10.15 Beta (19A471t).zip Mojave Support for Mac OS Majave 10.14.5 (Clover 4934): CLOVER-10.14.5.zip Support for Mac OS Majave 10.14.4 (Clover 4910): CLOVER 10.14.4.zip Support for Mac OS Mojave 10.14 Beta 4 18A326h (Clover 4586): CLOVER 10.14 Beta 4.zip Support for Mac OS Mojave 10.14 Beta 18A293U (Clover 4517): CLOVER 10.14 Beta.zip High Sierra Support for Mac OS High Sierra 10.13.6 (Clover 4635) CLOVER 10.13.6.zip Support for Mac OS High Sierra 10.13.4 (Clover 4428) CLOVER-V4.zip Support for Mac OS High Sierra 10.13.2 (Clover 4360) CLOVER-V3.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) CLOVER-V2.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) with Intel Graphics: CLOVER-Intel.zip Support for Mac OS High Sierra 10.13.1 (Clover v4293) with ATI Graphics: CLOVER-ATI.zip Notes on Mac OS Catalina 10.15 Beta (19A471t) (1) Everything works (2) Whatevergreen.kext requires graphics injection from Clover Notes on Mac OS Mojave 10.14.5 (1) Everything works (2) Mac OS 10.14.5 Update Installer now complaints "Cannot Find Installer Resources". A very crude workaround is to remove all other hard drives except for the Mac OS hard drive. Let me know if anyone find a solution to this without having to open the casing each time we want to update. Notes on Mac OS Mojave 10.14.4 (1) Everything works (2) Whatevergreen.kext now autodetects the graphics card. Make sure no graphics injection is done in Clover. Notes on Mac OS Mojave 10.14 Beta 4 18A326h (1) Everything works (2) Updated from Mac OS Majave 10.14 Beta 18A293U via Software Update in the System Preference. Notes on Mac OS Mojave 10.14 Beta 18A293U (1) Everything works including sleep. (2) Dedicated GPU Radeon Pro 560 not displaying on monitor. May need to wait for WhateverGreen.kext to be updated with support for this Mac OS version. Notes on Mac OS High Sierra 10.13.1 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) Added IntelGraphicsFixup.kext and Shiki.kext (4) Combined all ATI & Intel GPU configs & kexts into single bootpack for multi GPU support (5) For those that need to update 10.13 to 10.13.1, you will need to install the latest clover (version 4293 is the one I used). If there are error messages, you may try to remove EmuVariableUefi-64.efi from Clover EFI temporarily, clear NVRAM using sudo nvram -c in terminal, download the update directly from apple website and install. Notes on Mac OS High Sierra 10.13.2 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) For those updating from 10.13.1 to 10.13.2, you will need to install the latest clover and lilu including plugins (or download latest bootpack above) as well as download and install the update directly from apple website. Updating via App Store doesnt seem to work for me as I get the mkpg not found error message after reboot. Notes on Mac OS High Sierra 10.13.4 (1) Everything works including sleep. (2) Updated all kexts to latest versions (3) For those updating from an earlier version of 10.13 to 10.13.2, you will need to install the latest clover and lilu including plugins (or download latest bootpack above) as well as download and install the update directly from apple website. The OS X installer will reboot several times. Notes on Mac OS High Sierra 10.13.6 (1) Everything works including sleep. General Notes (1) The UEFI Bios does not detect Clover EFI natively. For first boot into Mac OS, you will need to boot Clover EFI using the Installer USB. In order to add Clover EFI into UEFI Bios, you will need to manually add it using the Clover UEFI shell using the following command:- (a) bcfg boot add 3 fsX:\EFI\BOOT\CLOVER\CLOVERX64.EFI "Clover" (You will need to replace X with the location of your Clover EFI partition. This is shown in the list when you first enter the UEFI shell) (b ) Lastly, do bcfg boot mv 3 0 to move the Clover boot order to the first. (2) I found that this motherboard is very compatible with Mac OS and patched DSDT / SSDT is not required. Notes on Mining (1) As all you miners know, this motherboard can take up to six (6) GPUs, I have yet to test additional GPU on the PCIEx1 slots. At the moment, the single GPU that i'm using is installed on the PCIEx16 slot. I will test it once I have opportunity to get additional GPU. In the mean time, for those miners who already have this motherboard in their rig and are already using Windows or Linux, Mac OS may be a good OS to try since some miners (like ethereum's ethminer) are also released for Darwin and both NVIDIA and ATI have provided drivers for their latest GPUs. This does open up a good possibily of using Mac OS for GPU mining! (2) I was able to use the dedicated RX560 GPU for both as primary display as well as for mining. However, it causes the system to slow down and created artifacts when I rebooted / shutdown. I was able to make the system more stable by using the integrated HD4600 GPU as primary display and the dedicated RX560 GPU for mining. In order to use both integrated GPU and dedicated GPU, both Intel and ATI need to be injected by Clover. In the case of ethereum miner, ethminer was able to recognized all GPU but I only selected the RX560 for mining. This made the system more stable. (3) [10-11-2017] I just installed a third old AMD Radeon HD 7750 GPU on the first PCIEx1 slot and am very happy to see that Mac OS recognized it straight away. In the case of ethereum miner, ethminer was able to recognized all GPU. Attached pictures below:- (4) One of my main concern is I am still not able to get HWMonitor to show GPU temperature which is very important to monitor the current health of the GPUs. We would not want the GPU to overheat due to unforeseen reasons. Let me know if you are able to solve this issue. (5) During my discussion with crew member Rhyker, we were discussing on ways to tune the GPU from within Mac OS. As you know, currently the manufacturer only provide tuning software for Windows and to a limited extend Linux. We were thinking of running Windows under a virtual machine to access the GPU tuner to tune the GPUs. However, based on my last attempt, accessing native GPU from a virtual machine is still not possible although there are projects that are attempting to do this. Let me know if this idea is workable. Let me know if the clover bootpack works for you. Credits goes to Jake Lo and Bronx Teck Cheers!
  19. 3 points
    Further to new information posted here, it appears that calling on AirportBrcmFixup with boot option brcmfx-driver=1 (to force BRCM4360 kext rather than BrcmNIC) allows to run Ok with some if not all those DW1820a cards that were reported to cause performance degradation and system freeze after a few minutes. Using that add-on kext + boot option allows me to use the CN-096JNT card without clogging the Hackintosh too a halt. I only experienced 2 x brief wireless disconnections during which system appeared to briefly freeze or, at least, the USB ports froze (hence mouse frozen) but all resumed after wireless automatically reconnected a few seconds later. I've updated the above posts accordingly.
  20. 3 points
    @EMlyDinEsH It's been more than 2 years since last update of the kext and about 1,5 year since last update of the first post. Can you finally release the source code, so someone could finally improve it?
  21. 3 points
    We are pleased to announce that we have expanded our social networks presence to Discord. Come over and chat with the crew and other members. Joins us there at: https://discord.gg/vVCpPWu
  22. 3 points
    Hi, Running OSXL have always been a mission we have been proud of - from the early days of D4x0 we could never have imagined that OSXL would grow to what it is today - a safe and nice place where hackintosh and macOS nerds can meet, have fun and play around. But running OSXL also have costs.. hosting.. the forum software.. mail service.. dns .. it cost.. and it never gets cheaper - so faar donations usually covers less than 5% of our operating cost. So.. what todo ? OSXL have always been against showing commercial ads our site - mostly because it slows down the site and ruin the user experience - personally .. i hate a slow website. So, we always explore new options (specially if its fun.. like the seedbox partnership) Anyway, today Brave browser launched - brave browser is (besides being a really nice web browser) - is a browser that allows its users to earn $BAT (a crypto currency) and donate those earned Bat(s) to websites they visit. We have enabled donations to the site - both automatic - but also by using the browsers build-in functionality. Wanna test brave browser? .. head over to: https://brave.com/osx926 (Btw, brave gives us 5 USD for each download, so you having fun testing a new browser, is also helping us and by that yourself) ... and may this be a hint of more fun stuff with cryptocurrencies coming your way //OSXLteam
  23. 3 points
    Hi all, We have successfully upgraded the forum to latest IPboard version 4.4.2. The current default theme is still buggy. We will upgrade the theme to the latest OSXL 2018 v1.07 later today. Thank you all for your patience. Best regards, Syonagar
  24. 3 points
    @Nancy10 Try my Mojave guide here Use this bootpack, files goes into /EFI/Clover replacing the default installed by Clover Kexts in ../kext/Other/CopyToLE should be copied to /Library/Extensions after installation as part of post install. Good luck 7480_HD620.zip
  25. 3 points
    DisableTurboBoostBatery.kext doesn't work with VirtualSMC.kext and SMCBatteryManager.kext. Problem is here: void DisableTurboBoostBattery::actOnChangedPowerState() { if (pPowerSource && isOnAC != pPowerSource->externalChargeCapable() && pPowerSource->batteryInstalled()) { if ((isOnAC = pPowerSource->externalChargeCapable())) enable_tb(); else disable_tb(); } } Reason is simple - externalChargeCapable returns different values with VirtualSMC.kext and SMCBatteryManager.kext than with FakeSMC.kext and ACPIBatteryManager.kext. ExternalChargeCapable property has same value as ExternalConnected in case of FakeSMC.kext and ACPIBatteryManager.kext. On battery both values are false, on charger both values are true. With VirtualSMC.kext and SMCBatteryManager.kext only ExternalConnected property change value. It's true on charger and false on battery. ExternalChargeCapable is always true. This is the reason why disable_tb() is never called with VirtualSMC.kext and SMCBatteryManager.kext and Turbo Boost remains active. Fix should be simple as this: void DisableTurboBoostBattery::actOnChangedPowerState() { if (pPowerSource && isOnAC != pPowerSource->externalConnected() && pPowerSource->batteryInstalled()) { if ((isOnAC = pPowerSource->externalConnected())) enable_tb(); else disable_tb(); } } This should work in both usage cases - VirtualSMC.kext with SMCBatteryManager.kext and FakeSMC.kext with ACPIBatteryManager.kext. VirtualSMC implementation of ExternalChargeCapable looks proper based on documentation: ExternalConnected Type: bool IORegistry Key: kIOPMPSExternalConnectedKey True if computer is drawing external power ExternalChargeCapable Type: bool IORegistry Key: kIOPMPSExternalChargeCapableKey True if external power is capable of charging internal battery
  26. 3 points
    - First create 2 partitions Extended Journal when installing OS X. Make sure to jot down the size so you won't wipe out the wrong partition when you install Windows on it later. Hint: don't make both the same size - Use Disk Utility to prepare a Mac OS X Extended partitions (don’t ever use Fat32, Disk Utility will mess up your drive) - After installing OS X, everything all setup. Then install Windows - Create a FAT32 usb drive, extract Windows 10 64-bit iso there (done on a Windows system) - Boot to Win10 usb drive, select custom install, locate the partition that is not OS X, delete it. Then select it (unallocated space) format it to NTFS, install Windows there. - Windows will automatically boots back to Windows. Install all drivers...etc. - Now to fix the boot option - Go to BIOS, create boot option. Browse to /EFI/Clover/Cloverx64.efi, give it a Name. Now move the Clover boot entry to top. - Save and reboot. Now you'll see the option to boot Windows or OS X from the Clover GUI. To fix the time in Windows, launch regedit navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] create a DWORD (32 bit) value, name it RealTimeIsUniversal. Set the value to 1. Exit Boot to OSX, then reboot to Windows. You should see time is correctly sync'd up.
  27. 3 points
    Just another 1-2 weeks, and you will have updates from me sure. I am working on it as I have some issues with my dev environment right now to finish. Thanks for the patience.
  28. 3 points
  29. 3 points
    Sierra Guide See here for install guide, just replace with Sierra bootpack. E7x70_Sierra.zip - See Update files below Known Issue & Workaround: HDMI-Output works but if connect HDMI-Cable the local Display goes off and never recovers. I had tried different configurations but none panned out. Here's a workaround: Close the LID until you see the HDMI display becomes the primary display, then open the LID. It'll switch LCD as primary and HDMI as secondary. NOTE: Workaround is only needed on clean boot, no issue if system has gone through a sleep/wake cycle Update: Fixed it by modifying EDID with this kext, but not work for Mojave. Post Install: Enable Brightness Control and Trackstick Scrolling Trackstick Scrolling Download and install Smartscroll for trackstick scrolling Touchpad - 2 fingers scrolling, 2 finger tab for right click, tap and drag Brightness Control Download and Install Karabiner-Elements Launch Karabiner-Elements Copy karabiner.json to ~/.config/Karabiner karabiner.json.zip or copy the settings according to diagram below Now use F11 & F12 for Brightness, use F1, F2, & F3 for Volumes Control
  30. 3 points
    Updates El Capitan 10.11.1 STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: None El Capitan 10.11.2 (15C50) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: None El Capitan 10.11.3 (15D21) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: None El Capitan 10.11.4 (15E65) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Upgrade to latest Clover prior to upgrade just in case New Issues: 1) KP on some systems with VoodooPS2Controller (Alps touchpad). Reboot with USB installer, select HD/SSD to boot. Remove /EFI/Clover/Kexts/Other/VoodooPS2Controller and replace it with Dr. Hurt's version R6B6 2) DummyHDA with Clover-on-the-fly patch stopped working Install new kexts for according to your CodecID Latitude Exx20 AppleHDAIDT.kext.zip Latitude Exx30 AppleHDA_IDT.kext.zip Latitude E7x40, E6540, E5440 Precision M4800, M6800 AppleHDA_ALC292.kext.zip Latitude E7x70, E7x50, E5450 Precision 7510 AppleHDA_ALC293.kext.zip Inspiron 3542, 5548, 5558, 5458 Latitude 3340, 3550 AppleHDA_ALC255.kext.zip Inspiron 5537 Latitude 3440, 3540 AppleHDA_ALC283.kext.zip Optiplex 9020 AppleHDA_ALC280.kext.zip Lenovo Z51-70 AppleHDA_ALC236.kext.zip * If your dummyHDA is not listed here and was working prior to 10.11.4, see here how to update it El Capitan 10.11.5 (15F34) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Same fix applied from 10.11.4 if you're upgrading from 10.11.3 and below or new install using provided bootpacks El Capitan 10.11.6 (15G31) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Same fix applied from 10.11.4 if you're upgrading from 10.11.3 and below or new install using provided bootpacks
  31. 3 points
    Search for PW934, that should get you the same card. For the card you have which is DW1520 to work, you can change your SMBIOS to MBA5,1 or MBA5,2, but AirDrop might not work as it doesn't work for me.
  32. 2 points
    Questions still arise about this matter so here's a recap of what caching kexts and injecting kexts (through Clover) mean: 1/ Caching kexts: Kexts placed in /L/E and/or /S/L/E are cached in the kernel cache (or prelinked kernel) which aims to accelerate boot time. Cached kexts are subject to signature by Apple and must be set with the correct permissions (Cf. our FAQ topics on permissions). Cached kexts will be shown/listed/registered in System Info (ex-SysProfiler) -> Software -> Extensions. Caching kexts is the recommended scheme for all add-on kexts. /S/L/E is the location for Apple's own (i.e. vanilla) kexts. Ideally, this should be left untouched by Hackintoshers unless for very specific and rare reasons (eg: patched AppleHDA). /L/E is the location for 3rd party/add-on kexts. This is where all kexts we use for our Hackintoshes should go. Add-on kexts should only be placed in either folder, never in both. 2/ Injecting kexts through Clover: Injected kexts are not cached and will not be shown/listed/registered in System Info (ex-SysProfiler) -> Software -> Extensions. Injecting kexts results in a slightly slower boot than caching kexts (though many would arguably say it's hardly noticeable). Kexts injection operates according to Clover settings on the matter: If kext injection is set to Yes, kexts placed in E/C/K/O (or E/C/k/10.xx) will be injected. If kext injection is set to No, no injection takes place; obviously... If kext injection is set to Detect, kext injection operates according to the presence of FakeSMC in the kext cache (the kext having been poperly installed in /L/E or /S/L/E). If present, no injection takes place, if absent, kext injection is performed. If kext injection is used, make sure the kexts aren't cached at the same time. Clover's E/C/k/O and E/C/k/10.xx are the locations for kexts that Clover injects at boot time: E/C/k/O is used to inject kexts regardless of the OS X/macOS version. E/C/k/10.xx are used to inject kexts for the given OS X/macOS version and therefore allow different kexts to be injected for different versions. Kext injection is very useful for recovery purposes (like booting without cache which ignores /L/E) or when testing kexts for instance; if a newly injected kexts causes issues (like a KP), it's very easy to remove/bypass it. On the other hand, kext injection is known to occasionally cause problem because it's not the natural way in which kexts should be loaded. Kext injection is basically a form of forced loading and, sometimes (though rare these days), it does not work. My own recommendation is to experiment with kexts through injection and, once kexts are validated, to cache them from /L/E. Google for this kext injection matter or consult the Clover wiki/InsanelyMac forum. It's all quite widely documented.
  33. 2 points
    It's a high-end GCN4.0 card, probably in the USD $150-$200 price range these days. Good for Mojave too. It really depends on what you want to do with it. For a fraction of the price (say USD $50), you can probably get a Kepler GT730 which will roughly provide similar performance as the GTX460 and is Mojave compatible too. Higher Kepler cards will do great too. I would have loved to recommended Pascal cards (I have a low-end GT1030 in my Vostro200 for High Sierra) but these are not Mojave compatible...
  34. 2 points
    what herve said. the kext is Dr.Hurts hard work not mine. i had no involvement in it. i did not have anything to do with writing the code for the kext. i just compiled Dr.Hurts last code he left us with so that we could try it.
  35. 2 points
    @MrJonesIII Download AppleALC.kext + Lilu.kext and place into /EFI/Clover/kexts/Other In Config file, change Devices/Audio, change Inject from 1 to 5, under ACPI, enable FixMutex
  36. 2 points
    I made that update Hervé after @Virtus confirmed it's working. I noticed the other Lenovo also has the same ID, so I added them.
  37. 2 points
    That's normal in Hackintosh for those brief seconds. Lilu.kext + Whatevergreen will remove some but not 100%. If you boot with verbose mode, you won't see it, so take your pick.
  38. 2 points
    El Capitan Guide Specifications: Processor : Intel® Core i5-6300U / i7-6600U Processor Graphics Processor(GPU) : Intel® Integrated HD Graphics 520 Chipset : 6th Generation Intel®Core Storage : Samsung PM851 256GB M.2 Form factor Sata-SSD RAM : 16GB DDR4 SDRAM 2133 MHz; 2 slots supporting up to 16GB Wifi : Intel Wireless Gigabit Ethernet 802.11AC (M.2, 8260AC), Bluetooth 4.1 LAN : Intel I219-LM PCI-E Gigabit Ethernet Adapter Audio : Realtek® High Definition Audio ALC293 (ALC3235) USB 3.0 : Intel USB 3.0/3.1 xHCI Controller Touchpad : Alps Multi-touch Touchpad v7 Hardware Webcam : USB3.0 UVC HD WebCam Card reader : SD 4.0 Memory Card Reader Monitor : (14) FHD (1920x1080) Anti Glare (16:9) WLED, 300 nits, Magnesium Alloy LCD back Battery : 55 Wh ExpressCharge Capable (4-cell) Lithium-Ion Interface : 1 x Microphone/Headphone Combo jack 1 x Mini DisplayPort for external monitor 3 x USB 3.0 port(s) (one with PowerShare) 1 x RJ45 LAN Jack for LAN insert 1 x HDMI Working: Graphics with Acceleration Audio with patched AppleHDA Bluetooth /Wireless (Replaced with DW1560 / DW1830) HDMI Video / Audio mini DisplayPort / Audio LAN USB3.0 Webcam Battery Fn Hotkeys (Brightness & Audio control) Alps Touchpad / Trackstick Sleep, Processor P&C-States with Native power management Not working: Finder Sensor, smart card reader if you have one SD Card reader DisplayPort on Port Replicator - no DP audio Work in Progress: HDMI Audio (no support yet) HDMI Audio Supported, updated files in the Sierra guide below Slow to boot/Restart/Shutdown Better when dual booting with Win10/not sure why Prerequisite: Set DVMT to 96MB (0x3) Source = FireWolf™s guide Steps to change the DVMT value (Done on Windows or WinPE) 1) Universal BIOS Backup ToolKit 2.0.exe - to backup the BIOS (DellInc.-1.5.3.rom) At time of writing - BIOS version 1.5.3 2) UEFITool.exe to find the module labeled Setup and extract the PE32 image section (setup.bin) Update: For Dell Only: Search with this GUID then extracting the PE32 body under it would be faster /easier than finding the module per guide 899407d7-99fe-43d8-9a21-79ec328cac21 3) Universal IFR Extractor.exe to extract setup.bin to a readable text file 4) Use notepad to search for DVMT in the text file, 2 were found at 0x432 and 0x433 Both with value of 0x1 but only 0x432 needs to be set to 0x3 5) Format a USB drive to fat32 and create a folder name EFI (SD Card works too) 6) Download the EFI Shell and extract the Boot folder into the newly created EFI folder i.e.. /EFI/Boot/bootx64.efi 7) Boot system with the USB and select UEFI Boot At the grub prompt, enter these commands, hit enter after each command, then exit and reboot setup_var 0x432 0x3 To verify, just enter setup_var 0x432 and hit enter, the value will be listed Note: Settings will retain after BIOS update but will reset if you select "Restore Settings" in BIOS!!! /!\ New Development: If you don't want to mod the BIOS as it might be difficult for some models, you could skip this step by adding 2 new kexts to /EFI/Clover/kexts/Other Lilu.kext & Whatevergreen BIOS Settings: Set to "Load Default", Apply, then set the following: TPM = Disabled Secure Boot = Disabled UEFI = Enabled SATA Operation = AHCI Wake on Lan /WLan = Disabled Enable Legacy Option ROMs = Disabled Installation: See here install guide, use below bootpack E7x70.zip Note: Must be OS X 10.11.4 and newer for Skylake support Post Install: Enable Brightness Control and Trackstick Scrolling Trackstick Scrolling Download and Install Karabiner Launch Karabiner/Preferences/Change key/Point Devices/CursorMove to ScrollWheel Enable MiddleClick+CursorMove to Scrollwheel Brightness Control Launch Karabiner/Preferences/Misc & Uninstall Under Custom Setting, click Open private.xml Replace file with the attached -> private.xml.zip Go back to Change Key Tab and select 'Reload XML' The new custom file will show on the very top call 'Remap Brightness Key' & 'Remap Volumes Key' Place the check marks there. Now use F11 & F12 for Brightness, use F1, F2, & F3 for Volumes Control (Keyboards with same/similar layout will work with custom xml above too) Note1: Personally use SmartScroll for Trackstick scrolling with Inertia. Don't really use Touchpad, 2 fingers scrolling and tap and drag does work. Note2: Please use this beta version of ssdPRGen.sh generate SSDT.aml for Skylake system Note3: If you're installing Sierra, there's a known artifact issue on the upper left corner! Update: Fix can be found here Credits: FireWolf, Joe82, EmlyDinEsh, Bronxteck, Hervé, Rehabman, Piker-Alpha, Sontrg, toleda, Dr. Hurt, Clover Team, ...everyone involved with getting Skylake supported
  39. 2 points
    Try adding this to /EFI/Clover/kexts/Other
  40. 2 points
    You probably didn't have the DVMT Pre-allocation patch. You need to add it to the properties section under Devices, can't use KexttoPatch for FB in Mojave on Skylake and above See here for more info https://www.insanelymac.com/forum/topic/335018-intel-fb-patcher-v164/
  41. 2 points
    Yes, replace with this one if it's not working Use layout-id 1
  42. 2 points
    Ok, so it's a Haswell laptop with the following specs: Series 8 chipset i3-4005U @1.70GHz (no Turbo boost) 8GB RAM Intel HD 4400 graphics + Nvidia GeForce 820M 14.0" LCD 1366x768 Realtek RTL8106/RTL8111 Gigabit Ethernet DW1705 802.11n + BT4.0 wireless card (compatible but poorly supported; better to replace) Realtek ALC255 ? (ALC3223) audio USB 2.0 + USB3 ports HD Webcam Synaptics Touchpad If you have a SD card reader, it should be: Realtek RTS5170 Card Reader That laptop is perfectly able to run current macOS High Sierra and will support Mojave. Optimus technology being unsupported in Hackintoshes, you won't be able to have dual graphics, only the HD4400 (fully supported) or, possibly, the nVidia (if supported). We can look at extracting the ACPI tables (DSDT/SSDT) from your BIOS for eventual patching.
  43. 2 points
    Welcome @Badruzeus. N00b you?? hahaha you're the master bro. Enjoy your stay here, I have sure that you'll like to be here too.
  44. 2 points
    Just an update to share as I promised few days ago. I am still working on it, and might need an extra week or 2 to share some news as i have issues with my development environment. Thanks
  45. 2 points
  46. 2 points
    @vinh1978, whenever you try something new suggested by some member and yet are unable to fix the problem then when you report back (after trying) you are expected to provide new problem reporting files (it is written clearly in FAQ thread for gen_debug). Why submit new files everytime you try changing something? Coz, if you change the files many other things also change and they help keep track of how close we are from fixing the problem. Without new files after change, it is like shooting in the darkness and hoping to hit the bull's eye. Hope you understand. Regards
  47. 2 points
    High Sierra High Sierra Guide Bootpacks E7470_1.17.5_HS.zip E7470_1.17.5_HS-alternate.zip E7270_1.17.5_HS.zip E7270_1.19.4_HS.zip Note: 1) 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 UPDATES High Sierra 10.13.1 (17B48) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update High Sierra 10.13.2 (17C88) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Install latest Lilu.kext v1.2.1 High Sierra 10.13.3 (17D47) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Install latest Lilu.kext v1.2.1 High Sierra 10.13.4 (17E199) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Install latest Lilu.kext v1.2.1 High Sierra 10.13.5 (17F77) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Install latest Clover prior to update Install latest Lilu.kext v1.2.3 High Sierra 10.13.6 (17G65) STATUS: GOOD UPDATE METHOD: APP STORE/SYSTEM UPDATE MODIFICATIONS NEEDED: Update USB port limit patch
  48. 2 points
    It's required after any kext addition, removal or modification, whether in /S/L/E or in /L/E. To repair permissions, type the following Terminal commands: sudo chmod -Rf 755 /S*/L*/E* sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo chown -Rf 0:0 /L*/E* ` To rebuild kextcache and prelinked kernel, type the following Terminal command: sudo touch -f /S*/L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / ` Sometimes, the system returns an error message about not being able to modify/rebuild the cache and/or the prelinked kernel. In this case, the existing cache and prelinked kernel can be deleted using the following Terminal commands: sudo rm -Rf /S*/L*/PrelinkedKernels sudo rm -Rf /S*/L*/Caches/com.apple.kext.caches The cache and prelinked kernel can then be rebuilt using the above touch and kextcache commands.
  49. 2 points
    Chameleon Guide Target OS X release: Yosemite 10.10.2 The specs: BIOS A13 (needs HDD set to AHCI mode) Intel QM87 Express chipset Intel i7-4800MQ 2.69GHz quad-core Haswell-MB CPU -> needs Haswell-patched kernels integrated Intel HD4600 GPU (PCI ven id 0x8086, dev id 0x0416) discrete Nvidia Quadro K3100M GPU (PCI ven id 0x10de, dev id 0x11b6)17" 1920x1080 WideScreen LCD 16GB DDR3L-1600 RAM Intel i217-LM Gigabit Ethernet (PCI ven id 0x8086, dev id 0x153a) Realtek ALC3226 High Def audio (PCI ven id 0x8086, dev id 0x8c20) Intel wireless card 7260 (PCI ven id 0x8086, dev id 0x08b1 - unsupported) + Bluetooth 4.0 (PCI ven id 0x8087, dev id 0x07dc) Sonix Technology integrated HD webcam (USB internal, PCI ven id 0x0c45, dev id 0x64d2) O2 Micro SD card reader (PCI ven id 0x1217, dev id 0x8520) CD/DVD drive 1 x headset port 1 x mic port 1 x eSata/USB 2.0 port 4 x USB 3.0 1 x VGA 1 x HDMI 1 x DisplayPort 1 x 34mm ExpressCard BIOS Settings: Set BIOS to default. Then set SATA Operations to AHCI. Disable "Enable Switchable Graphics" Working: Full QE/CI with Nvidia Quadro K3100M (LVDS display) Wireless (Replaced with supported device) HDMI Video/ DP Video HDMI Audio with HDMIAudio.kext v1.0 ( Stop working after sleep and will require a reboot to work again) Internal Speaker/Headphone/Mic USB 3.0/USB 2.0/eSata Ports SD Card Reader DVD Player Webcam LAN WIP: HDMI Audio Fixed Sleep/Wake (not with LID close). Wake to blank screen unless AC is connected before wake. Not Working: ExpressCard SmartCard Reader Step 1: Prepare Bootable USB Drive Follow step #2 of guide here to create the Yosemite USB Installer Note: Add the patched Haswell Kernel (10.10.2) Step 2: Install OS X Yosemite Follow steps #3 from same guide above Note: Boot from the eSata/USB 2.0 combo port on the back Step 3: Post-Installation Follow steps #4 from guide above Note: Need to copy patched Haswell Kernel from Installer to HDD/SSD M6800.zip
This leaderboard is set to Amsterdam/GMT+02:00
×
×
  • Create New...