Clover General discussion

deeveedee · December 24, 2020

2 hours ago, MacKonsti said:

Hi @tonyx86 has this been confirmed to work with r5xxx release you are using, as the absolute minimum information required for SMBIOS (and by removing/commenting out the others you mention) eventually? Does Clover successfully fill-in the missing data? (the one you use, I mean, r5122 or r5123-1) Thanks... I wish all that extremely useful knowledge would go into some Wiki for everyone (including Google search) to find...

I didn't test much after finding that my attempts to pare down my CLOVER parameters as I mentioned here resulted in iCloud/AppleID problems as I mentioned here. It seems to me that if one were performing a clean install of a system for the first time, only the CLOVER parameters listed below would be necessary. However, if one has already installed CLOVER using the "old" method of specifying everything and has already registered the system with their AppleID, I don't know what parameters can be safely eliminated from the config.plist without making the system look to Apple like a different system. That is why I was trying to determine (with Hackintool) what parameters were changing as I changed my CLOVER config.plist. CLOVER's redundant use of RtVariables > MLB and SMBIOS > BoardSerialNumber still confuse me, especially given that when both are specified, it appears that only RtVariables > MLB is reported by Hackintool as BoardSerialNumber.

Again, I believe you only need to specify the parameters below in your config.plist if configuring a new system for the first time (not previously registered with Apple). I stopped trying to figure out how to pare down an existing config.plist after already registering the system with my AppleID.

RtVariables > MLB
SMBIOS > SerialNumber
SMBIOS > SmUUID
SMBIOS > ProductName

Edited December 24, 2020 by tonyx86

MacKonsti · December 24, 2020

Well, I've been trying to find in Terminal the parameters left out, they don't seem registered in IORegistry, e.g.

ioreg -l | grep -i bios | grep -i vendor
ioreg -l | grep -i bios | grep -i release
ioreg -l | grep -i board | grep -i manuf
ioreg -l | grep -i board | grep -i type
ioreg -l | grep -i chassis | grep -i type
ioreg -l | grep -i chassis | grep -i manuf

Perhaps these aren't the right key names, but you may be right @tonyx86 (even if I never got success with iMessage) I would prefer to use my fully-completed SMBIOS keys, already from ages ago.

But for an emergency USB booted or (re)installation on an another system (with macOS install USB) these minimal keys come in handy.

So for me, in an installed OS with everything working, I would use (and revert to) a fully-described SMBIOS in Config.plist.

Edited December 24, 2020 by MacKonsti

deeveedee · December 24, 2020

4 hours ago, Alpha999 said:

By the way, it seems that mifjpn's account was stolen. I managed to get it back, but I want everyone to be careful.
Thank you.

Sorry to hear that. My account was stolen, too. If I say anything stupid in this forum, it was posted by the person who stole my account. If I say anything smart, it's me.

@Matgen84 - this is a joke.

Edited December 24, 2020 by tonyx86

jsl2000 · January 1, 2021

On 12/23/2020 at 10:08 PM, Slice said:

It is for 10.7 and older systems which are able to load individual kexts instead of prelinkedkernel.

Hi, Slice:

In OpenCore I can fix IOHIDFamily at Big Sur without Find Data, but in Clover I got this error as attached picture:

How can I fix this error as Invalid Find/Replace Data in KextsToPatch or KernelToPatch ?

[Solved incompletely]

In Clover 5127 I need boot by -s then exit way to get USB keyboard/mouse working again which's not so convenient for routine use because it disabled all audio output.

Also I did not favor patcher from MacRumor which fix by hard coding method of system softwares.

[Solved]

In Clover 5127 need fill empty DATA with 000000000000 which fix this issue satisfactorily now !

Edited January 1, 2021 by jsl2000

Slice · January 2, 2021

Set "Find" to any value but with the same length as "Replace". It is 6 bytes.

for example <112233445566>

And then set zero mask "MaskFind" = <000000000000>

It will mean the value of "Find" will be ignored.

Clover's patching ability beats OC patching ability.

MacKonsti · January 2, 2021

Hi everyone, happy new year!

I am facing again build issues... @Jief_Machak had helped me successfully build on my Catalina (sans Xcode) by tweaking the makefile (I think) but when I tried today again, with or without XCODE8 parameter, it fails with error:

build.py...
~/Desktop/CloverGIT/CloverBootloader/Clover.dsc(294): error 000E: File/directory not found in workspace
	~/Desktop/CloverGIT/CloverBootloader/OpenCorePkg/Platform/OpenCore/OpenCoreLib.inf

Here's the complete output on Terminal after doing: git clean f -f -d -x

Spoiler


~/Desktop/CloverGIT/CloverBootloader % git clean f -f -d -x

~/Desktop/CloverGIT/CloverBootloader % ./buildme XCODE8

------------------------------------------------------------------------
buildme, Clover r5127 (SHA: f5ae33896)
TOOLCHAIN: XCODE8 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: 10

[UPDATE CLOVER]
Fetching origin
From https://github.com/CloverHackyColor/CloverBootloader
 * branch                master     -> FETCH_HEAD
Already up to date.

------------------------------------------------------------------------
buildme, Clover r5127 (SHA: f5ae33896)
TOOLCHAIN: XCODE8 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: 13

Are you sure? (type y to confirm or any other to negate) y
[UPDATE RESET CLOVER]
Fetching origin
HEAD is now at f5ae33896 fix capitalization of SMC
From https://github.com/CloverHackyColor/CloverBootloader
 * branch                master     -> FETCH_HEAD
Already up to date.

------------------------------------------------------------------------
buildme, Clover r5127 (SHA: f5ae33896)
TOOLCHAIN: XCODE8 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: 1

[CHECK XCODE]
WORKSPACE: ~/Desktop/CloverGIT/CloverBootloader
EDK_TOOLS_PATH: ~/Desktop/CloverGIT/CloverBootloader/BaseTools
CONF_PATH: ~/Desktop/CloverGIT/CloverBootloader/Conf
Copying $EDK_TOOLS_PATH/Conf/build_rule.template
     to ~/Desktop/CloverGIT/CloverBootloader/Conf/build_rule.txt
Copying $EDK_TOOLS_PATH/Conf/tools_def.template
     to ~/Desktop/CloverGIT/CloverBootloader/Conf/tools_def.txt
Copying $EDK_TOOLS_PATH/Conf/target.template
     to ~/Desktop/CloverGIT/CloverBootloader/Conf/target.txt
[BUILD CLOVER]
TOOLCHAIN_DIR: ~/Desktop/CloverGIT/CloverBootloader/toolchain
MTOC_PREFIX: ~/Desktop/CloverGIT/CloverBootloader/toolchain/bin/
NASM_PREFIX: ~/Desktop/CloverGIT/CloverBootloader/toolchain/bin/
NASM_VER: 2.15.05
Initializing workspace
WORKSPACE: ~/Desktop/CloverGIT/CloverBootloader
EDK_TOOLS_PATH: ~/Desktop/CloverGIT/CloverBootloader/BaseTools
CONF_PATH: ~/Desktop/CloverGIT/CloverBootloader/Conf
Copying $EDK_TOOLS_PATH/Conf/build_rule.template
     to ~/Desktop/CloverGIT/CloverBootloader/Conf/build_rule.txt
Copying $EDK_TOOLS_PATH/Conf/tools_def.template
     to ~/Desktop/CloverGIT/CloverBootloader/Conf/tools_def.txt
Copying $EDK_TOOLS_PATH/Conf/target.template
     to ~/Desktop/CloverGIT/CloverBootloader/Conf/target.txt

Running edk2 build for CloverX64 using the command:
build  -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/XXXX/Desktop/CloverGIT/CloverBootloader/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -p Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9 

Build environment: Darwin-19.6.0-x86_64-i386-64bit
Build start time: 15:04:18, Jan.02 2021

WORKSPACE        = ~/Desktop/CloverGIT/CloverBootloader
EDK_TOOLS_PATH   = ~/Desktop/CloverGIT/CloverBootloader/BaseTools
CONF_PATH        = ~/Desktop/CloverGIT/CloverBootloader/Conf

Processing meta-data 
.Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = ~/Desktop/CloverGIT/CloverBootloader/Clover.dsc

build.py...
~/Desktop/CloverGIT/CloverBootloader/Clover.dsc(294): error 000E: File/directory not found in workspace
	~/Desktop/CloverGIT/CloverBootloader/OpenCorePkg/Platform/OpenCore/OpenCoreLib.inf

- Failed -
Build end time: 15:04:19, Jan.02 2021
Build total time: 00:00:00

(for hiding my username, I replaced in the log above /Users/XXXX/ with ~/ just FYI)

Did anyone manage to fix this error, if encountered? Thanks!

UPDATE:

It seems that by deleting the whole folder and redownloading it all over again, provides a successful build; I only need to test the EFI binaries to confirm. But not sure if this means that any Git changes when obtained, will allow to successfully build new master commits... Perhaps I need to constantly deleting the main folder and re-downloading it? Not sure.

$ git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git
$ cd CloverBootloader
$ ./buildme XCODE8

Edited January 2, 2021 by MacKonsti

Slice · January 2, 2021

When you made

git clone --recurse-submodules

then you downloaded OpenCore from second repository which was absent before.

Max.1974 · January 2, 2021

Hi Guys, im successful can install and run Clover 5127 with Big Sur with my Lenovo, so I have a question, if is possible rename entries in GUI like Preboot ? And its possible hide normal partition that not boot, and rename too Windows partition EFI? (only appears EFI boot from EFI...)

Im try usually configurations but not sure if is possible rename Preboot (boot to Big Sur) on GUI in Clover Configurator.

Edited January 2, 2021 by Max.1974

Slice · January 3, 2021

I don't know about Configurator but there are Custom entries that allow you to rename any entry you want.

The name of Windows entry depends on the entry.

If you want to start from /EFi/BOOT/BOOTX64.EFi then it is "EFI boot from EFI".

If you started from /EFI/Microsoft/boot/bootmgfw.efi then it is "Windows boot from EFI"

Matgen84 · January 3, 2021

Hi @Slice

I have doubts about my local Opencore submodule update. If you have time to look at the two results files, to see if this is normal. Thank you.

Résultat de Terminal

Résultat de Terminal-2

ameenjuz · January 3, 2021

@Slice do not boot sandy bridge machine intel hd graphic 3000 with OpenRuntime.efi high sierra

how to boot high sierra using openrunetime.efi in Clover 5127

kushwavez · January 3, 2021

12 hours ago, Max.1974 said:

Hi Guys, im successful can install and run Clover 5127 with Big Sur with my Lenovo, so I have a question, if is possible rename entries in GUI like Preboot ? And its possible hide normal partition that not boot, and rename too Windows partition EFI? (only appears EFI boot from EFI...)

Im try usually configurations but not sure if is possible rename Preboot (boot to Big Sur) on GUI in Clover Configurator.

Here:

After that:

My question is how can I make Clover to boot this new entry automatically? What do I need to put to "DefaultBootVolume"? Now I can boot it automatically if I write "Preboot" to DefaultBootVolume, but then for example if I have 3 more Big Sur drive then obviously that won't work.

Can I put the ID (for ex. "7434A65C-9925-47BB-A6FE-95753DA18597") to the DefaultBootVolume?

EDIT: Yes, I can. After putting the UUID to DefaultBootVolume now it's automatically booting. Great!

Edited January 3, 2021 by kushwavez

naiclub · January 3, 2021

Now 2 terabytes of disk I broke it :cry: :bye: :no:

iCanaro · January 3, 2021

7 hours ago, ameenjuz said:

@Slice do not boot sandy bridge machine intel hd graphic 3000 with OpenRuntime.efi high sierra

how to boot high sierra using openrunetime.efi in Clover 5127

see clover quirks that i have signed if they can help you

55 minutes ago, LIMITANT said:

How this could happened? Clover is the reason

we're not kidding, a bootloader can't cause a disc to break.

naiclub · January 3, 2021

1 hour ago, LIMITANT said:

How this could happened? Clover is the reason !!! It's SSD or HDD ?

It's not really about the clover boot. Is that it does not boot at all And also pulled the windows down as well A Hard disk rotating disc

24 minutes ago, iCanaro said:

see clover quirks that i have signed if they can help you

we're not kidding, a bootloader can't cause a disc to break.

Yep, it's not about clover.

Edited January 3, 2021 by naiclub

Max.1974 · January 3, 2021

17 hours ago, Slice said:

I don't know about Configurator but there are Custom entries that allow you to rename any entry you want.

The name of Windows entry depends on the entry.

If you want to start from /EFi/BOOT/BOOTX64.EFi then it is "EFI boot from EFI".

If you started from /EFI/Microsoft/boot/bootmgfw.efi then it is "Windows boot from EFI"

Thanks @Slice for everething!!! You are the Man!!!

deeveedee · January 3, 2021

Just booted my rig with CLOVER r5127 for the very first time and on the very first try! I've been selfishly waiting for the dust to clear while many of you have been developing and testing. It is the super-easy bootloader that I've grown to know and love! Well done! I won't risk naming the names for fear of leaving some out, but thank you VERY MUCH for doing an AWESOME job on r5127!

EDIT:

The 'only' major difference I see between CLOVER r5127 and OC 0.6.3 booting Catalina 10.15.7 is something that @MacKonsti previously mentioned: there are more Energy Saver options when booting with OC. I don't really care, but it is curious. When booting with CLOVER r5127, options are 'Put hard disks to sleep...' and 'Wake for Ethernet ...' With OC, the options are as shown... Note that in this particular rig, I'm booting OC 0.6.3 and CLOVER r5127 with a custom DSDT (not using on-the-fly patching) for this (except for Plugin-Type).

Energy Saver Options with OC 0.6.3

Spoiler

274108965_ScreenShot2021-01-03at11_13_07PM.png.6f73f939f9fe0c5de7f41688bd46c2a2.png

Edited January 4, 2021 by tonyx86

Henry2010 · January 4, 2021

Happy new year and wish clover gets better and better! :thumbsup_anim:

MacKonsti · January 4, 2021

12 hours ago, tonyx86 said:

EDIT:

The 'only' major difference I see between CLOVER r5127 and OC 0.6.3 booting Catalina 10.15.7 is something that @MacKonsti previously mentioned: there are more Energy Saver options when booting with OC. I don't really care, but it is curious. When booting with CLOVER r5127, options are 'Put hard disks to sleep...' and 'Wake for Ethernet ...' With OC, the options are as shown... Note that in this particular rig, I'm booting OC 0.6.3 and CLOVER r5127 with a custom DSDT (not using on-the-fly patching) for this (except for Plugin-Type).

Yes and this is strange, considering nothing else has changed at all, no parameters, no SMBIOS nothing.

Plus, on my hack (NUC8i7BEH from Intel) a perfectly working sleep breaks BADLY

I was able to even verify the SLEEP options via Hackintool or pmset -g assertions in Terminal, less options there too!

I hope you figure out faster than me the causes for this @tonyx86 as it seems you were able to invest some studying time this festive season on OC and Clover, certainly more than I did...

EDIT:

@Slice hello, please remind us: From the old days of hackintoshing, I remember VERY WELL that it was fully advised to TICK the option "Startup automatically after a power failure". This was in every guide. Is this still the case? Perhaps it was for Chameleon, and early Clover. Any idea if we need this ticked/active at all times? I have it anyway, from old habits... your feedback would be very significant, as usual. Спасибо

Edited January 4, 2021 by MacKonsti

ameenjuz · January 4, 2021

On 1/3/2021 at 6:31 PM, iCanaro said:

see clover quirks that i have signed if they can help you

we're not kidding, a bootloader can't cause a disc to break.

i don't know what we should say about this guys

he do not give ans clearly and ignore with joking

geticus · January 4, 2021

Hi,

I'm running High Sierra on a Jingsha x99 d8 motherboard, e5-2678 v3, GTX 1060, everything is fine except USB 3.

I finally managed to do an usb mapping with USB.Map by booting with USBInjectAll.kext and XHCI-unsupported.kext but rebooting with USBMap.kext the Usb 3 ports don't work, a usb flash ejects itself, it's very strange, sometimes the usb flash drive appears, sometimes not...

What to do ?

Pene · January 4, 2021

Hi @Slice

Happy new year! How are you?

Your commit which changes Library/OcAppleKernelLib/KextPatcher.c breaks OC Quirk XhciPortLimit (at least for Big Sur).

This is because PatchUsbXhciPortLimit2 targets "__ZN12AppleUSBXHCI11createPortsEv" and in AppleUSBXHCI exist first "__ZN12AppleUSBXHCI11createPortsEv.cold.1" and then "__ZN12AppleUSBXHCI11createPortsEv", so the wrong one is attempted to be patched.

Edited January 4, 2021 by Pene

Slice · January 5, 2021

8 hours ago, Pene said:

Hi @Slice

Happy new year! How are you?

Your commit which changes Library/OcAppleKernelLib/KextPatcher.c breaks OC Quirk XhciPortLimit (at least for Big Sur).

This is because PatchUsbXhciPortLimit2 targets "__ZN12AppleUSBXHCI11createPortsEv" and in AppleUSBXHCI exist first "__ZN12AppleUSBXHCI11createPortsEv.cold.1" and then "__ZN12AppleUSBXHCI11createPortsEv", so the wrong one is attempted to be patched.

Hi @Pene,

Happy New Year!

It is unexpected problem.

I may propose to change

  .Count       = 1,

to 2 to check both procedures.

Slice · January 5, 2021

But where did you find this "__ZN12AppleUSBXHCI11createPortsEv.cold.1"?

MICKHAEL · January 5, 2021

On 1/3/2021 at 11:56 PM, tonyx86 said:

Just booted my rig with CLOVER r5127 for the very first time and on the very first try! I've been selfishly waiting for the dust to clear while many of you have been developing and testing. It is the super-easy bootloader that I've grown to know and love! Well done! I won't risk naming the names for fear of leaving some out, but thank you VERY MUCH for doing an AWESOME job on r5127!

EDIT:

The 'only' major difference I see between CLOVER r5127 and OC 0.6.3 booting Catalina 10.15.7 is something that @MacKonsti previously mentioned: there are more Energy Saver options when booting with OC. I don't really care, but it is curious. When booting with CLOVER r5127, options are 'Put hard disks to sleep...' and 'Wake for Ethernet ...' With OC, the options are as shown... Note that in this particular rig, I'm booting OC 0.6.3 and CLOVER r5127 with a custom DSDT (not using on-the-fly patching) for this (except for Plugin-Type).

Energy Saver Options with OC 0.6.3

Hide contents

I think you have a problem) check again your config

Quote

Edited January 5, 2021 by MICKHAEL
quote image

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