Jump to content
5 posts in this topic

Recommended Posts

Restored Sequoia and Sonoma from backup and that resolved the issue completely.

 

Completely replaced the clover versions from backup, so preboot log was deleted.

 

It appears it was something to do with the Sequoia and Sonoma partitions, after being restored, clover detected them correctly and displayed the correct icons and booted ok.

 

Does clover write anything to the macOS partition? 

 

What information, how and where does clover scan to determine the macOS version? 

 

I checked the systemversion.plist and it was not changed.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

This situatiion is probably best answered by Slice, but since clover discussion does not have a "start new topic" in my window, it is posted here.

 

After test booting from portable media, some old archived macOS versions, including High Sierra, using Clover 5158 and MBP SMBIOS 14.1, to be sure that they still booted ok, a very unusual problem cropped up after clearing NVRAM.

 

Subsequently attempting to boot Sequoia and Sonoma with Clover 5159 and SMBIOS 19.1 resulted in the Sonoma and Sequoia icons being displayed as High Sierra icons, and failure to boot with an "incorrect platform" message.

 

Clover 5158 and 5159 are on separate partitions and are chainloaded via Linux bootloader GRUB2.

 

It appears that clover is scanning the Sonoma and Sequoia macOS installations and somehow incorrectly detecting them as High Sierra.

 

Did running the MBP 14.1 SMBIOS somehow write a clover configuration to the Sonoma and Sequoia installations that caused Clover to subsequently detect them as High Sierra?

 

This method of chainloading differently configured clover versions in order to provide the correct SMBIOS for the mac OS version has worked without this type of problem for many months and am unsure as to why it has cropped up recently.

 

Note also that Open Core 101 boots both Sonoma and Sequoia.

 

Can anyone give me some pointers as to how to clear up this misdetection issue?

 

What specific information does Clover scan for when detecting the macOS version?

 

 

Edited by mek21
  • Like 1

first of all make sur you have a theme updated with a Sequoia icons

Make sur booting with latest Clover release

here attaching Atomic theme

 

Atomic.zip

 

  • Like 2
9 minutes ago, Slice said:

Create preboot.log by F2 and upload here.

Thanks.  Restored Sequoia and Sonoma from backup and that resolved the issue completely.

 

Completely replaced the clover versions from backup, so preboot log was deleted.

 

It appears it was something to do with the Sequoia and Sonoma partitions, after being restored, clover detected them correctly and displayed the correct icons and booted ok.

 

Does clover write anything to the macOS partition? 

 

What information, how and where does clover scan to determine the macOS version? 

 

I checked the systemversion.plist and it was not changed. 

  • Like 1

No, Clover can't write to macOS partition because HFS+ and APFS drivers are read-only.

Clover reads file /System/Library/CoreServices/SystemVersion.plist 

which contains

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>BuildID</key>
	<string>1BFE207C-45AE-11EF-A635-B033852F5AC2</string>
	<key>ProductBuildVersion</key>
	<string>24A5298h</string>
	<key>ProductCopyright</key>
	<string>1983-2024 Apple Inc.</string>
	<key>ProductName</key>
	<string>macOS</string>
	<key>ProductUserVisibleVersion</key>
	<string>15.0</string>
	<key>ProductVersion</key>
	<string>15.0</string>
	<key>iOSSupportVersion</key>
	<string>18.0</string>
</dict>
</plist>

and nothing more 

  • Like 2
×
×
  • Create New...