EnriqueV

Avoiding EFI Multiboot Problems With GRUB2 and Linux/MacOS/Windows Note that not every combination of installed and otherwise boot capable devices (spinning rust, SSD, NVMe) will be selectively recognized by the BIOS as bootable. BIOS and/or hardware and/or firmware limitations may determine which devices can be used together. Operating system contraints can also be a factor. So do the research first for hardware and software compatibility, and make sure that the BIOS and firmwares are up to date. Create a FAT32 ESP (suggest 400 MB) on your intended boot device, and verify that the BIOS is configured to boot from that device. For those who have multiple SSD devices, each with an installed operating system, including at least one drive with linux installed, and complaining that the linux bootloader, GRUB2, overwrites the ESP, the following information may be of help in resolving your issues. Note that if you are not using GRUB2 as your main bootloader, it does not need to be installed on the ESP. This is a choice for you to make when you are installing linux. If, however, you wish to use GRUB2 as your main bootloader, you can avoid multiboot problems by installing both linux and GRUB2 to the same partition. Once installed, open a linux terminal session and create an efi directory (if one does not already exist): sudo mkdir /boot/efi next, mount your ESP to the efi directory: sudo mount /dev/sda1 /boot/efi (verify your FAT32 ESP partition number with "sudo fdisk -l") next, install GRUB2 boot parameters to the ESP: sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Linux --recheck --no-floppy --debug note that the parameter --bootloader-id=Linux will produce an ESP entry named Linux. You can change the name to suit your taste. There should be an ESP linux file tree entry that includes grub.cfg. Within grub.cfg, xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is the partition UUID of the linux installation, and in this example, hd0 and gpt2 are the GRUB2 hard drive number and partition number, respectively, pertaining to the linux installation: search.fs_uuid xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx root hd0,gpt2 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg if no installation errors were reported, you can now unmount the ESP: sudo umount -l /dev/sda1 Once you have installed GRUB2 parameters to the ESP using this method, designating GRUB2 as your main bootloader, the GRUB2 boot menu will be located in the linux partition file tree as follows: boot/grub/grub.cfg Note that now, when updating the GRUB2 boot menu for your linux installation (for example, by installing a new kernel or manually updating with update-grub), the updated boot menu is written to the linux partition, and not the ESP. This means that even if you are not using GRUB2 as your main boot loader, linux updates should not overwrite the ESP. Alternatively, if you are using Open Core as your main boot loader you can create a custom boot menu entry to chainload the GRUB2 bootloader: <key>Entries</key> <array> <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>Name</key> <string>GRUB2</string> <key>Path</key> <string>the PciRoot data for your configuration goes here</string> <key>TextMode</key> <false/> </dict> </array> If, however, you do decide to use GRUB2 as your main boot loader, you can add custom entries to boot linux, macOS, and windows following the instructions here: https://www.olarila.com/topic/15309-updated-big-surmonterey-tipsobservations/

https://www.olarila.com/topic/15309-updated-big-surmonterey-beta2-tipsobservations/

updated 26 August, 2021 tags: Big Sur/Monterey multibooting chainloading tweaks brew migrating apps tags: Big Sur/Monterey partitioning multibooting chainloading tweaks brew migrating apps links swap virtual memory Some updated tips and observations concerning Big Sur/Monterey installation to an available APFS HDD container/partition. Assumes an existing working ESP bootloader. System file modifications are made in recovery terminal with SIP disabled (csrutil disable and csrutil authenticated-root disable) Any changes to the system files in recovery console require creating a new shapshot to be retained. A comment about installing Monterey beta. If you have downloaded a Monterey full installer and if you have an existing installation of Big Sur with sufficient free space, you can create a new APFS partition and replicate Big Sur to your new partition with SuperDuper v3.5 beta3 or newer. Then install Monterey over the copy of Big Sur. This should preserve your configurations and installed programs without having to create a USB installer. For both Big Sur and Monterey you can edit the name of your Open Core or Clover boot entries within: .disk_label.contentDetails located in the file tree here: System/Volumes/Preboot/UUID/System/Library/CoreService where a UUID is the actual directory name. As pertaining to Big Sur: 1. Go ahead and make your USB installer with Open Core or Clover, but if you have an existing install of Catalina you can save time by starting the Big Sur installer directly from Catalina, choosing the target partition, and letting the installer copy over the install files rather than waiting on USB to boot and copy. If you then need the USB installer to boot and complete the Big Sur installation, you are prepared. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bootmanagers and bootloders and partitioning <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< A warning about partitioning. There are numerous well known third party partitioning programs, including those running on windows, that can alter the partiton table in such a way as to render your APFS containers unrecognizable and unbootable. Whenever possible use the mac OS Disk Utility to do your partitoning, and do so after you have backed up your partition table with a suitable utility. One such free utility for linux is sgdisk. You can boot a live linux distro from USB, and backup/restore your hard drive (example: /dev/sda) GPT partition table to/from USB media as follows: backup: sudo sgdisk --backup=/path/to/USB/sda_partition_table_01.01.2021 /dev/sda restore: sudo sgdisk --load-backup=/path/to/USB/sda_partition_table_01.01.2021 /dev/sda 2. If you are a linux multi-booter and using GRUB2 as your main bootloader, and if you have an existing Catalina install with a working chainloaded Open Core or Clover, suggest you don't disturb/break your existing bootloader by making tweaks for Big Sur. You can make an additional small 200MB FAT32 partition on your HDD and put your Big Sur bootloader there. Note that if you choose to use clover you can directly chainload from GRUB2 by adding this entry to your grub.cfg file (where xxxx-xxxx is your Big Sur bootloder partition from "lsblk -f" or "sudo blkid" terminal output in Linux): menuentry "Clover"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/CLOVER/CLOVERX64.efi # or whatever path you use } With Open Core version 0.6.4 and earlier chainloading from GRUB2 was relatively simple with grub.cfg menu entry: menuentry "Open_Core"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/OC/OpenCore.efi # or whatever path you use } Note: Observed with Open Core 0.7.3, GRUB2 can once again directly chainload OpenCore.efi. Future code changes may prevent direct chainloading and you may wish to use Refind boot manager. You can install Refind 0.13.2 to the same ESP with GRUB2 and chainload to Refind in grub.cfg with the following menu entry (where xxxx:xxxx is your ESP UUID}: menuentry "refind"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/refind/refind_x64.efi } A note from the refind page author: http://www.rodsbooks.com/refind/ begin excerpt: Note: I've seen reports that rEFInd is failing to boot macOS 11 ("Big Sur"). There seem to be two problems. First, and confusingly, macOS 11 requires booting via the boot loader Preboot partition, not the main macOS installation partition. With recent versions of macOS, rEFInd normally presents both options, but users might reasonably hide the poorly-named Preboot option, which is the only one that works. Second, a bug in rEFInd 0.12.0's memory management could cause it to hang on some EFIs, including some that Apple rolled out as part of the macOS 11 upgrade. Using rEFInd 0.13.0 and booting via the Preboot loader option should work around these problems. If all else fails, the new (rEFInd 0.13.0) feature to boot via an EFI firmware boot option may help; see the description of this feature here. end excerpt. You can launch Open Core from the Refind GUI. Here is a sample refind.conf that should chainload Open Core (where xxxx is the volume name or UUID name of your Open Core partition): menuentry "OpenCore" { icon /EFI/refind/icons/youricon.png volume xxxx loader /EFI/OC/OpenCore.efi options "-v" } When chainloading Open Core from Refind you may have to change the Vault configuration in Open Core config.plist from Secure to Optional. This chainloading is an extra step but it preserves GRUB2 as the main bootloader and facilitates use of newer Open Core versions. Note that you can install GRUB2, Refind, Open Core and the windows 10 bootloader bootmgfw.efi all on the ESP or you can install Open Core to a separate partition in order to edit/tweak your Big Sur bootloader settings without breaking an existing working ESP bootloader. When editing config.plist files, if you are not comfortable using an XML editor, and you have Catalina installed, you can download ProperTree from github and launch it from Catalina. For Linux multibooters, you can modify your linux /etc/grub.d/40_custom to include any custom bootloader menu entries you want to keep, and then run update-grub from within Linux. Using GRUB2 to chainload windows 10 in EFI mode. Make sure that both secure boot and TPM are disabled in BIOS Hide TPM in BIOS config. Verify that windows was installed in EFI mode or has been configured after the install to boot in EFI mode. Ensure that GRUB2 in your BIOS EFI config is your default boot selection. Migrate the windows 10 boot files including BCD files to the main Windows partition as they are not there by default. Verify that your machine is booting in EFI mode and not CSM. Verify that your EFI boot partition has "boot" and "ESP" flags set. Make sure you shut down windows while holding down the shift key until completely shut down. As an example, using a single hard drive for all of your OS's, your GRUB2 grub.cfg windows 10 boot entry should look similar to the configuration below where xxxx-xxxx represents the UUID of the windows 10 partition, where the "x" in sdax represents the linux GRUB2 number of your ESP (with /efi/Microsoft/Boot/bootmgfw.efi), where the "x" in hdx and ahcix represents the GRUB2 hard drive number of the windows 10 installation, and where the "x" in gptx represents the GRUB2 partition number of the windows 10 installation. GRUB2 numbers hard drives starting with 0, and partitions starting with 1. Examples: /dev/sda1, hd0,gpt3, ahci0,gpt3. menuentry 'Windows Boot Manager (on /dev/sdax)' --class windows --class os $menuentry_id_option 'osprober-efi-xxxx-xxxx' { insmod part_gpt insmod fat set root='hdx,gptx' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hdx,gptx --hint-efi=hdx,gptx --hint-baremetal=ahcix,gptx xxxx-xxxx else search --no-floppy --fs-uuid --set=root xxxx-xxxx fi chainloader /efi/Microsoft/Boot/bootmgfw.efi } 3. When your install is finished and you are finally at the working desktop, you may want to make a backup. With Catalina this was easily done by using Disk Utility from a bootable USB installer to restore to an APFS formatted backup media. The Big Sur Disk Utility ASR has repeatedly failed to replicate (bootable) Big Sur and it appears Disk Utility from Catalina 10.15.7 can not perform this task with Big Sur APFS containers. You can, however, use third party freeware other than dd to make a sector by sector clone of the entire Big Sur container onto removable media. Alternatively, depending on the size of your AFPS container/partition and transfer rate, using dd can take quite a long time to do the backup. If you only clone to USB media and then boot the clone to test the backup on the same computer from which it was made, both the Big Sur USB clone and the Big Sur HDD container installation show up within disk utility, in the USB media area. The clone will have the same UUIDs. SuperDuper v3.5 beta3 is tested and produces bootable backup with different UUIDS for both Big Sur and Monterey. 4. If your Open Core keyboard language is not properly configured the recovery console language may default to Chinese or some other language. To avoid this make sure your keyboard language is specified in Open Core NVRAM section of the config.plist. Recovery terminal is available for system file changes. The mount command within recovery terminal will show volumes. You can then run: diskutil mountDisk diskXsY (where x is the number of your Big Sur disk and y is the read-only slice from the mount command output). You can then run: mount -uw /Volumes/thenameofyourBigSurvolume (not Data volume) to make the normally read-only volume writable. Make any desired system file changes from the console and reseal (where X is your Big Sur volume name shown with mount command): bless --folder /Volumes/X/System/Library/CoreServices --bootefi --create-snapshot Reboot. 5. If you have an existing Catalina installation with brew and numerous brew installed programs such as ntfs-3g, you can directly copy the brew files/programs (usr/local) to the corresponding file system locations within Big Sur and if necessary, manually create the soft links to enable programs. If you need to write to the system file tree you can do this from the recovery console as previously referenced. NTFS volumes will normally mount read-only but read-write can be enabled if the installed /sbin/mount_ntfs supports read/write: From terminal make a mount point of your choice for each ntfs volume. Example: sudo mkdir ~/ntfs Unmount the target read-only ntfs volume where x is disk number and y is slice: sudo umount /dev/diskxsy Mount ntfs volume as read-write: sudo mount -t ntfs -o rw,auto,nobrowse /dev/diskxsy ~/ntfs Link to desktop: sudo ln -s ~/ntfs ~/Desktop/whatever_name_you_choose Make sure finder is configured to show mounted volumes on the desktop. Keep in mind that if you use ntfs-3g with osxfuse in Big Sur to automount ntfs volumes, install version 4.1.2 or later of macFUSE. You may have to copy the ntfs-3g mount_ntfs binary directly to /sbin using recovery console. Note that brew's ntfs-3g 2017.3.23_3 has previously failed to mount NTFS volumes with all files and folders visible. You can use a prior Catalina Version, although it may be necessary to copy mount_ntfs directory to /sbin. Note that as of this writing macFUSE 4.12 apparently does not support Monterey. There is a 4.20 beta that works in Monterey. If you already have an install of Big Sur with version 4.20 (beta upgrade box checked) you can easily boot into Monterey and go into Big Sur file system to Library/PreferencePanes and click the 4.20 beta preference pane to install in Monterey. Then reboot. https://osxfuse.github.io/ Any changes made to system files in recovery console should be followed by creating a new shapshot: bless --folder /Volumes/x/System/Library/CoreServices --bootefi --create-snapshot (where X is your Big Sur volume name shown with mount command. Here are some post-install terminal tweaks/info for zsh. If you do not know what they do, don't use them: defaults write NSGlobalDomain NSDocumentSaveNewDocumentsToCloud -bool false defaults write com.apple.finder AppleShowAllFiles TRUE defaults write com.apple.TextEdit RichText -int 0 defaults write com.apple.finder _FXShowPosixPathInTitle -bool YES sudo defaults write /.Spotlight-V100/VolumeConfiguration Exclusions -array "/Volumes" sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist defaults write com.apple.desktopservices DSDontWriteUSBStores -bool true defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true sudo mdutil -i off -d /Volumes/whatevervolumename (Disable Indexing AND Searching of specified Volume) sudo mdutil -a -i off top -o CMPRS top -o MEM 6. If you have an existing Catalina installation with third party programs they may work without modification by copying them directly from Catalina Applications folder to the Big Sur Applications folder AND copying the corresponding entries for those programs from Catalina ~/Library/Application Support to Big Sur ~/Library/Application Support. Note that ~/Library/Application Support refers to Users/yourusername/Library/Application Support. 7. A suitable Open Core NVRAM csr-active-config value to receive software updates with a supported hardware profile is 67080000. 8. Automator utility can create an apple script or shell script app for Big Sur but it may fail with error message when run from the desktop if absolute paths are not specified within the script. Test by opening the app in automator and click the step button and see if the app executes with the desired result. Test by running the command line directly within the zsh terminal. 9. The attached EFI with OC was modified for Skylake/520/Sunrise Point but you may find that it works for a range of models with similar Intel hardware. Supply your own Platforminfo. If you multi-boot with linux you can run lspci -k from terminal in linux to show your pci hardware configuration. The EFI attachment may be omitted from the post due to upload limitations. 10. If you desire an Open Core GUI, change the config.plist PickerMode specification from BuiltIn to External and make sure you have the required Resources installed for your version of Open Core. Set the applicable resolution for Open Core or all icons may not be completely visible. Change HideAuxiliary to true if you do not want to see recovery. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 11. Removing old/unwanted snapshots. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Boot into recovery mode and disable SIP: csrutil disable/csrutil authenticated-root disable. Reboot into recovery mode if necessary. Run the mount command to see your Big Sur partition name and disk/slice. In terminal type: diskutil mount /dev/diskXsY and hit enter (where X and Y are your Big Sur disk and slice) then type: mount -uw /Volumes/X and hit enter (where X is your Big Sur volume name) Your Big Sur volume should now be read-write. Run: bless --folder /Volumes/x/System/Library/CoreServices --bootefi --create-snapshot (and hit enter to generate a new snapshot) Now you can remove old/unwanted snapshots. diskutil apfs listSnapshots diskXsY for a list of snapshots/uuids delete unwanted snapshots one at a time: diskutil apfs deleteSnapshot diskXsY -uuid (the snapshot uuid you want to delete) How to name snapshots and make bootable snapshots from recovery console (tested with Big Sur). Create a new APFS snapshot: /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -s "you_pick_name" -v /Volumes/your_Big_Sur_volume_name Second, make it bootable: /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "you_pick_name" -v /Volumes/your_Big_Sur_volume_name >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 12. Change the Big Sur login background. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Boot into recovery mode with SIP/authenticated-root disabled. From prompt run: cd / cd into the desktop pictures folder (where X represents the name of your Big Sur install volume) cd /Volumes/X/System/Library/Desktop\ Pictures The default Big Sur login background in Desktop Pictures is Big Sur Graphic.heic. You can optionally save this graphic by typing: mv /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur\ Graphic.heic /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur\ Graphic.heic.orig Create a symlink to the desired login graphic....using Big Sur.heic as an example: ln -s /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur.heic /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur\ Graphic.heic Run: bless --folder /Volumes/x/System/Library/CoreServices --bootefi --create-snapshot Reboot. Due to a glitch in Big Sur you make occasionally reboot with your prior login background if you do not remove the snapshot that contained it. Once you have altered the installation snapshot ensure that your csr-active-config will allow booting. A suitable value for Open Core is 67080000, and for clover 0x867. Updates via full installer after altering install snapshot. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 13. Memory and Swap. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Note if you disable swap without enough memory your machine may freeze or slow to a crawl. The risk/performance tradeoff is up to you. turn off swap: sudo launchctl unload -wF /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist re-enable swap: sudo launchctl load -wF /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist delete swap: sudo rm /private/var/vm/swapfile* for those who have nvram.plist: search for swap enabled: nvram.plist vm_compressor=4 or swap disabled: nvram.plist vm_compressor=2 view swap status: sysctl -a vm.compressor_mode nvram config to enable swap: sudo nvram boot-args="vm_compressor=4" disable swap: sudo nvram boot-args="vm_compressor=2" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 14. Disabling Sleep/Hibernation <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< check state: sudo pmset -g | grep hibernatemode disable: sudo pmset -a hibernatemode 0 remove file to reclaim space: sudo rm /private/var/vm/sleepimage in /private/var/vm/ make a dummy: sudo touch /private/var/vm/sleepimage prevent write access to it: sudo chmod 000 /private/var/vm/sleepimage sudo chflags schg /private/var/vm/sleepimage >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 15. Manually install kexts to System/Library/Extensions. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< You need to enter recovery mode, open terminal, type at prompt csrutil status hit enter verify response is "disabled" if not, run at prompt: csrutil disable type at prompt csrutil authenticated-root status hit enter verify response is "disabled" if not run at prompt: csrutil authenticated-root disable reboot into recovery mode if required open terminal, at prompt run: mount hit enter verify volumes, disk numbers, slices. confirm with: diskutil list at prompt type: diskutil mountDisk diskXsY where X is the Big Sur disk number and Y is the Big Sur slice. hit enter at prompt type: mount -uw /Volumes/your Big Sur volume name hit enter at prompt type: mount hit enter Your Big Sur volume should no longer indicate read-only at prompt: cp -r where/ever/your/kext/is/whatever.kext /Volumes/your Big Sur volume name/System/Library/Extensions hit enter for each kext: at prompt: chown -R 0:0 /Volumes/your Big Sur volume name/System/Library/Extensions/target.kext && chmod -R 755 /Volumes/your Big Sur volume name/System/Library/Extensions/target.kext hit enter then type at prompt: touch /Volumes/your Big Sur volume name/System/Library/Extensions && kmutil install --volume-root /Volumes/your Big Sur volume name --update-all --force hit enter, wait for finish then type at prompt: /Volumes/your Big Sur volume name/usr/sbin/kcditto hit enter, wait for finish then type at prompt: bless --folder /Volumes/your Big Sur volume name/System/Library/CoreServices --bootefi --create-snapshot hit enter, wait for finish reboot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16. some intel wifi info <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Lilu.kext should load first and -lilubetaall in boot arguments in config.plist. Use either Itlwm.kext with Heliport.app OR AirportItlwm.kext. Don't load both Itlwm.kext and AirportItlwm.kext. Itlwm.kext version 1.2.0 has worked well with Catalina and Big Sur when used in conjunction with the Heliport.app. If you have both Catalina and Big Sur installed and prefer to use AirportItlwm.kext, you can rename one of them (example: Catalina version renamed to AirportItlwm2.kext) and inject them with Open Core by specifying MinKernel and MaxKernel versions in the config.plist to load the appropriate kext based on whether Catalina or Big Sur is booting. Useful links: https://github.com/1hbb/OpenIntelWireless-Factory/releases https://github.com/ClayMoreBoy/Hackintosh-Kext-Factory/releases >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Audio config <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The following information excerpted from the web may help you: For Open Core: Suggest you use AppleALC and modify the Open Core config.plist to show the layout-id for your audio. Don't use the kernel switch method for Open Core. Configuring your Audio Device Audio devices are much simpler to configure than they used to be thanks to the development of AppleALC. AppleALC is a kernel extension that provides native Apple audio capabilities. To use it, the first thing you will need to know is what audio codec your laptop uses. If you don't already know, or if you're unsure, you can use a Linux live USB to do a codec dump. A codec dump provides a treasure trove of information about your device and the paths it uses to connect things like internal amplifiers to speakers or headphones. Creating a Codec Dump If you do need a codec dump for whatever reason, boot from your Linux live USB and find the nearest terminal or command line. The following command will display the details of your codec on screen with a pause so you can read it. cat /proc/asound/card0/codec#0 | less The first line should provide your codec. It will look something like this: Codec: Realtek ALC294 If you would like to save the codec to a file so you can reference it again when you're back in macOS, cat it to a file instead and save the file to the boot partition of the USB drive, on another USB drive, or somewhere on your network. cat /proc/asound/card0/codec#0 > /mnt/MyOtherUSBDrive/codec.txt Now that you're familiar with your codec, let's install AppleALC. AppleALC Prerequisites If you're dual booting with Windows or Linux, you should enable the Devices/Audio/ResetHDA property which will reset the audio device on startup to flush any configuration . Installing AppleALC Installing AppleALC is simple. You just need to download the AppleALC kext from the project's release page and add the kext to Open Core Kexts. If you do add it, make sure to edit your config.plist Download AppleALC @ Github Open Core: Your new AppleALC kext path should look like it does in the tree below. EFI └── OC └── Kexts └── AppleALC.kext Before rebooting, let's configure it! Configuring AppleALC Knowing your codec makes things somewhat easier as you can look it up in the AppleALC WIKI and find all of the layouts that could work with it. AppleALC Supported Codecs If you don't find your codec listed, you might find that it's just a rebranded version of another so it wouldn't hurt to search for "AppleALC {your codec}". Once you have a list of layouts, but you don't know which is the right one you can test them one by one. Just configure the layout id in config.plist with your favorite plist editor and reboot. If audio works, congratulations! Otherwise, repeat until you've found it. Open up your plist editor and the config.plist, then browse to DeviceProperties/Add and your layout-id. None of the Layout IDs Worked! You could try using VoodooHDA instead. Using VoodooHDA VoodooHDA is an alternative to AppleALC, and it works pretty well but rather than adding native support, VoodooHDA provides its own audio solution. Installing it is pretty straightforward. Simply download the kext, preference pane, and settings loader and add them to your system. Clover: The kext goes in Clover/kexts/Other, if you have AppleALC installed you'll want to remove it. Open (execute) the preferences pane and it should prompt you to install, if it doesn't drag it onto System Preferences and it'll install that way. The settings loader should be installed to Applications, and you should run it once to enable it. Download VoodooHDA @ SourceForge Open Core: As with AppleALC, it should follow the same pattern in the tree. EFI └── OC └── Kexts └── VoodooHDA.kext >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Big Sur Missing Secure Boot Manifests <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Sometimes the already installed operating system may have outdated Apple Secure Boot manifests on the Preboot partition causing boot failure. If there is a boot message: “OCB: Apple Secure Boot prohibits this boot entry, en- forcing!”, it is likely the case. When this happens, either reinstall the operating system or copy the manifests (files with .im4m extension, such as boot.efi.j137.im4m) from /usr/standalone/i386 to /Volumes/Preboot/<UUID>/System/Library/CoreServices. Here <UUID> is the Big Sur system volume identifier. On HFS+ installations the manifests should be copied to /System/Library/CoreServices on the system volume. Find your preboot volume from terminal: diskutil list mount the Preboot volume diskutil mount diskxsy (x=disk, y=slice) CD into your Preboot volume Note the actual volume is under /System/Volumes/Preboot in macOS however in Recovery it's simply under /Volumes/Preboot cd /System/Volumes/Preboot Grab your UUID ls 46923F6E-968E-46E9-AC6D-9E6141DF52FD CD844C38-1A25-48D5-9388-5D62AA46CFB8 If multiple show up(ie. you dual boot multiple versions of macOS), you will need to determine which UUID is correct. Print the value of .disk_label.contentDetails of each volume. cat ./46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices/.disk_label.contentDetails Big Sur HD% cat ./CD844C38-1A25-48D5-9388-5D62AA46CFB8/System/Library/CoreServices/.disk_label.contentDetails Catalina HD% Copy over the secure boot files, recovery will need different commands Example commands for inside macOS Replace 46923F6E-968E-46E9-AC6D-9E6141DF52FD with your UUID value cd ~ sudo cp -a /usr/standalone/i386/. /System/Volumes/Preboot/46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices Example commands for Recovery: Replace Macintosh\ HD and 46923F6E-968E-46E9-AC6D-9E6141DF52FD with your System Volume's name and Preboot's UUID cp -a /Volumes/Macintosh\ HD/usr/standalone/i386/. /Volumes/Preboot/46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices Enable SecureBootModel and reboot. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ext Filesystem Read/Write <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< https://github.com/gpz500/fuse-ext2/releases/tag/v0.0.9-gpz501 Follow applicable directions on page, but suggest you don't automount ext volumes. Confirmed working RW for Monterey beta 1 with macFUSE 4.20. Determine your ext volume(s) with diskutil list. Make a mount point: sudo mkdir /Volumes/ext Mount the volume: sudo /usr/local/bin/fuse-ext2 -o force /dev/diskXsY /Volumes/ext -o allow_other X=disk Y=slice Softlink to desktop: sudo ln -s /Volumes/ext /Users/yourusername/Desktop/ext Make sure finder is configured to show mounted volumes on desktop. You can mount an ext volume from terminal or make an automator app that works with a double click from the desktop. A simple example for automator to mount ext volume without desktop softlink: do shell script "sudo /usr/local/bin/fuse-ext2 -o force /dev/diskXsY /Volumes/ext -o allow_other" with administrator privileges Unmount ext volume from terminal: sudo umount /dev/diskXsY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> useful links <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< posted EFIs https://github.com/topics/hackintosh?o=desc&s=updated https://github.com/loctran016/efi-database ##### FUSE for mac https://osxfuse.github.io/ https://github.com/osxfuse/osxfuse/releases ##### FUSE ext https://github.com/gpz500/fuse-ext2/releases/tag/v0.0.9-gpz501 ##### https://github.com/CloverHackyColor/CloverBootloader/releases https://github.com/CloverHackyColor/CloverThemes https://github.com/1hbb/OpenIntelWireless-Factory/releases https://github.com/ClayMoreBoy/Hackintosh-Kext-Factory/releases https://gitter.im/OpenIntelWireless/itlwm# https://non-vanilla-way.github.io/builds/?product=OpenCorePkg&viewall=true https://github.com/ic005k/QtOpenCoreConfig/releases/ https://github.com/OpenIntelWireless/itlwm/releases orig. https://github.com/1hbb/OpenIntelWireless-Factory/issues https://www.shirtpocket.com/blog/index.php/shadedgrey/comments/finally/ https://github.com/MonitorControl/MonitorControl/releases https://github.com/acidanthera/MaciASL/releases https://github.com/ITzTravelInTime/MenuBarSIPDetector/releases https://github.com/0xFireWolf/RealtekCardReader/releases https://github.com/headkaze/Hackintool/releases https://github.com/zzanehip/Safari-Experiment/releases/tag/v1.0 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> send message if you encounter broken links ===================EOF==================== EFI_Clover5137_clean.zip

For instance. Clover5131 boots Catalina 10.15.7 without issues, but KPs quickly when boo ting Big Sur, even from Preboot. However, clover boots a fresh install of Big Sur that is not modified, but once, for instance, I change the login graphic, it KPs when booting. That same Big Sur boots fine with Open Core, including any changes after fresh install. Why is that? This is unexplained. It logically follows thathere must be some particular modification to the config.plist or other component of clover to cause it to boot Big Sur without errors/panics. The guide appears to be basic but does not appear to address this issue. That is why I have asked for a working EFI. Do you have a clover EFI that will boot Big Sur on HP skylake 520/sunrise point 100 laptop?

Guide is not specific to requirements for HP laptop -Clover Vanilla Guide https://www.olarila.com/topic/5794-hackintosh-guide-install-macos-with-vanilla-olarila-image-step-by-step-install-and-post-install-windows-linux-or-mac/

Does anyone have a booting clover EFI 5127+ for HP skylake/520 laptop w/Big Sur. Does clover's LAPIC fix work for Big Sur or is there a workaround? Essential to boot Big Sur from preboot? Is DSDT necessary? What is correct csr-active-config? Do kexts have to be added to S/L/E or L/E to run Big Sur SIP enabled in both clover and Open Core? Clover 5128 works fine for Catalina but almost immediate KP for Big Sur. Thanks for any pointers/help.

Have read recently on Gitter forum for itlwm that Intel 3165 wifi no longer working. kittummi2@kittummi2 Nov 29 07:48 itlwm.kext is not working for intel 3165,7265 dell wireles 1707 Qualcomm 9565 , Qualcomm QCA61x4A, QCA9377 WiFi Drivers please can anyone fix this issue Anyone with working Open Core using itlwm/Heliport or AirportItlwm and intel 3165 m.2 wifi please post your working EFi and any configs to enable Heliport to scan and show/connect to displayed networks. Itlwm and Heliport work fine in Catalina with Clover 5122. Both itlwm/Heliport and AirportItlwm fail to display networks in Catalina 10.5.7 and Big Sur 11.0.1 20B29 when loaded with Open Core 0.6.4. Please message me if you need more info. Update 091220: Resolved with firmware update. Thank you.

itlwm/AirportItwlm/Heliport.app working in BS beta, stop in release 20B29. Open Core 0.6.4 not loading AirportItlwm.kext. kextstat show AirportItwlm and IO80211Family.kext not loaded. csrutil status and csrutil authentiated-root status in recovery terminal both show disabled but will not toggle to enabled. What is correct csr-active-config value for Open Core 0.6.3/0.6.4 with Big Sur 11.0.1 20B29? Clover is loading the intel kexts but Open Core fail to load in both Catalina and Big Sur? Is this an Open Core issue, a csr-active-config issue? Any help appreciated.

Anyone have atheros wifi 9565/Dell 1707 working on DP7? Shows in menu bar scanning but not finding APs. Can someone post kexts/firmware/config for OC? Thanks for any help.

Some updated tips and observations concerning Big Sur 11.4 installation to an available APFS HDD container/partition. Assumes an existing working ESP bootloader. System file modifications are made in recovery terminal with SIP disabled (csrutil disable and csrutil authenticated-root disable) Any changes to the system files in recovery console require creating a new shapshot to be retained. 1. Go ahead and make your USB installer with Open Core or Clover, but if you have an existing install of Catalina you can save time by starting the Big Sur installer directly from Catalina, choosing the target partition, and letting the installer copy over the install files rather than waiting on USB to boot and copy. You can then use the USB installer to reboot Big Sur as required to complete the installation. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bootmanagers and bootloders and partitioning <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< A warning about partitioning. There are numerous well known third party partitioning programs, including those running on windows, that can alter the partiton table in such a way as to render your APFS containers unrecognizable and unbootable. Whenever possible use the mac OS Disk Utility to do your partitoning, and do so after you have backed up your partition table with a suitable utility. One such free utility for linux is sgdisk. You can boot a live linux distro from USB, and backup/restore your hard drive (example: /dev/sda) GPT partition table to/from USB media as follows: backup: sudo sgdisk --backup=/path/to/USB/sda_partition_table_01.01.2021 /dev/sda restore: sudo sgdisk --load-backup=/path/to/USB/sda_partition_table_01.01.2021 /dev/sda 2. If you are a linux multi-booter and using GRUB2 as your main bootloader, and if you have an existing Catalina install with a working chainloaded Open Core or Clover, suggest you don't disturb/break your existing bootloader by making tweaks for Big Sur. You can make an additional small 200MB FAT32 partition on your HDD and put your Big Sur bootloader there. Note that if you choose to use clover you can directly chainload from GRUB2 by adding this entry to your grub.cfg file (where xxxx-xxxx is your Big Sur bootloder partition from "lsblk -f" or "sudo blkid" terminal output in Linux): menuentry "Clover"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/CLOVER/CLOVERX64.efi # or whatever path you use } With Open Core version 0.6.4 and earlier chainloading from GRUB2 was relatively simple with grub.cfg menu entry: menuentry "Open_Core"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/OC/OpenCore.efi # or whatever path you use } It now appears that Open Core 0.6.5 and newer have undergone code change that prevents directly chainloading OpenCore.efi from GRUB2. However, if you want to continue to use GRUB2 as your main ESP bootloader, you can work around this issue by installing Refind 0.13.2 to the same ESP with GRUB2 and chainload to Refind in grub.cfg with the following menu entry (where xxxx:xxxx is your ESP UUID}: menuentry "refind"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/refind/refind_x64.efi } You can launch Open Core from the Refind GUI. Here is a sample refind.conf that should chainload Open Core (where xxxx is the volume name or UUID name of your Open Core partition): menuentry "OpenCore" { icon /EFI/refind/icons/youricon.png volume xxxx loader /EFI/OC/OpenCore.efi options "-v" } When chainloading Open Core from Refind you may have to change the Vault configuration in Open Core config.plist from Secure to Optional. This chainloading is an extra step but it preserves GRUB2 as the main bootloader and facilitates use of newer Open Core versions. Note that you can install GRUB2, Refind, Open Core and the windows 10 bootloader bootmgfw.efi all on the ESP or you can install Open Core to a separate partition in order to edit/tweak your Big Sur bootloader settings without breaking an existing working ESP bootloader. When editing config.plist files, if you are not comfortable using an XML editor, and you have Catalina installed, you can download ProperTree from github and launch it from Catalina. For Linux multibooters, you can modify your linux /etc/grub.d/40_custom to include any custom bootloader menu entries you want to keep, and then run update-grub from within Linux. Using GRUB2 to chainload windows 10 in EFI mode. Make sure that both secure boot and TPM are disabled in BIOS Hide TPM in BIOS config. Verify that windows was installed in EFI mode or has been configured after the install to boot in EFI mode. Ensure that GRUB2 in your BIOS EFI config is your default boot selection. Migrate the windows 10 boot files including BCD files to the main Windows partition as they are not there by default. Verify that your machine is booting in EFI mode and not CSM. Verify that your EFI boot partition has "boot" and "ESP" flags set. Make sure you shut down windows while holding down the shift key until completely shut down. As an example, using a single hard drive for all of your OS's, your GRUB2 grub.cfg windows 10 boot entry should look similar to the configuration below where xxxx-xxxx represents the UUID of the windows 10 partition, where the "x" in sdax represents the linux GRUB2 number of your ESP (with /efi/Microsoft/Boot/bootmgfw.efi), where the "x" in hdx and ahcix represents the GRUB2 hard drive number of the windows 10 installation, and where the "x" in gptx represents the GRUB2 partition number of the windows 10 installation. GRUB2 numbers hard drives starting with 0, and partitions starting with 1. Examples: /dev/sda1, hd0,gpt3, ahci0,gpt3. menuentry 'Windows Boot Manager (on /dev/sdax)' --class windows --class os $menuentry_id_option 'osprober-efi-xxxx-xxxx' { insmod part_gpt insmod fat set root='hdx,gptx' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hdx,gptx --hint-efi=hdx,gptx --hint-baremetal=ahcix,gptx xxxx-xxxx else search --no-floppy --fs-uuid --set=root xxxx-xxxx fi chainloader /efi/Microsoft/Boot/bootmgfw.efi } 3. When your install is finished and you are finally at the working desktop, you may want to make a backup. With Catalina this was easily done by using Disk Utility from a bootable USB installer to restore to an APFS formatted backup media. The Big Sur Disk Utility ASR has repeatedly failed to replicate (bootable) Big Sur and it appears Disk Utility from Catalina 10.15.7 can not perform this task with Big Sur APFS containers. You can, however, use third party freeware other than dd to make a sector by sector clone of the entire Big Sur container onto removable media. Alternatively, depending on the size of your AFPS container/partition and transfer rate, using dd can take quite a long time to do the backup. If you clone to USB media and then boot the clone to test the backup on the same computer from which it was made, both the Big Sur USB clone and the Big Sur HDD container installation show up within disk utility, in the USB media area. The clone will have the same UUIDs. 4. If your Open Core keyboard language is not properly configured the recovery console language may default to Chinese or some other language. To avoid this make sure your keyboard language is specified in Open Core NVRAM section of the config.plist. Recovery terminal is available for system file changes. The mount command within recovery terminal will show volumes. You can then run: diskutil mountDisk diskXsY (where x is the number of your Big Sur disk and y is the read-only slice from the mount command output). You can then run: mount -uw /Volumes/thenameofyourBigSurvolume (not Data volume) to make the normally read-only volume writable. Make any desired system file changes from the console and reseal (where X is your Big Sur volume name shown with mount command): bless --folder /Volumes/X/System/Library/CoreServices --bootefi --create-snapshot Reboot. 5. If you have an existing Catalina installation with brew and numerous brew installed programs such as ntfs-3g, you can directly copy the brew files/programs (usr/local) to the corresponding file system locations within Big Sur and if necessary, manually create the soft links to enable programs. If you need to write to the system file tree you can do this from the recovery console as previously referenced. NTFS volumes will normally mount read-only but read-write can be enabled if the installed /sbin/mount_ntfs supports read/write: From terminal make a mount point of your choice for each ntfs volume. Example: sudo mkdir ~/ntfs Unmount the target read-only ntfs volume where x is disk number and y is slice: sudo umount /dev/diskxsy Mount ntfs volume as read-write: sudo mount -t ntfs -o rw,auto,nobrowse /dev/diskxsy ~/ntfs Link to desktop: sudo ln -s ~/ntfs ~/Desktop/whatever_name_you_choose Make sure finder is configured to show mounted volumes on the desktop. Keep in mind that if you use ntfs-3g with osxfuse to automount ntfs volumes, install version 4.1.0 or later of macFUSE. You may have to copy the ntfs-3g mount_ntfs binary directly to /sbin using recovery console. Note that brew's ntfs-3g 2017.3.23_3 has previously failed to mount NTFS volumes with all files and folders visible. You can use a prior Catalina Version, although it may be necessary to copy mount_ntfs directory to sbin. https://osxfuse.github.io/ Any changes made to system files in recovery console should be followed by creating a new shapshot: bless --folder /Volumes/x/System/Library/CoreServices --bootefi --create-snapshot (where X is your Big Sur volume name shown with mount command. Here are some post-install terminal tweaks/info for zsh. If you do not know what they do, don't use them: defaults write NSGlobalDomain NSDocumentSaveNewDocumentsToCloud -bool false defaults write com.apple.finder AppleShowAllFiles TRUE defaults write com.apple.TextEdit RichText -int 0 defaults write com.apple.finder _FXShowPosixPathInTitle -bool YES sudo defaults write /.Spotlight-V100/VolumeConfiguration Exclusions -array "/Volumes" sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist defaults write com.apple.desktopservices DSDontWriteUSBStores -bool true defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true sudo mdutil -i off -d /Volumes/whatevervolumename (Disable Indexing AND Searching of specified Volume) sudo mdutil -a -i off top -o CMPRS top -o MEM 6. If you have an existing Catalina installation with third party programs they may work without modification by copying them directly from Catalina Applications folder to the Big Sur Applications folder AND copying the corresponding entries for those programs from Catalina ~/Library/Application Support to Big Sur ~/Library/Application Support. Note that ~/Library/Application Support refers to Users/yourusername/Library/Application Support. 7. A suitable Open Core NVRAM csr-active-config value to receive software updates with a supported hardware profile is 67080000. 8. Automator utility can create an apple script or shell script app for Big Sur but it may fail with error message when run from the desktop if absolute paths are not specified within the script. Test by opening the app in automator and click the step button and see if the app executes with the desired result. Test by running the command line directly within the zsh terminal. 9. The attached EFI with OC was modified for Skylake/520/Sunrise Point but you may find that it works for a range of models with similar Intel hardware. Supply your own Platforminfo. If you multi-boot with linux you can run lspci -k from terminal in linux to show your pci hardware configuration. The EFI attachment may be omitted from the post due to upload limitations. 10. If you desire an Open Core GUI, change the config.plist PickerMode specification from BuiltIn to External and make sure you have the required Resources installed for your version of Open Core. Set the applicable resolution for Open Core or all icons may not be completely visible. Change HideAuxiliary to true if you do not want to see recovery. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 11. Removing old/unwanted snapshots. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Boot into recovery mode and disable SIP: csrutil disable/csrutil authenticated-root disable. Reboot into recovery mode if necessary. Run the mount command to see your Big Sur partition name and disk/slice. In terminal type: diskutil mount /dev/diskXsY and hit enter (where X and Y are your Big Sur disk and slice) then type: mount -uw /Volumes/X and hit enter (where X is your Big Sur volume name) Your Big Sur volume should now be read-write. Run: bless --folder /Volumes/x/System/Library/CoreServices --bootefi --create-snapshot (and hit enter to generate a new snapshot) Now you can remove old/unwanted snapshots. diskutil apfs listSnapshots diskXsY for a list of snapshots/uuids delete unwanted snapshots one at a time: diskutil apfs deleteSnapshot diskXsY -uuid (the snapshot uuid you want to delete) How to name snapshots and make bootable snapshots from recovery console: Create a new APFS snapshot: /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -s "you_pick_name" -v /Volumes/your_Big_Sur_volume_name Second, make it bootable: /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "you_pick_name" -v /Volumes/your_Big_Sur_volume_name >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 12. Change the Big Sur login background. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Boot into recovery mode with SIP/authenticated-root disabled. From prompt run: cd / cd into the desktop pictures folder (where X represents the name of your Big Sur install volume) cd /Volumes/X/System/Library/Desktop\ Pictures The default Big Sur login background in Desktop Pictures is Big Sur Graphic.heic. You can optionally save this graphic by typing: mv /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur\ Graphic.heic /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur\ Graphic.heic.orig Create a symlink to the desired login graphic....using Big Sur.heic as an example: ln -s /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur.heic /Volumes/X/System/Library/Desktop\ Pictures/Big\ Sur\ Graphic.heic Run: bless --folder /Volumes/x/System/Library/CoreServices --bootefi --create-snapshot Reboot. Due to a glitch in Big Sur you make occasionally reboot with your prior login background if you do not remove the snapshot that contained it. Once you have altered the installation snapshot ensure that your csr-active-config will allow booting. A suitable value for Open Core is 67080000, and for clover 0x867. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 13. Memory and Swap. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Note if you disable swap without enough memory your machine may freeze or slow to a crawl. The risk/performance tradeoff is up to you. turn off swap: sudo launchctl unload -wF /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist re-enable swap: sudo launchctl load -wF /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist delete swap: sudo rm /private/var/vm/swapfile* for those who have nvram.plist: search for swap enabled: nvram.plist vm_compressor=4 or swap disabled: nvram.plist vm_compressor=2 view swap status: sysctl -a vm.compressor_mode nvram config to enable swap: sudo nvram boot-args="vm_compressor=4" disable swap: sudo nvram boot-args="vm_compressor=2" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 14. Disabling Sleep/Hibernation <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< check state: sudo pmset -g | grep hibernatemode disable: sudo pmset -a hibernatemode 0 remove file to reclaim space: sudo rm /private/var/vm/sleepimage in /private/var/vm/ make a dummy: sudo touch /private/var/vm/sleepimage prevent write access to it: sudo chmod 000 /private/var/vm/sleepimage sudo chflags schg /private/var/vm/sleepimage >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 15. Manually install kexts to System/Library/Extensions. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< You need to enter recovery mode, open terminal, type at prompt csrutil status hit enter verify response is "disabled" if not, run at prompt: csrutil disable type at prompt csrutil authenticated-root status hit enter verify response is "disabled" if not run at prompt: csrutil authenticated-root disable reboot into recovery mode if required open terminal, at prompt run: mount hit enter verify volumes, disk numbers, slices. confirm with: diskutil list at prompt type: diskutil mountDisk diskXsY where X is the Big Sur disk number and Y is the Big Sur slice. hit enter at prompt type: mount -uw /Volumes/your Big Sur volume name hit enter at prompt type: mount hit enter Your Big Sur volume should no longer indicate read-only at prompt: cp -r where/ever/your/kext/is/whatever.kext /Volumes/your Big Sur volume name/System/Library/Extensions hit enter for each kext: at prompt: chown -R 0:0 /Volumes/your Big Sur volume name/System/Library/Extensions/target.kext && chmod -R 755 /Volumes/your Big Sur volume name/System/Library/Extensions/target.kext hit enter then type at prompt: touch /Volumes/your Big Sur volume name/System/Library/Extensions && kmutil install --volume-root /Volumes/your Big Sur volume name --update-all --force hit enter, wait for finish then type at prompt: /Volumes/your Big Sur volume name/usr/sbin/kcditto hit enter, wait for finish then type at prompt: bless --folder /Volumes/your Big Sur volume name/System/Library/CoreServices --bootefi --create-snapshot hit enter, wait for finish reboot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16. some intel wifi info <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Lilu.kext should load first and -lilubetaall in boot arguments in config.plist. Use either Itlwm.kext with Heliport.app OR AirportItlwm.kext. Don't load both Itlwm.kext and AirportItlwm.kext. Itlwm.kext version 1.2.0 has worked well with Catalina and Big Sur when used in conjunction with the Heliport.app. If you have both Catalina and Big Sur installed and prefer to use AirportItlwm.kext, you can rename one of them (example: Catalina version renamed to AirportItlwm2.kext) and inject them with Open Core by specifying MinKernel and MaxKernel versions in the config.plist to load the appropriate kext based on whether Catalina or Big Sur is booting. Useful links: https://github.com/1hbb/OpenIntelWireless-Factory/releases https://github.com/ClayMoreBoy/Hackintosh-Kext-Factory/releases >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Audio config <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< The following information excerpted from the web may help you: For Open Core: Suggest you use AppleALC and modify the Open Core config.plist to show the layout-id for your audio. Don't use the kernel switch method for Open Core. Configuring your Audio Device Audio devices are much simpler to configure than they used to be thanks to the development of AppleALC. AppleALC is a kernel extension that provides native Apple audio capabilities. To use it, the first thing you will need to know is what audio codec your laptop uses. If you don't already know, or if you're unsure, you can use a Linux live USB to do a codec dump. A codec dump provides a treasure trove of information about your device and the paths it uses to connect things like internal amplifiers to speakers or headphones. Creating a Codec Dump If you do need a codec dump for whatever reason, boot from your Linux live USB and find the nearest terminal or command line. The following command will display the details of your codec on screen with a pause so you can read it. cat /proc/asound/card0/codec#0 | less The first line should provide your codec. It will look something like this: Codec: Realtek ALC294 If you would like to save the codec to a file so you can reference it again when you're back in macOS, cat it to a file instead and save the file to the boot partition of the USB drive, on another USB drive, or somewhere on your network. cat /proc/asound/card0/codec#0 > /mnt/MyOtherUSBDrive/codec.txt Now that you're familiar with your codec, let's install AppleALC. AppleALC Prerequisites If you're dual booting with Windows or Linux, you should enable the Devices/Audio/ResetHDA property which will reset the audio device on startup to flush any configuration . Installing AppleALC Installing AppleALC is simple. You just need to download the AppleALC kext from the project's release page and add the kext to Open Core Kexts. If you do add it, make sure to edit your config.plist Download AppleALC @ Github Open Core: Your new AppleALC kext path should look like it does in the tree below. EFI └── OC └── Kexts └── AppleALC.kext Before rebooting, let's configure it! Configuring AppleALC Knowing your codec makes things somewhat easier as you can look it up in the AppleALC WIKI and find all of the layouts that could work with it. AppleALC Supported Codecs If you don't find your codec listed, you might find that it's just a rebranded version of another so it wouldn't hurt to search for "AppleALC {your codec}". Once you have a list of layouts, but you don't know which is the right one you can test them one by one. Just configure the layout id in config.plist with your favorite plist editor and reboot. If audio works, congratulations! Otherwise, repeat until you've found it. Open up your plist editor and the config.plist, then browse to DeviceProperties/Add and your layout-id. None of the Layout IDs Worked! You could try using VoodooHDA instead. Using VoodooHDA VoodooHDA is an alternative to AppleALC, and it works pretty well but rather than adding native support, VoodooHDA provides its own audio solution. Installing it is pretty straightforward. Simply download the kext, preference pane, and settings loader and add them to your system. Clover: The kext goes in Clover/kexts/Other, if you have AppleALC installed you'll want to remove it. Open (execute) the preferences pane and it should prompt you to install, if it doesn't drag it onto System Preferences and it'll install that way. The settings loader should be installed to Applications, and you should run it once to enable it. Download VoodooHDA @ SourceForge Open Core: As with AppleALC, it should follow the same pattern in the tree. EFI └── OC └── Kexts └── VoodooHDA.kext >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Big Sur Missing Secure Boot Manifests <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Sometimes the already installed operating system may have outdated Apple Secure Boot manifests on the Preboot partition causing boot failure. If there is a boot message: “OCB: Apple Secure Boot prohibits this boot entry, en- forcing!”, it is likely the case. When this happens, either reinstall the operating system or copy the manifests (files with .im4m extension, such as boot.efi.j137.im4m) from /usr/standalone/i386 to /Volumes/Preboot/<UUID>/System/Library/CoreServices. Here <UUID> is the Big Sur system volume identifier. On HFS+ installations the manifests should be copied to /System/Library/CoreServices on the system volume. Find your preboot volume from terminal: diskutil list mount the Preboot volume diskutil mount diskxsy (x=disk, y=slice) CD into your Preboot volume Note the actual volume is under /System/Volumes/Preboot in macOS however in Recovery it's simply under /Volumes/Preboot cd /System/Volumes/Preboot Grab your UUID ls 46923F6E-968E-46E9-AC6D-9E6141DF52FD CD844C38-1A25-48D5-9388-5D62AA46CFB8 If multiple show up(ie. you dual boot multiple versions of macOS), you will need to determine which UUID is correct. Print the value of .disk_label.contentDetails of each volume. cat ./46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices/.disk_label.contentDetails Big Sur HD% cat ./CD844C38-1A25-48D5-9388-5D62AA46CFB8/System/Library/CoreServices/.disk_label.contentDetails Catalina HD% Copy over the secure boot files, recovery will need different commands Example commands for inside macOS Replace 46923F6E-968E-46E9-AC6D-9E6141DF52FD with your UUID value cd ~ sudo cp -a /usr/standalone/i386/. /System/Volumes/Preboot/46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices Example commands for Recovery: Replace Macintosh\ HD and 46923F6E-968E-46E9-AC6D-9E6141DF52FD with your System Volume's name and Preboot's UUID cp -a /Volumes/Macintosh\ HD/usr/standalone/i386/. /Volumes/Preboot/46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices Enable SecureBootModel and reboot. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> useful links <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< https://github.com/topics/hackintosh?o=desc&s=updated https://github.com/CloverHackyColor/CloverBootloader/releases https://github.com/1hbb/OpenIntelWireless-Factory/releases https://github.com/ClayMoreBoy/Hackintosh-Kext-Factory/releases https://gitter.im/OpenIntelWireless/itlwm# https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true https://github.com/ic005k/QtOpenCoreConfig/releases/ https://github.com/OpenIntelWireless/itlwm/releases orig. https://github.com/1hbb/OpenIntelWireless-Factory/issues https://osxfuse.github.io/ https://www.shirtpocket.com/blog/index.php/shadedgrey/comments/finally/ https://github.com/topics/hackintosh?o=desc&s=updated posted EFIs

Thanks, MaLdOn for all the work and posts that go into your site. It has helped a lot, especially your catalina iso. Big Sur is a lot harder to boot. Have tried the EFI PREMADE CLOVER from your EFI page, but was not able to boot DP4 with it. Alternatively, tried to modify clover with the bootx64.efi and cloverx64.efi/QcQuirks/OpenRuntime.efi but that also would not boot DP4. Also tried using the SSDT-OLA.aml but that did not prevent boot hang or KP. The CLOVER.NOTEBOOKS.100.200.300 and OPENCORE.NOTEBOOKS.100.200.300 EFIs from your EFI page appear to be for booting pre-Big Sur. Have HP laptop/Skylake/i5/520/sunrise. Lapic and UnblockFsConnect enabled for OC, but boot fails with KP. Have also found that OC with VirtualSMC freezes the boot, but FakeSMC appears to boot further but also fails with KP. Not sure if KP issue is specific to HP laptops/if doing something wrong. Have followed Skylake OC tutorial, Catalina booting fine. Have included a txt file OC generates with KP. Would an lspci -k from linux help? If there are special configs for OC or Clover on HP laptop please tell me what needs to be done for booting BS DP4 installer. Thank you. ola.zip

Does anybody have a solution to get an m.2 wifi DW1707 atheros 9565 working? Card has Japan country code and scans when turned on but does not detect wifi networks. Using correctly modified atheros 40 kext in S/L/E with correct permissions. Menu bar wifi applet show device detected but network applet has yellow indicator. So far forums do not have a solution for me. Any help appreciated.

System volume in Catalina is RO while running even with SIP disabled. You can boot into a second mac OS install such as Mojave and write to the Catalina system and/or Data volumes. Keep in mind that if you use Mojave that disk utility does not have exactly the same functionality as the Catalina version. Better if you have a bootable backup of Catalina to do mods. Use a bootable Catalina USB installer/disk utiility to clone your Catalina install to something inexpensive such as an SD card via a USB reader/writer. SIze matters. A 32 gig or larger SD card should have enough room for future updates and it is better if your backup is only one APFS container with only Catalina installed. Booting from a Catalina SD backup is not as fast as hard drive but gets the job done. Use USB 2 SD card reader/writer to avoid issues with unsupported hardware/specs.

I-5 Skylake/520 graphics/4gig RAM/UEFI boot/GPT Any one had issues with supplemental updates and/or security updates booting very slowly after install and using approx. 750 more megs of memory? This has happened with recent updates to Catalina 10.15.1, Mojave security update 2019-001, and High Sierra security update 2019-006. I know that the first reboot after updates is usually slow but this problem with slow booting and hard drive thrashing persists after multiple reboots. It seems as though hard drive access is being channeled though a buffer. In one instance Catalina paused for a long time on reboot and a message appeared indicating that enough information had been found to re-enable the soft bloc. afterward Catalina booted normally but Mojave was booting so slow that it was practically unusable. After multiple reboots High sierra takes around a minute for the desktop to fully initialize after the login, but it was usable. Does mac os use some kind of software input-output hard disk buffer that can be manually reset from the terminal? Disabling/enabling virtual memory paging seems to have no effect and the vm compressor mode is set to 2. The laptop only has 4 gig of memory but this has been enough to run all three os without boot issues in the past. Catalina on APFS, Mojave and High Sierra on H FS+. Any help appreciated

I-5 Skylake/520 graphics/4gig RAM/UEFI boot/GPT Any one had issues with supplemental updates and/or security updates booting very slowly after install and using approx. 750 more megs of memory? This has happened with recent updates to Catalina 10.15.1, Mojave security update 2019-001, and High Sierra security update 2019-006. I know that the first reboot after updates is usually slow but this problem with slow booting and hard drive thrashing persists after multiple reboots. It seems as though hard drive access is being channeled though a buffer. In one instance Catalina paused for a long time on reboot and a message appeared indicating that enough information had been found to re-enable the soft bloc. afterward Catalina booted normally but Mojave was booting so slow that it was practically unusable. After multiple reboots High sierra takes around a minute for the desktop to fully initialize after the login, but it was usable. Does mac os use some kind of software input-output hard disk buffer that can be manually reset from the terminal? Disabling/enabling virtual memory paging seems to have no effect and the vm compressor mode is set to 2. The laptop only has 4 gig of memory but this has been enough to run all three os without boot issues in the past. Catalina on APFS, Mojave and High Sierra on H FS+. Any help appreciated.

Thanks Maldon, resolved with your laptop config.plist. HP 250 G5/Skylake/I5-6200U/520. Essentials.zip