Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

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

Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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 !

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
2 hours ago, Slice said:

Preboot.log shows what entries Clover found, what operating systems and what bootloaders, what disks for legacy boot and who is hidden and why.

 

I find a preboot.log (probably second boot during Ventura Installation). I don't understand why 'GetDefaultModel' is Imac18,3 before using SMBIOS data in config.plist. (My Z390 : i7 9700k)

Sorry for my bad English.

 

 

2022-10-29_12-17_CLOVERX64-r5150_9300267.efi.log

Edited by Matgen84
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
46 minutes ago, Matgen84 said:

 

I find a preboot.log (probably second boot during Ventura Installation). I don't understand why 'GetDefaultModel' is Imac18,3 before using SMBIOS data in config.plist. (My Z390 : i7 9700k)

Sorry for my bad English.

 

 

2022-10-29_12-17_CLOVERX64-r5150_9300267.efi.log 54.47 kB · 0 downloads

Spoiler

0:108  0:000  _checkOEMPath Look for oem dir at path '\EFI\CLOVER-5149\OEM\Z87X-UD3H-CF\UEFI'. Dir doesn't exist.
0:108  0:000  _checkOEMPath Look for oem dir at path '\EFI\CLOVER-5149\OEM\Z87X-UD3H'. Dir doesn't exist.
0:108  0:000  _checkOEMPath Look for oem dir at path '\EFI\CLOVER-5149\OEM\Z87X-UD3H-3800'. Dir doesn't exist.
0:108  0:000  _checkOEMPath Look for oem dir at path '\EFI\CLOVER-5149\OEM\Z87X-UD3H-CF'. Dir doesn't exist.
0:108  0:000  _checkOEMPath Look for oem dir at path '\EFI\CLOVER-5149\OEM\Z87X-UD3H-CF-3800'. Dir doesn't exist.
0:108  0:000  === [ GetUserSettings ] =========================
0:108  0:000  GetDefaultModel()=iMac14,2
0:109  0:000  Using config.plist at path: \EFI\CLOVER-5149
0:109  0:000  Cannot find smbios.plist at path '\EFI\CLOVER-5149' : Not Found
0:109  0:000  '\EFI\CLOVER-5149\smbios.plist' not loaded. Efi error Not Found
0:109  0:000  Using latest BiosVersion from config instead of default 'IM191.88Z.F000.B00.2106222356'
0:109  0:000  Using latest BiosReleaseDate from config instead of default '06/22/2021'
0:109  0:000  Using latest EfiVersion from config instead of default '1554.140.20.0.0'
0:109  0:000  BiosVersion: IM191.88Z.F000.B00.2203311557
0:109  0:000  BiosReleaseDate: 03/31/2022
0:109  0:000  EfiVersion: 1731.120.8.0.0
 

Yes, similar symptoms to mine

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
1 hour ago, Matgen84 said:

 

I find a preboot.log (probably second boot during Ventura Installation). I don't understand why 'GetDefaultModel' is Imac18,3 before using SMBIOS data in config.plist. (My Z390 : i7 9700k)

Sorry for my bad English.

 

 

2022-10-29_12-17_CLOVERX64-r5150_9300267.efi.log 54.47 kB · 1 download

This is default value if you don't specify own value. You do

17:629  0:014  void PatchTableType1(const SmbiosInjectedSettings &) : UpdateSmbiosString ProductName=iMac19,1

But next you make a little mistake

void PatchTableType2(const SmbiosInjectedSettings &) : UpdateSmbiosString Version=BoardVersion=Imac19,1

not Imac but iMac!

  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
36 minutes ago, Slice said:

This is default value if you don't specify own value. You do

17:629  0:014  void PatchTableType1(const SmbiosInjectedSettings &) : UpdateSmbiosString ProductName=iMac19,1

But next you make a little mistake

void PatchTableType2(const SmbiosInjectedSettings &) : UpdateSmbiosString Version=BoardVersion=Imac19,1

not Imac but iMac!

 

Right. The correct syntax is iMac19,1 not Imac19,1. So I correct my config.plist. Thanks. 

  • Like 1
Link to comment
Share on other sites
PG7
PG7
Posted
Posted (edited)
On 10/24/2022 at 5:48 PM, PG7 said:

@Slice

 ****. Sloved 

 ( Delete ARGS "debug=0x100" )

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

@Slice

ola thanks for all that tried to help, resolution of the error that was presented is simply the ARGS "debug=0x100" that was doing all this problem HICBY for the error is delete args "debug=0x100"

 

Spoiler

646548692_Capturedecran2022-11-02a12_10_33.thumb.png.10d6e271f69006b9578318a2bd4a9053.png556689574_Capturedecran2022-11-02a12_10_08.thumb.png.03bce3c36124a6ab97a90ff4d4af8d73.png



thanks team 

thanks Slice 

 

 

Edited by PG7
  • Like 1
  • Confused 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
6 hours ago, PG7 said:

@Slice

ola thanks for all that tried to help, resolution of the error that was presented is simply the ARGS "debug=0x100" that was doing all this problem HICBY for the error is delete args "debug=0x100"

 

  Reveal hidden contents



thanks team 

thanks Slice 

 

 

It is not resolution but workaround. See 

ffffff80004785d7 833D3A31AA0000                  cmp        dword [ds:_debug_boot_arg], 0x0
ffffff80004785de 740D                            je         0xffffff80004785ed      <- this is a way to avoid panic, if "debug=0"
                                       ; Basic Block Input Regs: <nothing> -  Killed Regs: <nothing>
ffffff80004785e0 833DEDF29E0000                  cmp        dword [ds:0xffffff8000e678d4], 0x0
ffffff80004785e7 0F84FD000000                    je         0xffffff80004786ea     <-  this is jump to panic that non fixed
                                       ; Basic Block Input Regs: <nothing> -  Killed Regs: rax
ffffff80004785ed 658B042520000000                mov        eax, dword [gs:0x20]          ; XREF=0xffffff80004785de
ffffff80004785f5 3B05D555A600                    cmp        eax, dword [ds:_master_cpu]
ffffff80004785fb 0F85E9000000                    jne        0xffffff80004786ea     <-  this is jump to panic that patched by LapicPatch (OC or Clover)

I don't know what is the first condition for panic. It may be the number of interrupts and may be this can be resolved by DSDT patches.

It is check for "lapic_dont_panic".

Anyway your workaround is good enough.

  • Thanks 1
Link to comment
Share on other sites
LAbyOne
LAbyOne
Posted
Posted (edited)

 

2 hours ago, oldman20 said:

which value I need when want to disable SIP?

https://github.com/5T33Z0/Clover-Crate/tree/main/RtVariables#readme

in this I choose 0xFEF for CsrActiveConfig is correct?

 

 

SIP values are :

 

4.png

depending on your needs you get to choose among them

the sum will give you the final value to enable/disable SIP on your machine.

So either you know exactly what you want to disable and ask / calculate the right value

you might need  or explain what you want to achieve

 

The value you posted there will disable :

 

CSR_ALLOW_UNTRUSTED_KEXTS
CSR_ALLOW_UNRESTRICTED_FS
CSR_ALLOW_TASK_FOR_PID
CSR_ALLOW_KERNEL_DEBUGGER
CSR_ALLOW_UNRESTRICTED_DTRACE
CSR_ALLOW_UNRESTRICTED_NVRAM)
CSR_ALLOW_DEVICE_CONFIGURATION
CSR_ALLOW_ANY_RECOVERY_OS
CSR_ALLOW_UNAPPROVED_KEXTS
CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE
CSR_ALLOW_UNAUTHENTICATED_ROOT      //  <----      Mostly used to disable this one

 

Edited by LAbyOne
  • Like 4
  • Thanks 2
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...