OpenCore General Discussion

[Matgen84]

11 hours ago, Max.1974 said:

With Clover all fine with @chris1111 themes, im not test all Linux icons but everething im test is fine 

@Max.1974 Right @chris1111 themes works fine for all linux with Clover (except there are some distros os_ missing like Manjaro or mx-linux for example, in source). My issues cames from Opencore or Linux itself (multiboot between Debian based and Arch Linux) ? 

My deal is to have multiboot linux distros on a specific hard drive, and macos on another disk. 

Edited April 14, 2024 by Matgen84

[Max.1974]

Yes nice my friend @Matgen84 i've have been used Fedora Workstation 39 and its amazing project from Linux Fedora Team. Much advanced then macOs in many aspects, included editor to images, my tools from Certisign signature and the challenge now is try Compile Clover on Linux, just for knowledge and im surprise with so many resources from  Linux Fedora, very easy to use, and thousands of programs.

 

God bless you!!

 

Spoiler

 

[ameenjuz]

ExFAT Volumes grayed out on macOS Sonoma on recovery mode in diskutility

because exfat natively supported file system why do not show on recovery mode under diskutility

working fine in normal use but not mountable in diskutility 

anyone guide me and fix

[Slice]

10 hours ago, ameenjuz said:

ExFAT Volumes grayed out on macOS Sonoma on recovery mode in diskutility

because exfat natively supported file system why do not show on recovery mode under diskutility

working fine in normal use but not mountable in diskutility 

anyone guide me and fix

I am not sure but I may propose that the exfat.kext is not present in cache in recovery mode. Consider a way to inject it by a bootloader.

[ameenjuz]

Just now, Slice said:

I am not sure but I may propose that the exfat.kext is not present in cache in recovery mode. Consider a way to inject it by a bootloader.

thanks for replying i will try to inject using bootloader

[deeveedee]

On 12/18/2023 at 1:55 PM, deeveedee said:

I have performed a few brief tests with Open Core 0.9.7 (upgraded from OC 0.9.6) on my Dell Latitude E6410 (SMBIOS MBP6,2) and am finding that I can only boot with OC 0.9.7 if  I use the LegacyBoot utility from OC 0.9.6.  Is anyone else finding this? 

 

I am hopeful that the OC OpenDuet issues that I've experienced since OC 0.9.7 are resolved in the next release of OC.  The fix "Fixed problem loading non-firmware runtime drivers" seems promising.

[Stefanalmare]

8 hours ago, deeveedee said:

 

I am hopeful that the OC OpenDuet issues that I've experienced since OC 0.9.7 are resolved in the next release of OC.  The fix "Fixed problem loading non-firmware runtime drivers" seems promising.

 

I tried, same problem.

[mhaeuser]

12 hours ago, Stefanalmare said:

 

I tried, same problem.

Well, define “tried”, this is a multi-step fix that requires latest AUDK as well. OpenDuet should work just fine again, except for NOOPT, which is still being worked on.

[Stefanalmare]

9 hours ago, mhaeuser said:

Well, define “tried”, this is a multi-step fix that requires latest AUDK as well. OpenDuet should work just fine again, except for NOOPT, which is still being worked on.

 

Since OC 0.9.7, duet doesn't work for me. Some of OC I builded myself, others I downloaded. I use duet in 4-5 legacy rigs. With some version it don't boot at all with an error message, others boot but after drive selection, black screen and back to OC picker (last OC has this behaviour). It is true that I don't used debug version and I don't compiled myself the last OC. Next week I'll investigate more and give feedback, since I'm not at home.

[chris1111]

No issue Compilling OC myself Xcode 15.4 in macOS Sonoma 14.5 Beta (23F5064f)

Spoiler

 

Booting macOS Sonoma with Duet-OpenCore-1.0.0
REL-100-2024-04-28

Machine Dell Optiplex 790 Legacy booting

 

 

 

 

 

Duet-OpenCore-1.0.0

You need set up Booter/Quirks/FixupAppleEfiImages=true
Then use HfsPlusLegacy.efi

See here

Edited April 27, 2024 by chris1111

[Max.1974]

Uooowwww!!! 🇨🇦 

 

@chris1111 🥷 

[ameenjuz]

On 4/24/2024 at 9:07 AM, Slice said:

I am not sure but I may propose that the exfat.kext is not present in cache in recovery mode. Consider a way to inject it by a bootloader.

I inject exfat.kext by OpenCore during boot but stuck apple logo no boot issue

any idea how to inject or force load to kext by open core

 

[miliuco]

@ameenjuz

Try the driver (ExFatDxe.efi) instead of the kext, put it into Drivers folder and config.plist and remove exfat.kext:

https://github.com/acidanthera/OcBinaryData/tree/master/Drivers

[Slice]

7 hours ago, miliuco said:

@ameenjuz

Try the driver (ExFatDxe.efi) instead of the kext, put it into Drivers folder and config.plist and remove exfat.kext:

https://github.com/acidanthera/OcBinaryData/tree/master/Drivers

There are two different worlds divided by mach_kernel start to process. First of all it clears all interrupt vectors and set own drivers.

Briefly:

efi drivers work before kernel started

kext drivers work after kernel started including recovery mode.

[ameenjuz]

19 hours ago, miliuco said:

@ameenjuz

Try the driver (ExFatDxe.efi) instead of the kext, put it into Drivers folder and config.plist and remove exfat.kext:

https://github.com/acidanthera/OcBinaryData/tree/master/Drivers

Didn’t work with ExFatDxe.efi but in Ventura exfat volume mountable work fine intel base Mac without ExFatDxe.efi  

other hand in macOS Sonoma exfat volume is not mount recovery mode under disk utility 

Edited April 28, 2024 by ameenjuz

[Slice]

Apple didn't make exfat driver working in recovery because the is no sense to use exfat during system recovery.

System recovery should use only APFS drives, exfat can be used for data store, no more. 

If you have a system installer on exfat volume then copy it in a bootloader to APFS volume and then use in recovery.

[deeveedee]

@chris1111 Thanks . I have been setting FixupAppleEfiImages since here, but it didn't work for me and I still needed to use OC 0.9.6 legacy boot.  I'll try again after OC 1.0.0 is released.

 

EDIT: I have always required HfsPlusLegacy.efi on my HackBookPro6,2 since I created the Open Core solution for it.  Since OC 0.9.7, I have assumed that I'm doing something wrong, but never took the time to debug and just reverted to OC 0.9.6 legacy boot.

Edited May 4, 2024 by deeveedee

[chris1111]

1 hour ago, deeveedee said:

@chris1111 Thanks . I have been setting FixupAppleEfiImages since here, but it didn't work for me and I still needed to use OC 0.9.6 legacy boot.  I'll try again after OC 1.0.0 is released.

 

EDIT: I have always required HfsPlusLegacy.efi on my HackBookPro6,2 since I created the Open Core solution for it.  Since OC 0.9.7, I have assumed that I'm doing something wrong, but never took the time to debug and just reverted to OC 0.9.6 legacy boot.

Maybe a temporary solution

Did you try to use only boot file from OC 0.9.6 to OC 1.0.0 EFI duet

simply replace it

If it work You are booting  to OC 1.0.0 after Duet Init -

Edited May 4, 2024 by chris1111

[deeveedee]

@chris1111 Thanks.  That is similar to @droples suggestion here.  I haven't tried it, but I'm sure it would work.  I'm going to test again when OC 1.0.0 is officially released.  Thanks again.

[Stefanalmare]

3 hours ago, deeveedee said:

@chris1111 Thanks.  That is similar to @droples suggestion here.  I haven't tried it, but I'm sure it would work.  I'm going to test again when OC 1.0.0 is officially released.  Thanks again.

It works. I used duet like this last months.

[Slice]

I used duet like this ten years or more.

[Anto65]

Release  v1.0.0   🎉

 

• Updated builtin firmware versions for SMBIOS and the rest
• Switched to Apple silicon GitHub runner for CI, thx @Goooler
• Added Apple Silicon support in all provided utilities
• Utilities now require macOS 10.9+ (OpenCore itself still supports macOS 10.4+)
• Added AllowRelocationBlock support for 32-bit version
• Enabled additional serial logging in non-RELEASE builds of OpenDuet
• Added missing DxeCore ImageContext HOB in OpenDuet
• Fixed assert caused by dependency ordering in OpenDuet
• Prevented assert in normal situation when freeing memory above 4GB in OpenDuet
• Prevented debug assert reporting that optional Hii protocols are not present in OpenDuet
• Fixed problem loading non-firmware runtime drivers (e.g. OpenRuntime.efi) in OpenDuet
• Resolved issue using NOOPT debugging in OpenDuet
• Fixed alphabetical ordering in Configuration.pdf, thx @leon9078
   

Edited May 9, 2024 by Anto65

[deeveedee]

Upgraded my HackBookPro6,2 to Open Core 1.0.0.  LegacyBoot, LogoutHook and Vault all working perfectly.  Running Big Sur, Monterey, Ventura and Sonoma.  Well done, Devs!

[chris1111]

Why Insanelymac is not anymore in the support forum list of OpenCore ?

I don't dream he was before

EDIT *** Got it He was remove from this commit

 

 

 

 

Edited June 8, 2024 by chris1111

[MaLd0n]

Some comrades think here is a mess like Reedit or TonyMAc. There they can lie as much as they want or create 30 accounts to make cute spam.

Here we have order and people have to follow the laws. We need understand one thing, wherever the Acidanthera sycophant are, it's just a mess and people know these guys. That's all folks!