Lapic Kernel Patch on Yosemite

hadyhallak said:

Hi

On mavericks we where using a patched kernel for having a full processor cores

as described here

so is there a new method for patching the kernel on Yosemite

I'm using a temporary solution now by adding "cpus=1" boot flag

Click to expand...

hadyhallak said:

I installed the module

the following is logged on the boot loader :

Code:

Read HFS+ file: [hd(0,1)/System/Library/Kernels/kernel] 4069 bytes
Read HFS+ file: [hd(0,1)/System/Library/Kernels/kernel] 10617640 bytes
kernel_patcher.c[549]: patching 64bit XNU Kernel 14.0.0
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; "patched-2782.1.97~2/RELEASE_X86_64"/
commpage_patch.c[87]: _commpage_stuff_routine patched.
lapic_patch.c[76]: lapic_init panic removed.
lapic_patch.c[133]: lapic_interrupt panic removed
bootstrap_patch.c[167]: KLDBootstrap:readBooterExtensions() call injected into KLDBootstrap::readPrelinkedExtensions(void* section_64)
kernel_patcher.c[341]: Returning...
Press a key to continue...

I continued .. while loading kexts when i comes to
Read hfs+ file : ..../AppleKextExcludeList.kext

screen goes dark and I shutdown the laptop forcibly

Click to expand...

hadyhallak said:

No Only Radeon Graphics, But what's the problem ???

Click to expand...

hadyhallak said:

Removing AppleKextExecludeList.kext solved the problem...
seems that Yosemite Prevents unsigned kext from loading ?

But I have
<key>Kernel Flags</key>
<string>kext-dev-mode=1</string>

Click to expand...

hadyhallak said:

after some diagnostics I found out the following

when deleting the kernel_patcher module things goes great and everything is okay.

but when it's installed the problem goes back.

so is it a problem with patching the kernel or what??


I'm using an original AppleKextExcludeList.kext

Click to expand...