Clover General discussion

[Matgen84]

26 minutes ago, ori said:

 

RAM is marked in the picture ( Corsair CMK64GX4M2D3000C16 64 GB (2x 32 GB) 3000 MHz CL16-20-20-38 1.35 V). I also tried Corsair CMK64GX4M2A2666C16 64 GB (2x 32 GB) 2666 MHz and it was the same.
I lowered it even to the lowest values. I disabled XMP in the BIOS. And it did nothing. I tried with one memory and it didn't start either. It wasn't until somewhere on the forum that I found an entry that someone made a post under SMbios 4x16GB and it went. I don't understand why, but it works with this post.
The processor is i7 9700K. SMbios iMac 19.1.
Gigabyte Z390 M Gamming motherboard. I can also check the Z90 Aorus Pro, but I doubt anything will change.
Interesting that on Open Core enters MacOS. Works well with Windows.
It looks like Clover's problem to me. Because I saw more such posts in the forums. This happens on different motherboards. Clover once had a similar problem with memories in the Asus Z370, where it only saw 2 out of 4 RAM and had to be added manually.

 

 

 

Some users on a banned forum succeed to install Clover + 64GB Ram. Could you post your EFI Folder?

 

You can open a ticket in SourceForge, if you believe Clover's problem

 

@arsradu and me ask you to put complete signature. Please

Edited September 19, 2019 by Matgen84

[Florin9doi]

A ticket is already open: https://sourceforge.net/p/cloverefiboot/tickets/595/

Edited September 19, 2019 by Florin9doi

[ori]

14 minutes ago, Matgen84 said:

 

Some users on a banned forum succeed to install Clover + 64GB Ram. Could you post your EFI Folder?

 

You can open a ticket in SourceForge, if you believe Clover's problem

 

@arsradu and me ask you to put complete signature. Please

 

I understand that other forums are blocked here, but I found only one example in this forum. Google has shown more.
I tried 2x16GB, 4x16GB and no problem.
I have 128GB of RAM on X299 and no problem with Clover.
It seems to me an allocation error when configuring the Z390 and 32GB of RAM.

[Matgen84]

16 minutes ago, Florin9doi said:

A ticket is already open: https://sourceforge.net/p/cloverefiboot/tickets/595/

 

There is a interesting answer

 

 

9 minutes ago, ori said:

 

I understand that other forums are blocked here, but I found only one example in this forum. Google has shown more.
I tried 2x16GB, 4x16GB and no problem.
I have 128GB of RAM on X299 and no problem with Clover.
It seems to me an allocation error when configuring the Z390 and 32GB of RAM.

 

What AptioFix did you use? Try to use Free2000 version.

 

EDIT: What BIOS for your Z390 M Gaming?

Edited September 19, 2019 by Matgen84

[ori]

4 minutes ago, Matgen84 said:

 

There is a interesting answer

 

 

 

What AptioFix did you use? Try to use Free2000 version.

 

I tried AptioMemoryFix.efi and OsxAptioFix2Drv-free2000.efi. At Clover he always stays in the same place.
On Open Core I have OsxAptioFix2Drv-free2000.efi
 

[Matgen84]

5 minutes ago, ori said:

 

I tried AptioMemoryFix.efi and OsxAptioFix2Drv-free2000.efi. At Clover he always stays in the same place.
On Open Core I have OsxAptioFix2Drv-free2000.efi
 

 

What BIOS version? Set DVMT Pre-Allocated to 32M. This single change enabled the use of the standard driver OsxAptioFix3Drv.efi

[arsradu]

25 minutes ago, ori said:

 

I understand that other forums are blocked here, but I found only one example in this forum. Google has shown more.
I tried 2x16GB, 4x16GB and no problem.
I have 128GB of RAM on X299 and no problem with Clover.
It seems to me an allocation error when configuring the Z390 and 32GB of RAM.

 

Ok, so it is a problem with this specific configuration.

 

I'm guessing the RAM sticks are in the correct slots according to the motherboard's user manual, right?

 

Just trying to exclude the most common mistakes.  Cause if everything is done correctly (and my guess is that it is)...then the most unlikely possibility becomes the only logical one.

[iCanaro]

tested boot arguments

 

slide=0

[ori]

11 minutes ago, Matgen84 said:

 

What BIOS version? Set DVMT Pre-Allocated to 32M. This single change enabled the use of the standard driver OsxAptioFix3Drv.efi

BIOS:

 

Driver:

ApfsDriverLoader.efi
DataHubDxe.efi
FSInject.efi
OsxAptioFix3Drv.efi
PartitionDxe.efi
SMCHelper.efi
VBoxHfs.efi

 

Still the same.

I tried the same drivers as I have in Open Core (ApfsDriverLoader.efi HfsPlus.efi OsxAptioFix2Drv-free2000.efi) and it also doesn't work on Clover

 

 

1 minute ago, arsradu said:

 

Ok, so it is a problem with this specific configuration.

 

I'm guessing the RAM sticks are in the correct slots according to the motherboard's user manual, right?

 

Just trying to exclude the most common mistakes.  Cause if everything is done correctly (and my guess is that it is)...then the most unlikely possibility becomes the only logical one.

I tried singly, twice in each slot. The effect is the same.

3 minutes ago, iCanaro said:

tested boot arguments

 

slide=0

 

slide=0 dart=0 darkwake=no keepsyms=1 debug=0x100

The effect is the same.

[Matgen84]

11 hours ago, ori said:

BIOS:
Driver:

ApfsDriverLoader.efi
DataHubDxe.efi
FSInject.efi
OsxAptioFix3Drv.efi
PartitionDxe.efi
SMCHelper.efi
VBoxHfs.efi

 

Still the same.

I tried the same drivers as I have in Open Core (ApfsDriverLoader.efi HfsPlus.efi OsxAptioFix2Drv-free2000.efi) and it also doesn't work on Clover

 

 

I tried singly, twice in each slot. The effect is the same.

 

slide=0 dart=0 darkwake=no keepsyms=1 debug=0x100

The effect is the same.

 

Multiple time, I asked you to post your EFI Folder???

 

Try to contact @MaLd0n here or on olarila.com, he have the same mobo but with i9-9900K

 

 

[Sherlocks]

@Slice

real mac smbios info from system profiler

like this

https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27749989

 

but we always include apple rom info

 

can we choice enable/disable to hide this apple rom info part?

[Slice]

2 hours ago, Sherlocks said:

@Slice

real mac smbios info from system profiler

like this

https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27749989

 

but we always include apple rom info

 

 

can we choice enable/disable to hide this apple rom info part?

It is also hackintosh, see Lilu on screens.

Real Mac doesn't show this info if it has SMBIOS 3.0. To do this in Clover we have to remake a huge part of codes.

[Sherlocks]

27 minutes ago, Slice said:

It is also hackintosh, see Lilu on screens.

Real Mac doesn't show this info if it has SMBIOS 3.0. To do this in Clover we have to remake a huge part of codes.

i think

if apple rom info shown on t2 chip or each model smbios version, we just divide part according to model.

[Badruzeus]

Still curious how VMWare did this uhmmb...

[Slice]

5 hours ago, Sherlocks said:

i think

if apple rom info shown on t2 chip or each model smbios version, we just divide part according to model.

We can't produce smbios3 until we will know all details what is allowed and what influences on system.

[Matgen84]

Hi @vector sigma @Slice

 

Thanks a lot for last commit on Clover Template 

 

It is possible to have: Clover v2.5 RELEASE (nb_commits-last-commits) both in Installer and Read Info (Version line).

[vector sigma]

53 minutes ago, Matgen84 said:

It is possible to have: Clover v2.5 RELEASE (nb_commits-last-commits) both in Installer and Read Info (Version line).

No because breaks Clover updater

[artur_pt]

hello

 

with new Xcode 11 buildme

 

is giving me this error compiling gettext

 

gettext.make.log.txt.zip

 

thanks

[vector sigma]

56 minutes ago, artur_pt said:

hello

 

with new Xcode 11 buildme

 

is giving me this error compiling gettext

 

gettext.make.log.txt.zip

 

thanks

Hi, what's the result of 'which libtool'?

[artur_pt]

30 minutes ago, vector sigma said:

Hi, what's the result of 'which libtool'?

 

hello

 

i set to buildme xcode8

 

thanks

[vector sigma]

3 minutes ago, artur_pt said:

 

hello

 

i set to xcode8

 

thanks

Anyway I've just chaged buildgettext.sh to use default PATH enviroment variable, so it should use default and expected command lines.

 

P.S. at github atm

[artur_pt]

3 hours ago, vector sigma said:

Anyway I've just chaged buildgettext.sh to use default PATH enviroment variable, so it should use default and expected command lines.

 

P.S. at github atm

hello

 

sorry not solved

 

 

thanks

[Matgen84]

Hi @artur_pt @vector sigma

 

All works fine here: XCode11/ Builme (Github) on my Mojave rig

 

• option 7: update Clover 
• option 2: make pkg

gettext 0.20.1 installed correctly

Edited September 22, 2019 by Matgen84

[artur_pt]

hello

 

not here

 

gettext 0.20.1 error compiling

 

Catalina last beta with Xcode 11

 

anyway if I use opt folder from Mojave, works good

 

thanks

 

Edited September 22, 2019 by artur_pt

[fusion71au]

On 9/21/2019 at 9:15 PM, vector sigma said:

' I got this:

------------------------------------------------------------------------
cat: vers.txt: No such file or directory
buildme, Clover v2.5k r (SHA: not a git repo)

Anyway we can ask Mr. @fusion71au if can test the chage in Linux....

 

Well on my system it worked even when not symlink, but it doesn't matter really. Your version:

On 9/21/2019 at 3:55 AM, vector sigma said:

 

cd "$(dirname $([ -L $0 ] && readlink $0 || echo $0))"

 

is probably better as it works on both of our system.

Remains to be tested in linux...

 

 

 

@vector sigma and @Pene,

 

Either

cd "$(dirname "$(readlink "$0")")"

or

cd "$(dirname $([ -L $0 ] && readlink $0 || echo $0))"

 

works in Linux Mint 19.1, running buildme script from link (in secondary location) to actual script in ~/src/CloverBootloader...

fusion71au@GA-P55A-UD3:~$ cd src
fusion71au@GA-P55A-UD3:~/src$ ./buildme

------------------------------------------------------------------------
buildme, Clover v2.5k r5089 (SHA: 0f1bca80)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) make pkg
 3) make iso
 4) build all
 5) test build (no autogen, no boot files)
 6) status
 7) update Clover
 8) update Clover (reset changes)
 9) show diff
10) open drivers directory
11) clean BaseTools
12) quit
Please enter your choice: 1
Loading previous configuration from /home/fusion71au/src/CloverBootloader/Conf/BuildEnv.sh
WORKSPACE: /home/fusion71au/src/CloverBootloader
EDK_TOOLS_PATH: /home/fusion71au/src/CloverBootloader/BaseTools
CONF_PATH: /home/fusion71au/src/CloverBootloader/Conf
[BUILD CLOVER]
TOOLCHAIN_DIR: /home/fusion71au/src/CloverBootloader/../opt/local
No clover toolchain found !
Install on your system or define the TOOLCHAIN_DIR variable.

Notice the buildme script in Linux is not fully automatic since I still need to run source edksetup.sh in order to set correct TOOLCHAIN_DIR in /usr...

 

Spoiler

fusion71au@GA-P55A-UD3:~/src$ cd CloverBootloader
fusion71au@GA-P55A-UD3:~/src/CloverBootloader$ source edksetup.sh
Loading previous configuration from /home/fusion71au/src/CloverBootloader/Conf/BuildEnv.sh
WORKSPACE: /home/fusion71au/src/CloverBootloader
EDK_TOOLS_PATH: /home/fusion71au/src/CloverBootloader/BaseTools
CONF_PATH: /home/fusion71au/src/CloverBootloader/Conf
fusion71au@GA-P55A-UD3:~/src/CloverBootloader$ ./ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -t GCC53
TOOLCHAIN_DIR: /usr
NASM_PREFIX: /usr/bin/
NASM_VER: 2.13.02
Building from: /home/fusion71au/src/CloverBootloader

Running edk2 build for CloverX64 using the command:
build  -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER --conf=/home/fusion71au/src/CloverBootloader/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -p Clover.dsc  -a X64 -b RELEASE -t GCC53 -n 5 

Build environment: Linux-4.15.0-64-generic-x86_64-with-LinuxMint-19.1-tessa
Build start time: 08:37:29, Sep.23 2019

WORKSPACE        = /home/fusion71au/src/CloverBootloader
EDK_TOOLS_PATH   = /home/fusion71au/src/CloverBootloader/BaseTools
CONF_PATH        = /home/fusion71au/src/CloverBootloader/Conf


Architecture(s)  = X64

Processing meta-data .Build target     = RELEASE
Toolchain        = GCC53

Active Platform          = /home/fusion71au/src/CloverBootloader/Clover.dsc
.... done!
Building ... /home/fusion71au/src/CloverBootloader/Library/MemLogLibDefault/MemLogLibDefault.inf [X64]
Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull.inf [X64]
Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]
Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/UefiLib/UefiLib.inf [X64]
Building ... /home/fusion71au/src/CloverBootloader/MdePkg/Library/BasePciLibCf8/BasePciLibCf8.inf [X64]

 

 

PS:  I can't reply in original thread since I am not a developer