jalavoui Posted Monday at 09:37 PM Share Posted Monday at 09:37 PM (edited) nice kp. check nblue::init it uses a specific card id. also patched on icl frame u might wanna change this values if trying to load icl graph kext for icl graph i use to test with this card id icl graph code as SYSLOG_COND. i bet the patched bytes won't match your os x version. change to panic_cond and test latest nblu bin src is updated- check it btw this functions is not working correctily. Gen11::getGPUInfo(void *that) check tgl graph patch for num slices,etc. and use same logic for icl graph kext you card values sould show up in linux logs Edited Monday at 09:50 PM by jalavoui Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Monday at 10:32 PM Author Share Posted Monday at 10:32 PM (edited) NootedBlue nblue: @ stolen_size 0x8000000 NootedBlue nblue: @ kextG11HW Failed to apply patches! NootedBlue NBlue: @ Failed to apply AGDP board-id patch Edited Monday at 10:32 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Monday at 10:47 PM Author Share Posted Monday at 10:47 PM (edited) I applied my icl sku bypass patch ant it worked!! Now I got new kp (GraphicsSchedulerSelect = 4) GUC Binary Load Failure Kernel-2024-11-04-234536.panic Edited Monday at 11:25 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Monday at 10:55 PM Author Share Posted Monday at 10:55 PM (edited) - with GraphicsSchedulerSelect = 5 no kp but stucks here - with GraphicsSchedulerSelect = 2 got kp unsupported scheduler select - with GraphicsSchedulerSelect = 0 it booted! but same problems.. but I got a faster pc! Always with no QE/CI No metal Edited Monday at 11:25 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Monday at 11:11 PM Share Posted Monday at 11:11 PM (edited) very interesting. what about scheduler 0 (apple) Failed to apply AGDP board-id patch gonna check this. no idea why it fails. it's a very old wg path also used on nred btw your nblue source is old. download from other thread (page 24). the one you have says "it's bad" they're together i wonder what icl graph is doing cause the ig-platform should be unsupported 0x9a49 is ment for tgl graph kext i got what you did. you load the graph kext without the framebufer. its is possible but only to get some logs. u will need to have the framebuffer loaded. or it might just do work for something Edited Monday at 11:45 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Monday at 11:30 PM Author Share Posted Monday at 11:30 PM (edited) Same result with newer version.. btw I've got always IONDRVSupport.kext.zipas loaded framebuffer and always NootedBlue nblue: @ stolen_size 0x8000000 NootedBlue nblue: @ kextG11HW Failed to apply patches! NootedBlue NBlue: @ Failed to apply AGDP board-id patch btw it boots............... Edited Monday at 11:56 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 12:28 AM Share Posted Tuesday at 12:28 AM (edited) that code is disabled in nblue latest this is to load signed tgl - only possible from /S/L/E but you can test on /L/E just install tgl graph from /sle_Internal/le and change the path in nblue to test in /S/L/E only by breaking os x seal. if u never did it you will probably break os x (read other thread) Edited Tuesday at 12:31 AM by jalavoui Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 12:32 AM Author Share Posted Tuesday at 12:32 AM (edited) Got these kps when I copy files into L E with nb in boot ... I'm gonna reusing weg to do it... with weg no problems... nblue : genx Failed to resolve symbols nblue : genx Failed to route symbols Kernel-2024-11-05-012957.panic Kernel-2024-11-05-013711.panic Edited Tuesday at 12:40 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 12:56 AM Share Posted Tuesday at 12:56 AM (edited) you can't copy kexts from /sle_Internal/sle to /L/E cause they are signed. copying bundles might be ok in /L/E use kexts from /sle_Internal/le that's why u got a kp but yeah wg is also ok for test new patches make sure you have kextacache of /L/E working Edited Tuesday at 12:58 AM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 01:00 AM Author Share Posted Tuesday at 01:00 AM (edited) It boots always on gen7icl and It's empty the IOPrimaryMatch inside NootedBlue nblue: @ kextG11HW Failed to apply patches! NootedBlue nblue: @ Loaded AppleIntelICLGraphics! but I've choosen TGL... can't understand why Tryed to clean nvram too and nothing changes.. Edited Tuesday at 01:33 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 01:46 AM Share Posted Tuesday at 01:46 AM (edited) that's strange if icl id is empty (try use fake id just in case put 0x12348086 instead of empty to disable) i think nblue will hang on icl framebuffer b4 loading icl graph kext but... nblue patches failed as the log says. disable what you dont need. check here (enable panic_Cond maybe) if 1 patch fails you get that msg no matter if others are correct. maybe replace f2 with your patch and disable others? LookupPatchPlus const patchesc[] = { are for mac os catalina - ignore them Edited Tuesday at 01:55 AM by jalavoui Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 02:05 AM Author Share Posted Tuesday at 02:05 AM (edited) 19 minutes ago, jalavoui said: that's strange if icl id is empty (try use fake id just in case put 0x12348086 instead of empty to disable) i think nblue will hang on icl framebuffer b4 loading icl graph kext but... nblue patches failed as the log says. disable what you dont need. check here (enable panic_Cond maybe) if 1 patch fails you get that msg no matter if others are correct. maybe replace f2 with your patch and disable others? LookupPatchPlus const patchesc[] = { are for mac os catalina - ignore them I put 0x12348086 on Gen7icl and my id in gen7tgl and It comes loaded Always gen7icl ... It's indestructible Edited Tuesday at 02:06 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 02:11 AM Share Posted Tuesday at 02:11 AM (edited) can you upload the nblue src that you are using. maybe u modify something wrong. or you can try to delete Gen7ICL from the info.plist if that helps oh w8 did you modify the kexts info.plist inside /L/E - check that first Edited Tuesday at 02:15 AM by jalavoui Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 02:13 AM Author Share Posted Tuesday at 02:13 AM (edited) kern_gen11.cpp kern_nblue.cp Nblue in use NootedBlue.kext.zip L/E plist of AppleIntelTGLGraphics Info.plist Edited Tuesday at 02:22 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 02:21 AM Share Posted Tuesday at 02:21 AM (edited) hmmm. does kextload -v 6 gives errors for tgl graph loading? nvm i found the bug change this to nblue default if you need to use icl id just remove // and comment 0x9a49 icl id is 0x8a5c tgl id is 0x9a49 but carefull cause this changes device-id and also ig-platformid this is funny u tell os x that your card id is 0x8a5c and ig-platform is 0x9a4a i think os x went crazy Edited Tuesday at 02:30 AM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 02:24 AM Author Share Posted Tuesday at 02:24 AM (edited) 5 minutes ago, jalavoui said: hmmm. does kextload -v 6 gives errors for tgl graph loading? No but i delete and reload as a try now.. Got a kp when delete It... Edited Tuesday at 02:26 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 02:36 AM Share Posted Tuesday at 02:36 AM (edited) kp are your friend dont complain if you get a kp log. fix the wrong ids in nblue. let me explain better use this if testing icl kexts use this if testing tgl kexts or idk you can comment all the code (+2 lines for properties inject) and do this with opencore properties the icl indestructible was funny ! Edited Tuesday at 02:40 AM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 02:36 AM Author Share Posted Tuesday at 02:36 AM (edited) 9 hours ago, jalavoui said: hmmm. does kextload -v 6 gives errors for tgl graph loading? nvm i found the bug change this to nblue default if you need to use icl id just remove // and comment 0x9a49 icl id is 0x8a5c tgl id is 0x9a49 but carefull cause this changes device-id and also ig-platformid this is funny u tell os x that your card id is 0x8a5c and ig-platform is 0x9a4a i think os x went crazy Nothing fuc*** changes! Always load Gen7icl.. Edited Tuesday at 12:18 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 02:46 AM Share Posted Tuesday at 02:46 AM oh yes i forgot if you use tgl from sle_Internal/lep that is production version. then u need to use the patches with "p" in nblue and disable the others. but you problem with icl graph is strange. only possible with wrong device-id or ig-platform 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 11:06 AM Author Share Posted Tuesday at 11:06 AM (edited) bool Gen11::processKext (..) { SYSLOG("SYSLOG", "index %lu", index); SYSLOG("SYSLOG", "kextG11FB.loadIndex : %lu", kextG11FB.loadIndex); SYSLOG("SYSLOG", "kextG11HW.loadIndex : %lu", kextG11HW.loadIndex); SYSLOG("SYSLOG", "kextG11HWT.loadIndex %lu", kextG11HWT.loadIndex); SYSLOG("SYSLOG", "kextG11FBT.loadIndex : %lu", kextG11FBT.loadIndex); ... } Wanna check this piece of code.. [EDIT] Got this : ( now it hits good! TGL seems loaded ... were my logs that weren't updated, sorry for the inconventient ) However, method Gen11::processKext came called multiple times... it is correct? ... NootedBlue SYSLOG: @ index 1 NootedBlue SYSLOG: @ kextG11FB.loadIndex : 4 NootedBlue SYSLOG: @ kextG11HW.loadIndex : 5 NootedBlue SYSLOG: @ kextG11HWT.loadIndex 7 NootedBlue SYSLOG: @ kextG11FBT.loadIndex : 6 ... NootedBlue SYSLOG: @ index 8 NootedBlue SYSLOG: @ kextG11FB.loadIndex : 4 NootedBlue SYSLOG: @ kextG11HW.loadIndex : 5 NootedBlue SYSLOG: @ kextG11HWT.loadIndex 7 NootedBlue SYSLOG: @ kextG11FBT.loadIndex : 6 ... NootedBlue SYSLOG: @ index 9 NootedBlue SYSLOG: @ kextG11FB.loadIndex : 4 NootedBlue SYSLOG: @ kextG11HW.loadIndex : 5 NootedBlue SYSLOG: @ kextG11HWT.loadIndex 7 NootedBlue SYSLOG: @ kextG11FBT.loadIndex : 6 ... NootedBlue SYSLOG: @ index 10 NootedBlue SYSLOG: @ kextG11FB.loadIndex : 4 NootedBlue SYSLOG: @ kextG11HW.loadIndex : 5 NootedBlue SYSLOG: @ kextG11HWT.loadIndex 7 NootedBlue SYSLOG: @ kextG11FBT.loadIndex : 6 ... NootedBlue SYSLOG: @ index 7 NootedBlue SYSLOG: @ kextG11FB.loadIndex : 4 NootedBlue SYSLOG: @ kextG11HW.loadIndex : 5 NootedBlue SYSLOG: @ kextG11HWT.loadIndex 7 NootedBlue SYSLOG: @ kextG11FBT.loadIndex : 6 ... Lilu_1.6.9_23.6.txt Edited Tuesday at 04:03 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 01:00 PM Author Share Posted Tuesday at 01:00 PM (edited) - With loaded (gen7TGL) com.xxxxx.driver.AppleIntelTGLGraphics", graphicsschedulerselect = 0 -> framebuffer not loaded -> always 15 mb vrAM -> still no acceleration -> can't see [IGPU] logs in boot Edited Tuesday at 01:23 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 04:31 PM Author Share Posted Tuesday at 04:31 PM (edited) [WEG] I'm understanding now that "-disablegfxfirmware" boot arg disable the possible scheduler selection so i cannot change scheduler.. but if i toggle this boot arg i obtain the consequent scheme : ------------ Resume ------------ Without boot arg -disablegfxfirmware - boot arg igfxfw=2, kp "Firmware Load failed boot hash check!" - boot arg igfxfw=1, kp "guc binary load failure" - boot arg igfxfw=0 / igfxfw=-1, gpu stall --------------------------------- With -disablegfxfirmware - gpu stall and no scheduler selection --------------------------------- In weg src code we've got these cases, so i think i tryed everything.. with bad results.. I don't know what to choose as "the best of" XD /** * GuC firmware loading scheme */ enum FirmwareLoad { FW_AUTO = -1 /* Use as is for Apple, disable for others */, FW_DISABLE = 0, /* Use host scheduler without GuC */ FW_GENERIC = 1, /* Use reference scheduler with GuC */ FW_APPLE = 2, /* Use Apple GuC scheduler */ }; Edited Tuesday at 05:23 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 05:09 PM Share Posted Tuesday at 05:09 PM (edited) yes since in linux your drivers loads firmware don't use -disablegfxfirmware. unless you wanna test scheduler 5 did you check wg firmware patches? they are for very old os x version btw this didint panic. so the patch worked Edited Tuesday at 05:33 PM by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Tuesday at 05:25 PM Author Share Posted Tuesday at 05:25 PM (edited) Want to try to config better like linux configs the numofslices, etc in method getgpuinfo of weg.. maybe i can avoid the icl sku patching... but in weg i'm in doubt.. what is the best way i found second you? Just look above.. Edited Tuesday at 05:26 PM by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted Tuesday at 05:34 PM Share Posted Tuesday at 05:34 PM the icl sku check depends on ig-platform. i think you need to patch it. focus on framebuffer as graph kext only matter if framebuffer kexts loads 1 Link to comment Share on other sites More sharing options...
Recommended Posts