Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
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.

PG7
PG7
Posted
Posted
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

Slice
Slice
Posted
Posted
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
Slice
Slice
Posted
Posted
33 minutes ago, PG7 said:

preboot.log 58.54 kB · 1 download

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>

 

PG7
PG7
Posted
Posted
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 ?

 

jsl2000
jsl2000
Posted
Posted
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

Slice
Slice
Posted
Posted
On 10/26/2022 at 5:24 PM, PG7 said:

 

tested but it didn't work

how can I try to repair lapic ?

 

I compared Lapic patch in recent Opencore and in Clover. They are identical.

 

But I may propose to test new ProvideCurrentCpuInfo quirk as it changed in Opencore.

For my Skylake it produces wrong bus speed and sound is crackled. But I hope it will work for AlderLake.

CLOVERX64.efi.zip

PG7
PG7
Posted
Posted
6 hours ago, Slice said:

I compared Lapic patch in recent Opencore and in Clover. They are identical.

 

But I may propose to test new ProvideCurrentCpuInfo quirk as it changed in Opencore.

For my Skylake it produces wrong bus speed and sound is crackled. But I hope it will work for AlderLake.

CLOVERX64.efi.zip 743.48 kB · 1 download

looks the same 😢

  • Like 1
jsl2000
jsl2000
Posted
Posted (edited)
10 hours ago, PG7 said:

looks the same 😢

My Sandy Bridge Q65 hackintosh (Acer Veriton M4610 MB) had the same KP issue at Monterey or ventura if not add cpus=1.

It seems VoodooTSCSync.kext (v. 1.1) not compatible to this old hardware.

All my legacy Clover (5149 or 5150) booting hackintoshs (LGA 775, X58, Q65, & FX-6300) always got red screen panic if ProvideCurrentCpuInfo quirk was enabled.

No such an issue of Clover 5148.

Screenshot 2022-10-28 at 7.33.28 PM.png

Edited by jsl2000
  • Like 1
Slice
Slice
Posted
Posted
13 minutes ago, jsl2000 said:

My Sandy Bridge Q65 hackintosh (Acer Veriton M4610 MB) had the same KP issue at Monterey or ventura if not add cpus=1.

It seems VoodooTSCSync.kext (v. 1.1) not compatible to this old hardware.

All my legacy Clover (5149 or 5150) booting hackintoshs (LGA 775, X58, Q65, & FX-6300) always got red screen panic if ProvideCurrentCpuInfo quirk was enabled.

No such an issue of Clover 5148.

 

Did you try the quirk TscSyncTimeout=750000 with Clover 5150?

 

I see no reasons why VoodooTSCSync.kext (v. 1.1) is not compatible with old hardware. Just set thread count in info.plist.

  • Thanks 1
jsl2000
jsl2000
Posted
Posted
49 minutes ago, Slice said:

Did you try the quirk TscSyncTimeout=750000 with Clover 5150?

 

I see no reasons why VoodooTSCSync.kext (v. 1.1) is not compatible with old hardware. Just set thread count in info.plist.

Yes, I had tried the quirk TscSyncTimeout=750000 with Clover 5150 but in vain and I must disable ProvideCurrentCpuInfo quirk to prevent red screen panic on booting.

  • Thanks 1
PG7
PG7
Posted
Posted (edited)
1 hour ago, Slice said:

Did you try the quirk TscSyncTimeout=750000 with Clover 5150?

 

I see no reasons why VoodooTSCSync.kext (v. 1.1) is not compatible with old hardware. Just set thread count in info.plist.

here in several machines i find this problem in HP about everything in 2 over 3, the same problem happens with clover or opencore which all indicates that there was change with patch LAPIC in Ventura !

Edited by PG7
  • Like 1
  • Thanks 1
Slice
Slice
Posted
Posted
3 hours ago, PG7 said:

here in several machines i find this problem in HP about everything in 2 over 3, the same problem happens with clover or opencore which all indicates that there was change with patch LAPIC in Ventura !

May be you should cancel using patch lapic? 

	<key>KernelAndKextPatches</key>
	<dict>
		<key>KernelLapic</key>
		<false/>

But set patch apic 

	<key>ACPI</key>
	<dict>
		<key>PatchAPIC</key>
		<true/>

 

  • Like 2
  • Thanks 1
jsl2000
jsl2000
Posted
Posted (edited)
15 hours ago, Slice said:

May be you should cancel using patch lapic? 

	<key>KernelAndKextPatches</key>
	<dict>
		<key>KernelLapic</key>
		<false/>

But set patch apic 

	<key>ACPI</key>
	<dict>
		<key>PatchAPIC</key>
		<true/>

 

Unfortunately my Sandy Bridge Acer Veriton M4610 & X58 P6TSE hackintoshs can not boot by Clover 5149 or 5150 even ProvideCurrentCpuInfo was disabled because it always got red screen panic !

Only OC 0.8.5 can boot it successfully but VoodooTSCSync.kext only worked up to Big Sur. At Monterey or Ventura I must add cpus=1 to prevent KP during booting.

Edited by jsl2000
Matgen84
Matgen84
Posted
Posted (edited)

Hi all

 

I create an USB Installer (Clover r5150 commit 9300267) to clean install Ventura 13.0 Release. First boot, Clover GUI don't show Ventura icon in the installer, only the generic macOS icon

 

Did I make a mistake somewhere!

Edited by Matgen84
  • Sad 1
naiclub
naiclub
Posted
Posted
2 hours ago, Matgen84 said:

Hi all

 

I create an USB Installer (Clover r5150 commit 9300267) to clean install Ventura 13.0 Release. First boot, Clover GUI don't show Ventura icon in the installer, only the generic macOS icon

 

Did I make a mistake somewhere!

I think you may not have done anything wrong. It's been like that for a long time. Show some, don't show some, definitely nothing at all. It's showing, but when I booted to the Hai Sierra, it turned out to be the Hai Sierra icon.

  • Like 1
Slice
Slice
Posted
Posted
On 10/29/2022 at 3:37 PM, Matgen84 said:

Hi all

 

I create an USB Installer (Clover r5150 commit 9300267) to clean install Ventura 13.0 Release. First boot, Clover GUI don't show Ventura icon in the installer, only the generic macOS icon

 

Did I make a mistake somewhere!

The answer to your question is in preboot.log obtained by F2.

  • Like 1
  • Thanks 1
Matgen84
Matgen84
Posted
Posted
15 hours ago, Slice said:

The answer to your question is in preboot.log obtained by F2.

 

Thanks for your asnwer. 😊

 

Since the second boot and installation of Ventura, there are no more problems with the Ventura icons. I forgot to type F2. What preboot.log would show !

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