Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

chris1111
chris1111
Posted
Posted

Where abouts in src can i find the gui for clover? specifically the final screen.

src/edk2/Clover/CloverPackage/Package/Resources/Templates/Concusion.html

Open with Xcode's for editing the file

This is what you want ?

 

Post édit

Link to comment
Share on other sites
ccphuc2016
ccphuc2016
Posted
Posted

used latest Clover 4182 and Unplug Windows SSD

 

where link dowload clover 4182 thank

 

my pc install macos sierra 10.13 public beta 7 safe mode to macos but use clover 4173 restart back green just boot safe mode go to macos

Link to comment
Share on other sites
ccphuc2016
ccphuc2016
Posted
Posted

thank i use clover 4184 install to  USB "Boot Disk Ulitity" make USB clover 4173 and boot  "macos High Sierra 10.13 beta 7" OK

 

thank alot

 

clover 4173  12.2Mb not work why clover 4184 just 4.2mb work very well ?

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

thank i use clover 4184 install to  USB Boot Disk Ulitity make USB clover 4173 boot to macos Ok

 

thank alot

 

clover 4173  12.2Mb not work why clover 4184 just 4.2mb work very well ?

Clover 4184 is more suitable for the latest Beta

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

src/edk2/CloverPackage/Package/Resources/Templates/Concusion.html

Open with Xcode's for editing the file

This is what you want ?

Doesn't exist (file and folder) in my ~src directory?  :)

 

 

Edit: sorry,, I found it in src/edk2/Clover/CloverPackage/Package/Resources/Templates/Conclusion.html

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Doesn't exist (file and folder) in my ~src directory?  :)

 

 

Edit: sorry,, I found it in src/edk2/Clover/CloverPackage/Package/Resources/Templates/Conclusion.html

Yes sorry I forgot this

Clover

  • Like 1
Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

fusion71au: You did install into efi partition. That makes the whole thing very complicated and hard to manage, also for noobs. Clover should also boot if the hdd has an efi partition, but clover was started in legacy mode. Please fix boot0 so it also has a look onto partition 2 for boot1h / boot1h2 and not partition 1 only.

 

Or add boot0md to the clover installer as an option.

 

Or build a boot0md variant, only for the same hdd, not multiple.

Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

Or add boot0md to the clover installer as an option...

If you build your own Clover, you can edit ~/src/edk2/Clover/CloverPackage/package/buildpkg.sh 

and replace all references to boot0ss with boot0md ---> have installer option to install boot0md in MBR in place of boot0ss (or boot0af).

 

post-846696-0-72160500-1503530139_thumb.png

 

 

What you are trying to achieve (install legacy Clover to HFS partition on GPT drive) probably requires the creation of a Hybrid MBR before it will work - you can use gdisk or simply add a FAT partition with Disk Utility to create the Hybrid MBR.

 

IMHO, with a GPT formatted drive, it is still preferable to install Clover to the EFI system partition (where all UEFI aware OS's install their boot loaders) instead of to your HFS partition.  This way, you can keep your drive as full GPT (with protective MBR) and install other OS's in UEFI mode through Clover incl UEFI Windows 10.

 

To mount the EFI partition, just use a simple terminal command eg

 

 

fusion71aus-iMac:~ fusion71au$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data WIN7_X64HDD             161.1 GB   disk0s2
   3:       Microsoft Basic Data DATA                    785.2 GB   disk0s3
   4:                  Apple_HFS macOS                   52.9 GB    disk0s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5

fusion71aus-iMac:~ fusion71au$ diskutil mount disk0s1

Volume EFI on disk0s1 mounted

 

 

buildpkg_boot0md.sh.zip

Clover_v2.4k_r4187_boot0md.zip

  • Like 1
Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

Hi, 

 

I mirrored my system drive to a new SATA HDD "OSX2". It's 1:1 cloned. CCC reports "Sierra 10.12.6" on the drive. Also there is a recovery partition on the drive, but still empty.

 

Now clover only shows the recovery partition as a boot option, and not the OSX2 system partition. boot0ss is installed on the drive.

 

Here is the drive info:

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS OSX2                    4.0 TB     disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3

And system info:

Intel 8 Series Chipset:

  Hersteller:	Intel
  Produkt:	8 Series Chipset
  Link-Geschwindigkeit:	6 Gigabit
  Ausgehandelte Link-Geschwindigkeit:	6 Gigabit
  Physischer Verbindungstyp:	SATA
  Beschreibung:	AHCI Version 1.30 Supported

ST4000LM024-2AN17V:

  Kapazität:	4 TB (4.000.787.030.016 Byte)
  Modell:	ST4000LM024-2AN17V                      
  Version:	1
   Native Command Queuing:	Ja
  Queue Depth:	32
  Wechselmedien:	Nein
  Absteckbares Laufwerk:	Nein
  BSD-Name:	disk2
  Rotationsfrequenz:	5526
  Medienart:	Rotierend
  Partitionstabellentyp:	GPT (GUID-Partitionstabelle)
  S.M.A.R.T.-Status:	Überprüft
  Volumes:
EFI:
  Kapazität:	209,7 MB (209.715.200 Byte)
  Dateisystem:	MS-DOS FAT32
  BSD-Name:	disk2s1
  Inhalt:	EFI
OSX2:
  Kapazität:	4 TB (3.999.927.271.424 Byte)
  Verfügbar:	2,33 TB (2.334.169.554.944 Byte)
  Beschreibbar:	Ja
  Dateisystem:	Journaled HFS+
  BSD-Name:	disk2s2
  Mount-Point:	/Volumes/OSX2
  Inhalt:	Apple_HFS
Recovery HD:
  Kapazität:	650 MB (650.002.432 Byte)
  Dateisystem:	Journaled HFS+
  BSD-Name:	disk2s3
  Inhalt:	Apple_Boot

What is the problem here? Thanks for help.

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Hi, 

 

I mirrored my system drive to a new SATA HDD "OSX2". It's 1:1 cloned. CCC reports "Sierra 10.12.6" on the drive. Also there is a recovery partition on the drive, but still empty.

 

Now clover only shows the recovery partition as a boot option, and not the OSX2 system partition. boot0ss is installed on the drive.

 

Here is the drive info:

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS OSX2                    4.0 TB     disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3

And system info:

Intel 8 Series Chipset:

  Hersteller:	Intel
  Produkt:	8 Series Chipset
  Link-Geschwindigkeit:	6 Gigabit
  Ausgehandelte Link-Geschwindigkeit:	6 Gigabit
  Physischer Verbindungstyp:	SATA
  Beschreibung:	AHCI Version 1.30 Supported

ST4000LM024-2AN17V:

  Kapazität:	4 TB (4.000.787.030.016 Byte)
  Modell:	ST4000LM024-2AN17V                      
  Version:	1
   Native Command Queuing:	Ja
  Queue Depth:	32
  Wechselmedien:	Nein
  Absteckbares Laufwerk:	Nein
  BSD-Name:	disk2
  Rotationsfrequenz:	5526
  Medienart:	Rotierend
  Partitionstabellentyp:	GPT (GUID-Partitionstabelle)
  S.M.A.R.T.-Status:	Überprüft
  Volumes:
EFI:
  Kapazität:	209,7 MB (209.715.200 Byte)
  Dateisystem:	MS-DOS FAT32
  BSD-Name:	disk2s1
  Inhalt:	EFI
OSX2:
  Kapazität:	4 TB (3.999.927.271.424 Byte)
  Verfügbar:	2,33 TB (2.334.169.554.944 Byte)
  Beschreibbar:	Ja
  Dateisystem:	Journaled HFS+
  BSD-Name:	disk2s2
  Mount-Point:	/Volumes/OSX2
  Inhalt:	Apple_HFS
Recovery HD:
  Kapazität:	650 MB (650.002.432 Byte)
  Dateisystem:	Journaled HFS+
  BSD-Name:	disk2s3
  Inhalt:	Apple_Boot

What is the problem here? Thanks for help.

Sometimes cloning may have some flaw ?
check that you still have the boot.efi  at System / Library / CoreServices
also in the root disk at /usr / standalone / i386
you must show the hidden files for this one
Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

 

Sometimes cloning may have some flaw ?
check that you still have the boot.efi  at System / Library / CoreServices
also in the root disk at /usr / standalone / i386
you must show the hidden files for this one

 

 

Really strange, both there. 

 

What else could cause that only the recovery partition is shown in clover? Does clover install boot1h to the HFS+ system partition and if not, doesnt clover show that partition then?

 

Oh btw, CCC added the recovery partition after the system partition (not before). Is that normal?

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Really strange, both there. 

 

What else could cause that only the recovery partition is shown in clover? Does clover install boot1h to the HFS+ system partition and if not, doesnt clover show that partition then?

 

Oh btw, CCC added the recovery partition after the system partition (not before). Is that normal?

I dont know ? I dont trust this kind of soft

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

Really strange, both there. 

 

What else could cause that only the recovery partition is shown in clover? Does clover install boot1h to the HFS+ system partition and if not, doesnt clover show that partition then?

 

Oh btw, CCC added the recovery partition after the system partition (not before). Is that normal?

 

yes the recovery HD is normally right after the HFS partition. CCC is doing the right thing.... for example:

2 physical disks:

disk0 - APFS

disk2 - HFS

$ diskutil list
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         499.3 GB   disk0s2
   3:       Apple_KernelCoreDump                         655.4 MB   disk0s3
/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +499.3 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume macOS                   431.0 GB   disk1s1
   2:                APFS Volume Preboot                 19.1 MB    disk1s2
   3:                APFS Volume Recovery                519.6 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS macOS-SSD               499.2 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
  • Like 1
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

Really strange, both there. 

 

What else could cause that only the recovery partition is shown in clover? Does clover install boot1h to the HFS+ system partition and if not, doesnt clover show that partition then?

 

Oh btw, CCC added the recovery partition after the system partition (not before). Is that normal?

 

 

 

yes the recovery HD is normally right after the HFS partition. CCC is doing the right thing.... for example:

2 physical disks:

disk0 - APFS

disk2 - HFS

$ diskutil list
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         499.3 GB   disk0s2
   3:       Apple_KernelCoreDump                         655.4 MB   disk0s3
/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +499.3 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume macOS                   431.0 GB   disk1s1
   2:                APFS Volume Preboot                 19.1 MB    disk1s2
   3:                APFS Volume Recovery                519.6 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS macOS-SSD               499.2 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3

he made a Clover Legacy install

So May be just missing apfs-64.efi ?

@Funky frank

If you dont have this driver on drivers64, here attaching file

apfs-64.efi.zip

  • Like 1
Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

fusion71au:

 

But managing a clover installation on a by default hidden EFI partition is a pain in the ass. Why boot0 or boot1 cannot simply look on the next partition, if the EFI partition is empty? 

 

Also the installation on the system partition is a best practise for backups. The clover setup will be backed up, too, so my backup drive can fully boot in the same way.

 

Etc.

 

EFI partition is ugly, system partition is beauty.

 

 

I mean some logic like this:

 

1. boot0 loads and checks for boot1 on 1st partition

2. boot1 of partition 1 doesn't find clover on this partition and returns false, returns back to boot0

3. boot0 tries the next partition on the same drive for a boot1

4. boot1 of partition 2 finds clover and loads it -> lot of headaches gone

  • Like 1
Link to comment
Share on other sites
apianti
apianti
Posted
Posted

That's not how legacy boot works, you can't return to the previous stage. Also, there is already a method to perform what you want: install boot0af, set your second partition as the active boot partition using fdisk. No idea why you think EFI volume is ugly, it should have only a few folders that you never even see on it, literally the same files that will end up on the system volume in what you want....

 

EDIT: You can also set it up to always mount your EFI partition, google it. Or use the rc scripts.

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...