Jump to content

ham4ever

Members
  • Content Count

    344
  • Joined

  • Last visited

  • Days Won

    2

Reputation Activity

  1. Like
    ham4ever reacted to canyondust in OpenCore Discussion   
    I have the same issue since updating to OC 0.5.1. Did you find a fix for this? (I tried selecting the startup disk in system preferences)
     
    EDIT: the fix is setting RequestBootVarRouting = TRUE
  2. Like
    ham4ever got a reaction from xtddd in [pre-release] macOS Catalina   
    updated to beta 9 build 19573a.
    OpenCore bootloader.
     
     

  3. Like
    ham4ever reacted to MaLd0n in [Guide] Sierra / High Sierra / Mojave / Catalina on mobos Serie 100 / 200 / 300 / SkyLake / KabyLake / CoffeeLake DSDT   
    Now have a Olarila app, just download app and clover folder for your Chipset! https://olarila.com/forum/viewtopic.php?f=81&t=6771   ***The topic is for Notebooks and Desktops***   Install MacOS with Olarila Image, Step by Step, Install and Post Install
     
    https://olarila.com/forum/viewtopic.php?f=50&t=8685
        -Mojave Full DSDT patch http://olarila.com/forum/viewtopic.php?f=59&t=6428 First... ***Update bios to last available version!***   If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Extract tables with F4 key in Clover boot screen! -Run it and send me files! RunMe.app     Look at my Clover folders and understand what we really need, this is the best way to learn     1-Installation     --Create a bootable copy of macOS Sierra / High Sierra / Mojave   https://github.com/chris1111/Create-Install-Media/releases   --Install Clover in USB stick   https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder    https://olarila.com/files/Clover.Folder/CLOVER.SERIES.100.200.300.zip   --Install Sierra/High Sierra and boot into system! 2-Post Installation     --Install Clover in HDD/SSD and replace with my folder   https://olarila.com/forum/viewtopic.php?f=28&t=8222   --Reboot and activate video!   3-Video     -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/   -Nvidia WebDriver High Sierra   http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/   -Cuda   http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/   -Check it, easy way   nvidia-update.command.zip by Benjamin-Dobell   4-DSDT       Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC* -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS* -BLC0 -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -IMEI -EC -PNLF(Nvidia/AMD) -HDMI ---To avoid problems use some patches in config.plist, don't forget!--- GLAN to GIGE 474c 414e 4749 4745 GFX0 to IGPU 47465830 49475055 HDAS to HDEF 48444153 48444546 HECI to IMEI 48454349 494d4549 SAT0 to SATA 53415430 53415441 5-SSDT   Generate your SSDT for PM, use ssdtPRGen by Piker-Alpha https://github.com/Piker-Alpha ssdtPRGen.command.zip   or just use "plugin-type"=0x01 in DSDT, SSDT or Clover config.plist   for check Power, Frequency, Temperature and Utilization, use it Install Intel Power Gadget.pkg.zip   6-Brightness  
    Install .app, select the required permission and reboot. Work in F1 / F2 keys!
    NativeDisplayBrightness.app.zip


    https://github.com/Bensge/NativeDisplayBrightness/releases
    *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install
      -Clover   https://sourceforge.net/projects/cloverefiboot/files/Installer/   -Lan driver by Mieze     -Atheros http://www.insanelymac.com/forum/files/file/313-atherose2200ethernet/   -Intel http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/   -Realtek http://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/   -Links     -FakeSmc https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek   -Audio https://github.com/vit9696/AppleALC http://www.insanelymac.com/forum/topic/293863-applehda-patch-requests/   -USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads   if u like, Rate Topic     It's time to Rock -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, badruzeus and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
  4. Like
    ham4ever reacted to dracoflar in OpenCore Configurator   
    @arsradu Oh that's actually my old guide, you might find the newer one more useful as it's the one I'm actively working on with Vit9696: https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/
  5. Like
    ham4ever reacted to Sanom4 in [pre-release] macOS Catalina   
    Here's developer utility 

    https://gofile.io/?c=KT4jJX
  6. Like
    ham4ever reacted to MaLd0n in [pre-release] macOS High Sierra   
    4084
    Clover_v2.4k_r4084.pkg.zip
     
    4090
    Clover_v2.4k_r4090.pkg.zip
     
    4094
    Clover_v2.4k_r4094.pkg.zip
  7. Like
    ham4ever reacted to PMheart in [pre-release] macOS High Sierra   
    And what about this one? (To enroll your device)
     
    macOSDeveloperBetaAccessUtility.dmg
  8. Like
    ham4ever reacted to toleda in El Capitan: Realtek ALC AppleHDA Audio   
    10.12 Audio/Temporary Fix
    edit config.plist/KernelAndKextPatches/KextsToPatch/
    1. Duplicate:

    2. Edit:

     
    Credit: pcpaul/#10344
    http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2243118
  9. Like
    ham4ever reacted to MacPeet in Apple unveils "macOS Sierra"   
    CloverConfigurator  Version 4.27 works
    4.28 / 4.29 no
  10. Like
    ham4ever reacted to fantomas in Apple unveils "macOS Sierra"   
    Tape this in Terminal
    sudo spctl  --master-disable (Credits to Netkas)
  11. Like
    ham4ever reacted to insanelyDeepak in Apple unveils "macOS Sierra"   
    @Mirone you are missing comma at line 146 

    so i added and updated your app AppleHDAPatcher.zip
     
    @ham4ever try this 
  12. Like
    ham4ever reacted to tt22 in El Capitan - Problems with sleep   
    Just updating you guys with fresh information. According to the last clover ticket http://sourceforge.net/p/cloverefiboot/tickets/179/almost everyone has troubles with sleep. This is the bug of El Capitan. Tmrw I will try to dig it deeply. Will try to configure power management kext to our systems. Cheers!
  13. Like
    ham4ever reacted to toleda in El Capitan: Realtek ALC AppleHDA Audio   
    Audio - Realtek ALC AppleHDA, El Capitan Update
    Realtek ALC/Desktop: 269*, 283*, 885, 887, 888, 892, 898 and 1150 on board audio (*BRIX/NUC only)
    Supports OS X: 10.12, 10.11, 10.10, 10.9 and 10.8 
     
    DEPRECATED: See AppleHDA Realtek Audio - AppleHDA - InsanelyMac Forum
     
    Enables OS X Realtek ALC on board audio for Intel motherboards. El Capitan requires native AppleHDA.kext. Codec specific script edits binaries and installs specific files. Depending on user requirements, select one Realtek ALC Installation Method.
     
    Change Log
    v3: 8/17/16 - Initial 10.12/Sierra Support/cloverALC, see I. Realtek ALC AppleHDA Scripts v2.6 - 6/16/16 - 10.12 Audio/Temporary Fix, see Post #271, credit pcpaul v2.5 - 4/8/16 - x99/AppleHDA.kext/10.11 support, see 2. X99/Intel High Definition Audio, credit bOLEMO v2.4 -1/25/16 - Uninstall Realtek ALC AppleHDA added v2.3 - 1/18/16 - Audio/ALC Injection verification (Tools 3.) v2.2 - 12/15/15 - audio_pikeralpha-110 (Clover version of Piker Alpha/AppleHDA8Series.sh)  v1.1 - 11/28/15 - 100 Series/Skylake  (see Unsupported/Non-working Realtek ALC AppleHDA/1. 100 Series, below) and X99 update (see Unsupported/Non-working Realtek ALC AppleHDA/2. X99, below) v1.0 - 10/4/15 - El Captain Support Realtek ALC Installation Methods (Select one method)
     
    I. Realtek ALC AppleHDA Scripts
    Download script (select one script, Download/View Raw)  
    audio_cloverALC.command.zip
    patch kernel cache no edits to any native AppleHDA.kext file 2-4 files added to Resources folder Clover only audio_realtekALC.command.zip
    patch kext in place edits AppleHDA.kext binaries and adds files run script after Software Update Chameleon, Clover, Osmosis, others audio_pikeralphaALC.command.zip
    patch kernel cache native AppleHDA.kext (signed) installs AppleHDAxxx.kext (ex., L/E/AppleHDA892.kext) Not supported: ALC269 and ALC 283 Clover only Double Click Downloads/audio_. . .ALC-110.command Enter Password Answer questions (y/n) Restart II. Piker-Alpha AppleHDA8series Script
    Download script (see README) Piker-Alpha/AppleHDA8Series.sh (10.10 working, 10.11TBA, 10.11 fix, see below) patch alias no edits to any native AppleHDA.kext file installs AppleHDAxxx.kext (ex., S/L/E/AppleHDA892.kext) Chameleon, Clover, Osmosis, Revoboot, others Terminal (Select one method) Clover/ALC audio $ ./AppleHDA8Series.s ​ALC audio: $ ./AppleHDA8Series.sh -b AppleHDA ALC audio and HD4600 HDMI audio: $ ./AppleHDA8Series.sh -b AppleHDA -b AppleHDAControll   Enter Password ... choose desired codec: (1-7) ... layout-id (y/n) Answer questions (y/n) 10.11 fix, see Credit/lisai9093 (below) Restart Requirements
    OS X versions supported El Capitan/10.11.x Disable SIP: CsrActiveConfig=0x3 ​Yosemite/10.10.x Allow unsigned kexts: kext-dev-mode=1 Mavericks/10.9.x  Mountain Lion/10.8.x Intel Desktop motherboards Native AppleHDA (Restore native AppleHDA [Guide].pdf) Audio codec/ALC Injection, see Tools 3. (below), confirms: Supported Codecs, see Realtek Codecs and Applications (below) Supported Audio IDs, see Audio IDs (below) Working Audio ID Injection, Audio ID Injection (below) Realtek Codecs and Applications (Codec/Device_ID/Application/Audio ID(s)/Audio Devices)
    ALC269/0x10ec0269/BRIX/1/HP, SPDIF ALC283/0x10ec0283/NUC and BRIX Pro/1/HP, Mic ALC885/0x10ec0885/Desktop/1/All ALC889A/same as ALC885  ALC887/0x10ec0887_v003002/Desktop/1 or 2 or 3/All ALC887-L/0x10ec0887_v002002Desktop/1 or 2/All ALC888B/same as ALC887   ALC888/0x10ec0888_v003002/Desktop/1 or 2 or 3/All ALC888-L/0x10ec0888_v002002Desktop/1 or 2/All ALC888S/same as ALC888   ALC889/0x10ec0889/Desktop/1 or 2/All ALC892/0x10ec0892/Desktop/1 or 2 or 3/All ALC898/0x10ec0899/Desktop/1 or 2 or 3/All ALC1150/0x10ec0900/Desktop/1 or 2 or 3/All Audio IDs
    Audio ID: 1 (motherboard with 3, 5 or 6 audio ports) Stereo (2 inputs, 4 outputs), 5.1 analog surround (3 outputs) and 5.1 digital surround (optical) Front Panel: Pink & GreenMotherboard: Pink, Blue, Green, Orange, Black and SPDIF Audio ID: 2 (motherboard with 3 audio ports, enables analog surround sound)) Stereo (1 input, 4 outputs), 5.1 analog surround (3 outputs) and 5.1 digital surround (optical) Front Panel: Pink & Green Motherboard: Green, Pink (> Orange), Blue (> Black) and SPDIF Audio ID: 3 (Enables HD3000/HD4000/HD5xx HDMI audio) Stereo (2 inputs, 3 outputs/) and 5.1 digital surround (optical) Front Panel: Pink & Green Motherboard: Pink, Blue, Green, Black and SPDIF No Orange support if required, see More Info/2. Customization guide (below)  Audio ID Injection, audio_ALCInjection
    HDEF/kext/no dsdt/HDAEnabler_.kext = Audio_ID HDEF/dsdt/layout-id = Audio_ID HDEF/ssdt/layout-id = Audio_ID, see ssdt_hdef HDEF/Clover/config.plist/Devices/Audio/Inject/Audio_ID HDEF/Chameleon/Extra/org.chameleon.Boot.plist HDAEnabler = Yes HDEFLayoutID = 01000000 or 02000000 or 0300000  Unsupported/Non-working Realtek ALC AppleHDA.kext
    100 Series/Intel High Definition Audio (Workaround requires 1, 2, 3 and 4) Rename dsdt/HDAS to HDEF  (Select one method) Clover: Download/config-audio_cloverALC-100series.plist.zip Add config.plist/ACPI/DSDT/Patches/Rename HDAS to HDEF ssdt injection (Any bootloader. Select Audio ID and install) Audio ID: 1, ssdt_hdef-1-100-hdas.zip Audio ID: 2, ssdt_hdef-2-100-hdas.zip Audio ID: 3, ssdt_hdef-3-100-hdas.zi  Restart Install Realtek ALC Audio (see Realtek ALC Installation Methods) Restart X99/Intel High Definition Audio  (Workaround requires 1, 2, 3, 4 and 5), 10.11/credit bOLEMO Rename dsdt/ALSA to HDEF (Select one method) Clover: Download/config-audio_cloverALC-x99.plist.zip Add config.plist/ACPI/DSDT/Patches/Rename ALZA to HDEF ssdt injection (any bootloader): Audio ID: 1, install ssdt_hdef-1-x99_alza.zip Restart Install Realtek ALC Audio (see Realtek ALC Installation Methods) Add x99 HD Audio device_id (Select one method) Clover: Download/config-audio_cloverALC-x99.plist.zip (Select one, appropriate version) Add config.plist/KernelAndKextPatches/KextsToPatch/10.10-10.11+x99-ALC-Onboard-Audio Add config.plist/KernelAndKextPatches/KextsToPatch/110.9.4-10.9.5-x99-ALC-Onboard-Audio Patched AppleHDA.kext (RealtekALC) Double Click/audio_alc_x99-hda-100_patch.command.zip Restart 887_v100101 and earlier Workaround: try 887 Legacy 888_v100101 and earlier Workaround: try 888 Legacy Asus P67H67 3xxx BIOS: Phantom codec Workaround: 2xxx BIOS downgrade, 7/8 Series motherboard upgrade MSI motherboards, pre Sandy Bridge Workaround: 6/7/8 Series motherboard upgrade AC97 (Front Panel) Workaround: HD Audio Front panel More Information audio_ALC_guides
    Capabilities - Realtek ALC AppleHDA_v2 [Guide].pdf Audio_ID Configurations, Surround sound, audio popping, USB start up problem  Customization - Realtek ALC AppleHDA_v2 [Guide].pdf Manual speaker and headphone selection, Substitute SPDIF-2 Wire Output  Screenshots - Realtek ALC AppleHDA_v2.pdf System Information/Audio/Intel High Definition Audio, System Preferences/Sound/Output  No Audio Devices - Realtek ALC AppleHDA [Guide].pdf No audio devices, no sound, no codec  No Sound - Realtek ALC AppleHDA [Guide].pdf Audio devices present, no sound when selected  No Audio After Sleep/Wake - Realtek ALC AppleHDA [Fixes].pdf No audio devices on wak  Surround Sound - Realtek ALC - AppleHDA [Guide].pdf Players, analog, optical Uninstall Realtek ALC AppleHDA
    cloverALC, remove: S/L/E/AppleHDA.kext and install the native AppleHDA.kext or S/L/E/AppleHDA.kext/Contents/Resources/layout1.zml.zlib, layout2.zml.zlib, layout3.zml.zlib, Platforms.zml.zlib config.plist/.../KextsToPatch/AppleHDA (3x) EFI/CLOVER/kexts/10.xx or other/realtekALC.kext pikeralphaALC, remove: L/E/AppleHDA8xx.kext config.plist/.../KextsToPatch/AppleHDA (3x) realtekALC, remove: S/L/E/AppleHDA.kext and install the native AppleHDA.kext pikeralpha AppleHDA8Series, remove: S/L/E/AppleHDA8xx.kext and install the native AppleHDA.kext Tools
    IORegistry Explorer (choose one) IORegistryExplorer_v2.1.zip (View Raw) IOJones
    DPCIManager Audio/ALC Injection: audio_codecdetect.command.zip (select View Raw, double click) MaciASL Problem Reporting
    Description of audio problem OS X version/motherboard model/BIOS version/processor/graphics Procedure/Guide Used Audio/ALC Injection (Tools 3.) Double click/Downloads/audio_codecdetect.command Terminal/Shell/File/Export Text As. . Copy of IOReg - IOReg_v2.1/File/Save a Copy As…, verify file (Tools 1.) Copy Of Console/All Messages  (last boot)/File/Save a Copy As.. Installed S/L/E/AppleHDA.kext or AppleHDA8Series AppleHDAxxx kext Screen shots: DPCIManager/Status (Tools 2.) System Information/Hardware/Audio/Intel High Definition Audio (not Devices)  Terminal/Shell/Export Test As. . .  (if script used) audio_realtekALC-100.command AppleHDA8Series.sh audio_cloverALC-100.command  Chameleon Extra/org.chameleon.Boot.plist DPCIManager/Misc/Boot Log (Tools 2.) Extra/dsdt.aml (if installed) Extra/ssdt.aml (if installed  Clover EFI/Clover/config.plist DPCIManager/Misc/Boot Log (Tools 2.) EFI/Clover/ACPI/Patched/dsdt.aml (if installed) EFI/Clover/ACP Patched/ssdt.aml (if installed)  Credit
    bOLEMO, post #196, El Capitan: Realtek ALC AppleHDA Audio
    lisai9093, Post #5, AppleHDA for El Capitan discussion
    THe KiNG [HOW TO] Patch AppleHDA - Knowledge Base - Project OS X Forums
    PikeRAlpha New style of AppleHDA.kext patching for Yosemite | Pike's Universum
    abxite  http://applelife.ru/...06/#post-353647
    TimeWalker75a, Post # 20, No sound after waking from sleep
    RevoGirl
  14. Like
    ham4ever reacted to Micky1979 in OS X El Capitan DP's builds!   
    There are 3 methods to create an Installer:
     
    1) restore the basesystem.dmg to a USB drive and copying Pakages folder, kernel, etc. (Hack way)
    2) using terminal (Vanilla way):
    sudo /Applications/Install\ OS\ X\ El\ Capitan\ GM\ Candidate.app/Contents/Resources/createinstallmedia --volume /Volumes/YourUSB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan\ GM\ Candidate.app --nointeraction (the example require that your app is inside the /Applications folder)
     
     
    3) Open and run  /Applications/Install OS X El Capitan GM Candidate.app and point the installation to a selected Volume! (Vanilla way)
     
     
    Method 1 is not automated, 2 and 3 yes. But method 3 do things in a way the bootloader can't know which version you are installing (problem for Clover, Enoch etc.) because no SystemVersion.plist exist in this way (btw I'm making a workaround here:            #3409            ).
    Method 2 instead create some folders containing the SystemVersion.plist on your USB stick... Well now the bootloader know the Os version inside the Installer, then can apply patches to the kernelcache to boot correctly your Installer... try method 2!
     
     
    EDIT
    Method 3 also create problem if the app is not inside the /Applications folder, because the app write some file on the Volume where the app reside (can be another Volume too if you have it somewere)
  15. Like
    ham4ever reacted to Micky1979 in OS X El Capitan DP's builds!   
    You can not see everything in the picture  ..... However I did the "middle school" at the time Snow Leopard released...
    I've installed it when already in 10.6.8, first time I did (it took me 1 mounth , after I discovered the FakeSMC  ) 
  16. Like
    ham4ever reacted to fantomas in OS X El Capitan DP's builds!   
    hi
     
    just to clarify a thing... I read in a post that using ' f ' option with -R option (like that -Rf) would force permissions to change but it's not correct.
     
    in fact, -Rf it makes no sense and means absolutely nothing... there's no ' f ' in chmod command but ' -f ' and it's not meaning ' force ' but ' Do not display a diagnostic message if chmod could not modify the mode for file '.
     
    in -Rf case, only -R is taken into account... it's why you can see the command working but not in the way you want.
     
    if you want to know what you can do with chmod, then tape man chmod
     
    it also works with chown
     

  17. Like
    ham4ever got a reaction from muitoslogs in Intel HD Graphics 4600 (Haswell) working displayport   
    thanks my intel 4600 woooorkiing
  18. Like
    ham4ever reacted to arsradu in OS X El Capitan DP's builds!   
    EFI folder inside the EFI partition is the way it's always been, for as far as I know. So, your unbootable system doesn't have anything to do with that. I've got the files in EFI (partition)>EFI(folder)>CLOVER (etc) and I have no problems booting up. So, I'm not sure what's going on with your PC, but that is not the issue.
     
    As for copying the kexts into the right place, you can use Slice's method (thanks for the tip! ). It's the easiest and the most effective one I've seen so far.
     
    Assuming you've got the kext on your Desktop, and using FakeSMC.kext as an example, type this in terminal:
    sudo cp -R -v ~/Desktop/FakeSMC.kext /Library/Extensions/ This will copy your kext from Desktop into /Library/Extensions and will set the appropriate permissions to the kext. You don't need to use S/L/E. Theoretically you can use any location where you can write (haven't tried that theory). I used L/E and I got no issues. So, up to you.
     
    Yes, it is still possible to use unsigned kexts in DP6 if:
    1. you've got a newer version of Clover (3252 is perfect)
    2. you got the custom kexts (especially FakeSMC.kext) in L/E or S/L/E and you set the correct permissions (if you're using the command above, the permissions will be automatically set)
     
    After everything is correctly set up and you can boot up successfully, if you really want that SIP enabled, you can add this in Clover config.plist (RtVariables section):
     
    <key>RtVariables</key> <dict>         <key>CsrActiveConfig</key>         <string>0x00</string>         <key>BooterConfig</key>         <string>0x28</string> </dict> Don't use Clover Configurator for that. Open the config file with Text Edit and do the changes manually.
     
    You might (so far, it's just a theory, but it's worth remembering for the next update) want to switch from 0x00 to 0x01 before applying the next update. This will allow unrestricted access to unsigned kexts (only), such as FakeSMC, and you should have no problems booting up after the update. I haven't tried keeping it on 0x00 (SIP fully enabled). But if you want, you can try with the next update and see what happens.
     
    To check if SIP is enabled, you can call csrutil status using this command in terminal:
     
    csrutil status If it's enabled, you should see this:
    System Integrity Protection status: enabled.
  19. Like
    ham4ever reacted to blackosx in Clover General discussion   
    Clover needs to adapt to allow SIP to remain enabled and still give us freedom to load/inject kexts etc. for El Capitan DP4 and onwards. Pike’s changes for RevoBoot and r2737 of Enoch branch of Chameleon are working well here. I would like to see Clover follow this route.
  20. Like
    ham4ever reacted to Pike R. Alpha in Chameleon 2.4svn Official PKG Installer   
    Never let the word "friends" be just friends, but be there when they need you...
  21. Like
    ham4ever reacted to toleda in Yosemite: Audio - Realtek ALC AppleHDA   
    Yosemite: Audio - Realtek ALC AppleHDA - Deprecated
    For Realtek ALC885 through ALC1150 on board audio codecs
     
    Yosemite/solutions/support, see El Capitan: Realtek ALC AppleHDA Audio
     
    Enables Realtek ALC on board audio for Intel motherboards running Yosemite. Requires installed native AppleHDA.kext. Codec specific script edits binaries and installs specific files. Depending on user requirements, 3 Realtek ALC AppleHDA installation techniques are available.
     
    Change Log
    10/18/15 - Deprecated
    v3.4 - 1/8/2015: audio_cloverALC-100/audio_realtekALC-100 (v1.0.4) release; 887/888 legacy detection, ALC1150 patch fix, Clover/Legacy support, bug fixes
    v3.3 - 12/27/2014: No Audio after Sleep/Wake, credit: TimeWalker75a, see Note 6.
    v3.2 - 11/29/2014: BRIX/ALC269, BRIX Pro/ALC283 and NUC/ALC283 Support, see Note 5.
    v3.1 - 11/15/2014: x99 audio, see Post #237, Haswell-E mach_kernel patch (5960X, 5830K and 5820K)
    v3.0 - 10/15/2014 - Yosemite  Release
    v2.1- 8/12/2014 - 9 Series/EAPD added to 887, 892, 898, 1150, credit: kidalive
    v2.0 - 8/12/2014 - v2 AppleHDA.kext patch scripts available; easier, simpler and faster.
    v1.1 - 6/130/14 - Yosemite/Realtek ALC AppleHDA Support Kext Available - credit PikeRAlpha v1.0 - 6/14/14 - Yosemite (DP - initial support) Yosemite/New Feature
    9 Series AppleHDA.kext support New User/First Time/Yosemite Audio
    Determine motherboard audio codec (Realtek ALCxxx) Source: User manual, specifications, website Supported: ALC885, 887, 888, 889, 892, 898 or 1150 Audio Codec is: ALCxxx Recommended Audio Selections Chameleon/Clover Injection Audio ID: 1 ALCxxx Requirements
    OS X versions supported: Yosemite/10.10, see Notes 1 and 2, below Native AppleHDA.kext Need native, see Restore native AppleHDA [Guide].pdf Realtek ALC, one of the following Device_ID - Codec Name Not sure, see Notes 3, below Supported motherboard on board audio codecs 10ec0885 - ALC885/ALC889a 10ec0887 (v100202 and v100302) - ALC887/ALC888b 10ec0888 (v100202 and v100302) - ALC888/ALC888s 10ec0889 - ALC889 10ec0892 - ALC892 10ec0899 - ALC898 10ec0900 - ALC1150 Supported Audio-IDs (Audio_ID = layout-id), select one Audio IDs Audio_ID: 1 - 5/6 port Realtek ALC onboard audio and HD5K/AMD/Nvidia HDMI audio Audio_ID: 2 - 3 port Realtek ALC onboard audio and HD5K/AMD/Nvidia HDMI audio Audio_ID: 3 - 3/5/6 port Realtek ALC onboard audio and HD3K/HD4K/AMD/Nvidia HDMI audio Details Audio_IDs: 1 and 2 support analog 5.1 surround sound, 3 does not Audio_IDs: 1, 2 and 3 require HDMI audio dsdt edits/ssdts for HDMI audio Audio_ID Injection, select one Supported Realtek ALC Injection methods, see audio_ALCInjection HDEF/kext/No dsdt/HDAEnabler_.kext = Audio_ID HDEF/dsdt/layout-id = Audio_ID, HDEF/ssdt/layout-id = Audio_ID HDEF/Clover/Config.plist/Devices/Audio/Inject = Audio_ID HDEF/Chameleon Installer/Customize/Setting/HDEF Layout/ Verification, see Notes 4, below Realtek ALC AppleHDA Audio Patch Methods v2 - select one
    realtekALC/patch in place- new script detects the codec and patches the native AppleHDA.kext for ALC onboard audio. Run the same script to restore audio after Software Update
    Piker-Alpha AppleHDA8series - installs an audio support kext for ALC onboard audio. AppleHDA.kext remains native and the technique survives most Software Updates. Credit: Piker-Alpha
    cloverALC/Clover patched - automatically detects codec and installs all audio files and patches for ALC onboard audio. Audio survives most Software Updates.  Install once and done. Credit: abxite
    1. realtekALC/patch in place
     
    New script detects the codec and patches the native AppleHDA.kext for ALC onboard audio. Run the same script to restore audio after Software Update.
    realtekALC/patch in place Bootloaders: Chimera, Chameleon, Clover Software Update: run same script after update restart More Info: audio_RealtekALC Installation - realtekALC Download: (View Raw) audio_realtekALC-100.command.zip Double click: Downloads/audio_realtekALC-100.command Password? Verify Codec - y/n? (885, 887, 888, 889, 892, 898, 1150 only) Enable HD4600 HDMI audio - y/n? (887, 892, 898, 1150 only) Restart Verify Patched AppleHDA kext installed S/L/E/AppleHDA.kext_vx.x-toledaALCxxx Verify ALC onboard audio System Preferences/Sound/Output/select audio device 2. Piker-Alpha AppleHDA8series
     
    installs an audio support kext for ALC onboard audio. AppleHDA.kext remains native and the technique survives most Software Updates. Credit: Piker-Alpha
    Piker-Alpha AppleHDA8series Bootloaders: Chimera, Chameleon, Clover Software Update: persistent, no action required More Info: audio_pikeralphaALC Installation - AppleHDA8Series Piker-Alpha/AppleHDA8Series.sh Download Zip $ cd Downloads/AppleHDA8Series.sh-master Chameleon/Chimera/Clover - no AppleHDA binary patch $ ./AppleHDA8Series.sh -b AppleHDA $ ./AppleHDA8Series.sh -b AppleHDA -b AppleHDAController Clover - with AppleHDA kext patch(es) $ ./AppleHDA8Series.sh Password Codec Layout Install S/L/E Reboot Verify ALC AppleHDA8Series kext installed S/L/E/AppleHDAxxx Verify ALC onboard audio System Preferences/Sound/Output/select audio device 3. cloverALC/Clover patched
     
    Automatically detects codec and installs all audio files and patches for ALC onboard audio. Audio persists after most Software Updates.  Install once and done. Credit: abxite
    cloverALC/Clover patched Bootloaders: Clover Software Update: persistent, no action required More Info: audio_CloverALC Installation - cloverALC (See Note 3) Download: (View Raw) audio_cloverALC-100.command.zip
    Double click Downloads/clover-90_patch_v2.command Password? Verify Codec - y/n? (885, 887, 888, 889, 892, 898, 1150 only) 1150 Only: see note 5. before restarting Restart Verify ALC onboard audio System Preferences/Sound/Output/select audio device Notes
    10.10 and newer/Boot flags Clover/config.plist Mandatory, Add: Boot/Arguments/kext-dev-mode=1 Remove: Boot/Arguments/npci=0x3000 Chameleon/Extra/org.chameleon.Boot.plist Mandatory:, Add: Kernel Flags//kext-dev-mode=1 Remove Kernel Flags/npci=0x3000 AppleHDA.kext version matters AppleHDA.kext can be the same as or earlier than the installed OS X version AppleHDA.kext does not work if newer than the installed OS X version Audio Codec Verification/DPCIManager see Tools 2. See Status/Codec ID/Revision, note Codec ID Verify Requirements/2. Realtek ALC/1. Supported audio codecs, above Audio_ID verification/IORegistryExplorer see Tools 3. Search: HDEF Locate: layout-id (right pane, scroll down) Verify: <01 00 00 00> or <02 00 00 00> or <03 00 00 00> BRIX/ALC269, BRIX Pro/ALC283 and NUC/ALC283 Support
    Installation methods realtekALC/patch in place Piker-Alpha AppleHDA8series (N/A) cloverALC/Clover patched Audio Devices ALC269 - BRIX/Headphones and SPDIF out ALC283 - BRIX Pro and NUC/Headphones (Microphone is not supported) HDMI audio with dsdt edits or ssdt: see HDMI Audio AppleHDA ​​No Audio after Sleep/Wake Codec-Commander, credit TimeWalker75a Instructions: Post #333, Yosemite: Audio - Realtek ALC AppleHDA Unsupported/Non-working Realtek ALC AppleHDA.kext
    887_v100101 and earlier 888_v100101 and earlier Asus P67H67 3xxx BIOS: Phantom codec Workaround: 2xxx BIOS downgrade, 7/8 Series upgrade MSI motherboards, pre Sandy Bridge Workaround: 6/7/8 Series upgrade AC97 (Front Panel) Workaround: HD Audio Realtek ALC Speakers
    Audio ID: 1 and 3, match speaker connector color to same motherboard/case port color Audio ID: 2 (3 port motherboard audio) Plug black connector into blue motherboard port for rear speakers Plug green connector into green motherboard port for front speakers Plug orange connector into pink motherboard port for center/sub speakers Front panel: Match connector color to same case port color Optional Installs
    Configure 5.1 Surround Sound Aggregate Device (Not available with Audio ID: 3) Applications/Utilities/Audio MIDI Setup/Audio Devices/+/Create Aggregate Device Select (in order) Built-in Output Built-in Line Output (1st) Built-in Line Output (2nd) Configure Speakers Multichannel 5.1 Surround Apply/Done Connect Audio Input to Audio Output Line In - http://www.rogueamoeba.com/freebies/ More Information - audio_ALC_guides
    Capabilities - Realtek ALC AppleHDA_v2 [Guide].pdf
    ex., Audio_ID Configurations, Surround sound, audio popping, USB start up problem Customization - Realtek ALC AppleHDA_v2 [Guide].pdf
    ex., Manual speaker and headphone selection, Substitute SPDIF-2 Wire Output Screenshots - Realtek ALC AppleHDA_v2.pdf
    ex., System Information/Audio/Intel High Definition Audio, System Preferences/Sound/Output No Audio Devices - Realtek ALC AppleHDA [Guide].pdf
    ex., No audio devices, no sound, no codec No Sound - Realtek ALC AppleHDA [Guide].pdf
    ​ex., Audio devices present, no sound when selected
    No Audio After Sleep/Wake - Realtek ALC AppleHDA [Fixes].pdf
    ex., No audio devices on wake
    Surround Sound - Realtek ALC - AppleHDA [Guide].pdf
    ​​ex., Players, analog, optical
    Tools
    IORegistry Explorer (choose one) IORegistryExplorer_v2.1.zip (View Raw) IOJones MaciASL DPCIManager Kext Install utilities, i.e., Kext Wizard, Kext Utility, DPCIManager, etc. Troubleshooting - audio_ALC_guides
    See No Audio Devices - Realtek ALC AppleHDA [Guide].pdf See No Sound - Realtek ALC AppleHDA [Guide].pdf See No Audio After Sleep:Wake - Realtek ALC AppleHDA [Fixes].pdf Problem Reporting (Post to this thread with requested information attached)
    Description of audio problem OS X version/motherboard model/BIOS version/processor/graphics Procedure/Guide Used Copy of IOReg (Tools 1.) - File/Save a Copy As…, verify file (no ioreg.txt) Copy Of Console/All Messages  (last boot)/File/Save a Copy As..
    Installed S/L/E/AppleHDA.kext or AppleHDA8Series AppleHDAxxx kext Screen shots: DPCIManager/Status (Tools 3.) System Information/Hardware/Audio/Intel High Definition Audio (not Devices) Terminal/Shell/Export Test As. . .  (if script used) audio_realtekALC-100.command AppleHDA8Series.sh audio_cloverALC-100.command Chameleon Extra/org.chameleon.Boot.plist DPCIManager/Misc/Boot Log Extra/dsdt.aml (if installed)  Extra/ssdt.aml (if installed) Clover EFI/Clover/config.plist DPCIManager/Misc/Boot Log EFI/Clover/ACPI/Patched/dsdt.aml (if installed)  EFI/Clover/ACPI/Patched/ssdt.aml (if installed) Credit
    THe KiNG [HOW TO] Patch AppleHDA - Knowledge Base - Project OS X Forums
    PikeRAlpha New style of AppleHDA.kext patching for Yosemite | Pike's Universum
    abxite  http://applelife.ru/...06/#post-353647
    TimeWalker75a, Post # 20, No sound after waking from sleep
    RevoGirl
  22. Like
    ham4ever reacted to ludox in Guida Yosemite su Asus X52J Radeon 6370M 512MB Full   
    Yes Guide:
     
    http://www.insanelymac.com/forum/topic/306599-guida-installazione-asus-x52j-el-capitan/
  23. Like
    ham4ever reacted to ludox in Guida Installazione Asus X52J El Capitan   
    Iniziamo
     
    1- Per creare e preparare il boot Pendrive andate su questa topic c'è la guida con il Tools : http://www.insanelymac.com/forum/topic/306553-osx-1011-su-asus-z87-plus/
     
    NB: per quanto riguarda il boot dovete mettere la spunta su Clover Legacy
     
    2- Finito la procedura pendrive aprite il Clover_v2.3k_r3241 configurate come nelle foto riportate
    aggiungete nella cartella Kexts dell'EFI questi kexts
     
    EvOreboot
    FakeSMC
    NullCPUPowerManagement
     
    3- configurate il "Confg.Plist" come su questa guida: http://www.insanelymac.com/forum/topic/305356-guida-yosemite-su-asus-x52j-radeon-6370m-512mb-full/
     
    4- System Parameters su Inject Kexts=Yes
     
    6- dopo l'istallazione avviate per la prima volta con pendrive
     
    7- una volta avviato il sistema, installate il clover con la stessa procedura della pendrive, poi copiate EFI della Pendrive e lo mettete nell'EFI dell' HDD
     
    8- in fine avviate il OSX normale boot hardisk
     
    Se tutto e andato bene avete anche per OX 10.11 El Capitan Full-Profilo del vs Asus.
     
    Luigi





  24. Like
    ham4ever reacted to ludox in Guida Yosemite su Asus X52J Radeon 6370M 512MB Full   
    Amici del Forum sono riuscito finalmente dopo tanto lavoro di prove ecc, a far riconoscere al 100% compreso "Attivazione Accelleratore Grafico" la scheda Video Radeon 6370M 512MB con Yosemite 10.10.2

    Metto a disposizione la guida

    1- Aprire il Clover Configurator;
    2 - importate il config.plist;
    3 - portatevi sulla voce "Kernel and Kext Patches"
    - Su ATI Connectors Controller: 5000

    4 - Sulla voce "Graphics" scrivete queste informazioni:
    - FB Name : Hoolock
    - VRAM: 512 (questo numero si riferisce alla ram in dotazione alla scheda video in questo caso e 512MB)
    - Video Port: 1

    5 - Attivate la spunta su:
    Inject ATI=Yes
    LoadVBios=Yes
    Inject EDID=Yes

    6- portatevi sulla voce "Device"
    FakeID ATI: 0x68E01002

    7-portatevi sulla voce "SMBIOS"
    - MacBookPro6.2

    8- portatevi sulla voce "Boot"
    Attivate la spunta su: key-dev-mode=1

    9- Esportate il config.plist

    Riavviate e godetevi Full-Profilo VGA sul vs Asus.

    Credo che sia l'unica guida che esista su questo modello di Asus per Yosemite, perchè girando sul web su questo argomento nessuno e riuscito a risolvere.
    Spero con questa guida gli utenti che possiedono questo Notebook siano contenti di avere Yosemite

    NB: Chi ha ancora Yosemite 10.10.1 questa procedura non funziona, biosogna avere Yosemite 10.10.2 come all'inizio indicato.

    Posto alcune immagini

     l'aggiornamento OS X 10.10.3 è stato installato con successo.
     
    Luigi







  25. Like
    ham4ever reacted to Vlada. in [HOW TO] Modification of AMD FB + Clover injection   
    Mostly because of my partly success in making proper patch for all Radeon R9 270 Series GPU-s described in Radeon R9 270X FrameBuffer issue topic, but also because I see that many of you are still searching for some sort of help, I was coming to an idea to share some of my conclusions via this tutorial, in hope that it will resolve all of your current troubles. Once when you check this tutorial and you use it, you will understand better where is the problem and eventually, after you determinate what is what you will be able to fix it. It is important to say, that this tutorial is universal and it can be used for any AMD GPU.
     
    So lets start… 
     
    Modifying the AMD driver is one of the advanced hacker's technique, however, recently with clover in combination, the whole process can be reduced to a decent minimum. This tutorial aims to discover what specific digits in the code do and basically to educate so that everyone can make necessary modification alone and w/o further assistant. All you need is a bit of good will and some patience.
     
    ---------------------------------------------------------------------------------------------------------
     
    Extracting ROM file - Step 1 involves extraction of the original ROM file from your graphics card. This could be done from Windows by applications such as GPU-Z or some other similar, or from Mac OS X via DPCIManager application. Extracted ROM file you’ll need to save and then switch again in your Mac OS X.
     
    ---------------------------------------------------------------------------------------------------------
     
    Finding proper FB - Step 2 involves finding proper frame buffer that can be used by your GPU. In order to do this properly, we will need a terminal and corresponding ATI FrameBuffers script. We need this one to extract FB code inside AMDXXXXControllers.kexts. 
     
    Download ATI FrameBuffers php scripts by Pavo. Unpack the zip file on the desktop, then switch to terminal. Type php then simply drag the script in the terminal and press enter.
     
    What you’ll get is a long series of codes together with the exact names of the frame buffers inside certain AMD Controller kexts.
     
    Although by using this patching method we can modified any FB, it is recommended that you find the proper one for your GPU, which might already work with your card. The point with this is to locate those that contain the same number of connectors, so per example:   My GPU has 4 connectors: 2xDVI, 1xHDMI and 1xDP  -  so this means that I need to use FB with 4 connectors.   In the AMD personality dump file, just under the first line with FB name, we can find info that we need.   Personality: Futomaki ConnectorInfo count in decimal: 4   So this means that I should check those FB-s first.    Copy the code from the terminal in the Text Editor and save it on the desktop. Then take a look carefully extracted code, and write all frame buffers from the AMD Controller kext that drives your video card. For example, Radeon R9 270X that I’m using, is driven by AMD7000Controller.kext which containing the following list of frame buffers: MaguroS, Maguro, KaniS, Kani, Junsai, IkuraS, Ikura, OPM, Hamachi, Futomaki, Gari, Ebi, Dashimaki, Chutoro, Buri, Aji. For Radeon 6850HD it is necessary to look at the list of FB extracted from AMD6000Controller.kext, etc. ...
     
    Now that you have the names of FB-s you will need to determine which of them your card can use. The simplest way of doing this is Clover, although it is possible to do the same thing with Chameleon boot loader, but I'll be focusing exclusively this time on Clover.
     
    So open Clover Configurator and in the Graphics section of the FB Name field, type the first FB from your list. Then restart computer and reboot again in OS X. If all goes well, your graphics will work immediately (with or without GL quartz enabled), however, there are two more situations that may occur.
     
    First one is a situation where you will get a black screen, but the monitor will stays on. This also means that assigned FB works, but the connectors code inside dedicated AMD Controller kext is mismatched. In this situation pressing the ALT+CMD+Eject buttons on Apple keyboards and WIN+ALT+F12 on PC keyboards will simply sleep your computer. After waking from sleep your computer will activate the screen again. Basically, this is the one of the most common situation which requires further patching.
     
    In all other situations, most likely your monitor will automatically be switched off. This means that the assigned FB does not work, or another word that is not compatible with your GPU. In this situation my recommendation would be that you simply restart your computer. The best way to do that is to implement the software restart by pressing CTRL+CMD+Eject buttons on Apple keyboards or for PC keyboards that would be CRTL+ALT+F12, after which the computer will just restart immediately.
     
    By modifying Clover Boot options from its menu, where you can rename assigned FB or simply remove all enabled Graphics options that you are previously assigned, you will be able to re-boot OS X normally again. Basically, this is the part that will certainly take you some time before you discover which FB best suits to your card, but when you do this, you're ready for the next step.
     
    ---------------------------------------------------------------------------------------------------------
     
    FB Code Construction - Step 3 is the most important and involves modifying the original driver or more precisely, it considers changing hexadecimal values inside the driver that are defining the connector output signal from your graphic card.
     
    For this maneuver we will need correct values extracted from the existing ROM file, and that can be done through the two scripts: radeon_bios_decode  and redsock_bios_decoder scripts. It is necessary to use both because they are giving different results. Basically only with both results we can collect all the necessary data that we need.
     
    Scripts can be used in a similar way. You’ll need to open the terminal, drag the first script in a terminal then press once space, than type  <  than once space again and now drag your ROM file in the terminal and simply hit Enter. The obtained result will look something like this (example R9 270X)
     
    localhost:~ Vladimir$ /Users/Vladimir/Developer/Ati\ Workbench/AMD\ Graphics\ tool/Radeon\ BIOS\ decoders/radeon_bios_decode < /Users/Vladimir/Developer/Ati\ Workbench/AMD\ Graphics\ tool/AMD\ BIOS/Pitcairn.rom
     
    radeon_bios_decode will give the following result:


    ATOM BIOS Rom:   SubsystemVendorID: 0x148c SubsystemID: 0x2336   IOBaseAddress: 0x0000   Filename: E8B11LCC.HHW   BIOS Bootup Message: C63101 CURACAO XT 2GB GDDR5 64Mx32 E8B11LCC.HHW 2013 PCI ID 1002: 6810 Connector at index 0   Type [offset 43522]: DisplayPort (10)   Encoder [offset 43526]: INTERNAL_UNIPHY2 (0x21)   i2cid [offset 43632]: 0x90, OSX senseid: 0x1 Connector at index 1   Type [offset 43532]: HDMI-A (11)   Encoder [offset 43536]: INTERNAL_UNIPHY2 (0x21)   i2cid [offset 43659]: 0x92, OSX senseid: 0x3 Connector at index 2   Type [offset 43542]: DVI-I (2)   Encoder [offset 43546]: INTERNAL_UNIPHY (0x1e)   i2cid [offset 43696]: 0x95, OSX senseid: 0x6 Connector at index 3   Type [offset 43552]: DVI-I (2)   Encoder [offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15)   i2cid [offset 43696]: 0x95, OSX senseid: 0x6 Connector at index 4   Type [offset 43562]: DVI-D (3)   Encoder [offset 43566]: INTERNAL_UNIPHY1 (0x20)   i2cid [offset 43723]: 0x94, OSX senseid: 0x5 redsock_bios_decoder will give the following result:
    E8B11LCC.HHW: C63101 CURACAO XT 2GB GDDR5 64Mx32 E8B11LCC.HHW 2013 Subsystem Vendor ID: 148c   Subsystem ID: 2336 Object Header Structure Size: 355 Connector Object Table Offset: 48 Router Table Object Offset: 0 Encoder Object Table Offset: fd Display Path Table Offset: 12 Connector Object Id [19] which is [DISPLAY_PORT]   encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A]   encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true Connector Object Id [2] which is [DVI_I]   encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [2] which is [DVI_I]   encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 0x10 enc)] linkb: false Connector Object Id [4] which is [DVI_D]   encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Copy and paste the results into Text Editor and save it. Then extract the following items from both results like in this example by following the color order:
     
    01 [DISPLAY_PORT] 
    redsock_bios_decoder :
    enc obj 0x21 transmitter 0x12 dual link 0x2 enc 0x4
    radeon_bios_decode:
    Connector at index 0
    Type [@offset 43522]: DisplayPort (10)
    Encoder [@offset 43526]: INTERNAL_UNIPHY2 (0x21) 
    i2cid [@offset 43632]: 0x90, OSX senseid: 0x1
     
    Code construction: 12 04 01 01
     
    02 [HDMI_TYPE_A] 
    redsock_bios_decoder :
    enc obj 0x21 transmitter 0x22 dual link 0x2 enc 0x5
    radeon_bios_decode:
    Connector at index 1
    Type [@offset 43532]: HDMI-A (11)
    Encoder [@offset 43536]: INTERNAL_UNIPHY2 (0x21)
    i2cid [@offset 43659]: 0x92, OSX senseid: 0x3
     
    Code construction: 22 05 02 03
     
    03 [DVI_I] 
    redsock_bios_decoder :
    enc obj 0x1e transmitter 0x10 dual link 0x0 enc 0x0
    radeon_bios_decode:
    Connector at index 2
    Type [@offset 43542]: DVI-I (2)
    Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
     
    Code construction: 10 00 03 06
     
    04 [DVI_I] 
    redsock_bios_decoder :
    enc obj 0x15 transmitter 0x00 enc 0x10
    radeon_bios_decode:
    Connector at index 3
    Type [@offset 43552]: DVI-I (2)
    Encoder [@offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15)
    i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
     
    Code construction: 00 10 04 06
     
    05 [DVI_D] 
    redsock_bios_decoder :
    enc obj 0x20 transmitter 0x11 dual link 0x1 enc 0x2
    radeon_bios_decode:
    Connector at index 4
    Type [@offset 43562]: DVI-D (3)
    Encoder [@offset 43566]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 43723]: 0x94, OSX senseid: 0x5
     
    Code construction: 11 02 05 05
     
    Now let's look at the original source code extracted from the original driver for the FB Futomaki that activates R9 270X:
     
    Personality: Futomaki 10.9.2
    ConnectorInfo count in decimal: 4
    Disk offset in decimal 811280
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01
    00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02
    04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06
    00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03
     
     
    Each row represents definition for the one connector. In this case we have 4 of them.
    In order to better understand what is what I will separate first line from the code as an example:
     
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01
     
    Divided into segments:
     
    00 04 00 00 / Connector type
    04 03 00 00 / ATY, ControlFlags
    00 01 01 01 / Features
    12 / Transmitter
    04 / Encoder
    04 / hotplug ID
    01 / Sense ID
     
    What this means?
     
    First I’ll put the list of all types of connectors:
     
    Connector Type LVDS 0 × 00000002 = 02 00 00 00 Note: Laptop Monitor
    Connector Type DVIDL 0 × 00000004 = 04 00 00 00 Note: Dual Link DVI
    Connector Type VGA 0 × 00000010 = 10 00 00 00
    Connector Type SV 0 × 00000080 = 08 00 00 00
    Connector Type DP = 0 × 00000400 00 04 00 00
    Connector Type HDMI 0 × 00000800 = 00 08 00 00
    Connector Type DVISL 0 × 00000200 = 00 02 00 00 Note: Single Link DVI
     
    So now it's clear that first 4 pair of numbers represents the type of connector in the code:
     
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 / Display Port
    00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 / Display Port
    04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 / DVI-D
    00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 / HDMI
     
    Constructed FB is made this way, mostly due to the fact that Apple monitors are using DP as the primary connection and then we have beneath in order all others.
     
    In the vast majority of cases there, you will need to change only the last 4 digits, which are also the most important for proper connector injection, or eventually you will need to assign further a DVI-I (SL) connection for your monitor. In this case, it is basically a mandatory thing mostly because the original code does not have it. Therefore, we will need to change the second row from DP into DVI-SL.  The initial input of first four pairs of digits we will need to change from 00 04 00 00 to 00 02 00 00, which is the proper input for DVI-SL.
     
    00 02 00 00
     
    Then follows the explanation of the second set of digits:
     
    0×0002 : LVDS               ControlFlag : 0×0040 and 0×0100
    0×0004 : DVI                  ControlFlag : 0×0016, 0×0014, and 0×214
    0×0010 : VGA                ControlFlag : 0×0010
    0×0080 : S-Video           ControlFlag : 0×0002
    0×0200 : DVI                  ControlFlag : 0×0014, 0×0214, and 0×0204
    0×0400 : DisplayPort     ControlFlag : 0×0100, 0×0104, 0×0304, 0×0604, and 0×0400
    0×0800 : HDMI               ControlFlag : 0×0200 
    0×1000 : DVI                   ControlFlag : 0×0016
     
    Translated in to:
     
    Connector Type DP 04 03 00 00
    Connector Type DP 04 03 00 00
    Connector Type HDMI 00 02 00 00
    Connector Type DVIDL 14 02 00 00
    Connector Type_DVISL C 04 02 00 00
    Connector Type_DVISL 04 02 00 00
     
    From this example it is clear that in the modified row we should add further 04 02 00 00 according to the matched connector name. So after first 00 02 00 00 we will need to add the following 4 pair of digits 04 02 00 00 and all together it looks like this:
     
    00 02 00 00 04 02 00 00
     
    The following is the part that relates to the ATY,Features (hex digits):
     
    The first pair of numbers:
     
    0 × 0002: LVDS * 0x09 = 09
    0 × 0004: DVI 0x00 = 00
    0 × 0010: VGA 0x00 = 00
    0 × 0080: S-Video 0x04 = 04
    0 × 0200: DVI 0x00 = 00
    0 × 0400: Display Port 0 × 00 = 00
    0 × 0800: HDMI 0 × 00 = 00
    0 × 1000: DVI 0x00 = 00
     
    The second pair of numbers:
     
    Use Internal * 0 × 01 = 01
    Use RGB YUV On 0 × 04 = 04
    Use Backlight * 0 × 08 = 08
    Backlight Inverted 0 × 10 = 10
    Use Clamshell 0 × 20 = 20
     
    A third pair of numbers represents the order of connector activation
     
    01 = first active connector
    02 = second active connector
    03 = third active connector
    etc. ...
     
    I suggest that you mark as first, connector raw that your monitor will use it as primary. 
     
    The fourth two numbers are listed as Unknown:
     
    You can leave the same like in the original code (usually stands 01 or 00) or simply replace it with zeros - 00. I will in this demonstration left the original values:
     
    Finally, we add the following digits:
     
    00 02 00 00 04 02 00 00 00 01 01 01
     
    Last four digits simply rewrite from the above constructed table:
     
    03 [DVI_I] 
    redsock_bios_decoder :
    enc obj 0x1e transmitter 0x10 dual link 0x0 enc 0x0
    radeon_bios_decode:
    Connector at index 2
    Type [@offset 43542]: DVI-I (2)
    Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
     
    Code construction: 10 00 03 06
     
    I will explain in short, what is what here, but that would not be important much anyway. The only one thing important it is the order of digits that we need to use and the patch will work. So here it is:
     
    Transmitter - the first two digits
    Encoder - the second two digits
    Hotplug ID - third two digits
    Sense ID - Fourth two digits
     
    ---------------------------------------------------------------------------------------------
     
    So that was detail explanation, however, we can simplify this procedure by using next basic code schematics per connector:
     
    LVDS / 02000000 40000000 08010000 / + (add your code construction)
    VGA / 10000000 10000000 00010000 / + (add your code construction)
    DP / 00040000 04030000 00010000 / + (add your code construction)
    DVI-SL / 00020000 04020000 00010000 /  + (add your code construction)
    DVI-DL / 04000000 14020000 00010000 /  + (add your code construction)
    HDMI / 00080000 00020000 00010000 / + (add your code construction)
     
    As you can see, all you have to do is to add the last 8 digits which you need to construct by yourself (see example above)
     
    Sierra is using additional digits in the code, so you'll need to add extra zero segments in front of your code construction and after it. Check example bellow:
     
    00080000 00020000 00010000 00000000 + (add your code construction) 00000000
     
    -----------------------------------------------------------------------------------------------
     
    So this is it, and here we have final construction.
     
    00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06
     
    Except for the above modification, like I said, in most cases you will need to replace only the last four values:
     
    Original code:
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 - DP
    00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 - DP
    04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 - DVI-DL
    00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 - HDMI
     
    Modified code:
     
    00 04 00 00 04 03 00 00 00 01 02 01 12 04 01 01 - DP
    00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06 - DVI-I
    04 00 00 00 14 02 00 00 00 01 03 00 11 02 05 05 - DVI-D
    00 08 00 00 00 02 00 00 00 01 04 00 22 05 02 03 - HDMI
     
     
    With this, the whole thing is completed and you are now ready for the final step.
     
    ---------------------------------------------------------------------------------------------------------
     
    Clover Injection - Step 4 involves injection of the code and its activation.
     
    This can be done in several ways: kext patching by some hex tool or making the Binary patch, however, none of these methods are sufficiently elegant, mostly because in this case we will need to patch driver every time when we make system upgrade.
     
    Luckily we have a Clover, which is able to apply such modification "on the fly" which is ideal concept, or other words, this method represents a permanent solution that does not depend from the future system upgrades.
     
    Open Clover Configurator, and go to the Kernel & Kext patches. Click on the plus sign in the KextsToPatch field :
     

     
    Then type the name of the kext you want to patch, in this case this is AMD7000Controller. In the next field, enter the original hex code extracted from the driver, and next to it write a new one that you have created. Eventually, you can add notes in the next field (par example: Connectors patch) and that was it. You are ready for testing.
     

     
    If you are all done properly everything will work from the first attempt. If not you will need to work further on it. But if something goes wrong, you can always change the name of the FB or simply to uncheck the options that you have activated in the Graphics panel and thus everything will be back to its initial state.
    Decoders.zip
    ATI-framebuffers.zip
×