Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

n.d.k
n.d.k
Posted
Posted
1 hour ago, Matgen84 said:

 

I don't understand well this change. Hackinbtosher who choose UEFI only knows that Clover boot from EFI, I think.

I don't understand also: "If Volumename begins with #: it means we have to rename the volume: for example catalina-HD to #catalina-HD :worried_anim:

 

Personally, I prefer the reverse: In the case of "#...." the message Clover boot from XXX" will appear. Just my opinion: this change could be optional.

 

Sorry for my bad english, If I misunderstood what you says.

You don't have to rename anything.  Ok to make it clear for someone not understand it well.

 

- Create a file name VolumeLabel.txt on Desktop

- Open it with text editor and write #EFI or any name you want with # in front on the first line, then save it.

- Mount the EFI partition (the one you install the clover on) and open up Finder click EFI on the left pane.

- Drag the VolumeLabel.txt file to it (the root, not into the EFI folder)

- Rename VolumeLabel.txt to .VolumeLabel.txt and it will disappear from the Finder since it's a hidden file name.

Done!

 In Finder, you can use Shift + Command + . to show/hide the hidden files. 

  • Thanks 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
28 minutes ago, Jief_Machak said:

The point is not to tell you it's booted from EFI. In fact a legacy should tells you the same. The point is to know which Clover is booted when you have more than one.

If you give a name to your volume, it can tells you which clover you are booting. Especially useful to prevent a mistake I made : I was mistakenly booting from my regular Clover while I was trying to test a new clover on a USB stick. Took me some time to realise why my modification seems to be uneffective !!

I'll move at the bottom. More discrete...

 

Thanks for moving  at the bottom :) 

 

I have two Hacks UEFI only: one HD for Mojave and another HD for Catalina. The first volume is named 'Mojave', the second 'Catalina'. The message is: "Clover booted from EFI". That doesn't tell me what efi on which volume. Can you explain to me, why?

 

 

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
6 minutes ago, n.d.k said:

You don't have to rename anything.  Ok to make it clear for someone not understand it well.

 

- Create a file name VolumeLabel.txt on Desktop

- Open it with text editor and write #EFI or any name you want with # in front on the first line, then save it.

- Mount the EFI partition (the one you install the clover on) and open up Finder click EFI on the left pane.

- Drag the VolumeLabel.txt file to it (the root, not into the EFI folder)

- Rename VolumeLabel.txt to .VolumeLabel.txt and it will disappear from the Finder since it's a hidden file name.

Done!

 In Finder, you can use Shift + Command + . to show/hide the hidden files. 

 

Thanks for this explanation :) 

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
1 minute ago, vector sigma said:

Sorry but what is 'EFI' for you?

 

For me, EFI is EFI Partition. Take a look to the screenshot, I've post before: in attachment bellow, and diskutil list via Terminal.

  

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk0
   1:                        EFI NO NAME                 353.4 MB   disk0s1
   2:         Microsoft Reserved                         16.8 MB    disk0s2
   3:       Microsoft Basic Data Win10                   2.0 TB     disk0s3
   4:           Windows Recovery                         516.9 MB   disk0s4

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1  <----------
   2:                 Apple_APFS Container disk2         1000.0 GB  disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1000.0 GB  disk2
                                 Physical Store disk1s2
   1:                APFS Volume Mojave                  496.6 GB   disk2s1
   2:                APFS Volume Preboot                 24.1 MB    disk2s2
   3:                APFS Volume Recovery                510.3 MB   disk2s3
   4:                APFS Volume VM                      8.6 GB     disk2s4

 

Clover_screenshot.png

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
4 minutes ago, vector sigma said:

  


 1:                        EFI EFI                     209.7 MB   disk1s1  <----------

And why you expect to show something else then?

 

For example, Clover booted from EFI / Volume_Name :) Just "Clover booted from EFI" doesn't give me any information

  • Like 1
Link to comment
Share on other sites
n.d.k
n.d.k
Posted
Posted
3 minutes ago, Matgen84 said:

 

For example, Clover booted from EFI / Volume_Name :) Just "Clover booted from EFI" doesn't give me any information

That's where the VolumeLabel.txt become useful, instead of #EFI, write Samsung970EVO on the first line, so you know that Clover booted from that drive,  One drive can have multiple volume with multiple macOS, but can only have one EFI partition.  So Use the drive brand makes more sense than use the macOS name if one have multi OSes on the same drive.

  • Like 2
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
19 minutes ago, Matgen84 said:

 

For example, Clover booted from EFI / Volume_Name :) Just "Clover booted from EFI" doesn't give me any information

EFI is the name of the partition. '/Volumes' is a folder that exist only in macOS. '/Volumes/EFI' is a mount point which can exists only after the volume is mounted, after the OS is loaded. But you are in a time you don't even boot into one OS.

The same for disk0s1. It is called BSD name and it is only used by Darwin OSes due to the BSD kernel part. In Linux would be some thing like sda1. In Windows would be B:. 

Now, if you mount the disk0s1 and create a file ".VolumeLabel.txt" on it, you can write for example "This is the disk where my preferred Clover is" and reboot. Now you know where you are booting from.

  

echo "This is the disk where my preferred Clover is" > /Volumes/EFI/.VolumeLabel.txt

 

Edited by vector sigma
  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
21 minutes ago, vector sigma said:

EFI is the name of the partition. '/Volumes' is a folder that exist only in macOS. '/Volumes/EFI' is a mount point which can exists only after the volume is mounted, after the OS is loaded. But you are in a time you don't even boot into one OS.

The same for disk0s1. It is called BSD name and only used by Darwin OSes due to the BSD kernel part. In Linux would be some thing like sda1. In Windows would be B:. 

Now, if you mount the disk0s1 and create a file ".VolumeLabel.txt" on it, you can write for example "This is the disk where my preferred Clover is" and reboot. Now you know where you are booting from.

  


echo "This is the disk where my preferred Clover is" > /Volumes/EFI/.VolumeLabel.txt

 

 

I've to do the same for all bootable macOS devices: USB Installer, external drive that I use for test, etc... Right? If I don't need this info :cry:

 

I second @Florin9doi : " I think that by default, when no VolumeLabel.txt file is present, the text should be hidden."

Edited by Matgen84
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
1 hour ago, bronxteck said:

using 2 different themes would have saved you the headache. use one for usb and a different one for HDD. problem solved.

I did that for a while.

I also modified the background image. But, eventually, when I copied a Clover folder onto an old one, I forgot to change...

I moved to the bottom right corner.

A setting in the GUI section would make everyone agree ? (the default would be not to display, of course).

  • Thanks 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
37 minutes ago, Jief_Machak said:

I moved to the bottom right corner.

A setting in the GUI section would make everyone agree ? (the default would be not to display, of course).

 

Thanks a lot :) I'm agree of course for setting in GUI section.

 

I've compile and install r5101 (7a0295e3): no new kexts folder structure. Same thing for a clean install 

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
1 hour ago, Matgen84 said:

I've compile and install r5101 (7a0295e3): no new kexts folder structure. Same thing for a clean install 

 

assuming an OS goes to 10.X.6 max (Snow Leopard 10.6.8 Lol)... there are six seven folders each, so since 10.6 there are 11 OSes to be multiplied for 3 (_normal, _recovery and _install).... for an amount of 198 231 directories :hysterical: in the OEM path and in the usual place. 

 

I think no one wants hundreds of empty folders at each installation in the EFI directory. Since no one knows what a user needs, this must be done at user will, imho.

 

Edited by vector sigma
  • Like 2
Link to comment
Share on other sites
artur_pt
artur_pt
Posted
Posted
6 hours ago, Jief_Machak said:

OK, some people don't like the information about CLover boot volume.

Is it really a problem to see that in Clover, which you are supposed to see only few seconds at boot ? Maybe I should move on bottom right corner, like "5100, booted from xxx" ? Or a setting, disabled by default ?

 

hello

 

just what I think about that

 

thanks

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
2 hours ago, vector sigma said:

 

 for an amount of 198 231 directories :hysterical: in the OEM path and in the usual place. 

 

I think no one wants hundreds of empty folders at each installation in the EFI directory. Since no one knows what a user needs, this must be done at user will, imho.

 

Not sure what you mean. You're not obliged to create folders you don't need. So why "empty folders" ?

Just create the one you need, and if you need to make a difference for a minor version for 1 or 2 kext, you can.

4 hours ago, Matgen84 said:

 

" I think that by default, when no VolumeLabel.txt file is present, the text should be hidden."

That's a lot of noise for a small piece of text in a screen you see few seconds now and then.

Still, I'm perfectly fine with no .VolumeLabel.txt == no text.

  • Like 1
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
3 hours ago, Jief_Machak said:

Not sure what you mean. You're not obliged to create folders you don't need. So why "empty folders" ?

Sorry but you got it well, and the point is just the same:

--> Question: why the installer did not create these new directories?

3 hours ago, Jief_Machak said:

Just create the one you need

agreed.

--> inplicit answere: There is no need to create any folder because nor the package nor the app knows what you need. Create ones you need manually!

 

We just have the same opinion, and my post was just to let understand that create them by the installer is not possible.... unless you create hundreds of directories to cover any supported OSes.

Edited by vector sigma
  • Like 2
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
4 hours ago, vector sigma said:

Sorry but you got it well, and the point is just the same:

--> Question: why the installer did not create these new directories?

agreed.

--> inplicit answere: There is no need to create any folder because nor the package nor the app knows what you need. Create ones you need manually!

 

We just have the same opinion, and my post was just to let understand that create them by the installer is not possible.... unless you create hundreds of directories to cover any supported OSes.

Ah ok. I didn't realise it was about the installer. I must have missed a post.

 

NOTE : Ideally, these directory wouldn't be used. For few years, I had the same clover for install recovery and normal boot. VoodooI2C.kext doesn't work for install, that's why I made that possibility.

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

43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0_normal

10.5.8.0 seems wrong 

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
On 12/21/2019 at 10:22 AM, Florin9doi said: 


43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0_normal

10.5.8.0 seems wrong 

Sure it is. I'll have a look soon.

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