Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

LAbyOne
LAbyOne
Posted
Posted (edited)
28 minutes ago, STLVNUB said:

it did get further, still won't run at the moment it is open

but doesn't show itself, trying to delete it say it is open

 

to solve this just open Activity Monitor /App/Utilities

and kill the process

  

29 minutes ago, STLVNUB said:

knocks head on brick wall, I've a lot of issues with my setup

maybe its about your accessibility preferences.

as it uses osascript probably there must be some setting on your machine preventing it to run.

Edited by LAbyOne
STLVNUB
STLVNUB
Posted
Posted
12 hours ago, LAbyOne said:

Probably, but normally once you allow the browser to download files from different locations you shouldn't have any issue at all, later on.

 

Now Runs But No Screen is Visible ☹️

STLVNUB
STLVNUB
Posted
Posted

Any Body Having Problems Installing Try This:-

 

Copy The Installer To Another HDD Using Terminal And Run It From There

e.g sudo cp -R The Installer Name  /Volumes/Your HDD

Had Me Stumped For A While,Tried Everything, Made USB Install, Didn't Work

Then I Ran The Installer From That USB And It Worked 😀

Hope This Helps

  • 2 weeks later...
jackacc
jackacc
Posted
Posted

In order to ensure that there are no issues with breaking existing installs, OCLP takes a safe approach when it comes to enabling AMFI.

  • You must be building OpenCore on the host (so you cannot be building the EFI for another device)
    • If you build from another machine, we cannot automatically ensure that the target machine has root patches compatible with AMFIPass
  • If you currently have root patches installed, they must be at least v0.6.6 or newer

Thus, for new OCLP users, there is nothing special to do besides building OpenCore on the host.

For existing users, follow these steps:

  1. Download the OCLP version linked below
  2. Build and install OpenCore in order to add AMFIPass to your EFI.
  3. Reboot
  4. Install the new root patches
  5. Reboot
  6. Build and install OpenCore again to disable AMFI
  7. Reboot
  8. You should now be booting with AMFI enabled!

In the patch does not support macos

clover?

  • Like 1
  • Confused 1
BuXb
BuXb
Posted
Posted (edited)

Hi @Slice, good to see you around here 😎

 

I posted an issue at GitHub > Clover disobeys Efi Version set in config.plist/SMBIOS

 

I guess I don't need to post the same content here again, do I. Just wanted to post the link here because not everybody checks Clover's issue section over at GitHub.

 

When the gap between the EFI version macOS finds and the one it would like to see gets too big, functionality might get curtailed, so I felt it makes sense to address this issue.

 

Thanks for looking into this 💪

Edited by BuXb
Slice
Slice
Posted
Posted
7 hours ago, BuXb said:

Hi @Slice, good to see you around here 😎

 

I posted an issue at GitHub > Clover disobeys Efi Version set in config.plist/SMBIOS

 

I guess I don't need to post the same content here again, do I. Just wanted to post the link here because not everybody checks Clover's issue section over at GitHub.

 

When the gap between the EFI version macOS finds and the one it would like to see gets too big, functionality might get curtailed, so I felt it makes sense to address this issue.

 

Thanks for looking into this 💪

See you.

Show please Clover preboot.log.

LAbyOne
LAbyOne
Posted
Posted (edited)
On 5/12/2023 at 7:21 AM, STLVNUB said:

Any Chance Of Updating GCC Build Script To 13.1.0?

Builds Smaller EFI Files

Latest IS Greatest

If you tried and all builds works as expected feel free to submit.

 

I tested 13.1.0 and by my side Clover builds fails on all systems i tried.

there are different new implementations which need patches

if you want to update you current GCC there is the 12.3.0 which came out the same day, and its the only actually the safest one to use

 

I may eventually if @Slice is ok pull the actual 12.3.0 already tested

Edited by LAbyOne
  • Like 2
BuXb
BuXb
Posted
Posted (edited)

@Slice (and also @LAbyOne since you happen to be active in here right now): can you let me know what happens when you edit the Efi Version string in Clover config.plist/SMBIOS as I described in  Clover disobeys Efi Version set in config.plist/SMBIOS -> reboot: what do you see in "About this Mac > System Report > System Firmware Version" - the updated string you wrote into config.plist, or some old one?

Edited by BuXb
LAbyOne
LAbyOne
Posted
Posted

@BuXb

for what i see in your log Clover is just doing its job. 

0:124  0:001  There is a problem in plist '\EFI\CLOVER\config.plist'
0:124  0:000  Warning: EfiVersion '1968.100.17.0.0' is older than default ('1715.0.57.0.0') -> ignored. Dict '/SMBIOS:913'.

.....

3:131  0:000  BiosVersion: MBP154.88Z.F000.B00.2107050236
3:131  0:000  BiosReleaseDate: 07/05/2021
3:131  0:000  EfiVersion: 1715.0.57.0.0

your EfiVersion seems to be obsolete for the corresponding model and Clover apply the most correct one for the chosen smbios.

since any version is timestamp based meaning it get updated (if exists) anytime your machine receive an update

Now i do not know the specific but if clover suggest and apply that one, its most probably the the latest checked against your smbios model.

Matgen84
Matgen84
Posted
Posted
26 minutes ago, LAbyOne said:

@BuXb

for what i see in your log Clover is just doing its job. 

0:124  0:001  There is a problem in plist '\EFI\CLOVER\config.plist'
0:124  0:000  Warning: EfiVersion '1968.100.17.0.0' is older than default ('1715.0.57.0.0') -> ignored. Dict '/SMBIOS:913'.

.....

3:131  0:000  BiosVersion: MBP154.88Z.F000.B00.2107050236
3:131  0:000  BiosReleaseDate: 07/05/2021
3:131  0:000  EfiVersion: 1715.0.57.0.0

your EfiVersion seems to be obsolete for the corresponding model and Clover apply the most correct one for the chosen smbios.

since any version is timestamp based meaning it get updated (if exists) anytime your machine receive an update

Now i do not know the specific but if clover suggest and apply that one, its most probably the the latest checked against your smbios model.

 

Hi @LAbyOne @BuXb Sorry if I made a mistake, but.. :

Below Opencore Model data update 2 months ago. @BuXb in your config.plist: are you also change BiosReleasedate and BiosVersion data to the newest ! 

BIOSVendor: "Apple Inc."
BIOSVersion: "1968.100.17.0.0"
BIOSLegacyVersion: "MBP154.88Z.F000.B00.2303040348"
BIOSReleaseDate: "03/04/2023"
SystemManufacturer: "Apple Inc."
SystemProductName: "MacBookPro15,4"
SystemVersion: "1.0"
# Note, this one is used by macserial
SystemSerialNumber: "FVFYV019L40Y"
SystemSKUNumber: ""
SystemFamily: "MacBook Pro"
BoardManufacturer: "Apple Inc."
# This and similar ones can be an array itself, like this:
# BoardProduct:
#  "Mac-53FDB3D8DB8CA971"
#  "Mac-smthelse"
BoardProduct: "Mac-53FDB3D8DB8CA971"
BoardVersion: "MacBookPro15,4"
# FIXME: check
BoardRevision: 0x1
BoardAssetTag: ""
BoardType: 0xA
BoardLocationInChassis: ""
ChassisManufacturer: "Apple Inc."
ChassisType: 0x9
ChassisVersion: "Mac-53FDB3D8DB8CA971"

Below Clover platformdata:
  

    { MacBookPro151, "MBP151.88Z.F000.B00.2107050205"_XS8, "715.0.57.0.0"_XS8, "Mac-937A206F2EE63C01"_XS8, // Intel Cor…
    { MacBookPro152, "MBP152.88Z.F000.B00.2107050204"_XS8, "1715.0.57.0.0"_XS8, "Mac-827FB448E656EC26"_XS8, // Intel Co…
    { MacBookPro153, "MBP153.88Z.F000.B00.2107050204"_XS8, "1715.0.57.0.0"_XS8, "Mac-1E7E29AD0135F9BC"_XS8, // Intel Co…
    { MacBookPro154, "MBP154.88Z.F000.B00.2107050236"_XS8, "1715.0.57.0.0"_XS8, "Mac-53FDB3D8DB8CA971"_XS8, // Intel Co…

 

BuXb
BuXb
Posted
Posted (edited)

@LAbyOne Latest Efi Firmware Version for the MacBookPro15,4 is 1968.120.12.0.0 = more recent than the 1715.0.57.0.0 imposed by Clover. Therefore the calculation behind 

0:124  0:000  Warning: EfiVersion '1968.100.17.0.0' is older than default ('1715.0.57.0.0')

and consequently both, the error message and Clover disregarding the newer string is not correct.

 

@Matgen84  great, thank you! Even OC v. 0.9.2's platformdata is thus a bit outdated - 1968.100.17.0.0 (old) vs. 1968.120.12.0.0 (current). But even with BiosReleasedate and BiosVersion data updated to the most recent, Clover does not accept the values.

 

@Slice (or whoever else can): can you:

a) pull over the current platformdata from OC so it's updated in the next Clover release (or even nightly)?

b) correct the function which calculates if a string value is higher = newer or lower = older than the one coded into Clover?

 

That would be awesome 😎

 

Thanks for all your input, folks - very much appreciated!

Edited by BuXb
  • Like 2
BuXb
BuXb
Posted
Posted

@Slice Cool, so it's narrowed down already. Can you point me to the function in the code on GitHub which calculates if the manually entered EfiVersion string is older or newer than the default one? Maybe I can figure out how to correct it. My code skills are kind of rusty, but oh well, it's worth a try. Above all it should be logic to be applied, shouldn't it.

Slice
Slice
Posted
Posted

Yes 

6:166  0:001  Using latest EfiVersion from config instead of default '1715.0.57.0.0'
6:167  0:001  BiosVersion: IM131.88Z.F000.B00.1912181754
6:168  0:000  BiosReleaseDate: 12/18/2019
6:169  0:001  EfiVersion: 1968.100.17.0.0

 

  • Thanks 1
Matgen84
Matgen84
Posted
Posted

Hi @Slice

I can't build Clover latest 0bc9659 (XCODE 14,2) 🥲

 

Spoiler

build.py...
 : error C0DE: Unknown fatal error when processing [/Users/mathieu/src/Cloverbootloader/OpenCorePkg/Library/OcDebugLogLibOc2Clover/OcDebugLogLibOc2Clover.inf [X64, XCODE8, RELEASE]]
    
(Please send email to devel@edk2.groups.io for help, attaching following call stack trace!)

(Python 3.11.2 on darwin) Traceback (most recent call last):
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 1388, in _BuildPa
    RemoveDirectory(AutoGenObject.BuildDir, True)
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/Source/Python/Common/Misc.py", line 443, in RemoveDirectory
    os.rmdir(Directory)
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/Source/Python/Common/LongFilePathOs.py", line 33, in rmdir
    return os.rmdir(LongFilePath(path))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 66] Directory not empty: '/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2695, in Main
    MyBuild.Launch()
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 2488, in Launch
    self._BuildPlatform()
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 1823, in _BuildPlatform
    self._BuildPa(self.Target, Pa, FfsCommand=CmdListDict,PcdMaList=PcdMaList)
  File "/Users/mathieu/src/Cloverbootloader/BaseTools/BinWrappers/PosixLike/../../Source/Python/build/build.py", line 1389, in _BuildPa
    except WindowsError as X:
           ^^^^^^^^^^^^
NameError: name 'WindowsError' is not defined
 

 

 Share
Go to topic listing
×
×
  • Create New...