Jump to content

Clover General discussion


ErmaC
29,818 posts in this topic

Recommended Posts

Is it possible to fix this small windows where you choose which drive to mount (EFI mount)?

 

Before update for SIerra, windows showed all drives (EFI) without scroll.

I'm afraid I don't think this has anything to do with Slice and Co (Clover Developers) you'll have to contact Clover Configurator developer.

Link to comment
Share on other sites

@davidm71,

 

You can compile it yourself with @Micky1979's Build_Clover.command script (prerequisite: needs Xcode).  Easiest to choose option 3 ---> downloads Clover source and compiles/builds the standard Clover package installer in the ~/src/edk2/Clover/CloverPackage/sym folder.  Alternatively, choose option 2 first (to get latest Clover source & sync edk2), then option 6 or 7 to build the package installer.

 

I have attached the BOOTX64.efi from Clover r3781 to this post (replace the one in your EFI partition's EFI/Boot folder and also EFI/CLOVER folder with BOOTX64.efi renamed as CLOVERX64.efi).

 

To "clean" the build, use terminal....

cd ~/src/edk2/Clover
./ebuild.sh cleanall
./ebuild.sh cleanpkg

BOOTX64.zip

Link to comment
Share on other sites

@davidm71,

 

You can compile it yourself with @Micky1979's Build_Clover.command script (prerequisite: needs Xcode).

 

I have attached the BOOTX64.efi from Clover r3781 to this post (replace the one in your /EFI/Boot folder and also /EFI/CLOVER/CLOVERX64.efi).

 

Thanks Fusion,

 

I appreciate the file though I am a little confused which option I need to select? If I select update will it update my existing Clover install? What if i just want to build the installer? Also do I copy BootX64.efi to my EFI partition you mean? And replace Cloverx64 with Bootx64 -- should I rename it after?

 

Thanks

 

Edit: Also how do you "clean" the build if you want to recompile if you made mistakes?

 

Thanks again

Link to comment
Share on other sites

@Slice and Clover gurus.

 

I was playing around with the different clover configurations when I noticed this:

81:248  0:000  first CPU found at 2D32 offset 2D36
81:248  0:000  device candidate at 2C99
81:248  0:000  device inserted in acpi_cpu_score SCK0
81:248  0:000  score candidate at 2AAD
81:248  0:000  score inserted in acpi_cpu_score _SB_SCK0
81:248  0:000  Found ACPI CPU: CP00 | CP01 | CP02 | CP03 | CP04 | CP05 | CP06 | CP07 | CP08 | CP09 | CP0A | CP0B | CP0C | CP0D | CP0E | CP0F | CP10 | CP11 | CP12 | CP13 | CP14 | CP15 | CP16 | CP17 | CP18 | CP19 | CP1A | CP1B | CP1C | CP1D | CP1E | CP1F , within the score: _SB_SCK0
81:248  0:000  Found PCIROOTUID = 0
81:248  0:000  === [ ACPIDropTables ] ====================================
81:248  0:000  Drop tables from Xsdt, SIGN=DMAR TableID=A M I  Length=248
81:248  0:000   Xsdt has tables count=20
81:248  0:000   Table: DMAR  A M I   248 dropped
81:248  0:000  corrected XSDT length=188
81:248  0:000  === [ PatchAllSSDT ] ======================================
81:248  0:000  Patch table: SSDT  PmMgt
81:248  0:000   SSDT len = 0x1700F
81:248  0:000  Patch table: SSDT  SpsNm   
81:248  0:000   SSDT len = 0x2652
81:248  0:000  Patch table: SSDT  SpsNvs  
81:248  0:000   SSDT len = 0x64
81:248  0:000  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
81:248  0:000   Xsdt has tables count=19
81:248  0:000  corrected XSDT length=188
81:248  0:000  Out of control with CPU numbers
81:248  0:000  CPUBase=0 and ApicCPUBase=0 ApicCPUNum=22

Since I have 2 cpus clover only get scope from the _SB_SCK0 and not _SB_SCK0 and _SB_SCK1 is this normal,  ACPI issue or a bug?

 

And: Out of control with CPU numbers

 

 

And for some odd reasons it doesn't detect all 16 memory slots with 8 slots populated.

Total Memory Slots Count = 4
0:101  0:000  Type 17 Index = 0
0:101  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:101  0:000  SmbiosTable.Type17->Size = 16384MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A1
0:101  0:000  SmbiosTable.Type17->Vendor = Micron
0:101  0:000  SmbiosTable.Type17->SerialNumber = 12167707
0:101  0:000  SmbiosTable.Type17->PartNumber = 36ASF2G72PZ-2G1B1  
0:101  0:000  Type 17 Index = 1
0:101  0:000  Ignoring insane frequency value 0MHz
0:101  0:000  SmbiosTable.Type17->Speed = 0MHz
0:101  0:000  SmbiosTable.Type17->Size = 0MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A2
0:101  0:000  SmbiosTable.Type17->Vendor = <null string>
0:101  0:000  SmbiosTable.Type17->SerialNumber = <null string>
0:101  0:000  SmbiosTable.Type17->PartNumber = <null string>
0:101  0:000  Type 17 Index = 2
0:101  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:101  0:000  SmbiosTable.Type17->Size = 16384MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B1
0:101  0:000  SmbiosTable.Type17->Vendor = Micron
0:101  0:000  SmbiosTable.Type17->SerialNumber = 121676FD
0:101  0:000  SmbiosTable.Type17->PartNumber = 36ASF2G72PZ-2G1B1  
0:101  0:000  Type 17 Index = 3
0:101  0:000  Ignoring insane frequency value 0MHz
0:101  0:000  SmbiosTable.Type17->Speed = 0MHz
0:101  0:000  SmbiosTable.Type17->Size = 0MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B2
0:101  0:000  SmbiosTable.Type17->Vendor = <null string>
0:101  0:000  SmbiosTable.Type17->SerialNumber = <null string>
0:101  0:000  SmbiosTable.Type17->PartNumber = <null string>

Thanks a lot

 

Link to comment
Share on other sites

Build_Clover.command doesn't touch your existing install it just creates a new installer.

 

If I need to correct a compile error I just delete the /src folder as everything the command does is in there.

Well the first time I compiled the new release osx complained it needed Java and I noticed an error or two. So I installed Java and recompiled once again no issues. Then installed the new clover build onto a USB key not knowing the script also manages to update your existing Clover install. Thank god nothing was corrupted and it worked. Just wish the options on the script menu where a little bit more clear for us first timers. Anyhow was fun. Now can't wait to install multiple config.plist files. Wonder how that works..

 

Thanks

Build_Clover.command doesn't touch your existing install it just creates a new installer.

 

If I need to correct a compile error I just delete the /src folder as everything the command does is in there.

Well the first time I compiled the new release osx complained it needed Java and I noticed an error or two. So I installed Java and recompiled once again no issues. Then installed the new clover build onto a USB key not knowing the script also manages to update your existing Clover install. Thank god nothing was corrupted and it worked. Just wish the options on the script menu where a little bit more clear for us first timers. Anyhow was fun. Now can't wait to install multiple config.plist files. Wonder how that works..

 

Thanks

Build_Clover.command doesn't touch your existing install it just creates a new installer.

 

If I need to correct a compile error I just delete the /src folder as everything the command does is in there.

Well the first time I compiled the new release osx complained it needed Java and I noticed an error or two. So I installed Java and recompiled once again no issues. Then installed the new clover build onto a USB key not knowing the script also manages to update your existing Clover install. Thank god nothing was corrupted and it worked. Just wish the options on the script menu where a little bit more clear for us first timers. Anyhow was fun. Now can't wait to install multiple config.plist files. Wonder how that works..

 

Thanks

Link to comment
Share on other sites

It's gettext that prompts for java when being built. I just ignored it and didn't install java. Clover still builds ok.

Right  :yes:

Then installed the new clover build onto a USB key not knowing the script also manages to update your existing Clover install. 

Wrong, Build_Clover.commad is a script to compile Clover, not to install it. After the package is compiled you can use it...  at your will and risk only.

 

 Just wish the options on the script menu where a little bit more clear for us first timers. Anyhow was fun. Now can't wait to install multiple config.plist files. Wonder how that works..

Sorry I cannot make it more Clear:

Please enter your choice: 
 1) update Build_Clover.command
 2) update Clover only (no building)
 3) update & build Clover
 4) run my script on the source
 5) build existing revision (no update, for testing only)
 6) build existing revision for release (no update, standard build)
 7) build existing revision with custom macros enabled
 8) info and limitations about this script
 9) enter Developers mode (only for devs)
10) Exit

.. but you use always option 3, so you will have latest Clover.

Also sorry, this script is an automation and allow you to build Clover, but surely cannot solve some errors or typo that may occur in new commits (is normal during development) or if your internet connection is reset by peers downloading or updating the source. It's a script and have no brain .. this part is expected from you :D

  • Like 1
Link to comment
Share on other sites

Right  :yes:

Wrong, Build_Clover.commad is a script to compile Clover, not to install it. After the package is compiled you can use it...  at your will and risk only.

 

 

Sorry I cannot make it more Clear:

Please enter your choice: 
 1) update Build_Clover.command
 2) update Clover only (no building)
 3) update & build Clover
 4) run my script on the source
 5) build existing revision (no update, for testing only)
 6) build existing revision for release (no update, standard build)
 7) build existing revision with custom macros enabled
 8) info and limitations about this script
 9) enter Developers mode (only for devs)
10) Exit

.. but you use always option 3, so you will have latest Clover.

Also sorry, this script is an automation and allow you to build Clover, but surely cannot solve some errors or typo that may occur in new commits (is normal during development) or if your internet connection is reset by peers downloading or updating the source. It's a script and have no brain .. this part is expected from you :D

 

Thanks. Even though it was a late night I swear I hit option 3 and I swear my efi folder got updated with newest version. Only thing i do not understand

is why i have to copy that bootX64.efi file over to the efi folder?

 

Thanks

Link to comment
Share on other sites

On fresh installed systems clover doesn't install in UEFI's ESP partition, i have to manually mount it then proceed with installation. Clover installer instead copies the files at root directory of OSX. 

Link to comment
Share on other sites

@Slice and Clover gurus.

 

I was playing around with the different clover configurations when I noticed this:

81:248  0:000  first CPU found at 2D32 offset 2D36
81:248  0:000  device candidate at 2C99
81:248  0:000  device inserted in acpi_cpu_score SCK0
81:248  0:000  score candidate at 2AAD
81:248  0:000  score inserted in acpi_cpu_score _SB_SCK0
81:248  0:000  Found ACPI CPU: CP00 | CP01 | CP02 | CP03 | CP04 | CP05 | CP06 | CP07 | CP08 | CP09 | CP0A | CP0B | CP0C | CP0D | CP0E | CP0F | CP10 | CP11 | CP12 | CP13 | CP14 | CP15 | CP16 | CP17 | CP18 | CP19 | CP1A | CP1B | CP1C | CP1D | CP1E | CP1F , within the score: _SB_SCK0
81:248  0:000  Found PCIROOTUID = 0
81:248  0:000  === [ ACPIDropTables ] ====================================
81:248  0:000  Drop tables from Xsdt, SIGN=DMAR TableID=A M I  Length=248
81:248  0:000   Xsdt has tables count=20
81:248  0:000   Table: DMAR  A M I   248 dropped
81:248  0:000  corrected XSDT length=188
81:248  0:000  === [ PatchAllSSDT ] ======================================
81:248  0:000  Patch table: SSDT  PmMgt
81:248  0:000   SSDT len = 0x1700F
81:248  0:000  Patch table: SSDT  SpsNm   
81:248  0:000   SSDT len = 0x2652
81:248  0:000  Patch table: SSDT  SpsNvs  
81:248  0:000   SSDT len = 0x64
81:248  0:000  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
81:248  0:000   Xsdt has tables count=19
81:248  0:000  corrected XSDT length=188
81:248  0:000  Out of control with CPU numbers
81:248  0:000  CPUBase=0 and ApicCPUBase=0 ApicCPUNum=22
Since I have 2 cpus clover only get scope from the _SB_SCK0 and not _SB_SCK0 and _SB_SCK1 is this normal,  ACPI issue or a bug?

 

And: Out of control with CPU numbers

 

I checked and found this message is safe.

May be Patch APIC will be not correct. But sorry I have no knowledge what to do with it in your case.

 

And for some odd reasons it doesn't detect all 16 memory slots with 8 slots populated.

Total Memory Slots Count = 4
0:101  0:000  Type 17 Index = 0
0:101  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:101  0:000  SmbiosTable.Type17->Size = 16384MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A1
0:101  0:000  SmbiosTable.Type17->Vendor = Micron
0:101  0:000  SmbiosTable.Type17->SerialNumber = 12167707
0:101  0:000  SmbiosTable.Type17->PartNumber = 36ASF2G72PZ-2G1B1  
0:101  0:000  Type 17 Index = 1
0:101  0:000  Ignoring insane frequency value 0MHz
0:101  0:000  SmbiosTable.Type17->Speed = 0MHz
0:101  0:000  SmbiosTable.Type17->Size = 0MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_A2
0:101  0:000  SmbiosTable.Type17->Vendor = <null string>
0:101  0:000  SmbiosTable.Type17->SerialNumber = <null string>
0:101  0:000  SmbiosTable.Type17->PartNumber = <null string>
0:101  0:000  Type 17 Index = 2
0:101  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:101  0:000  SmbiosTable.Type17->Size = 16384MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B1
0:101  0:000  SmbiosTable.Type17->Vendor = Micron
0:101  0:000  SmbiosTable.Type17->SerialNumber = 121676FD
0:101  0:000  SmbiosTable.Type17->PartNumber = 36ASF2G72PZ-2G1B1  
0:101  0:000  Type 17 Index = 3
0:101  0:000  Ignoring insane frequency value 0MHz
0:101  0:000  SmbiosTable.Type17->Speed = 0MHz
0:101  0:000  SmbiosTable.Type17->Size = 0MB
0:101  0:000  SmbiosTable.Type17->Bank/Device = NODE 1 DIMM_B2
0:101  0:000  SmbiosTable.Type17->Vendor = <null string>
0:101  0:000  SmbiosTable.Type17->SerialNumber = <null string>
0:101  0:000  SmbiosTable.Type17->PartNumber = <null string>

Thanks a lot

 

This is a big problem of 2 controllers SPD. We didn't find a solution for this case.

Link to comment
Share on other sites

Hi,

 

Was wondering if Clover installer has ability to format the efi partition fat32? Even on a newly partitioned hard drive?

 

Thanks

 

Ps: Reason I ask is because my uefi bios refused to recognize the efi partition to create a custom boot entry unless I format the efi partition myself.

Link to comment
Share on other sites

:cry:

 

Hi,

Was wondering if Clover installer has ability to format the efi partition fat32? Even on a newly partitioned hard drive?

Thanks

Ps: Reason I ask is because my uefi bios refused to recognize the efi partition to create a custom boot entry unless I format the efi partition myself.

??? Sorry Sir... but are you serious? :blush:

Clover pkg would be a crazy/foolish installer doing that. Fortunately this cannot be happen, it only try to mount it.

maybe you mean that you mount  and not that you format it?

On a newly partitioned hard drive the EFI Partition already exist if GPT formatted. 

 

check your partitions by copy paste this in Terminal.app:

diskutil list

and post the result. Probably you have a coreStorage Volume somewhere..

Link to comment
Share on other sites

@davidm71 -

 

how did you create the partition scheme on your disk? meaning what tool/OS was used. its not common in my experience to have to format the ESP.

typical tools will create the GUID scheme or individual partitions and the format the partitions (i.e. create the filesystems). for example, using diskutil (or disk utility.app) will create and format the EFI partition for example. where as a tool like gtp will just make the partitions.

 

so beside using diskutil to list a disk, i recommend using gpt to see if you have PMBR or MBR on the GUID disk. sometimes a MBR (vs PMBR) will mess up UEFI.

$ sudo gpt -r show disk0
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6        
          40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640   998536000      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
   998945640     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
  1000215176           7        
  1000215183          32         Sec GPT table
  1000215215           1         Sec GPT header

$ diskutil list disk0
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *512.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS OSX+                    511.3 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
Link to comment
Share on other sites

To Mickey1979 and Tluck,

 

Honestly I can't recall how the partitions were originally created as far as Chimera being there once or just a virgin install followed by Clover install. Though I probably used Diskutility app to create GUID partition scheme  with a standard case insensitive HFS partition where I would have installed El Capitan. Every now and then I may have used Carbon copy cloner to copy one partition from one disk to another freshly created backup disk, and then ran the Clover installer upon it to recreate the efi partition. My diskutil list commands always produced disk layouts that looked like the one above you posted Tluck. There would be the EFI EFI disk1s1 partition, the Apple HFS partition, and the Recovery partition just like you described and I swear the EFI partition was  fat32 according to Diskutil info.

 

So the problem I was trying to solve originally was that no matter what disk I selected to boot from on the bios boot menu the config.plist and theme was being loaded from the first disk in the system as opposed to separate independant installs. Not only that in the EFI shell booted straight from bios (or within the UEFI booted Clover bootloader) some of my disks were missing and I couldn't create UEFI boot entries using BCFG until I formated the EFI partition using: newfs_msdos -v EFI /dev/disk0s1 and then reinstalling Clover and setting the boot0af option on the Clover install dialogue. After that even the UEFI Clover Bootloader was able to see the other installs and even better loading config.plist and theme from the selected UEFI bios boot option.

 

This system is running an old Asus Z68 Deluxe motherboard that doesn't have the best UEFI support and compatibility even with the supplied Clover EFI shell efi program. Theres a special shellx64 efi program I found thats compatible so if anyone else is having this issue you need it. Any I suspected perhaps it was an UEFI compatibility issue or the disk signature was at fault but I also read that EFI shells only can view fat32 formated partitions. So I thought it was the msdos fat32 patition at fault and I thought it would be useful for clover installer to format the EFI partition when installing upon a fresh install to prevent this kind of a problem.  I mean I'm not an expert and it was just an idea Mickey so please forgive me if I am in error.

 

Thanks.

Link to comment
Share on other sites

Hello guys,

 

from https://clover-wiki.zetam.org/Configuration/Devices#FakeID

 

This substitution will work if InjectATI (Nvidia, Intel) is set. Or if FixDsdtMask set for the device.

Likewise, the IMEI fix will only work if the DSDT Patch AddMCHC_0008 is enabled.

Does this mean the SATA FakeID will only work if FixSATA_0400 is set?

Thanks.

Link to comment
Share on other sites

my hibernate mode become 3 (presumably when I upgraded to Sierra) by mistake. So today on wake from sleep I get a panic. no big deal. but quickly i found out there is a sleep image when i restart.

 

Im on Clover 3786 and it will not ignore the sleep image. I hit space bar and check hibernate wake. right? what am i missing.  ( i turned hibernate off for now)  but there used to be an option to get around hibernation image if desired. (mode  7 works for hibernation if i need/want it). i had to boot from another disk and manually remove /var/vm/sleepimage

 

maybe a bug? if so move to appropriate topic. thanks

Link to comment
Share on other sites

my hibernate mode become 3 (presumably when I upgraded to Sierra) by mistake. So today on wake from sleep I get a panic. no big deal. but quickly i found out there is a sleep image when i restart.

 

Im on Clover 3786 and it will not ignore the sleep image. I hit space bar and check hibernate wake. right? what am i missing. ( i turned hibernate off for now) but there used to be an option to get around hibernation image if desired. (mode 7 works for hibernation if i need/want it). i had to boot from another disk and manually remove /var/vm/sleepimage

 

maybe a bug? if so move to appropriate topic. thanks

I have same issue about hibernate.

 

Can you use hibernate wake option?

 

It means system with hibernate can booting. If my system have hibernate status(sleep or deep sleep or etc), i cant booting with "hibernate wake" option. My system isnt work hibernate mode.

 

Therefore i have to use "cancel hibernate wake". This option exist in OLD GUI.

 

 

I reported this issue. But surely not clear now in latest clover.

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

×
×
  • Create New...