Jump to content

oldnapalm

Retired
  • Content Count

    6,720
  • Joined

  • Last visited

  • Days Won

    3

Reputation Activity

  1. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  2. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  3. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  4. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  5. Like
    oldnapalm reacted to MaLd0n in [Guide] Sierra / High Sierra on GA H97M-DS3P / 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   Install MacOS with Olarila Image, Step by Step, Install and Post Install
     
    https://olarila.com/forum/viewtopic.php?f=50&t=8685
        First... If you need DSDT edits... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Run it, post files generated in your desktop RunMe.app  Installation   --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder  CLOVER.zip   --Install Sierra/High Sierra and boot into system!   Post Installation   --Install Clover in HDD/SSD and replace with my folder CLOVER.zip   --Reboot and activate 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/   -DSDT My DSDT DSDT.GA H97M-DS3P MaLd0n.zip   -Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -HDEF -RTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -EC -PNLF -HDMI





    -FakeSMC
    https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek -Audio https://github.com/vit9696/AppleALC -LAN https://github.com/Mieze/IntelMausiEthernet   -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 and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!  
  6. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  7. Like
    oldnapalm got a reaction from lj3lj3 in VoodooHDA - common problems   
    Download:
    http://code.google.com/p/voodoohda/downloads/list
     
    Official thread:
    http://www.projectosx.com/forum/index.php?showtopic=355
     
     
    Problem: kernel panic.
    Solution 1: remove AppleHDA and restart the system before installing VoodooHDA.
    Solution 2: edit Info.plist, replace the key IOPCIClassMatch by IOPCIPrimaryMatch and put the PCI ID of your audio card in string.
    Before

    <key>IOPCI[color="#FF0000"]Class[/color]Match</key> <string>0x04030000&0xffff0000</string>
    After

    <key>IOPCI[color="#FF0000"]Primary[/color]Match</key> <string>0x[color="#0000FF"]3b56[/color][color="#008000"]8086[/color]</string>
    0xDeviceIDVendorID
     
    How to find device and vendor ID
    http://www.insanelymac.com/forum/index.php?showtopic=219584
     
     
    Problem: kext doesn't work (usually when there's more than one audio card or the video card has HDMI audio).
    Solution: use solution 2 for kernel panic problem above. If you want to use both cards, create one entry for each card in IOKitPersonalities.
     
     
    Problem: sound crackles.
    Solution 1: change output format in Applications - Utilities - Audio MIDI Setup

    Solution 2: check "Use SSE2" in VoodooHDA prefPane

    You can also enable Vectorize in Info.plist

    <key>Vectorize</key> <[color="#FF0000"]true[/color]/>
     
     
    Problem: volume control (slider) doesn't work.
    Solution: enable VoodooHDAEnableVolumeChangeFix in Info.plist

    <key>VoodooHDAEnableVolumeChangeFix</key> <[color="#FF0000"]true[/color]/>
     
     
    Problem: volume too low.
    Solution: enable VoodooHDAEnableHalfVolumeFix in Info.plist

    <key>VoodooHDAEnableHalfVolumeFix</key> <[color="#FF0000"]true[/color]/>
     
     
    Problem: audio feedback (Larsen effect), sound loop between input (microphone) and output (speakers).
    Solution: mute iGain and increase iMix or Mic if microphone doesn't work

    <key>iGain</key> <string>[color="#FF0000"]0[/color]</string>
    It can also be done in the prefPane. In some cases you may need to mute Monitor instead of iGain.
     
     
    Problem: audio delay. If you change volume, for example, it takes 1 or 2 seconds to play the test sound.
    Solution 1: delete com.apple.audio.DeviceSettings.plist and com.apple.audio.SystemSettings.plist from /Library/Preferences/Audio and reboot.
    Solution 2: use SoundFlower.
     
     
    Problem: inputs or outputs don't show in sound preferences.
    Solution 1: look for a kext patched for your codec.
    For VT1708S
    http://www.insanelymac.com/forum/index.php?showtopic=231508
    For AD1988B
    http://www.insanelymac.com/forum/index.php?showtopic=267898
    Solution 2: add NodesToPatch basead on getDump output (download in official thread).
    Example

    <key>NodesToPatch</key> <array> <dict> <key>Codec</key> <integer>2</integer> <key>Config</key> <string>0x90a70120</string> <key>Node</key> <integer>12</integer> </dict> </array>
    Config (PinDefault) is made up of the last 2 digits of each codec verb, but in the opposite order

    0x[color="#FF0000"]01[/color][color="#008000"]01[/color][color="#0000FF"]44[/color][color="#8000FF"]10[/color] = 21471c[color="#8000FF"]10[/color] 21471d[color="#0000FF"]44[/color] 21471e[color="#008000"]01[/color] 21471f[color="#FF0000"]01[/color] |||||||+- [color="#8000FF"]Sequence[/color] ||||||+-- [color="#8000FF"]Default Association[/color] |||||+--- [color="#0000FF"]Misc[/color] ||||+---- [color="#0000FF"]Color[/color] |||+----- [color="#008000"]Connection Type[/color] ||+------ [color="#008000"]Default Device[/color] |+------- [color="#FF0000"]Location[/color] +-------- [color="#FF0000"]Port Connectivity[/color]
     
    More detailed example
    http://olarila.com/forum/viewtopic.php?f=18&t=604
     
    Info about codec verbs
    Source: http://www.projectosx.com/forum/index.php?showtopic=465
     
    For each input/output there is a sequence of 4 verbs.

    Jack Color Description Node PinDefault Original Verbs -------------------------------------------------------------------------------------------------------- 1/8 Green Line Out at Ext Rear 20 0x14 0x01014410 21471c10 21471d44 21471e01 21471f01
    Its about NodeID(NID) 0x14 in hex, 20 in decimal.
     
    The default verbs for it: 21471c10 21471d44 21471e01 21471f01
     
    CAd (Codec Adress) NID (NodeID) Verb Command Verb Data
     
    71cXY X=Default Association Y=Sequence
     
    Default Association and Sequence are used together by software to group Pin Complexes (and therefore jacks) together into functional blocks to support multichannel operation. Software may assume that all jacks with the same association number are intended to be grouped together, for instance to provide six channel analog output. The Default Association can also be used by software to prioritize resource allocation in constrained situations. Lower Default Association values would be higher in priority for resources such as processing nodes or Input and Output Converters. Note that this is the default association only, and software can override this value if required, in particular if the user provides additional information about the particular system configuration. A value of 0000b is reserved and should not be used. Software may interpret this value to indicate that the Pin Configuration data has not been properly initialized. A value of 1111b is a special value indicating that the Association has the lowest priority. Multiple different Pin Complexes may share this value, and each is intended to be exposed as independent devices.
     
    Sequence indicates the order of the jacks in the association group. The lowest numbered jack in the association group should be assigned the lowest numbered channels in the stream, etc. The numbers need not be sequential within the group, only the order matters. Sequence numbers within a set of Default Associations must be unique.
     
    *My notes for this, if you look on the vanilla codec verb(no matter what codec) you will see that Sequence is always 0.
    Why that, and why for us on our codec verbs is different? Simple b/c Apple dosen't have multichannel analog out! so you must change it to 0.
     
    *About Default Association, Keep the default one, in order, and on those that are the same replace them with new one that dosen't exist already in the dump... the values you can use are: 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d and f.(see what does verbit if you still don't understand)
     
    71dXY X=Color Y=Misc
     
    Color indicates the color of the physical jack for use by software.

    Unknown 0 Black 1 Grey 2 Blue 3 Green 4 Red 5 Orange 6 Yellow 7 Purple 8 Pink 9 Reserved A-D White E Other F
     
    Misc is a bit field used to indicate other information about the jack. Currently, only bit 0 is defined. If bit 0 is set, it indicates that the jack has no presence detect capability, so even if a Pin Complex indicates that the codec hardware supports the presence detect functionality on the jack, the external circuitry is not capable of supporting the functionality.
    Reserved 3
    Reserved 2
    Reserved 1
    Jack Detect Override 0
     
    *Use 0 for Jack Detect - External Device(e.g. Headphones Mic etc)
    Use 1 for Jack Detect Disabled - Internal Device(e.g. Internal speakers, Internal mic)
     
    71eXY X=Default Device Y=Connection Type
     
    Default Device indicates the intended use of the jack or device. This can indicate either the label on the jack or the device that is hardwired to the port, as with integrated speakers and the like.

    Line Out 0 Speaker 1 HP Out 2 CD 3 SPDIF Out 4 Digital Other Out 5 Modem Line Side 6 Modem Handset Side 7 Line In 8 AUX 9 Mic In A Telephony B SPDIF In C Digital Other In D Reserved E Other F
     
    Connection Type indicates the type of physical connection, such as a 1/8-inch stereo jack or an optical digital connector, etc. Software can use this information to provide helpful user interface descriptions to the user or to modify reported codec capabilities based on the capabilities of the physical transport external to the codec.

    Unknown 0 1/8" stereo/mono 1 1/4" stereo/mono 2 ATAPI internal 3 RCA 4 Optical 5 Other Digital 6 Other Analog 7 Multichannel Analog (DIN) 8 XLR/Professional 9 RJ-11 (Modem) A Combination B Other F
     
    71fXY X=Port Connectivity Y=Location
     
    Port Connectivity indicates the external connectivity of the Pin Complex. Software can use this value to know what Pin Complexes are connected to jacks, internal devices, or not connected at all.
    00b - The Port Complex is connected to a jack (1/8", ATAPI, etc.).
    01b - No physical connection for Port.
    10b - A fixed function device (integrated speaker, integrated mic, etc.) is attached.
    11b - Both a jack and an internal device are attached. The Information provided in all other fields refers to the integrated device. The PD pin will reflect the status of the jack; the user will need to be queried to figure out what it is.
     
    Location indicates the physical location of the jack or device to which the pin complex is connected. This allows software to indicate, for instance, that the device is the “Front Panel Headphone Jack” as opposed to rear panel connections.
     
    *Details:
    Convert the 2 digit hex number to binary.
    Pad the front with zero's to make it 8 dgits.
     
    Example:

    0x02 = binary 10 = 00000010 8 digit binary Reading the bits from left to right: Port Connectivity bits 7:6 ----------------------------------------------------------- 00 - Port is connected to a Jack 01 - No External Port -or- No physical connection for Port 10 - Fixed Function/Built In Device (integrated speaker, mic, etc) 11 - Jack and Internal device are attached Location Part 1 - bits 5:4 ----------------------------------------------------------- 00 - External on primary chassis 01 - Internal 10 - Separate chassis 11 - Other Location Part 2 - bits 3:0 ----------------------------------------------------------- The meaning depends on Location Part 1 00 0000 N/A 00 0001 Rear 00 0010 Front 00 0011 Left 00 0100 Right 00 0101 Top 00 0110 Bottom 00 0111 Special (Rear panel) 00 1000 Special (Drive bay) 01 0000 N/A 01 0111 Special (Riser) 01 1000 HDMI 01 1001 ATAPI 10 0000 N/A 10 0001 Rear 10 0010 Front 10 0011 Left 10 0100 Right 10 0101 Top 10 0110 Bottom 11 0000 N/A 11 0110 ? 11 0111 Inside Mobile Lid (example: mic) 11 1000 Outside Mobile Lid Bits Hex 76 54 3210 ------------------- 71f01 = 00 00 0001 - Port has a jack - It is External - Rear Location 71f02 = 00 00 0010 - Port has a jack - It is External - Front Panel Location 71f59 = 01 01 1001 - No External Port - ATAPI 71f18 = 00 01 1000 - Port has a jack - External - HDMI 71f90 = 10 01 0000 - Built In Device - Internal - N/A | | |||| | | |--------- Location part 2 | |------------ Location part 1 |--------------- Port Connectivity
     

  8. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  9. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  10. Like
    oldnapalm reacted to Brumbaer in Tardis - Case fo the Kaby Lake   
    My newest Hack is a Kaby Lake. Regarding Hackintoshes that's a bit ahead of it's time. So I decided to use a time machine for a case. There are three well known time machines.   The Time Machine from the 60s film "Time Machine" The DeLorean from "Back to the Future" The Tardis from "Doctor Who"   The "Time Machine" is not really suited because of it's open frame The DeLorean is not open framed, but it will have a lot of unused spaces, because they are just too small to cram some PC component in. The Tardis on the other hand is a high box with a square footprint - just perfect.   The case was build keeping the best traditions of medieval artisan guilds firmly in mind using a CNC milling machine and a 3D printer. Materials are MDF, acrylic glas and resin, painted with spray paint and acrylic paint.       The computer is a i7-7700K at 5100MHz, a GTX980TI, 32GB of Memory and a total of 3TB SSD storage. Cooled by a Kraken X61. Mobo is a AsRock ITX.   Those components define the overall size which is 24,5 x 24,5 x 50 cm incl. lantern, but excluding the plinth. Size of the plinth is 27 x 27 x 2 cm.   At the moment there are no light effects. I'm considering adding those, but I might postpone it for a 2.0 version, which would have the cables routed through the bottom and would feature an "ordinary" back.   P.S.  
    This Tardis isn_t bigger on the inside.
  11. Like
    oldnapalm got a reaction from cuthead in AppleRTC patch (CMOS reset after sleep/wake)   
    Without a patched DSDT you will have CMOS reset even without using sleep/wake on many machines.
     
    AppleRTC patch avoids CMOS reset after sleep/wake.
     
    It's a well known issue, anyway I've updated the title.
     
    More info
    http://www.insanelymac.com/forum/topic/253992-cmos-resets-on-restarts-after-sleep-and-wake-in-107-lion/
     
    If it's not the case, how do you patch DSDT to avoid CMOS reset after sleep/wake?
  12. Like
    oldnapalm got a reaction from nmano in Sierra AppleGraphicsDevicePolicy Clover Patch   
    Patches work after 10.12.1 update.
  13. Like
    oldnapalm got a reaction from nmano in Sierra AppleGraphicsDevicePolicy Clover Patch   
    Patches work after 10.12.1 update.
  14. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  15. Like
    oldnapalm got a reaction from Allan in Sierra AppleGraphicsDevicePolicy Clover Patch   
    Thanks! Tested and working under Sierra and Yosemite.
  16. Like
    oldnapalm got a reaction from Mirone in Problems with Graphics Cards on the macOS Sierra   
    I used these properties to activate nVidia GeForce GTX 460M up to El Capitan
    <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict>     <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>     <dict>         <key>@0,AAPL,boot-display</key>         <string>0x00000001</string>         <key>@0,EDID</key>         <data>         AP///////wANryYXAAAAAAIVAQOAJhV4CtiVo1VNnScPUFQAAAABAQEBAQEB         AQEBAQEBAQEBLjaAoHA4H0AwIDUAftcQAAAYAAAA/gBOMTczSEdFLUwyMQog         AAAA/gBDTU8KICAgICAgICAgAAAA/gBOMTczSEdFLUwyMQogAGY=         </data>         <key>@0,NVDA,UnderscanMin</key>         <string>0x00000052</string>         <key>@0,backlight-control</key>         <string>0x00000001</string>         <key>@0,built-in</key>         <string>0x01</string>         <key>@0,compatible</key>         <string>NVDA,NVMac</string>         <key>@0,connector-type</key>         <string>0x00000800</string>         <key>@0,device_type</key>         <string>display</string>         <key>@0,display-cfg</key>         <string>0x00030103</string>         <key>@0,fboffset</key>         <string>0x00030000</string>         <key>@0,name</key>         <string>NVDA,Display-A</string>         <key>@0,pwm-info</key>         <data>         AhgAZJBZAgAIUgAApRwAAAAEAAABAAAA         </data>         <key>@0,use-backlight-blanking</key>         <string></string>         <key>@1,NVDA,UnderscanMin</key>         <string>0x00000052</string>         <key>@1,can-hot-plug</key>         <string></string>         <key>@1,compatible</key>         <string>NVDA,NVMac</string>         <key>@1,connector-type</key>         <string>0x00000800</string>         <key>@1,device_type</key>         <string>display</string>         <key>@1,display-cfg</key>         <string>0x0100ffff</string>         <key>@1,name</key>         <string>NVDA,Display-B</string>         <key>@2,connector-type</key>         <string>0x00000800</string>         <key>@3,connector-type</key>         <string>0x00000800</string>         <key>AAPL00,DataJustify</key>         <string>0x00000001</string>         <key>AAPL00,Dither</key>         <string>0x00000000</string>         <key>AAPL00,DualLink</key>         <string>0x00000001</string>         <key>AAPL00,InverterFrequency</key>         <string>0x00000000</string>         <key>AAPL00,LinkFormat</key>         <string>0x00000000</string>         <key>AAPL00,LinkType</key>         <string>0x00000000</string>         <key>AAPL00,PixelFormat</key>         <string>0x00000000</string>         <key>AAPL00,T1</key>         <string>0x00000000</string>         <key>AAPL00,T2</key>         <string>0x00000001</string>         <key>AAPL00,T3</key>         <string>0x000000c8</string>         <key>AAPL00,T4</key>         <string>0x000000c8</string>         <key>AAPL00,T5</key>         <string>0x00000001</string>         <key>AAPL00,T6</key>         <string>0x00000000</string>         <key>AAPL00,T7</key>         <string>0x00000190</string>         <key>NVCAP</key>         <data>         BAAAAAAAAQD+AAAAAAAABwAAAAA=         </data>         <key>NVDA,Features</key>         <string>0x000c16ff</string>         <key>NVDA,invalid-config</key>         <string>0x00000000</string>         <key>VRAM,memvendorID</key>         <string>0x0006</string>         <key>VRAM,totalsize</key>         <string>0x60000000</string>         <key>built-in</key>         <string>0x00</string>         <key>device_type</key>         <string>NVDA,Parent</string>         <key>graphics-options</key>         <string>0x0000000c</string>         <key>hda-gfx</key>         <string>onboard-1</string>         <key>model</key>         <string>Asus GeForce GTX 460M</string>     </dict> </dict> </plist> Now with Sierra I get KP related to NVDAStartup.kext using this injection. Using Clover default settings it works fine (needs edit in AppleGraphicsDevicePolicy.kext as before to avoid getting stuck in black screen).
  17. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  18. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  19. Like
    oldnapalm got a reaction from undertaker00 in DSDT editor and patcher   
    El Coniglio released this DSDT editor with automated patching capabilities
     

     
    The main editor windows allows the user to open a DSL file or extract the DSDT from IOReg. It has some useful resources, like syntax highlighting, navigation tree and some options that came with the text editor component it uses, like regex matching, auto completion, jump to pair, etc.
     
    The patcher window parses a script-like language representing the patches. The user can preview the modifications before applying them. This "language" allows us to write dynamic patches that can be applied in various situations. More specific commands can be written as they become necessary.
     
    For now these are the implemented commands (which can be stacked separated by ";")
     
    Changes in latest release:
    fixed bug which caused data loss if number of open and close brackets don't match
    fixed compile window to work with new IASL versions
    updated IASL to 20120420

    Download: (last updated on 17/May/2012)
     
    Mac OS: DSDTEditor_Mac.zip
    Linux and Windows: DSDTEditor_Linux_Windows.zip
     
    How to apply a patch:
     
    [media]http://www.youtube.com/watch?v=nZIHw-QYO64[/media]
     
     
    Screenshots:
     
    Linux

     
    Windows

     
     
    Credits:
     
    Editor component: jsyntaxpane (http://code.google.com/p/jsyntaxpane/)
    IASL Copyright © Intel Corporation
    Written in Java
  20. Like
    oldnapalm got a reaction from Rodion2010 in [DSDT] Renamed devices to mac specific ones   
    Check this post
    http://www.insanelymac.com/forum/index.php...t&p=1280888
  21. Like
    oldnapalm got a reaction from gils83 in AppleRTC patch (CMOS reset after sleep/wake)   
    sudo perl -pi -e 's|\x75\x2e\x0f\xb6|\xeb\x2e\x0f\xb6|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC sudo touch /System/Library/Extensions  
    It's the same patch as ML, just different location, thanks rayap   http://www.insanelymac.com/forum/topic/276066-cmos-resets-by-applertckext/   10.8 < 0000000000001d32 jne 0x1d64 --- > 0000000000001d32 jmp 0x1d64 10.9 < 0000000000000d3e jne 0xd6e --- > 0000000000000d3e jmp 0xd6e  
  22. Like
    oldnapalm got a reaction from gils83 in AppleRTC patch (CMOS reset after sleep/wake)   
    sudo perl -pi -e 's|\x75\x2e\x0f\xb6|\xeb\x2e\x0f\xb6|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC sudo touch /System/Library/Extensions  
    It's the same patch as ML, just different location, thanks rayap   http://www.insanelymac.com/forum/topic/276066-cmos-resets-by-applertckext/   10.8 < 0000000000001d32 jne 0x1d64 --- > 0000000000001d32 jmp 0x1d64 10.9 < 0000000000000d3e jne 0xd6e --- > 0000000000000d3e jmp 0xd6e  
  23. Like
    oldnapalm got a reaction from MaLd0n in Chameleon 2.4svn Official PKG Installer   
    Congratulations sir, Chameleon is able to boot 10.10 with those changes.
     
    boot.zip
     
    Use flags "/System/Library/Kernels/kernel -f -v" (assuming it's already installed)
  24. Like
    oldnapalm reacted to Slice in [HOWTO] ACPI access for monitoring   
    This is the guide how to make monitoring of hardware parameters (temperatures, fan speeds, voltages etc) using DSDT programming.
    The method invented by me with THeKiNG presence and improved by Kozlek.
     
    Prerequisites
    There is FakeSMC plugin named ACPImonitor in my branch or renamed to ACPISensors in kozlek's branch. They are the same.
    HWMonitor or other monitoring application: iStat, K-Stat-i, ...
     
    How it works.
    HWMonitor or other software make a request for known SMC key, for example TA0P (ambient temperature), every 1 seconds.
    The request catched by FakeSMC which knows that the key registered by ACPImonitor plugin.
    This plugin knows that the value for the key must be read from ACPI device "monitor" by method "TCRR" and make a request to AppleACPIPlatform for evaluate this method.
    AppleACPIPlatform interpretates AML codes written into DSDT, finds the method and calculates the value using hardware access.
    The value return back to ACPImonitor -> FakeSMC -> AppleSMC -> HWMonitor which shows the "temperature".
     
    The kext ACPImonitor will not work OOB. It will work only with DSDT patches for the usage.
     
    Simple example DSDT.
    Device (FSAM) { Name (_HID, EisaId ("APP0111")) Name (_CID, "monitor") Name (TCRK, Zero) Method (TCRR, 0, NotSerialized) { Return (TCRK) } Method (TCRW, 1, NotSerialized) { Store (Arg0, TCRK) Return (TCRK) } Method (TCPP, 1, NotSerialized) { Store (\_TZ.THM._TMP (), Local0) Return (Local0) } } You have to create new device. It must have
    Name (_CID, "monitor")
    This is the key for ACPImonitor attached to it.
    Then see Method (TCRR,0, NotSerialized) mentioned above. It will return a value or variable TCRK.
    In this demo I made a method TCRW which will fill the variable TCRK from SMC key.
    The I have to make correspondence ACPI_methodSMC_key in ACPImonitor.kext/info.plist

    I can write values to the SMC key TA1P
    ./SMC_util3 -kTA1P -w28
    and see the value 28 appears in HWMonitor as "Ambient temperature"
    Value conversions must be provided in DSDT.
     
    Predefined keys
    ACPI        SMC     Name
    TCPU        Th0H    CPU heatsink
    TSYS        TN0P    Northbridge temperature
    TDIM        Tm0P    DIMM temperature
    TAMB        TA0P    Ambient
    TCPP        TC0P    CPU proximity
    VCPU        VC0C    CPU voltage
    VMEM        VM0R    DIMM voltage
    ACDC        ACIN, ACEN  Presence of AC power
    FAN0 - FAN9 for FAN speed
    FTN0 -FTN9 for FAN rotation time
     
    In the case of FAN reading we also want to assign name to them. It is also possible with the Info.plist

     
     
    What to monitor in real DSDT?
    This is individual. So why the ACPImonitor will not work OOB.
    See example from my notebook. looking through DSDT I found the follow region.
    OperationRegion (TMIF, SystemMemory, 0xFF800160, 0x20) Field (TMIF, ByteAcc, Lock, Preserve) { THS0, 8, THS1, 8, THS2, 8, Offset (0x08), FAN1, 8, Offset (0x10), TSP0, 8, TSC0, 8, TSP1, 8, TSC1, 8 } Looks like three temperatures and one FAN.
     
    As well I found ThermalZone
    Scope (_TZ) { ThermalZone (THM) { Method (_CRT, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.TSC0), Local0) Return (Local0) } Method (_TMP, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.THS0), Local0) Return (Local0) }  
    _CRT - critical temperature
    _TMP - current temperature
    _SB.PCI0.LPCB.WSEC.C2K is a method to convert Celsius to Kelvin degrees.
    So I see that the field THS0 is really CPU temperature.
     
    Using ACPImonitor is only way to do monitoring on notebooks because no other methods works and because it usually contains ThermalZone.
     
    I know my guide is too short and hope some users shows own examples how to do ACPI monitoring.
     
    Note. This method is useful mostly for notebook where temperature and FANs control present in DSDT.
    For desktops there are plugins like ITE87xx, Winbond, Fintek depending on you LPC chip installed.
     
     
    10.10.2017 ACPIMonitor version 1.0.3
    There is a possibility to define some types and sizes for custom keys
    <key>keysToAdd</key> <dict> <key>TCRR</key> <string>TA0P-2</string> <key>TCRW</key> <string>TA1P-3</string> <key>MSLD</key> <string>MSLD-1</string> </dict>  
    The number after key name means follow
    0 -> "flag", len 1
    1 -> "ui8 ", len 1
    2 -> "ui16", len 2
    3 -> "sp78", len 2
    4 -> "ui32", len 4
  25. Like
    oldnapalm got a reaction from Allan in Atheros 9285   
    My Atheros 9285 (ID 0x2b) used to work only with a DSDT patch until 10.8.4, but stopped working in 10.9 DP, I had to edit the Info.plist of AirPortAtheros40 or use an injector kext.
     
    I was able to fix it using only DSDT patch again by injecting the properties name, IOName and compatible (I'm not sure all 3 are necessary, will test later)
    Method (_DSM, 4, NotSerialized) {     Store (Package (0x12)         {             "AAPL,slot-name",              Buffer (0x08)             {                 "AirPort"             },              "device-id",              Unicode ("*"),              "device_type",              Buffer (0x08)             {                 "AirPort"             },              "model",              Buffer (0x33)             {                 "Atheros 9285 802.11 b/g/n Wireless Network Adapter"             },              "subsystem-id",              Buffer (0x04)             {                  0x8F, 0x00, 0x00, 0x00             },              "subsystem-vendor-id",              Buffer (0x04)             {                  0x6B, 0x10, 0x00, 0x00             },              "compatible",              Buffer (0x0B)             {                 "pci168c,2a"             },              "IOName",              Buffer (0x0B)             {                 "pci168c,2a"             },              "name",              Buffer (0x0B)             {                 "pci168c,2a"             }         }, Local0)     DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))     Return (Local0) } Thanks to nyolc8 for the tip in this topic
     
    http://www.insanelymac.com/forum/topic/289791-fixed-by-dsdt-edit-10c-temps-500rpm-fans/?do=findComment&comment=1923734
     
×