Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/08/2021 in all areas

  1. 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!
    8 points
  2. 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é)
    6 points
  3. @LIMITANT - Thank you, I did manage to compile the kexts but did not have the chance to check without the mentioned boot args as the wife was on my back to do the gardening (should have stayed a bachelor ).
    6 points
  4. I encourage all less advanced users to read these instructions in detail so that their hackintosh gets better and better with the improvements of OpenCore. Some users are only interested in config.plist changes to get the new version up and running in no time. This is the wrong approach because this makes errors more difficult to understand or fix. This time the writing of the differences between versions has been very complicated. OpenCore developers have made a lot of changes and improvements. Suffice it to say that over 60 compilations have been released throughout May. Some of the changes are real news and require study and learning to be fully understood. With all this, Opencore is improving and currently has reached a maturity that has nothing to do with its consideration as a beta program. OpenCanopy continues with its great evolution and brings many changes and improvements. Some of these enhancements require training and will only be used by a limited number of users and mostly by artists designers of themes and icons. Improvements of the OpenCore graphical interface have been huge in just a few releases. The text is divided into sections: config.plist: display rotation, flavours, SIP and other modifications. csrutil and SIP: added 2 new tools to have an easy handling of SIP from the picker. OpenCanopy: new structure of the Resources/Image folder, themes organized by author, new Flavour system (custom icons in Entries and Tools), etc. message from vit9696 Do not miss the @vit9696 message as every time a new version of OpenCore is published, it is the best way to know the main changes and improvements applied. config.plist Display rotation ProtocolOverrides > added AppleEg2Info (Boolean): replaces the Apple EFI Graphics 2 protocol with a builtin version. This protocol allows newer EfiBoot versions (at least 10.15) to expose screen rotation to macOS. It can be False. NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > added ForceDisplayRotationInEFI (Number): defines display rotation. It can be 0 for no rotation or any of 90, 180, 270 for matching rotation in degrees. Only enabled if AppleEg2Info=True. Flavour Misc > Boot > PickerAttributes > added a new bitmask 0x0080 — OC_ATTR_USE_FLAVOUR_ICON to enable flavours. Misc > Entries > added Flavour (String) to configure custom icons for Entries. It can be Auto. Misc > Tools > added Flavour (String) to configure custom icons for Tools. It can be Auto. PlatformInfo > Generic AdviseWindows replaced by AdviseFeatures (Boolean) to update FirmwareFeatures (PlatformInfo > PlatformNVRAM and PlatformInfo > SMBIOS) with supported bits. It can be False. A new bit has been added to FirmwareFeatures: FW_FEATURE_SUPPORTS_APFS (0x00080000) Without this bit, it is not possible to install macOS on an APFS disk. On most newer UEFI firmwares these bits are already set. Note: most of us use only Generic section of PlatformInfo and don't need to install FirmwareFeatures or FirmwareFeaturesMask. But we all need to replace AdviseWindows with AdviseFeatures. Misc > Security Added AllowToggleSip (Boolean): if True, it enables the ToggleSIP tool to enable or disable System Integrity Protection in OpenCore picker. This will toggle Apple NVRAM variable csr-active-config between 0 for SIP Enabled and a default for SIP Disabled (currently 0x26F). Note: It is strongly recommended not to make a habit of running macOS with SIP disabled. Note: OpenCore uses 0x26F even though csrutil disable on Big Sur sets 0x7F. For any other value which you may need to use, it is possible to configure CsrUtil.efi as a TextMode tool entry to configure a different value, e.g. use toggle 0x67 in Arguments to toggle the default SIP Disabled value for macOS Catalina. It's mandatory to download the new Labels folder included into OcBinaryData from Acidanthera. This folder now contains 2 new labels SIPEnabled and SIPDisabled, without them OpenCanopy falls back to text mode. UEFI > Output GopPassThrough changed type from Boolean to String. This option provides the GOP protocol for firmware that do not implement the protocol. Supported values are: Enabled (provide GOP for all UGA protocols), Apple (provide GOP for AppleFramebufferInfo-enabled protocols) and Disabled (do not provide GOP). Failsafe Value is Disabled. This option requires ProvideConsoleGop to be enabled. Memory testing utility Added Flavour key for MemTest (memtest86) and updated recommended memtest86 config in sample.plist files. To use MemTest you have to download memtest86 from its website. Mount the file memtest86-usb.img. Now, you should see a folder named EFI containing a folder named BOOT, open it. We are interested in only 2 files: BOOX64.efi (it's the app for 64 bits) and unifont.bin. Save these 2 files in a folder called memtest86 and put this folder inside the OpenCore Tools folder. The Path key of this tool in config.plist must point to memtest86/BOOTX64.efi. This way, running MemTest from its icon in the picker executes the memory check. CPU info for Hyper-V Kernel > Quirks > added ProvideCustomCpuInfo ProvideCurrentCpuInfo (Boolean): Provides current CPU info to the kernel. This quirk currently provides correct TSC and FSB values to the kernel. It's for Hyper-V virtual machines. It can be False. csrutil and SIP Added optional ToggleSIP system boot menu option: ToggleSIP (Enabled) / ToggleSIP (Disabled). It doesn't exist in the Tools folder, i's included into OpenCore. Operation is very simple. The tool is on/off style. By clicking on the icon, the status changes (Enabled > Disabled and vice versa). If csr-active-config has a value assigned (not empty) in config.plist, this is the setting that will be active on every new boot. Otherwise, action performed on Toggle SIP is kept between boots. Added CsrUtil.efi tool, similar to Apple csrutil. Visible in the Tools folder. It is an argument tool: you can pass argument in config.plist (active at every boot) setting it as TextMode tool or run it interactively from OpenShell. Available arguments in text mode: clear, enable value, toggle value, status. It is not required to have both tools active in the picker. Toggle SIP works fine even if CsrUtil.efi is disabled and not showing in the picker. And vice versa. SIP values which affect macOS updates are documented in configuration docs. OpenCanopy Added support for display rotation (0, 90, 180, 270). Changed OpenCanopy image directory to support subdirectories. Changed OpenCanopy preferred image set to Acidanthera\GoldenGate (former Modern theme). Implementation of boot entries Flavour system. OpenCanopy image directory structure There is a new structure of the Resources/Image folder, now subdirectories with themes are supported. It's set in Misc > Boot > PickerVariant. An icon set is a directory path relative to \EFI\OC\Resources\Image where the icons are located, in the Creator\Set format. OcBinaryData now have the following icon sets: Acidanthera\GoldenGate - macOS 11 styled. Acidanthera\Syrah - macOS 10.10 styled. Acidanthera\Chardonnay - macOS 10.4 styled. We have 2 ways to assign a value to PickerVariant: Predefined aliases: Default: Automatically select Acidanthera\GoldenGate. Auto: Automatically select one set of icons based on the Default Background colour: Acidanthera\GoldenGate for Black and Acidanthera\Chardonnay for Light Gray. Icons sets included into its own folder (as mentioned above), writing the value Creator\Set in PickerVariant. For example, you have 3 icon sets made by different vendors: EFI\OC\Resources\Image\Acidanthera\GoldenGate\Apple.icns, AppleRecv.icns, ApleTM.icns, BtnFocus.icns... EFI\OC\Resources\Image\Blackosx\BsxM1\Apple.icns, AppleRecv.icns, ApleTM.icns, BtnFocus.icns... EFI\OC\Resources\Image\Chris1111\Apple-BnW\Apple.icns, AppleRecv.icns, ApleTM.icns, BtnFocus.icns.... Depending on the value of PickerVariant: PickerVariant=Default > GoldenGate is the chosen theme PickerVariant=Blackosx\BsxM1 > BsxM1 is the chosen theme PickerVariant=Chris1111\Apple-BnW > Apple-BnW is the chosen theme. PickerVariant intentionally supports \ or / as separator, e.g. Blackosx\BsxM1 or Blackosx/BsxM1. Note: you must remove prefixes from icon names. Flavour: custom icons in Entries and Tools There is a new flavours system for custom icons in Entries and Tools. It's set in Misc > Boot > PickerAttributes. A new bitmask 0x0080 — OC_ATTR_USE_FLAVOUR_ICON has been added in PickerAttributes. When it's true enables flavours, boot entries content descriptions to have custom icons for Entries and Tools. These flavours can be enabled when PickerAttributes=144 (0x90 hex) which is the sum of: - 0x0010 - OC_ATTR_USE_POINTER_CONTROL + 0x0080 - OC_ATTR_USE_FLAVOUR_ICON ->10 + 80 = 90 hex = 144 decimal. When using flavours, it is recommended to disable: 0x0001 - OC_ATTR_USE_VOLUME_ICON. Flavour is a new string key added in Misc > Entries and Misc > Tools. Its value is a succession of text elements separated by : up to a maximum of 5 elements. The first item has the highest priority and the last item has the lowest priority. Flavour value by default is Auto. When Flavour has a custom value in an Entry or Tool, OpenCanopy looks for the icon named with that value in the folder of the active theme. If the icon corresponding to the first element of Flavour does not exist, the second is selected and so on. If none of Flavour icons are found, default icon is assigned according to the type of Entry. An example of Flavour could be Windows10:Windows in an Entry for a Windows 10 system. If there is a Windows10.icns file, this is the one associated with the Entry but, if it does not exist, Windows.icns is searched and, if it does not exist, default icon for this type of Entry is loaded (HardDrive.icns). With this method it is easier to configure custom icons for Entries, you just have to include the icons in the Icon Set and configure the Flavour key. Example: How to set Flavours for Big Sur, Catalina, Monterey and Windows? Set 144 (0x90 hex) value in PickerAttributes. Put the appropriate icons in the theme's folder. In this example, we are going to use Apple11.icns + ExtApple11.icns (Big Sur), Apple12.icns + ExtApple12.icns (Monterey), Apple10_15.icns + ExtApple10_15.icns (Catalina) and Windows10.icns + ExtWindows10.icns. Without Ext icons it doesn't work (at least in the tests I have done). macOS Entries only need the icons, nothing more; macOS will have its flavour set automatically by OC and it will pick the correct icon from the theme set in PickerVariant; this way it is possible to have different icons for different versions of operating systems. Windows Entry needs Flavour=Windows10:Windows. Thanks to @blackosx for these beautiful hardrive icons with images. Note: There is an intention to have a list of tools which are common enough that some icon pack artists may wish to provide an icon for them, for example ToggleSIP.icns or MemTest.icns. Certain well-known bootloaders have also been assigned a flavour (OpenCore of course, Grub2). This way, Flavour will allow to display a custom icon (if it exists) for these elements. Do I have to use Flavour in all cases? Short answer: no Flavour property in config.plist isn't required for macOS because macOS (versions included) is detected by OpenCore and the correct icon is picked up automatically. Flavour property has to be used when OpenCore does not automatically pick up the icon for an element, specifically Entries and Tools. There is no need to create an Entry to apply a flavour; if you need to apply a flavour and there isn't already an entry, then you must use a .contentFlavour file. You don't have to use Flavour in all cases, generally themes and Icon Sets are enough to customize the picker to your liking, reserving Flavour for more specific uses. .contentFlavour file Another way to get flavours is by placing a .contentFlavour file next to the operating system's bootloader. This option is indicated when the system does not have an entry created in config.plist. For example, for a Windows system the .contentFlavour file must be in the /EFI/Microsoft/Boot/ folder of the Windows EFI partition. The content of .contentFlavour is the same as Flavour key: Windows10:Windows, assuming there is a Windows10.icns icon into the active theme folder. It is another way to have flavours but more complex than if you use the Flavour key in an Entry. Algorithm used to determine content flavour For a Tool, the value is read from Flavour key. If Flavour=Auto and there is no .contentFlavour file, entry flavour is chosen based on the entry type (e.g. Windows automatically gets Windows flavour). For an automatically discovered entry, it is read from the .contentFlavour file next to the bootloader, if present. If there is a .VolumeIcon.icns (placed at the root of the Preboot volume (macOS) or at the root volume for other filesystems) it takes precedence over .contentFlavour file. For a custom entry: it is read from the .contentFlavour file next to the bootloader if Flavour is Auto otherwise it is read from Flavour key. Note: To better understand flavours, it is advisable to read Mike Beaton's text explaining these changes and defining flavours lists. Kexts It is recommended to switch to the new versions of the kexts that have been modified and updated: RestrictEvents 1.0.2 AppleALC 1.6.1 NVMeFix 1.0.8 VirtualSMC 1.2.4 BrightnessKeys 1.0.2 WhateverGreen 1.5.0 SidecarFixup 1.0.1 BrcmPatchRAM 2.5.9 MacHyperVSupport 0.5 gfxutil 1.81b. Replace only the ones you use regularly. Note: AppleALC is accompanied by a new variant called AppleALCU.kext intended for systems that have digital audio (USB) only.
    4 points
  5. I installed Monterey over Big Sur. I am not using Lilu and all around so I need no new boot-args. VoodooHDA continue working. FakeSMC with plugins are working too.
    4 points
  6. In my opinion, please use the current release with beta flag, until 2021.07 has been released in July.
    4 points
  7. Success. With these kexts i can boot Big Sur and Monterey. Bluetooth is working without any kexts. Hackintool quits when opened.
    4 points
  8. or replace garden with nice concrete pavers....but be warned then there's power washing every few years....
    4 points
  9. Will be. It was night for me when Monterey was introduced and this moment I am at work. Wait please.
    4 points
  10. Some of you (or then again maybe none at all) , may be wondering why I've been silent on this Monterey Beta, quite frankly it gave me a battle to get it up and running after a fresh install. Initially I changed nothing from BS but at boot during the verbose text the purple lines appeared like the first BS Beta and then the graphics signal will just die, aha I thought, I need to add a boot arg of some sort. So with my injured pride I scoured the posts here from the knowledgeable and came up with pleasing results, kudos to all the OC Brainiacs here on IM. See attached (so far as I can tell everything is working apart from Graphics Card is not displayed in About this Mac).
    4 points
  11. macOSDeveloperBetaAccessUtility.dmg.zip
    4 points
  12. I upgraded from Big Sur 11.5 beta to Monterey with no problems I have everything as before. I did the clean install on Monterey hdd, everything perfect.
    3 points
  13. Thank you give me more lively. Now I can boot the iMac14.2 smoothly. Plus, the sound is very complete.
    3 points
  14. @SavageAUS It is done automatically, no need for update. It's working. [...] 24:582 0:000 AddKextsInArray from 12 24:582 0:000 ->Extra kext: 12\AppleALC.kext (v.1.5.7) 24:582 0:000 ->Extra kext: 12\IntelMausi.kext (v.1.0.3) 24:582 0:000 ->Extra kext: 12\Lilu.kext (v.1.5.0) 24:582 0:000 ->Extra kext: 12\Sinetek-rtsx.kext (v.9) 24:582 0:000 ->Extra kext: 12\SMCBatteryManager.kext (v.1.1.9) 24:582 0:000 ->Extra kext: 12\SMCProcessor.kext (v.1.1.9) 24:582 0:000 ->Extra kext: 12\USBPorts.kext (v.1.0) 24:582 0:000 ->Extra kext: 12\VirtualSMC.kext (v.1.1.9) 24:582 0:000 ->Extra kext: 12\VoodooPS2Controller.kext (v.2.2.2) 24:582 0:000 |-- PlugIn kext: 12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext (v.2.2.2) 24:582 0:000 |-- PlugIn kext: 12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext (v.2.2.2) 24:582 0:000 ->Extra kext: 12\VoodooRMI.kext (v.1.3.3) 24:582 0:000 |-- PlugIn kext: 12\VoodooRMI.kext\Contents\PlugIns\VoodooInput.kext (v.1.1.3) 24:582 0:000 |-- PlugIn kext: 12\VoodooRMI.kext\Contents\PlugIns\RMISMBus.kext (v.1.0) 24:582 0:000 ->Extra kext: 12\VoodooSMBus.kext (v.3.0) 24:582 0:000 ->Extra kext: 12\WhateverGreen.kext (v.1.4.5) 24:582 0:000 AddKextsInArray from 12_normal 24:582 0:000 AddKextsInArray from 12.0 24:582 0:000 AddKextsInArray from 12.0_normal 24:582 0:000 AddKextsInArray from 12.0.0 24:582 0:000 AddKextsInArray from 12.0.0_normal [...]
    3 points
  15. i m updated from yesterday On Z390 Aorus pro and RX 590 All working,but as usual the first beta is bugy..
    3 points
  16. Now I also get 503. Here they are zipped as I downloaded them earlier. kexts.zip
    3 points
  17. Have this into your bookmarks, the repo where new builds for OpenCore and kexts are released. https://github.com/dortania/build-repo/releases Get kexts with comment ready for Monterey.
    3 points
  18. My installation is perfect.😁
    3 points
  19. 3 points
  20. So I was able to boot to Monterey successfully. I seem to have an issue with bluetooth loading properly but I will work on that. In the meantime, for those who, like me, forget this annual venture into uncharted waters, remember that this is a new version of macOS. If you use Lilu, be sure to add -lilubetaall to your boot args and, if you use Clover, be sure to put your custom kexts in the Other folder in Kexts. Once I did that, my system started up just fine.
    3 points
  21. OpenCore 0.7.0 EFI Update (Big Sur 11.6 Ready), 7th June 2021 (Use With Bios Revision F11L or Newer) The EFIs and DSDTs have now been updated to the my latest versions. Changes made include, Lilu 1.5.3, AppleALC 1.6.1, IntelMausi 1.0.6, VirtualSMC 1.2,4, WhateverGreen 1.5.0 OpenCore Updated to Revision 0.7.0 (Big Sur 11.5 Ready), SIP can now be toggled from within OpenCanopy New OpenCanopy Icons HFSPlus Updated Plus other minor tweaks and changes to all of the configs. OpenCore EFI Update v0.7.0 - 07/06/2021 OC 070 1,1 Z390 Master EFI.zip - OpenCore v0.7.0, SMBios iMacPro1,1 (IGPU Disabled) OC 070 19,1 Z390 Master EFI.zip - OpenCore v0.7.0, SMBios iMac19,1 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 Sadly this will be my last EFI update for this thread as my focus is no longer on the Intel side of life and it’s hard for me to keep up with little quirks and problems on the EFI side of life. Im still here to annoy you all though and the thread will stay alive. Enjoy and BigUps AG
    3 points
  22. Soporte: iMac: desde 2015 en adelante iMac Pro: desde 2017 en adelante MacBook Air: desde 2015 en adelante MacBook Pro: desde 2015 en adelante Mac Pro: desde 2013 en adelante Mac mini: desde 2014 en adelante MacBook: desde 2016 en adelante Algunas novedades en apps nativas, son compartidas con los sistemas operativos del iPad e iPhone. Facetime: ahora aisla el sonido de fondo para potenciar la voz. También permite utilizar el chip M1 para crear modo retrato en tiempo real. Nueva vista para ver a todos los participantes en la llamada con el mismo tamaño y enlaces para que Facetime funcione en Android. SharePlay: esta nueva función permite a los usuarios compartir contenido de sus aplicaciones con otros usuarios de Apple. Los desarrolladores pueden usar la API para que se comparta contenido con apps de terceros. Compartido contigo: una nueva función para que todo el contenido que se comparte mediante la app de mensajes se incluya en una carpeta dentro de la app Fotos. AirPlay: ya es compatible, por lo que podemos enviar contenidos de iPhone y iPad al Mac. Fotos: ahora es capaz de detectar texto, por lo que podemos aislar números de teléfono, direcciones, enlaces a páginas web, etc. Todas las funciones: https://www.apple.com/macos/monterey-preview/features/ Monterey debería funcionar sin problemas con opencore 0.6.9, pero se recomienda usar la version 0.7.0, y actualizar los kexts. Como en la última versión de Big Sur debes tener correctamente mapeados los puertos USB. El audio precisa de agregar el boot flag -lilubetaall, hasta que se actualice lilu. Descarga y ejecuta gibMacOS.command Elige la opción C: C. Change Catalog (Currently publicrelease) Elige la opción 4: 4. developer Finalmente la opción 1 macOS 12 Beta Puede crear un instalador USB de arranque de Monterey formateando primero un USB de 16GB o 32GB como Mac OS Extended (Journaled) y nombrándolo "Untitled".Después de descargar el instalador Monterey Beta 1 (que hasta ahora no tiene nombre, aunque ahora sabemos que tiene el nombre Monterey), puede ejecutarlo en la Terminal para hacer el USB de arranque:sudo /Applications/Install\ macOS\ 12\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/UntitledEl comando probablemente cambiará con Beta 2 y las betas posteriores asudo /Applications/Install\ macOS\ Monterey\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitledy luego con la divulgación pública (o incluso la liberación de candidatos) asudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled gibMacOS-master.zip
    2 points
  23. @chris1111 I have i5-4300U Haswell with HD 4400. MBP11,4 also Haswell and it is not dropped, still on support list. It is working natively without any issues.
    2 points
  24. 2 points
  25. 2 points
  26. check your boot syntax, I had the same experience but -lilubetaall Brought it back. per @PMheart continue to use the boot flags for Lilu and WEG. -v keepsyms=1 -lilubetaall -wegbeta
    2 points
  27. Hi, I'd like to inform everybody that even though Apple reports that the minimum iMac version for Monterey is iMac16,1 (Late 2015, with Broadwell or later), Azul graphics drivers are still present in macOS 12, and the only parameter necessary to boot the system is -no_compat_check And then the installer works perfectly, does not complain about iMac15,1 SMBIOS which I am currently using. The repository can be found here: https://github.com/1alessandro1/HP-Prodesk-600-G1-SFF-macOS I'll soon merge the 0.7.0 branch to master
    2 points
  28. Do you have an USB audio device? Have you installed AppleALCU instead of or in addition to AppleALC? EDIT: I see you only have AppleALC. My post was published a few seconds before yours Sorry, I can't help you with Clover because I'm on OC but your hardware has to work fine with Monterey, it's very similar to mine.
    2 points
  29. 2 points
  30. BrcmPatchRAM issues seems to be related to firmware loading. If you require BrcmBluetoothInjector and the BrcmFirmwareData kext, it currently isn't working for Monterey.
    2 points
  31. FCPX, Motion and Compressor ok Monterey
    2 points
  32. Working 11.5b, 12b1 We're happy (and, frankly, relieved) to announce the immediate availability of SuperDuper v3.5 Beta 1: our first version to fully support Big Sur backups. https://www.shirtpocket.com/blog/index.php/shadedgrey/comments/finally/ https://s3.amazonaws.com/shirtpocket/SuperDuper/SuperDuper! 3.5 B3.dmg
    2 points
  33. Updated without problems. Approx. 45' in total. I have used -lilubetaall in boot-args. The rest of the EFI folder is the same as for Big Sur. This test with iMac19.1. Slight disappointment to see the system so similar to Big Sur, at least in the user interface. Graphics card is missing from About this Mac but not from System Profiler. I have graphics acceleration with the RX 580 primary card and the iGPU in headless mode seems to work fine judging from what I see on the Intel Power Gadget while I was running a graphics test. Monterey works surprisingly well for such an early beta.
    2 points
  34. Smooth installation, zero problems. Interesting, that now you can have same windows across two desktops/monitors, nice.
    2 points
  35. By the time this finishes downloading I'll have to go to bed. So no testing until tomorrow evening. Are the nvidia drivers still there? Hoping they haven't dropped support for other v1 Metal cards like my 670.
    2 points
  36. Ok, so a new background and new Safari. The Intel HD4000 driver is gone. The Intel Power Gadget still works, so no changes regarding third-party kexts.
    2 points
  37. OpenCore 0.7.0 EFI Update (Big Sur 11.5 Ready), 7th June 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.3, AppleALC 1.6.1, IntelMausi 1.0.6, VirtualSMC 1.2.4, WhateverGreen 1.5.0, OpenCore Updated to Revision 0.7.0 (Big Sur 11.5 Ready), SIP can now be toggled via OpenCanopy, New OpenCanopy Icons, HFSPlus Updated, Plus other minor tweaks and changes to all of the configs, OpenCore EFI Update v0.7.0 - 07/06/2021 OC 070 19,1 Z390 Pro EFI.zip - OpenCore v0.7.0, SMBios iMac19,1 OC 070 1,1 Z390 Pro EFI.zip - OpenCore v0.7.0, SMBios iMacPro1,1 (IGPU Disabled) OC 070 19,1 Z390 Pro iGPU ONLY EFI.zip - OpenCore v0.7.0, SMBios iMac19, IGPU ONLY 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.9. Use the new Config.plist instead. For OpenCore Using PlistEdit Pro add your details by modifying the following Sadly this will be my last EFI update for this thread as my focus is no longer on the Intel side of life and it’s hard for me to keep up with little quirks and problems on the EFI side of life. Im still here to annoy you all though and the thread will stay alive. Enjoy and BigUps AG
    2 points
  38. @miliuco Just a post above yours... but I edited OP as well.
    2 points
  39. At least, a new wallpaper 😧
    2 points
  40. Version 1.0.0

    6,191 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
    1 point
  41. Monterey works surprisingly well in my hack considering it's a very early beta: CPU and RX 580 scores are very similar to Big Sur The system behaves very smoothly and with performance comparable to Big Sur The apps i have tried so far work fine As I have Fenvi T-919, Bluetooth and Wifi work fine. A couple of things that don't work: When choosing a desktop picture, we have to download it from the download icon but it will not download, only the Monterey-specific wallpapers (the colored ones) are enabled System Preferences> Screens takes a few seconds to open, when it opens it works fine. Note: I use BT speaker so I have not tried AppleALC which is giving problems to some users.
    1 point
  42. No, probably new patch is needed. Look appropriate topic https://www.insanelymac.com/forum/topic/330614-marvell-aquantia-10-gb-ethernet-support-thread/page/15/#elControls_2760169_menu Update: This patch works https://www.insanelymac.com/forum/topic/330614-marvell-aquantia-10-gb-ethernet-support-thread/?do=findComment&comment=2760231
    1 point
  43. Z490 HACK updated from auto updates. didn't change anything in my EFI Folder. sound from motherboard stopped but got sound though HDMI. (mite need a new ALC KEXT to get onboard sound working UPDATE. Have went back to BigSur. on my Z490 Hack. as I can't get a stable install on it.(random crashes.)on board Network not working I have my old Z97 Hack this installed Monterey no problems there just changed id from 15,1 to 17,1. so I will use that hack for experimenting with. weather to nice to be inside Hackintoshing at the moment
    1 point
  44. But since @PMheart has released kexts for Monterey (AppleALC included) I think it's better to use them without this boot argument. Same with -lilubetaall, now I'm working without it.
    1 point
  45. installation without problems, I have not made any modifications to my EFI that I use with BigSur, I have not had black screen blocks.
    1 point
  46. Update went well, except I don't have sound... but I'll work on that. Used -llibetaall in boot arguments, and my RX 570 is a no show in system profiler too...
    1 point
  47. It looks like macOS Monterey now supports variable refresh rate. I have an AMD Freesync Premium 165 HZ monitor and can see "Variable" being a refreshrate option. In Big Sur I could choose up to 165 HZ, In Monterey I can choose 144 HZ, and then Variable. EDIT: changing some display properties such as refresh rate can reboot the system, and there is flickering with Variable refresh rate option. Maybe Whatevergreen needs to be updated to inject something more? Or it is simple just because it is a macOS beta.
    1 point
  48. When I try to create the installer USB in terminal I get the error message "/Applications/Install macOS 12 Beta.app does not appear to be a valid OS installer application". Help. thanks
    1 point
  49. 1 point
×
×
  • Create New...