Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 09/26/2020 in all areas

  1. 👉 Rules Our goal is ensure that the forum remains a helpful & friendly place to learn about how to run Mac OS X on non-Apple hardware, and of course other general banter. We want you to be able to discuss anything and everything here, and to do so we ask that you check out these guidelines for forum use. Do not upload anywhere else files when developers specifically ask not to. We take this matter very seriously, as developers are the very heart of our community. No Flaming. This includes racism, threatening, personal attacks, victimization or hateful content. Retaliation will not be tolerated either; if a member has broken a rule, please use the report feature on the forum and the staff will deal with the situation appropriately. No posting of direct or indirect links to warez or pirated pieces of software, this includes cracks, serials and torrents. Do not publicly argue the decision of a moderator. If you disagree with a moderator take it up with them in private via PM. Only one (1) login is allowed per member. Duplicate accounts will be banned or deleted. Bumping of posts is not permitted. Other than being less annoying it also keeps the posts more informative. Meaningless and useless posts may be removed at Moderator's discretion. Only post your post once (1). This keeps the forum cleaner and makes it easier to find what you are looking for. No advertising or business offers of any kind. No posting of copyrighted material. This includes copying and pasting news articles from news websites. Attached materials must come with clear descriptions of what they are and what they do, linking to this information elsewhere is not sufficient. Materials derived from Open Source must include source code, as well as an explanation of what has been done to it. Discussion of P2P, torrent sites, or similar download sites of any kind will not be tolerated. We do not want to know your illegal downloading habits. Do not post spyware or any other malware. This includes linking to other sites which may contain it. Posting just to promote another site, product, or service (spamming) is not allowed. This site is not here for you to promote your own or anyone else's material. Discussion of commercial spin-offs of the OSx86 scene is allowed if it’s to understand their existence, but no discussion of how to use them, nor any support for these commercial spin-offs are allowed as they are not in the spirit of the OSx86 scene. Example of commercial spin-off: tonymacx86. Why InsanelyMac does not support tonymacx86 VERY IMPORTANT: PLEASE READ! (ABOUT TONYMACX86 AND iATKOS M / Y / EC / SR) 👉 Posting Guidelines If you have a question please do your best to use the search feature and search the forum before creating a new topic. Post in the correct forum and read the forum description. This will make sure that your post will not be removed. Pick an appropriate title and tags (if any) for your post. A good title makes it easier to find what you are looking for. Using informative tags allows for improved searching of related topics. All posts must be clearly written and easy to read. For example, if you have long blocks of text, use the Code option, etc. Limit "empty lines" as much as possible, use punctuation where you can and be concise. Posts may be edited for this reasons by InsanelyMac staff at their discretion. Please remember that you are in a public forum, a bit of courtesy is always welcome. It's always nice to start by saying "Hi" or "Hello" before asking a question or seeking help. Also a "thank you" would be appreciated, especially if the help you get is effective. Your topic does not deserve any more attention than others seeking help hence topic titles must reflect their content, and topic titles containing things like: 'please help' 'look here' 'cash reward' 'urgent' or other inaccurate descriptions will be removed. This includes all-caps titles. Give your hardware specs when necessary (asking for support) and any other time where it may be beneficial to have them listed. Watch this video to guide you how to do that: [Video] How to add a signature. 👉 Signatures, Avatars and Nicks Keep your signature/avatar clean and tidy - should you receive a PM from the staff regarding your signature/avatar, please make the requested alterations or it may be removed/shortened appropriately. To keep pages loading fast for everyone, we request that your signatures and avatars contain no animations or high-definition graphics of any kind. Signatures should be no more than 6 lines of text using a regular font. If you can't fit all of your system specs in that you'd like, why not create a small graphic to contain the information? They should also contain no referral or affiliate program graphics. Avatars should be in "good taste," a qualification that is broad enough to let us determine what is and isn't. Goth-devil-child-wild-eyed-in-the-violent-blackness probably qualifies as being in bad taste. Nothing offensive, pornographic, or vulgar. Nicknames must be readable by the system (without question marks). This will ensure that your nickname can be searched, and that other users can contact you. They should also not contain staff member groups (administrator, moderator, developer, etc.) to prevent confusion. Nicknames should also show respect to the community, thus nothing containing offensive language. Email addresses must be real. Accounts not in line with the last two rules will be edited or deleted without warning. 👉 Policing Do not publicly discuss the decision of a moderator. If there is any issue with a decision of a staff member PM them or contact an admin. Moderators have the ability to suspend or impose posting restrictions upon accounts based on the user's history. Records are kept to keep track of user's behavior and point out repeat offenders. Attempts to circumvent posting restrictions will lead to your account being banned, and any other accounts affiliated with your account being banned also. These rules cover a broad spectrum and are set up to preserve a free and open (and fun) place for discussion. They, in conjunction with common sense and good judgment, should steer you in the right direction. We're all human and we know that people make mistakes... but that's also not an excuse. More rules are subject to appear on this board as we see fit, so please check back from time to time for your own benefit. Thanks for joining our community and helping make it the best it can be. In case the rules localizations should differ, the English rules are the standard.
    54 points
  2. Version 1.0.0

    3,208 downloads

    Modified IO80211Family.kext especially who use device based on Atheros40 (the idea came from CtlnaAHCIPort.kext) so we don't need to touch /S/L/E just inject via OpenCore, and we can running Big SUr without open Sealed (no need remove/delete vanilla IO80211Family.kext in /S/L/E) I'm not try in Mojave or Catalina but I'm sure is worked too 1. just put 2 kext HS80211Family.kext & AirPortAtheros40.kext .../OC/Kexts and make sure inject via config.plist do not inject IO80211NetBooter in the plist (must do research so i leave there in plugin), I remove IO80211NetBooter from plugin so as not to confuse see my pict below just add 2 value 2. you can add value manually VendorID in IONameMatch (atheros40) if your ID not present 3. refer to @MaLd0n guide in olarila for working Wifi Atheros AR9565, AR9462, AR9463, AR9485 here is the modification (no need injector) AR9565 AirPortAtheros40-9565.kext.zip AR9462 AirPortAtheros40-9462.kext.zip AR9463 AirPortAtheros40-9463.kext.zip AR9485 AirPortAtheros40-9485.kext.zip Additional : Fake Locale & Country Code Use this kext WifiLocFix.kext.zip to fix Locale & Country Code (Fake AirPort Location Interface) You can change it inside WifiLocFix.ket depend on your location and don't forget to inject in your config.plist Card Type: AirPort Extreme (0x168C, 0x3112) Firmware Version: Atheros 9380: 4.0.74.0-P2P MAC Address: XXXXXXXXXXXXXX Locale: ETSI Country Code: ID Supported PHY Modes: 802.11 a/b/g/n Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64 Wake On Wireless: Supported Status: Connected
    29 points
  3. Hi everyone This post is more concerning all our current and futur Just Joined members. Back in the days we had IPB v3.x.x software version, we implemented a quiz to prevent spammers from posting their articles. But since the last forum upgrade (to IPB v4.x), the quiz plugin needed to be completely recoded from scratch for Invision Community 4.x but never seen the light. As a result, it allowed all our Just Joined members to post and create new topics almost over the whole forum... including spammers. So to overcome the problem related to the absence of a quiz to counter spammers, I just created a new group promotion rule that will move all members from Just Joined group to Newbies group once they reached 10 posts. But that this rule can make sense, I also removed all forum access (from creating new topics and replying) to the Just Joined group except New Users Lounge section. So for asking for help, please do it in that section 'till you reached Newbies group level. With that move, it will not prevent spammers from posting but at least their content(s) will be condensed in one and only area, which would help us to better deal with them. So before you ask why you no longer are able to post in a specific area, this is why. Of course, once accessed to Newbies group, you'll also have some restrictions but it should be more in accordance with the permissions you currently have. But as reminder, to have a full forum access, you need to reach full Members group level (50 posts). Thank you for your understanding. BR fantomas
    27 points
  4. Here is a discussion about my little tool : BootloaderChooser This is the solution if you : - are not sure on which file his EFI bios is booting - are annoyed because clover and oc efi has to be named CloverX64.efi and OpenCore.efi. Hence, you can't easily see the version - ares tired of renaming efi files to try different version (that's the consequences of the previous point). - find not great the need to have a bootable Clover/OC backup on a USB stick in case something goes wrong at update or config modification. - you also tired to often rename Clover folders to use them. What is it : This tool is a menu that allows you to choose which bootloader you wanna load. It designed to choose between Clover and OpenCore. You can name your efi file anything you want (Clover-v5119, Clover-v5122, OC-v0.6.1, etc.). You can also have many folders in your EFI folder. Although to boot Clover from a folder named anything else than CLOVER, you'll need a new version. To boot OpenCore from a folder named anything else than OC, you'll need my version. Here is how it looks : How to install Binary efi file are here : https://github.com/jief666/BootloaderChooser Let me know what you think...
    22 points
  5. We celebrate 10th anniversary of Clover project! http://web.archive.org/web/20140317061109/http://www.projectosx.com/forum/lofiversion/index.php/t2008-0.html
    21 points
  6. https://github.com/ic005k/QtOpenCoreConfig If you like to use Plist editor to complete the editing of configuration files, you can give it a try:PlistEDPlus OC auxiliary tools(OCAT or ocat for short) = Config.plist editor + Config.plist database + ... Note: All platforms have the same interface style Features include but are not limited to: * Write plist files with spaces for indentation to fit all editors or editing environments, such as the Shell editing environment * Powerful keyword search function, including retrieval of unseen data tables * All tabs and checkbox text are supported for copying (right-click menu) * Unlimited levels of undo and redo (automatically cleared when opening a new file) * Copy and paste rows between multiple processes and single processes * Well-built data structures to accommodate rapid iterations of OpenCore * Built-in configuration file database * Generate EFI folders on the desktop based on configuration files * Each function option adopts suspension prompt and status bar prompt * Keep up with the latest development version of OpenCore and keep pace with it completely * Double-click to open the file, drag and drop the file to the software interface to open the file, and open the file history display * All three platforms use OC's official macserial to generate serial numbers * Software UI adapts to various resolutions, including winpe and linux livecd, etc. * Built-in update check ......
    20 points
  7. https://github.com/ic005k/PlistEDPlus New: Add aml, kext, efi files for OpenCore. The operation is very simple, take ACPI as an example: select Add under ACPI, drag and drop one or more aml files to the app window. Features include but are not limited to: * Lightweight and high performance * Automatic detection of OpenCore configuration files with corresponding operation prompts * Support multi-select operations (including copy, cut, delete, etc.) * Open source, cross-platform (currently supports win, mac, linux) * Humanized search function (a. Keyboard initial character search for each column of key, data type, and value within the expanded node range; b. Search box global search, one-time display of search results) * Fully comply with and conform to the technical specifications of plist files, data types are displayed exactly the same as plist text, without any escaping * Multi-tab view or edit files * Multi-language support (currently supports Chinese, Russian, English) * Drag and drop files to the software interface to open files, double-click to open files, file open history display, automatically load the last opened file * Add, remove, paste, cut, edit entries, etc., all included in Undo, Redo policy group, support undo and restore * Expand and collapse entries right-click menu, in different columns, with different effects * For values of data type, the hover window automatically displays the corresponding ASCII and Base64 values * When changing the data type, the value is automatically converted with it * Free to select the children under a node for A->Z sorting (currently no sorting of arrays) * Drag and drop to adjust the order of sibling items, up or down button to adjust the order of sibling items * Rich shortcut keys * Built-in update checking * If the currently opened file is modified by other programs, it automatically prompts whether to reload * Software UI adapts to various resolutions, supports winpe, linux livecd, etc. ...
    20 points
  8. Useful information: macOSDeveloperBetaAccessUtility (thanks to gengik84) Black Screen on reboot -> use bootarg "-lilubetaall" (thanks to antuneddu) 'Til devs update WEG & Lilu, use -wegbeta boot arg to avoid KP on wake on SKL Laptops (thanks to Hervé)
    19 points
  9. Latest Update: September 18th, 2021. Guide is applicable to: Clover r5123 to r5139+ (UEFI only) Background: Since the Pre-Release of Clover r5123, OpenCore's Memory Fixes have been integrated completely into Clover in the form of OpenRuntime.efi, replacing the previously used AptioMemoryFixes. Since r5126 these are now obsolete and no longer supported, so an upgrade to r5126 or later is mandatory in order to be able to install and boot macOS Big Sur and Monterey with Clover! Aim: This guide is for everyone trying to update to the latest revision of Clover, so they can install and run Big Sur and newer on their machines. When updating to the latest revision of Clover, there are several obstacles one might face along the way. This guide is here to assist users in trying to make the switch from the "old" Clover with AptioMemoryFixes to the new one with Open Runtime and Quirks (make sure to update Clover Configurator to the latest version as well). Problem: If you update your existing Clover installation by installing the clover.pkg file like you used to, this will most likely result in an inoperable bootlader due to missing boot parameters in the config.plist. Approach: In order to avoid the dilemma of your system not wanting to boot, you have to know that the following files are obsolete and are no longer necessary, so they should either be deleted when updating Clover from a built prior to r5123 or omitted altogether when setting up a new EFI Folder: AptioMemoryFixes: AptioMemoryFix.efi, OsxAptioFix3Drv.efi, OsxAptioFixDrv.efi and everything else containing "memoryfix". Unnecessary Drivers (for UEFI-based Systems): DataHubDxe.efi – DataHub protocol which provides parameters like OEM Model, FSBFrequency, ARTFrequency, Clover's boot-log and many other things to macOS which it cannot obtain otherwise. It has been fully integrated into Clover since r5129, so delete it. Newer versions of the Clover Package don't contain this driver anyway. EmuVariableUefi.efi – necessary for emulating NVRAM, if it is not available (legacy systems) or working incorrectly. FSInject.efi – For Kext injection. Necessary only for legacy versions of macOS ≤ 10.7 (Lion) which are capable of loading individual kexts instead of prelinkedkernel. Fully integrated in Clover nowadays, so delete it. OcQuirks.efi and OcQuirks.plist – delete if present. OcQuirks is a relic from earlier attempts to include OpenCore Booter Quirks into Clover up until r5122. SMCHelper.efi – Necessary when using FakeSMC.kext. If you use it in combination with VirtualSMC.efi, it can cause instant Kernel Panics. In other words: VirtualSMC + VirtualSMC.efi = good; FakeSMC + SMCHelper.efi = good; any other combination = bad. Nowadays, using VirtualSMC.kext alone is sufficient and recommended. Kexts: Outdated, incompatible and/or duplicate Kexts (and variations thereof) can cause boot crashes, kernel panics and general system instability. Therefore, you should always keep yout kexts up to date for maximum compatibility with macOS and Clover! You can use Kext-Updater to download the latest kexts and other Bootloader-related files. If you are using a lot of Kexts (usually on Laptops), have a look inside of them (right-click and select "show package contents") to check if they include additional kexts (as "Plugins") and make sure that no duplicates exist in the "kexts" folder – Kexts for HID, WiFi and Bluetooth come to mind. If you get panics you can not isolate, move all non-essential kexts to the "off" folder temporarily to work around the issue by starting with a minimal set of Kexts to get the system running. Once it runs, put the disabled Kexts back one at a time, reboot, and repeat until you to find the culprit for the panic and look for a solution (verbose mode is your friend). Here are some examples of Kexts I've experienced issues with when updating: VoodooPS2Controller.kext: can cause Kernel Panic if one of it's Plugins (VoodooInput.lext, VoodooPS2Mouse.kext, VoodooPS2Trackpad.kext and VoodooPS2Keyboard.kext) is also present at the root level of the "kexts" Folder. AirportBrcmFixup.kext: this Kexts contains 2 Plugins, AirPortBrcm4360_Injector and AirPortBrcmNIC_Injector.kext. When using AirPortBrcmFixup, you are supposed to use only one of these plugins, not both! Using both can cause the boot process to stall indefinitely. On top of that, AirPortBrcm4360_Injector is not supported by macOS Big Sur and has to be disabled anyway. In OpenCore, you can just disable a Kext in the config. Since the Clover config does not support to take control of the kext loading sequence, you have to delete it from the Kext itself (right click on AirportBrcmFixup, select "Show package contents" > "Plugins"). BrcmPatchRAM and a bad combination of it's accompanying kexts can cause issues as well. Don't use BlueToolFixup.kext and BrcmBluetoothInjector.kext together. Former is needed for enabling Bluetooth in macOS Monterey where the latter is used in earlier versions of macOS. Updating your EFI Prepare an USB Stick. Format it to FAT32 (MBR). We'll use it for testing our updated EFI Folder first, before copying it to the ESP on the HDD. Download the latest Clover Release as a .zip archive for a manual update: https://github.com/CloverHackyColor/CloverBootloader/releases Extract the .zip. We'll create our EFI Folder based on the one inside of it. Have a look at "EFI > Clover > drivers > off > UEFI" and it's sub-folders. Inside of them, you will fibd the following Files: Copy the following files over to EFI > Clover > drivers > UEFI: ApfsDriverLoader.efi, VBoxHfs.efi (or HfsPlus.efi, which is faster) and OpenRuntime.efi Now we have a minimal set of Drivers (see screenshot below). Files tagged in gray are in the "drivers" Folder by default and are most likely unnecessary for UEFI-based systems. I would move them into the "off" folder one by one to disable them and check if the system still boots from the USB stick without them. AudioDXE.efi is only needed for playing back audio files like boot chimes - so if you don't use any, you can delete it. As mentioned earlier, SMCHelper MUST be deleted when using VirualSMC.kext! Next, copy over your kexts (updated to the latest available version, of course), your ACPI > patched folder and your config.plist form your existing EFI Folder Open Clover Configurator and update it to the latest Version. It should now include a new section at the bottom called Quirks, as mentioned earlier Now open your config.plist you copied over from your working EFI and click on "Quirks". It should look like this (without the descriptions of course): Head over to the OpenCore Install Guide and pick the guide for your CPU Family and Platform. Jump to the "Booter" Section. It contains all required Booter Quirks tinted green in the screenshot. Make sure to unfold the "more in-depth info" box to see what they do. Find the options for your system and tick them away in Clover Configurator. Next, jump to the "Kernel" section of Dortania's guide and copy over the settings from "Quirks" and "Scheme". Again, make sure to unfold the "more in-depth" section to find all necessary settings. NOTE: some of the settings Located in "Kernel > Quirks" have different names and are located in the "Kernel and Kext Patches" section of Clover Configurator. These include: In most cases you have these set up correctly already, otherwise your system wouldn't have started before. But it's good to double check if you have settings enabled which may be unnecessary. Once you've ticked all the necessary quirks, save your configuration, copy the new EFI Folder to the root of your USB Flash Drive and try booting from it. If everything was set up correctly, the system should boot as expected. In the Clover Boot menu, perform an NVRAM Reset (F11) to clean out possible remnants of previous Aptio Memory Fixes and then start macOS. If it does boot, you can mount the ESP partition of your hard drive, backup your ole EFI Folder, delete it and put in the one from your USB Flash drive to make the changes permanent. VALIDATING YOUR CONFIG and FIXING ERRORS: Starting from version r5134, Clover now includes error reporting similar to OpenCore which displays configuration errors before the actual boot menu appears. Do the following to validate your config and fix configuration errors: Download CloverConfigPlistValidator.zip contained in the Assets of the Clover release: https://github.com/CloverHackyColor/CloverBootloader/releases Unpack it Open Terminal Drag CloverConfigPlistValidator into it and hit the right arrow key once, so the file path is no longer highlighted Next, drag and drop your clover config.plist into the terminal window. Make sure there is a blank space between the 2 file paths Hit "Enter" Check the results. If it says: "Your plist looks so wonderful. Well done!", then you don't have to do anything else. If there are errors shown in the log, open both your config.plist and the config-sample.plist included in the Clover download – preferably in a plist editor. Look for any differences (like formatting, deleted features, etc.) and fix them Save your config Re-check for errors Repeat comparison, fixing, saving and re-checking until all issues are resolved FURTHER RESOURCE AND TROUBLESHOOTING: General Clover Config Setup (for systems up to Coffeelake, excluding Quirks): Hackintosh Vanilla Desktop Guide To find out more about how OpenCore differs from Clover and see which settings, drivers and features are compatible, check out the Clover Conversion Guide. Clover Changelog: https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/ If you get Kernel Panics: head over to the OpenCore Troubleshooting Guide and have a look at the "OpenCore Boot issues" and "Kernelspace Issues" sections to find your error message and possible fixes to resolve it. Fixing Network issues after Clover Update: Have a look at this Check my "Clover Configurator ACPI Section Explained.pdf" to learn more about the all important ACPI Section of Clover Configurator. I've spend a lot of time and effort translating it from russian and making it useable Clover_Configurator_ACPI_Section_Explained.pdf Good luck! PS: If you run into trouble after following this guide you can upload your config.plist and I can have a look at the quirks. PSS: When running Big Sur, you need to remove the PreBoot Volume from the "Hide" Section of the GUI because if I understand correctly, Big Sur requires booting from it. PSSS: if your system boots correctly you can upload a screenshot with your quirks with additional Info like your Board and CPU which might be helpful for other users.
    19 points
  10. Rev 5123->5125 Since rev5123 we make joined bootloader Clover+OpenCore. It started as Clover using Clover's GUI and ability to change settings and then started OpenCore to inject and patche kexts and start macOS. Starting Windows and other OSes is done by Clover's way. There are new section in config.plist named Quirks that collect setting for OpenCore but some setting is just delegated from Clover because it can change it on the fly. There is a correspondence of OpenCore and traditional Clover settings to easy migrate from OpenCore to new Clover. OpenCore Clover AppleCpuPmCfgLock AppleIntelCPUPM AppleXcpmCfgLock KernelPm DisableRtcChecksum AppleRTC LapicKernelPanic KernelLapic About kernel and kext patches there is the follow. 1. OC accounts them as same and name "kernel" in the place of name of kext. Clover has different section for Kernel patches, kexts patches and Booter (boot.efi) patches. 2. Clover deal only with 64 bit arch while OC has "Arch" parameter. Other fields are OpenCore Clover Base Procedure Comment Comment Count Count Enabled Disabled Skip Skip Identifier Name Find Find Mask MaskFind Replace Replace ReplaceMask MaskReplace MaxKernel - MinKernel - - MatchOS - InfoPlistPatch - RangeFind 3. Procedure name in OpenCore must be long like __ZN8AppleRTC18setupDateTimeAlarmEPK11RTCDateTime Clover can use short name. In the example it can be setupDateTimeAlarm. 4. OpenCore assumes byte mask while Clover assumes bit masking. In the case of 0xFF00FF it will be the same. More careful see documentation for OpenCore and samples for Clover at this page. 5. RangeFind restrict search in Clover by several bytes. I don't know if OpenCore is able do the same. 6. Patches in OpenCore can be "Enabled" by setting the variable while in Clover they are enabled by default. User can disable it in the config.plist or in Clover GUI. 7. For Kernel patches we had additional "StartPattern" and corresponding "MaskStart" to define a place from what we want to search. OpenCore has no such service. Later we will extend the possibility.
    19 points
  11. Please read carefully the message from @vit9696, it is always an excellent source of information about the evolution of OpenCore and hackintosh in general. This time changes and improvements are a lot. OpenCanopy has been revamped with changes in any aspect related to the picker graphical interface. New icons have been added, labels have been improved, initial pointer position has been changed, keyboard and mouse behaviour have been improved, etc. It is almost a new driver due to the big amount of modifications. Other drivers as well have improvements, CrScreenshotDxe for example. External tools have also been improved, especially ocvalidate and ocpasswordgen. The same applies to OpenCore tools: OpenShell, ControlMsrE2 (successor to Brumbaer's CFGLock), etc. Config.plist file brings several changes, the most significant being new UEFI > AppleEvents section that allows you to configure keyboard and mouse behavior. Apart from all this, documentation has been reviewed and updated. Anyway, OpenCore developers have worked very hard and offer us this 0.6.8 version much improved compared to the previous one. config.plist A lot of changes to make text more readable and understandable, including typos corrected ACPI > Patch: added 2 new properties, Base and BaseSkip: Base (String): ACPI path base for patch lookup (ex. \ _SB.PCI0.LPCB.HPET), it can be empty BaseSkip (Integer): number of found Base occurrences to skip before finds and replacements are applied, it can be zero Booter > Quirks: added ForceBooterSignature (Boolean) for set macOS boot-signature to OpenCore launcher, it can be False Misc > Boot > LauncherOption (String): until now there were 3 options, Disabled, Full and Short, added a 4th option System that creates no boot option but assume specified custom option is blessed. Most of us use Disabled or Full. UEFI > added new section AppleInput that provides more detailed control of Apple Event protocol. It has 6 properties: AppleEvent (String): determines whether OC builtin or OEM Apple Event (if available) protocol is used. In general OpenCore’s re-implementation should be preferred. It can be Auto (failsafe), Builtin and OEM. I use Builtin CustomDelays (String): enables custom key repeat delays. It can be Enabled (the values KeyInitialDelay and KeySubsequentDelay are used), Disabled (Apple default values of 500ms (50) and 50ms (5) are used) and Auto (failsafe) (treated as Enabled when KeySupport is true and Disabled otherwise). I use Auto KeyInitialDelay (Number): when not using KeySupport, this option will configure the initial delay before key repeat as expected. The Apple OEM default value is 50 (500ms). I have 0 (acts as 50, or 500ms) KeySubsequentDelay (Number): configures subsequent keyboard repeat delay in OpenCore. The Apple OEM default value is 5 (50ms). I have 5 (acts as 25, or 250ms) PointerSpeedDiv (Number): configures the divisor for pointer movements. Failsafe value is 1. 0 is an invalid value for this option. I use 2 to have a slower pointer. PointerSpeedMul (Number): configures the multiplier for pointer movements. The Apple OEM default value is 1. UEFI > ProtocolOverrides: deleted AppleEvent. OpenCanopy driver Huge list of improvements, it is probably one of the OpenCore elements that receives the most changes in this new version: Improvements in almost every aspect of the driver Improved presentation of labels Improved presentation when UIScale=2 Improved support for mouse pointer that is now displayed centered on the screen by default. For it to work you must enable pointer control in the picker: the value of Misc > Boot > Picker Attributes must be 17 (0x11) if you normally use 1 (0x01). Added new icons, required icons currently are:1. AppleRecv / 2. AppleTM / 3. BtnFocus / 4. Cursor / 5. Dot / 6. Enter / 7. HardDrive / 8. Left / 9. Lock / 10. Password / 11. Restart / 12. Right / 13. Selected / 14. Selector / 15. SetDefault / 16. Shell / 17. ShutDown / 18. Tool / 19. Windows. But some others can be added to improve the design: Apple, ExtAppleRecv, ExtAppleTM and ExtHardDrive. Even ResetNVRAM or Linux icons. Notes about OpenCanopy: Resources > Image folder must have one item of each type of icon to get graphic picker (External). You can download the Resources folder with all required elements from acidanthera. These are the default icons made by OpenCore developers. Its purpose is to display the picker as it is displayed on real Macs. But there are already some OpenCore 0.6.8-capable themes designed by others users. For example, Default-StarWars by @chris1111 or BsxDarkFence series by @blackosx, all of them high quality themes. Left and Right only appear when the row of icons does not fit the width of the screen, they are used to move along entries. Restart and ShutDown icons are placed at the bottom of the screen, they can be reached by mouse pointer or by Tab key. These icons are highlighted by BtnFocus when selected Dot, Lock, Password an Enter are used if we have configured password for OC. Selector changes to SetDefault when you press the Ctrl key so that, if you press ENTER at the same time, the entry is marked as default bootable device. Recovery entries now have (dmg) suffix. macOS volumes are shown with the generic HardDrive.icns icon but, if there is an Apple.icns icon, they are shown with this specific icon (this isn't related to OpenCore 0.6.8, just to remember). Really default cursor position isn't fully centered but has a slight offset to the right to match Apple picker. CrScreenshotDxe driver Improved screenshot making driver, saving images to the root of OpenCore partition (ESP) or any available writeable filesystem, upon pressing F10. This is a modified version of CrScreenshotDxe driver by Nikolaj Schlej. ocpasswordgen Although ocpasswordgen utility exists since version 0.6.7, new icons specific to this feature have been added: Dot, Lock, Password and Enter. To set a password to OpenCore you have to run ocpasswordgen in Terminal. >> ./ocpasswordgen Please enter your password: acidanthera PasswordHash: <63ebfabb7271ba639b74688b45e99ea7b1ef9f8e71b113f5a27de914a577b705fd2a062445cc6af6fa921b49e5d1f9cdee94f4b4a7d75be15352eb39a5ad6c PasswordSalt: <de0cd941ed93a97e0927c86f7ab052e1> 2 hashes are generated, PasswordHash and PasswordSalt, which must be entered in the text boxes of the same name in Misc > Security, also selecting the EnablePassword option. This way, OpenCore presents the dialog to enter password to access the menu.
    17 points
  12. Dear forum dwellers and visitors, the team from CleverFiles is pleased to welcome you here. We've taken over this cozy Mac-devoted community space a couple weeks ago, and we are learning our ways around with the help of the friendly team of long-time admins and community supporters. First and foremost, we'll do our best to help the forums evolve and prosper. With some optimizations already under way, most of the sections you are all used to will live on. Expect a ton of new materials, FAQs and articles, product comparison and expert advice. You may have noticed the vastly improved speed, and tiny refinements here and there. The most important of those - we turned off all ads! We are committed to removing all distractions and boosting our communication on the way to the world's #1 fan-supported forums about Macs. We are open to your comments and suggestions. Have you found a bug or a forum issue, please report to our team asap. BTW, we are always looking for talented writers to help us with the new content (top-level English only, for now). Get in touch for our pricing offer. Seeking high quality, self-verified and self-uploaded content. Wordpress knowledge required. Contact us: send a direct message via these forums, email info@insanelymac.com or just post below... PS: Please excuse some technical turbulence the upcoming weeks while we are fine-tuning the new server. PSS: We are software developers, just like many of you. Our brainchild product is Disk Drill, the top data recovery app on the net. We'd appreciate a shout-out at www.cleverfiles.com - thx!
    17 points
  13. macOSDeveloperBetaAccessUtility.dmg.zip
    16 points
  14. Hello Everybody, I just wanted to update you lot about a few things. I have now moved away from Intel and im running a AMD build so I will no longer be able to delve deep into the inner workings of the Z390 platform so for this reason I am going to make my next EFI update my last. I will keep the threads open and continue supporting whenever I can but with the way things are now and the M1 Apple products out there it’s all abit pointless in my eyes. I want better gpu performance then my 5700xt has to offer and I’m sorry but for all the people thinking Big Navi will work one day with Big Sur well I believe your all dreaming cos I don’t think it’s going to happen. Why would Apple do anything more with Intel or AMD when they are moving away from them? You can’t integrate Arm and a discrete GPU so why would Apple release drivers for big Navi now? Even with my Ryzen platform I am having to cut corners for it to work properly with macOS. Like for instance I’m using a Gigabyte X570 Pro in my build yet I also have a Ultra and a Master both sitting here that are both much better boards but I use the Pro cos it works the best in hackintosh land. I would much rather have the Mastsr or Ultra as my board and a 6800Xt or 3080 as my GPU. I also own a M1 Mac Mini and like it enough to happily use it for the stuff I do in MacOS, It’s not the monster that people like to pretend it is and I can make it hit it’s limit easily but using it it’s plain to see that it’s a game changer and will only get better in time (quickly). Lastly the thread EFI’s are perfect so once a new version of OpenCore is released you can update to it very easily yourselves and use a sanity checker to make sure all your changes are right.  Im not disappearing and the thread is still here and there’s one more EFI update to come from me yet, It’s been a roller coaster of a year hasn’t it people? Stay safe and stay happy, have a lovely Christmas (as much as you can do) and next year things will hopefully get better for us all. Merry Christmas AG
    16 points
  15. This is my first fully functional Ryzen Hackintosh after many many years of intel builds and when I say fully functional I mean just that. Everything is working bar SideCar of course as there's no IGPU and I'm using SMBios iMacPro1,1 but as for everything else goes like proper sleep, Wake, All iCloud functions, Handoff, AppleWatch Unlock etc etc all works beautifully. I have fully mapped out USB manually on all ports and there's no micro stutters or freezes or anything else strange that you can think of. A big huge Thank you too @Shaneee For he's amazing patches and help when I needed it and a I couldn't put up a thread like this without showing my respect to the jedi master @MaLd0n, You both rock PLEASE NOTE - The EFI has now been expanded and usb has been fully mapped to included the X570 Pro, Pro Wifi and Ultra. No changes to the EFI are needed for any of the above boards, Just add your info and away you go. If you want to use the internal intel wifi and bluetooth combo card then make sure you download and instal the correct kexts from here. https://github.com/OpenIntelWireless Build Spec CPU: Ryzen 9 5900X Motherboard: Gigabyte AORUS X570 Pro (Bios Revision - F33a) RAM: Corsair Pro Vengeance 32GB DDR4 3600Mhz (Tuned) Graphics: Sapphire RX 6800 Case : Lian Li PC-O11DW Dynamic NVMe: Samsung 970 EVO 1TB & Samsung 970 EVO Plus 1TB SSD: Samsung 860 EVO 1TB HDD: Seagate Barracuda 1TB PSU: EVGA SuperNOVA 850 G5, 80 Plus Gold 850W WiFi-Bluetooth: ABWB BCM94360CS2 802.11AC WI-FI With Bluetooth 4.0 PCIe Sound: Onboard & Native Instruments Audio 6 Cooling : Arctic Liquid Freezer II 360 AIO Installed Operating Systems: Big Sur 11.4 - Windows 10 Pro Bootloader: OpenCore 0.6.9 ACPI SSDT's SSDT-USBX.aml (USB power tables) SSDT-PLUG.aml (CPU power management) SSDT-SBRG.aml (Correcting EC, RTC Memory & IRQ Conflicts) SSDT-SBUS-MCHC.aml (Correct SMBus) SSDT-XHC.aml (USB rename's) Kexts Lilu.kext VirtualSMC.kext WhateverGreen.kext AppleALC.kext SmallTreeIntel82576.kext AMDRyzenCPUPowerManagement.kext SMCAMDProcessor.kext USBMap.kext What Works Sound including the case's front headphones 3.5mm port Ethernet Port WiFi / Bluetooth USB Type C, 3.0 & 2.0 (All ports Mapped & Open) AirDrop iCloud Hardware Acceleration iMessages Facetime Sleep & Wake Sleep and Shutdown via the Power Button Power Nap Handoff Netflix on Safari browser Continuity Apple Watch Unlock What Doesn't Work Sidecar Bios Settings Enter BIOS -> Press Delete -> Enter Setup Save & Exit -> Load Optimized Defaults Boot -> CSM Support -> Disabled Boot -> Fast boot -> Disabled Boot -> Secure Boot -> Disabled Settings -> IO Ports -> Above 4G Decoding -> Disabled Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Auto OpenCore EFI Update V0.7.3 - 07/09/2021 Gigabyte X570 Pro 7,1 073 EFI.zip - OpenCore v0.7.3, SMBios MacPro7,1 SMBIOS iMacPro1,1 Conversion Kit - 07/06/2021 Gigabyte X570 Pro 1,1 Conversion Kit.zip IMPORTANT BIOS CHANGE Settings -> IO Ports -> Above 4G Decoding -> Disabled IMPORTANT NOTE - PLEASE DISABLE ABOVE 4G DECODING IN THE BIOS. I HAVE DISCOVERED A SERIOUS FLAW IN THE GIGABYTE BIOS EFFECTING THE GPU PERFORMANCE AND THE ONLY WAY TO FIX IT WAS TO DISABLE ABOVE 4G DECODING IN THE BIOS AND TO ADD THE BOOT ARGUMENT npci=0x2000 TO THE CONFIG.PLIST. Note 2 - I have decided to fully bypass OpenCore when booting into any other OS other then MacOS so now Windows and Linux no longer see your PC as a MAC and no parts of the ACPI, Patches, MacOS Details or anything else is loaded into any other OS. Note 3 - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments. Note 4 - The SmallTreeIntel82576.kext is not working under Monterey 12.0. Current EFIs Change-Log Updated 07/09/2021 EFI Install Notes Using PlistEdit Pro add your details by modifying the following IMPORTANT PATCH INFO TO SET THE CORRECT CORE COUNT FOR YOUR CPU Core Count patch needs to be modified to boot your system. Find the three algrey - Force cpuid_cores_per_package patches and alter the Replace value only. Changing B8000000 0000/BA000000 0000/BA000000 0090* to B8 <CoreCount> 0000 0000/BA <CoreCount> 0000 0000/BA <CoreCount> 0000 0090* substituting <CoreCount> with the hexadeciamal value matching your physical core count. Note: The three different values reflect the patch for different versions of macOS. Be sure to change all three if you boot macOS 10.13 to macOS 12 See the table below for the values matching your CPU Core Count. CoreCount Hexadecimal 6 Core 06 8 Core 08 12 Core 0C 16 Core 10 32 Core 20 So for example a 6 Core 5600X Replace value would result in these replace values, B8 06 0000 0000/BA 06 0000 0000/BA 06 0000 0090 Or a 12 Core 5900X that I have it setup as standard would result in these replace values, B8 06 0000 0000/BA 0C 0000 0000/BA 0C 0000 0090 12 Core EXAMPLE Additional Tools and Files PlistEdit Pro.zip - PlistEdit Pro (use to edit OpenCore) https://github.com/headkaze/Hackintool/releases - Hackintool Screenshots & Benchmark Results If you have any questions or need any assistance with using this EFI then feel free to get in touch.
    15 points
  16. Hello everybody, here's Clover Suite Builder is now Menulet the evolution of what you were used to know as builme New Setup The main goal, and the way this new tool has been designed is to be of use for the largest possible Clover's users and that means Not Only those used to clone the repository and having buildme do the rest. Clover Suite Builder will provide support also for those not inclined or not familiar with Terminal. And essentially you can place it anywhere into you drive, it doesn't need be placed into Clover folder to work correctly. and Clover Suite Builder will be available just by clicking the icon... Some infos about this version. Its advised to delete any old release before testing. as this one and app versions have been updated How it works: Once launched it will just sit on top your menubar to activate just click on the Icon and main Window will show up Quit Options. By pressing quit from any window other then Main Window the menu will stay operational so you can recall the app whenever you need To completely exit the application you have to choose to Quit From Main window. *** warning RE-Updated Quit function *** (1.3r4) The reason why i've reverted back to previous behaviour is for practical reasons. I don't know how many among you, use the terminal in daily basis, and having such a kind of behaviour, becomes very unpractical for those who do use it very often. So here we go latest release Download Release 1.3r4 Clover Suite Builder 1.3r4-menulet.dmg 1) if somehow (for testing or other reasons) the Clover Directory is not in place you will get this 1.1) Can now Download Clover from source, Get all Utilities known, Extensions, and Install to EFI 1.2) Added an ulterior warning if somehow you didn't saw the previous and try to build Clover 1.3) while and end of download 2) new Builder design, splitted int 2 columns (i know you see 3, but logically they are 2) main change here is - added links to online documentation - ccpv, is automated for your installed config, it wiil open your EFI and verify your config.plist 2a) sorted extra builds into another menu, - added new options to build boot6 and boot7 separately GCC53 (Slice's whishes) - added also options to build boot6 and boot7 separately with Xcode8 2b) As already noticed, now show Status, Diff are exported to text - you now have also build logs, possibility to open logs directory and to clear all 2c) as announced above, Links directly to online Documentations but also add links to known DSDT's patches you may need for your machine 2d) visual of online docs 2e) visual of online pre-built DSDTs 3) Utilities has been renamed to Tools and added a few more to the list 4) it has now its own Kexts builder - there I added the most common, and differently from my old friend "Lilu Suite Builder" it download / build only the one you choose. All kexts will be put on Kexts directory and from there you can also choose to install/update into EFI or Library/Extensions 5) - It can backup your EFI, - update your current boot files (at the moment only those who build their own copy are allowed) - Install (for now it only uses the installer.pkg for both users, but it is on todo list for futures releases and will be corrected) 5a) - The Updater will let you update your boot files - Depending on your boot installation - Even if using bootloaderchooser you can choose to update by selecting that option This finally is the new files structure you'll have into your src folder Now into src/ will be present, the new created directories, used to store all new items it will manage, kexts, tools etc, Feel free in the mean time to leave your impressions and suggestions. Thanks P.S if you happen to Download the @ic005k PlistEDPlus and QtiASL you may have a surprise. As (very sorry ic005k, i apologize in advance for what i'm going to write here) i really can't be at peace using those icons, during install they will be replaced by my created ones. Of course,if they are not of your liking, or just think its inappropriate for the application just tell me and will be removed.
    15 points
  17. @Slice @Jief_Machak verry proud and happy to announce that the Clover package is correct for macOS Big Sur 11 and works on all other macOS versions. There are no more Clover files installed on the Root disk, everything done in / Private / tmp No need for the java script package for the read / write disk anymore, I will remove it from the Distribution UEFI and ESP Legacy mode is fully functional, Backup Clover is done on the desktop. I give you the files that I have to modify to be done. File on Github ➤ Fix Package Clover any macOS
    15 points
  18. Please read the message from @vit9696 with the best summary you can read about what's new in OpenCore 0.7.1. This time we may think that we are facing a minor OpenCore update because we have to learn and modify an affordable number of features. Nothing comparable to June's update. However this is not entirely true. What happens is that the 0.7.0 update was huge, much more complex than usual. This 0.7.1 update may seem simple compared to the previous one but it does not stop having important changes: more than 60 builds have been released some bugs have been fixed documentation has been improved (adding debug docs updates) OpenCanopy continues to receive improvements builtin firmware versions have been updated PCI device info dumping has been added to SysReport new kext patcher for Lilu, supporting macOS from 10.6 to 12 For Monterey: OpenCore and kexts have been adapted to macOS 12 Monterey added BlueToolFixup to fix Bluetooth issues on macOS 12 For Windows 11: added a document containing requirements and potential paths to work around them added TpmInfo.efi tool to check TPM status. config.plist ACPI > Quirks > added SyncTableIds (boolean): to sync table OEM identifiers with the SLIC table to prevent licensing issues in older Windows operating systems. It can be False. Kernel > Scheme > added CustomKernel(boolean): to support custom kernels from the Kernels directory located at the root of the ESP partition. For unsupported platforms including Atom and AMD that require modified versions of XNU kernel in order to boot. It can be False. OpenCanopy Fixed transparency click detection on OpenCanopy boot entries for the icon to be selected when clicking on the transparent areas. Note for artists: transparent areas of icons can have opacity=1% to ensure correct operation, although in theory it is not necessary with this OpenCanopy enhancement. Added recommended Apple12 and Windows11 flavours. Fixed various bugs. Improved documentation. Tools TpmInfo.efi: to check Intel TPM capability on the platform, which allows using TPM 2.0 if enabled. The tool does not check whether TPM 2.0 is actually enabled or disabled. TpmInfo must be run from the UEFI Shell, if it is run from the picker it shows a text message so short that it is impossible to read what it says. ocvalidate Fix path length calculation and remove the wrong check for Misc > Entries > Path and Misc > Boot > PickerVariant. Sometimes ocvalidate showed an error message (path too long) even if it did not exceed 128 bytes. As per ocvalidate's Readme: "All the paths relative to OpenCore root must be 128 bytes total". kexts It's recommendable to update kexts to the new versions: AirportBrcmFixup AppleALC BrcmPatchRAM CPUFriend IntelMausi Lilu NVMeFix RestrictEvents SidecarFixup VirtualSMC VoodooPS2 WhateverGreen.
    14 points
  19. If I have the time I will try to put up 0.7.4 EFIs for you all when it releases. No promises though but I will try to get it done.
    13 points
  20. 13 points
  21. I updated DirectHW and pciutils-3.7.0 for macOS Big Sur. It has 4 PCI accessor methods: - default: darwin accessor, requires boot arg debug=0x144 & run as root. - intel-conf1: DirectHW accessor 1, requires root - intel-conf2: DirectHW accessor 2, requires root - dump: read from dump file * You can set these with the -A flag. DirectHW for macOS Big Sur repo: https://github.com/vampirecat35/DirectHW-BigSur pciutis-3.7.0 for macOS Big Sur repo: https://github.com/vampirecat35/pciutils-osx Flashrom-1.2 for macOS Big Sur repo: https://github.com/vampirecat35/flashrom-osx iwleeprom for macOS Big Sur repo: https://github.com/vampirecat35/iwleeprom-osx ectool, msrtool, inteltool, ifdtool, superiotool, mptable, osxpmem and nvramtool repo: https://github.com/vampirecat35/hwtools-osx ECTool for macOS: Tool to read embedded controller info. nvramtool for macOS: Tool for nvram info. inteltool for macOS: Intel CPU/chipset info. msrtool for macOS: Model Specific Register info. iwleeprom for macOS: Flashing and reading Intel ROM and Atheros ROM to WiFi card. EDIT: Built a version for Mac OS X 10.9 and above. It targets Xcode's minimum deployment target (10.9) It's bundled inside the hwtools zip file. DirectHW for older targets also attached now (DirectHW-macOS). Also replaced hwtools zip file (fix kext). EDIT2: Fixed nvramtool for macOS. Changed /dev/mem to /dev/pmem for Apple. Needs MacPmem.kext (included in hwtools zip file). EDIT3: Added new AMD+Intel CPU models to msrtool. Added AMD family 16 and 17. Added Intel *lake cpu models. Added sandy bridge cpu models. EDIT4: Fixed nvramtool. EDIT5: Added superior-tool and ifdtool. EDIT6: iwleeprom fixes. EDIT7: New approach to iwleeprom. pciutils-3.7.0-osx.zip DirectHW-BigSur.zip flashrom-v1.2-osx.zip ectool-osx.zip inteltool-osx.zip DirectHW-macOS.zip msrtool-osx.zip nvramtool-osx.zip OSXPMem.zip mptable-osx.zip superiotool-osx.zip ifdtool-osx.zip iwleeprom-osx.zip hwtools-osx-10.9-and-above.zip
    13 points
  22. The day has come boys......
    13 points
  23. Good Morning/Evening/Night for all (without quotes )... tomorrow its possible in Apple event release Big Sur...
    13 points
  24. Most of us have, probably, never met, yet we all build some kind of relationship in these forums. You will always be remembered artur_pt and I will always remember “good hack”.
    13 points
  25. I made a new driver for Realtek card readers, and I would like to invite people to join the beta testing. Please use this thread for general discussion and test reports. This driver is based on the Linux driver module `rtsx_pci/usb` which is contributed by engineers from Realtek and therefore is more mature than the FreeBSD/OpenBSD driver. But I wrote this driver from scratch instead of blindly copying the code from Linux to macOS, so there is no compatibility layer (and performance degradation introduced by the compatibility layer) at all. This driver supports SDSC/HC/XC cards and UHS-I SDR12/25/50/104 and DDR50 modes. I tested my RTS525A with a SDXC card and got about 75MB/s read speed and 60MB/s write speed. Note that your card may support even higher speed but your card reader may be limited by the OEM. Always test your card under Windows or Linux to get an estimate on the threshold. Use the `dd` command to get a precise estimate on the I/O speed under macOS. As a bonus, your card reader will be recognized as a native one and is listed under Card Reader in System Information. You need to install the companion Lilu plugin `RealtekCardReaderFriend` which is available at https://github.com/0xFireWolf/RealtekCardReaderFriend/. As of v0.9.5, USB-based RTS5129, RTS5139 and RTS5179 are supported. Please give a try and report any issues, as I don't have these chips thus cannot test them. Feel free to report any issues. Detailed information can be found in the Github repo (https://github.com/0xFireWolf/RealtekCardReader). Downloads: https://github.com/0xFireWolf/RealtekCardReader/releases Enjoy -- FireWolf
    12 points
  26. Hi guys, after a while I am back posting news about that new TINU version compatible with Monterey i have been teasing in the past. I have released it and here is the download page for the new version: https://github.com/ITzTravelInTime/TINU/releases/tag/3.0_RC_(101) And some pictures if you are curious: EDIT: I have also published an bug fix release and updated the download link here.
    12 points
  27. for macOS Monterey i am working on a new version of TINU, the app has been migrated to swift 5, has native Apple Silicon support, new icons and improved graphics and of course I am testing it on the new os, it still isn't quite ready for release but the latest released beta version will work with the new OS release.
    12 points
  28. As always, it is highly recommended to read @vit9696 message. It is the best place to find out what is new and changed in the new version of OpenCore. This step from 0.6.8 to 0.6.9 brings quite a few changes and some of them are very important but they are not as many as in the step from 0.6.7 to 0.6.8. Some of the things that have been improved: AppleEvents and some of its keys compatibility with older systems OpenCanopy and the picker presentation OpenCore password decryption speed, especially on slow systems memory devices on MacPro7,1 SMBIOS. config.plist Misc > Boot > PickerAttributes: OC_ATTR_USE_MINIMAL_UI (0x0040) will hide Restart and ShutDown buttons in the picker (text and OpenCanopy). Misc > Security > ExposeSensitiveData: OCS_EXPOSE_VERSION_UI (0x04) will show OpenCore version in OpenCanopy. Misc > Tools: added support for case-insensitive argument handling in the UEFI tools. UEFI > AppleInput > CustomDelays new type Boolean (former String). It can be False. UEFI > AppleInput > KeyInitialDelay and KeySubsequentDelay failsafe values to Apple OEM values (50 and 1). UEFI > AppleInput > PointerSpeedMul failsafe value changed to Apple OEM value (1). UEFI > Quirks > added EnableVectorAcceleration: enable AVX vector acceleration of SHA-512 and SHA-384 hashing algorithms. Failsafe value is False. If it's true, the signature verification process when OpenCore has a password is faster. UEFI > Quirks > added quirks to increase compatibility with older Mac firmwares: - ForgeUefiSupport (Boolean): to workaround legacy EFI 1.x firmwares compatibility. Failsafe value is False. - ReloadOptionRoms (Boolean): to force-load Option ROMs on PCI devices. Failsafe value is False. Only for MacPro7,1 SMBIOS PlatformInfo > Memory > Update SampleCustom.plist with MacPro7,1 memory samples. Only for empty slots: PartNumber and SerialNumber now are empty (previous value was 0) Size and Speed = 0 (previous value was 1) Manufacturer = NO DIMM (previous value was empty). For all slots (filled and empty): DeviceLocator values are ChannelA-DIMM0, ChannelA-DIMM1, ChannelB-DIMM0, ChannelB-DIMM1 and so on up to 12 devices. It is recommended to use RestrictEvents.kext to eliminate the warning displayed on the desktop at startup. OpenCanopy Added PickerAttributes: OC_ATTR_USE_MINIMAL_UI to allow running pickers with no Shutdown and Restart buttons. Added ExposeSensitiveData: OCS_EXPOSE_VERSION_UI (0x04) to display OpenCore's version number to OpenCanopy as well as builtin picker. Fallback to builtin picker when OpenCanopy fails to launch or has low resolution. Fixed wraparound when using arrow keys in OpenCanopy: arrow keys will wrap around the boot entry list. Updated kexts AppleALC.kext IntelMausi.kext Lilu.kext NVMeFix.kext RestrictEvents.kext SMCSuperIO.kext VirtualSMC.kext. WhateverGreen.kext These kexts have new versions, it's advisable to use them with OpenCore 0.6.9.
    12 points
  29. OC Developers, I frequently review your github repo and each time I finish my review, I'm blown away by the volume of work and attention to configuration management. Just when I think your work load will diminish in a subsequent release, I see that your work load has actually increased, yet you relentlessly persist. Your work is impeccable. In addition to the challenge and reward of hacking my own rigs, the thing I will miss most when I switch to Apple silicon is watching you all work your magic. You have and continue to do an incredible job. Thank you!
    12 points
  30. Hey, look this matter! Some guys are going crazy about it. Some of them thinks that it's a secret Apple's project lol The source: https://videocardz.com/newz/amd-ryzen-9-5950x-overclocked-to-6-0-ghz-with-apple-imac-pro But, look something familiar to us at the Geekbench's result page:
    12 points
  31. macOS Big Sur 11 beta 10 (20A5395g)
    12 points
  32. 12 points
  33. Everyone : wait a little. Yes, my "opencore_integration" doesn't work (it sort of). Problems have been identified and I'm sorting out "side" problems after haveing made sure that BigSur can boot : previous macOs boot, windows boot. Maybe that setting (ProvideConsoleGop) will disappear, or move. We have to decide few things. All I did was an experiment. That means I didn't work on proper default values, or a proper name for Quirks in config.plist. Let us talk and I'll get back to you.
    12 points
  34. Thank you @Hervé So guys, I'll move all the posts talking about the I225 + Monterey to the proper Forum area. Thanks EDIT: Done! You all can continue talking about it here: [Discussion] Intel i225-V on macOS Monterey
    11 points
  35. Not sure whether they actually wanted to drop support for Nvidia GPUs... All legacy NV drivers are still there though. Changing SMBios should work then. By the way, I have added Monterey support to Lilu, AppleALC, and WhateverGreen. And I will add the same thing to all plugins now! EDIT: All done!
    11 points
  36. Over the past few days, I've been working on ECEnabler, with u/midi1996's help with testing. ECEnabler is a Lilu plugin which allows macOS to read any size of EC field, meaning that no more ACPI patches are needed to split EC fields up within ACPI. I got tired of trying to make a complicated automated ACPI battery patcher (like SSDTTime), especially when dealing with all different vendors. I eventually had the idea to try patching macOS instead, which turns out to be much easier. Hopefully this saves you guys a little time with not having to go through Rehabman's patching guide Link: https://github.com/1Revenger1/ECEnabler Obligatory picture showing it working: There are a few caveats to this plugin: You may still need ACPI patches to combine data from 2 batteries This plugin will not help some devices such as the Surface Pro 7 which don't use ACPI Operating Regions/Fields to get their battery info. Supported macOS versions: Mac OS X Lion (10.7) through macOS Monterey (12)
    11 points
  37. I don't understand why you want to hide warnings. Why would you want to keep problems in your config.plist ??? It's not a lot of work to clean. It's usually because of unknown keys, like "Ignore" in custom entries that never existed that I saw a lot. I called them warnings because Clover will "correct" and "ignore" this problems, but it is still problems. Just take 5 minutes and correct, and you won't need an ignore option. The day you'll immediately realise that your config plist modification doesn't work because of a misspelling, you'll be happy to get warning at Clover start. I'm a democratic guy. If a majority of people can convince that it is good to keep wrong keys in config.plist, I'll do the option...
    11 points
  38. https://github.com/ic005k/QtiASL Basic features include but are not limited to: * Automatically load the list of currently used SSDTs (under Windows and Mac) * Smooth and efficient editing environment, tens of thousands or even hundreds of thousands of lines of code can be edited very smoothly * grammar highlights * code automatic prompt * code folding * Show indent edit lines * Display case bracket matching * Multilingual support (currently supports Chinese and English) * you can freely define or select compilation parameters, and the compilation parameters are automatically saved. for specific compilation parameters, you can check iasl's help * edit the scene automatically restored after the software is opened, accurate to the cursor position * edit files with multiple labels, and the status of file editing will be displayed in real time (red dot and green dot on the label page) * Support DSDT+SSDT decompilation and batch decompilation * Support double-click to open files, drag and drop to the software interface to open files, and open the history of files * If the currently opened file is modified by other software, it will automatically prompt whether to reload. * humanized search function, and supports simple regular expressions * Search box supports history list and input auto-complete * Automatically mark all search results * Search result counter * Drag and drop tabs to form a new window * Unlimited levels of revocation and recovery * compile the wrong place, next to the line number with red dot to identify * perfect information display window, which can display "basic information", "error", "warning" and so on. click the contents in the information window to locate the associated code line ......
    11 points
  39. A very custom DSDT for best experience under macOS. Removed all unused devices, injected all Apple devices, essentials, cosmetics, real improvements. -OpenCore Vanilla TUTORIAL- -USB Port Mapping TUTORIAL- -Bios/UEFI Settings- Serial Port = Disable CFG Lock = Disable -Hardware- Mobo - Ga Z490 Vision G Processor - i9 10th Intel GPU - RX 580, 590, VEGA 56, VEGA64, 5600XT, 5700XT or RADEON VII Cooler - CoolerMaster Masterliquid ML360R RGB NVME - Corsair MP600 -EFI folders- -EFI OpenCore Folder https://tinyurl.com/ybr968w3 -EFI Clover Folder https://tinyurl.com/ybr968w3 Paste EFI folder into EFI partition, reboot and extract one SendMe. Post this dump here for full ACPI solution! Download RunMe.app dumper -DSDT Patches- -Screenshots- -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!
    11 points
  40. OpenCore 0.6.8 EFI Update (Big Sur 11.3 Ready), 5th April 2021 (Use With Bios Revision F12K or Newer) The EFIs and DSDTs have now been updated to the my latest versions. Changes made include, Lilu 1.5.2, AppleALC 1.5.9, WhateverGreen 1.4.9, VirtualSMC 1.2.2, OpenCore Updated to Revision 0.6.8 (Big Sur 11.3 Ready), OpenCanopy is Enabled as Standard, New OpenCanopy Icons, Mouse now working in OpenCanopy, Plus other minor tweaks and changes to all of the configs, OpenCore EFI Update v0.6.8 - 05/04/2021 OC 068 19,1 Z390 Pro EFI.zip - OpenCore v0.6.8, SMBios iMac19,1 OC 068 1,1 Z390 Pro EFI.zip - OpenCore v0.6.8, SMBios iMacPro1,1 (IGPU Disabled) Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments. Note 2 - Do not try to carry across your old OpenCore Config.plist to the new EFI as to many changes have occurred in 0.6.7. Use the new Config.plist instead. For OpenCore Using PlistEdit Pro add your details by modifying the following
    11 points
  41. This week has been full on with work but I've managed to put together my first actual theme; BsxDark1_ It's clean and simple and based on the mockup image I posted last week, but with some changes/refinements. The .zip includes 12 different background files (each for a different resolution) and the required icns files for OpenCore/OpenCanopy v0.6.8. There are also extra icns for Linux installs if the user wishes to use them. See the included ReadMe for setup instructions. Available at: https://github.com/blackosx/BsxDark1_ Note: I think I've included everything in the .zip, but if anything is in error or missing then please let me know.
    11 points
  42. I've continued to extend the Set3 icon range for the macOS drive images, this time with full out images in the icons.
    11 points
  43. Fixed version for Big Sur x86_64. Enjoy AnVMSR-BigSur.zip
    11 points
  44. [GUIDE] MSI MEG Z490I Unify ComponentsSingularity Computers WraithIntel i7 10700KMSI MEG Z490I Unify2x 32 GB 3200MHz Patriot Viper 4 Blackout RAMMSI RX 5700 XT Evoke OC1 TB Samsung 970 EVO Plus NVMeApple Broadcom BCM94360CS2 Bluetooth/WifiSeasonic Focus SGX-650 Watt PSUCableMod Custom PSU Cable4x Noiseblocker B12-PS FansPrehistoryThis build came about through a cooperation with igorsLAB and was supposed to be something very special.mITX form factor, Z490 chipset, powerful, quiet and water-cooled,which in itself is not an easy thing to do if you assume a mITX build.When it came to the case selection, I chose a Singularity Computers Wraith Case,because it has an integrated distribution panel with pump mount which makes it easier to build. We use a MSI MEG Z490I Unify motherboard which is equipped with a 10th Gen i7 10700K.For RAM we decided to use a 64 GB kit ala 2x 32 GB 3200 MHz Patriot Viper 4 Blackout with CL16-18-18-36.Because the mainboard can only be equipped with CNVi NGFFm2 modules,I was forced to come up with something regarding Bluetooth/Wlan.I removed the original Intel® AX201 NGFFm2 card from the module and installed new antenna cables including connectors.The original antenna cables were far too short for our use.The BCM94360CS2 is a Original Apple Notebook solution and does not fit into the NGFFm2 module,for this purpose one of the two NVMe slots that the board owns had to be sacrificed.With a DeLock m.2 Key -> m.2 Key E module the original Apple Broadcom BCM94360CS2 Bluetooth/Wifi card was installed into the NVMe slot.For the Bluetooth data connection I used the JUSB1 USB 2.0 Connector on the Motherboard. The 1 TB Samsung 970 EVO Plus with current Firmware was installed on the back of the motherboard.For this project Igor released a MSI RX 5700 XT Evoke OC from his private stock.For the water cooling components we got support from the company Alphacool, who completely equipped us with everything our heart desires.For the 10th Gen i7 10700K we use an Alphacool ice block XPX in the Polished Clear version.The MSI RX 5700 XT Evoke OC was equipped with an Alphacool ice block Aurora acrylic GPX-A GPU cooler including backplate. The cooling system is connected by Alphacool 13/10mm Black Chrome Tubes and Alphacool icicle PRO fittings in chrome.An Alphacool ice pump VPP755 pumps the coolant into the two 240mm Alphacool NexXxoS ST30 V.2 radiators.The radiators were equipped with 4x Noiseblocker NB-eLoop B12-PS Fans.The power is provided by a sponsored Seasonic Focus SGX-650 Watt SFX power supply,the original cables were replaced with cables from CableMod.A very big thank you to the sponsors at this point again: Alphacool, Blacknoise, igorsLAB and Seasonic! BIOSFirst download the following Bios File and the Bios Settings Profile attached to this post and extract them.Bios: https://www.dropbox.com/s/ea0dq7uzayu3ita/E7C77IMS.120.zip?dl=0Bios Profil: https://www.dropbox.com/s/m29ssxrthb0u2oi/Hackintosh Bios Settings.ocb.zip?dl=0Copy the two files to a Fat32 formatted USB stick and plug it into a free USB port.Start the computer and open the bios menu with the ESC key, then switch to EZ mode with the F7 key.Open the M-Flash menu You will be informed that your system will perform an auto reboot and start the flash mode.Confirm the selection with Yes. In flash mode you choose the firmware on your USB stick and confirm the flash process with Enter.After you have flashed the bios successfully and the system has rebooted,you open the Bios menu again with the ESC key and switch back to the EZ mode with F7.Afterwards you open the Save/Load Bios Settings OC PROFILE menu. Once there select the option "OC Profile Load From USB" and choose the "Hackintosh Bios Settings.ocb" file.Once the settings are loaded, save them with the F10 key before leaving the Bios.Alternatively you can also save the settings manually. BIOS SETTINGS PCIe/PCI Sub-system SettingsAbove 4G : EnabledSettings/Advanced/Integrated PeripheralsSATA Mode : AHCI ModeSettings/Advanced/Intel (R) ThunderboltDiscrete Thunderbolt(TM) Support : EnabledThunderbolt Boot Support : Pre-Boot ACLSecurity Level : No SecuritySettings/Advanced/Intel (R) Thunderbolt/Discrete Thunderbolt(TM) ConfigurationGPIO3 Force Pwr : EnabledSettings/Advanced/Intel (R) Thunderbolt/Discrete Thunderbolt(TM) Configuration/Thunderbolt(TM) OS SelectThunderbolt support : Enabled + RTD3Settings/Advanced/Power ManagementUSB Standby Power at S4/S5 : EnabledSettings/Advanced/USB ConfigurationXHCI Hand-Off : EnabledLegacy USB Support : EnabledBIOS CSM/UEFI ModeUEFISettings/BootMSI Fastboot : DisabledFastboot : DisabledSettings/Security/Secure BootSecure Boot : DisabledSettings/Security/Trusted ComputingSecurity Device Support : DisabledOC/Overclocking/CPU FeaturesCFG Lock : Disabled What do we need ?1. access to a computer where Windows/MacOS is already running2. macOS license or the operating system/Internet Recovery Files.3. a USB stick with 16 GB free memory.4. OpenCore EFIExample: Original Apple Mac OS X Snow Leopard DVD Create a USB flash drive via Windows What is required ?1. big sur recovery image : https://www.dropbox.com/s/kcp3pl83qgb6c2q/recovery.7z?dl=02. USB pen drive with 16 GB memory3. etcher for the recovery stick creation : https://www.dropbox.com/s/i5uurrk7zcwzmr4/balenaEtcher-Setup-1.5.112.exe?dl=0 Create a USB flash drive via macOS 1. open the App Store, enter Big Sur in the search bar and hit enter.2. start download and wait until it is completed.Once the download is complete, the following window will appear3. insert the USB stick and open the disk utility via Spotlight search 4. in the disk utility change the view to "Show all devices" first Now select your USB stick, in my case it is an Intenso cMobile Line Media USB Drive and select the option delete.A window will open and here you can set the settings for the formatting.Name: USBFile format : MS-DOS file system (Fat)Scheme : Master Boot RecordTo perform formatting, press Delete.If the process is successful, you will see the following window which can be closed then:5. enter Terminal in the Spotlight Search and run this application.Copy the command for Big Sur, paste it into the Terminal window and confirm with Enter.Big Sur: sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/USBCatalina: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USBIn the terminal the whole thing should look like this:5. you will be asked to enter your password, which you confirm with Enter.Don't be irritated by the fact that the password field remains empty even after you have typed the password.You will be reminded that the volume named USB must be deleted.Enter Y and confirm with Enter.Now the USB stick will be formatted and created correctly.This is how it looks like in the terminal when the stick has been created successfully.Congratulations - your macOS Install Stick is created Create the EFI for macOS via Windows What is required ?1. A bootloader: OpenCorehttps://github.com/acidanthera…penCore-0.6.3-RELEASE.zipGUI and HFSPlus driver for the bootloader:https://github.com/acidanthera…ryData/archive/master.zip2. to be able to configure the EFI, we need an additional Plist Editor. https://github.com/corpnewt/ProperTree/archive/master.zip 3. to facilitate the generation of the serials and SMBIOS data we need GenSMBIOS. https://github.com/corpnewt/GenSMBIOS/archive/master.zip 4. in order for our system to run as a hackintosh, some kexts are required.AppleALC = Audio https://github.com/acidanthera/AppleALC/releases/ Lilu - A versatile plugin that is required for both AppleALC and WhateverGreen. https://github.com/acidanthera/Lilu/releases LucyRTL8125Ethernet - Required for the Realtek® RTL8125B 2.5Gbps LAN controller https://github.com/Mieze/LucyRTL8125Ethernet SMCProcessor - Plugin for VirtualSMC - Allows to read CPU relevant data like temperatures etc.Can be found in the table of contents of VirtualSMC.SMCSuperIO - Plugin for VirtualSMC - Allows to read out CPU relevant data like fan speeds etc.Can be found in the table of contents of VirtualSMC.VirtualSMC - Apple SMC emulator including plugins - makes it possible to boot macOS https://github.com/acidanthera/VirtualSMC/releases Whatevergreen - Swiss Army Knife for GPUs, but now also includes many additional fixes https://github.com/acidanthera/WhateverGreen/releases You can download the kexts as a package here: https://www.dropbox.com/s/klfaadmfelwk937/Kext Files - MSI MEG Z490I Unify - Build.zip?dl=0 Additionally you have to download the BASIS-SSDT.aml https://www.dropbox.com/s/x8yn33yyizsnqoa/BASIS-SSDT.aml?dl=0 Create the EFI for macOS via macOS What is required ?1. A bootloader: OpenCorehttps://github.com/acidanthera…penCore-0.6.3-RELEASE.zipGUI and HFSPlus driver for the bootloader:https://github.com/acidanthera…ryData/archive/master.zip2. to be able to configure the EFI, we need an additional Plist Editor.We use the PlistEdit Pro under macOS, the trial version is absolutely fine. https://www.dropbox.com/s/bqradkm2pgiklep/PlistEdit Pro.zip?dl=0 3. to facilitate the generation of the serials and SMBIOS data we need GenSMBIOS. https://github.com/corpnewt/GenSMBIOS/archive/master.zip 4. in order for our system to run as a hackintosh, some kexts are required.AppleALC = Audio https://github.com/acidanthera/AppleALC/releases/ Lilu - A versatile plugin that is required for both AppleALC and WhateverGreen. https://github.com/acidanthera/Lilu/releases LucyRTL8125Ethernet - Required for the Realtek® RTL8125B 2.5Gbps LAN controller https://github.com/Mieze/LucyRTL8125Ethernet SMCProcessor - Plugin for VirtualSMC - Allows to read CPU relevant data like temperatures etc.Can be found in the table of contents of VirtualSMC.SMCSuperIO - Plugin for VirtualSMC - Allows to read out CPU relevant data like fan speeds etc.Can be found in the table of contents of VirtualSMC.VirtualSMC - Apple SMC emulator including plugins - makes it possible to boot macOS https://github.com/acidanthera/VirtualSMC/releases Whatevergreen - Swiss Army Knife for GPUs, but now also includes many additional fixes https://github.com/acidanthera/WhateverGreen/releases You can download the kexts as a package here: https://www.dropbox.com/s/klfaadmfelwk937/Kext Files - MSI MEG Z490I Unify - Build.zip?dl=0 Additionally you have to download the BASIS-SSDT.aml https://www.dropbox.com/s/x8yn33yyizsnqoa/BASIS-SSDT.aml?dl=0 Installation Plug in your USB Flash Drive and open the boot menu with the F11 key.Select the USB flash drive and confirm the selection with Enter.In the OpenCore Boot Picker, select the recovery stick with the name DSM2RECBS and confirm the selection again with Enter.Once you have arrived in the installer, open the Utilities tab and start the terminal.Then enter ifconfig and confirm the entry with Enter.The terminal lists all available interfaces.lo0gif0stf0xhc20xhc0en0For us en0 is important because this is our lan port, which is currently "inactive" according to ifconfig.With the Realtek 2,5 Gbit Lan Controller it is the case that it can not automatically get the correct settings for the Lan Port.Without the correct settings, no access to the Internet is possible, and without Internet access, no Internet Recovery Install can be performed.However, we can solve the whole problem via terminal.To do so, type the following command into the terminal and confirm the input with Enter:ifconfig en0 media 1000baseT mediaopt full-duplexTo check, enter ifconfig again and confirm with Enter. Now you should see "active" instead of "inactive".Thanks to griven who helped to solve the lan problem via terminal.After that close the terminal and switch to the disk utility.First change the view to "Show all devices" and then select the hard disk you want to use for macOS in the left tab.In my case this is a Samsung 970 EVO Plus with current firmware.(without current firmware on the 970 EVO Plus, it is not possible to install macOS on it)After that click on "Delete", another window will open and here you can define the following things:Name: Can be assigned as desiredFormat: Mac OS Extended (journaled)Scheme: GUID Partition TableClick on "Delete" afterwards.Once the formatting is complete, click "Done" and close the disk utility.Back in the selection menu, select "Reinstall macOS Big Sur".Press "Continue" and accept the terms and conditions.Select the hard disk you formatted for macOS and confirm the selection with "Continue".The remaining part of the installation runs automatically and we only need to intervene again briefly when it is finished.To avoid open questions I have captured the whole installation process in full length. Copy the EFI from the Recovery Install Stick to the ESP of the hard disk Lan Fix - Realtek 8125B As with the installation you have to fix the lan port again.This time the whole thing will stay the same and not only active for the installer.Open the terminal and enter the command already mentioned above, but this time you add a "sudo" to the command.The complete command will be:sudo ifconfig en0 media 1000baseT mediaopt full-duplexPress Enter to confirmYou will then be asked to enter your password for the system,don't be surprised that the password input is not displayed.Confirm with EnterReady Thunderbolt3 The mainboard has a Thunderbolt port, which we have to bend a bit for macOS,because without this adjustment Thunderbolt Hotplug will not work.Thunderbolt is connected via PCH and is connected to the RP01 of the MSI MEG Z490I Unify.In the picture below you can see the Path and the successful Inject of the properties via SSDT.First download the following SSDT: https://www.dropbox.com/s/wxtsmopnbgwq8t8/TTRidge.aml?dl=0 Additionally you need MaciASL: https://www.dropbox.com/s/ku31d8zimw7arvs/MaciASL.zip?dl=0 As well as PlistEdit Pro to edit your config.plist: https://www.dropbox.com/s/bqradkm2pgiklep/PlistEdit Pro.zip?dl=0 Open the TTRidge.aml with MaciASL and change the Device PathFromExternal (_SB_.PCXX.RPXX, DeviceObj)External (_SB_.PCXX.RPXX.PXSX, DeviceObj)Scope (_SB.PCXX.RPXX)ToExternal (_SB_.PCI0.RP01, DeviceObj)External (_SB_.PCI0.RP01.PXSX, DeviceObj)Scope (_SB.PCI0.RP01)Afterwards you compile the file. (Point 1 in the picture)Another window will open which ideally should not contain any errors. (point 2 in the picture)If no errors are displayed, you can now save the file.To do so, click on File (point 3 in the picture) and then on Save as (point 4 in the picture)A wide window will appear, choose the place where you want to save the file.In my case this is the desktop and then click on Save.In the next step you open the terminal and mount your EFI partition.In my case the command is :sudo diskutil mountdisk disk0s1Now copy the TTRidge SSDT saved on your desktop and paste it into your EFI under EFI/OC/ACPI.Load your config.plist with PlistEdit Pro and open the property list ACPI/Add.Click on "New Sibling Element" while you have selected the Add Property.Change the type of the new sibling element from String to Dictionary.You should now have the following picture in front of youNow click 1x on "New Child Element" and then 2x on "New Sibling Element".Now rename the properties added as "New Objects".We also change the property type from String to Boolean and set it from No to Yes.The property names are :Name : Comment - Type : String - Value : TTRidgeName : Enabled - Type: Boolean - Value: YesName: Path - Type: String - Value: TTRidge.amlIn the config.plist it should look like this:If this is the case click on "File" and save the config.plist with "Save". PS: If you use this guide for another Z490 motherboard,which is also equipped with a Thunderbolt port,you have to find out the device address for your Thunderbolt Port via IORegistryExplorer. USB-Ports Under macOS there is a port limit for USB ports, i.e. if more than 15 ports are available, everything beyond this limit will be ignored.USB 3.0 ports are backwards compatible and use two ports at once by definition,i.e. a USB 2.0 part and the actual USB 3.0 part.But not all listed ports under macOS are physically present,just because macOS lists them to us doesn't mean that this is true.With original Apple devices the port definition for each SMBIOS is stored, with a Hackintosh this is of course not the case.Therefore a definition of the USB ports is essential, otherwise certain functions such as sleep cannot work.To create a Custom USB Kext you need Hackintool: https://www.dropbox.com/s/f80m1ef7k5drc0s/Hackintool-3.4.9.zip?dl=0 With this tool you can create your own USB Kext under the tab USB and remove ports that are not assigned (not available).The procedure documented by @CMMChris was great and simple which I quote here:Open Hackintool and switch to the USB tab. There all USB ports are listed.Now test all ports one after the other with a USB 2 and a USB 3 device to see which ones are in use.Then delete the ones that are not in use from the list.After that you set the type of the port:- USB 2.0 part of a USB 3 port is set to USB3- USB 3.0 portion of a USB 3 port is set to USB3- Pure USB 2.0 connections on USB2- Special feature of Type-C: Same port in both directions = TypeC + SW; different port depending on direction = TypeC- Internal USB ports (e.g. internal Bluetooth) is set to InternalIf your connections exceed the port limit of 15 ports per controller, you have to disconnect ports (1 USB3 port = 2 USB ports - USB2 share and USB3 share).Then you have to decide yourself if you want to disable ports completely,remove the USB 2.0 part from a USB 3.0 port or vice versaOnce everything is configured you can export the data.Hackintool generates 5 files: SSDT-EC-USBX.aml, SSDT-EC-USBX.dsl, SSDT-UIAC.aml, SSDT-UIAC.dsl and USBPorts.kext.Usually only two of them are important, SSDT-EC-USBX.aml and USBPorts.kext.In our case only the USBPorts.kext is needed, because I have done some preliminary work in the BASIS-SSDT which is also USB related.Mount your ESP partition of your macOS disk and store the files as follows:- SSDT-EC-USBX.aml should be placed in EFI/OC/ACPI/ (if you use another Z490 board)- The USBPorts.kext should be placed in EFI/OC/Kexts/To edit the config.plist we use PlistEdit Pro: https://www.dropbox.com/s/bqradkm2pgiklep/PlistEdit Pro.zip?dl=0 Open the config.plist via PlistEdit Pro and stores the entries for the two files,so they are loaded at boot time and also disable the XhciPortLimit Quirk.After a reboot the whole things will be taken over and should work fine if you did everything right.The Singularity Computers Wraith Case has no connectors on the case itself,for this reason my USBPorts.kext differs slightly from your definition.HS01, HS03, HS04 are USB 2.0 parts of the USB 3.0 ports.In other words the counterparts of SS01, SS03,SS04. (USB 3.0 Ports)HS07, HS08 are the two pure USB 2.0 ports.HS09 is the USB 2.0 header I forked for the Bluetooth and is stored as Internal.HS13 is the Mystic Light Controller of the mainboard which I also set to Internal,so that it cannot cause a Wake from Sleep.SSP1/SSP2 is the Thunderbolt port and a standalone controller.If your setup is build one on one, you can alternatively use the Custom USB Kext I created here. https://www.dropbox.com/s/nh2qn14upwqix1b/USBPorts.kext.zip?dl=0
    11 points
  45. New theme available for MacPro fan MacPro
    11 points
  46. I just found out about this. Artur_pt was a good friend. He was a good moderator on the forum, and on the chat. Back when InsanelyMac had a chat, from the simple AJAX type chat, moved over to IRC chat. Artur was always there to cheer us up. I must confess, at first I didn't understand his humour, but I later on picked it up. Whenever he encountered people who didn't want to work hard enough to get their machines to run MacOS, he often joked around with the most funniest jokes. Such as putting a MacBook in a computer case, and you'd get a hackintosh out of it. Having people who'd want to get hackintosh service by getting silver spoon fed was annoying, but Artur made it seem funny, the annoyance just left easily after a nice giggle. Artur always wanted people he helped to be more independent with their hackintoshing, to be able to use the forum to their advantage, to be able to research and learn. He would help people, he would give hints to them and he would guide them. Artur_pt was a great example to this community, to people who come here one time for their one and only hackintosh round, to people who come here frequently, and to moderators.
    11 points
  47. Finally I can boot X99 Gaming G1 I just change SSDT-RTC0.aml SSDT-RTC0.aml I check Big Sur AirPortBrcmNIC.kext My wifi card is pci14e4,43b1 I patched via SSDT change device-id & compatible like this. SSDT-RP04-ARPT.aml I update XCPM patches 10.16 /11.0 Beta 10 (20A5395g) X99/X299
    11 points
  48. OpenCore 0.6.2 EFI Update - 10.15.7 & Big Sur Ready, 5th October 2020 (Use With Bios Revision F12d or Newer) The EFIs and DSDTs have now been updated to the my latest versions. Changes made include, AppleALC 1.5.3 Lilu 1.4.8 WhateverGreen 1.4.3 VirtualSMC 1.1.7 AirportBrcmFixup 2.1.0 IntelMausi 1.0.4 OpenCore Updated to Revision 0.6.2 (Big Sur Ready) OpenCanopy is Enabled as Standard Plus other major tweaks and changes to all of the configs OpenCore EFI Update v0.6.2 - 05/10/2020 OpenCore 062 Z390 Pro 19,1 051020.zip - OpenCore v0.6.2, SMBios iMac19,1 OpenCore 062 Z390 Pro 1,1 051020.zip - OpenCore v0.6.2, SMBios iMacPro1,1 (IGPU Disabled) Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments. Note 2 - Do not try to carry across your old OpenCore Config.plist to the new EFI as to many changes have occurred in 0.6.0. Use the new Config.plist instead. For OpenCore Using PlistEdit Pro add your details by modifying the following PLEASE NOTE - These EFIs are setup to be used with your msr Unlocked so make sure you use the F12d Unlocked Profile but if for any reason you can not unlock MSR then just modify following in the OpenCore config.plist :  Additional Downloads PlistEdit Pro.zip - PlistEdit Pro (use to edit OpenCore) Bios Update F12K (F12J Pro Wifi) and Bios Settings (Profile's Coming Soon) mb_bios_z390-aorus-pro_f12k.zip - Aorus Z390 Pro Bios Firmware F112K mb_bios_z390-aorus-pro-wifi_f12j.zip - Aorus Z390 Pro Wifi Bios Firmware F112J PLEASE NOTE - MSR Unlock is now baked into the BIOS as a setting so you no longer need my bios profile to unlock your MSR. BIOS SETTINGS (Bios Revision F12k & F12j Pro Wifi) • Enter BIOS -> Press Delete -> Enter Setup • Save & Exit -> Load Optimized Defaults • Boot -> CFG Lock -> Disabled • Boot -> Windows 8/10 Features -> Win 8/10 WHQL • Boot -> CSM Support -> Disabled (Can be set to Enabled if need be but try to have it set to Disabled first) • Favourites -> Extreme Memory Profile (X.M.P.) -> Profile1 • Favourites -> VT-d -> Disabled (Can be set to Enabled or Disabled, Your choice) • Settings -> IO Ports -> Internal Display Output -> PCIe 1 Slot • Settings -> IO Ports -> Internal Graphics -> Enabled (Disabled If Using SMBios 1,1) • Settings -> IO Ports -> DVMT Pre-Allocated -> 64M • Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M • Settings -> IO Ports -> Aperture Size -> 256MB • Settings -> IO Ports -> Wifi -> Disabled (Z390 Pro Wifi Only) • Settings -> IO Ports -> Audio Controller -> Enabled • Settings -> IO Ports -> Above 4G Decoding -> Enabled • Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Auto • Settings -> IO Ports -> USB Configuration -> XHCI Hands-off -> Enabled • Settings -> Miscellaneous -> Software Guard Extensions (SGX) -> Disabled • Settings -> Platform Power -> Platform Power Management -> Enabled • Settings -> Platform Power -> ErP -> Enabled • Settings -> Platform Power -> RC6(Render Standby) -> Enabled • Save & Exit → Save & Exit Setup F12K BIOS Profile With MSR Unlocked & All The Correct Settings Dialled in for you - The Easy Way  @texem has made this bios profile for you all to use that will unlock CFG on your motherboard making it play alot more friendly with the NVRam. It also has all the bios settings listed on this guide pre done and saved onto the profile.  Z390 PRO BIOS PROFILE - F12k.zip - Use with Z390 PRO Bios Revision F12K ONLY Z390 PRO WIFI BIOS PROFILE - F12J.zip - Use with Z390 PRO WIFI Bios Revision F12J ONLY (Coming Soon) 1 - Download the profile and save it to a USB Key 2 - Go into the bios, 3 - Load the profile, 4 - Save and exit 5 - Go straight back into the bios and save your bios to a new profile and name it Default or something like that. 6 - Save the changes and then restart and your done, your motherboard will now be CFG (MSR) Unlocked and all the correct settings will be dialled in for you. Clover EFI Update Coming Soon (I am holding off from updating the Clover EFI until it is fully Big Sur Compatible and will update the EFI as soon as it is so)
    11 points
×
×
  • Create New...