Jump to content

[Acer PT14-51 Laptop] HowTo

ASUS Vivobook

By ASUS Vivobook,
in Intel

 Share
170 posts in this topic

Recommended Posts

ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)

I've paired my confs like the confs you indicated me, except only these two params

 

-----------------------------

Kernel -> quirks

ProvideCurrentCpuInfo - true (if false my system doesn't boot)

------------------------------

Miax -> security

Securebootmodel - Disabled (if Default my system doesn't boot)

------------------------------

 

Now i can install with native NVRAM [Canceled OpenVariableRuntimeDxe.efi (which emulated NVRAM) from drivers]

Finally hope can have panic reports!!!

 

[EDIT] I got newly car-active-config set to unknown and I can't modify it.. wtf

Edited by ASUS Vivobook
Link to comment
Share on other sites
benmacfreak
benmacfreak
Posted
Posted
On 10/27/2024 at 3:24 PM, jalavoui said:

always from yours. you can then check some things from what we post here

ok so i got progress (somewhat) no audio, no trackpad, or acceleration. I checked my DSDT voodooi2c is loaded but idk what my device name is or how to find it. I tried the tigerlake 43e8 geni2c app says it's not in my DSDT, so i dont know what to do. I know my audio is realtek alc256 according to windows device manager, and my igpu is 9a68 8086 beyond that im dumbfound jala, sorry.

Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

so many questions. but this is the right place to help you. start by uploading oc config and ioreg so we can check what is loading on your system

 

asus i think you miss delete some vars here. (check my config or the 1 i send to ben)

 

image.png.d4341ae0439de3376b56569c294c095e.png

Edited by jalavoui
  • Like 1
Link to comment
Share on other sites
benmacfreak
benmacfreak
Posted
Posted (edited)
56 minutes ago, jalavoui said:

so many questions. but this is the right place to help you. start by uploading oc config and ioreg so we can check what is loading on your system

ok here's my oc config plist and my IOreg file 

config.plist bennji’s MacBook Pro.ioreg and a link to my full EFI https://download1503.mediafire.com/fxjvfhg84xkg_Ln6dftTS904XILAm6qG3JW34MYT4FMOs1e_d6QUASeBtLYw3JKr3wmzxzG0n0VcZwye3-wqAAo5iaNIvcLR2ogPTH0z0VLwed5lLHJSD91HEWeUSiO4OXyMmzBBpTWEH8oLNDtXE06crg0dEAvqH48Ov5X_ZaHAgw/xtbn5d2o4xvk1ox/EFI-OC-Ben-ASUS-TGL.zip

Edited by benmacfreak
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

nice you can boot. get macial and attach dsdt.aml

 

you just need small fixs and soon can try igpu

 

hope you can read this thread and do the fixing youself.

 

you and asus and kinda on same hardware

 

try start with this config based on yours. check you have the match OpenCore Configurator for your opencore version or you will get oc errors at boot.

i'm using this old version but you can try with a more recent OC. just open this config and save using your OpenCore Configurator

 

image.png.16a3b6cd77471f954513e7f820b640b6.png

 

- test this on a usb pen

- open this config use OpenCore Configurator and save it. check for errors or it won't boot

- check if this devices path are correct

- add the .aml files to oc/acpi folder

- if you get a boot screen try old nbue or wahtevergreen releases from other thread (for wg add back some properties for igpu)

- if all good get xcode and try new nblue

 

Arquivo.zip

 

Edited by jalavoui
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)

in oc verbose i got this strange message.. this is the cause why my nvram doesn't give me a sip disabled 

00:398 00:011 OCVAR: Setting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config - ignored, exists

can't reset because sip is in unknown state... and if I modify car-active-config it doesn't came modified because of this verb.

 

Not showing anything .. can't see picker selection menu either in dos way or Syrah.. but it boots fortunately directly in macOS APFS partition 

05:820 00:009 OCB: Adding custom entry CleanNvram.efi (tool|B:0) -> CleanNvram.efi
05:828 00:008 OCB: Registering entry CleanNvram.efi [Auto] (T:128|F:0|G:0|E:0|B:0) - <nil>
05:837 00:009 OCB: Adding custom entry OpenShell.efi (tool|B:0) -> OpenShell.efi
05:846 00:008 OCB: Registering entry OpenShell.efi [OpenShell:UEFIShell:Shell] (T:128|F:0|G:0|E:0|B:0) - <nil>
05:855 00:009 BEP: Reset NVRAM entry, preserve boot 0, apple 0
05:865 00:009 OCB: Adding custom entry Reset NVRAM (action|B:1) -> <null string>
05:875 00:009 OCB: Registering entry Reset NVRAM [ResetNVRAM:NVRAMTool] (T:256|F:0|G:0|E:0|B:1) - <nil>
05:883 00:008 OCB: Showing menu... 
05:892 00:009 OCHK: InitHotKeys
05:901 00:008 OCKM: Allocated key repeat context 274A6218 274A6298 2748AE18
05:910 00:009 OCAE: Set screen resolution to 2560x1600 - Success
05:919 00:008 OCTY: Registered handler
05:928 00:009 OCAE: Set screen resolution to 2560x1600 - Success
05:937 00:008 OCUI: Console attributes: 0
05:946 00:009 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
05:956 00:009 OCB: Get volume icon for Windows <null string> - Not Found
05:966 00:010 OCUI: Using flavour icon, custom: 0
05:975 00:008 OCUI: Console attributes: 0
05:984 00:009 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
05:993 00:008 OCB: Get volume icon for MacOSX D6F62EB5-0852-4CD3-A22B-DC9D3DCA8C73\ - Not Found
06:002 00:009 OCUI: Using flavour icon, custom: 0
06:011 00:008 OCUI: Console attributes: 0
06:020 00:009 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
06:029 00:008 OCB: Get volume icon for Recovery 14.7.1 D6F62EB5-0852-4CD3-A22B-DC9D3DCA8C73\ - Not Found
06:038 00:009 OCUI: Using flavour icon, custom: 0
06:046 00:008 OCUI: Console attributes: 0
06:056 00:009 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
06:066 00:009 OCUI: Console attributes: 0
06:075 00:009 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
06:084 00:008 OCUI: Using flavour icon, custom: 0
06:093 00:009 OCUI: Console attributes: 0
06:102 00:008 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
06:111 00:009 OCUI: Using flavour icon, custom: 0
11:137 05:025 OCHK: FreeHotKeys
11:148 00:011 OCTY: Unregistered handler
11:159 00:010 OCKM: Freeing key repeat context 274A6218 274A6298 2748AE18
11:167 00:008 OCB: Should boot from 2. MacOSX (T:2|F:0|G:0|E:0|DEF:0)
11:177 00:009 OCB: Saved mode 0/0/0 - Success
11:185 00:008 OCB: Perform boot MacOSX

 

opencore-2024-11-01-233752.txt

Edited by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

you need to delete the vars you create in nvram

this is your config - check agains mine

fix it and do clear nvram with console tool

 

image.png.ffb4e68f762fed1684c182121b8298af.png

 

csr unknow msg is fine for 0xFFFFFFFF

 

do you have opencore configurator for this OpenCore DBG-102-2024-10-08  ?? otherwise you can get config errors

 

idk if you really need lilucpu=17 slide=0

 

idk if you need this resetnvram as driver. maybe use console tool?image.png.5832eab07bbf3a0b0073500a6f197c5e.png

 

no SSDT-OSYS.aml enabled OMFG!! review all i think you miss others

 

this is invalid - check my config

image.png.ed7f2886e171f5f38db0a63894f2d2ec.png

Edited by jalavoui
  • Like 1
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)
2 hours ago, jalavoui said:

you need to delete the vars you create in nvram

this is your config - check agains mine

fix it and do clear nvram with console tool

 

image.png.ffb4e68f762fed1684c182121b8298af.png

 

csr unknow msg is fine for 0xFFFFFFFF

 

do you have opencore configurator for this OpenCore DBG-102-2024-10-08  ?? otherwise you can get config errors

 

idk if you really need lilucpu=17 slide=0

 

Can't have access to console tool because oc picker is not showing... and I can't undestand why... I think I must insert acpi disable gpu.aml 

 

P.S. I need lilucpu=17 because it sets my cpu gen to raptor lake gen... I see in weg source code that 17 represent my gen.. because exploring weg in detail I saw that my cpu is set to gen 0 or unknown and modified forked weg doesn't work

Edited by ASUS Vivobook
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)

Just added this to NVRAM settings 

Delete
	7C436110-AB2A-4BBB-A880-FE41995C9F82
		csr-active-config

and it worked!! Now I've got SIP disabled... finally!!

 

P.S. with secure bootmodel set to default my system won't boot

 

Now, I can go to the night club happy

Edited by ASUS Vivobook
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)

Got it !!! It is strange how can someone be happy to have a kernel panic! XD

Kernel-2024-11-02-095354.panic

 

I think i've found the exact point : in 0x3ed (i think line 1005 of com.apple.driver.AppleIntelICLGraphics binary) and after in 0x51 (i think line 81 of WhateverGreen binary) 

0xffffff7f94e37e8b com.apple.driver.AppleIntelICLGraphics : __ZN16IntelAccelerator10getGPUInfoEv + 0x3ed
0xfffffff4130a3b20 : 0xffffff800586d4c1 as.vit9696.WhateverGreen : __ZN4IGFX10getGPUInfoEPv + 0x51
0xfffffff4130a3b80 : 0xffffff7f94e37a71 com.apple.driver.AppleIntelICLGraphics : __ZN16IntelAccelerator15configureDeviceEP11IOPCIDevice + 0x31
0xfffffff4130a3ba0 : 0xffffff7f954e4e3d com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x2d5

And voilà.. it is the commit that lshBluesky did to bypass ICL SKU kp which generates a kp to me (https://github.com/lshbluesky/WhateverGreen/commit/54257ca01f9475c163e1693a981b7968474d8d09) 

KernelPatcher::RouteRequest request("__ZN16IntelAccelerator10getGPUInfoEv", getGPUInfo, ogetGPUInfo);
		patcher.routeMultiple(index, &request, 1, address, size);

 

Him talking about it at page 6 :

 

Edited by ASUS Vivobook
  • Haha 1
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)

Just a try : by commenting these two lines in wet source code 

KernelPatcher::RouteRequest request("__ZN16IntelAccelerator10getGPUInfoEv", getGPUInfo, ogetGPUInfo);
		patcher.routeMultiple(index, &request, 1, address, size);

and adding -igfxdvmt to boot args result is the same, kp always 0x3ed problem  

0xffffff7f94e37e8b com.apple.driver.AppleIntelICLGraphics : __ZN16IntelAccelerator10getGPUInfoEv + 0x3ed

Kernel-2024-11-02-121950.panic

Edited by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

nice. give me a sec

 

i've added gen7icl back to nblue info.plist (was disabled cause i went focus on tgl)

 

image.png.d3c1d24cd39942b868292005f851bbc9.png

 

the iclgraph patches start here

 

image.png.1384d0e08f37006cc035826e9abc7865.png

 

mostly ventura patches. note that the patches have a syslog_cond. so if they fail to apply you won't be noticed

better change to panic_cond after changing them. why? cause if the patch fails to apply you get a nice kp warn msg

 

image.png.70edc835574e294b2e615f8f250093ab.png

 

as for kext extract go check decompkernelcache on

 

or load /System/Library/KernelCollections/SystemKernelExtensions.kc on ida pro (takes long time)

 

you can copy nblue patches to wg if you want

 

let's say this patch is for ventura

image.png.d220fa89f945dc90e727d61118f8c93b.png

 

if you're on sonoma just check the function Intelaccelerator::init and try guess the bytes offset

 

Edited by jalavoui
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
  • Author
Posted (edited)

$ sudo ./decompkernelcache /System/Library/Extensions/AppleIntelICLGraphics.kext -kexts

 

ERROR: Read too few bytes from file /System/Library/Extensions/AppleIntelICLGraphics.kext, 96 bytes wanted but 0 bytes read!

Edited by ASUS Vivobook
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

u miss the destination folder. note the "x" its a folder that will be created

 

usage:

./decompkernelcache /System/Library/KernelCollections/SystemKernelExtensions.kc x -kexts

 

i think you dont need sudo cause then you get root permissions on files error

 

if this doesnt work for the os x version you have u might need to check with xcode decompkernelcache src code.

 

btw now that you finally have a working system do you wanna publish it so others can copy your configs, etc?

oh w8 better when you have working trackpad,etc then publish it

 

this are from ventura. i just used the tool to extract. you can check then for nblue patched bytes

dam this are latest ventura and i'm using an old ventura release. i'mi not sure if nblue bytes will match

Arquivo.zip

a good idea is install

 image.png.70e8eddc40ffe011c6ec5e94cb75bc38.png

kdk depends on os x version and sometimes as usefull kexts inside. but care cause those kexts dont have the same bytes as the ones from /S/L/E

theyre good to read the code cause all offsets are fixed and they load fine on ghidra,etc

 

i think youi should focus on framebuffer 1st cause linux shows you have a display family 13 and also an edp connector

Edited by jalavoui
  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...