![]() ![]() For a new installation of macOS, you MUST erase and format the destination drive according to the following steps before continuing.(If you have issues reaching the installer, you can use the spacebar on the boot screen to enter alternate boot modes such as verbose and safe mode.)Īt Clover boot screen, choose Boot Install macOS Catalina from myVolume.assign leterO Now, open Windows Explorer and you should see your EFI partition is mounted there. In the top menu bar choose Utilities and open Disk Utility b. Highlight your target drive for the Mojave installation in the left column. c. Close Disk UtilityWhen the installer asks you where to install, choose Catalina For Name: type MacintoshHD (You can rename it later) e. Upon completion, the system will automatically restart. ![]() Press the hotkey to choose boot device (F12 for Gigabyte mobo), Choose USB At the Boot Screen, choose Boot macOS from MacintoshHD Complete macOS installation. Clover is one of bootloaders developed by Slice, Apianti, BlackOSX, Dmazar, Blusseau, and other devs with great community for booting OS X, Windows and Linux on Mac or PC with UEFI / BIOS firmware.GUI Custom Entries Arguments initrd=/initramfs-linux.img root=UUID=d4f1e3b7-b466–4c1b-991c-90fa99cafbc6 rw add_efi_memmap Disabled FullTitle Arch Linux Hidden Ignore Path vmlinuz-linux Type Linux Volume EFI VolumeType Internal.Scroll to the GUI Section and add the Following Code in Custom Boot Entries.( make sure you backed up your EFI Folder before Continuing) Open your favorite plist editors like plistEdit Pro or Whatever.The system will automatically reboot.Ĭomplete the Post-Installation and Setup the EFI Drive. Moreover, from Windows 11 installation media filesystem I'm able to trigger cdboot.efi (prompts to press any key, quits after that's done) and cdboot_noprompt.Go to GUI Section from the Left Sidebar. efi files that seem to work using regular F10 and selection. "Nothing" -> EFI shell goes to newline and nothing happens, seems to correlate with "flash" behaviour efi files I get either:Ĭommand Error Status: Unsupported # probably files that aren't really compatible with UEFI, e.g. Also UUID doesn't seem to match anything. UPDATE2: I can see "Windows Boot Manager" entry in efibootmgr but not in UEFI boot menu. Is it possible it's some bug in UEFI that doesn't work with Windows? It's able to boot on NUC using purely UEFI mode (systemd-boot as a bootloader). UPDATE: Swapped yet another drive, SATA SSD, this time with Arch Linux installed. I'm unhappy to report that my FAT32-formatted, Windows 11-host MS tool created Windows 11 bootable USB stick (not using Rufus or any other shenanigans) is still "flashing" after getting selected.Ĭan boot in legacy mode but like I said, not really my goal. flashing) unless Arch USB is used, then I get Image Authorization Fail (again, expected). ![]() Just for clarity - no Secure Boot enabled on NUC either, not that it matters that much.īehaviour with it is still the same (i.e. Let me know if you need any more details about it vs the other USBs/OS.Īside from the existing SSD I was able to confirm other SSD and USBs boot on other UEFI boards (intel-based: Z97 and AMD-based: X570, both ASRock if that matters). I think it might have been dd'd from the img/iso years ago. Now, for some reason it does boot to Arch Linux archiso just fine using UEFI on generic USB 2.0 thumb-drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |