Jump to content

Mork vom Ork

  • Content Count

  • Joined

  • Last visited

  • Days Won


Mork vom Ork last won the day on September 25 2018

Mork vom Ork had the most liked content!

About Mork vom Ork

  • Rank
    InsanelyMac Sage

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

7,138 profile views
  1. Mork vom Ork

    Clover.app testing

    fixed a misspelling in one line. sorry, so this is the new translation for german... de.strings.zip
  2. Mork vom Ork

    ThunderBolt Drivers

    Want real Thunderbolt HotPlug/HotSwap on the fly while your Hackintosh is running? Well, than this might be your solution: I have tested a lot of so promising Thunderbolt HotPlug SSDTs out there and none of them provide a working solution for me, so i decided to spend some time on a working solution for real Thunderbolt HotPlug/HotSwap, where you can change your Thunderbolt devices on the fly w/o restarting your Hackintosh every time you connect/change a device. Also this tutorial will work for motherboards with onboard Thunderbolt as well as for motherboards with Thunderbold Header connector. Ok, lets start how to make it work: as in many other threads the first thing you have to know is where your Thunderbolt hardware belongs in your ACPI path. To find out where it belongs, just open "IORegistryExlorer" while bootet normaly into macOS. Than search for some entrys like this: Sample of ASRock Z270 Super Carrier: Sample of ASRock Z370 Professional Gaming i7: Just for explanation: ASRock Z270 Super Carrier used builtin/onboard Thunderbolt 3, while ASRock Z370 Professional Gaming i7 uses Thunderbolt Header and a GC Gigabyte Titan Ridge PCIe card for Thunderbolt 3. As you can see for the Z270 the ACPI path looks like RP01/PXSX, while ACPI path for Z370 looks like PEG2/PEGP. Rememeber these entrys for later modification when it comes to edit the Thunderbolt SSDT file. Second: lets set the right BIOS settings for working Thunderbolt HotPlug/HotSwitch Lets take a look at the default BIOS settings for the given two sample motherboards ASRock Z270/370. The following screenshots shows their default settings for Thunderbolt when you install their latest BIOS revisions: standard BIOS settings ASRock Z270 Super Carrier: standard BIOS settings ASRock Z370 Professional Gaming i7: These are all settings for Thunderbolt given by default from ASRock on their Motherboards. But there are even more settings for Thunderbolt within their BIOS files, which need to be "unlocked"* first. After doing so, there might be a lot of more settings, like this: ASRock Z270 Super Carrier all settings unlocked: - ASRock Z370 Professional Gaming i7 all settings unlocked: - To make HotPlug/HotSwap working for your motherboard, just look for similar settings in your BIOS for Thunderbolt and set them as shown in the above screens. Sorry, i could only provide screenshots from ASRock machines, cause i do not have any other manufacturer. The most importent settings you need are "Thunderbolt (TM) Force Power" (which not all boards will have) and "GPIO3 Force Pwr" (which i recognized allmost every manufacturer will have in their BIOS settings for Thunderbolt). Just set these two settings to "ENABLED". <--- otherwise HotPlug/HotSwap will not work as expected. Also important is to switch a setting called "AIC Location" from "NB PCIE D01F0" to "NB PCIE D01F2". Notice: on Z270 Super Carrier i had to set this setting from NB PCIE D01F0 to NB PCIE D01F2 while on the Z370 Professional Gaming i7 it was set to NB PCIE D01F02 by default. If all settings set as described, save your settings and restart your Hackintosh. Third: prepare an SSDT for Thunderbolt to use with your Hackintosh. Place the SSDT file in the following location: EFI/CLOVER/ACPI/patched Attached to this tutorial you will find a sample SSDT (SSDT-10-TbtOnPch.aml), which we use to modify for our needs. Lets take a look at its code: Remeber your ACPI values from part one of this tutorial? These values are now needed to make this SSDT work for your personal machine. You might notice that the sample SSDT file is from my ASRock Z270 Super Carrier, cause the used ACPI values are RP01/PXSX within our sample. So all you need to do, is to change the values RP01/PXSX used in this sample SSDT to your values. If you open the sample SSDT within "MaciASL" you will get linenumbers, so i tell you, for which line you have to edit the given values: Line 23: External (_SB_.PCI0.RP01, DeviceObj) Line 24: External (_SB_.PCI0.RP01.PXSX, DeviceObj) Line 27: External (PXSX, DeviceObj) // (from opcode) Line 29: Scope (_SB.PCI0.RP01) Line 31: Scope (PXSX) Line 38: Notify (\_SB.PCI0.RP01.UPSB.DSB0.NHI0, 0x02) After you change these values to the values you found for your ACPI path, just save the so modified SSDT to the above given path, restart your Hackintosh and enjoy full working, on the fly HotPlug/HotSwap for all your Thunderbolt devices (also working for USB-C devices connected to your Thunderbolt ports). Feedback on how it works for you is welcome. I might help as long as i can. Regards, Mork vom Ork * = unlocking settings within BIOS files isn't an easy job and needs a tool so called "AMIBCP". Also from my personal test i know, it only works for ASRock BIOS files. Tested with BIOS files from ASUS, GIGBYTE and MSI makes the app crash while saving a so modified BIOS file. Also i know, that other manufacturers than ASRock like ASUS and GIGABYTE provide a lot more settings for Thunderbolt as standard settings, which are already unlocked for the enduser. I just moticed this so far on ASRock BIOS files. SSDT-10-TbtOnPch.aml.zip
  3. Mork vom Ork

    [pre-release] macOS Catalina

    anyone tried to make bootable install stick from Catalina Beta 7? I'll get message, that Catalina Beta app does not appear to be a valid OS installer application ! solved: downloaded DMG was corrupt. Stick still created.
  4. Mork vom Ork

    ThunderBolt Drivers

    !!! There seems to be good news for REAL Thunderbolt live HotPlug/HotSwap functionallity while your Hackintosh is running !!! I found a solution with just 7 rows of code within any of your Thunderbolt-SSDTs (you are just using right now to make it work) to make HotPlug/HotSwap work for any Thunderbolt/USB-C device possible w/o the need for shutdown/restart of the machine. Right now i still test it with some german guys to make sure, it runs on any motherboard (not just ASRock Z3x0 like mine). If all tests confirmed it working succesfully, i promise, i will provide you with a detailed instruction on how to make it work. And SORRY, it's still a solution for HotPlug/HotSwap with Thunderbolt, it's NOT a solution to make Thunderbolt-tree visible under Systeminformation/Thunderbolt So far you will find attached an IORegistryExplorer file of my System connected with CalDigit ThunderboltStation 2 connected to CalDigit ThunderboltStation 3 on Port #1 of GC Titan Ridge PCIe Card and a LaCie Tb2-SSD connected to Port #2 I just swapped the Devices on Port #1 to Port #2 and vice versa while runnning my machine - not turning off/on before swapping. You will notice this in the IOReg file by the red parts within Thunderbolt Part at PCI0-PEG2. RED lines mean in which position the TB-device was connected before HotSwapping it to the new position, black lines mean where it sits right now. Just a little notice: TB-SSDs/TB-HDDs need to be unmounted before hotswapping - otherwise you will get error message of not correctly unmounted device ;-) IOReg_allTB3-Devices_I_have.zip
  5. Hey Mork, thanks for providing the Classic Mac OS Theme. It's just great. I wanted to ask if there is an update available that contains the ICNS for Catalina? Great work and thanks again. Warmest regards from Steglitz :-D

    1. Mork vom Ork

      Mork vom Ork

      here it is. just place in:


      EFI/CLOVER/Themes/Classic Mac OS/Icons


    2. nokemix


      Thanks a bunch!!! And all the best, ximekon

  6. Mork vom Ork

    Clover General discussion

    one short question: are the MEMORY FIX drivers just UEFI or are the MEMORY FIX drivers LEGACY & UEFI (especialy the AptioMemoryFix.efi)? never used LEGACY BIOS, that's why i ask.
  7. Mork vom Ork

    [Pre-Release] macOS Mojave 10.14.6

    same here today: yesterday shows 10.14.6 beta4 rev 18G75a today shows 10.14.6 beta4 rev 18G78a but for me it showed NEVER beta5 ?!?
  8. Mork vom Ork

    Clover Localizations

    sorry, but found some minor glitches for translation in CLOVER PREF PANE. Fixed with this revision. I promise, this is really FINAL rev. de.po.zip
  9. Mork vom Ork

    Clover Localizations

    mea culpa and i am very sorry, but here is my FINAL german translation (including optical finetuning and better wording/grammar): this time the edits where made with "PoEdit" de.po.zip
  10. Mork vom Ork

    Clover Localizations

    find a second one: optional RC scripts missing description field for translation
  11. Mork vom Ork

    Clover Localizations

    i have a question about the po language files: what is this: #. type: "FileSystem64UEFI_title" #: Resources/templates/Localizable.strings:87 #: Resources/templates/Localizable.strings:121 #, fuzzy, no-wrap #| msgid "FAT filesystem driver." msgid "File System drivers" msgstr "Treiber für Dateisystemte." #. type: "FileSystem64UEFI_description" #: Resources/templates/Localizable.strings:88 #: Resources/templates/Localizable.strings:122 #, fuzzy, no-wrap #| msgid "Alternate HFS+ filesystem driver." msgid "A collection of file system drivers." msgstr "Eine Sammlung von Treibern für versah. Dateisysteme." lines, which contains the strings "#| " seems not to be translated correctly. that ONLY happen to areas, which contains such strings. For example: as you can see in the above code, the translation for "File system drivers" contains such lines and therefor the translation is missing in the finished Installer: WHY is this happening?
  12. Mork vom Ork

    Clover Localizations

    here is my latest translation: de.po.zip
  13. Mork vom Ork

    Clover Localizations

    i have updated the german translation, see attachment. feel free to commit de.po.zip
  14. Mork vom Ork

    Clover General discussion

    yep, that's it. works perfect! <-- as allways ;-) PS: i doubt for rev4986 it should be like this: # clean old drivers directories if [[ "$DRIVERS_LEGACY" != drivers64 ]]; then rm -rf "$CLOVER_PKG_DIR"/EFI/CLOVER/drivers/BIOS fi if [[ "$DRIVERS_UEFI" != drivers64UEFI ]]; then rm -rf "$CLOVER_PKG_DIR"/EFI/CLOVER/drivers/UEFI fi rm -rf "$CLOVER_PKG_DIR"/CloverV2/drivers-Off
  15. Mork vom Ork

    Clover General discussion

    no, it is correct, but will allways recreate that folder, even it is no longer needed since latest rev4986. But i see your request to let it stay for users, which are not allways on latest rev.