Jump to content

Maf3r0

Members
  • Content Count

    81
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Maf3r0 reacted to Slice in [pre-release] macOS Big Sur in VMWare   
    Is there anybody can make a dump of failed installation process with this driver?
    And yes, I want to see an attempt with latest Clover.
    DumpUefiCalls.efi.zip
  2. Like
    Maf3r0 got a reaction from Allan in Windows OpenCore Issue!!   
    If u r using 0.5.8 all u have to do is change
     
    PlatformInfo/UpdateSMBIOSMode from Create to Custom
     
    and set
     
    Kernel/Quirks/CustomSMBIOSGuid = YES
  3. Like
    Maf3r0 reacted to Shaneee in macOS Catalina 10.15.5 released!!!   
    All updated just fine on AMD. 

  4. Like
    Maf3r0 reacted to fantomas in macOS Catalina 10.15.5 released!!!   
    macOS Catalina 10.15.5
     
    macOS Catalina 10.15.5 introduces battery health management in the Energy Saver settings for notebooks, a new option to disable automatic prominence in Group FaceTime calls, and controls to fine-tune the built-in calibration of your Pro Display XDR. The update also improves the stability, reliability, and security of your Mac. 
     
    Battery Health Management
    Battery health management to help maximize battery lifespan for Mac notebooks Energy Saver preference pane now displays battery condition and recommends if the battery needs to be serviced Option to disable battery health management For more information, please visit https://support.apple.com/kb/HT211094
     
    FaceTime Prominence Preference 
    New option to control automatic prominence on Group FaceTime calls, so video tiles do not change size when a participant speaks  
    Calibration Fine-Tuning for Pro Display XDR
    Controls to fine-tune the built-in calibration of your Pro Display XDR by adjusting the white point and luminance for a precise match to your own display-calibration target  
    This update also includes bug fixes and other improvements:
    Fixes an issue that may prevent Reminders from sending notifications for recurring reminders Addresses an issue that may prevent password entry on the login screen Fixes an issue where System Preferences would continue to show a notification badge even after installing an update Resolves an issue where the built-in camera may not be detected when trying to use it after using a video conferencing app Addresses an issue for Mac computers with the Apple T2 Security Chip where internal speakers may not appear as a sound output device in Sound preferences Fixes a stability issue with uploading and downloading media files from iCloud Photo Library while your Mac is asleep Resolves a stability issue when transferring large amounts of data to RAID volumes Fixes an issue where the Reduced Motion Accessibility preference did not reduce the speed of animations in a Group FaceTime call  
    Enterprise content:
    Improves performance on certain Mac models when enabling hardware acceleration in GPU-intensive apps such as those used for video conferencing Addresses an issue where Microsoft Exchange accounts were unable to sign in during account setup when using Conditional Access Apple Push Notification Service traffic now uses a web proxy when specified in a PAC file via the Proxies payload Resolves an issue that prevented some displays connected to MacBook Pro (16-inch, 2019) from waking from sleep when the Mac wakes Major new releases of macOS are no longer hidden when using the softwareupdate(8) command with the  --ignore flag This change also affects macOS Mojave and macOS High Sierra after installing Security Update 2020-003.
     
    macOS Catalina 10.15.5 (19F96)
     
    Update
    Combo
     
    View full article
     
  5. Like
    Maf3r0 reacted to MacNB in OpenCore Discussion   
    Yes it does seem strange that CMD+V actually works WITHIN OpenCanopy even though it's a hotkey.
     
    The problem is terminology. CTRL+ENTER is NOT technically a HOT KEY.
    According to the Configuration PDF, hot keys are:
     
    This list of known modifier hotkeys includes:
    • CMD+C+MINUS — disable board compatibility checking.
    • CMD+K — boot release kernel, similar to kcsuffix=release.
    • CMD+S — single user mode.
    • CMD+S+MINUS — disable KASLR slide, requires disabled SIP.
    • CMD+V — verbose mode.
    • Shift — safe mode.
     
    So let's not refer to CTRL+ENTER as a hot key as it may confuse the devs.
    Call CTRL+ENTER as a boot picker ACTION Key.
  6. Thanks
    Maf3r0 reacted to MacNB in OpenCore Discussion   
    I don't think there's a requirement for CTRL+ENTER OUTSIDE of picker BUT while in the picker, it makes sense.
    OpenCanopy currently detects RIGHT arrow key, LEFT arrow key and the SPACEBAR key (may be other keys in the future to turn ON/OFF audio picker).
    It would be nice for it detect CTRL+ENTER to select the default boot drive. 
  7. Thanks
    Maf3r0 reacted to Download-Fritz in OpenCore Discussion   
    @Maf3r0 Hotkey support is two stages - OC and picker. OC is shared and polls before showing picker (this is what works when using Canopy, because it happens before Canopy), Picker polling is implemented while it is shown (i.e. not here, because Canopy does not implement it).
  8. Thanks
    Maf3r0 reacted to Andrey1970 in OpenCore Discussion   
    Hot keys not implemented in OpenCanopy.
  9. Like
    Maf3r0 reacted to Hervé in [Release] macOS 10.15.4 is out!   
    Please STOP posting the same thing repeatedly. We all got it. Again, this is normal with 10.15.4; there is no problem. If you don't want to see that, don't boot in verbose mode. End of story.
     
    If your English is bad, use Google Translate.
  10. Like
    Maf3r0 reacted to CMMChris in [Pre-Release] macOS Catalina 10.15.5   
    Run
    sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll CustomerSeed then run
    sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil fixup Now reboot. Then try switching to the Developer Seed again
    sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll DeveloperSeed  
  11. Thanks
    Maf3r0 reacted to ghost8282 in OpenCore Discussion   
    Issue solved, thanks to vit9696, here is his reply, I think it can help some other people:
    https://github.com/acidanthera/bugtracker/issues/864
     
    So I simply changed the address in the config.plist (Audio section) from PciRoot(0x1)/Pci(0x2,0x0)  ---> which was the address reported by gfxutil, to PciRoot(0x0)/Pci(0x2,0x0) ---> which is the address seen by opencore, and now chime works good.
  12. Thanks
    Maf3r0 reacted to CMMChris in [KEXT] Tired of low Geekbench scores? Use RadeonBoost!   
    Hello everyone!
     
    Together with the help of @DSM2 I built a Kext aiming at removing limitations put in place by Apple for PC graphics cards that reduce performance in some benchmarks like Geekbench and some scenarios where memory bandwidth is crucial.
     
    Likely most of you already know the issue that some GPUs don't perform as expected in Geekbench. For example, a Radeon VII only scores around 50k to 60k points while on Windows it can easily reach the 82k range - with overclocking even more. This issue is not only affecting the Radeon VII but numerous other graphics cards as well.
    This problem started back when macOS 10.14.5 Mojave was released, introducing the fix for fan control on Vega 56 / 64 cards.
     
    As it turns out, Apple never fixed the fan issues but instead put a dirty workaround in place. Modern AMD GPUs utilize a so-called SMU firmware to manage some of the cards functions. This SMU firmware needs to be uploaded by the graphics driver. It looks like the Vega 56 / 64 fan control bug was caused by a faulty SMU firmware implementation by Apple. Instead of fixing it, all they did was to disable loading of SMU firmware on PC graphics cards. This can be verified by force loading the SMU firmware again on Vega 56 / 64 cards. The fan control bug will then be back. Not loading SMU firmware causes a number of issues and one of them is memory bandwidth being cut in half. Since Geekbench is very sensitive to memory bandwidth, this is what causes the low scores.
     
    So essentially, Apple scammed their customers here, putting a dirty fix in place that now affects a large amount of graphics cards. And of course this not only affects hackintosh users but also Mac Pro users or eGPU users, utilizing PC graphics cards on their Mac.
     
    Now this is where my RadeonBoost Kext comes in. It makes sure that SMU firmware is loaded again, removing the memory bandwidth limitations, making sure the GPU can be used to its fullest potential. The results really speak for themselves.
     
    Demo of the result:
     
    RadeonBoost.kext has been built with Hackintosh users in mind, but of course it does work on a real Mac as well. That includes both Mac Pros as well as Macs with an eGPU. You can either inject the kext via OpenCore or put it into /Library/Extensions, repair permissions and rebuild kext cache. Putting it inside /L/E of course requires SIP (System Integrity Protection) to be disabled since the Kext is not signed.
     
    Of course you can go ahead and edit the info.plist of RadeonBoost.kext to your likings. For example you can add your own properties. This comes handy if you want to additionally overclock or undervolt your GPU by using a PowerPlay Table, which of course can be added to the Kext as well. On a Hackintosh you of course can keep injecting them through the bootloader without having to edit the kext.
     
    List of supported GPUs:
    RX480, RX580, RX590 (!!! USE ALONG WHATEVERGREEN !!!) Radeon VII, RX 5500, RX 5500 XT, RX 5600, RX 5700, RX 5700 XT (WHATEVERGREEN NOT NECESSARY)  
    Download & Changelog
    May 28 2020: V1.6 - Disabled SMU Firmware Loading for Navi10/14 due to broken SMU firmware starting from macOS 10.15.5, improved Polaris compatibility April 24 2020: V1.4 - Added target SMBIOSes for AGPM injector to prevent overriding of stock AGPM configuration on SMBIOSes that don't need an AGPM injector (e.g. iMac19,1 etc) April 20 2020: V1.3 Replaced "ATY,EFIVersion" with "ForceLoadFalconSmuFirmware" (thanks to Whatevergreen developers for discovery of this parameter), changed Polaris properties (RX480, 580, 590 users please re-test), removed Apple framebuffer properties (performance difference is minor) April 19 2020: V1.2 Removed support for Vega 56, Vega 64 and Vega Frontier (REASON) April 19 2020: V1.1 Removed unnecessary device properties, added embedded AGPM injector for SMBIOSes where it makes sense (iMacPro1,1; MacPro7,1; MacPro5,1; MacPro4,1) April 17 2020: V1.0 Initial Public Release  
    For download of RadeonBoost.kext please check this posts attachements.
    Enjoy!
     
    RadeonBoost.kext.zip
  13. Like
    Maf3r0 got a reaction from Allan in macOS + Win dual boot (at same disk) with OpenCore   
    This is not intend to be a guide at all, but instead, is just what I did to get dual boot with OpenCore. Pls, feel free to advise if there's any wrong, I'll be much thankful.
     
    -- PREREQUISITES --
     
    (1) HD/SSD free to formatting
     
    (2) Windows UEFI installer
     
    (3) Working NVRAM (native or emulated) and also available to be cleaned
     
    (4) Firmware UUID:
         – Original hardware UUID. Necessary to avoid Windows activation problems
         – To get this, type: wmic CsProduct Get UUID at Windows Command Prompt
         – The result will look like 00000000-1111-2222-3333-444444444444
     
    (5) OpenCore's config.plist edits:
         – At Misc/BlessOverride add following String: \EFI\Microsoft\Boot\bootmgfw.efi
         – At Misc/Boot, set HideSelf=NO and PollAppleHotKeys=YES
         – At Misc/Security, set AllowNvramReset=YES. This allow's OC to reset NVRAM
         – At Misc/Security, set AllowSetDefault=YES. This allow's OC set default boot option
         – At PlatformInfo/Generic, replace SystemUUID from SMBIOS with Firmware UUID
         – At UEFI/Drivers, add entry OpenUsbKbDxe.efi and add related file (found in OC's release) in folder EFI/OC/Drivers
     
    (6) BootCamp software for Windows:
         – See Additional Boot Camp Notes, please
         – At macOS, insert a flash drive
            ** THIS UNIT WILL BE FORMATTED AND ALL DATA WILL BE LOST **
         – Open Disk Utility
         – From the menu bar, select View/Show All Devices
         – Select flash drive and format it as MS-DOS (FAT32), with Main Boot Record (MBR) scheme
         – After that, run Boot Camp Assistant (in Applications)
         – From the menu bar, select Action/Download Support Software for Windows, select flash drive as destination and wait for the entire process finish (it may take a while)
         – TIP: I have a single 16GB usb with OpenCore, Windows installer and also Boot Camp software, so I can choose what start when I need. That save time when I'm looking pendrivers during installation process! That save time when I'm looking pendrivers during installation process!

    -- INSTALATION --
     
    (1) Through OpenCore USB stick, boot into macOS installer.
         – This is first time I've clean nvram
     
    (2) Format entire disk as HFS+ with GUID scheme (REMEMBER: ALL DATA WILL BE LOST)
         – Add two partitions, one for each system
         – Format macOS's volume as APFS
         – OPTIONAL: Format Windows's volume as ExFAT
     
    (3) Start macOS installation
        – At the end of 2nd stage, we can go to Windows
     
    (4) Through Windows usb, boot installer
         – Remove ExFat volume to create Windows's default partition
         – An aditional partition, only 16MB – MSR (Reserved) – will be created automatically
         – Start Windows installation
     
    (5) Once Windows's full installation is finished, is time to back to macOS using OC usb
         – Finish macOS installation
         – Mount EFI partition
         – Delete "Boot" folder and rename "Microsoft" folder (eg: Microsoft-bak)
         – Add OpenCore folders: BOOT + OC
     
    (6) Restart system and remove all/any pendrive
         – Press BIOS boot key (F12 on Gigabyte) to check available boot options
         – Probably there's two options: Windows Boot Manager and UEFI OS (HD). The first one boot, of course, only Windows and the second one boot OpenCore
         – At this point I've cleaned NVRAM once more, first to remove "ghost" Windows Boot Manager option and second to make UEFI OS (HD) the default boot option
     
    (7) Back into macOS (now through DISK)
         – Restore renamed Microsoft's folder from EFI disk partition
     
    (8) Restart system and let it boot automatically into OpenCore GUI
         – At this point, Windows's partition is available to boot
     
    (9) Start Windows through OpenCore
         – Connect flash drive with Boot Camp installer
         – From WindowsSupport\BootCamp, run Setup.exe
         – Authorize instalation, click "Next", accept license terms and then click "Install"
         – After succesfull instalation, system will restart automatically and when back to Windows, Boot Camp icon will be at Task Bar (next to clock)
     
    (10) How Boot Camp works?
         – It allows quick switching between macOS and Windows.
         – When a system is chosen to boot from Boot Camp, that information is saved to NVRAM and this becomes the default boot option. Eg .: If, at Windows, I select "Restart on macOS…", every time I turn on PC, or macOS will already be selected at OC GUI, or will start automatically and same happens when Windows is selected at macOS's Preferences/Startup Disk.
         – To make Boot Camp more dynamic, additional configuration in cofig.plist is required: or Misc/Boot/Timeout=5 or Misc/Boot/HidePicker=YES. In the first one a countdown will start and in the second one, OC GUI will not appear and selected system will start automatically. But still possible to choose manually a different system to boot, just hold down "Alt" key (or Windows key) until OpenCore GUI appears, hit Enter to boot only this time into desired system or CTRL+Enter to save this option as defult partition.
     
    (11) Additional Boot Camp Notes
         – The only big advantage of Boot Camp is the quick switching between systems, much like switching users. What means that, even w/o Boot Camp, still possible to choose which system to start from OpenCore GUI
         – HFS+ or APFS disks probably will not be accessible in Windows until a third party program is used
         – There's, at least, two cases in that Boot Camp fails to install: (1) If Windows is booted without OpenCore and (2) if Boot Camp's installer folder was renamed.
     
    (12) Credits: All credits goes to OpenCore developers, big thanks to all!
  14. Thanks
    Maf3r0 reacted to Slice in Block injected kexts using config.plist   
    Currently Clover has no such feature. Someone may implement this.
  15. Like
    Maf3r0 got a reaction from newskillter in [pre-release] macOS Catalina   
    seems that quicklook "bug" was fixed in Catalina -- at least worked here with no additional configuration
  16. Like
    Maf3r0 reacted to superxgz in A simple OpenCore config.plist online editing tool   
    Hello, everyone, I made a simple online edit openCore config.plist tool
    Use the address https://galada.gitee.io/opencoreconfiguratoronline
    Support for OpenCore-0.5.3-RELEASE
     
    How to use:
    1 Back up your config.plist
    2 Open the https://galada.gitee.io/opencoreconfiguratoronline with Chrome, Safari, Firefox or Opera
    3 points in the upper right corner of the Open button select your config.plist file, or you can create your config.plist directly from scratch without opening any files
    4 Double-click on the row in the table for data modification, after the modification is completed press enter key to submit the modification, other input box direct modification can be, the lower right corner of the table can be copied, pasted, add edgy, add row, delete the row operation
    5 point Down button download the modified file, then copy to eFI to cover the original file, or click the Copy button, copy the content spally to the clipboard, open the config.plist file under EFI with a text editor, and paste it in to save

     
    If you find a bug, please tell me, follow or send my mailbox 295799583@qq.com, thank you
  17. Like
    Maf3r0 got a reaction from nmano in OpenCore Discussion   
    Despite tip from @ken394 (thanks) I'm still completely lost about emulated nvram I've read many stuff but is so controversial. If anybody successfully got nvram emulated, please take a look (thanks too) at this configurations that, according to this, are supposed to be set:
     
    EFI Driver: FwRuntimeService.efi
     
    Booter/Quirks:
    • AvoidRuntimeDefrag: YES,
    • DisableVariableWrite: YES -- and -- NO (those two options was described)
    • EnableWriteUnprotector: YES
     
    Note: With DisableVariableWrite as NO I get KP at shutdown/restart.
     
    Misc/Security: ExposeSensitiveData: 3
     
    NVRAM: LegacyEnable: YES
     
    and finally:
     
    Generate nvram.plist: Run at Terminal: sudo defaults write com.apple.loginwindow LogoutHook /path/to/LogoutHook.command… According to this guide "This will create a new folder, which dumps the basic output. And you'll find a plist file named nvram.plist. Place this in the root of your EFI Folder" — but I cannot find this folder… in fact, I don't know even if that was created.
     
  18. Thanks
    Maf3r0 reacted to ken394 in OpenCore Discussion   
    https://github.com/InsanelyHack/Emulated-NVRAM
  19. Like
    Maf3r0 reacted to fantomas in OSX86.net taken down?   
    The site is back again! 
     
    --Edit--
     
    But no sign from any major staff members. I guess someone revived it for trafic purposes only.
    Really sad how the story of that site just ended. 
    The site deserves a lot more respect than that, IMHO.
  20. Thanks
    Maf3r0 reacted to Hervé in macOS Catalina 10.15.1 est disponible   
    Version 19B88:

     
  21. Sad
    Maf3r0 reacted to RePete222 in OSX86.net taken down?   
    Does anyone here know the scoop on the osx86.net site?  It's been taking me to a "Community Not Found" page since this past weekend.  Can someone with direct connections to that site's mods reach out and inquire about the status?
     
    Thanks.
  22. Like
    Maf3r0 reacted to Allan in OSX86.net taken down?   
    I'm a osx86.net member, but I don't know what happened.
     
    Maybe it's a Forum upgrade...don't have idea, but unfortunately I was not much active there...
  23. Like
    Maf3r0 reacted to Hervé in OSX86.net taken down?   
    It's no longer a very active forum, full stop. Not been for a long time now. Used to be an excellent place as a repository for kexts/apps/tools though.
  24. Like
    Maf3r0 got a reaction from Allan in Is there a way to restore "Add ClockID" functionality?   
    Well @Hervé, after read your post I stayed so disappointed…
     
    First: The options that I found related to Power and Keyboard/Mouse was already disabled in BIOS:
     

     
    Second: Appears that ClockID still not funcional like before El Cap (not Yose like I said, sorry) and requires more workarounds to be funcional.
     
    and Third: After read Allan's topic I see that Hibernate, on desks, is more hard than deep sleep…
     
    But I'll try atempting to get one or another to working and I'll share.
     
    At now, I can get deep sleep by remove _PRW methods on a patched DSDT, but I feel that mouse freezes randomly with this and I prefer do not use DSDT, once I cannot guarantee that DSDT was correctly patched.
     
    Would be helpful if Clover can drop OEM_PRW like do to OEM_DSM, so I think this might solve my situation.
     
    Anyway, thanks @Hervé for your attention and @Allan also.
     
    Regards!
  25. Thanks
    Maf3r0 reacted to Hervé in Is there a way to restore "Add ClockID" functionality?   
    USB Wake (mouse, keyboard) is often a BIOS option, even on desktops... Did you check that out? If it's available in your BIOS Power Management settings, disable it and you should only be able to wake your computer through the PWR button.
     
    The Clover option still injects the clock-id ACPI property under each USB device (EHCx, EH0x, UHCx, ...), I've verified this on my old Vostro200 desktop. In case it did not in your case (but there's no reason to think so), each entry would require it's own unique clock-id number and you can start at 0 (0x00). It would look like this:
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method                 {                     If (LEqual (Arg2, Zero))                     {                         Return (Buffer (One)                         {                              0x03                                                                    })                     }                     Return (Package (0x0B)                     {                         "AAPL,clock-id",                          Buffer (One)                         {                              0x--                                                                   },                          "AAPL,current-available", 0x----,                          "AAPL,current-extra", 0x----,                          "AAPL,current-in-sleep", 0x----,                          "AAPL,device-internal", 0x--,                          Buffer (One)                         {                              0x00                                                                    }                     })                 }
    But, given the significant USB re-engineering that took place with El Capitan 10.11, this clock-id property injection may not work like it did any more. I've just tried it on my Vostro200 desktop and it's a no-no. Pressing a key or clicking the mouse to wake the computer (as configured in BIOS) still works... Then again, it always did, even when I use to run older versions os OS X (SL, Lion, ML, Mavericks) with Chameleon bootloader and my patched DSDT contained the clock-id injections.
     
    I'm also a little doubtful about the stated usage of this parameters, i.e. "Deep Sleep which cannot be exited by keyboard or mouse input". If you look at the available literature, "AAPL,clock-id" property was required to ensure a USB hub/device would "survive sleep" or to avoid instant wake on entering sleep. 
     
    I believe your best shot is with your BIOS parameters.
     
     Failing that, maybe you can try and turn to hibernation rather than sleep.
     
×