Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Funky frank
Funky frank
Posted
Posted (edited)
4 hours ago, apianti said:

Clover detects macOS from the HFS+ partition as that is where the OS loader is. There must be something wrong with the partition map or the parition/volume itself.

Hm, ok thanks for this info. What is clover exactly looking for on the HFS+ partition? Only /Sys/Lib/Kernels/kernel ?  What files do have to exist to make it appear in the list?

 

btw. these are the bootlog entries: 

3:569  0:001  === [ ScanLoader ] ========================================
3:569  0:000  - [05]: 'Win8Boot'
3:569  0:000  - [06]: 'Win8System', hidden
3:569  0:000  - [07]: 'ntfsrest', hidden
3:569  0:000  - [08]: 'EFI'
3:570  0:000  - [09]: 'OSX2'
3:649  0:079          AddLoaderEntry for Volume Name=OSX2
3:719  0:070      hibernated: set as never
3:778  0:058  - [10]: 'Recovery HD'
3:778  0:000          AddLoaderEntry for Volume Name=Recovery HD
3:809  0:031  - [11]: 'EFI'
3:812  0:002  - [13]: 'EFI'
3:815  0:003  - [14]: 'OSXSSD'
3:819  0:004          AddLoaderEntry for Volume Name=OSXSSD
3:822  0:002      hibernated: set as never
3:824  0:002  Scanning legacy ...
3:824  0:000   5: 'Win8Boot' (vista,win) add legacy
3:825  0:000   added 'Boot Windows from Win8Boot' OSType=2 Icon=vista,win
3:825  0:000   6: 'Win8System' (vista,win) hidden
3:825  0:000   7: 'ntfsrest' (vista,win) hidden
3:825  0:000  11: 'EFI' (win) add legacy
3:825  0:000   added 'Boot Windows from EFI' OSType=2 Icon=win

That new "EFI" entry really seems to come from the EFI partition of "OSX" and will be falsely listed as windows...?

Edited by Funky frank
Funky frank
Funky frank
Posted
Posted (edited)
8 minutes ago, Slice said:

Clover looks for file boot.efi to mark the HFS+ partition to be loadable.

Thanks for info.

But on the "OSX" HFS+ partition, there is a 571.960 bytes sized "boot.efi" under /System/Library/CoreServices/boot.efi.

Also more log: 

3:825  0:000  === [ AddCustomTool ] =====================================
3:830  0:005  found tool \EFI\CLOVER\tools\Shell64U.efi
3:830  0:000  Checking EFI partition Volume 8 for Clover
3:831  0:001  Checking EFI partition Volume 11 for Clover
3:845  0:014   Found Clover
3:846  0:000  === [ GetEfiBootDeviceFromNvram ] =========================
3:846  0:000   - found entry 2. 'Boot macOS from OSXSSD', Volume 'OSXSSD', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(2,GPT,8718D221-ECD2-4374-XXXX-AAB2D2CEA036,0x64028,0x3A2E1FE0)\System\Library\CoreServices\boot.efii'
3:846  0:000  DefaultIndex=2 and MainMenu.EntryCount=11
3:875  0:028  GUI ready
5:876  2:001  === [ StartLoader ] =======================================

So it cannot find the boot.efi on "OSX", even if I see here that it is there...

Btw. notice the typo? in the log "boot.efii' instead "boot.efi"...

Also why is it getting the info only from nvram? "GetEfiBootDeviceFromNvram"...

Edited by Funky frank
vector sigma
vector sigma
Posted
Posted (edited)
1 hour ago, Funky frank said:

Also why is it getting the info only from nvram? "GetEfiBootDeviceFromNvram"...

can you temporarily remove EmuVariable and then reboot?

looks like you played with boot camp assistant (why you had an hybrid MBR): 

// UEFI boot: get gEfiBootDeviceGuid from NVRAM.
    // if present, ScanVolumes () will skip scanning other volumes in the first run.
    // this speeds up loading of default OSX volume.
    GetEfiBootDeviceFromNvram ();

it's in your nvram.plist

Edited by vector sigma
  • Like 1
Funky frank
Funky frank
Posted
Posted

Hi, I am not using emuvariable, but real nvram from the board. I already cleaned the nvram (there were lots of efi-apple-payload entries, but no change).

So could I select the other drive in the macos settings as boot device and it would work? I am afraid of setting this, so the computer would not boot at all anymore...

vector sigma
vector sigma
Posted
Posted (edited)
12 minutes ago, Funky frank said:

Hi, I am not using emuvariable, but real nvram from the board. I already cleaned the nvram (there were lots of efi-apple-payload entries, but no change).

So could I select the other drive in the macos settings as boot device and it would work? I am afraid of setting this, so the computer would not boot at all anymore...

Looks like is still in your nvram, otherwise how can be printed in your log?. Unless Clover adds this using something like a default volume taken from the config plist... 

Can you show me a screenshot of your nvram using Clover Configurator Pro or nvram -p?

Edited by vector sigma
Funky frank
Funky frank
Posted
Posted
8 minutes ago, vector sigma said:

Looks like is still in your nvram, otherwise how can be printed in your log?. Unless Clover adds this using something like a default volume taken from the config plist... 

Can you show me a screenshot of your nvram using Clover Configurator Pro or nvram -p?

Sure. This is after a nvram clearing and a reboot of Sierra: 

nvram -p
fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j17%00%00%00%00%00
fakesmc-key-RBr -ch8*	j16j17%00%00
EFILoginHiDPI	%01%00%00%00
fakesmc-key-#KEY-ui32	%00%00%00%00
SystemAudioVolumeDB	%80
fakesmc-key-BATP-flag	%00
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSTc-ui8	%00
fakesmc-key-BNum-ui8	%00
security-mode	none
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%02%15%0f%00%00%07
fakesmc-key-MSPS-ui16	%00%03
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%07%a0%07%00
bluetoothActiveControllerInfo	%01%00%12%0a%01%00%00%00%12%1a%00%1a}%daq%0c
nvda_drv	1%00
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	%80
fakesmc-key-RMde-char	A
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%03%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%e0%1f.:%00%00%00%00Q%d2%18%87%d2%ectC%b4%95%aa%b2%d2%ce%a06%02%02%7f%ff%04%00
fakesmc-key-BEMB-flag	%00

 

apianti
apianti
Posted
Posted
8 hours ago, Slice said:

Big thanks for the explanation!

I encountered this message

but I miss words about section.

EDK2 is right. The GUID is defined correctly. It is not protocol and must be defined under [Guids] section as MdePkd did.

Sorry I will remake this solution again. Rev 4437

Yeah, I didn't even look, it just gave that error so I defined it under Protocols, it built for me... I should have moved it in the module to under Guids instead.

4 hours ago, Funky frank said:

Thanks for info.

But on the "OSX" HFS+ partition, there is a 571.960 bytes sized "boot.efi" under /System/Library/CoreServices/boot.efi.

Also more log: 


3:825  0:000  === [ AddCustomTool ] =====================================
3:830  0:005  found tool \EFI\CLOVER\tools\Shell64U.efi
3:830  0:000  Checking EFI partition Volume 8 for Clover
3:831  0:001  Checking EFI partition Volume 11 for Clover
3:845  0:014   Found Clover
3:846  0:000  === [ GetEfiBootDeviceFromNvram ] =========================
3:846  0:000   - found entry 2. 'Boot macOS from OSXSSD', Volume 'OSXSSD', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(2,GPT,8718D221-ECD2-4374-XXXX-AAB2D2CEA036,0x64028,0x3A2E1FE0)\System\Library\CoreServices\boot.efii'
3:846  0:000  DefaultIndex=2 and MainMenu.EntryCount=11
3:875  0:028  GUI ready
5:876  2:001  === [ StartLoader ] =======================================

So it cannot find the boot.efi on "OSX", even if I see here that it is there...

Btw. notice the typo? in the log "boot.efii' instead "boot.efi"...

Also why is it getting the info only from nvram? "GetEfiBootDeviceFromNvram"...

There is something wrong with your partition map or that partition on the disk, as it's not even detected as a file system volume, it might be corrupt, did you run disk repair? The GetEfiBootDeviceFromNvram gets the boot disk selection from what is set in macOS pref pane. Clover will set any disks it boot from appropriately, all that is working fine, it's something to do with the disk.

Matgen84
Matgen84
Posted
Posted (edited)
1 hour ago, Slice said:

It is not Clover affair.

Thanks. Any ideas? Only available with internal hard disk, when  update is finishing, ESP partition is mounted but hidden on Desktop. All work fine for USB Installer.

Edited by Matgen84
chris1111
chris1111
Posted
Posted
7 hours ago, Matgen84 said:

Hi

Please help.

Since r4435, when  update is finishing, ESP partition is mounted but hidden on Desktop??? I don't understand why.

I think HDD mechanical is the cause, thats not append with a SSD

  • Like 1
smolderas
smolderas
Posted
Posted

Is this known: 

clover/src/edk2/MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.inf [X64]
[CC] DxeCapsuleLibNull
[CC] AuthVariableLibNull
[CC] TpmMeasurementLibNull
[CC] DxeServicesTableLib
[CC] InternalGetSpinLockProperties
clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.c:1530:19: error: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Werror,-Wvarargs]
  VA_START (Args, Iso639Language);
                  ^
clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.c:1517:19: note: parameter of type 'BOOLEAN' (aka 'unsigned char') is declared here
  IN BOOLEAN      Iso639Language,
                  ^
[CC] RuntimeLib
1 error generated.
make: *** [clover/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib/OUTPUT/UefiLib.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [clover/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib]


build.py...
 : error F002: Failed to build module
	clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 16:49:23, Apr.13 2018
Build total time: 00:00:44

 

Somehow I can't edit my previous reply.

I'm with NASM_VER: 2.13.03, edk2 @26797 and clover @4439

Slice
Slice
Posted
Posted
13 hours ago, smolderas said:

Is this known: 


clover/src/edk2/MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.inf [X64]
[CC] DxeCapsuleLibNull
[CC] AuthVariableLibNull
[CC] TpmMeasurementLibNull
[CC] DxeServicesTableLib
[CC] InternalGetSpinLockProperties
clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.c:1530:19: error: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Werror,-Wvarargs]
  VA_START (Args, Iso639Language);
                  ^
clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.c:1517:19: note: parameter of type 'BOOLEAN' (aka 'unsigned char') is declared here
  IN BOOLEAN      Iso639Language,
                  ^
[CC] RuntimeLib
1 error generated.
make: *** [clover/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib/OUTPUT/UefiLib.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [clover/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib]


build.py...
 : error F002: Failed to build module
	clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 16:49:23, Apr.13 2018
Build total time: 00:00:44

 

Somehow I can't edit my previous reply.

I'm with NASM_VER: 2.13.03, edk2 @26797 and clover @4439

cp -R Patches_for_EDK2/* ../

apianti
apianti
Posted
Posted (edited)
14 hours ago, ellaosx said:

Can someone update the wiki regarding ACPI>DSDT>Fixes please

The wiki is broken because the authentication does not work and the developer who set it up is no where to be found. There's many other things there that are out of date as well. I don't know what to do about it....

 

13 hours ago, smolderas said:

Yeah, I conditioned that with my previous command "svn up edk2", so it didn't copied over. I removed the condition and it build...

Thanks

You should revert your EDK2 before updating, where EDK2_DIR is your EDK2 path (or ../edk2 if in clover package directly inside EDK2) or you may have merge issues: 

pushd EDK2_DIR
svn revert
svn up
popd

Then copy the patches back.

Edited by apianti
  • Thanks 1
Allan
Allan
Posted
Posted
4 hours ago, apianti said:

There's many other things there that are out of date as well. I don't know what to do about it....

Would be a great idea to update it. If anyone have the complete knowledge about Clover, we can create a "second" Wiki here in IM.

What do you think?

  • Like 4
 Share
Go to topic listing
×
×
  • Create New...