ASUS Vivobook Posted October 14 Share Posted October 14 (edited) Laptop's Motherboard : Acer Predator PT14-51 CPU : 14 Core Intel Core i7-13700H Integrated graphics : Intel Iris Xe Graphics (Raptor Lake gen) Dedicated GPU : NVIDIA GeForce RTX 4070 Laptop GPU Bios : Insyde UEFI V1.08 I've managed to go stuck at the loading screen... Attached my files.. opencore-2024-10-15-090113.txt EFI.rar Edited Friday at 10:37 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 (edited) Toggling all the ACPI patches the installation started..!!! ... but now is stucking at middle installation.. now i'll try to add one ACPI patch i removed per time.. Edited Friday at 10:37 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 (edited) Now it's stucking at middle installation.. Attached my EFI files... EFI_PT.rar The guide i follow : https://chriswayg.gitbook.io/opencore-visual-beginners-guide/advanced-topics/using-alder-lake Edited October 15 by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 I did it Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 (edited) Killer Wi-Fi 6E AX1675i is not working.. WTF Edited Saturday at 03:13 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
miliuco Posted October 15 Share Posted October 15 (edited) @ASUS Vivobook This card is not supported. See here supported models: https://openintelwireless.github.io/itlwm/Compat Please add a signature to your Account Details. EDIT: Nvidia not supported. iGPU is a work in progress. Edited October 15 by miliuco Ask for signature Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 49 minutes ago, miliuco said: @ASUS Vivobook This card is not supported. See here supported models: https://openintelwireless.github.io/itlwm/Compat Please add a signature to your Account Details. EDIT: Nvidia not supported. iGPU is a work in progress. At the moment iGpu seems working.. 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 (edited) 19 hours ago, miliuco said: @ASUS Vivobook This card is not supported. See here supported models: https://openintelwireless.github.io/itlwm/Compat Please add a signature to your Account Details. EDIT: Nvidia not supported. iGPU is a work in progress. I've resolved with an "hama" usb ethernet adapter (the package told compatible for win and mac both) Edited October 16 by ASUS Vivobook 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 15 Author Share Posted October 15 (edited) - installation sometimes boot and sometimes not.. - Touchpad is not working - Screen turned on and off isn't working during the installation - audio is not working Edited October 16 by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted October 16 Author Share Posted October 16 (edited) - It detects (to me) a generic iGPU card with 15 MB of ram.... here my final EFI working I have followed this guide : https://chriswayg.gitbook.io/opencore-visual-beginners-guide/advanced-topics/using-alder-lake Using this whatevergreen : https://github.com/lshbluesky/WhateverGreen/releases/tag/v1.6.7-d8 (with the latest release of WhateverGreen it gives me the same result) EFI.rar Edited Thursday at 09:34 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Thursday at 09:34 AM Author Share Posted Thursday at 09:34 AM (edited) With this kext instead of whateverergreen it works a little bit fine.. but only 15 mb of ram and no acceleration ... but detected as Intel Iris Xe Graphics that is true.. NootedBlue.kext.zip Edited 8 hours ago by ASUS Vivobook 1 Link to comment Share on other sites More sharing options...
miliuco Posted Thursday at 09:45 PM Share Posted Thursday at 09:45 PM @ASUS Vivobook Congratulations. Your iGPU is not working yet at 100%, but as far as I know this iGPU is not yet able to be completely installed on macOS. Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Friday at 09:21 AM Author Share Posted Friday at 09:21 AM (edited) Using Whatevergreen (instead of nootedblue) (latest version) putting only AAPL,ig-platform-id taken by the previous "nootedblue conf" it gives to me a iGPU : Generic iGPU 15MB PCIe : Intel Raptor Lake-P [Iris Xe Graphics] AAPL,ig-platform-id <02005C8A> device-id <A0A70000> and setting this too : <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data>AAAF/w==</data> <key>acpi-path</key> <string>IOACPIPlane:/_SB/PC00/GFX0@20000</string> <key>AAPL,GfxYTile</key> <data>AQAAAA==</data> <key>AAPL,slot-name</key> <string>Internal@0,2,0</string> <key>AAPL00,override-no-connect</key> <data>AP///////wAw5HycAAAAAAAfAQSVIhNgA2+xp1VMniUMUFQAAAABAQEBAQEBAQEBAQEBAQEBLjaAoHA4H0AwIDUAWMIQAAAaHySAoHA4H0AwIDUAWMIQAAAaAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAMOv8KPH0SFCR9AAAAAEY=</data> <key>complete-modeset</key> <data>AQAAAA==</data> <key>disable-agdc</key> <data>AQAAAA==</data> <key>dpcd-max-link-rate</key> <data>CgAAAA==</data> <key>rps-control</key> <data>AQAAAA==</data> <key>igfxfw</key> <data>AgAAAA==</data> <key>framebuffer-stolenmem</key> <data>AAAwAQ==</data> <key>framebuffer-fbmem</key> <data>AACQAA==</data> <key>framebuffer-patch-enable</key> <data>AQAAAA==</data> <key>enable-dvmt-calc-fix</key> <data>AQAAAA==</data> <key>enable-dbuf-early-optimizer</key> <data>AQAAAA==</data> <key>enable-dpcd-max-link-rate-fix</key> <data>AQAAAA==</data> <key>enable-cdclk-frequency-fix</key> <data>AQAAAA==</data> <key>enable-backlight-smoother</key> <data>AQAAAA==</data> <key>enable-backlight-registers-fix</key> <data>AQAAAA==</data> <key>force-online</key> <data>AQAAAA==</data> <key>framebuffer-con0-alldata</key> <data>AAAAAAAAAAAAAAAAAAAAAAIAAAAYAAAA</data> <key>framebuffer-con0-enable</key> <data>AQAAAA==</data> <key>framebuffer-con1-alldata</key> <data>AgAAAAAAAAABAAAAAQAAAAAEAADBAgAA</data> <key>framebuffer-con1-enable</key> <data>AQAAAA==</data> <key>framebuffer-con2-alldata</key> <data>AwAAAAoAAAABAAAAAQAAAAAEAADBAgAA</data> <key>framebuffer-con2-enable</key> <data>AQAAAA==</data> <key>framebuffer-unifiedmem</key> <data>AAAAgA==</data> <key>hda-gfx</key> <string>onboard-1</string> <key>model</key> <string>Intel Raptor Lake-P [Iris Xe Graphics]</string> - and emulating kernel like this (https://chriswayg.gitbook.io/opencore-visual-beginners-guide/advanced-topics/using-alder-lake) but maybe better inserting Ice Lake kernel datas (i applied the Fake but setting the Ice Lake CPU ID 0x0706E5, instead of Comet lake of the guide mentioned) : Cpuid1Data : E5060700 00000000 00000000 00000000 Cpuid1Mask : FFFFFFFF 00000000 00000000 00000000 It's working but still 15 MB of RAM on system informations and no acceleration (either metal or QE/CI graphics acceleration didn't work) So, today i discovered that there is a little bit accent of support tò Raptor Lake gen.. i think i must wait future release of Whatevergreen tò have full support.. or maybe i'm not seeing right the Hackintool logs .. Edited 8 hours ago by ASUS Vivobook 1 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Saturday at 02:44 AM Author Share Posted Saturday at 02:44 AM (edited) EFI.rar Edited Saturday at 04:44 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 11:46 AM Author Share Posted Sunday at 11:46 AM (edited) - [EDIT] NB : Now using this rebuilded from clean master Nootedblue my PCIe is seen like an "Intel TigerLake-LP GT2 [Iris Xe Graphics]" ... but still 0 total VRAM either or acceleration either no framebuffer loaded... I'm going crazy.. platform id 0x9A490000 , device id 0x9A498086 (here the config.plist used with nb) (attached my L/E folder..) confignb.plist - [EDIT] WG : According to lshbluesky WhateverGreen (using his wg instead of nb), this conf should work but.. it reboot at middle loading of OS .. it respects his commits... but still not working I changed no platform id 0x9A490000 but yes device id to 0x8A5A8086 (spoofing like a Tiger Lake) (it's the device-id that make me crash... i know) (here the config.plist used) configwg.plist His commits { 0x9A49, 0x0000, "Intel Iris Xe Graphics" }, { 0x9A49, 0x8A52, "Intel Iris Xe Graphics" }, { 0x9A40, 0x8A52, "Intel Iris Xe Graphics" }, { 0x9A60, 0x8A5A, "Intel Iris Xe Graphics" }, { 0x9A68, 0x8A5A, "Intel Iris Xe Graphics" }, { 0x9A70, 0x8A5A, "Intel Iris Xe Graphics" }, { 0x9A78, 0x8A5A, "Intel Iris Xe Graphics" }, // Reserved/unused/generic Tiger Lake }, (Also applying this https://dortania.github.io/Getting-Started-With-ACPI/Universal/spoof.html doesn't work) (Also tryed to modify lshbluesky wg and applying only platform id 0x9A490000 (device-id is now 0xA7A08086) this works but no framebuffer loaded This is my commit : { 0x9A49, 0x8A5A, "Intel Iris Xe Graphics" }, { 0xA7A0, 0x8A5A, "Intel Iris Xe Graphics" }, ) NootedBlue.kext.rar WhateverGreen-1.6.7-d8.zip Edited 8 hours ago by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted Sunday at 05:43 PM Author Share Posted Sunday at 05:43 PM (edited) How can i get and where can i get HW Graphics debugging for fails with Whenevergreen kext ? Please tell me precisely I want to investigate on the reboot of my machine with tiger lake spoofing... i don't understand very much easier in this topic... -liludbg ? Add -liludbg to enable debug printing (available in DEBUG binaries). -wegdbg ? Enable debug printing (available in DEBUG binaries) Must i use debug version of the kexts? -v ? Any other methods? This is the folder i can access from windows I've found E:\private\var\log\system.log but there are no related messages .. i cannot reach to find/to have log output or system log related to the graphic fail.. i cannot understand without these [EDIT] I'm looking now inside Mac with dmesg or Hackintool... nothing found related to graphic or framebuffer loading.. Edited yesterday at 02:06 AM by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted 8 hours ago Author Share Posted 8 hours ago (edited) I'm going forward and reaching to understand how nootedblue (rebuilded from master version) works.. before i used it without inserting my real device-id that is "0xA7A08086" in info.plist IOPrimaryMatch .. i've updated/erased some early post [EDIT] tryed nootedblue rebuilded from the master instead of wg with *LE what i should try? It stucks on boot with my real device-id.. i've tryed also signed sle internal with graphicscheduler select 0,1,3, or 5... it stucks or reboots... Edited 4 hours ago by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted 6 hours ago Share Posted 6 hours ago (edited) since you're in adl i think it's better to discuss it here. to get logs open terminal and paste log show --style syslog --predicate 'processID == 0' --last 1h --info --debug > /tmp/x.log then open /tmp/x.log 1st step is install the framebuffers kexts in /L/E next build and install hookcase.kext in /L/E fix permissions for kexts /L/E - os x will ask for permission to use the new kexts. if this fails delete /Library/KernelCollections/AuxiliaryKernelExtensions.kc bulid nblue.kext install in opencore kexts folder. add your card id to the correct info.plist entry boot with -v debug=0x100 keepsyms=1 IGLogLevel=8 dont use whatevergreen with nblue ! on panic,hang some logs will be on /Library/Logs/DiagnosticReports as for adl cards i think enabling/disabling some patches (from nblue or whatevergreen code) might make the framebuffer to load your config.ini don't need PciRoot(0x0)/Pci(0x2,0x0) if using nblue Edited 2 hours ago by jalavoui 1 Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted 4 hours ago Author Share Posted 4 hours ago (edited) .Found nothing of useful with "log show --style syslog --predicate 'processID == 0' --last 1h --info --debug > /tmp/x.log then open /tmp/x.log" Edited 2 hours ago by ASUS Vivobook Link to comment Share on other sites More sharing options...
ASUS Vivobook Posted 1 hour ago Author Share Posted 1 hour ago (edited) I've found a method : is that to remove IONDRVSupport.kext from the system ... but I don't have a root with write permission I've got csrutil disabled but Authenticated Root status: enabled [EDIT] But wtf is a kext in use ... i cannot perform this... Edited 53 minutes ago by ASUS Vivobook Link to comment Share on other sites More sharing options...
jalavoui Posted 37 minutes ago Share Posted 37 minutes ago (edited) very bad idea remove iondrv - it is needed by other kexts. take a look at my config. maybe it helps when your system is fine just install the kexts i said in /Library/Extensions you only will get logs after correctly install nblue don't mount the system rw - you only will break it Arquivo.zip Edited 35 minutes ago by jalavoui Link to comment Share on other sites More sharing options...
Recommended Posts