Jump to content
30960 posts in this topic

Recommended Posts

6 hours ago, kushwavez said:

Hello all!
 

I doesn't seem to receive updates on Ventura, seems like the hwtarget isn't working. Is this known?

I have set it to J160AP, it worked on Monterey, but now is not. hwtarget is empty when I get it in Terminal

11:06:46 > kushwavez@X1C6-Pro:~$ softwareupdate -l
Software Update Tool

Finding available software
No new software available.
11:06:55 > kushwavez@X1C6-Pro:~$ sysctl hw.target
hw.target:
11:06:58 > kushwavez@X1C6-Pro:~$ csrutil status
System Integrity Protection status: enabled.
<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x00</string>
		<key>HWTarget</key>
		<string>J160AP</string>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>

SMBIOS I am using is: MacBookPro15,2 on Lenovo X1 Carbon 6th (i7-8650U)

Should I change anything?

Clover v5151

 

Hi @kushwavez Do you try J132AP for SMBIOS MacBookPro15,2 instead of J160AP. According to platform file in Clover Github repository, J160AP is for SMBIOS macPro7,1. If I am not mistaken.
 

Capture d’écran 2023-01-18 à 17.34.36.png

Edited by Matgen84
8 hours ago, kushwavez said:

Hello all!
 

I doesn't seem to receive updates on Ventura, seems like the hwtarget isn't working. Is this known?

I have set it to J160AP, it worked on Monterey, but now is not. hwtarget is empty when I get it in Terminal

11:06:46 > kushwavez@X1C6-Pro:~$ softwareupdate -l
Software Update Tool

Finding available software
No new software available.
11:06:55 > kushwavez@X1C6-Pro:~$ sysctl hw.target
hw.target:
11:06:58 > kushwavez@X1C6-Pro:~$ csrutil status
System Integrity Protection status: enabled.
<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x00</string>
		<key>HWTarget</key>
		<string>J160AP</string>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>

SMBIOS I am using is: MacBookPro15,2 on Lenovo X1 Carbon 6th (i7-8650U)

Should I change anything?

Clover v5151

I am sorry but HWTarget no more works in Ventura. So to get updates we have to set SMBIOS for models without T2.

  • Like 2
4 minutes ago, PG7 said:

@Slice  @Jief_Machak


LEGACY Boot

 

Too bad Clover couldn't do the complete installation or update of the latest system on a non-UEFI PC (Legacy)

would there be a solution?

 

 

thanks team

I don't know what is the issue but I know that since BigSur we need hardware NVRAM which is absent on legacy computers.

QEMU works with legacy Clover.

  • Like 1
21 hours ago, PG7 said:

and will it be possible to somehow emulate the NVRAM or are we without a solution?

Yes, legacy system is able to emulate NVRAM but when the system installed. The problem is during installation.

16 hours ago, Slice said:

Yes, legacy system is able to emulate NVRAM but when the system installed. The problem is during installation.

yes I use Clover on Legacy machines with Ventura, Monterey and BigSur

I just can't even update or install these latest complete systems with Clover

AnyBody Interested In Helping Me Resurrect My OLD CloverGrower
To Compile And Do Other Things 

Maybe OCGrower As Well

https://github.com/STLVNUB/CloverGrower

Edited by STLVNUB

@STLVNUB

I'm actually now in the process to migrate Clover Suite Builder to something else

https://github.com/LAbyOne/Clover-Suite-Builder-SetUp

which is most likely a merged version of Clover Suite Builder + Clover Setup

(for now i just created the page, i'm still not so sure if it's really a good idea (lol), and files will be up pretty soon)

in the meantime i'm also thinking about building a Themes Downloader with a decent GUI, but still evaluating / testing all possible ideas

so not really available

So if you ever need some advice feel free to ask, and if I can will gladly help.

  • Like 3
  • Thanks 1
  • 3 weeks later...

Hi @Slice

 

I build Clover with Xcode 12.4

Commit 777e573 update nasm to 2.16.01. How to update my local existing nasm 2.15.05 ? Just using buildnasm.sh, right ! Let me know, please

42 minutes ago, Matgen84 said:

Hi @Slice

 

I build Clover with Xcode 12.4

Commit 777e573 update nasm to 2.16.01. How to update my local existing nasm 2.15.05 ? Just using buildnasm.sh, right ! Let me know, please

I think the question is to @LAbyOne

I will look.

  • Like 1

@Matgen84

Internal build system will check if NASm version is greater then 2.12 to update to newer version.

But as you have 2.15 then no update is proposed. You should do it by yourself with the script buildnasm.sh or just download binary from nasm.org.

Or just don't bother.

  • Thanks 1
2 hours ago, LAbyOne said:

ok

updated nasm version check on main script

will pull it in a moment

 

also is now safe to remove "isl archive" from repo I guess

I included isl archive into repo because otherwise I can't download it from usual addresses. 

If now build from scratch works then we can exclude extra file.

3 hours ago, Slice said:

I included isl archive into repo because otherwise I can't download it from usual addresses. 

If now build from scratch works then we can exclude extra file.

Yes it does

Now get the files directly from source

hello, is there any setting with Clover to put in the config.plist,in Platforminfo with CustomMemory under Smbios MacPro 7,1 ?

 

like memory/devices ?

 

restrictevents.kext, does not prevent the warning of the memory installation fault under clover in my config Z390

 

thanks

 

Edited by odemolay
On 2/23/2023 at 6:57 PM, odemolay said:

hello, is there any setting with Clover to put in the config.plist,in Platforminfo with CustomMemory under Smbios MacPro 7,1 ?

 

like memory/devices ?

 

restrictevents.kext, does not prevent the warning of the memory installation fault under clover in my config Z390

 

thanks

 

But what is the problem? How it is looked? Yes clover has some setting about memory in SMBIOS section.

ok i make myself clear, rescrictsevent.kext ddoesn't work in my case, i dont know why. 

i had custumised my config.plist opencore with the personnal settings to not use rescrictsevent.kext

but i do prefer tu use clover, so i was wondering if i can do the same in my config.plist Clover.

or if there is a special setting to make work restrictesevent with.

 

Spoiler

image.png.e16762a70a705e12d01350c885224be8.png

 

Edited by odemolay
  • 3 weeks later...

This is probably a remedial question, so forgive my naivete.  Would anyone be able to briefly explain how CLOVER patches macOS kernel and kexts?  What I don't understand is how CLOVER is able to implement kernel and kext patches if CLOVER operates before macOS boots.  Do CLOVER kernel and kext patches operate on kernel in memory, or do they patch a cache that is stored on disk before macOS boots?  Also, are CLOVER kext patches able to patch kexts that are stored in /S/L/E and also kexts that are stored in /L/E?

 

Thank you.

16 hours ago, deeveedee said:

This is probably a remedial question, so forgive my naivete.  Would anyone be able to briefly explain how CLOVER patches macOS kernel and kexts?  What I don't understand is how CLOVER is able to implement kernel and kext patches if CLOVER operates before macOS boots.  Do CLOVER kernel and kext patches operate on kernel in memory, or do they patch a cache that is stored on disk before macOS boots?  Also, are CLOVER kext patches able to patch kexts that are stored in /S/L/E and also kexts that are stored in /L/E?

 

Thank you.

In the older system there was prelinkedkernel downloaded into memory by boot.efi. Then boot.efi eject event ExitBootServices which catched by Clover and then Clover find the prebootkernel in memory and applies patches to it.

Since BigSur the behavior changed. Now we have KernelCollections where we should make the patches. All gratitudes for the algorithm to Vit9696. We just call OpenCore as a library and commit the patches to it.

  • Like 2
  • Thanks 1

@Slice Thank you for the explanation.  I was trying to help someone patch HD4000 VRAM.  In "the old days" the patch was achieved by performing a binary replace in AppleIntelFramebufferCapri.kext/Contents/MacOS/AppleIntelFramebufferCapri as follows:

sudo perl -pi -e 's|\x00.{1}\x10\x07\x00\x00\x10\x07|\x00\x80\x10\x07\x00\x00\x10\x07|g' AppleIntelFramebufferCapri.kext/Contents/MacOS/AppleIntelFramebufferCapri

 

I attempted to apply the following kernel patch (to replace the edit of the raw kext), but it doesn't work:

Find: <0000100700001007>
Identifier: com.apple.driver.AppleIntelFramebufferCapri
Mask: <FF00FFFFFFFFFFFF>
Replace: <0080100700001007>

 

I am only able to make the AppleIntelFramebufferCapri patch for HD4000 by using WhateverGreen.kext and the following DeviceProperties:

framebuffer-patch-enable 1
framebuffer-unifiedmem <00000080> 

 

Do you know why the kernel patch (Find/Replace) doesn't work, the perl edit of the raw kext (and then rebuilding KextCache) does work?  It seems to me that the kernel patch should achieve the same as the perl edit.  Thank you.

Edited by deeveedee

Yes, graphics kext can't be patched from a bootloader because they are not present in bootkernelcollection. I don't know details.

You should write a plugin for Lilu which is able patch kernel and kext when a system is already working.

Or other way, like OCLP you should patch a kext and then apply a method like OCLP to use this kext[k] in the system.

  • Thanks 1

Hi @Slice and all

 

I would like to go to Monterey on my old ivybridge with Catalina installed. Is this possible? Of course I would like to keep Clover as my bootloader.

How do I do this, if it is possible.

 

Thanks for your help.

×
×
  • Create New...