Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

55 minutes ago, PG7 said:

how can I do that?

my Config.plist CLover 

 

 

Clover must be up to date. TscSyncTimeout is a new quirk with default value 0. For testing,  the recommended starting value is 500000. (Dortinia guide) See below.

 

Spoiler

TscSyncTimeout

Type: plist integer

Failsafe: 0

Description: Attempts to perform TSC synchronisation with a specified timeout.

The primary purpose of this quirk is to enable early bootstrap TSC synchronisation on some server and laptop

models when running a debug XNU kernel. For the debug kernel the TSC needs to be kept in sync across the cores

before any kext could kick in rendering all other solutions problematic. The timeout is specified in microseconds

and depends on the amount of cores present on the platform, the recommended starting value is 500000.

This is an experimental quirk, which should only be used for the aforementioned problem. In all other cases, the

quirk may render the operating system unstable and is not recommended. The recommended solution in the

other cases is to install a kernel extension such as VoodooTSCSync, TSCAdjustReset, or CpuTscSync (a more

specialised variant of VoodooTSCSync for newer laptops).

Note: This quirk cannot replace the kernel extension because it cannot operate in ACPI S3 (sleep wake) mode

and because the UEFI firmware only provides very limited multicore support which prevents precise updates of

the MSR registers.

 

Edited by Matgen84
Link to comment
Share on other sites

On 10/19/2022 at 12:39 PM, Slice said:

I don't think the problem is in Lapic Kernel Patch. 

Probably you should test TscSyncTimeout patch.

@Slice

sorry not to have indicated that i used already the CpuTscSync.kext as the KernelLAPIC clover in the first verses of Ventura Beta worked normal but with the recent stopped working and only with you the boot with the args cpus=1which makes me think that it is even the LAPIC of this HP that is causing the Kernel Panic

*Google Translate

photo_2022-10-24 17.53.50.jpeg

Edited by PG7
Link to comment
Share on other sites

18 hours ago, Slice said:

Look this version. It works in Monterey on my computer #3 (8 cores, 16 threads). 

Recent Clover supported the quirk TscSyncTimeout which is in my case = 750000.

VoodooTSCSync.kext.zip 8.16 kB · 4 downloads

Hy @Slice

 

here does not work in any way I tested already everything and I can not pass the kernel panic print but using args cpus=1 there enters normal in systyem but only with 1 cpu

Edited by PG7
Link to comment
Share on other sites

43 minutes ago, PG7 said:

Hy @Slice

 

here does not work in any way I tested already everything and I can not pass the kernel panic print but using args cpus=1 there enters normal in systyem but only with 1 cpu

Look to Info.plist of the kext. I wrote here 15 because I have 16 threads. You should write your number of threads - 1.

Link to comment
Share on other sites

4 hours ago, Slice said:

Look to Info.plist of the kext. I wrote here 15 because I have 16 threads. You should write your number of threads - 1.


@Slice  

have some sugestao to test,

I leave here the full EFI of r5150


Thanks for everything


EFI

Link to comment
Share on other sites

13 hours ago, PG7 said:


@Slice  

have some sugestao to test,

I leave here the full EFI of r5150


Thanks for everything


EFI

You'd better show me preboot.log obtained from Clover GUI by pressing F2. May be this way I'll see the problem.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

33 minutes ago, PG7 said:

I forgot to mention that you should edit VoodooTSCsync/Contents/Info.plist my value 15 to your value 3 because you have 

0:193  0:000  Threads: 4

Here

			<key>IOPropertyMatch</key>
			<dict>
				<key>IOCPUNumber</key>
				<integer>3</integer>
			</dict>

 

Link to comment
Share on other sites

Il y a 36 minutes, Slice a dit :

 

			<key>IOPropertyMatch</key>
			<dict>
				<key>IOCPUNumber</key>
				<integer>3</integer>
			</dict>

 

image.png.d949e6dc73f878ffa9e50c6992ef0462.png

51 minutes ago, Slice said:

Regardez ici

image.png

C’est peut-être votre cas. Je vois que vous avez le soutien de MATS.

tested but it didn't work

how can I try to repair lapic ?

 

Link to comment
Share on other sites

On 10/25/2022 at 12:58 AM, Slice said:

Look this version. It works in Monterey on my computer #3 (8 cores, 16 threads). 

Recent Clover supported the quirk TscSyncTimeout which is in my case = 750000.

VoodooTSCSync.kext.zip 8.16 kB · 8 downloads

Thanks for the new VoodooTSCSync.kext but it still not working for my Sandy Bridge Hackintosh (Acer Veriton M4610 MB) at Monterey or Ventura.

Only add cpus=1 can boot Monterey or Ventura without KP.

At Big Sur or lower macOS previous or your VoodooTSCSync.kext worked very well for 2C4T CPU with IOCPUNumber=3

Link to comment
Share on other sites

×
×
  • Create New...