ASUS Vivobook Posted Wednesday at 09:15 PM Author Share Posted Wednesday at 09:15 PM (edited) 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 Wednesday at 09:19 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Wednesday at 09:21 PM Share Posted Wednesday at 09:21 PM (edited) 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 Wednesday at 09:52 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Wednesday at 09:28 PM Author Share Posted Wednesday at 09:28 PM here ioreg ioreg.ioreg Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 12:17 PM Author Share Posted Thursday at 12:17 PM (edited) 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 Saturday at 08:15 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 04:14 PM Author Share Posted Thursday at 04:14 PM (edited) 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 Thursday at 04:22 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 04:38 PM Author Share Posted Thursday at 04:38 PM (edited) 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 Thursday at 04:40 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Thursday at 05:12 PM Share Posted Thursday at 05:12 PM (edited) 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 Thursday at 05:35 PM by jalavoui Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 05:27 PM Author Share Posted Thursday at 05:27 PM (edited) . Edited Saturday at 08:14 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 05:36 PM Author Share Posted Thursday at 05:36 PM (edited) . Edited Saturday at 03:08 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Thursday at 05:37 PM Share Posted Thursday at 05:37 PM (edited) 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 Thursday at 05:59 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 05:52 PM Author Share Posted Thursday at 05:52 PM (edited) 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 Thursday at 05:58 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Thursday at 05:59 PM Share Posted Thursday at 05:59 PM (edited) 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 Thursday at 06:49 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 06:53 PM Author Share Posted Thursday at 06:53 PM (edited) . Edited Saturday at 03:08 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 08:20 PM Author Share Posted Thursday at 08:20 PM (edited) 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 Thursday at 10:08 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 09:32 PM Author Share Posted Thursday at 09:32 PM (edited) 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 Saturday at 08:08 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 10:09 PM Author Share Posted Thursday at 10:09 PM (edited) Or It Is an hack that must be done only after installation... Then i accomplish.. Edited Thursday at 11:11 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Thursday at 11:50 PM Share Posted Thursday at 11:50 PM (edited) 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 Thursday at 11:58 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Friday at 02:43 AM Author Share Posted Friday at 02:43 AM (edited) . Edited Saturday at 03:07 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Friday at 03:25 AM Author Share Posted Friday at 03:25 AM (edited) 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 Friday at 11:26 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Friday at 07:56 PM Author Share Posted Friday at 07:56 PM (edited) Done a big work.. now i paired my config.plist s like yours... except these i must put so (tryed and retryed to toggle but no way) ----------------------------- Booter -> quirks DevirtualiseMmio - true SetupVirtualMap - true ----------------------------- Kernel -> quirks ProvideCurrentCpuInfo - true (if false my system reboot during os loading) ------------------------------ Miax -> security Securebootmodel - Disabled (if Default my system reboot during os loading) ------------------------------ [EDIT] I resolved some problems... installation didn't boot... now it boots.. i can finally do a clean install.. trying the sonoma offline installation taken via mac.. before i was using the online installer taken via windows.. maybe something changes.. confignb.plist configwg.plist Edited Saturday at 04:48 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 05:24 PM Author Share Posted Saturday at 05:24 PM (edited) 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 Saturday at 08:55 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Saturday at 06:38 PM Share Posted Saturday at 06:38 PM (edited) 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 Saturday at 06:42 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 08:06 PM Author Share Posted Saturday at 08:06 PM here the dsdt.aml and dsdt.dsl DSDT.aml DSDT.dsl Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 07:20 AM Author Share Posted Sunday at 07:20 AM (edited) 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 Sunday at 07:30 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 07:53 AM Author Share Posted Sunday at 07:53 AM (edited) 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 Sunday at 07:59 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
Recommended Posts