Jump to content

[Acer PT14-51 Laptop] HowTo

Stezza88

By Stezza88,
in Intel

 Share
408 posts in this topic

Recommended Posts

jalavoui
jalavoui
Posted
Posted (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

 

image.png.f4160a4ad2406d0f184a99dddf7eb1fa.png

 

for icl graph i use to test with this card id 

image.png.d5932374e7470cf1ecbf772de5d0e7fd.png

 

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 by jalavoui
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (edited) 
NootedBlue     nblue: @ stolen_size 0x8000000
NootedBlue     nblue: @ kextG11HW Failed to apply patches!
NootedBlue     NBlue: @ Failed to apply AGDP board-id patch
Edited by ASUS Vivobook
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (edited)

- with GraphicsSchedulerSelect = 5 no kp but stucks here

 

IMG_20241104_235432167.jpg

 

- 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

 

Screenshot 2024-11-05 alle 00.22.00.png

Edited by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (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

image.png.07fb8226d05b1474302d869f44aeb07e.png

 

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 by jalavoui
  • Like 1
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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 by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

that code is disabled in nblue latest

 

image.png.abf142c25dabc7b52e8db4113b66f13e.png

 

this is to load signed tgl - only possible from /S/L/E

image.png.095f57b280e7f0c45b5bbe43ac6ab2b2.png

 

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 by jalavoui
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (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 by jalavoui
  • Like 1
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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

 

Screenshot 2024-11-05 alle 02.18.03.png

 

Tryed to clean nvram too and nothing changes..

Edited by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (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?

 

image.thumb.png.0682df9fff4af0e4563caaa7f0fb1426.png

 

LookupPatchPlus const patchesc[] = { are for mac os catalina - ignore them

Edited by jalavoui
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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?

 

image.thumb.png.0682df9fff4af0e4563caaa7f0fb1426.png

 

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 by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (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 by jalavoui
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

hmmm.

 

does kextload -v 6 gives errors for tgl graph loading?

 

nvm i found the bug

 

change this 

image.png.1411677cce613b9778ff283230928ea9.png

 

to

nblue default

 

image.png.76e3dd279b5144b2a7c7c7e7978c77d0.png

 

 

if you need to use icl id just remove //   and comment 0x9a49 

image.png.a6a41f70ef68c81fbb1c62a05b0c189d.png

 

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 by jalavoui
  • Like 1
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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 by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (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

image.png.7136b5a81ade78b4926508b3443e03c3.png

 

use this if testing tgl kexts

image.png.d29857f18c180c2173dd2499f3148093.png

 

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 by jalavoui
  • Like 1
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (edited)
9 hours ago, jalavoui said:

hmmm.

 

does kextload -v 6 gives errors for tgl graph loading?

 

nvm i found the bug

 

change this 

image.png.1411677cce613b9778ff283230928ea9.png

 

to

nblue default

 

image.png.76e3dd279b5144b2a7c7c7e7978c77d0.png

 

 

if you need to use icl id just remove //   and comment 0x9a49 

image.png.a6a41f70ef68c81fbb1c62a05b0c189d.png

 

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 by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted

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

  • Like 1
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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 by ASUS Vivobook
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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

 

Screenshot 2024-11-05 alle 13.59.20.png

Edited by ASUS Vivobook
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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,

                       SCHEDULER 5 => gpu stall

                       SCHEDULER 4 => kp "guc binary load failure"

                       SCHEDULER 3 => kp "Firmware Load failed boot hash check!"

                       SCHEDULER 1 => kp "unsupported graphic scheduler select"

                       SCHEDULER 0 => kp "Firmware Load failed boot hash check!"

- 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 by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (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

 

image.png.fd0f3af8b132e6ba76e793e115e9ddea.png

Edited by jalavoui
  • Like 1
Link to comment
Share on other sites
Stezza88
Stezza88
Posted
  • Author
Posted (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 by ASUS Vivobook
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...