Clover General discussion

Un!x · November 25, 2019

On 11/15/2019 at 6:17 PM, Slice said:

Or for older Mac

0x0206

to be version 2.6

iMacPro1,1 has 2.4 but why so old?!

Slice · November 25, 2019

Apple has own Smbios definition based on standard 2.4 but with own tables and with own interpretations.

BCD revision remains 24.

For the new Macs they make BCD revision 30. There is a point to investigation for us what is changed else and what we have to do.

Drinahn · November 26, 2019

On 11/24/2019 at 8:37 PM, Pene said:

The feature is meant to be used for injecting properties depending on which card is the monitor connected to when system boots up. It checks which card has the GOP active (that will be the card where you see the POST output), and allows you to inject properties judging by that. For example, if you want to always disable the card which was not active when booting, you can inject to SecondaryGPU.

As in your case you always want to disable a specific card, it is better to inject directly to it, as you are already doing.

Ah I see. Thank you sir!

telepati · November 28, 2019

Hide options don't work for me. I am trying to hide windows and preboot drive and I am writing Windows and Preboot to hide section after restart it doesn't affect anything. I remember earlier version of clover always hide when I write the driver's name.

Edited November 28, 2019 by telepati

Slice · November 29, 2019

20 hours ago, telepati said:

Hide options don't work for me. I am trying to hide windows and preboot drive and I am writing Windows and Preboot to hide section after restart it doesn't affect anything. I remember earlier version of clover always hide when I write the driver's name.

Worked as before.

Andres ZeroCross · November 29, 2019

Can we use hibernatemode 25 with Clover???

I tried it,, after system sleep (ram led off, machine off) then i wake the machine -> BIOS Logo -> menu entry then i select macOS partition,, loading like boot. Then there is log about sleep wake failure. Sleep with hibernatemode 3 and 0 is fine. (I am using AptiMemoryFix.efi)

Sorry, i tried with other bootloader,, Sleep -> wake the machine -> BIOS Logo -> Menu entry -> Select Menu Entry (macos partition), then i reach desktop screen (no apple loading),, I get desktop in 2 seconds after press macOS partion.

Sleep Wake Failure_2019-11-29-231307_Andress-iMac.diag

Edited November 29, 2019 by Andres ZeroCross

Slice · November 29, 2019

4 hours ago, Andres ZeroCross said:

Can we use hibernatemode 25 with Clover???

I tried it,, after system sleep (ram led off, machine off) then i wake the machine -> BIOS Logo -> menu entry then i select macOS partition,, loading like boot. Then there is log about sleep wake failure. Sleep with hibernatemode 3 and 0 is fine. (I am using AptiMemoryFix.efi)

Sorry, i tried with other bootloader,, Sleep -> wake the machine -> BIOS Logo -> Menu entry -> Select Menu Entry (macos partition), then i reach desktop screen (no apple loading),, I get desktop in 2 seconds after press macOS partion.

Sleep Wake Failure_2019-11-29-231307_Andress-iMac.diag

The question has several caveats.

1. Not all hackintoshes are able to hibernate.

2. There is a new problem in Catalina even if it worked in Mojave.

3. If OC embedded the quirk then it doesn't mean Clover must do the same. Changing config.plist or use additional kexts are also variants.

Additional kext is HibernationFixup new version. It worked with Clover.

In config.plist you may write kext patch

com.apple.iokit.IOAHCIBlockStorage

0F 84 6F 01 00 00 FF CB -> 90 90 90 90 90 90 FF CB

Andres ZeroCross · November 30, 2019

6 hours ago, Slice said:

The question has several caveats.

1. Not all hackintoshes are able to hibernate.

2. There is a new problem in Catalina even if it worked in Mojave.

3. If OC embedded the quirk then it doesn't mean Clover must do the same. Changing config.plist or use additional kexts are also variants.

Additional kext is HibernationFixup new version. It worked with Clover.

In config.plist you may write kext patch

com.apple.iokit.IOAHCIBlockStorage

0F 84 6F 01 00 00 FF CB -> 90 90 90 90 90 90 FF CB

Sorry, i don't want to compare both of Bootloader. I just want to inform my machine work Hibernate in Catalina with other bootloader.

So, no problem with AptioMemoryFix.efi?? Or should i change OsxAptioFixDrv.efi or OsxAptioFix3Drv,efi?? I have read only OsxAptioFix2Drv.efi support hibernate.

I will try you patch soon,, will report back

telepati · November 30, 2019

16 hours ago, Slice said:

Worked as before.

is that so? This are the settings I used for hiding and these did not make an effect. am I doing something wrong?

943223483_ScreenShot2019-11-30at07_27_09.png.95c698f5871e1738ebc5b02368018b5b.png

Slice · November 30, 2019

4 minutes ago, telepati said:

is that so? This are the settings I used for hiding and these did not make an effect. am I doing something wrong?

It may be an error of the CloverConfigurator.

Show your config.plist and preboot.log.

Andres ZeroCross · November 30, 2019

57 minutes ago, Slice said:

It may be an error of the CloverConfigurator.

Show your config.plist and preboot.log.

In Mojave
1. Sleep and wake with hibernatemode 0 and 3 is fine
2. Sleep with hibernatemode 25 is fine but when i press button to wake -> bios logo -> GUI CLOVEr -> Select Mojave partition -> boot like cold boot (with apple loading bar),, so this is not boot from hibernate file. But there is no KP log in Desktop

In Catalina
1. Sleep and wake with hibernatemode 0 and 3 is fine
2. Sleep with hibernatemode 25 is fine but when i press button to wake -> bios logo -> GUI CLOVEr -> Select Catalina partition -> boot like cold boot (with apple loading bar),, so this is not boot from hibernate file. But there log about Kernel Panic in Desktop (like attachment log above)

I am using AptioMemoryFix.efi + ptch bin above..

Slice · November 30, 2019

37 minutes ago, Andres ZeroCross said:

In Mojave
1. Sleep and wake with hibernatemode 0 and 3 is fine
2. Sleep with hibernatemode 25 is fine but when i press button to wake -> bios logo -> GUI CLOVEr -> Select Mojave partition -> boot like cold boot (with apple loading bar),, so this is not boot from hibernate file. But there is no KP log in Desktop

In Catalina
1. Sleep and wake with hibernatemode 0 and 3 is fine
2. Sleep with hibernatemode 25 is fine but when i press button to wake -> bios logo -> GUI CLOVEr -> Select Catalina partition -> boot like cold boot (with apple loading bar),, so this is not boot from hibernate file. But there log about Kernel Panic in Desktop (like attachment log above)

I am using AptioMemoryFix.efi + ptch bin above..

If you see no (Hibernated) in Clover GUI then you have no NVRAM working.

Do you use HibernationFixup.kext?

telepati · November 30, 2019

12 hours ago, Slice said:

It may be an error of the CloverConfigurator.

Show your config.plist and preboot.log.

Here they are;

config.plist

debug.log

Slice · November 30, 2019

2 hours ago, telepati said:

Here they are;

config.plist

debug.log

It works

2:920  0:003  - [06]: 'Windows 10', hidden
3:001  0:003  - [15]: 'Preboot', hidden

But there are also legacy entries

3:067  0:004  Scanning legacy ...
3:070  0:003   3: '' (vista,win) add legacy
3:077  0:006   added 'Boot Windows from ' OSType=2 Icon=vista,win
3:081  0:003   4: 'EFI' (vista,win) add legacy
3:087  0:006   added 'Boot Windows from EFI' OSType=2 Icon=vista,win
3:091  0:003   6: 'Windows 10' (vista,win) hidden
3:097  0:006   7: '' (vista,win) add legacy
3:104  0:006   added 'Boot Windows from ' OSType=2 Icon=vista,win

So make

		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>

LockDown · December 2, 2019

OS: High Sierra 10.13.6

Xcode: 10.1

SDK: MacOSX10.14.sdk

Im trying to complie latest Clover source using it's own buildme (GCC53).

The build was successful. But checking the log, I see some errors.

[CC] Gcd
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2FBdsDxe/BdsDxeOffset.raw] Error 1 (ignored)
...

[CC] FSInject
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/A17F4A89-5F19-444f-B7BE-48195E0575DBSmbiosGenDxe/SmbiosGenDxeOffset.raw] Error 1 (ignored)
...

[CC] egemb_icons
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/E660EA85-058E-4b55-A54B-F02F83A24707DisplayEngine/DisplayEngineOffset.raw] Error 1 (ignored)
...

[CC] PciDriverOverride
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2FBdsDxe/BdsDxeOffset.raw] Error 1 (ignored)
...

[GENFW] SmbiosGenDxe
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/A17F4A89-5F19-444f-B7BE-48195E0575DBSmbiosGenDxe/SmbiosGenDxeOffset.raw] Error 1 (ignored)
...

[GENFW] DisplayEngine
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/E660EA85-058E-4b55-A54B-F02F83A24707DisplayEngine/DisplayEngineOffset.raw] Error 1 (ignored)
...

Are these to be ignored or a bug?

mrjayviper · December 2, 2019

What's the best Clover version for Mojave? I'm asking since if I used v5099, the USB stick doesn't show up in the bootable devices list. When I tried v4586, the USB installer shows up.

Thanks

edit:

I normally have to select these 4 drivers to get my setup to work (i mean not just this instance but on previous setup/High Sierra as well):

1. ApfsDriverLoader-64

2. AptioMemoryFix-64

3. EmuVariableUefi-64

4. NvmExpressDxe-64

Edited December 2, 2019 by mrjayviper

Matgen84 · December 2, 2019

24 minutes ago, mrjayviper said:

What's the best Clover version for Mojave? I'm asking since if I used v5099, the USB stick doesn't show up in the bootable devices list. When I tried v4586, the USB installer shows up.

Thanks

The latest r5099 works fine here, for Mojave. Clover shows up the USB installer.

mrjayviper · December 2, 2019

g

21 minutes ago, Matgen84 said:

The latest r5099 works fine here, for Mojave. Clover shows up the USB installer.

good for you.

There's no difference between the installer except the version of Clover used. The installer is created using some scripts I created so there's almost zero percent chance I have created the USB installer for v5099 and v4586 differently.

Matgen84 · December 2, 2019

9 minutes ago, mrjayviper said:

g

good for you.

There's no difference between the installer except the version of Clover used. The installer is created using some scripts I created so there's almost zero percent chance I have created the USB installer for v5099 and v4586 differently.

Sorry if It isn't good for you.

I don't understand why you've this problem with USB installer

Edited December 2, 2019 by Matgen84

bronxteck · December 2, 2019

try adding HFS driver. the installer is HFS not APFS

telepati · December 2, 2019

On 11/30/2019 at 10:15 PM, Slice said:

It works


2:920  0:003  - [06]: 'Windows 10', hidden
3:001  0:003  - [15]: 'Preboot', hidden

But there are also legacy entries


3:067  0:004  Scanning legacy ...
3:070  0:003   3: '' (vista,win) add legacy
3:077  0:006   added 'Boot Windows from ' OSType=2 Icon=vista,win
3:081  0:003   4: 'EFI' (vista,win) add legacy
3:087  0:006   added 'Boot Windows from EFI' OSType=2 Icon=vista,win
3:091  0:003   6: 'Windows 10' (vista,win) hidden
3:097  0:006   7: '' (vista,win) add legacy
3:104  0:006   added 'Boot Windows from ' OSType=2 Icon=vista,win

So make


		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>

I enabled the Legacy and it looks hidden in the debug. But in reality, I am still seeing those drivers on the boot screen. I really don't get it why.

IMG_0250.JPG.80efc5e5e4faeb1701c1c8ff38aedaec.JPG

config.plist

debug.log

Edited December 2, 2019 by telepati

vector sigma · December 2, 2019

17 hours ago, ellaosx said:

OS: High Sierra 10.13.6

Xcode: 10.1

SDK: MacOSX10.14.sdk

Im trying to complie latest Clover source using it's own buildme (GCC53).

The build was successful. But checking the log, I see some errors.


[CC] Gcd
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2FBdsDxe/BdsDxeOffset.raw] Error 1 (ignored)
...


[CC] FSInject
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/A17F4A89-5F19-444f-B7BE-48195E0575DBSmbiosGenDxe/SmbiosGenDxeOffset.raw] Error 1 (ignored)
...


[CC] egemb_icons
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/E660EA85-058E-4b55-A54B-F02F83A24707DisplayEngine/DisplayEngineOffset.raw] Error 1 (ignored)
...


[CC] PciDriverOverride
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2FBdsDxe/BdsDxeOffset.raw] Error 1 (ignored)
...


[GENFW] SmbiosGenDxe
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/A17F4A89-5F19-444f-B7BE-48195E0575DBSmbiosGenDxe/SmbiosGenDxeOffset.raw] Error 1 (ignored)
...


[GENFW] DisplayEngine
...
make: [/Users/ella/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Ffs/E660EA85-058E-4b55-A54B-F02F83A24707DisplayEngine/DisplayEngineOffset.raw] Error 1 (ignored)
...

Are these to be ignored or a bug?

use XCODE8 as gcc has compile/run time problems in Catalina and only developers can get rid of them with OS headers. I guess this will be fixed with newer gcc releases soon. (but who built it is very happy because is better than Clang as for c code more "understandable" warnings show up, also lto remove unused code which means smaller binaries)

4 hours ago, telepati said:

I enabled the Legacy and it looks hidden in the debug. But in reality, I am still seeing those drivers on the boot screen. I really don't get it why.

config.plist

debug.log

Slice said to you Legacy=No:

<key>Legacy</key>
<false/>

but you stlll have Legacy=Yes (i.e. true), so don't be surprised .

Works very well instead

EDIT

4 hours ago, telepati said:

I enabled the Legacy

yep, just the opposite and in fact your legacy entries are added instead of to be removed:

3:137  0:004  Scanning legacy ...
3:141  0:003   3: '' (vista,win) add legacy
3:151  0:003   4: 'EFI' (vista,win) add legacy
3:167  0:006   7: '' (vista,win) add legacy
2:322  0:008          Result of bootcode detection: bootable unknown (legacy)
2:343  0:010          Result of bootcode detection: bootable unknown (legacy)
2:368  0:007          Result of bootcode detection: bootable unknown (legacy)
2:385  0:009          Result of bootcode detection: bootable unknown (legacy)
3:154  0:004  Scanning legacy ...
3:158  0:003   3: '' (vista,win) add legacy
3:167  0:003   4: 'EFI' (vista,win) add legacy
3:186  0:008   7: '' (vista,win) add legacy

Edited December 2, 2019 by vector sigma

vector sigma · December 2, 2019

If you want an advice.... stop using Clover Configurator and do it by your self... as if the result of your screenshot doesn't reflect the reality you cannot trust it.

Edited December 2, 2019 by vector sigma

bronxteck · December 2, 2019

it is a bug in clover configurator app. it does not have the drop down option Legacy=false instead it just deletes the config entry. the only variable it adds is Legacy=Yes

vector sigma · December 2, 2019

3 minutes ago, bronxteck said:

it is a bug in clover configurator app. it does not have the drop down option Legacy=false instead it just deletes the config entry. the only variable it adds is Legacy=Yes

And I cannot imagine how many errors can be present in the entire config file...

Edited December 2, 2019 by vector sigma

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites