[Acer PT14-51 Laptop] HowTo

[jalavoui]

you can't add apple signed kexts to /L/E...

 

already explained here

 

https://www.insanelymac.com/forum/topic/360106-acer-pt14-51-laptop-howto/?do=findComment&comment=2826778

 

upload your dsdt.aml after os x boot - bet it is not working

 

boot with -v will help check for igpu hang

 

can you boot with this ?

 

your config as this disabled so no ota updates

i use this only when breaking os x seal

 

don't copy the .aml i send without checking if they work for you. for instance this

 

only works if you have a PC00 device. some systems have PCI0.

 

same for ssdt-osys

you must have a OSYS var in dsdt.aml and the value i use 

might not be the best for your system

 

AppleIntelTGLGraphics.kext + bundles are now in /S/L/E i removed old /L/E version

don't bother use them without having a working framebuffer 1st

Edited October 24, 2024 by jalavoui

[Stezza88]

.

Edited October 26, 2024 by ASUS Vivobook

[Stezza88]

.

Edited October 26, 2024 by ASUS Vivobook

[jalavoui]

 

do it after booting os x

 

when you get dsdt.aml check for errors using macial -press compile. if you get erros fix them by creating a new SSDT-xxx file

 

ok nvm security maybe your seal is broken

no problem

 

-v don't work ??? that is very strange

 

your system seems very bugged. it should work with default security and -v must show the console during boot

try fix it. maybe install ventura

 

think i got what's wrong

your settings of

my system wont work with devirtualisemmio. others works

 

might be wrong and cause all this. recheck them

 

also the kexts list order might cause a bug. try this order

and remove kexts you dont need to boot (for testing if it helps)

 

this is my smbios - idk which will work better for you

Edited October 24, 2024 by jalavoui

[Stezza88]

20 minutes ago, jalavoui said:

 

do it after booting os x

 

when you get dsdt.aml check for errors using macial -press compile. if you get erros fix them by creating a new SSDT-xxx file

 

ok nvm security maybe your seal is broken

no problem

 

-v don't work ??? that is very strange

 

your system seems very bugged. it should work with default security and -v must show the console during boot

try fix it. maybe install ventura

 

Then i did a 

 

PS C:\Users\stefa\Downloads\mac_av\iasl-win-20240927> .\iasl.exe .\DSDT.dsl

...

Compilation successful. 0 Errors, 180 Warnings, 530 Remarks, 270 Optimizations

Edited October 24, 2024 by ASUS Vivobook

[jalavoui]

omg u got dsdt.aml from windows ??

get it from mac os so we can check if the ssdt patches worked...

 

funny that when i start my laptop was like yours - total failure

it took some time to make it work

Edited October 24, 2024 by jalavoui

[Stezza88]

.

Edited October 26, 2024 by ASUS Vivobook

[Stezza88]

Macbook14,1 supports at max ventura.. i put Macbook16,2 i want sonoma

 

[SOLVED] -v boot args wasn't accepted because i had Misc -> Debug -> Target = 3 now i put it to 67 and it's working newly...

Edited October 24, 2024 by ASUS Vivobook

[Stezza88]

Look at this statements, there is something wrong :

I put everything in pendrive EFI -> OC -> Kexts (Hookcase, Apple*LE and nootedblue)

 

01:554 00:007 AAPL: #[EB.LD.LKC|R.1] <"System\Library\KernelCollections\BootKernelExtensions.kc">
02:886 01:332 OC: Prelinked injection AppleIntelTGLGraphicsFramebuffer.kext (AppleIntelTGLGraphicsFramebuffer.kext) - Invalid Parameter
02:928 00:042 OC: Prelinked injection AppleIntelICLLPGraphicsFramebuffer.kext (AppleIntelICLLPGraphicsFramebuffer.kext) - Invalid Parameter

 

A clean installation cannot be done like this way.. solutions?

(i've tryed also DmgLoading String Signed, SecureBootModel String Default = same result)

 

[EDIT] (Inverting the order like you suggested i've got bad report

00:830 00:009 AAPL: #[EB.LD.LKC|R.1] <"System\Library\KernelCollections\BootKernelExtensions.kc">
01:703 00:872 OC: Prelinked injection VirtualSMC.kext (VirtualSMC.kext) - Invalid Parameter
01:717 00:013 OC: Prelinked injection RestrictEvents.kext (RestrictEvents.kext) - Invalid Parameter
01:899 00:181 OC: Prelinked injection AppleIntelICLLPGraphicsFramebuffer.kext (AppleIntelICLLPGraphicsFramebuffer.kext) - Invalid Parameter
01:921 00:021 OC: Prelinked injection AppleIntelTGLGraphicsFramebuffer.kext (AppleIntelTGLGraphicsFramebuffer.kext) - Invalid Parameter
01:947 00:026 OC: Prelinked injection SMCBatteryManager.kext (SMCBatteryManager.kext) - Invalid Parameter
01:958 00:011 OC: Prelinked injection SMCLightSensor.kext (SMCLightSensor.kext) - Invalid Parameter
01:970 00:011 OC: Prelinked injection SMCProcessor.kext (SMCProcessor.kext) - Invalid Parameter
01:982 00:011 OC: Prelinked injection SMCSuperIO.kext (SMCSuperIO.kext) - Invalid Parameter

)

Edited October 26, 2024 by ASUS Vivobook

[Stezza88]

Or It Is an hack that must be done only after installation... Then i accomplish..

Edited October 24, 2024 by ASUS Vivobook

[jalavoui]

you can't load AppleIntelICLLPGraphicsFramebuffer.kext, hookcase or any other like it in opencore

 

on opencore only load nblue

 

put sle_internal/le kexts on /L/E

 

i've updated sle_internal to have 1 AppleIntelTGLGraphics.kext in /L/E for testing (need path change + info.plis in nblue source code)

 

the other AppleIntelTGLGraphics.kext is tobe installed in /S/L/E but must breal os x seal

 

at this stage focus on /L/E and only on framebuffer

Edited October 24, 2024 by jalavoui

[Stezza88]

.

Edited October 26, 2024 by ASUS Vivobook

[Stezza88]

Every testing syslog i try doesn't show .. this is a problem.. something is going wrong

 

I've looked in the kern_util.cpp and syslog is implemented as "lilu_os_log(...)" maybe I must insert -liludbg or -NBlueDebug to show them ... today I'll try..

 

[EDIT] -liludbg or -liludbg liludump=30 are not printing anything of anything to me... so sad

Edited October 25, 2024 by ASUS Vivobook

[Stezza88]

.

Edited November 2, 2024 by ASUS Vivobook

[Stezza88]

I got this on log

2024-10-26 18:41:47.252412+0200  localhost kernel[0]: (Sandbox) Sandbox: com.apple.quicklook.ThumbnailsAg(541) deny(1) file-read-xattr /Library/Extensions/AppleIntelICLLPGraphicsFramebuffer.kext
2024-10-26 18:41:47.252518+0200  localhost kernel[0]: (Sandbox) Sandbox: com.apple.quicklook.ThumbnailsAg(541) deny(1) file-read-xattr /Library/Extensions/AppleIntelTGLGraphicsFramebuffer.kext

P.S. with offline installer I've got more clean log files.. better than nothing..

Edited October 26, 2024 by ASUS Vivobook

[jalavoui]

if u wanna do a crazy test:

- do not load nblue

- goto /L/E and add your card id to info.plist of AppleIntelICLLPGraphicsFramebuffer.kext or tgl

- rebuild /L/E cache

- boot with -v (pray for no hang)

 

- it probably will give a kernel panic

- boot from recovery delete /Library/KernelCollections/AuxiliaryKernelExtensions.kc

- boot mac os

- remove the card id from the kext in /L/E so you can reboot mac os

- rebuild /L/E cache

- check logs and /Library/Logs/DiagnosticReports

 

as for wg

the gitthub release as no support for your card family - it will do nothing

you can try my other thread wg it as this code

just change for your card family

 

Edited October 26, 2024 by jalavoui

[Stezza88]

here the dsdt.aml and dsdt.dsl

DSDT.aml DSDT.dsl

[Stezza88]

12 hours ago, jalavoui said:

if u wanna do a crazy test:

- do not load nblue

- goto /L/E and add your card id to info.plist of AppleIntelICLLPGraphicsFramebuffer.kext or tgl

- rebuild /L/E cache

- boot with -v (pray for no hang)

 

- it probably will give a kernel panic

- boot from recovery delete /Library/KernelCollections/AuxiliaryKernelExtensions.kc

- boot mac os

- remove the card id from the kext in /L/E so you can reboot mac os

- rebuild /L/E cache

- check logs and /Library/Logs/DiagnosticReports

 

as for wg

the gitthub release as no support for your card family - it will do nothing

you can try my other thread wg it as this code

just change for your card family

 

 

The wg try already done.. I've changed all the parts like lshbluesky.. I'm suspicious that I'm  not signed like RaptorLake...

 

I've added this to kern_model.cpp

{ 0xA7A0, 0x8A5A, "Intel Iris Xe Graphics" },
	// Reserved/unused/generic Raptor Lake },

this to kern_igfx.cpp

else if (cpuGeneration == CPUInfo::CpuGeneration::TigerLake)
			success = applyPlatformInformationListPatch(framebufferId, static_cast<FramebufferICLLP *>(gPlatformInformationList));
		else if (cpuGeneration == CPUInfo::CpuGeneration::RaptorLake)
			success = applyPlatformInformationListPatch(framebufferId, static_cast<FramebufferICLLP *>(gPlatformInformationList));
		else if (cpuGeneration == CPUInfo::CpuGeneration::AlderLake)
			success = applyPlatformInformationListPatch(framebufferId, static_cast<FramebufferICLLP *>(gPlatformInformationList));

case CPUInfo::CpuGeneration::RaptorLake:
			supportsGuCFirmware = true;
			currentGraphics = &kextIntelICL;
			currentFramebuffer = &kextIntelICLLPFb;
			currentFramebufferOpt = &kextIntelICLHPFb;
			modDVMTCalcFix.available = true;
			modForceCompleteModeset.supported = modForceCompleteModeset.enabled = true;
			break;

Result : nothing happened except iGPU signed like "Intel Iris Xe Graphics" instead of "???" inside Hackintool.. now I wanna put some SYSLOG to see what is my CpuGeneration inside the kext code..

 

Edited October 27, 2024 by ASUS Vivobook

[Stezza88]

I read "make sure you're using either the DEBUG or NOOPT versions of OpenCore"

 

But i'm still using the RELEASE version... maybe is this the problem of why I can't see SYSLOG statements ??

Edited October 27, 2024 by ASUS Vivobook

[Stezza88]

11 minutes ago, ASUS Vivobook said:

I read "make sure you're using either the DEBUG or NOOPT versions of OpenCore"

 

But i'm still using the RELEASE version... maybe is this the problem of why I can't see SYSLOG statements ??

 

Doesn't change anything... -wegdbg doesn't show anything

[Stezza88]

I did also (like suggested here https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Radeon.en.md)

log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source

and nothing shows..

Edited October 27, 2024 by ASUS Vivobook

[Stezza88]

[EDIT] NVRAM now is working!!! I had wrong config.plist

Edited October 27, 2024 by ASUS Vivobook

[Stezza88]

I see logs!!!! but they are too fast in booting.. and cannot print them in system.log... don't understand WHY

Edited October 27, 2024 by ASUS Vivobook

[jalavoui]

yes forgot to mention that opencore config / OpenCore Configurator must match or you get config errors with opencore

 

did you fix the smbios ? if you copy my config you need to generate new serial number

 

try get logs using terminal command or hackintool

 

don't expect wg or nblue to magically work. your card is still not supported

 

 

 

 

Edited October 27, 2024 by jalavoui

[Stezza88]

1 hour ago, jalavoui said:

yes forgot to mention that opencore config / OpenCore Configurator must match or you get config errors with opencore

 

did you fix the smbios ? if you copy my config you need to generate new serial number

 

try get logs using terminal command or hackintool

 

don't expect wg or nblue to magically work. your card is still not supported

 

 

 

 

 

SMBIOS I use MacbookPro16,2 because it supports Sonoma... MacbookPro14,1 or 14,2 don't

 

I've got problems with logs... wanna modify the masters of wg and of nb.. but SYSLOG are shown too fast on boot, but not in system.log file inside the system..

 

Don't understand why...

Edited October 27, 2024 by ASUS Vivobook