Jump to content

[Acer PT14-51 Laptop] HowTo


Stezza88
 Share

413 posts in this topic

Recommended Posts

Laptop's Motherboard : Acer Predator PT14-51

CPU : 14 Core Intel i7-13700H

Integrated graphics : Intel Iris Xe Graphics (Raptor Lake gen)

Dedicated GPU : NVIDIA GeForce RTX 4070 Laptop GPU

Bios : Insyde UEFI V1.08

 

Final working stable versions of my OC config.plist with native NVRAM.. to change the Platform - Generic part, I'm still using those serials, btw generate it with the generator in the Opencore guide... boot arg lilucpu=17 isn't always needed but my system resulted like gen unknown so I must use it... dGPU must be disabled taking your path with gfxutil app (https://github.com/acidanthera/gfxutil/releases) .. I'm using Sonoma 14.7.1 so SMBIOS setupped at MacBook16,2 but maybe is better to use ventura..

 

BTW

- Touchpad is still not working

- Screen turned on and off isn't working during the installation

- audio is not setupped

- It detects (to me) a generic iGPU card with 15 MB of ram

 

GUIDES

- I have followed this guide : https://chriswayg.gitbook.io/opencore-visual-beginners-guide/advanced-topics/using-alder-lake

- followed @jalavoui hints in the later part of this topic for better config parameters

- follow this topic can help too

 

Here the config.plist.

 

confignb.plist

Edited by Stezza88
  • Like 1
Link to comment
Share on other sites

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

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

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

macos.jpg

 

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

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 posts

Edited by ASUS Vivobook
Link to comment
Share on other sites

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

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

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

very bad idea remove iondrv - it is needed by other kexts.

 

when your system is fine just install the kexts i said in /Library/Extensions

image.png.c956c285e0711f3f043d506d986bf656.png

 

 

you only will get logs after correctly install nblue

 

don't mount the system rw - you only will break it.

 

i would start by installing only this 2 kexts +hookcase.kext in /L/E

image.png.e7717108cbbcb8f5393c37680345cd0f.png

and test for loading using kextload -v

then try load nblue in opencore

 

when all his is done check for log files and post them here

 

btw get a linux log file for your card so we can check how it works

 

Edited by jalavoui
Link to comment
Share on other sites

I've strip down to the bone my config files however... adding this to wg doesn't change... maybe with the linux log things could go better

 

<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>

 

 

Edited by ASUS Vivobook
Link to comment
Share on other sites

Here the linux /var/log/syslog

 

syslog

 

sgiammoript@sgiammoript-Predator-PT14-51:~$ sudo lshw -C display
  *-display
       description: VGA compatible controller
       product: Raptor Lake-P [Iris Xe Graphics]
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 04
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 resolution=2560,1600
       resources: iomemory:620-61f iomemory:400-3ff irq:194 memory:6202000000-6202ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff
sgiammoript@sgiammoript-Predator-PT14-51:~$ lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}

00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) (prog-if 00 [VGA controller])
	Subsystem: Acer Incorporated [ALI] Raptor Lake-P [Iris Xe Graphics]
	Flags: bus master, fast devsel, latency 0, IRQ 194, IOMMU group 0
	Memory at 6202000000 (64-bit, non-prefetchable) [size=16M]
	Memory at 4000000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 4000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915, xe
sgiammoript@sgiammoript-Predator-PT14-51:~$ glxinfo | egrep -i 'device|memory'
    Device: Mesa Intel(R) Graphics (RPL-P) (0xa7a0)
    Video memory: 31797MB
    Unified memory: yes
    GL_AMD_performance_monitor, GL_AMD_pinned_memory, 
    GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_memory_object, 
    GL_EXT_memory_object_fd, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, 
    GL_AMD_pinned_memory, GL_AMD_query_buffer_object, 
    GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, GL_EXT_memory_object, 
    GL_EXT_memory_object_fd, GL_EXT_multi_draw_arrays, 
    GL_EXT_instanced_arrays, GL_EXT_map_buffer_range, GL_EXT_memory_object, 
    GL_EXT_memory_object_fd, GL_EXT_multi_draw_arrays,

 

Edited by ASUS Vivobook
Link to comment
Share on other sites

u forgot to use debug args

image.png.91c94adf74dd8fd678d2074f5b9c685d.png

you can remove the linux boot args as it produces huge log files when done

 

i use this boot args to get logs - but only if nblue loads to boot screen

 

image.png.5af8a0b137a1de7028a1794a8ffa690a.png

Edited by jalavoui
Link to comment
Share on other sites

kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=67dccc2e-d519-46e1-9d0b-3d6ce52c15ab drm.debug=0x1e log_buf_len=100M ro splash

 

it has produced a syslog file of 40Mb

and i have done "sudo truncate -s 0 /var/log/syslog" before restarting so the file was cleaned

Edited by ASUS Vivobook
Link to comment
Share on other sites

 Share

×
×
  • Create New...