Clover General discussion

chris1111 · December 14, 2019

1 hour ago, Matgen84 said:

After a few days in the hospital, my mind is not clear. Sorry.

Right, my custom script don't embed HFSPlus inside boot 6 or boot7 for my UEFI system. If I understand well, option 2 is optional. Is it mandatory to embed VBoxHFS or HFPlus to Clover Boot I want to use Clover Installer like before.

My english is very bad

curl -L https://raw.githubusercontent.com/JrCs/CloverGrowerPro/master/Files/HFSPlus/X64/HFSPlus.efi -o /tmp/HFSPlus.efi
cp -rp "$3"/tmp/HFSPlus.efi ~/src/CloverBootloader/CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/FileSystem
Sleep 1

rm -rf /tmp/HFSPlus.efi
echo "********************************************** "
echo "HFSPlus Installed done. "

Slice · December 15, 2019

17 hours ago, vector sigma said:

oh, Hope you're be well soon

Is it not mandatory to use this option. HFSPlus should be used only for UEFi boot as boot6/7 already has an HFS driver. I.e. there is no need to add it to drivers/BIOS. If you use both, Is not clear what driver will be used or anyway you are going to load both and I really don't know which one will win or if some conflicts are going to happen.

buildme tells ebuild.sh to use HFSPlus for legacy boot and also add it to the FileSystem drivers for UEFI booting, skipping VboxHfs (so will show up in the pkg). More than one driver is embedded, but if no HFSPlus is provided, VboxHfs will be used anyway.

It was special improvement in CloverEFI (file boot6 or boot7) for external driver will be winner.

It means that if boot6 was compiled with VBosHFS.efi and the folder drivers/BIOS contains HFSPlus.efi then the last will be winner. And vice versa.

tluck · December 15, 2019

On 12/13/2019 at 6:45 AM, artur_pt said:

hello Slice

Clover last commit

thanks

got the same thing? has this been sorted out?

Edited December 16, 2019 by tluck

Slice · December 16, 2019

On 12/14/2019 at 5:14 PM, maleorderbride said:

I am attempting to inject some thunderbolt AAPL,PathProperties via .efi, but am unable to do so in Clover. OpenCore supports it, but Clover does not yet.

Even removing this partial implementation in Clover would be an improvement since then I could use EfiDevicePathPropertyDatabase.efi to enable AAPL,PathProperties injection via .efi, which used to work in older versions of Clover before Clover partially enabled this feature.

Clover since the first day enabled this feature.

telepati · December 17, 2019

On 12/12/2019 at 12:20 PM, Sherlocks said:

thanks slice. after check, i will commit it

EDIT1.

committed

yes we back hardware overview like real mac, if you want it, add NoRomInfo TRUE in smbios part in config.

NoRomInfo is YES but I am still seeing Apple ROM section;

2081403521_ScreenShot2019-12-17at17_36_06.png.3a01666633851dbecae9b5e605ece177.png

714887285_ScreenShot2019-12-17at17_37_09.png.0bddadd357894f74d76c68d76067a003.png

MICKHAEL · December 17, 2019

40 minutes ago, telepati said:

NoRomInfo is YES but I am still seeing Apple ROM section;

well, you have 5100)) and that was from 5101 and up

Matgen84 · December 17, 2019

1 hour ago, telepati said:

NoRomInfo is YES but I am still seeing Apple ROM section;

NoRomInfo is committed 12/12. It works if you compile r5100 from GitHub Repo. Or wait r5101 Release.

Edited December 17, 2019 by Matgen84

pico joe · December 17, 2019

or try this Clover 5100-NoRomInfo.zip

Clover 5100-NoRomInfo.zip

Edited December 17, 2019 by pico joe

Sherlocks · December 18, 2019

build fail with xcode 8 option

Spoiler

Ran 280 tests in 2.430s

OK

Running edk2 build for CloverX64 using the command:

build -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/sherlocks/src/CloverBootloader/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -p Clover.dsc -a X64 -b RELEASE -t XCODE8 -n 5

Build environment: Darwin-19.3.0-x86_64-i386-64bit

Build start time: 21:51:44, Dec.18 2019

WORKSPACE = /Users/sherlocks/src/CloverBootloader

EDK_TOOLS_PATH = /Users/sherlocks/src/CloverBootloader/BaseTools

CONF_PATH = /Users/sherlocks/src/CloverBootloader/Conf

Architecture(s) = X64

Processing meta-data Build target = RELEASE

.Toolchain = XCODE8

Active Platform = /Users/sherlocks/src/CloverBootloader/Clover.dsc

.... done!

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiLib/UefiLib.inf [X64]

Building ... /Users/sherlocks/src/CloverBootloader/MdePkg/Library/UefiRuntimeServicesTableLib/UefiRuntimeServicesTableLib.inf [X64]