Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 12/04/2011 in Posts

  1. 23 points
    Shaneee

    AMD Vanilla Kernel

    AMD OS X is proud to announce that native macOS is available on Ryzen CPUs thanks to AlGrey. No need to use a patched kernel/prelinkedkernel. This is currently being classed as beta support and other CPUs are being worked on. https://github.com/AMD-OSX/AMD_Vanilla
  2. 16 points
    Pavo

    AGPM Injector kext generator app!!

    I would like to introduce you to a new app I just go done creating. AGPM Injector, its an app to generate an injector kext for Apple Graphics Power Management for discrete GPUs. AGPMInjector
  3. 16 points
    MinusZwei

    APFS support is coming!

    Hi guys, I was really frustrated when Mojave got released, since the installer did not let us the possibility to control the APFS conversion... ...so I started to google around and found out that: 1. Apple finally released some kind of high-level APFS specification for read-only access (https://developer.apple.com/go/?id=apfs-file-format-spec) 2. An APFS driver for FUSE was already available on github (https://github.com/sgan81/apfs-fuse) Using both, I was able to write a pre-alpha-unstable-whatever APFS driver that is: - able to parse the first non-encrypted volume of an APFS container - supports ASCII path lookup Basically, a driver that is able to boot (at the moment) macOS High Sierra installed inside an AFPS container. I still need to clean my code, but I will publish a patch for Enoch pretty soon.... Stay tuned! M.
  4. 16 points
    Slice

    Clover Change Explanations

    Rev 4540 New driver developed by savvas https://github.com/acidanthera/ApfsSupportPkg/ You may exclude private apfs.efi from drivers64UEFI folder and place here the driver ApfsDriverLoader.efi. It performs loading the driver from APFS container by DiskIO protocol. The driver is open source but located not in Clover repository and at link above. It contains macbuild.tool for those who want to compile by himself.
  5. 15 points
    Slice

    Clover Change Explanations

    Rev 4847-4852 There is interface in Clover GUI to tune startup sound parameters Computer will play a sound before enter Clover GUI. To do this you have to 1. Use CloverX64.efi revision 4852 or up. 2. Place AudioDxe-64.efi into drivers64 and drivers64UEFI. Playing is possible in both legacy and UEFI modes. AudioDxe.efi is included into Clover project and will be differ from original by Goldfish64 but almost compatible. 3. Place sound.wav and may be sound_night.wav into your theme folder, for example /EFI/CLOVER/theme/Clovy/. The sound must be 16bit, and 44100 or 48000Hz. But I also made conversion on the fly so 8000Hz is also supported. 4. Tune sound output in Clover GUI as on screen above. The settings will be stored in NVRAM and used next restart. With legacy Clover or systems without nvram you have to use EmuVariableUefi.efi and rc.scripts to save nvram.plist. For very new systems like Z370 where nvram is not working in macOS there is a chance that the nvram is working on Clover level and so all will works. SIC! Legacy Clover saved Variables only with Apple guid so why it will not work. After some discussing I may rebuild the system to use AppleBootGuid. In this case the system will not be compatible with the original driver but will work with legacy systems. No more needs in BootChimeCfg and BootChimeDxe while the compatibility still remains.
  6. 14 points
    Allan

    [READ] - InsanelyMac Forum Rules

    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 (nothing like bugmenot or similar). 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.
  7. 13 points
    I did it again! With the release of the Navi drivers for macOS by Apple I bought a card and ported my popular PowerPlay Table generators to the RX 5700 and RX 5700 XT. Some might know I already did the same for V56/64 and Radeon VII. This tool allows you to change GPU, SoC and Memory Clocks, voltages for GPU and SoC (for undervolting or overvolting), adjust Power and TDC limits and customizing fan control. The whole thing is based in a simple Excel spreadsheet and provides you with a long Hex string you can then inject to your graphics card via Clover device properties. If you want to use it on a real Mac (eGPU or Mac Pro) you can use a Dummy Kext to inject the PowerPlay Table. Please make sure that you only run this spreadsheet in Excel! iWork, OpenOffice and Libre Office are known to do wrong calculations. Release: AMD Radeon RX 5700 (XT) PowerPlay Table Generator V1.0 (October 27 2019) Changelog 1.0: Initial Release RX 5700 Download: Radeon_RX_5700_PowerPlayTable_Generator.xlsx.zip RX 5700 XT Download: Radeon_RX_5700_XT_PowerPlayTable_Generator.xlsx.zip WARNING: Use this this tool at your own risk! I am not responsible for your mistakes. Wrong / too high values can potentially damage or destroy your card.
  8. 12 points
    Slice

    Clover Change Explanations

    Rev 5052 Implemented a possibility to change injected kext. For example you want to text new version of VoodooPS2.kext while you have another one. Place new kext in folder /EFI/CLOVER/kexts/Off and your old kext in /EFI/CLOVER/kexts/Other as usual. Then go to menu and click disable one and enable another. Screenshots i.e. kexts in the folder Off are disabled by default.
  9. 11 points
    Since apparently there is quite a big demand for it, I am now starting an official topic for my Radeon VII PowerPlay Table generator for macOS. It's a simple Excel spreadsheet where you can change the settings to your desired values. The result is a PowerPlay Table you can inject via Clover on your GPUs PCI path (example below). Recommendation: Set the parameters PP_DisableDIDT=1 (Number) and PP,PP_DisableULV=0 (Number) in addition to your PowerPlay Table. This gives a significant performance boost and reduces power consumption further. The performance boost is especially noticeable in some games. For the DisableULV Parameter you need Whatevergreen since it overwrites an existing parameter. Here is how the PowerPlay Table Generator looks like: It's possible to change GPU Clock, HBM Clock, GPU Voltage, SoC Voltage, Power Limit, TDC Limit for GPU, TDC Limit for SoC as well as the Fan Curve. Something that's not working is ZeroRPM due to driver limitations. Turning those parameters on has no effect. The pre-set values are optimized for the vast majority of cards and use cases (changed Fan curve and UV as well as 1100MHz HBM OC). Please adjust if you have any issues. Warning: I am not responsible for any damaged cards by setting wrong / too high values. If you don't know what you are doing, don't touch it. Enjoy! RadeonVII-PPT-Generator.xlsx.zip
  10. 11 points
    Slice

    Clover v.2 Instructions

    Device Properties This is Apple's protocol since many years to provide information from AppleEFI to macOS about used deviced. It is obligatory and present in all hackintosh bootloaders. The information can be provided also by _DSM methods since OSX 10.5. But ACPI method will work after kernel started and after AppleACPIPlatform started and so may depend on its version. DPProtocol works before kernel and inject properties at boot.efi time. Historically Clover has several methods to fill the database of Device Properties. 1. There is just hex-string injection that can be manually constructed by gfx-util. Not convenience. 2. There are automatic injections or Graphics card, LAN, Sound and USB devices. It is very convenient but very questionable by final results. There are many properties that should be injected or no and we are not sure what values must be injected versus Clover choice. 3. To resolve these question two setting added "NoDefaultProperties" and "AddProperties". This way smart people can cancel all automatically injected properties and inject own properties. This way is not very good as devices chosen by nickname "ATI", "Nvidia", "LAN" etc. which not assumed present of two different videocard, for example, or similar videocards but required different properties. 4. More advanced way is "Arbitrary" properties when you can inject all properties you want for a device chosen by its PCI address. The address of the device is set as 08:00:00. But this is the fault of the method. The bus number (08 in this example) may changed with BIOS changed or with new device inserted. As well this is hard to set device address of device at second bridge (bridge after bridge). 5. More correct way is introduced in Clover since 4497 revision. This is XML dictionary as it created by gfx-util. Example <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x14,0x0)</key> <dict> <key>AAPL,clock-id</key> <data>AA==</data> <key>AAPL,current-available</key> <data>sAQ=</data> <key>AAPL,current-extra</key> <data>vAI=</data> <key>AAPL,current-in-sleep</key> <data>6AM=</data> <key>built-in</key> <data>AA==</data> <key>device_type</key> <string>XHCI</string> </dict> <key>PciRoot(0x0)/Pci(0x19,0x0)</key> <dict> <key>built-in</key> <data>AQ==</data> </dict> Compared to old and buggy gfxutil Clover also accepted <integer> and </true> </false> types of values. As well you may see <data> array when you know there is <string>. This method allows you to use properties found in DarwinDumps of real Macs just by copy/paste into your config.plist How to convert your old config.plist to new method of injection? 1. Boot macOS with your old Clover and old config.plist. Assumed there is full success. 2. Use clover-genconfig utility (rev >4508) to produce config-imprint.plist with all properties you previously use by methods 1-4. $ clover-genconfig > config-imprint.plist 3. Use any editor to copy data from imprint to you working config.plist to make your new config.plist. You have to find Device->Properties dictionary and make a full copy of it. 4. Then you should switch off any other injection by methods 1-4. Graphics->Inject->ATI,NVIDIA,Intel=NO Devices->USB->Inject=NO Devices->LANInjection=NO Devices->HDAInjection=NO Devices->HDMIInjection=NO AddProperties -> #AddProperties Arbitrary -> #Arbitrary 5. Install Clover 4497 or up. 6. You may also add new properties to this array by the given sample. 7. Reboot. 8 During reboot you can enter Options menu -> PCI Devices -> Custom and see all properties you may inject. This is good time to enable or disable some of the properties. To temporary disable a property in the config place # sign at the start of the key <key>#AAPL,clock-id</key> To write a comment to the device you may insert pair <key>#Comment</key> <string>This is XHCI device</string> There is one special case "ig-platform-id". To have an ability to change a value of the property Clover gives you an additional setting <key>Graphics</key> <dict> <key>ig-platform-id</key> <string>0x01660003</string> This value will be present in Options menu -> Graphics and changeable here. New value will replace the value from the Properties dictionary. EDITED Clover-genconfig must be exactly same revision as clover which boot the system. So instructions updated 1. Boot macOS with your old Clover and old config.plist. Assumed there is full success. -> 1. Install new Clover and boot with old config.plist
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×