Clover General discussion

chris1111 · February 19, 2018

Quick question: is there any way to mount the EFI partition from the Terminal?

Right now I use Clover Configurator, and Google has also shown me another GUI app "EFI Mounter v3".

But is there no command I can use from the command line?

Thanks.

diskutil list

diskutil Mount /dev/disk0s1

TheBloke · February 19, 2018

Awesome, thanks very much both!

cecekpawon · February 20, 2018

Sorry if this was already discussed but I'm wondering it it's possible to change the black boot screen(white apple/black background) to the gray one like real macs.

Any news? I did some experiment according grey boot last year. I gave up and abandon that thread. Please share your experiences..

Yes, "DefaultBackgroundColor" wil get deleted everyboot & not taking any effect with 0x00bfbfbf value.

FP.D79E3F20[\System\Library\PrelinkedKernels\prelinkedkernel].Close() = Success
->SetVariable(DefaultBackgroundColor, gEfiAppleNvramGuid, 0, 0, 0) = Not Found

For me, default "gBootArgs->flags" would be 0x41 (kBootArgsFlagRebootOnPanic | kBootArgsFlagBlackBg).

By manually storing that flags without kBootArgsFlagBlackBg, I got greyed boot and then black again.

Lucy183 · February 20, 2018

Any news? I did some experiment according grey boot last year. I gave up and abandon that thread. Please share your experiences..

Yes, "DefaultBackgroundColor" wil get deleted everyboot & not taking any effect with 0x00bfbfbf value.
FP.D79E3F20[\System\Library\PrelinkedKernels\prelinkedkernel].Close() = Success
->SetVariable(DefaultBackgroundColor, gEfiAppleNvramGuid, 0, 0, 0) = Not Found
For me, default "gBootArgs->flags" would be 0x41 (kBootArgsFlagRebootOnPanic | kBootArgsFlagBlackBg).

By manually storing that flags without kBootArgsFlagBlackBg, I got greyed boot and then black again.

I abandoned this too, I'll let it black...

smolderas · February 20, 2018

It is possible to print out the versions of loaded drivers in LoadDrivers() too?

Slice · February 20, 2018

It is possible to print out the versions of loaded drivers in LoadDrivers() too?

They have no version string. There are only two versions new and bad.

If you somehow want to keep old drivers then you may copy drivers64UEFi folder to drivers64UEFI_rev4415 and keep it proposing all newer version will be wrong. It is not true.

smolderas · February 20, 2018

They have no version string. There are only two versions new and bad.

If you somehow want to keep old drivers then you may copy drivers64UEFi folder to drivers64UEFI_rev4415 and keep it proposing all newer version will be wrong. It is not true.

Thanks for the advice, I was just curious to read out the version.. According to specification, the drivers (should) have versions...

Slice · February 21, 2018

Thanks for the advice, I was just curious to read out the version.. According to specification, the drivers (should) have versions...

This is version of the specification

[Defines]
  INF_VERSION                    = 0x00010005
  BASE_NAME                      = AtaAtapiPassThruDxe
  MODULE_UNI_FILE                = AtaAtapiPassThruDxe.uni
  FILE_GUID                      = 5E523CB4-D397-4986-87BD-A6DD8B22F455
  MODULE_TYPE                    = UEFI_DRIVER
  VERSION_STRING                 = 1.0
  ENTRY_POINT                    = InitializeAtaAtapiPassThru

chris1111 · February 21, 2018

Source Forge remote Clover works good here

just do this

mkdir Test

cd ~/Test

svn co svn://svn.code.sf.net/p/cloverefiboot/code Clover

Lucy183 · February 21, 2018

Source Forge remote Clover works good here

just do this

mkdir Test

cd ~/Test

svn co svn://svn.code.sf.net/p/cloverefiboot/code Clover

Yeah it works for me too, but not everytime.

buildclover command isn't working, but if you update the code with svn up, then compile with command it's ok.

TheBloke · February 21, 2018

Guys, I want to test the boot flag -nehalem_error_disable

In Clover Configurator, do I add that as typed above: -nehalem_error_disable

Or do I add it as: nehalem_error_disable ?

Looking at the default boot flags provided by Configurator, some are -flag and some are just flag, no - before it. I'd expect a flag to normally have a - so maybe this is just how Configurator is displaying some of them inconsistently.

I'm currently booted with -nehalem_error_disable added as follows:

My guess is that this is the correct way, but I wanted to ask to be sure, as I have no other way of confirming if the flag applied or not (I'm trying it on my X58 system as I've heard it's sometimes required/helpful on systems with SMBIOs 5.1.)

Lucy183 · February 22, 2018

Guys, I want to test the boot flag -nehalem_error_disable

In Clover Configurator, do I add that as typed above: -nehalem_error_disable

Or do I add it as: nehalem_error_disable ?

Looking at the default boot flags provided by Configurator, some are -flag and some are just flag, no - before it. I'd expect a flag to normally have a - so maybe this is just how Configurator is displaying some of them inconsistently.

I'm currently booted with -nehalem_error_disable added as follows:

My guess is that this is the correct way, but I wanted to ask to be sure, as I have no other way of confirming if the flag applied or not (I'm trying it on my X58 system as I've heard it's sometimes required/helpful on systems with SMBIOs 5.1.)

-nehalem_error_disable is the right flag.

toleda · February 22, 2018

Clover_v4369/MatchOS not working:

[OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed

0:100  0:000  Now is 21.2.2018,  21:16:59 (GMT)
0:100  0:000  Starting Clover revision: 4369 on American Megatrends EFI

14:193  0:000  Filtering KextPatches:
14:193  0:000   - [00]: com.apple.driver.AppleHDA (t1-10.8-AppleHDA-Realtek-ALC1150) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
14:193  0:000   - [01]: com.apple.driver.AppleHDA (t1-AppleHDA-Resources-xml>zml-(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
14:193  0:000   - [02]: com.apple.driver.AppleHDA (t1-10.12-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed
14:193  0:000   - [03]: com.apple.driver.AppleHDA (t1-10.11-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.11.x | MatchBuild: All] ==> not allowed

Suggestions?

Sherlocks · February 22, 2018

Clover_v4369/MatchOS not working:

[OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed

0:100  0:000  Now is 21.2.2018,  21:16:59 (GMT)
0:100  0:000  Starting Clover revision: 4369 on American Megatrends EFI

14:193  0:000  Filtering KextPatches:
14:193  0:000   - [00]: com.apple.driver.AppleHDA (t1-10.8-AppleHDA-Realtek-ALC1150) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
14:193  0:000   - [01]: com.apple.driver.AppleHDA (t1-AppleHDA-Resources-xml>zml-(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
14:193  0:000   - [02]: com.apple.driver.AppleHDA (t1-10.12-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed
14:193  0:000   - [03]: com.apple.driver.AppleHDA (t1-10.11-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.11.x | MatchBuild: All] ==> not allowed

Suggestions?

r4416 is no problem

com.apple.iokit.IONVMeFamily (10.13::External NVMe icon) :: BinPatch :: [OS: 10.13.4 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed

smolderas · February 22, 2018

r4416 is no problem

com.apple.iokit.IONVMeFamily (10.13::External NVMe icon) :: BinPatch :: [OS: 10.13.4 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed

It says that, but does it really patch?

The following doesn't work anymore after r4291 (I think)...

<key>KextsToPatch</key>                                         
                <array>                                                         
                        <dict>                                                  
                                <key>Comment</key>                              
                                <string>Boot screen fix</string>                
                                <key>Find</key>                                 
                                <data>AQAAdSI=</data>                           
                                <key>Name</key>                                 
                                <string>com.apple.iokit.IOGraphicsFamily</string>
                                <key>Replace</key>                              
                                <data>AQAA6yI=</data>                           
                        </dict>                                                 
                </array>

Sherlocks · February 22, 2018

It says that, but does it really patch?

The following doesn't work anymore after r4291 (I think)...

<key>KextsToPatch</key>                                         
                <array>                                                         
                        <dict>                                                  
                                <key>Comment</key>                              
                                <string>Boot screen fix</string>                
                                <key>Find</key>                                 
                                <data>AQAAdSI=</data>                           
                                <key>Name</key>                                 
                                <string>com.apple.iokit.IOGraphicsFamily</string>
                                <key>Replace</key>                              
                                <data>AQAA6yI=</data>                           
                        </dict>                                                 
                </array>

Did you rebuild cache?

나의 LG-F800S 의 Tapatalk에서 보냄

smolderas · February 22, 2018

Did you rebuild cache?

나의 LG-F800S 의 Tapatalk에서 보냄

Even though I don't think it is necessary, I did rebuild cache. It doesn't work with this message:

4:005  0:000  === [ StartLoader ] =======================================
4:005  0:000  Finally: ExternalClock=25MHz BusSpeed=100294kHz CPUFreq=4300MHz PIS: hw.busfrequency=100000000Hz
4:005  0:000  Loading boot.efi  status=Success
4:079  0:074  GetOSVersion: 10.13.3 (17D102)
4:079  0:000  Filtering KextPatches:
4:079  0:000   - [00]: com.apple.iokit.IOGraphicsFamily (Boot screen fix) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed
4:079  0:000  Will not patch boot.efi
4:079  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success

Sherlocks · February 22, 2018

Even though I don't think it is necessary, I did rebuild cache. It doesn't work with this message:

4:005  0:000  === [ StartLoader ] =======================================
4:005  0:000  Finally: ExternalClock=25MHz BusSpeed=100294kHz CPUFreq=4300MHz PIS: hw.busfrequency=100000000Hz
4:005  0:000  Loading boot.efi  status=Success
4:079  0:074  GetOSVersion: 10.13.3 (17D102)
4:079  0:000  Filtering KextPatches:
4:079  0:000   - [00]: com.apple.iokit.IOGraphicsFamily (Boot screen fix) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed
4:079  0:000  Will not patch boot.efi
4:079  0:000  EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success

log is good. i tested binary patches are good working. i don't use boot screen fix patch. i use Lilu.kext+IntelGraphicsFixup.kext

toleda · February 22, 2018

r4416 is no problem

com.apple.iokit.IONVMeFamily (10.13::External NVMe icon) :: BinPatch :: [OS: 10.13.4 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed

Thanks for your reply, no change

0:100 0:000 Starting Clover revision: 4411 on American Megatrends EFI

14:438 0:000 - [02]: com.apple.driver.AppleHDA (t1-10.12-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed

PMheart · February 22, 2018

Clover_v4369/MatchOS not working:

[OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed

0:100  0:000  Now is 21.2.2018,  21:16:59 (GMT)
0:100  0:000  Starting Clover revision: 4369 on American Megatrends EFI

14:193  0:000  Filtering KextPatches:
14:193  0:000   - [00]: com.apple.driver.AppleHDA (t1-10.8-AppleHDA-Realtek-ALC1150) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
14:193  0:000   - [01]: com.apple.driver.AppleHDA (t1-AppleHDA-Resources-xml>zml-(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
14:193  0:000   - [02]: com.apple.driver.AppleHDA (t1-10.12-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.12.x, 10.13.x | MatchBuild: All] ==> not allowed
14:193  0:000   - [03]: com.apple.driver.AppleHDA (t1-10.11-AppleHDA-Realtek-ALC...(cloverALC-all_codecs)) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.11.x | MatchBuild: All] ==> not allowed

Suggestions?

If I remember correctly the separator should only be a comma (i.e. ','), instead of a comma plus a space. (", ")

So you may try "10.12.x,10.13.x", rather than "10.12.x, 10.13.x".

It says that, but does it really patch?

The following doesn't work anymore after r4291 (I think)...

<key>KextsToPatch</key>                                         
                <array>                                                         
                        <dict>                                                  
                                <key>Comment</key>                              
                                <string>Boot screen fix</string>                
                                <key>Find</key>                                 
                                <data>AQAAdSI=</data>                           
                                <key>Name</key>                                 
                                <string>com.apple.iokit.IOGraphicsFamily</string>
                                <key>Replace</key>                              
                                <data>AQAA6yI=</data>                           
                        </dict>                                                 
                </array>

Is it possible that the patch is broken?

"allowed" means the patch is "legal", yet may not be "appropriate".

EDIT: You may check the debug log, particularly something like "patched %d times", or so...

Edited February 22, 2018 by PMheart

toleda · February 22, 2018

If I remember correctly the separator should only be a comma (i.e. ','), instead of a comma plus a space. (", ")

Spot on, working. Thank you.

Badruzeus · February 23, 2018

Kext to patch is also working just fine here Thanks.

1:446  0:000  Now is 22.2.2018,  22:35:37 (GMT)
1:446  0:000  Starting Clover revision: 4416 on CLOVER EFI
1:446  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/badruzeus/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2.1]
.....  .....
7:355  0:000  === [ StartLoader ] =======================================
7:355  0:000  Finally: ExternalClock=24MHz BusSpeed=99773kHz CPUFreq=2195MHz PIS: hw.busfrequency=96000000Hz
7:355  0:000  Loading boot.efi  status=Success
7:468  0:113  GetOSVersion: 10.11.6 (15G19009)
7:468  0:000  CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS | CSR_ALLOW_TASK_FOR_PID | CSR_ALLOW_UNRESTRICTED_DTRACE | CSR_ALLOW_UNRESTRICTED_NVRAM
7:468  0:000  Filtering KextPatches:
7:468  0:000   - [00]: com.apple.driver.AirPort.Atheros40 (Wi-Fi Region) :: BinPatch :: [OS: 10.11.6 | MatchOS: All | MatchBuild: All] ==> allowed
7:468  0:000   - [01]: com.apple.driver.AppleGraphicsDevicePolicy (Disable board-id check to prevent no signal (c) lvs1974, Pike R. Alpha, vit9696) :: BinPatch :: [OS: 10.11.6 | MatchOS: All | MatchBuild: All] ==> allowed
7:468  0:000   - [02]: AppleAHCIPort (Fix Intel Chipset Error) :: BinPatch :: [OS: 10.11.6 | MatchOS: 10.13.x | MatchBuild: All] ==> not allowed
7:468  0:000   - [03]: AppleAHCIPort (Fix Intel Chipset Error Hot-plug) :: BinPatch :: [OS: 10.11.6 | MatchOS: 10.13.x | MatchBuild: All] ==> not allowed

Funky frank · February 27, 2018

Hi,

I have two configs in my clover dir. The default config sets busspeed, c3-latency and a command line, the other config has no settings here. If I now choose the other config in the clover menu, there are still the settings of the default config visible...

Is this a bug?

Also I have a problem with installing the macOS 10.12.6 security update 2018-001: Every time I click on restart, nothing will happen. If I then restart manually, there comes another requester, I click "install & restart", still it only restarts... Any idea? Thanks!

Funky frank · February 27, 2018

Aaaaand a third one: I tried to update to High Sierra on my backup drive, it restarted and now there is no boot entry for my backup drive anymore.... Why? Clover is 4392. Update?

This is what was added to root dir:

The kernel in /System/Library/Kernels still is there. So why there is no entry in clover anymore? It was there before I run high Sierra installer (without APFS conversion).

Funky frank · February 27, 2018

Eh, that is so weird, it does not show a boot entry for the backup drive anymore. I now re-backupped the original drive, and still, no entry! oO I don't hide any drives except windows stuff. But why even after backup again still no boot entry?

What is the limit in number of entries in clover?

What is the usual location of the mac os sierra kernel, found by clover?

Is clover macos detection {censored}ed up?

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