jalavoui Posted Saturday at 02:17 PM Share Posted Saturday at 02:17 PM (edited) u miss the parameter (sys.kc or boot.kc) btw i use this to debug decompkernelcache. guess pass the parameter should work anyway to step debug comment fopen and choose sys or kc fopen don't hack my hack Edited Saturday at 02:45 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 02:51 PM Author Share Posted Saturday at 02:51 PM One question... but if i patch the AppleIntelICLGraphics driver.. how can i restore it in system/Library/Extensions the patched one? Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 03:05 PM Author Share Posted Saturday at 03:05 PM (edited) Got this situation in ghidra... so bad... 0x3ed .. variable __data i think.. Edited Saturday at 03:30 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Saturday at 04:10 PM Share Posted Saturday at 04:10 PM you dont patch the binary directly use wg or nblue todo it. did u make ghidra analyse the binary 1st? just testing for this if i try this in the ventura binary from decompkernelcachede ghidra failed to decompile the code and i get this this is bad luck but you can load on ida pro 1 Link to comment Share on other sites More sharing options...
jalavoui Posted Saturday at 04:19 PM Share Posted Saturday at 04:19 PM when you create the patch (new bytes) add to nblue or wg like this f2 are original bytes r2 is the patch (new hex bytes copyed from ghidra or ida pro) so you don't mess with the binary files. you just create patches to use on nblue or wg 1 Link to comment Share on other sites More sharing options...
jalavoui Posted Saturday at 04:26 PM Share Posted Saturday at 04:26 PM i you find code that you just can't decompile better (china code) like this (**(code **)(*in_RDI + 0x178))(); ask on the other thread - maybe visual helps you 1 Link to comment Share on other sites More sharing options...
benmacfreak Posted Saturday at 05:15 PM Share Posted Saturday at 05:15 PM i did test last night the config and acpi you did for me jala, it tries to boot (im using sonoma 14.7 from a usb) without nblue or weg fork it goes to a blank screen only. should i add reset nvram driver? Link to comment Share on other sites More sharing options...
jalavoui Posted Saturday at 05:20 PM Share Posted Saturday at 05:20 PM (edited) the config i did was based on my oc old 9.6 version. try to change it for the version you have this is my oc confg it's old just get OC + OC confgurator that can let you do proper configs if you read this thread you will see everyone does mistakes. so we talk about it here and try to find a solution asus for instance took 5 pages to figure out his nvram delete mistake so ben i think if you can fix the new config your system will work just fine Edited Saturday at 05:29 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
benmacfreak Posted Saturday at 05:22 PM Share Posted Saturday at 05:22 PM 1 minute ago, jalavoui said: the config i did was based on my oc old 9.6 version. try to change it for the version you have ok ill do that now. Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 06:33 PM Author Share Posted Saturday at 06:33 PM (edited) 1 hour ago, jalavoui said: you dont patch the binary directly use wg or nblue todo it. did u make ghidra analyse the binary 1st? just testing for this if i try this in the ventura binary from decompkernelcachede ghidra failed to decompile the code and i get this this is bad luck but you can load on ida pro Hope IDA 7.7 could do its dirty job too.. now i'm setupping some things.. Edited Saturday at 06:37 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Saturday at 07:30 PM Share Posted Saturday at 07:30 PM dont try in windows get ida pro for mac os it's free. better not use windows ever 2 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 08:14 PM Author Share Posted Saturday at 08:14 PM (edited) . Edited Sunday at 10:54 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 08:26 AM Author Share Posted Sunday at 08:26 AM (edited) I have found this... it was "com.apple.driver.AppleIntelICLGraphics : __ZN16IntelAccelerator10getGPUInfoEv + 0x3ed" And maybe i thought that 0x3ed is the offset inside this function.. Edited Sunday at 08:26 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 08:57 AM Author Share Posted Sunday at 08:57 AM (edited) In my code for example, i don't have this sequence of byte so the lshbluesky patch won't apply // Sku Bypass IntelAccelerator::getGPUInfo static const uint8_t f2[] = { 0x0F, 0x87, 0x17, 0x01, 0x00, 0x00, 0x48, 0x8D, 0x0D, 0x96, 0x02, 0x00, 0x00 }; when i find, it's empty the search Edited Sunday at 08:58 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 09:54 AM Author Share Posted Sunday at 09:54 AM (edited) I did my patch, and it worked!! I've followed lshbluesky methodology (pointing to a safe location) in the other post to do it.. // Sku Bypass IntelAccelerator::getGPUInfo static const uint8_t f2[] = { 0xE8, 0x38, 0x0C, 0x06, 0x00, 0xE9, 0x2D, 0x01, 0x00, 0x00 }; static const uint8_t r2[] = { 0xC7, 0x83, 0x98, 0x11, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00 }; Noi i have got a new kp... "Graphics Firmware Load failed boot hash check!\" Kernel-2024-11-03-115328.panic But this has no instructions associated... it could be a problem.. Edited Sunday at 11:13 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 11:26 AM Author Share Posted Sunday at 11:26 AM (edited) With -disablegfxfirmware boot arg kp disappeared but It loops on "busy timeout iGPU" Edited Sunday at 12:22 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Sunday at 12:56 PM Share Posted Sunday at 12:56 PM (edited) that's interesting you're using scheduler for apple firmware and icl is trying to load it. kinda like linux are you using wg from other thread? i hacked it long ago to load tgl guc but it sure miss lots of work cause this wg patches are for old os x version. try scheduler 4 also it's non apple firmware. 5 is nblue tgl default it's interesting your card is trying todo same as linux (firmware loading) did you try with AppleIntelTGLGraphics also ? igpu hang also happens on wg for framebuffer only? fix this first you can also try to load icl or AppleIntelTGLGraphics without the framebuffer driver for testing (will produce some logs) hope you can make nblue to work - much easier way to patch kexts this is the correct. the offset of panic is always printed in kp msg - i think i posted something about this with a calculator print make sure you check for the bytes in the binary for repeating. if f2 repeats in binary on some other function the patch will probably fail sometimes is better to use bigger pattern to avoid that Edited Sunday at 01:56 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 01:02 PM Author Share Posted Sunday at 01:02 PM (edited) 1 hour ago, jalavoui said: that's interesting you're using scheduler for apple firmware and icl is trying to load it. kinda like linux are you using wg from other thread? i hacked it long ago to load tgl guc but it sure miss lots of work cause this wg patches are for old os x version. try scheduler 4 also it's non apple firmware. 5 is nblue tgl default it's interesting your card is trying todo same as linux (firmware loading) did you try with AppleIntelTGLGraphics also ? igpu hang also happens on wg for framebuffer only? fix this first you can also try to load icl or AppleIntelTGLGraphics without the framebuffer driver for testing (will produce some logs) hope you can make nblue to work - much easier way to patch kexts [WEG] I've forked the forked weg source code to work for Raptor Lake too.. kern_igfx.cpp kern_model.cpp Edited Sunday at 02:30 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 01:52 PM Author Share Posted Sunday at 01:52 PM (edited) 1 hour ago, jalavoui said: that's interesting you're using scheduler for apple firmware and icl is trying to load it. kinda like linux are you using wg from other thread? i hacked it long ago to load tgl guc but it sure miss lots of work cause this wg patches are for old os x version. try scheduler 4 also it's non apple firmware. 5 is nblue tgl default it's interesting your card is trying todo same as linux (firmware loading) did you try with AppleIntelTGLGraphics also ? igpu hang also happens on wg for framebuffer only? fix this first you can also try to load icl or AppleIntelTGLGraphics without the framebuffer driver for testing (will produce some logs) hope you can make nblue to work - much easier way to patch kexts this is the correct. the offset of panic is always printed in kp msg - i think i posted something about this with a calculator print [NBlue] But the .bundle files must be loaded too? In folder GPUBundle? How can I copy the AppleIntelTGLGraphics into S L E ? [EDIT] With nblue (this is proof with com.apple.driver.AppleIntelICLLPGraphicsFramebuffer from S/L/E) is more complicated to me because i get no kp (= can't patch) .. i hang on this (same with *LE drivers) Edited Sunday at 02:30 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Sunday at 03:35 PM Share Posted Sunday at 03:35 PM (edited) you gotta break os x seal to install to /S/L/E. bad idea for now as you can't load any framebuffer you can try /sle/AppleIntelTGLGraphics.kext + bundles +hookcase into /L/E just for testing. patches are in nblue idk if putting bundles in /Library/GPUBundles would to anything put in /L/E 1st hope you can solve that igpu hang issue either with wg or nblue found a link error with nblue. gonna apply as nred - read other thread Edited Sunday at 03:52 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 04:46 PM Author Share Posted Sunday at 04:46 PM (edited) [WEG] Tryed scheduler 4 and 5 .. nothing changed... same hang.. here some logs dump .. Lilu_1.6.9_23.6.txt Edited Sunday at 06:32 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted 14 hours ago Author Share Posted 14 hours ago What i obtain if i do this boot arg? Could be important? Use the -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg and then File->Import->IOReg Dump menu Link to comment Share on other sites More sharing options...
jalavoui Posted 13 hours ago Share Posted 13 hours ago i think wg framebuffer settings dont work for icl but give it a try Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted 13 hours ago Author Share Posted 13 hours ago (edited) [NBlue] with ICLLE or TGLLE "Iokit daemon stall 'iGPU'" "Iokit daemon stall 'iGPU'" Edited 13 hours ago by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted 13 hours ago Author Share Posted 13 hours ago (edited) [NBlue] Using latest test NBLue kext setting only Gen7ICL IOPRimaryMatch 0xA7A08086, GraphicScheduler 4 : got an unsupported ICL SKU kp Kernel-2024-11-04-221337.panic Edited 13 hours ago by ASUS Vivobook Link to comment Share on other sites More sharing options...
Recommended Posts