Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 08/16/2021 in Posts

  1. 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
  2. Beta 6 (21A5506j) InstallAssistant.pkg http://swcdn.apple.com/content/downloads/41/36/071-90564-A_7W7WHLSY3Z/fx095l2r9n27ykzxmviuycydg88h86fjv7/InstallAssistant.pkg
    10 points
  3. First monday = exciting day! 😁 Already get OC 0.7.3 running veery smooth here! Thank you devs 👏👏
    9 points
  4. For anybody that’s not seeing the beta6 update using smbios 1,1 or 7,1 and probably anything else, What you need todo is go into the Config.plist and set the SecureBootModel to j160 restart and the update will show up and then disable the SecureBootModel while it’s downloading and let the system do its thing. This is the only method that seems to work so far.
    8 points
  5. Shaneee's ASUS ROG Strix X570-F GAMING - OpenCore 0.7.3 EFI For macOS Big Sur 11.x and macOS Monterey 12.x System Specs: CPU: AMD Ryzen 5 5600X Motherboard: ASUS ROG Strix X570-F Gaming RAM: Corsair Vengeance LED 2x8GB 3200MHz Graphics: XFX RX 480 8GB Case: Corsair iCUE 220T Airflow NVMe: 1TB Corsair MP400 - 500GB Samsung 960 EVO SSD: 250GB Crucial MX500 HDD: WD 640GB (Shared Storage) - WD 500GB (Games) PSU: Corsair RM750x WiFi / BT: BCM94360CS2 + Adapter Cooling: NZXT Kraken X53 Operating Systems:
    8 points
  6. As always, please read the message by @vit9696 , the best place to learn about the changes received by OpenCore. During the month of August, OpenCore Team has taken a break compared to other months but, despite this, more than 25 compilations have been launched making improvements in OpenCore, OpenCanopy and Drivers. The main changes (but not the only ones) are: Linux support to be natively displayed in the OpenCore boot pickers Updated MacPro7,1 database with new AMD graphic cards Improved laptop backlight (SSDT-PNLF compatibility with CFL+ graphics) Fixed
    7 points
  7. Fool-proof guide: Every time a new OpenCore version is released: Download the RELEASE tag from their GitHub repo Read the Dortania post that accompanies the release because if there are any changes that need super attention it will be stated there as well. Keep a backup of your current EFI on a USB Stick's EFI partition so you can boot if things go south. Copy EFI/BOOT/BOOTx64.efi from the downloaded zip to your EFI/BOOT folder. Copy EFI/OC/OpenCore.efi from the downloaded zip to your EFI/OC folder. Copy the drivers you are using on your EFI/OC/
    7 points
  8. Pleasant awakening this morning everything ok here too😀 https://www.insanelymac.com/forum/topic/348778-problems-with-latest-opencore-073-build/?do=findComment&comment=2765709
    7 points
  9. Please always use ocvalidate before posting reports. Don't rely on other junk tools, ocvalidate uses the exact scheme engine from OC + extra sanity-checking, and it is automatically up-to-date with updates.
    7 points
  10. @panosru 12.0 will not be the last version of MacOS with Intel support by a country mile. You have at least 4 or 5 more years of OS support before they do something like that or you would find a lot of Intel Mac users in the court rooms suing over there Intel Mac that they bought in 2021. As much as Apple would love to do it they simply can’t…lol…Hackintosh is safe for a fair few years yet.
    6 points
  11. For anyone upgrading to 0.7.3: Make sure to check your config.plist file against the "ocvalidate" utility... The validation errors might be not that clear but the most important thing is that your UEFI>Drivers should follow the "Dictionary" format instead of "String". Check the sample configuration there and update your files accordantly. Don't be like me, always read the changelog messages
    6 points
  12. Compare your plist with the Sample.plist inside the release the driver structure has changed from this 0.7.2 to this 0.7.3 Each driver has now 3 properties: Arguments, Enabled and Path (Also added ForceOcWriteFlash in UEFI -> Quirks) Otherwise the drivers are not loaded (see ocvalidate) Penalty text menu without GUI and the system will not boot Attention doing ocsnapshot with ProperTree could undo the changes made, double check with ocvalidate and edit manually with Plistedit pro
    6 points
  13. I just updated 2 machines to OpenCore 073 Commit 09930f3 After that, BootPicker GUI no longer worked and both machines didn't boot. So there's either an issue with the built or something drastically changed over night. Seems to be related to OpenRuntime.efi. EDIT: I compared the config against the sample and noticed UEFI > Drivers has a different form now: After adding these entries, everything is back to normal.
    6 points
  14. Clover 5138. Nothing to change
    6 points
  15. https://github.com/dortania/bugtracker/issues/192 You could try messing with the APFSTrimTimeout to see if it shortens or lengthens boot time.
    6 points
  16. 👉 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. Re
    6 points
  17. I see and thank you for the info!! Unfortunately I’d like to make it work on OC 😕 Slice provided a perfect solution. The problem for you is that OC does not yet allow sufficient configurability of SMBIOS. Since you have access to the OC developers on this forum, you might suggest a future improvement by adding Board ID to the PlatformInfo/Generic section of the config.plist. In the meantime, I have both Clover and OC in my EFI and use the boot selector that can be installed to BOOT in EFI to allow me to switch between Clover and OC at will. (The boot selector can be instal
    5 points
  18. @tonyx86 Not sure, the XML stack is entirely @vit9696's work. At the moment we have more urgent issues, like the continuous breaking of Apple Secure Boot, sorry.
    5 points
  19. Sorry, I will upload ccpv in each Release.
    5 points
  20. If it can be useful to anyone CloverConfigPlistValidator_r5139.zip
    5 points
  21. Another good example of ALWAYS using OCVALIDATE BEFORE switching to a new version of OC.
    5 points
  22. I managed to get beta 6 show up with CLOVER. This is what I did: 1) updated CLOVER from 5138 to 5139 (no effect) 2) switched from VirtualSMC to FakeSMC with SMCHelper.efi (no effect) 3) changed SMBIOS from iMacPro1,1 to iMac17,1 and deleted NVRAM (update shows up) Hope this helps!
    5 points
  23. Well, that was not the point. The point was that in Monterey, a Windows Disk is detected as an external Drive and therefore is displayed alongside USB Sticks and external drives connected via USB cable – even if the option to have internal drives displayed on desktop is turned off…
    5 points
  24. I solve my Windows 11 SSD showing as external disk by installing a trial version of iBoysoft NTFS for Mac. After installing the Windows 11 disappeared. It works for me and there is no harm in trying.
    5 points
  25. The beta 6 build is available in ANYmacOS now:
    5 points
  26. 5 points
  27. All is OK. Don't bother.
    5 points
  28. v0.9.6 comes with a bunch of fairly important bug fixes and enhancements. Downloads are available at the release page. In short, the driver is pretty stable now. USB-based card readers should be working properly, while PCIe-based ones should work even better than before. Please refer to the changelog for a list of changes since the previous 0.9.5 release. I would like to acknowledge the following members, @b0ltun, @Sherlocks, @whatnameisit, and @gnpaone, for testing early, unstable builds and reporting issues for USB-based card readers. This release
    5 points
  29. HP NC360T Intel PRO/1000 PT LP Gigabit Dual Port = Intel 82571EB work OTB from Mavericks to Monterey no issue no kext just relax eBay
    5 points
  30. I share my EFI with you, it works perfecly for MacOs Monterey BETA6. It's based on the (wonderful) Audiogod's one, and I added support for internal bluetooth (partially working, many devices aren't recognized, but Apple devices like Keyboard and mouse work perfectly) Follow Audiogod topic for Bios configuration : Simply, during Monterey installation, put "Other OS" in bios boot option. In your config.plist, verify that it's "x86legacy" for the "securebootmodel" option (it is done in my EFI). And everything else works like magic. If you have a
    4 points
  31. Nice find. I use the macOS Calculator app in Programmer mode for Field that has bit setting (like the ScanPolicy). Basically, open the OC Configuration.pdf and go to the section you are interested in changing. Open Calculator App Change View to "Programmer" (CMD+3) Then click each Bit you wish to set the Calculator will show you the new Hex value. Copy and Paste that hex value into the plist editor. If the editor cannot handle hex value, you can convert the hex to decimal in the Calculator App by simply clicking on 10 button before copy-n-paste.
    4 points
  32. Okay, thanks. Will check later what the name is. BTW, I created an issue for the Online ScanPolicy Generator and the guy fixed it already: https://oc-scanpolicy.vercel.app/
    4 points
  33. Hi @Benjamin Franklin This is the new way for 0.73+: <key>Drivers</key> <array> <dict> <key>Path</key> <string>OpenHfsPlus.efi</string> <key>Enabled</key> <true/> <key>Arguments</key> <string></string> </dict> <dict> <key>Path</key> <string>OpenRuntime.efi</string> <key>Enabled</key> <true/> <key>Arguments</key> <string></string> </dict> <dict>
    4 points
  34. @Muaitai using a third party Config Checker will most often give false positives as these will inevitably be late in updating to the latest version, you should always use the ocvalidate app within the updated OC version folder. This will insure all is well with the config.plist and settings.
    4 points
  35. Theme macOS add to the repos You can rename Logo blank.png to Logo.png if you want complete Black backround without Logo macOS.zip
    4 points
  36. 4 points
  37. AudioGod maybe absent doing other things but the Thread is still alive and well for members with queries. Big thanks to @ntuneddu and @WizeMan nice one Guys, much appreciated I am sure.
    4 points
  38. I have explained that this is not easily possible. Let me know when instead of CAPS you provide a PULL REQUEST to improve the tool.
    4 points
  39. I had to download the full installer to get beta 6 and that was before clover 5139 but clover 5139 is working great on both Intel and AMD with beta 6 on both machines. Sent from my iPhone using Tapatalk
    4 points
  40. And also Clover in the last vers. 5139 is fixed 🙂
    4 points
  41. And I'm back and renamed my Windows 11 with a . before windows and ... pufff the disk icon on my desktop is gone... Thanks @antuneddu, @Alex HQuest, that was the first to suggest renaming Windows with a dot before...
    4 points
  42. 🙂 It was enough to put a dot . in front of the name of the disk example .Windows11 is not shown on the desktop but is accessible from the Finder without installing anything
    4 points
  43. As far as I understand the Update is proposed for some mac models: iMac17,1, iMac19,1, iMacPro1,1, MacPro7,1. And I am not sure about other models. Then you should have correct other SMBIOS, SMC, NVRAM settings which is default for Clover. Voila! I changed nothing to get the update.
    4 points
  44. Well solved this too thanks to @AudioGod Her the values that can be set as SecureBootModel https://dortania.github.io/OpenCore-Post-Install/universal/security/applesecureboot.html#securebootmodel
    4 points
  45. Word of warning, if you're using j137 and 1,1 that won’t work. For some reason it needs to be j160 or bust. That could of just been on the two systems I tried it on but that’s what it looks like to me so far anyway. More people and more tests might expand on that though so it’s only via my bird eye and not set in stone..
    4 points
  46. 4 points
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...