[Acer PT14-51 Laptop] HowTo

[ASUS Vivobook]

16 hours ago, jalavoui said:

very bad idea remove iondrv - it is needed by other kexts.

 

when your system is fine just install the kexts i said in /Library/Extensions

 

 

you only will get logs after correctly install nblue

 

don't mount the system rw - you only will break it.

 

i would start by installing only this 2 kexts +hookcase.kext in /L/E

and test for loading using kextload -v

then try load nblue in opencore

 

when all his is done check for log files and post them here

 

btw get a linux log file for your card so we can check how it works

 

 

Must the info.plist section IOPrimaryMatch in AppleIntel* be changed too?

Edited October 23 by ASUS Vivobook

[jalavoui]

just upload it. we need to check the log.

 

only add your card id to AppleIntelFramebufferControllerICLLE or AppleIntelFramebufferControllerTGLLE

at this stage you can only test one of these framebuffers

choose 1 and test

 

not in the kexts!

use nblue - it is ment todo that

Edited October 23 by jalavoui

[ASUS Vivobook]

here the linux syslog after a clean reboot .. only 4 mb

syslog.txt

Edited October 23 by ASUS Vivobook

[ASUS Vivobook]

AppleIntelFramebufferControllerICLLE

... Stucks in boot

 

Edited October 23 by ASUS Vivobook

[ASUS Vivobook]

1 hour ago, jalavoui said:

just upload it. we need to check the log.

 

only add your card id to AppleIntelFramebufferControllerICLLE or AppleIntelFramebufferControllerTGLLE

at this stage you can only test one of these framebuffers

choose 1 and test

 

not in the kexts!

use nblue - it is ment todo that

 

What it changes if i add IOPrimaryMatch in kexts info.plist also? There was 0x12345678 inside the two kexts *LE .. nothing i suppose

Edited October 23 by ASUS Vivobook

[jalavoui]

you can only add your card id to ONE framebuffer not to all

this will test AppleIntelFramebufferControllerICLLE

 

 

same thing for AppleIntelFramebufferControllerTGLLE but delete id from ICLLE first!

 

 

did you check if the kexts are loading using kextload -v /Library/Extensions/AppleIntelTGLGraphicsFramebuffer.kext ?

 

you must get some kind of log from mac os x

 

next job is figure out what's wrong by using xcode functions/patches inside nblue

 

good luck

 

you have a edp connector so this might work

 

check nblue code as it is might not be enabled like this by default

Edited October 23 by jalavoui

[ASUS Vivobook]

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 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 Wednesday at 05:45 PM by jalavoui

[ASUS Vivobook]

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 Wednesday at 05:49 PM 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 Wednesday at 05:56 PM by jalavoui

[ASUS Vivobook]

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

 

Edited Wednesday at 06:30 PM by ASUS Vivobook

[jalavoui]

don't post pictures. log in and check logs

we need logs not pictures

 

[ASUS Vivobook]

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

x.log

Edited Wednesday at 06:46 PM by ASUS Vivobook

[ASUS Vivobook]

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 Wednesday at 06:20 PM by ASUS Vivobook

[ASUS Vivobook]

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 Wednesday at 06:51 PM 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 Wednesday at 07:13 PM by jalavoui

[ASUS Vivobook]

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 Wednesday at 07:14 PM by ASUS Vivobook

[ASUS Vivobook]

I see that id Is differenti from what i inserted

 

Ah but is yours.. sorry

Edited Wednesday at 07:18 PM 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 Wednesday at 07:24 PM by jalavoui

[ASUS Vivobook]

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 Saturday at 08:16 PM 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 Wednesday at 08:58 PM by jalavoui

[ASUS Vivobook]

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 Wednesday at 08:43 PM by ASUS Vivobook

[ASUS Vivobook]

.

Edited yesterday at 05:10 AM 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 Wednesday at 09:19 PM by jalavoui

[ASUS Vivobook]

1 minute ago, jalavoui said:

RestrictEvents.kext help. check xosi and acpi

 

What is XOSI? What do you mean for check?