hackaro Posted June 27, 2017 Share Posted June 27, 2017 @hackaro, Please post your boot.log and config.plist. Here it is. @apianti thank you. Archive.zip Link to comment Share on other sites More sharing options...
r!ppz Posted June 27, 2017 Share Posted June 27, 2017 I tested both the HFS+ and APFS installation of 10.13 on my Samsung SSD 840 pro. The APFS installation takes much longer to boot. HFS+ is almost instant. I guess this will be fixed in the final release. OS itself is smooth as always. Anyone seeing the same effect? Link to comment Share on other sites More sharing options...
PMheart Posted June 27, 2017 Share Posted June 27, 2017 I tested both the HFS+ and APFS installation of 10.13 on my Samsung SSD 840 pro. The APFS installation takes much longer to boot. HFS+ is almost instant. I guess this will be fixed in the final release. OS itself is smooth as always. Anyone seeing the same effect? Yes. The same on my real Mac NVMe disk. But not that serious I guess. Just a fair little bit slower than HFS+. Link to comment Share on other sites More sharing options...
arsradu Posted June 27, 2017 Share Posted June 27, 2017 @arsradu, There is a key for custom entries called, Hidden, if you set that to true, then entries will be hidden by default and can be toggled shown/hidden with F3. It's useful for recovery entries, or other stuff you don't use regularly but might need eventually. EDIT: Glad you got it looking like you want! Thanks for your help. Also, I'll try that. It is pretty much what I wanted. Which is to be able to easily toggle visible/hidden those Recovery partitions in case I need them. Link to comment Share on other sites More sharing options...
magnifico Posted June 27, 2017 Share Posted June 27, 2017 Yes. The same on my real Mac NVMe disk. But not that serious I guess. Just a fair little bit slower than HFS+. You mean only for istallation ? Link to comment Share on other sites More sharing options...
SavageAUS Posted June 27, 2017 Share Posted June 27, 2017 What is the easiest way to identify the UUID or unique number of the High Sierra recovery partition with apfs? Sent from my SM-G930F using Tapatalk Link to comment Share on other sites More sharing options...
gengik84 Posted June 27, 2017 Share Posted June 27, 2017 What is the easiest way to identify the UUID or unique number of the High Sierra recovery partition with apfs? Sent from my SM-G930F using Tapatalk diskutil info /dev/diskXsx | grep UUID Replace Xx with your "apfs volume recovery" Show with diskutil list 3 Link to comment Share on other sites More sharing options...
PMheart Posted June 27, 2017 Share Posted June 27, 2017 diskutil info /dev/diskXsx | grep UUID Replace Xx with your "apfs volume recovery" Show with diskutil list What about diskutil info Recovery | grep "Volume UUID" | awk '{print $3}' It gave me 24E61BE6-002D-431B-9632-E01122C4A385 2 Link to comment Share on other sites More sharing options...
PMheart Posted June 27, 2017 Share Posted June 27, 2017 You mean only for istallation ? No. Also booting the normal system. Link to comment Share on other sites More sharing options...
fusion71au Posted June 27, 2017 Share Posted June 27, 2017 diskutil info /dev/diskXsx | grep UUID The unique UUID for APFS Volumes that Clover uses (in its bootlog/bdmesg) is different to the one reported by the "diskutil info" command.... eg for my system, the APFS Recovery Volume is disk2s4 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +50.5 GB disk2 Physical Store disk1s7 1: APFS Volume macOS 30.3 GB disk2s1 2: APFS Volume VM 2.1 GB disk2s2 3: APFS Volume Preboot 18.4 MB disk2s3 4: APFS Volume Recovery 505.4 MB disk2s4 fusion71aus-MacBook-Pro:~ fusion71au$ diskutil info disk2s4 | grep UUID Volume UUID: 035D37E3-D29D-4793-8336-730AF9D47F15 Disk / Partition UUID: 035D37E3-D29D-4793-8336-730AF9D47F15 fusion71aus-MacBook-Pro:~ fusion71au$ bdmesg | grep 035D37E3-D29D-4793-8336-730AF9D47F15 fusion71aus-MacBook-Pro:~ fusion71au$ bdmesg | grep Recovery 8:919 0:000 Checking volume "Recovery HD" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,86DAF24D-5D5C-4629-BA3F-CB290BD13D88,0xE1C72D8,0x135F20)) ... skipped 9:030 0:000 Checking volume "Recovery" (PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x2,0x0)\HD(7,GPT,34A73EF5-D2F1-49D4-A682-FDB136B489D6,0x1F4E4800,0x5E11A88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,E3375D039DD293478336730AF9D47F15)) ... skipped 9:476 0:010 - [13]: 'Recovery HD' 9:477 0:000 AddLoaderEntry for Volume Name=Recovery HD 10:450 0:008 - [21]: 'Recovery' 10:453 0:002 AddLoaderEntry for Volume Name=Recovery Note "diskutil info" command returns 035D37E3-D29D-4793-8336-730AF9D47F15 but the unique part of the UUID used by Clover shown in bootlog/bdmesg (last section after VenMedia) is E3375D039DD293478336730AF9D47F15 IMHO, better to use UUIDs shown in Clover bootlog/bdmesg for the purposes of creating Custom Entries in config.plist.... 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 27, 2017 Share Posted June 27, 2017 The unique UUID for APFS Volumes that Clover uses (in its bootlog/bdmesg) is different to the one reported by the "diskutil info" command.... eg for my system, the APFS Recovery Volume is disk2s4 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +50.5 GB disk2 Physical Store disk1s7 1: APFS Volume macOS 30.3 GB disk2s1 2: APFS Volume VM 2.1 GB disk2s2 3: APFS Volume Preboot 18.4 MB disk2s3 4: APFS Volume Recovery 505.4 MB disk2s4 fusion71aus-MacBook-Pro:~ fusion71au$ diskutil info disk2s4 | grep "Volume UUID" Volume UUID: 035D37E3-D29D-4793-8336-730AF9D47F15 fusion71aus-MacBook-Pro:~ fusion71au$ bdmesg | grep 035D37E3-D29D-4793-8336-730AF9D47F15 fusion71aus-MacBook-Pro:~ fusion71au$ bdmesg | grep Recovery 8:919 0:000 Checking volume "Recovery HD" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,86DAF24D-5D5C-4629-BA3F-CB290BD13D88,0xE1C72D8,0x135F20)) ... skipped 9:030 0:000 Checking volume "Recovery" (PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x2,0x0)\HD(7,GPT,34A73EF5-D2F1-49D4-A682-FDB136B489D6,0x1F4E4800,0x5E11A88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,E3375D039DD293478336730AF9D47F15)) ... skipped 9:476 0:010 - [13]: 'Recovery HD' 9:477 0:000 AddLoaderEntry for Volume Name=Recovery HD 10:450 0:008 - [21]: 'Recovery' 10:453 0:002 AddLoaderEntry for Volume Name=Recovery Note "diskutil info" command returns 035D37E3-D29D-4793-8336-730AF9D47F15 but the unique part of the UUID used by Clover shown in bootlog/bdmesg (last section after VenMedia) is E3375D039DD293478336730AF9D47F15 IMHO, better to use UUIDs shown in Clover bootlog/bdmesg for the purposes of creating Custom Entries in config.plist.... The only correct way to gather the UUIDs is from Clover log, isn't it? 1 Link to comment Share on other sites More sharing options...
cecekpawon Posted June 28, 2017 Share Posted June 28, 2017 Or diskutil apfs list Link to comment Share on other sites More sharing options...
apianti Posted June 28, 2017 Share Posted June 28, 2017 Notice that the UUIDs you obtain from diskutil or from the device path string are the same UUID just in different formats: From diskutil:035D37E3-D29D-4793-8336-730AF9D47F15From device path:E3375D03 9DD2 9347 8336 730AF9D47F15So you can create the other from one. 3 Link to comment Share on other sites More sharing options...
SavageAUS Posted June 28, 2017 Share Posted June 28, 2017 I've been trying for ages to get a custom entry for my High Sierra Recovery with no luck, All my other entries are working fine. What can i add to this post to gain assistance? Link to comment Share on other sites More sharing options...
fusion71au Posted June 28, 2017 Share Posted June 28, 2017 @SavageAUS, Min info required would be your Clover boot log (output from bdmesg command in terminal), output from "diskutil list" and the complete GUI section from your config.plist ---> attach to your post so others can help you. Make sure to remove identifying serials eg MLB, ROM etc from your config.plist. If all you are needing is to hide the Recovery Volume, you can look at post#13505. Also some background on what to look for in your boot log in post#13512. Edit1 OK, info from your boot log: APFS Recovery UUID for High Sierra = Vol 12 = 4F725DE47024C0499E983E1100C1CD92 Recovery HD UUID for Sierra = Vol 3 = C0401322-7F93-4508-A319-52A75A81C24C Attached is the corrected GUI config.plist (Only changed UUID from A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538 to 4F725DE47024C0499E983E1100C1CD92) Good Luck! Edit2 You might also have to add the UUID of the High Sierra volume to the loader path for the APFS Recovery volume (like for Preboot Custom Entry post#13539). What is the output of diskutil info disk1s1 | grep UUID? Path would be in the form \UUID\boot.efi Edit3 Added \A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538\boot.efi to path. Hopefully this works.. GUI config_edited2.plist.zip Legend, that was the trick. All custom entries working now Great! Glad I could help GUI config_edited.plist.zip GUI config_edited2.plist.zip 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted June 28, 2017 Share Posted June 28, 2017 Ok thank you, hopefully i've removed personal stuff. Last login: Wed Jun 28 13:06:12 on ttys000 Shanes-MBP:~ shane$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS macOS Sierra 249.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Microsoft Reserved 16.8 MB disk0s4 5: Microsoft Basic Data Windows 10 142.5 GB disk0s5 6: Apple_APFS 53.1 GB disk0s6 7: Apple_KernelCoreDump 655.4 MB disk0s7 8: Linux Filesystem 21.5 GB disk0s8 9: Linux Filesystem 32.1 GB disk0s9 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme +53.1 GB disk1 /dev/disk1s1 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: APFS Volume macOS High Sierra +27.2 GB disk1s1 /dev/disk1s2 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: APFS Volume Preboot +19.2 MB disk1s2 /dev/disk1s3 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: APFS Volume Recovery +505.4 MB disk1s3 /dev/disk1s4 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: APFS Volume VM +1.1 GB disk1s4 bootlog.log.txt GUI config.plist.zip Terminal Saved Output.zip Link to comment Share on other sites More sharing options...
Slice Posted June 28, 2017 Share Posted June 28, 2017 Notice that the UUIDs you obtain from diskutil or from the device path string are the same UUID just in different formats: From diskutil: 035D37E3-D29D-4793-8336-730AF9D47F15 From device path: E3375D03 9DD2 9347 8336 730AF9D47F15 So you can create the other from one. Yes, device path string uses UEFI libraries with Little Endian numeration for UUID while Apple uses Big Endian. Clover contains many codes for the converting but this string is new. 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted June 28, 2017 Share Posted June 28, 2017 @SavageAUS, Min info required would be your Clover boot log (output from bdmesg command in terminal), output from "diskutil list" and the complete GUI section from your config.plist ---> attach to your post so others can help you. Make sure to remove identifying serials eg MLB, ROM etc from your config.plist. If all you are needing is to hide the Recovery Volume, you can look at post#13505. Also some background on what to look for in your boot log in post#13512. Edit OK, your from your boot log: APFS Recovery UUID for High Sierra = Vol 12 = 4F725DE47024C0499E983E1100C1CD92 Recovery HD UUID for Sierra = Vol 3 = C0401322-7F93-4508-A319-52A75A81C24C Attached is the corrected GUI config.plist (Only changed UUID from A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538 to 4F725DE47024C0499E983E1100C1CD92) Good Luck! Using 4F725DE47024C0499E983E1100C1CD92 in config didn't make any changes on my end. Do i need to add anything to the path or just 4F725DE47024C0499E983E1100C1CD92 in volume? It's just the High Sierra recovery i need to rename, Sierra's recovery is fine. It's really strange, if i add 4F725DE47024C0499E983E1100C1CD92 to the section to hide entries, High Sierra Recovery is hidden but using 4F725DE47024C0499E983E1100C1CD92 will not allow me to rename the entry in GUI. Link to comment Share on other sites More sharing options...
SavageAUS Posted June 28, 2017 Share Posted June 28, 2017 @SavageAUS, Min info required would be your Clover boot log (output from bdmesg command in terminal), output from "diskutil list" and the complete GUI section from your config.plist ---> attach to your post so others can help you. Make sure to remove identifying serials eg MLB, ROM etc from your config.plist. If all you are needing is to hide the Recovery Volume, you can look at post#13505. Also some background on what to look for in your boot log in post#13512. Edit1 OK, your from your boot log: APFS Recovery UUID for High Sierra = Vol 12 = 4F725DE47024C0499E983E1100C1CD92 Recovery HD UUID for Sierra = Vol 3 = C0401322-7F93-4508-A319-52A75A81C24C Attached is the corrected GUI config.plist (Only changed UUID from A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538 to 4F725DE47024C0499E983E1100C1CD92) Good Luck! Edit2 You might also have to add the UUID of the High Sierra volume to the loader path for the APFS Recovery volume (like for Preboot Custom Entry post#13539). What is the output of diskutil info disk1s1 | grep UUID? Path would be in the form \UUID\boot.efi eg like \5A3A032A-9A07-47DF-A631-FF80D3B3EEF2\boot.efi Output is Shanes-MBP:~ shane$ diskutil info disk1s1 | grep UUID Volume UUID: A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538 p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff} span.s1 {font-variant-ligatures: no-common-ligatures} Disk / Partition UUID: A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538 @SavageAUS, Min info required would be your Clover boot log (output from bdmesg command in terminal), output from "diskutil list" and the complete GUI section from your config.plist ---> attach to your post so others can help you. Make sure to remove identifying serials eg MLB, ROM etc from your config.plist. If all you are needing is to hide the Recovery Volume, you can look at post#13505. Also some background on what to look for in your boot log in post#13512. Edit1 OK, your from your boot log: APFS Recovery UUID for High Sierra = Vol 12 = 4F725DE47024C0499E983E1100C1CD92 Recovery HD UUID for Sierra = Vol 3 = C0401322-7F93-4508-A319-52A75A81C24C Attached is the corrected GUI config.plist (Only changed UUID from A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538 to 4F725DE47024C0499E983E1100C1CD92) Good Luck! Edit2 You might also have to add the UUID of the High Sierra volume to the loader path for the APFS Recovery volume (like for Preboot Custom Entry post#13539). What is the output of diskutil info disk1s1 | grep UUID? Path would be in the form \UUID\boot.efi Edit3 Added \A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538\boot.efi to path. Hopefully this works.. GUI config_edited2.plist.zip Legend, that was the trick. All custom entries working now This is the entry. <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra Recovery</string> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Path</key> <string>\A7BD56F8-BE2B-3C8B-A08E-9E3ED3EEE538\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>4F725DE47024C0499E983E1100C1CD92</string> <key>VolumeType</key> <string>Internal</string> </dict> </plist> 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 29, 2017 Share Posted June 29, 2017 @Slice Hi. I found hibernation not working with FV2 enabled. I followed your instructions on (http://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?p=2313627) Details: - MotherBoard: GA-B75M-D3V (UEFI & Real NVRAM) - GPT SSD with EFI and Recovery partition (You said it should be HDD, but I guess it doesn't really matter) - macOS Sierra 10.12.5 - Clover r4097 from sf.net - SMCHelper.efi and aptiofixv2.efi both from the pkg from sf.net - FakeSMC 3.4.2 from (https://sourceforge.net/projects/hwsensors3.hwsensors.p/), and it is extracted from HWSensors3-rev43.pkg - StrictHibernate = true in config.plist/Boot - hibernatemode = 25 Extras: - HibernationFixup.kext from (https://sourceforge.net/projects/hibernationfixup/) (Also tried without this, no luck) - Changed smc rev for FakeSMC/Info.plist to be compatible with MacPro6,1 With these stuffs, hibernation is still not working, I got a reboot while waking. I saw you said If you have a reboot during wake then most probably you have no correct FakeSMC. And what's "no correct FakeSMC" exactly referring to? Any idea? Thanks in advance Link to comment Share on other sites More sharing options...
savvas Posted June 29, 2017 Share Posted June 29, 2017 @Slice Hi. I found hibernation not working with FV2 enabled. I followed your instructions on (http://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?p=2313627) Details: - MotherBoard: GA-B75M-D3V (UEFI & Real NVRAM) - GPT SSD with EFI and Recovery partition (You said it should be HDD, but I guess it doesn't really matter) - macOS Sierra 10.12.5 - Clover r4097 from sf.net - SMCHelper.efi and aptiofixv2.efi both from the pkg from sf.net - FakeSMC 3.4.2 from (https://sourceforge.net/projects/hwsensors3.hwsensors.p/), and it is extracted from HWSensors3-rev43.pkg - StrictHibernate = true in config.plist/Boot - hibernatemode = 25 Extras: - HibernationFixup.kext from (https://sourceforge.net/projects/hibernationfixup/) (Also tried without this, no luck) - Changed smc rev for FakeSMC/Info.plist to be compatible with MacPro6,1 With these stuffs, hibernation is still not working, I got a reboot while waking. I saw you said And what's "no correct FakeSMC" exactly referring to? Any idea? Thanks in advance Check nvram var's , especially from fakesmc. May be they still not recent and Clover uses old smc keys values 1 Link to comment Share on other sites More sharing options...
Slice Posted June 29, 2017 Share Posted June 29, 2017 @Slice Hi. I found hibernation not working with FV2 enabled. I followed your instructions on (http://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?p=2313627) Details: - MotherBoard: GA-B75M-D3V (UEFI & Real NVRAM) - GPT SSD with EFI and Recovery partition (You said it should be HDD, but I guess it doesn't really matter) - macOS Sierra 10.12.5 - Clover r4097 from sf.net - SMCHelper.efi and aptiofixv2.efi both from the pkg from sf.net - FakeSMC 3.4.2 from (https://sourceforge.net/projects/hwsensors3.hwsensors.p/), and it is extracted from HWSensors3-rev43.pkg - StrictHibernate = true in config.plist/Boot - hibernatemode = 25 Extras: - HibernationFixup.kext from (https://sourceforge.net/projects/hibernationfixup/) (Also tried without this, no luck) - Changed smc rev for FakeSMC/Info.plist to be compatible with MacPro6,1 With these stuffs, hibernation is still not working, I got a reboot while waking. I saw you said And what's "no correct FakeSMC" exactly referring to? Any idea? Thanks in advance Correct FakeSMC saves all attempts to write to SMC into NVRAM. But not read back NVRAM values. Write yes Read no. Hibernation depends on many factors. First, you must have working simple sleep. Second. Hibernate mode 25 supported with hardware NVRAM without EmuVariable if StrictHibernate set. Otherwise with Lilu+HibernationFixup (I didn't tested). Or set hibernatemode 29. 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 29, 2017 Share Posted June 29, 2017 Check nvram var's , especially from fakesmc. May be they still not recent and Clover uses old smc keys values Thanks. Well, I may dig further in some days. Alright, yes, some keys can be too old... Correct FakeSMC saves all attempts to write to SMC into NVRAM. But not read back NVRAM values. Write yes Read no. Thx Slice. Is this done by SMCHelper.efi? Or do I need some changes in FakeSMC? Link to comment Share on other sites More sharing options...
Slice Posted June 29, 2017 Share Posted June 29, 2017 SMCHelper is obligatory for FV2, but I not sure about hibernation. You don't need to change FakeSMC 3.4. It is good enough. If you have a trouble try to catch it with DumpUefiCalls driver. 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 29, 2017 Share Posted June 29, 2017 Hibernation depends on many factors. First, you must have working simple sleep. Second. Hibernate mode 25 supported with hardware NVRAM without EmuVariable if StrictHibernate set. Otherwise with Lilu+HibernationFixup (I didn't tested). Or set hibernatemode 29. I see. Well, I tested normal sleep (without fv2 enabled) very long time ago... And I've totally forgotten the result. I'll report in a couple of days. Yes. The second condition is ok to me. If I remember correctly, Apple set a restriction on determining hibernatemode, which is you can only set it to 0, 3, 25 via `pmset`, we can still patch the related plist though, it doesn't really matter. SMCHelper is obligatory for FV2, but I not sure about hibernation. You don't need to change FakeSMC 3.4. It is good enough. If you have a trouble try to catch it with DumpUefiCalls driver. Thanks for the information. If I don't change anything in FakeSMC, then won't the smc-rev key in the default Info.plist be incorrect (for MacPro6,1)? Is there any link for that DumpUefiCalls driver? Thanks Link to comment Share on other sites More sharing options...
Recommended Posts