Jump to content

limurphy

Members
  • Content Count

    45
  • Joined

  • Last visited


Reputation Activity

  1. Like
    limurphy got a reaction from HUSABER in [GUIDE] EL Capitan / Sierra / High Sierra / Mojave / Catalina on Intel LGA 775 motherboards / DSDT   
    For those who wants to install Sierra with a Xeon CPU, must boot with arg npci=0x3000 also with VoodooTSCync.kext (IOCPUNumber = x -1 ;where x is no. of thread) .This is what I do. Of course you may have to mod your mobo bios with SSE4.1 microcode.
  2. Like
    limurphy reacted to crazybirdy in How to download the full installer   
    Download the dmg file and try this script inside it, Q6-DownloadFullApp/installScript_1014fullapp
  3. Like
    limurphy reacted to fantomas in [pre-release] macOS Mojave   
    Let me retry with my HD6770 'cause I failed the first time... I want to try the same method as for my HD4830.
     
    The big deal it is to be sure that your needed kexts are in the kext cache. For that, boot in  single user mode in first, give permissions for your kexts (chmod + chown bla bla), load them (kextload -v), then rebuild prelinked kernel (kextcache system-prelinked-kernel), then reboot.
     
    Now do your patch on the fly (boot with no_cache, patch your kexts [amd4800controller.kext and atiradeonx2000.kext in my case], check debug option) and it should be good.
     
    For my HD4830, the binary patch (atiradeonx2000.kext) is the same as for HS... take a look.
  4. Like
    limurphy reacted to fantomas in Apple released macOS 10.13.3 Update   
    This update:
    Addresses an issue that could cause Messages conversations to temporarily be listed out of order Resolves an issue that could cause your Mac to stop responding when connected to an SMB server  
    Update
     
    Combo
     
    iMac Pro
     
    Click here to view the article
  5. Like
    limurphy got a reaction from macinsane in [SUCCESS] Gigabyte EP43-DS3L High Sierra on obsolete hardware   
    I have a mobo almost same as yours,EP45-UD3R and I modded it from 775 to 771.After updated Clover to v4334, I also update from 10.13.1 to 10.13.2.Everything  works ok.
     
    mobo : EP45-UD3R
    CPU  :  E5450
    Ram  :  8g
    GPU  : ATI 4850 512g
    SSD  : ADATA 120g
  6. Like
    limurphy got a reaction from SiddRamesh in [HOW TO] Modification of AMD FB + Clover injection   
    ATOM BIOS Rom:
        SubsystemVendorID: 0x104d SubsystemID: 0x908a
        IOBaseAddress: 0x0000
        Filename: BR41199.024
        BIOS Bootup Message:
    Sony/Wistron Z50CR ThamesPro DDR3                                           
     
    PCI ID: 1002:6841
    Connector at index 0
        Type [@offset 16006]: LVDS (7)
        Encoder [@offset 16010]: INTERNAL_UNIPHY (0x1e)
        i2cid [@offset 16080]: 0x96, OSX senseid: 0x7
    Connector at index 1
        Type [@offset 16016]: HDMI-A (11)
        Encoder [@offset 16020]: INTERNAL_UNIPHY1 (0x20)
        i2cid [@offset 16103]: 0x90, OSX senseid: 0x1
    Connector at index 2
        Type [@offset 16026]: VGA (1)
        Encoder [@offset 16030]: INTERNAL_KLDSCP_DAC1 (0x15)
        i2cid [@offset 16130]: 0x97, OSX senseid: 0x8
     
     
    BR41199.024 :
     
    Sony/Wistron Z50CR ThamesPro DDR3                                           
     
    Subsystem Vendor ID: 104d
           Subsystem ID: 908a
    Object Header Structure Size: 199
    Connector Object Table Offset: 34
    Router Object Table Offset: 0
    Encoder Object Table Offset: 99
    Display Path Table Offset: 12
    Connector Object Id [14] which is [LVDS]
        encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
    Connector Object Id [12] which is [HDMI_TYPE_A]
        encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
    Connector Object Id [5] which is [VGA]
        encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
     
     
    LVDS    :  10 00 01 07
    HDMI    :  11 02 02 01
    VGA     :  00 10 03 08
     
    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 04020000 00010000 / + (add your code construction)
     
    From AMD6000Controller.kext:
    Ipomoea (3)
    DP, HDMI, VGA
    orig:
    00040000040300000001000012040105
    00080000040200000001000011020403
    10000000100000000001000000000002
     
    fix:
    02000000400000000801000010000107
    00080000040200000001000011020201
    10000000100000000001000000100308
     
     
     
     
     
    DSDT.aml.zip
  7. Like
    limurphy reacted to macinsane in [SUCCESS] Gigabyte EP43-DS3L High Sierra on obsolete hardware   
    Update: Now running Mojave! Thanks to mojave2core! Yeah   Still using C2D in 2019!
    Inserted a nice and cheap GT710 that is not relying on nVidias Webdrivers and runs OOB under Mojave.
     
    Nice, seeing High Sierra running on this old but capable system! It rocks with a new ASUS GT1030
     
    Config:
    Gigabyte EP43-DS3L
    Core2Quad Q9300
    6 GB DDR2 RAM
    Asus GT1030 2GB
    Sandisk SSD 128GB
    TP-Link AC1200 Wifi USB
    Inateck KT4006 USB 3.0 PCIe (No boot)
     
    SMBIOS: iMac14,1
    Clover: 4297  4360
     
    A good deal of DSDT editing was necessary to get this machine to boot High Sierra but finally it works flawlessly, even sleep and wake!
    You NEED to have the DSDT put in place for installation because otherwise macOS doesn't recognize the SATA ports.
    There are a few important BIOS settings: SATA hast to be set to AHCI and "native" and HPET has to be run "64-bit", I'd recommend to disable IDE and the serial and parallel port.
    For the GT1030 nVidia Webdrivers are needed, have to boot with nv_disable=1 until you have them installed.
    You have to install Clover in legacy mode because this old fella does not support UEFI.
     
    Only downside: The so often recommended Inateck USB-card isn't recognized by BIOS, so you cannot boot from it. It works perfectly within macOS though, have the ac-Wifi connected to it.
    config.plist.zip
    DSDT.aml.zip
  8. Like
    limurphy 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
  9. Like
    limurphy got a reaction from HUSABER in Gigabyte GA EP45UD3R   
    I have succeed fresh install High Sierra on my old mobo EP45UD3R.All credits to fusion71au.I just follow his instruction : http://www.insanelymac.com/forum/topic/308034-how-to-create-a-macos-installer-which-doesnt-need-bootloader-kext-injection-fakesmc-in-pre-linked-kernel-bypass-high-sierra-firmware-and-mbr-check/
     

  10. Like
    limurphy reacted to Blaggah in [GUIDE] EL Capitan / Sierra / High Sierra / Mojave / Catalina on Intel LGA 775 motherboards / DSDT   
    I'm still facing the sound stuttering and choppiness on my P35-DS3L. I don't think I'm gonna keep that board much longer because it's giving me the creeps. I'll just sell it and get me some SSD with the profit. I've only paid $30  from craigslist and it came with a super nice case too. I'll go back to my ASUS 775 board for now and call it a day.  Thanks for your response limurphy.
  11. Like
    limurphy got a reaction from MaLd0n in [GUIDE] EL Capitan / Sierra / High Sierra / Mojave / Catalina on Intel LGA 775 motherboards / DSDT   
    Hi passoporto:
    I followed the guide from the following website:
    http://www.overclock.net/t/1431723/mod-lga775-support-for-lga771-xeon-cpus
    I have Yosemite (10.10.5) & Sierra (10.12.5) on my SSD , both work fine.I even don't need FakeCPUID .From the photo attached,you can see cpuid : 00010676 patch id : 060F
     


    Hi Blaggah :I don't have the sound problem. For sound,it was ALC889A(same as ALC885) ,I have installed AppleALC. I use Clover with DSDT.
  12. Like
    limurphy got a reaction from Blaggah in Xeon Mac Pro 3.1   
    voodootscsync-configurator:
     
    http://www.insanelymac.com/forum/topic/323366-voodootscsync-configurator-create-a-custom-version-of-voodoo-tsc-sync/?hl=%2Bvoodootscsync&do=findComment&comment=2421765
  13. Like
    limurphy got a reaction from MaLd0n in Asus P5k-VM pre install hang with ++++++   
    Unless you modify LGA775 to  LGA771.
  14. Like
    limurphy got a reaction from MaLd0n in [GUIDE] EL Capitan / Sierra / High Sierra / Mojave / Catalina on Intel LGA 775 motherboards / DSDT   
    Hi passoporto:
    I followed the guide from the following website:
    http://www.overclock.net/t/1431723/mod-lga775-support-for-lga771-xeon-cpus
    I have Yosemite (10.10.5) & Sierra (10.12.5) on my SSD , both work fine.I even don't need FakeCPUID .From the photo attached,you can see cpuid : 00010676 patch id : 060F
     


    Hi Blaggah :I don't have the sound problem. For sound,it was ALC889A(same as ALC885) ,I have installed AppleALC. I use Clover with DSDT.
  15. Like
    limurphy got a reaction from Blaggah in Xeon Mac Pro 3.1   
    voodootscsync-configurator:
     
    http://www.insanelymac.com/forum/topic/323366-voodootscsync-configurator-create-a-custom-version-of-voodoo-tsc-sync/?hl=%2Bvoodootscsync&do=findComment&comment=2421765
  16. Like
    limurphy got a reaction from MaLd0n in [GUIDE] EL Capitan / Sierra / High Sierra / Mojave / Catalina on Intel LGA 775 motherboards / DSDT   
    I had succeed to install Sierra on my old mobo Giga EP-45 UD3P  with modded BIOS for Xeon E5450 CPU.
  17. Like
    limurphy got a reaction from ricoc90 in Apple releases macOS 10.12.5 update   
    My old mobo Gigabyte GA-EP45UD3P + Xeon E5450 also can run on this version(Sierra).
     


  18. Like
    limurphy got a reaction from MaLd0n in [GUIDE] EL Capitan / Sierra / High Sierra / Mojave / Catalina on Intel LGA 775 motherboards / DSDT   
    I had succeed to install Sierra on my old mobo Giga EP-45 UD3P  with modded BIOS for Xeon E5450 CPU.
  19. Like
    limurphy got a reaction from kosakgroove in [HELP] Fix battery percentage in DSDT Lenovo L420   
    I have modified your patch
    dsdt.zip
  20. Like
    limurphy reacted to rockinron_1 in [Guide] The all-in-one guide to Vanilla OS X (including Chameleon + DSDT) for beginners (updated for Yosemite!)   
    *****NOW UPDATED FOR YOSEMITE - PLEASE REPORT ANY PROBLEMS IN THE COMMENTS*****
     
    *****There are subtle differences in the guide depending on whether you’re using Lion / Mountain Lion or Mavericks*****
    *****For Lion / ML use the blue line. For Mavericks use the red line. For Yosemite use the green line.*****
     
    *****If you're creating the installer for Lion/ML use "Essential 03.08.2012" attachment*****
    *****Otherwise use the attachment for the version you’re using*****
     
    *****This guide will not work for versions of OS X earlier than Lion (10.7)*****
     
    The all-in-one guide to vanilla OS X + Chameleon + DSDT for beginners
     
    Preface:
    So I’ve built a few hackintoshes now to the point where I’ve a good idea what I’m doing. I’ve gone the distro way before as well as the vanilla way and I agree fully with the idea that vanilla is better. The problem with it being that I haven’t found a well explained start to finish guide of how to do it without a lot of Googling and combining numerous different guides so my idea is to collate everything into one place for beginners to hopefully understand the process better and build better systems. A lot of the leg-work for this guide has been done by other people; although I’m rewriting most of it if anyone wants credit adding to something I’ve accidentally stolen from them just PM me. Throughout the guide I try to avoid scripts and utilities so you can learn what your doing. If you want a one-click install this is not the guide for you; having said that there is nothing technically complicated that isn’t clearly explained so don’t be scared off if you’re a rookie.
    If any one has any suggestions on how to improve this guide PM me or mention it on the forum thread.
    Those who experience problems make sure you’ve read Part 7 before posting to the forum asking for help.
     
    Part 1 - Prerequisites
    1.0. Basic Requirements:
    The basic requirements for OS X from Lion onwards are:
    1. A Core 2 Duo processor or later
    2. 2GB or more RAM
    3. 8GB of disk space
    N.B. For details of specific hardware compatibility see the hardware compatibility list (HCL) in the wiki:
    http://wiki.osx86project.org/wiki/index.php/Main_Page
     
    Further to compatible hardware you will need:
    1. A working install of OS X (this may be in a virtual machine or a native install) to prepare the installer
    2. A flash drive of minimum size 8GB
    3. A copy of Lion / ML / Mavericks
    4. Patience
     
    Note: All essential software / kexts below are in the attachment.         
    1.1. Essential Software
    You will need to obtain the following. I suggest you place them all in the same folder along with the essential kexts below for use later:
    1. The Chameleon boot loader, the latest version of which can always be found here (You want "The Latest Trunk PKG ~ Standard and Official Revision"):
    http://www.insanelymac.com/forum/index.php?showtopic=231075
    2. Chameleon wizard to create a smbios (basically identify your machine as a mac) and to help with bootloader problems
    http://www.insanelymac.com/forum/index.php?showtopic=257464
    3. System info for finding device ID’s for general post-install troubleshooting (Check you get the Mac version).
    http://www.insanelymac.com/forum/index.php?showtopic=219584
    4. DSDT editor for extracting your DSDT once were up and running:
    http://www.insanelymac.com/forum/index.php?showtopic=223205
    5. Kext utility for installing additional kexts post-install:
    http://cvad-mac.narod2.ru/Kext_Utility/
    1.2. Essential Kexts (kernel extensions)
    1. FakeSMC – absolutely essential – tricks OS X into thinking it’s a real Mac.
    http://www.projectosx.com/forum/index.php?showtopic=1643
    2. NullCPUPowerManagement – generally required initially to prevent kernel panics, may not be needed once AppleIntelCPUPowerManagement is patched after install.
    http://www.osx86.net/view/16-nullcpupowermanagement_(32--64-bit).html
     
    Part 2 - Creating the installer
    2.0. Preparing the USB
    1. In your working OS X install open Disk Utility
    2. Click on your USB drive in the left sidebar
    3. Click the “Partition” tab
    4. Under “Partition Layout” click “1 Partition”
    5. Click Options -> select “GUID Partition Table”; check the format is set to “Mac OS X Extended (Journaled)”; name it “USB” and click Apply

     
    2.1. Creating the OS X installer on the USB drive
    1. Mount your OS X DMG. If using a copy downloaded from the app store: Navigate to Applications (which is where it will save your downloaded copy of OS X by default) -> right click "Install OS X *version*" and click "Show Package Contents" -> Contents -> SharedSupport -> Double click "InstallESD.dmg"
    2. Mount BaseSystem.dmg by typing the following in terminal:
    open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg
    open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg
    open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg
    3. Go back to disk utility and click on “(Mac )OS X Base System”, click the “Restore” tab then drag and drop “(Mac )OS X Base System” to “source” and your USB to “destination” and click restore then erase. This will take a while.
    4. You’ll now have 2 “(Mac )OS X Base Systems present in Finder, right click them and “get info” to determine which is your USB drive (hint: look at the size).
    5. Navigate to the one which is your USB drive, open it and go to /System/Installation. Delete the “Packages” link then create a folder called “Packages”.
    6. Open a new Finder window and navigate to “(Mac )OS X Install ESD”. Copy everything inside the packages folder to the packages folder you have just created. This will take a while.
    7. Copy mach_kernel from “OS X Install ESD” to the root of your USB drive.
    7. Use pacifist to extract mach_kernel from “OS X Install ESD/Packages/BaseSystemBinaries.pkg” and copy it to the root of your USB drive (note: this is in the attachment).
    7. Use pacifist to extract kernel from “OS X Installed ESD/Packages/Essentials.pkg/System/Library/Kernels/Kernel” and copy it to /System/Library/Kernels/ (You may need to create the “Kernes” folder) (note: this is in the attachment).
    8. Copy BaseSystem.chunklist and BaseSystem.dmg from InstallESD.img to the root of your USB drive. Since these files are hidden you must first show hidden files by typing the following in Terminal "defaults write com.apple.Finder AppleShowAllFiles YES" followed by "killall Finder". Once copied you can type "defaults write com.apple.Finder AppleShowAllFiles NO" followed by "killall Finder" to hide hidden files.

     
    The terminal will look something like this when you are done:

     
    2.2. Patching the installer for a PC
    1. Remember the two kexts we downloaded above? Copy both of them to /System/Library/Extensions on your USB stick.
    2. Run the chameleon installation package and ensure to choose your USB drive as the destination.
    3. Go to the root of your USB drive and create a folder called “Extra”. This is used to store configuration files for the chameleon boot-loader.
    4. Open Chameleon wizard, click the “SMBios” tab then click "Edit". Now there is a list of “Premade SMBioses”. Look through this list to see which relates best to your PC (Hint: iMac 12.2 for modern desktops or MacBook Pro 8.3 for modern laptops is a good place to look to start with). Click “Save As” and save it to the /Extra folder we created on the USB stick.
    N.B. make sure you’ve got a smbios from a Mac which supports your version of OS X, for a list of which do see here: http://www.apple.com/osx/specs/
    5. Use chameleon wizard to generate an “org.chameleon.boot.plist” this is necessary to set the kernel flag “kext-dev-mode=1” which allows us to boot using unsigned kexts. If you already have an org.boot.chameleon.plist you may simply add “kext-dev-mode=1” to your list of kernel flags. If not then use the one from the attachment. Copy this file to the /Extra folder we created on the USB stick.
    6. Copy your folder of essential software & kexts to the root of your USB stick.
    N.B.1: For those with a fully-working Lion / ML install you may omit 2.C.3. & 2.C.4. and use your old /Extra folder (including smbios & org.chameleon.boot.plist & DSDT).
    N.B.2: ATi6xxx users see step 7.6 now!




     
    2.3. A note for those wishing to boot OS X and Windows on the same HDD
    (This is not recommended but may be necessary for those installing on laptops)
    The OS X installer won’t install to an MBR partition scheme which Windows requires so we must patch the installer to allow this. If you intend on dual-booting OS X and Windows 7 then I suggest you install Windows 7 and update to Service Pack 1 before you install OS X to prevent problems updating to SP1 later. How to patch:
    1. Download the required files from here:
    http://www.osx86.net/view/2815-osinstallmbr+osinstall.mpkg_10.8.gm.html
    2. On the USB stick navigate to /System/Installation/Packages/. Delete OSInstall.mpkg and replace it with the one you just downloaded.
    3. On the USB stick navigate to /System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/. Delete OSInstall and replace it with the one you just downloaded.
     
    Part 3 – Installing OS X
    3.1 Installing OS X
    1. Stick the USB drive in the computer you wish to install OS X on and boot from your USB drive. If you’re unsure how to do this when your computer first turns on look for a prompt that says “Press X for boot selection menu” (where X is a key) or something of that effect. Common keys are F8 & F12.
    2. When Chameleon comes up press enter to boot OS X. The OS X installer should boot. Go to the utilities menu and click disk utility. Select the disk / partition you wish to install OS X to, call it "OS X" and format it as “Mac OS X Extended (Journaled)” (See Part 2.1. if you’re a bit rusty with disk utility).  
    N.B. For those dual booting on the same HDD as Windows ensure you've got the Partition Scheme set to MBR.
    3.  Follow the installer to install OS X to the desired partition.
    4. Take a well-deserved rest while it installs.
    5.  Once the installer is finished it will reboot, on reboot boot back into the install USB NOT your OS X install.

    3.1 Fixing the OS X install
    1. From the installer go to Utilities and Terminal.
    2. Type cp –R /System/Library/Extensions/NullCPUPowerManagement.kext /Volumes/"OS X"/System/Library/Extensions/
    3. Type: cp –R /System/Library/Extensions/FakeSMC.kext /Volumes/"OS X"/System/Library/Extensions/
    4. Type reboot
    NOTE: Include the quotes in the lines above. This assumes your install partition is called “OS X” as I said above. If for whatever reason you called it something else replace “OS X” with whatever you called it (still surrounded by quotation marks).

    Part 4 – Initial booot
    1. Reboot your system and boot to the USB stick again but this time select your OS X install. This should boot you into your installed copy of OS X.
    2. Open "System Preferences" go-to "Security and Privacy", click the lock and give it your password then set "Allow applications downloaded from" to anywhere.
    3. Navigate to your folder of essential software and run the chameleon package, install it to your OS X drive.
    4. Copy the Extra folder on your USB drive to the root of your HDD (open Finder -> Go -> Computer -> OS X -> paste folder).
    5. Reboot, remove USB, and let the computer boot from your HDD, select OS X and it should boot straight to OS X.
    You are not finished! You now need to at least read through step 6!
     
    Part 5 – DSDT
    5.0 Extraction
    Although not strictly required it is useful to have a DSDT for your system; with a bit of research and patching it can be used to solve almost all problems you may encounter.
    For those interested in what it actually is see here:
    http://wiki.osx86pro.../index.php/DSDT
    How to create it:
    1. Open DSDT Editor
    2. Go-to File -> Extract DSDT
    3. Go-to to IASL -> Compile (if you get any errors click “Fix Errors”)
    4. Go-to IASL -> Save AML as. Save it as “DSDT.aml” in /Extra.

    5.1 Common Fixes
    (coming soon eventually…)
     
    Part 6 – Finishing Touches
    6.0. A note on non-Mac monitors
    Most non-Mac monitors will start with the wrong color calibration. To fix this go-to "System Preferences" -> "Displays" -> "Color" -> select "Generic RGB Profile".
    Further to this, due to Mac monitor having a different dot pitch to normal monitors, LCD font smoothing may make the fonts appear blurred. To turn this off go-to “System Preferences” -> General -> uncheck “Use LCD Font…” (at the bottom).
     
    6.1. Keymaps
    If you have a British standard keyboard you will need to install the keymaps in the attachment. To do so decompress the attached zip and copy its contents to /Library/Keyboard Layouts then change the keymap by going to System Preferences -> Keyboard -> Input Sources.
     
    6.2. org.chameleon.boot.plist
    If you open Chameleon Wizard you can navigate to “org.chameleon.boot” here you can assign numerous settings which will be useful later as well as setting the default timeout and specifying the location of your SMBios and DSDT if you don’t place them in /Extra. I suggest you ensure the “Ethernet Built In” box is checked then set the "Time Out" to a reasonable figure and then click "Save As' and save it to /Extra (Note: save it as org.chameleon.boot, it automatically appends the .plist extension).
    When you've saved it you can go to "Theme" and download and apply a theme for the boot loader rather than having the default text boot.
    Once your system is stable and with all necessary hardware enabled set UseKernelCache=Yes to speed up boot times.

     
    6.3. NullCPUPowerManagement
    Currently we have NullCPUPowerManagement.kext installed. This disables speed-stepping and thus sleep (by disabling AppleIntelCPUPowerManagement.kext) so we need to remove it for a better system. Unfortunately not all system’s will work with the version that comes with OS X. The first thing to do is to try your system without it, to do this simply navigate to /System/Library/Extensions on your OS X drive and delete it then reboot. It’s possible you will see a kernel panic on reboot, if this is the case you will need to reinstall the kext by following Part 3.1.1&3.1.2.
    If your system panics on boot then you require a patched version of AppleIntelCPUPowermanagement; reading round the forum should allow you to obtain this relatively easily.

    6.4. Device Compatibility
    At this point it’s very likely you will have some devices not working. The best way to get devices working is through DSDT edits rather than by adding kernel extensions; often additional kernel extensions will have to be re-installed after updates whereas DSDT edit are permanent.
    To enable devices by using additional kexts: Run the “System Info” app we downloaded and click File -> check compatibility. This will let you see which devices are working and which aren’t. You can Google your vendor & device ID to find info about making them work. Once you find a kext that appears to be compatible for your hardware drag and drop it onto kext utility to install it.
    Example: If your Wi-Fi isn’t working you can look for your Wi-Fi device and find its device / vendor ID’s in my case its vendor ID is 168c and its device ID is 002a so Googling for “168c:002a kext” would return results about making the device work.

    6.5. Finder grid view (windows explorer behaviour)
    To make finder sort files in a grid by default open Finder, navigate to your root folder of the OS X install. Go-to View -> Show View options -> Arrange by "Name" -> Click "Use As Defaults"
     
    Part 7 – Common Errors & Basic Diagnostics
    7.0. Boot0:Error
    Boot0 error is most likely caused by incorrectly installing chameleon or having a drive with 4k-sector allocation. Try to reinstall chameleon (use the latest version!), if that doesn’t work see here:
    http://www.macbreaker.com/2012/02/hackintosh-boot0-error.html
     
    7.1. Boot flags
    When the chameleon screen boots you can specify kernel arguments to attempt to solve problems you may be having. When you see the boot-loader pop up press any key and ensure your OS X install is highlighted. You can then type any combination of kernel flags (with a space between them) to try to boot OS X / diagnose problems. For a complete list of kernel flags see here:
    http://www.osx86.net/guides-tutorials/10747-guide-chameleon-bootloader-basics.html
    A few of the more common ones are:
    1. –v verbose mode. If the system panics take a screen shot of the panic when you have typed this at boot and post it to the forums. It will help people diagnose your problems but won’t fix any problems.
    2. –x safe boot (like windows safe mode – minimal drivers).
    3. –f boot without the kernel cache (useful if you’ve installed kexts without rebuilding the kext cache – if you’ve used kext utility you shouldn’t have to use this).
    4. –npci=0x2000 (or –npci=0x3000) fixes the “PCI configuration Begin” error.
    5.  PCIRootUID=0 solves problems for some NVIDIA graphics card users (if it doesn't solve your issue try =1 instead).
    6. GraphicsEnabler=Yes (or GraphicsEnabler=No) add support for some non-OS X graphics cards.
    7. Note: The arch=i386 boot flag is now depreciated due to ML’s 64-bit only kernel.

    7.2. The console
    The console gives you a verbose output of any and all errors the system may encounter. It's particularly useful if you've a system which won't stay in sleep mode. Go-to Applications -> Utilities -> Console to open it.
     
    7.3. App store "Your device or computer could not be recognised..." error.
    App-store requires a MAC address to verify your computer (any address, it doesn't have to be an apple one) hence you MUST have a working Ethernet or Airport card for App Store to work. The problem is if you've enabled network hardware after first boot OS X won't update its caches. The fix: 
    Ensure "ethernet buit in" is checked in your org.chameleon.boot.plist. Go to system preferences and delete all the devices in the network section. Navigate to /Library/Preferences/SystemConfiguration and delete com.apple.airport.preferences.plist and networkinterfaces.plist and com.apple.boot.plist. Reboot then add your network interfaces in system preferences. Check app-store is now working.
     
    7.4 Motherboard POST Freeze
    I your motherboard freezes during POST (you don’t even get past the BIOS screen) it’s possible your BIOS isn’t compatible with the GUID partition table of the USB we created the installer on. To fix this in step 2.0.5 select MBR instead of GUID.
    Note: If you make it to the OS X boot-loader this is not your problem and will not fix any issues other than hanging at POST. For more information see here:
    http://www.rodsbooks.com/gdisk/bios.html
     
    7.5 When posting to the forum asking for help
    When posting to the forum asking for help if the installer / installation won’t boot please post a screenshot of where it stops – I suggest you post this to a new thread in a suitable place in the forum rather than this guide.
     
    7.6 ATi6xxx card white screen error
    There is a know permissions error in Mountain Lion regarding the ATi6000Controller kext causing white screen. To fix this:
    Navigate to /System/Library/Extensions on your install USB and copy ATi6000Ccontroller to your folder of essential kexts. Delete ATi6000Controller from /S/L/E. Install OS X (note: you will only have basic graphics support). After install (at the end of step 4) you can drag & drop the kext onto kextutility then reboot to enable your card.  
    Part 8 - Useful Tips
    8.0. To show or hide hidden files:
    In the terminal type:
    defaults write com.apple.finder AppleShowAllFiles YES
    or
    defaults write com.apple.finder AppleShowAllFiles NO
    Followed by killall Finder
     
    8.1. Spaces in terminal
    When using the terminal spaces must be preceded by \ or the file or folder name placed in quotations
    e.g.:
    open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg
    or
    open /Volumes/"Mac OS X Install ESD"/BaseSystem.dmg
     
    Part 9 – References
    Massive credit goes to this guide here:
    http://thetecherra.com/2012/07/10/tutorial-run-os-x-mountain-lion-10-8-gm-on-a-pc-hackintoshosx86-video/
    and this guide here:
    http://www.insanelymac.com/forum/index.php?showtopic=277015
     
    Part 10 – Change-log
    v2.3 - 25/07/2012 - Minor update to include InstallESD location from app-store.
    v2.4 - 27/07/2012 - Minor updates regarding Gringo Vermelho’s post.
    v2.5 - 03/08/2012 - Minor updates and touch-ups.
    v2.6 - 22/08/2012 - Addition of UseKernelCache=Yes plus key-maps and a few minor tweaks.
    v3.0 – 24/10/2012 – Addition of screenshots
    v3.1 – 03/12/2012 – British keyboard layout added
    v4.0 – 07/10/2013 – Updates so guide complies with Mavericks install procedure
    v4.2 – 10/11/2013 – Ironed out differences between Lion/ML and Mavericks
    v4.3 – 16/10/2014 – Added Yosemite support
    Essential - 03.08.12.zip
    Keyboard Layouts.zip
    Essential - Mavericks GM - 7.10.2013.zip
    Mavericks Install Guide - v0 - Quick Ref.pdf
    Mavericks install Guide - v4.2 - With Sreenshots.pdf
    Vanilla OS X Install Guide - v4.3 - With Sreenshots.pdf
  21. Like
    limurphy reacted to rayap in CMOS Resets by AppleRTC.kext   
    With the new AppleRTC kext version 1.5, got rid of CMOS Resets on my setup with this perl script [Edit: for arch=x86_64].Basically jumps over the checksum updates.
     

    sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /Extra/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

     
    AppleRTC.kext v1.5 does not jive with Lion when in E/E (multi boot); leave it in S/L/E .
  22. Like
    limurphy reacted to Boombeng in Editing custom personalities for ATI Radeon HD[45]xx   
    I had a look to enable hdmi audio on my HD4850 (2xdvi + s-video)
    Here is the atombios connector dump :
    Audio chip info: 0
    Connector at index 0 type: DVI-I (2)
    Connector at index 1 type: DVI-I (2)
    Connector at index 2 type: 9 pin DIN (9)
    Connector at index 4 type: DVI-I (2)
    Connector at index 5 type: DVI-I (2)
    Under Windows it is possible to have audio output using a dvi>hdmi dongle
    Using Motmot personnality of Atiframebuffer both dvi ports work well but ther is no audio
     
    Following your instructions i found this for motmot :
     
    addl $0x00010d60 (68960)
    movb $0x02
     
    offset_for_segment = 61624
    start_address_for_segment = 0000ed80 (60800)
     
    total = 225432
     
    at 225432 dec address in bin :
     
    00 04 00 00 04 01 00 00 00 01 00 00 10 00 02 03
    04 00 00 00 14 02 00 00 00 01 00 00 01 11 01 04
     
    looking ioregistry i can see port 0 and 1 are matched when i plug 2 displays in dvi
     
    Would that be possible to enable audio or the lack of hdmi connector in atombios is a problem ?
     
    Thanks again
×