[Acer PT14-51 Laptop] HowTo

[Stezza88]

sgiammoript@MacBook-Pro ~ % sudo kextload -v /Library/Extensions/AppleIntelICLLPGraphicsFramebuffer.kext
Password:
Executing: /usr/bin/kmutil load -p /Library/Extensions/AppleIntelICLLPGraphicsFramebuffer.kext
Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer' names a dependency on 'org.smichaud.HookCase', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer' names a dependency on 'org.smichaud.HookCase', which was not found.}

but bookcase.kext builded from master is already in the L/E folder

 

I did this also

chmod -R 755 test/Apple*
chown -R root:wheel test/Apple*
move the files to /L/E
delete /Library/KernelCollections/AuxiliaryKernelExtensions.kc
redo chown -R root:wheel /Library/Extensions/Apple*

 

Edited October 23, 2024 by ASUS Vivobook

[jalavoui]

did you fix hookcase permissions?

 

i'm gonna check if master build works.

 

done - loading fine for me

 

i think you dont need but here the files i used in /L/E

 

Arquivo.zip

 

from linux logs i kinda have a hope tgl framebuffer does somethins usefull

Edited October 23, 2024 by jalavoui

[Stezza88]

Now I fixed perms to hookcase.kext, then OS ask me to restart, did it and I received this after kextload

sgiammoript@MacBook-Pro test % sudo kextload -v /Library/Extensions/AppleIntelICLLPGraphicsFramebuffer.kext
Password:
Executing: /usr/bin/kmutil load -p /Library/Extensions/AppleIntelICLLPGraphicsFramebuffer.kext
Error Domain=KMErrorDomain Code=29 "Authenticating extension failed: Kext com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer v16.0.0 in executable kext bundle com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer at /private/var/db/KernelExtensionManagement/Staging/com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer.BWkfTz/AppleIntelICLLPGraphicsFramebuffer.kext:

Authenticating extension failed: Bad code signature" UserInfo={NSLocalizedDescription=Authenticating extension failed: Kext com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer v16.0.0 in executable kext bundle com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer at /private/var/db/KernelExtensionManagement/Staging/com.xxxxx.driver.AppleIntelICLLPGraphicsFramebuffer.BWkfTz/AppleIntelICLLPGraphicsFramebuffer.kext:

Authenticating extension failed: Bad code signature}

 

Edited October 23, 2024 by ASUS Vivobook

[jalavoui]

good it is working ! try change csrutil to get rid of that or maybe disableevents kext (i dont use that)

 

if you get  a panic during early stage check if you need to disable something in

 

maybe os x rebulded the cache.check with hexedit

 

when u managed to get it working check icl code

here you can enable/disable some hacks to make it work

Edited October 23, 2024 by jalavoui

[Stezza88]

ICLLE stucks in os loading the same.. os loading very slow too.. csrutil disabled.. now i try tglle

 

Edited November 2, 2024 by ASUS Vivobook

[jalavoui]

don't post pictures. log in and check logs

we need logs not pictures

 

[Stezza88]

here the log last 1 hour after trying ICLLE with boot arg IGLogLevel=8

x.log

Edited October 23, 2024 by ASUS Vivobook

[Stezza88]

32 minutes ago, jalavoui said:

good it is working ! try change csrutil to get rid of that or maybe disableevents kext (i dont use that)

 

if you get  a panic during early stage check if you need to disable something in

 

maybe os x rebulded the cache.check with hexedit

 

when u managed to get it working check icl code

here you can enable/disable some hacks to make it work

 

Where can i found master of ICL*/TGL* ?  .. cannot access the code with kexts only..

 

[TGLLE stucks in boot too]

Edited October 23, 2024 by ASUS Vivobook

[Stezza88]

Here the log after trying TGLLE ... stall finished between 2024-10-23 20:31:46 and 2024-10-23 20:44:06

 

this is the last command before stucking

2024-10-23 20:31:46.144458+0200  localhost kernel[0]: (IOUserBluetoothSerialDriver.dext) IOUserBluetoothSerialClient::Start Starting to create Serial Client

 

x.log

Edited October 23, 2024 by ASUS Vivobook

[jalavoui]

the logs show the kext is not loading at all. maybe it hangs at start or nblue info.plist as wrong/duplicated ids?

 

hope you can fix it. i can only help when we start to see some log lines like this

 

 

master code of icl/tgl ??? they're inside nblue. if you mean decompiled version try ghidra

 

try add extra debug lines in void NBlue::processPatcher(KernelPatcher &patcher) like this

SYSLOG("nblue","test 1");

...

SYSLOG("nblue","test 2");

Edited October 23, 2024 by jalavoui

[Stezza88]

7 minutes ago, jalavoui said:

the logs show the kext is not loading at all. maybe it hangs at start or nblue info.plist as wrong/duplicated ids?

 

One only id in nootedblue iokitpersonalities IOPrimaryMatch of Firstly in ICLLE then the same within TGLLE..

 

But i have modified also info.plist of AppleIntel* within IOPRIMARYMATCH of the two kexts in L/E too

 

0xA7A08086

Edited October 23, 2024 by ASUS Vivobook

[Stezza88]

I see that id Is differenti from what i inserted

 

Ah but is yours.. sorry

Edited October 23, 2024 by ASUS Vivobook

[jalavoui]

this from your log

 

 

means something is preventing the driver from loading at early start

maybe kexts load problem

 

check you only have your card id in

 

 

not on Gen7TGL, etc

 

this bug is annoying and hard to find

 

check id's in /L/E make sure they don't match your card or 0x9a49

 

i set 0x12348086 in /L/E to be sure they only load by using nblue

Edited October 23, 2024 by jalavoui

[Stezza88]

On 10/23/2024 at 9:07 PM, jalavoui said:

the logs show the kext is not loading at all. maybe it hangs at start or nblue info.plist as wrong/duplicated ids?

 

hope you can fix it. i can only help when we start to see some log lines like this

 

 

master code of icl/tgl ??? they're inside nblue. if you mean decompiled version try ghidra

 

try add extra debug lines in void NBlue::processPatcher(KernelPatcher &patcher) like this

SYSLOG("nblue","test 1");

...

SYSLOG("nblue","test 2");

 

I put SYSLOG("nblue","test1"); inside processPatcher but nothing found in tmp/x.log

 

"test 1" blank space leaves the time that it leaves

 

it seems that the method never be called

 

 

Edited October 26, 2024 by ASUS Vivobook

[jalavoui]

hmmm

 

maybe old lilu release ?

try this1

Lilu.kext.zip

 

agree with you looks like nblue is not loading at all or icl frame just hangs at probe() or start()

 

can be a acpi bug? i have imei device in my dsdt patches

or the XOSI bad defined bug? you dont seem to have a working SSDT-OSYS.aml (i got very bad bugs cause of this in the past)

 

take a look 

 

Arquivo.zip

 

sometimes i don't get log lines on very 1st boot

rebooting helps

 

you can use this in code wherever you want just set condition 1==1 instead of !this->igpu

 

you will get a kernel panic that can be seen on next reboot

 

found a bug in your config

dont do this!

Edited October 23, 2024 by jalavoui

[Stezza88]

1) There is something strange inside info.plist of my nootedblue ... take a look.. I'm using Sonoma 14.7...

 

NootedBlue.kext.zip

 

2) Lilu I'm using latest 1.6.9 version.. but for example liludbg or lilucpu boot flags never works to me... and this is strange too..

 

it seems that some kexts are not loaded..

Edited October 23, 2024 by ASUS Vivobook

[Stezza88]

.

Edited October 28, 2024 by ASUS Vivobook

[jalavoui]

RestrictEvents.kext help. check SSDT-OSYS.aml and acpi and lilu

SSDT-OSYS.aml makes os x loads certain devices/config settings it is very important

if you can get 1 that is tested for your laptop - better otherwise try make 1 or use the one i send

 

your nblue is all empty lol

no wonder it does nothing

 

add your card id here

 

if you wanna test tgl then set this empty and put id on TGLLE

 

if you wanna be sure other kexts won't load you can use 0x12348086 - but empty values are fine

 

you only will get problems if trying to load AppleIntelFramebufferControllerICL (ventura patches)

 

AppleIntelFramebufferControllerICLLE and AppleIntelFramebufferControllerTGLLE should load fine

 

Gen7TGL will load if using boot arg -allow3d (do that if framebuffer loads and you see os x boot screen)

 

dam if we had this discussion on the other thread it would reach 50 pages

 

on my dsdt if i try to use this

i get 100 bugs in acpi

but for some people it works fine

 

can you upload your ioreg using IORegistryExplorer ? maybe it helps

Edited October 23, 2024 by jalavoui

[Stezza88]

1 minute ago, jalavoui said:

RestrictEvents.kext help. check xosi and acpi

 

What is XOSI? What do you mean for check?

[Stezza88]

18 minutes ago, jalavoui said:

RestrictEvents.kext help. check SSDT-OSYS.aml and acpi and lilu

SSDT-OSYS.aml makes os x loads certain devices/config settings it is very important

if you can get 1 that is tested for your laptop - better otherwise try make 1 or use the one i send

 

your nblue is all empty lol

no wonder it does nothing

 

add your card id here

 

if you wanna test tgl then set this empty and put id on TGLLE

 

if you wanna be sure other kexts won't load you can use 0x12348086 - but empty values are fine

 

you only will get problems if trying to load AppleIntelFramebufferControllerICL (ventura patches)

 

AppleIntelFramebufferControllerICLLE and AppleIntelFramebufferControllerTGLLE should load fine

 

Gen7TGL will load if using boot arg -allow3d (do that if framebuffer loads and you see os x boot screen)

 

dam if we had this discussion on the other thread it would reach 50 pages

 

it's empty because at the moment if I put there 0xA7A08086 it won't boot...

the syslog I put inside master of nblue is not showing.. so the method is never be called... I was wondering why... my acpi folder is quite empty, I don't think is that the problem..

Edited October 23, 2024 by ASUS Vivobook

[jalavoui]

read my last post - i bet on xosi

 

some of my patches will apply to your ioreg (IMEI)

test with care

 

can you upload the dsdt.aml?

Edited October 23, 2024 by jalavoui

[Stezza88]

here ioreg

ioreg.ioreg

[Stezza88]

On 10/23/2024 at 11:01 PM, jalavoui said:

RestrictEvents.kext help. check SSDT-OSYS.aml and acpi and lilu

SSDT-OSYS.aml makes os x loads certain devices/config settings it is very important

if you can get 1 that is tested for your laptop - better otherwise try make 1 or use the one i send

 

your nblue is all empty lol

no wonder it does nothing

 

add your card id here

 

if you wanna test tgl then set this empty and put id on TGLLE

 

if you wanna be sure other kexts won't load you can use 0x12348086 - but empty values are fine

 

you only will get problems if trying to load AppleIntelFramebufferControllerICL (ventura patches)

 

AppleIntelFramebufferControllerICLLE and AppleIntelFramebufferControllerTGLLE should load fine

 

Gen7TGL will load if using boot arg -allow3d (do that if framebuffer loads and you see os x boot screen)

 

dam if we had this discussion on the other thread it would reach 50 pages

 

on my dsdt if i try to use this

i get 100 bugs in acpi

but for some people it works fine

 

can you upload your ioreg using IORegistryExplorer ? maybe it helps

 

1) You said 

Gen7TGL will load if using boot arg -allow3d (do that if framebuffer loads and you see os x boot screen)

but at me it stucks on os boot load.. so maybe i must load ICLLE or TGLLE in couple of this.. maybe i can try ICLLE or TGLLE with gen7TGL with graphicschedulerselect 0,1,3 or 5.. so i have some tests to do before surrender..

 

so it is the AppleIntelTGLsigned folder -> AppleintelTglGraohic.kext plus bundles, all in L/E plus permissions ?

 

2) I'm gonna put more SYSLOG like you said inside nootedblue code in various method... want to understand better where is the fault in my dev (at the moment I know that method processPatcher never be called... and it's bad I think)

 

 

 

Edited October 26, 2024 by ASUS Vivobook

[Stezza88]

I've putted two SYSLOG in the void NBlue::init() of kern_nblue.cpp method, one at the start of the method, one at the end.

 

They've not shown.

 

init method of nootedblue never be called

Edited October 24, 2024 by ASUS Vivobook

[Stezza88]

Now if I put -v in the nvram boot args it not do verbose... I don't understand... there is something blocking my usb-pen changes.. maybe I must rebuild cache? or something similar..

Edited October 24, 2024 by ASUS Vivobook