Clover General discussion

[PG7]

1 hour ago, STLVNUB said:

Don't Know What Bootloader I Was Using

But Checkout This:

SMBIOS ! 

video Broadwell SMBIOS MacbookPro12.1 update Ventura !!! 

https://we.tl/t-4RrEJpPYDL

[LockDown]

1 hour ago, Matgen84 said:

It said "OS X" because Clover Devs don't update typo for macOS 10.14+ 🙂 There is any consequence on functionalitys.

That is os x /macos message, not clover

[Matgen84]

50 minutes ago, LockDown said:

That is os x /macos message, not clover

Sorry but a verbose message from macOS before booting macOS is a little bit funny 🙂 This a warning message introduced by Clover Devs, Bro. It indicate that the board-id into config.plist (or generated by Clover) is not good for the version of macOS. For example, a Imac13,2 SMBIOS can't boot Ventura.

 

Edited July 3, 2022 by Matgen84

[LockDown]

6 minutes ago, Matgen84 said:

🙂This a warning message introduced by Clover Devs

 

😯

[naiclub]

HI all what's new

[polyzargone]

38 minutes ago, Matgen84 said:

Sorry but a verbose message from macOS before booting macOS is a little bit funny 🙂 This a warning message introduced by Clover Devs, Bro. It indicate that the board-id into config.plist (or generated by Clover) is not good for the version of macOS. For example, a Imac13,2 SMBIOS can't boot Ventura.

 

 

No, you'll find the exact same error message if you boot with OpenCore and an invalid SMBios. It's definitively not a warning from Clover's devs.

[Slice]

6 hours ago, Matgen84 said:

Sorry but a verbose message from macOS before booting macOS is a little bit funny 🙂 This a warning message introduced by Clover Devs, Bro. It indicate that the board-id into config.plist (or generated by Clover) is not good for the version of macOS. For example, a Imac13,2 SMBIOS can't boot Ventura.

 

This is the message from boot.efi.

Remember boot sequence: 

1. BIOS

2. Clover or Opencore or something else

3. Apple's boot.efi

4. macOS

 

It is really funny that Ventura's boot.efi still said "Mac OS X" but Clover has nothing to do with it. 

[Slice]

On 7/2/2022 at 5:39 PM, chris1111 said:

@Slice build failled Xcode 13.2.1

Xcode 13.2.1 worked fine before

Do not forget to update Opencore too.

[chris1111]

4 hours ago, Slice said:

Do not forget to update Opencore too.

Thanks I always Update OC Module to 👍

 

But Latest commit is perfect Fix thanks 

 

Edited July 3, 2022 by chris1111

[Matgen84]

Hi @Slice and all

I have a strange issue after update Clover r5147 to commit 7ffc6f3 (my Ivybridge config). On this config, I have a primary disk (Catalina + Clover) and a secondary disk ( Windows). Bios setting is macOS Catalina first.

After updating Clover via CloverPKG : my config starts Windows instead of Catalina. What happened and how to fix the problem, please

 

I've forgotten. EDIT: After update, I can't boot Clover at all. Even I choose manually the MacOS disk. My Ivybridge config only starts Windows 10.

Edited July 6, 2022 by Matgen84

[odemolay]

1 hour ago, Matgen84 said:

Salut@Tranche et tout

j'ai un problème étrange après la mise à jour de Clover r5147 pour valider 7ffc6f3 (ma configuration Ivybridge). Sur cette config, j'ai un disque primaire ( Catalina + Clover) et un disque secondaire (Windows). Le réglage du bios est macOS Catalina en premier.

Après la mise à jour de Clover : ma config lance Windows au lieu de Catalina . Que s'est-il passé et comment résoudre le problème, s'il vous plaît

go in the windows shell (as terminal in MacOs) and put

 

bcdedit /set '{bootmgr}' path \EFI\Clover\CloverX64.efi

 

then restart verify your Bios boot choice and tell us
 

[Matgen84]

21 minutes ago, odemolay said:

go in the windows shell (as terminal in MacOs) and put

 

bcdedit /set '{bootmgr}' path \EFI\Clover\CloverX64.efi

 

then restart verify your Bios boot choice and tell us
 

 

Thanks @odemolay Via a clone disk,  I have replace EFI folder with a backup, and delete the update one. 

 

bcedit is a windows command. Do you know alternative method under macOS !

 

I've forgotten. EDIT: After update, I can't boot Clover at all. Even I choose manually the MacOS disk. My Ivybridge config only starts Windows 10.

Edited July 6, 2022 by Matgen84

[Guest 5T33Z0]

@Slice These builds crash when switching configs in the Boot menu (Configs > Select Config)  

 

https://github.com/CloverHackyColor/CloverBootloader/actions/runs/2605995015

https://github.com/CloverHackyColor/CloverBootloader/actions/runs/2601163978

 

In the Release version of r5147 it's working fine. So the issue must have slipped in sometime after that

 

Edited July 6, 2022 by 5T33Z0

[Slice]

32 minutes ago, 5T33Z0 said:

@Slice These builds crash when switching configs in the Boot menu (Configs > Select Config)  

 

https://github.com/CloverHackyColor/CloverBootloader/actions/runs/2605995015

https://github.com/CloverHackyColor/CloverBootloader/actions/runs/2601163978

 

In the Release version of r5147 it's working fine. So the issue must have slipped in sometime after that

 

I see strange thing

1. I can successfully boot Mojave and Ventura with same config0 for iMacPro1,1

2. I can successfully boot Ventura with config1 for iMac17,1. But Mojave crashed with this config! As far as I remember it worked with clover-5146.

What is happen? Is it a problem of new embedded OpenCore? 

Why I can't boot Mojave as iMac17,1??? While Ventura no problem...

[Guest 5T33Z0]

I don't know – you're the Dev. You tell me. I'm just an annoying user reporting issues

[odemolay]

1 hour ago, Matgen84 said:

 

Thanks @odemolay Via a clone disk,  I have replace EFI folder with a backup, and delete the update one. 

 

bcedit is a windows command. Do you know alternative method under macOS !

 

I've forgotten. EDIT: After update, I can't boot Clover at all. Even I choose manually the MacOS disk. My Ivybridge config only starts Windows 10.

if you have a clover EFI op, on your selected drive 

 

just : open cmd in administrator on Windows and type:

bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi

restart, then Clover will start automatically.

if your problem come from Windows :

this is the way to use Windows Boot Manager Settings for UEFI

Windows Boot Manager ({bootmgr}) manages the boot process. UEFI-based systems contain a firmware boot manager, Bootmgfw.efi, that loads an EFI application that is based on variables that are stored in NVRAM.

The BCD settings for the device and path elements in Windows Boot Manager indicate the firmware boot manager. just : bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi

 

if your problem come from your bios -> see how reste CMOS

 

 

 

Edited July 6, 2022 by odemolay

[Stefanalmare]

2 hours ago, Matgen84 said:

 

Thanks @odemolay Via a clone disk,  I have replace EFI folder with a backup, and delete the update one. 

 

bcedit is a windows command. Do you know alternative method under macOS !

 

I've forgotten. EDIT: After update, I can't boot Clover at all. Even I choose manually the MacOS disk. My Ivybridge config only starts Windows 10.

Easiest solution for me it is always Hasleo -> EasyUEFI. Gui in windows to edit the boot OS's and the order.

[PG7]

4 hours ago, Matgen84 said:

Hi @Slice and all

I have a strange issue after update Clover r5147 to commit 7ffc6f3 (my Ivybridge config). On this config, I have a primary disk (Catalina + Clover) and a secondary disk ( Windows). Bios setting is macOS Catalina first.

After updating Clover via CloverPKG : my config starts Windows instead of Catalina. What happened and how to fix the problem, please

 

I've forgotten. EDIT: After update, I can't boot Clover at all. Even I choose manually the MacOS disk. My Ivybridge config only starts Windows 10.

 

here I use the r5147 version in ivy bridge without problems

what may be overtaking boot clover is boot windows after updating

normally you can through the bios set the boot order or if you did a reset NVRAM then you have to create a new boot entry again

several solutions
- manually create an entry \EFI\CLOVER\CLOVERX64.efi
- Bootice by Windows "UEFI" create new entry
- by Clover by a USB by the options

other ways through the Windows terminal as already advised

there is also a way through the shell but I can't help you in that part "I don't know the commands"

Google Translate

[MifJpnAlphaPlus]

Good evening
Developer Beta 3 seems to be difficult to work with.
I want to wait for a while.

If I use clover, I won't be notified of Beta3 updates.

I don't know the details, but I think it is related to the T2 chip.

I will report it for the time being.

CLOVER.zip

2022-07-07_10-56_CLOVERX64.efi.log.zip

 

Thank you.

[Matgen84]

1 hour ago, MifJpnAlphaPlus said:

Good evening
Developer Beta 3 seems to be difficult to work with.
I want to wait for a while.

If I use clover, I won't be notified of Beta3 updates.

I don't know the details, but I think it is related to the T2 chip.

I will report it for the time being.

 

Thank you.

 

Thanks @MifJpnAlphaPlus Right there is problems with Ventura beta 3. Wait and see for boot loader improvements.

There is a typo error in your Imac20,1 config.plist: Hwtarget J185FAP (wrong) instead of J185AP (Correct) 🙂

[Guest 5T33Z0]

@Matgen84 Not really a Typo, just a different model: J185FAP = iMac20,2 while J185AP = iMac20,1

[Common_Sense]

Hello!

 

I cannot see the Beta3 update when I am using a MacPro7,1 SMBIOS, even with HWTarget set:

        <key>HWTarget</key>
        <string>J160AP</string>

 

I also have Firmware variables set:

        <key>ExtendedFirmwareFeatures</key>
        <string>0x8FE001403</string>
        <key>ExtendedFirmwareFeaturesMask</key>
        <string>0xFFFFFFFFFF</string>

 

Do you see any misstakes? Below is the full config.plist.

 

Thanks for your help  

Quote

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>KernelAndKextPatches</key>
    <dict>
        <key>KernelPm</key>
        <false/>
        <key>AppleRTC</key>
        <false/>
    </dict>
    <key>ACPI</key>
    <dict>
        <key>DSDT</key>
        <dict>
            <key>#DropOEM_DSM</key>
            <dict>
                <key>ATI</key>
                <true/>
                <key>IntelGFX</key>
                <true/>
            </dict>
            <key>Fixes</key>
            <dict>
                <key>FixRegions_10000000</key>
                <true/>
            </dict>
        </dict>
        <key>SSDT</key>
        <dict>
            <key>DropOem</key>
            <true/>
            <key>Generate</key>
            <true/>
            <key>EnableC2</key>
            <true/>
            <key>EnableC4</key>
            <true/>
            <key>EnableC6</key>
            <true/>
            <key>EnableC7</key>
            <false/>
            <key>MinMultiplier</key>
            <integer>8</integer>
            <key>MaxMultiplier</key>
            <integer>44</integer>
        </dict>
        <key>HaltEnabler</key>
        <true/>
    </dict>
    <key>Boot</key>
    <dict>
        <key>Arguments</key>
        <string>agdpmod=ignore</string>
        <key>Timeout</key>
        <integer>0</integer>
        <key>XMPDetection</key>
        <integer>-1</integer>
    </dict>
    <key>GUI</key>
    <dict>
        <key>Mouse</key>
        <dict>
            <key>Enabled</key>
            <false/>
            <key>Mirror</key>
            <false/>
            <key>Speed</key>
            <integer>2</integer>
        </dict>
        <key>ProvideConsoleGop</key>
        <true/>
        <key>Scan</key>
        <dict>
            <key>Entries</key>
            <true/>
            <key>Linux</key>
            <false/>
            <key>Legacy</key>
            <false/>
            <key>Tool</key>
            <true/>
        </dict>
        <key>Theme</key>
        <string>OCIntegration</string>
    </dict>
    <key>Graphics</key>
    <dict>
        <key>Inject</key>
        <false/>
    </dict>
    <key>Quirks</key>
    <dict>
        <key>AppleXcpmExtraMsrs</key>
        <false/>
        <key>AppleXcpmForceBoost</key>
        <false/>
        <key>AvoidRuntimeDefrag</key>
        <true/>
        <key>DevirtualiseMmio</key>
        <false/>
        <key>DisableIoMapper</key>
        <true/>
        <key>DisableLinkeditJettison</key>
        <true/>
        <key>DisableSingleUser</key>
        <false/>
        <key>DisableVariableWrite</key>
        <false/>
        <key>DiscardHibernateMap</key>
        <false/>
        <key>DummyPowerManagement</key>
        <false/>
        <key>EnableSafeModeSlide</key>
        <true/>
        <key>EnableWriteUnprotector</key>
        <true/>
        <key>ExternalDiskIcons</key>
        <false/>
        <key>ForceExitBootServices</key>
        <false/>
        <key>FuzzyMatch</key>
        <true/>
        <key>IncreasePciBarSize</key>
        <false/>
        <key>KernelCache</key>
        <string>Auto</string>
        <key>PowerTimeoutKernelPanic</key>
        <true/>
        <key>ProtectMemoryRegions</key>
        <false/>
        <key>ProtectSecureBoot</key>
        <false/>
        <key>ProtectUefiServices</key>
        <false/>
        <key>ProvideCustomSlide</key>
        <false/>
        <key>ProvideMaxSlide</key>
        <integer>0</integer>
        <key>RebuildAppleMemoryMap</key>
        <false/>
        <key>SetupVirtualMap</key>
        <true/>
        <key>SignalAppleOS</key>
        <false/>
        <key>SyncRuntimePermissions</key>
        <false/>
        <key>ThirdPartyDrives</key>
        <false/>
        <key>XhciPortLimit</key>
        <false/>
    </dict>
    <key>RtVariables</key>
    <dict>
        <key>HWTarget</key>
        <string>J160AP</string>
        <key>BooterConfig</key>
        <string>0x285</string>
        <key>CsrActiveConfig</key>
        <string>0x0</string>
        <key>MLB</key>
        <string></string>
        <key>ROM</key>
        <data>
        fNHDU7tH
        </data>
    </dict>
    <key>SMBIOS</key>
    <dict>
        <key>SmUUID</key>
        <string>FA160C38-D4F9-42AA-893B-931C1FF1B452</string>
        <key>SerialNumber</key>
        <string></string>
        <key>BoardSerialNumber</key>
        <string></string>
        <key>ProductName</key>
        <string>MacPro7,1</string>
        <key>ExtendedFirmwareFeatures</key>
        <string>0x8FE001403</string>
        <key>ExtendedFirmwareFeaturesMask</key>
        <string>0xFFFFFFFFFF</string>
    </dict>
    <key>SystemParameters</key>
    <dict>
        <key>InjectKexts</key>
        <true/>
        <key>InjectSystemID</key>
        <true/>
    </dict>
</dict>
</plist>

 

 

[MifJpnAlphaPlus]

4 hours ago, MifJpnAlphaPlus said:

Good evening
Developer Beta 3 seems to be difficult to work with.
I want to wait for a while.

If I use clover, I won't be notified of Beta3 updates.

I don't know the details, but I think it is related to the T2 chip.

I will report it for the time being.

CLOVER.zip 13.55 MB · 3 downloads

2022-07-07_10-56_CLOVERX64.efi.log.zip 18.43 kB · 0 downloads

 

Thank you.

good evening
I participated in the OpenCore Beta3 test, but the Bata2 SSD image is on the file server.
The test is ready at any time.
Thank you.

[Guest 5T33Z0]

34 minutes ago, Common_Sense said:

Hello!

 

I cannot see the Beta3 update when I am using a MacPro7,1 SMBIOS, even with HWTarget set:

        <key>HWTarget</key>
        <string>J160AP</string>

 

I also have Firmware variables set:

        <key>ExtendedFirmwareFeatures</key>
        <string>0x8FE001403</string>
        <key>ExtendedFirmwareFeaturesMask</key>
        <string>0xFFFFFFFFFF</string>

 

Do you see any misstakes? Below is the full config.plist.

 

Thanks for your help  

 

 

 

You can't install beta 3 with Clover yet, anyway…

 

Clover had issues with HWTarget before the last update. Maybe HWTarget is bypassed for now and that's why you won't see updates.

[PG7]

thanks Team


commit Clover beta-c7789dc29
boot OK

 

Spoiler