dredhorse Posted August 28, 2022 Share Posted August 28, 2022 (edited) Hi, Posting it here because it is kind of a multiboot issue: 3 discs... 1 main macos, 1 windows, 1 backup macos catalina and opencore 0.6.9 Updated EFI of backup macos to latest OC with OC auxillary... did work.. was able to update the backup macos to monterey booting from the second efi doesn't show my main macos (samsung evo 970 plus) booting from the first efi does show both macos After reading a lot I thought perhaps I should swap the samsung and so I bought a new drive... removed the partitions from the second drive and copied my main drive over again booting from the first efi I see both macos, and can boot into both booting from the second efi I only see windows now... replaced the full second efi folder onces, still same issue. Any idea? Edited August 28, 2022 by fantomas Hi ! Hi ! Hi ! Link to comment Share on other sites More sharing options...
dredhorse Posted August 29, 2022 Author Share Posted August 29, 2022 and here are both EFI, first EFI 0.6.9.zip and second, perhaps somebody has an idea EFI 0.7.8.zip Link to comment Share on other sites More sharing options...
Anto65 Posted August 29, 2022 Share Posted August 29, 2022 Try ... Updated to ver. 0.8.3 (don't forget to rename it to "EFI") You should boot with a single EFI (Remove others from disks) EFI 0.6.9>0.8.3.zip 1 Link to comment Share on other sites More sharing options...
dredhorse Posted August 29, 2022 Author Share Posted August 29, 2022 (edited) thanks, will try tomorrow... Single EFI is an issue... I use it as backup if my original one breaks or to try out upgrade... which has proven invaluable again this time. BTW: what did you change? Edited August 29, 2022 by dredhorse Link to comment Share on other sites More sharing options...
Anto65 Posted August 29, 2022 Share Posted August 29, 2022 Of course, always have a backup copy (saved in documents or on the usb) ... i didn't mean erase that ... just use a single EFI to boot the disks ... reset the nvram before booting 1 Link to comment Share on other sites More sharing options...
dredhorse Posted August 31, 2022 Author Share Posted August 31, 2022 this works.. thanks... could you tell me what you did? Only use a newer version of OC and drivers or more? I try to compare the two configs but couldn't directly see a difference. Link to comment Share on other sites More sharing options...
makk Posted November 18, 2022 Share Posted November 18, 2022 @antuneddu reading through this build you made, I see no NVMe Driver. Does the new versions of OC incorporate the NVMe and therefore no need to use NvmeExpressDxe.efi? I've always used NvmeExpressDxe.efi Link to comment Share on other sites More sharing options...
1Revenger1 Posted November 18, 2022 Share Posted November 18, 2022 NvmeExpressDxe.efi is only needed on systems which can't natively boot from NVMe drives. Most systems already have a similar driver in their firmware, and really only need HFSPlus.efi and OpenRuntime.efi. 2 Link to comment Share on other sites More sharing options...
makk Posted November 18, 2022 Share Posted November 18, 2022 (edited) 31 minutes ago, 1Revenger1 said: NvmeExpressDxe.efi is only needed on systems which can't natively boot from NVMe drives. Most systems already have a similar driver in their firmware, and really only need HFSPlus.efi and OpenRuntime.efi. @1Revenger1 Great news. I was under the impression needed it for OC to boot NVME due to the bug in the past with OS. Thanks I can take it off. What bout the Kext? {{ NVMeFix.kext }} On a side note while you're on here, I'm not having success with Windows disklabel for the Boot Menu Icon. I've tried several ops and no luck. I'm not sure what how to troubleshoot this. Any suggestions to finding the cause? Thank you Edited November 18, 2022 by makk Link to comment Share on other sites More sharing options...
Recommended Posts