Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 07/01/21 in all areas

  1. Hello. I have found a solution to your mentioned issue. My Precision 7530, which also has a compatible dGPU, has non-working brightness after the 11.3+ upgrade. And yes, you are right -- the cause of the problem is because 11.3+ Apple decided to change its driver stack somehow to default the brightness control to the dGPU, which does not have internal screens. So either we use solely iGPU, or we route the internal display to the dGPU and turn off the iGPU which is power consuming. Someone on reddit, however, was smart enough to find a solution right here. In this solution, the dGPU brightness control were given back to the iGPU via a smart patch. Hope that helps! https://www.reddit.com/r/hackintosh/comments/nzsyqo/inspiron_15_r_se_7520_big_sur_115_beta_2_success/?ref=share&ref_source=embed&utm_content=title&utm_medium=post_embed&utm_name=d2f878a2486d45fa91e92a051f573f6b&utm_source=embedly&utm_term=nzsyqo
    2 points
  2. 4th beta released July 27th, 2021. Build 21A5294g. Ok on my Latitude E7270 (Clover r5133) and Satellite Pro R50-B (OC 0.7.0).
    1 point
  3. Ioreg my EFI I need to do tests, let's start to fine-tune the basic EFI, you'll see that every problem is solved I am a self-taught user, I need time and tests to be able to solve the various problems but everything works out, it takes patience and time
    1 point
  4. Please consult our FAQ section re: SIP. There's a dedicated thread to describe it and the values that may be used. By all means, do try and inject CodecCommander from that folder, but if it does not load, you'll have to cache it from /L/E; this will have to be done manually through Terminal and after disabling Gatekeeper: sudo spctl --master-enable Reboot then copy the kext to /L/E sudo cp -R <path>/CodecCommander.kext /L*/E*/ Authorise the kext through Security & Privacy PrefPane and reboot again. You may then disable Gatekeeper again if you wish: sudo spctl --master-disable
    1 point
  5. I asked for EFI + ioreg, to start Win from OC you need Darwin fix in ACPI so you need everything I asked for.
    1 point
  6. You'll need to upgrade Clover to the latest and there are big changes since it added OpenCore drivers to support Big Sur.
    1 point
  7. Please download Offline macOS Installer from Olarila, and replace with my EFI
    1 point
  8. what happens if you close the screen and open it again after it blacks out on the main screen? if you shine light on the screen do you still have images showing but with no backlight?
    1 point
  9. Compress the video and attach it here Does your system have a discrete graphics card? if so, it might need to be disabled via SSDT patching. Post an IOReg file for better troubleshooting using IORegistryExplore.app v2.1, not 3.0+
    1 point
  10. Thank you very much, @quynkk5! I am attaching the DSDT dumped from my Latitude E7490 which is the one on which I am trying to install Big Sur right now. Do you think there is something wrong with the SSDTs and you are going to create and send me the correct ones? I am planning on hackintoshing a couple more computers, so if you could help me understand how to prepare correctly the SSDTs, I would much appreciate it. In case it is too complex for a proper explanation or a couple of links to read and learn, would you please also help me with the Latitude 3390 I'll try to hackintosh right after the 7490? I am attaching the dumped DSDT of the 3390 too. Once again thank you very much! DSDTs Latitude E7490 and 3390.zip
    1 point
  11. Dell Latitude E5550: Intel Broadwell i3-5010U @2.10GHz Intel HD5500 graphics 8GB DDR3L RAM Intel I218V LAN Intel AC 7265 Wireless OpenCore 0.7.1 and Clover r5138 with up-to-date kexts at time of writing. https://github.com/quynkk5/E5550-macOS/releases/tag/v1.0 Working: Full graphics acceleration HDMI output Wifi and Bluetooth LAN Audio (speakers, headphones & HDMI) Sleep with lid off and  > Sleep Brightness control Multimedia button Keyboard and touchpad (ALPS) SD card reader USB2.0 & USB3.0 ports (USB remapping required macOS installation because my laptop doesn't have camera so I've not remapped yet) Battery Indicator and charger Not working: VGA output (unsupported)
    1 point
  12. Welcome to OSXL!!!
    1 point
  13. No need for the AppleCpuPmCfgLock kernel patch; that for 2nd gen Sandy Bridge and 3rd gen Ivy Bridge platforms. You opted for SSDT-EC table instead of SSDT-EC-USBX table as recommended in Dortania's documentation. Dortania does state that SSDT-EC is for Broadwell and older systems when SSDT-EC-USBX is for Skylake and later. Being a Coffee Lake platform, your laptop falls into the 2nd category. UHD630 iGPU of i7-9850H carries native id 0x3E9B. As such, no need to inject that exact same device-id through OpenCore. It does no harm of course. MacBookPro16,4 may not be the correct or best SMBIOS to use though MBP16,1/MBP16,4 are 9th gen Coffee Lake with UHD 630 graphics. You could try MacBookPro15,1 or MacBookPro15,3 instead. Absolutely no need for the -no_compat_check boot arg in NVRAM. That's for systems using an officially unsupported SMBIOS in a given macOS version. Not the case here, whether you use MBP15,x or MBP16,x SMBIOS. The boot-arg will do no harm but will block all macOS update offers. If you keep getting back screen, do experiment with other CFL mobile framebuffer layouts such as those listed in the https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md. You may also refer to the suggestions provided in Clover Configurator app. I've never Hackintoshed any Coffee Lake laptop so I don't know how accurate these are but 2018 8th gen CFL MBP15,1 certainly uses layout 0x3E0B0006: You've linked to the Dortania documentation but it appears you did not followed it thoroughly. I suggest you do so using the section written for the Coffee Lake laptops: https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/coffee-lake.html
    1 point
  14. 5GHz networks should normally be visible with a DW1820A but you may have an issue related to Country Code or something like that. Check what you card shows in SysInfo->Network->Wifi in terms of Locale and Country Code. Then check your box/router settings for 5GHz networks/SSIDs. You may need to use AirPortBrcmFixup and one of its parameters as indicated in our BCM4350 guide. But, what I don't understand the most is that you do not inject anything for your DW1820A given that the entry for it is commented out in your OC config... What's the reason for that?
    1 point
  15. try this config please post new IOReg file using IORegistryExplorer.app v2.1, not 3.0+ config.plist.zip
    1 point
  16. 2nd beta available. Build 21A5268h. A few little improvements like the return of GPU info in About This Mac or the refresh button in Safari. Bluetooth still buggy, especially after wake. We'll see what other improvements and new bugs it brings... Straight & easy update with Clover r5133 on my Skylake/HD520 Latitude E7270. Much more more complicated affair with OpenCore v0.7.0 on my Haswell/HD4400 Satellite Pro R50-B. From the 3rd reboot of the temp installation partition, laptop goes into a boot loop. On rebooting the original Monterey partition, system went through "xx minutes remaining", hinting the update was actually going through but, on reaching the Monterey desktop, back to beta1.
    1 point
  17. @augustopaulo No issue with my E7470 running Monterey with the files you mentioned. Looking closely at your IOReg file review that you have an AMD GPU. You'll need this disable. Add the attach SSDT to ACPI folder and in the Config file under ACPI/Add Reboot and it should fix your issue SSDT-DGPU.aml.zip
    1 point
  18. I'm tempted to say you're looking at brightness and brightness control the wrong way. Look up existing guides & threads related to the Latitude Exx70 models. Keep things simple and focused on the Latitude families. NB: As per our stated rules, which I invite to read if you've not done it yet, no links to forbidden sites and easy on the quoting!
    1 point
  19. Monterey usually works with the exact same settings as with Big Sur. On the various laptops I installed it on (Latitude E6230/E7270, Satellite Pro R50-B): Screen brightness works the same in Monterey as it does in Big Sur (brightness level should be retained if you have a fully working NVRAM) Brightness control works the same in Monterey as it does in Big Sur Sleep & wake work the same in Monterey as they does in Big Sur DW1820A works the same in Monterey as it does in Big Sur (Tosh R50B & Lat E7270) Touchscren stopped working in Big Sur on my Skylake E7270 whilst it worked OOB in Mojave and Catalina; such Toushcreens are USB-based and fully detected/reported in SysInfo->USB As for TouchPad, it really depends on the model fitted to your laptop but I2C models are limited
    1 point
  20. All, I see this question raised a lot in various OSXL forums, so I thought I would add my experience. I just successfully set up my Latitude E7270 to dual boot Windows 10 and Big Sur partitions on the same drive under OpenCore 0.68. The original guide is from a post on reddit (Credit: u/junkieslip_6). Then, there is a very good you tube video that walks you through the steps from that guide. Two important notes: -It took me a few tries in Disk Utility to make sure I had a separate NTFS partition for Windows, and not another Volume in the same APFS container for MacOS -I needed to make my Windows 10 install USB using Rufus on a Windows 10 machine (neither Win 7 nor Linux/gparted worked for me) ...well three important notes: -there is a typo in the text instructions under the video on the you tube pages: "partition efi size=100" should be "create partition efi size=100" Hope this helps-
    1 point
  21. It's still a recurring topic on the fourm, understandably so, so I thought I'd write a little recap about it. Brightness keys patch has been subject to discussion and queries for many years and much has been written on the matter. Among others, Rehabman did some extensive research work on this several years go and provided substantial information and debugging material to work out fixes. The brightness keys patch for many -if not most- Dell laptops since, at least, Ivy Bridge generations can be applied through DSDT patching or through pure SSDT patching. A DSDT patch for E6230 was 1st mentioned at OSXL by @jpz4085 in our old Dr Hurt's VoodooPS2Controller kext thread; the work derived from Rehabman's research and publications. I found that the patch was fully reusable on other models of the E Series and I fully detailed the DSDT patch code in my E6230, E7250 or 7490 guides. Unless I'm mistaken (happy to be corrected if required), the SSDT patch was derived from the DSDT patch by @Jake Lo and provided in various threads of his that I can't specifically remember. To successfully apply the required SSDT patch, given that a little tuning may be required depending on the target platform, it's most useful to understand that brightness keys of Dell laptops usually operate at ACPI level and according to the following reversed engineered process: brightness keys operation is handled through BRT6 method. BRT6 method is attached to IGPU device but there can be a 2nd BRT6 method under GFX0 (or whatever other name) if the laptop is fitted with a dGPU too. BRT6 is usually called from EV5 method. EV5 method is usually called from SMEE method on the condition that a call to OSID method returns a value greater or equal to 32 (0x20). OSID method returns the value set in ACOS parameter (integer). ACOS is set to different values according to the nature of the Operating System. It is set to 32 (0x20) for Win Vista, 64 (0x40) for Linux or 128 (0x80) for Win7/8/8.1. Value is under 32 for Windows versions older than Vista. I'll pass on the upstream process _Q66->NEVT->SMIE->SMEE which is of no specific interest in the context of this brightness keys patch description. Sample methods grabbed from Latitude E7270's extracted DSDT: BRT6 Method Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) // 1st arg=1 for brightness increase { Notify (LCD, 0x86) } If (And (Arg0, 0x02)) // 1st arg=2 for brigthness decrease { Notify (LCD, 0x87) } } EV5 method Method (EV5, 2, NotSerialized) { \_SB.PCI0.IGPU.BRT6 (Arg0, Arg1) // Call to BRT6 with 2 arguments } SME method Method (SMEE, 1, NotSerialized) { Store (Arg0, Local0) Store (GENS (0x11, Zero, Zero), Local0) If (LGreaterEqual (\_SB.OSID (), 0x20)) // If OSID returns a value >= 32 { If (And (Local0, 0x04)) { EV5 (One, Zero) // Call to EV5 with 1st arg set to 1 } If (And (Local0, 0x02)) { EV5 (0x02, Zero) // Call to EV5 with 1st arg set to 2 } } If (And (Local0, 0x08)) { Store (GENS (0x1D, Zero, Zero), Local0) EV17 (Local0, Zero) } } OSID method Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) // Check if ACOS lower or equal to 0 { Store (One, ACOS) // Initialises ACOS to 1 Store (Zero, ACSE) If (CondRefOf (\_OSI, Local0)) // Engages in tests according to OS identification { If (_OSI (WXP)) { Store (0x10, ACOS) // Sets ACOS to 16 if Win XP } If (_OSI (WLG)) { Store (0x20, ACOS) // Sets ACOS to 32 if Win Vista } If (_OSI (WIN7)) { Store (0x80, ACOS) // Sets ACOS to 128 if Win7 } If (_OSI (WIN8)) { Store (0x80, ACOS) // Sets ACOS to 128 if Win8 Store (One, ACSE) } If (_OSI (WN81)) { Store (0x80, ACOS) // Sets ACOS to 128 if Win8.1 Store (0x02, ACSE) } If (_OSI (LINX)) { Store (0x40, ACOS) // Sets ACOS to 64 if Linux } } Else { If (STRE (_OS, W98S)) { Store (0x02, ACOS) // Sets ACOS to 2 if Win98 } If (STRE (_OS, WINM)) { Store (0x04, ACOS) // Sets ACOS to 4 if Win ME } If (STRE (_OS, NT5S)) { Store (0x08, ACOS) // Sets ACOS to 8 if Win NT } } } Return (ACOS) // Value returned by OSID method } It should also be noted that, brightness keys patching only appears to work with VoodooPS2Controller kext, not with ApplePS2Controller (at least for me and the platforms I tested). To enable brightness control through the brightness keys of Dell laptops, 2 x things must be done: ensure that OSID returns a value greater or equal to 32 (0x20) for "Darwin" OS (i.e. OS X/macOS) ensure the correct key stroke codes are captured in BRT6 method (by default, BRT6 usually only operates for key stroke codes 0x86 and 0x87) 1) DSDT patch method: This is most probably the simplest of the 2 x methods because it involves very basic and very easy patching of the DSDT: 1st part of the patch is to insert a reference to Darwin OS as one of the tests used to set ACOS parameter to, at least, 32 (0x20). 2nd part of the patch is to insert the relevant key stroke codes in BRT6 method as keyboard event notifications. One code for brightness increase and another one for brightness decrease. Rehabman's ACPI debugging tools have allowed to identify various key codes, depending on laptops: brightness increase: key codes 0x10, 0x206, 0x286, 0x366, 0x0406 brightness decrease: key codes 0x20, 0x205, 0x285, 0x365, 0x0405 I have found that key codes 0x0365 and 0x0366 applied to the Latitude E6x20, E6x30, E6x40, E7x50, E7x70 or other 7x90. @Jake Lo found that codes 0x0405 and 0x0406 applied to other models such as the Precision 5510 or 7510. The DSDT patch can then be applied in the line of the following code: OSID method Before: Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) { [...] If (CondRefOf (\_OSI, Local0)) { [...] If (_OSI (WIN7)) { Store (0x80, ACOS) } [...] } [...] } Return (ACOS) } After: Method (OSID, 0, NotSerialized) { If (LEqual (ACOS, Zero)) { [...] If (CondRefOf (\_OSI, Local0)) { [...] If (LOr (_OSI ("Darwin"), _OSI (WIN7))) // Changes test from Win7-only to Darwin or Win7 { Store (0x80, ACOS) // Thereby setting ACOS to 128 for Darwin, i.e. OS X/macOS } [...] } [...] } Return (ACOS) } BRT6 method Before: Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) } } After: Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x0366) // Add capture of brightness-up key stroke } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x0365) // Add capture of brightness-down key stroke } } and that's it! 2) SSDT patch method: Over the last few years, DSDT patching has gradually and increasingly become less fashionable within the Hackintosh community in favour of alternatives in the form of dedicated and specific SSDTs, something which is considered far more efficient because: it's based on on-the-fly ACPI objects renaming in bootloaders. it's based on injection of new ACPI code through small and targeted SSDT tables that are meant for that very supplemental purpose (SSDT means Secondary System Description Table). it avoids extracting, fixing, patching, recompiling and replacing the system's original ACPI tables and most notably the DSDT, something that can be quite arduous at times. However, the process involved is a much more complicated because: it requires to have a minimum and non-negligeable skillset in ACPI coding. it requires to analyse the code of the original ACPI tables and often work out sections of code to bypass/replace (no duplicates allowed or code is useless) So, given that this method makes no change to the DSDT, it must: bypass the DSDT's BRT6 method. replace it by a new method that will include the desired keyboard notification codes; this will be done in a dedicated SSDT that can be called SSDT-BRT6. with regards to OSID and the requirement to make it return a value greater or equal to 32, there are 2 x possibilities that can be considered: as per BRT6, bypass the DSDT's OSID method and replace it by a new method that will set ACOS parameter according to "Darwin" OS replace calls to the _OSI method, that performs tests on the type of OS, by an alternative method that simulates Windows for Darwin. This allows to have the contents of the OSID method executed sequentially and set ACOS according to the last test in the list; as it stands, this happens to be the test on Linux which sets ACOS to 64, i.e. a value greater than 32 which is the minimum required. In order to replace the DSDT's BRT6 method by an alternative one, particular caution must be exercised because only the method must be replaced, not the call to it from EV5; so a little creativity is required here... To achieve this, ACPI renaming can be applied in the boot loader config to replace "BRT6,2" (as per contents of the method's definition) by "BRTX,2" rather than replace just "BRT6". This is achieved by configuring the following on-the-fly DSDT patch in the boot loader's config (the exact Hexadecimal string is found by opening the extracted DSDT in a Hex editor): Find (HEX): 4252543602 // Hexadecimal sequence for "BRT6, 2" when opening DSDT with a Hex editor Replace (HEX): 4252545802 // Hexadecimal sequence for "BRTX, 2" as replacement The replacement BRT6 method can then be defined in the dedicated SSDT-BRT6 patched table with the following code: DefinitionBlock ("", "SSDT", 2, "hack", "BRT6", 0x00000000) { External (_SB_.PCI0.IGPU, DeviceObj) // (from opcode) External (_SB_.PCI0.IGPU.LCD_, DeviceObj) // (from opcode) External (_SB_.PCI0.LPCB.PS2K, DeviceObj) // (from opcode) Scope (_SB.PCI0.IGPU) { Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) Notify (^^LPCB.PS2K, 0x0366) // Capture of brightness-up key stroke } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) Notify (^^LPCB.PS2K, 0x0365) // Capture of brightness-down key stroke } } } } As far as the OSID method is concerned, the trick is simply to rename it to XSID, rename _OSI method to XOSI and inject (Rehabman's ?) pre-existing and publicly available SSDT-XOSI that simulates Win7 or greater for Darwin (it basically returns true to the OS tests). This is achieved by configuring the following on-the-fly DSDT patches in the boot loader's config: Find (HEX): 4F534944 // OSID in Hexadecimal Replace (HEX): 58534944 // XSID in Hexadecimal Find (HEX): 5F4F5349 // _OSI in Hexadecimal Replace (HEX): 584F5349 // XOSI in Hexadecimal Contents of the SSDT-XOSI patched table is as per documented by Rehabman: DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000) { Method (XOSI, 1, NotSerialized) { Store (Package (0x0A) { "Windows", "Windows 2001", "Windows 2001 SP2", "Windows 2006", "Windows 2006 SP1", "Windows 2006.1", "Windows 2009", "Windows 2012", "Windows 2013", "Windows 2015" }, Local0) Return (LNotEqual (Ones, Match (Local0, MEQ, Arg0, MTR, Zero, Zero))) } } And that's it too!
    1 point
  22. DVMT pre-alloc can be bypassed with some patches but sometimes it's still needed. For example, you want support for 4k display, DVMT will need to be increased and the bypass won't work. It's not recommended for everyone since it can brick your system if done incorrectly. But you can still reset it back to default by setting the BIOS to load the default or remove all the batteries for a period of time.
    1 point
  23. Big Sur - OpenCore Installation: Download MacOS Big Sur / Catalina app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic MLB, ROM, SystemSerialNumber and SystemUUID Note: Replace Config.plist with Config-IntelWifi.plist if you have an Intel combo card E7270_OC_0.7.0.zip E7470_OC_0.7.0.zip E7270_OC_0.6.9.zip E7470_OC_0.6.9.zip E7270_OC_0.6.8.zip E7470_OC_0.6.8.zip E7270_OC_0.6.3.zip E7470_OC_0.6.3.zip
    1 point
  24. 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: Finger Sensor, smart card reader if you have one SD Card reader, unsupported, no driver 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
    1 point
  25. That worked! Thanks much for your support. I guess this issue has been resolved now.
    1 point
  26. Launch Clover Configurator and select install drivers, under UEFI 64 bit, select CsmVideoDxe. Target should be the EFI partition, so you need to mount the drive first. To get rid of that huge cursor, in the Config file uncheck enable mouse under GUI.
    1 point
  27. ALC3234 = ALC255 Try layout-id = 11 If still fails, try 3 Also you're using an SMBIOS of a MacBook, should change to an iMac or Mac mini.
    1 point
  28. remove these from your system RealtekALC.kext IntelBacklight.kext HDAEnabler13.kext Replace the attached into /EFI/Clover kexts in /EFI/Clover/kexts/Other/LE needs to go into /Library/Extensions, repair permissions and rebuild cache Make a backup first of course TP500L.zip
    1 point
This leaderboard is set to Amsterdam/GMT+02:00
×
×
  • Create New...