Jump to content

sebinouse

Members
  • Content Count

    179
  • Joined

  • Last visited


Reputation Activity

  1. Like
    sebinouse reacted to Slice in Clover Change Explanations   
    Rev 4294
    New Shell is able to correctly edit plists. Most important is config.plist. TAB characters converted to double spaces on the fly
    Enter Shell
    Shell> fs0:
    fs0:> cd EFI\CLOVER
    fs0:\EFI\CLOVER> edit config.plist
    ...
    Press F2 to save the result
    Press F3 to exit from editing
    fs0:> exit
    you will return to Clover
     
    Enjoy!
  2. Like
    sebinouse got a reaction from BSpot in Clover Configurator 4.55 breaks audio! be aware!   
    CC adds severals options with it's own default value even if you deleted deliberately this option !
     
    (I had the same issue with power management on haswell cpu several years ago)
  3. Like
    sebinouse reacted to Slice in Clover Configurator 4.55 breaks audio! be aware!   
    Don't use CC! This is wrong program.
  4. Like
    sebinouse got a reaction from D-an-W in Clover General discussion   
    I think this is the normal / expected behavior : 
     
    The first log is for DSDT :
    4:046 0:000 Patching DSDT:  The second is for SSDT :
    4:048 0:000 === [ PatchAllSSDT ] ======================================
  5. Like
    sebinouse got a reaction from Sherlocks in Clover Problems and Solutions   
    Thank you !
     
    I do confirm the patch works ... we can close ticket #381 on sourceforge
    (this update also solve my very long Clover loading time I had since several days) 
  6. Like
    sebinouse reacted to HmO in Clover Problems and Solutions   
    Clover 4154
  7. Like
    sebinouse reacted to RehabMan in Clover Problems and Solutions   
    This patch required for 10.11.6 security update 2017-003.
    The XCPM MSR tables have changed slightly (probably due to some small amount of KabyLake support sneaking in):
     

    Index: rEFIt_UEFI/Platform/kernel_patcher.c =================================================================== --- rEFIt_UEFI/Platform/kernel_patcher.c (revision 4138) +++ rEFIt_UEFI/Platform/kernel_patcher.c (working copy) @@ -689,6 +689,12 @@ DBG("Kernel power management patch 10.11.1(beta 15B38b)(data3) found and patched\n"); return TRUE; } + //rehabman: change for 10.11.6 security update 2017-003 15G1611 + else if (0x00001b90000000E2ULL == (*((UINT64 *)Ptr))) { + (*((UINT64 *)Ptr)) = 0x0000000000000000ULL; + DBG("Kernel power management patch 10.11.6(2017-003 15G1611)(data3) found and patched\n"); + return TRUE; + } //Sherlocks: change for 10.12 DP1 else if (0x00003390000000E2ULL == (*((UINT64 *)Ptr))) { (*((UINT64 *)Ptr)) = 0x0000000000000000ULL; Without this change, you have instant reboot for those computers that need KernelPm=true due to locked CPU MSR 0xE2. 
    Also, I would appreciate it if someone with commit access could restore "without caches" option, as previously requested.
     

    Index: rEFIt_UEFI/entry_scan/loader.c =================================================================== --- rEFIt_UEFI/entry_scan/loader.c (revision 4138) +++ rEFIt_UEFI/entry_scan/loader.c (working copy) @@ -759,7 +759,6 @@ } -// AddMenuCheck(SubScreen, "Without caches", OSFLAG_NOCACHES, 69); // AddMenuCheck(SubScreen, "With injected kexts", OSFLAG_WITHKEXTS, 69); AddMenuInfo(SubScreen, L"=== boot-args ==="); if (!KernelIs64BitOnly) { @@ -767,6 +766,7 @@ AddMenuCheck(SubScreen, "macOS 64bit", OPT_X64, 68); } AddMenuCheck(SubScreen, "Verbose (-v)", OPT_VERBOSE, 68); + AddMenuCheck(SubScreen, "Without caches (-f)", OSFLAG_NOCACHES, 69); AddMenuCheck(SubScreen, "Single User (-s)", OPT_SINGLE_USER, 68); AddMenuCheck(SubScreen, "Safe Mode (-x)", OPT_SAFE, 68); AddMenuCheck(SubScreen, "Disable KASLR (slide=0)", OPT_SLIDE, 68);
  8. Like
    sebinouse reacted to Sherlocks in Clover General discussion   
    I will check on my old laptop 
    나의 LG-F800S 의 Tapatalk에서 보냄
  9. Like
    sebinouse got a reaction from Sherlocks in Clover Problems and Solutions   
    You are very welcome, in fact I'm glad to see that my work has been(and is still) useful 
     
    Keep up the good work on Clover guys    !
  10. Like
    sebinouse reacted to Sherlocks in Clover Problems and Solutions   
    @Slice
     
    here is updated gma.c file
     
    on GMA950/X3100, i traced history on your attached file.
     
    surely awared of duallink through realmac ioreg.
    1366x768 duallink=0, but in hack, no need duallink=0, in your attached 950 file, not existed duallink=0
    1440x900 dualink=1
     
    but i see laptop that has 1400x1050 resolution between 1366x768 and 1440x900. X61 laptop has it. so i had to search it
     
    and found http://forum.thinkpads.com/viewtopic.php?t=86621
     
    in thinkpads forum, Sebinouse recorded important fact about dualink 1 or 0 on resolution.
     
    in his 2010 11 17 : MacPNT package, i can confirmed this true and other facts
     
     
    also i considered more desktop cases and laptop. and reduce code.
     
    sorry my english
     
    thanks to
    Slice
    Sebinouse http://forum.thinkpads.com/viewtopic.php?t=86621
    Rehabman https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/hotpatch/SSDT-IGPU.dsl
    toldea https://github.com/toleda/graphics_Intel_framebuffers
    https://github.com/toleda/audio_CloverHDMI
     
     
    thanks in advance
    gma.c-Sherlocks.zip
  11. Like
    sebinouse got a reaction from polyzargone in Versions bêta : macOS 10.12.2   
    Je ne savais pas que tout été stocké à cet endroit là ! MERCI ... ça va m'éviter des heures de recherche de kext non modifiés ...  
  12. Like
    sebinouse reacted to polyzargone in Versions bêta : macOS 10.12.2   
    Oui, pareil que chez Hervé pour moi et ça avec tous mes Hacks et mon MBA : 2 phases d'installation (ça va quand nettement plus vite si on a un SSD).
     
    Même si je triche un peu et que je récupère les packages d'install dans /Library/Update pour épargner ma pauvre connexion ADSL !
     



  13. Like
    sebinouse reacted to vit9696 in Shiki — protected video playback support on recent hardware   
    sebinouse, no, did not look at it, and will unlikely do that in the future.
    "Connector-full" platform-id may be an inaccurate term but I used it to distinguish from the platform-id without any connectors (i.e. the one used with discrete gpus). So basically it means any platform-id that has connectors.
     
    Actually, does anybody know whether Skylake GPUs are freezing or not?
  14. Like
    sebinouse got a reaction from oSxFr33k in [pre-releases] macOS Sierra   
    I do confirm ... firefox works like a charm ... this issue is due to Safari ... and iTunes ... and QuickTime ...
  15. Like
    sebinouse reacted to bronxteck in [pre-releases] macOS Sierra   
    i do not get the freeze issue in chrome it only happens on safari. i have had the issue since DP1 using hd4600
  16. Like
    sebinouse reacted to vandroiy2012 in AppleALC — dynamic AppleHDA patching   
    It's not HDMI audio patches. This patches prevents codec sleep to avoid clicking sounds in the beginning of playback. With patches codec works like on MacPro. Never sleeps. 
  17. Like
    sebinouse reacted to Needy in AppleALC — dynamic AppleHDA patching   
    Hello there, 
    In order to access the boot log in MacOS Sierra follow the steps below.
     
    1) Open the terminal application.
     
    2) Type in, sudo log show.
     
    Best regards.
  18. Like
    sebinouse reacted to D-an-W in AppleALC — dynamic AppleHDA patching   
    From what I know about it (Not much!), did you compile the kext in debug mode and also add -alcdbg to the boot arguments?
  19. Like
    sebinouse got a reaction from MacKonsti in AppleALC — dynamic AppleHDA patching   
    I chose this framebuffer to have stock AppleIntelFramebufferAzul.kext (except for audio HDMI). It has bigger Framebuffer and Cursor Size to allow higher resolutions. And it give me good results
     
    My HDA injector uses a Layout 1 indeed. The RehabMan's entry is there for CodecCommander searches & debug ...
     
    You can try my FB to see if there is any improvement. My HDMI detection in fine, but it is the only screen I use.
    Our ALC283 is a mess ! Sometimes it seems to work and after a few seconds/minutes quality drops ans the sound is no longer Stereo but dual Mono with the sum of both channels ...
    Make sure you have Stereo even after a loooong period of silence.
     
     
    10.12.DP2 seems to be OK with our ALC283, AppleALC and Mic !!!
    The two one issues I still have to solve :
    1) when I use layout=1 it works, if I do the exact same with layout=12 it doesn't
    2) Bin Patch 1984>0283 needs to be in config.plist to be done by Clover.
     
    I have no time to investigate now ... sorry
  20. Like
    sebinouse got a reaction from MacKonsti in AppleALC — dynamic AppleHDA patching   
    I didn't manage to get stock AppleALC.kext work properly on my NUC  ... but I manage to compile my own with custom codecs.
    I put aside AppleALC for the time being as it was not compatible with macOS Sierra and I needed my mike to control Siri.
     
    I'll try to create my own Codec ASAP and report here. My setup with injector still works on 10.12.
     
    For information I don't have "hda-gfx" on my HDEF ... 
    DefinitionBlock ("", "SSDT", 1, "hack", "hack", 0x00003000) {     Method (_SB.PCI0.HDEF._DSM, 4, NotSerialized)  // _DSM: Device-Specific Method     {         If (LEqual (Arg2, Zero))         {             Return (Buffer (One)             {                  0x03                                                        })         }           Return (Package (0x0C)         {             "layout-id",              Buffer (0x04)             {                  0x01, 0x00, 0x00, 0x00                                      },                "PinConfigurations",              Buffer (Zero) {},              "AAPL,slot-name",              "Built In",              "name",              "Audio Controller",              "model",              Buffer (0x20)             {                 "Realtek ALC283 Audio Controller"             },                "device_type",              Buffer (0x11)             {                 "Audio Controller"             }         })     } } DefinitionBlock ("", "SSDT", 1, "toleda", "ami8hdm1", 0x00003000) {     External (_SB_.PCI0, DeviceObj)    // Warning: Unknown object       Scope (_SB.PCI0)     {         Device (IGPU)         {             Name (_ADR, 0x00020000)  // _ADR: Address             Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method             {                 If (LEqual (Arg2, Zero))                 {                     Return (Buffer (One)                     {                          0x03                                                                })                 }                   Return (Package (0x04)                 {                     "AAPL,ig-platform-id",                      Buffer (0x04)                     {                          0x0D, 0x00, 0x26, 0x0A                                              },                        "hda-gfx",                      Buffer (0x0A)                     {                         "onboard-1"                     }                 })             }         }           Device (HDAU)         {             Name (_ADR, 0x00030000)  // _ADR: Address             Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method             {                 If (LEqual (Arg2, Zero))                 {                     Return (Buffer (One)                     {                          0x03                                                                })                 }                   Return (Package (0x04)                 {                     "RM,device-id",                      Buffer (0x04)                     {                          0x0C, 0x0A, 0x00, 0x00                                              },                        "hda-gfx",                      Buffer (0x0A)                     {                         "onboard-1"                     }                 })             }         }     } }   "hda-gfx" = "onboard-1" is used to link your HightDefinitionAudio controller to your IntegratedGraphicProcessorUnit. If you set the same value for your HDEF, system will be lost.
  21. Like
    sebinouse reacted to nguyenlc1993 in [GUIDE] Installing macOS on ASUS K501L   
    A-1. Postinstall optimization


    1. Generate SSDT.aml for your CPU
    All the SSDT.aml files in the installation pack are generated on my laptop with Pike R. Alpha’s ssdtPRGen.sh script (the latest version at the time of writing was 18.2). Although I ran the script with -p parameter to specify the target processor, running the script again on your computer is recommended. The steps are as follow: Step 1: Connect to the Internet. Open Terminal and execute the following commands:
    curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh chmod +x ~/ssdtPRGen.sh ~/ssdtPRGen.sh The script will automatically detect your CPU and generate the SSDT.aml.
    If it showed any warning, you may choose Yes. When it ask Do you want to copy /Users/nguyen/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml (y/n)?, answer No. For the later questions you may choose No.
     
    Step 2: Open Finder, click menu Go -> Go to Folder…, enter ~/Library/ssdtPRGen, then click Go. You will see your generated SSDT.aml in the opened ssdtPRGen folder.

    Step 3: Mount the EFI partition with EFI Mounter, then copy the SSDT.aml file to /EFI/CLOVER/ACPI/patched folder for use.
    To check whether P-States are fully recognized, you can:
    Use AppleIntelInfo.kext (you may have to install XCode to build the kext). Or open IORegistryExplorer, browse into CPU0@0/AppleACPICPU/X86PlatformPlugin and check the CPUPStates entry in the right list. 2. Configure the resolution and display color
    On Windows 10, I usually scale the display to 150% at native resolution (1920x1080) so that I can better see the texts and objects. However, Mac OS X doesn’t support the same scaling method on Windows but only allow you to lower the resolution, which will cause everything blurred out.
    Luckily, Mac OS X does support a mode called HiDPI (that combine several pixels into one, which is the display method on MacBook Pro Retina). To turn on this mode, you should do the following steps:
    Step 1: Open Terminal, run the following command to enable HiDPI mode, then restart your computer:
    sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true Step 2: Install SwitchResX. Then click on the app’s icon on the menu bar and select the 1280x720 HiDPI entry. That will scale up everything to 150%, but details are still sharp like at native resolution.
     

     
    In addition, ASUS has a utility called Splendid that makes the display color more dynamic or eye-friendly. The utility’s mechanism is to activate the proper color profile for your display, and it can be brought to Mac OS X. The steps are as follow:
    Step 1:
    Open SwitchResX Preferences, then go to the Unknown Monitor section at the bottom of the left sidebar. Get your monitor’s Vendor ID and Product ID. Then byte-flip the Vendor ID and combine with the Product ID.For example, the monitor on my laptop is produced by AU Optronics with Vendor ID 0x06AF and Product ID 0x38ED. Therefore the final result would be 0xAF0638ED.
     
    Step 2:
    Install Splendid Utility on Windows. Browse into C:\Program Files (x86)\ASUS\Splendid\icm folder, you will see a lot of color profiles (.icm files) in there. Select the .icm file that corresponds with your laptop model and monitor, then save it to a backup place.For example, the appropriate color profile for my monitor should be K501LX_8086_AF0638ED.icm. Step 3: Boot into Mac OS X, then copy the saved .icm file to /Library/ColorSync/Profiles/Displays folder to install the color profile.
    Finally click the SwitchResX icon in menu bar, select Color Profile menu, apply the installed color profile and enjoy.
     

     
    3. Fake Card Reader and Webcam to Apple’s built-in devices
    To fake your SD Card Reader into Apple’s Built-In Card Reader, and Webcam into FaceTime HD Camera, we will use CustomPeripheral.kext. The steps are as follow:
     
    Note: This kext doesn’t help you to make card reader and webcam working, its purpose is faking information only. You should rather check if there was any issue with your USB controller.
    Step 1:
    Open System Information. Go to Hardware -> USB section, you will see all the devices connected to USB interface. Select the USB2.0-CRW entry (which is your Card Reader), get the Product ID and Vendor ID of the device, then convert them to decimal number.For example, my card reader has Product ID of 297 (0x0129) and Vendor ID of 3034 (0x0BDA). Do the same things for USB2.0 VGA UVC Webcam entry (which is your Webcam).For example, mine has Product ID of 46211 (0xB483) and Vendor ID of 1266 (0x04F2).
     
    Step 2: Right-click the CustomPeripheral.kext, select Show Package Contents. Then open Info.plist file in the Contents folder.
    Step 3: Expand the IOKitPersonalities property, and you will see a bunch of sub-properties inside it.
    Change the value of idProduct and idVendor keys inside the following sub-properties to the converted Product ID and Vendor ID of your Card Reader: Any_Internal_SD_Card_Reader_1_00 Fake Apple Card Reader Device Fake Apple Card Reader Interface Fake Apple Card Reader SBC Inject Fake Apple Card Reader UMC Inject Change the value of idProduct and idVendor keys inside the following sub-properties to the converted Product ID and Vendor ID of your Webcam: Fake Built-in FaceTime HD Camera Device Fake Built-in FaceTime HD Camera Interface A Fake Built-in FaceTime HD Camera Interface B After editing, save the Info.plist file and install CustomPeripheral.kext to /Library/Extensions.
     

     
    4. Configure Touchpad and Keyboard
    To do this, you have to open the Info.plist file inside ApplePS2SmartTouchpad.kext or AsusNBFnKeys.kext, browse into IOKitPersonalities -> Smart-Pad / AsusNBFnKeys -> Preferences property, then change the configuration. For details about the meaning and possible values of each property, please read the following guides:
    Details about the Smart Touchpad driver Features Details about the Enhanced Keyboard for Smart Touchpad driver The original preferences of these kexts are kept originally, except for the following keys:
    ApplePS2SmartTouchpad - Preferences/Keyboard:
    AsusNBFnKeys - Preferences:

    5. Modify the wifi card’s ROM to fix ATHR: Unknown Locale 60 warning
    This fix is optional and is only applied to Dell DW1702 card or other Atheros wifi cards that have the issue. Details can be found in the guide AR9280 ATHR: Unknown locale: xx - EEPROM Mod.

    6. Improve performance by modifying FakeSMC.kext
    By default, FakeSMC will emulate SMC at version 1.3f3 and compatibility setting of smc-napa. This is not correct for the newer PCs and Mac models, and I recommend you to modify these settings to improve the system’s performance (usually GPU will be benefited more than CPU). Details can be found in the guide Performance tuning with FakeSMC & SMBIOS plist.
    The FakeSMC.kext included in the installation pack was tweaked to SMC version of 2.28f7 and smc-huronriver compatible.

    7. Modify X86PlatformPlugin.kext and AppleGraphicsPowerManagement.kext to to reduce idle frequencies of CPU and iGPU
    ACPI_SMC_PlatformPlugin.kext (for Sandy Bridge and older CPUs), X86PlatformPlugin.kext (for Ivy Bridge and newer CPUs) and AppleGraphicsPowerManagement.kext contain power profiles for every Mac model, which affects power settings and policies, CPU and iGPU frequencies, App Nap settings, etc. By modifying the profile corresponding with your Board-id in SMBIOS, you can reduce the idle frequencies of your CPU and iGPU, thus will save more power, and will make your Hackintosh cooler and quieter.
     
    For the case of Broadwell laptops, we have to look at the power profiles of MacBookPro12,1 (Mac-E43C1C25D4880AD6) and MacBookAir7,2 (Mac-937CB26E2E02BB01). Although the three supported CPUs in this guide can reduce their clock to 800MHz at idle, the power profile will force them to run at 1300MHz instead, as it is designed for the CPUs used in real MacBook Pro Early 2015 and MacBook Air Early 2015. The HD5500 iGPU also suffers a similar situation that it will be forced to run at above 300MHz at idle. Therefore we should modify the entries that affect these floor frequencies to the right value.
     
    The steps that need to be performed are:
     
    Note: Always backup the kexts before making any changes to them.
     
    For X86PlatformPlugin.kext:
    Step 1: Browse into the kext’s resource folder at:
    /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources You will see a bunch of plist files here, which are power profiles for new Mac models.
    Step 2:
    Open the plist file corresponding with the Board-id you are using.For example, if you are using MacBookPro12,1 SMBIOS configuration, you should open Mac-E43C1C25D4880AD6.plist. Navigate into IOPlatformPowerProfile -> FrequencyVectors property. Change the second word of the data in FrequencyVectors from 0D000000 to 0800000, and make sure the value of CPUFloor property is 800. This will enable CPU to run at 800MHz at idle. For AppleGraphicsPowerManagement.kext:
    Step 1: Browse into the kext’s content at:
    /System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents Step 2:
    Open Info.plist, then navigate into IOKitPersonalities -> AGPM -> Machines -> [Your Board-id] -> IGPU -> Heuristic property. Change the value of GT2Floor and GT3Floor properties to 6. This will enable iGPU to run at 300MHz at idle. Finally save the plist files, rebuild kext cache and restart. You can use Intel Power Gadget (it has a bug that will display the triple of your real iGPU frequency) or AppleIntelInfo.kext to verify if the changes are in effect.
     
    Actually, I included 2 dummy kexts in the installation pack namely AppleGraphicsPowerManagement_K501LX.kext and X86PlatformPlugin_K501LX.kext, which contain the modified power profiles. You just have to install these two kexts to get the effect, thus no need to modify the original kexts. 
     
    A-2. How to patch DSDT for ASUS K501LX

     
    https://www.youtube.com/watch?v=8tOr27_C0lc&list=PL28WpAHlndGCSJ5lkX_AajKctCqoSnidU&index=4
    Although the DSDT.aml file included is already patched, you may want to manually patch DSDT by yourself if:
    Your laptop model is K501LB, which seems to use a very similar motherboard like the one used in K501LX. You want to learn about the DSDT/SSDT patching procedure for K501LX model. You want to apply some patches that are not included in the installation pack to your DSDT. When ASUS releases a new BIOS version, and you want to update your DSDT to that version by yourself instead of waiting for my updates. The FixRegion option in Clover seemed not work well, which made your Hackintosh suffer some stability problem. To patch DSDT, we will use MaciASL. In the Preferences of MaciASL, remember to set the Compiler Options to ACPI 6.1 (without that, decompiled DSDT would be buggy).

    1. Extract DSDT, SSDT and decompile into .dsl files
    Step 1: When Clover Bootloader starts, press F4 (no feedback message will be shown). All the ACPI tables will be dumped into /EFI/CLOVER/ACPI/origin folder.
     
    Step 2: Boot into Mac OS X. Mount the EFI partition, then copy the origin folder above to your Desktop.
     
    Step 3: Open the copied origin folder. Except the DSDT and SSDT files, delete all the other .aml files.
     
    Step 4: Right-click the MaciASL.app, select Show Package Contents. Browse into /Contents/MacOS folder, then copy the iasl61 executable to the origin folder and rename it to iasl.
     
    Step 5: Open Terminal and run the following commands:
    cd ~/Desktop/origin/ ./iasl -da -dl *.aml cp ./DSDT.dsl ~/Desktop The DSDT.aml and SSDT-x.aml files will be decompiled together into .dsl files with the same names, and the original DSDT.dsl will be copied to your Desktop.
     
    From now on, you will work with that DSDT.dsl file, while the origin folder will serve as a backup.

    2. Patch DSDT
    Browse into /ACPI/Patches folder in the installation pack, you will see a lot of DSDT patches in this folder:
    Some of the patches are basically kept unchanged from the original version. Some are modified to work on K501LX’s DSDT (all the modifications are listed in the changelog at the beginning of the patches). A few patches are made for specific hardwares (like Ethernet_RTL8111, WiFi_DW1702, etc.). All the patches are selected, modified and tested by me, so there’s no need to apply any other patches, just using them is enough to successfully patch your K501LX’s DSDT.
    It is worth mentioning that many of the patches became deprecated, as I migrated the rename patches and IOReg injection patches to config.plist. The benefits of this movement are:
    As Clover applies the rename patches to not only DSDT but also SSDT tables, the SSDT files are not needed to be manually patched anymore. The problem that the Clover’s FixRegion patch is not applicable to custom SSDT files is now eliminated. The number of required patches decreased considerably.  It is now easier to modify the IOReg properties to be injected, as they are now in config.plist. The deprecated patches are kept in a subfolder for learning purpose, and should not be applied to your DSDT.
    The patching steps are as follow:
    Open DSDT.dsl file with MaciASL. Click Patch, click Open, load the patch file and click Apply to apply the patch. After each patch, you should compile to check for any error. If the log displayed no error, you should save the file so that you could revert back if any error happened later. The effects of the patches and the recommended apply order are listed in the table below:
     

     
    After completing the patch process, compile and save the file as DSDT.aml to your Desktop. Finally copy the patched DSDT.aml file to /EFI/CLOVER/ACPI/patched so that Clover will use it.

    Note: If you applied Generic Fixes patch but still got compilation errors, then it could be because you didn’t decompile the .aml files together, but only open the DSDT.aml file with MaciASL.
     
    A-3. How to generate proper serials for use in SMBIOS


    SMBIOS (System Management BIOS) can be understood as a collection of data tables that describe your system (e.g: model, serial number, CPU information, RAM information, etc.). Here are some important information that can be retrieved from SMBIOS:  

     
    To make your computer look like a real Mac in Mac OS X, Chameleon/Clover allow you to inject SMBIOS information from a configuration file. In the case of Clover, SMBIOS values are read and injected from config.plist -> SMBIOS section. It is highly recommended that these values should be persistent and unique to your computer, otherwise many of Apple services that require verification of system information may not work (e.g: iCloud, iMessage and FaceTime). The SMBIOS properties that affect these above services are:
     

     
    At the time of writing, the method to generate a proper system serial has been found out, while in contrast, the correct pattern of MLB serial is still a matter of research. However, Apple seems to have relaxed their strict MLB verification check, so a board serials generated by the currently available tools on the Internet may work with iMessage/FaceTime. However, it is likely that you still have to contact Apple Support to whitelist your MLB and ROM values.
     
    Here in this installation pack, I included 2 scripts written in Python to help you generate system serial and board serial for 2 Mac models: MacBookPro12,1 and MacBookAir7,2. Depending on which model you prefer to use in SMBIOS configuration, you will have to run the corresponding script. In the future, maybe I will convert the script to Swift language and extend the script so it could generate serials for other Mac models.
     
    It is worth mentioning that the deployed serial generation algorithm is based on knowledge and discoveries shared by many people at the thread Pattern of MLB (Main Logic Board) on InsanelyMac, as well as my own hypothesis about the pattern of MLB serial. Therefore, I do not guarantee that these scripts could generate a 100% correct MLB serial, but I hope that the serial will work with iMessage/FaceTime on your Hackintosh.
     
    If my explanation is still ambiguous, or if you want to clearly know how to activate iMessage/FaceTime on Hackintosh, please visit the thread How to fix iMessage.
     
    The steps to generate unique serials with the script are:
     
    Step 1: Open Terminal, then run the script with the following command:
    python [path to SerialGen_xxx.py] For example, if you already extracted the installation pack to Desktop, and you want to generate serials for MacBookPro12,1 model, then the appropriate command should be like this:
    python ~/Desktop/el-capitan-k501lx/Config/SerialGen/SerialGen_MBP121.py Step 2: In Phase 1, the script will generate 5 random system serials for your Mac model. Follow the instruction to check if any of the serials is available for your Hackintosh. Then enter the index number of the serial you choose and press Enter to proceed to Phase 2.
     
    Step 3: In Phase 2, the script will generate 5 random board serials corresponding with your selected system serial. Just choose the one you prefer, as they are generated by the same algorithm.
     
    Step 4: In Phase 3, the script will ask if you want to generate a partial config.plist containing SMBIOS information for your Mac model on your Desktop. Just simply choose Yes, the script will do the work and finish.
     
    Step 5: Open both your config.plist in the /EFI/CLOVER folder and the generated config.plist on Desktop. Then replace the SMBIOS section of your config.plist with the generated SMBIOS data in Desktop's config.plist.
     
    Step 6: As the SMBIOS of ASUS K501LX suffers from SId bug (inaccessible System ID), it is recommended to use a custom UUID:
    Open Terminal, then run uuidgen several times to get your own UUID. Apply it to config.plist -> SMBIOS -> SmUUID key. Set config.plist -> SystemParameters -> InjectSystemID to Yes. Step 7: After editting, save your config.plist and remember to make a backup of it so that you can use the old serials in case of OS X reinstallation.
     
    A-4. Information about patching AppleHDA


    Codec: Realtek ALC233
    Codec ID: 0x10EC0233
    Layout ID: 3
    PathMap:  

     
    Pin Configuration:
    01471C10    01471D00    01471E17    01471F90 01971CF0    01971D00    01971E00    01971F40 01B71C30    01B71D00    01B71EA0    01B71F90 02171C20    02171D10    02171E21    02171F00 01470C02 Note: At this moment, Line In is temporarily disabled due to causing cracking sound in case of plugging and then replugging headphone.
     
    How to set MuteGPIO?
    Look at VREF caps of Node 0x19 and Node 0x1B in codec dump:
    Vref caps: HIZ 50 GRD 80 100 The correct MuteGPIO value for Node XX is: 0x500100XX (replace XX with the Pin Complex Node ID)
    IntMic: MuteGPIO = 0x5001001B = 1342242843 LineIn: MuteGPIO = 0x50010019 = 1342242841 MuteGPIO for IntSpeaker should always be set to 0.
  22. Like
    sebinouse got a reaction from Micky1979 in Clover General discussion   
    Same here (you pasted it 2 times)
     
    Correct link :https://github.com/RehabMan/patch-nvme
     
     
    I read your Github page on NVMe, and I see your point. Do we need to disable the orignal kext to avoid further conflicts. Maybe this original kext won't be a problem as it doesn't recognize our SSDs and so it doesn't even load ...
  23. Like
    sebinouse got a reaction from Micky1979 in Clover General discussion   
    I tested once again ... and YES "10.11.x" is OK
  24. Like
    sebinouse got a reaction from Micky1979 in Clover General discussion   
    macOS 10.12.DP2 sw_vers -productVersion 10.12 Clover r3595 MatchOS key present set to blank skipped MatchOS key not present OK Rest unchanged ! Looks fine ! Thanks !
  25. Like
    sebinouse reacted to Slice in Clover General discussion   
    ?
    So blank works as "Disabled"? Let it be.
×