LAPIC kernel panics upon injecting AppleHDA into Tahoe through MyKextInstaller

[RobinAnd]

Was directed here by Mirone

 

Upon injecting AppleHDA into Tahoe, I receive a LAPIC kernel panic. I have tried:
- Enabling LapicKernelPanic in Kernel > Quirks

- Adding 

lapic_dont_panic=1 cpus=1

to my boot args (lapic_dont_panic on its own does not work, and cpus=1 causes a panic on virtualsmc and lilu)

 

I am at a loss on what to do, and I really need help.

config.plist

[Slice]

Did you have HP computer? Please make your signature.

[RobinAnd]

So sorry for not adding my signature. It's now there.

[Slice]

It is the common problem for HP computers and the quirk LapicKernelPanic  must work and other users are successful with HP in Tahoe.

[Mirone]

Look this:

 

[RobinAnd]

I'll try the

amfi=0x80

and see if that works.

Edited October 27, 2025 by RobinAnd

[verdazil]

22 minutes ago, RobinAnd said:

amfi=0x80

In modern versions of macOS, the amfi=0x80 boot argument is deprecated and no longer functional.
It has been replaced by amfi_get_out_of_my_way=1, which properly disables AMFI on current systems.

[RobinAnd]

Well that's the only difference that I can find in their tutorial vs mine (except theirs uses OpCore-Simplify and OCAT, which I'm NOT doing)

[RobinAnd]

This sadly didn't work and it still panics

[Slice]

7 hours ago, RobinAnd said:

This sadly didn't work and it still panics

Try Clover, it has PatchAPIC possibility.

Anyway try also VoodooTSCsync.kext