Jump to content

[80% Solved] Iris Xe iGPU on Tiger Lake successfully loaded ICLLP Frambuffer and VRAM also recognizes 1536MB! + However, some issues.

shl628

By shl628,
in Intel

 Share
604 posts in this topic

Recommended Posts

naiclub
naiclub
Posted
Posted (edited)
4 hours ago, litemintx said:

You have Radeon GPU, you can try NootedRed if thats supported.

@litemintx  Could you please explain this to me? What do I need? Is there anything special?

 this   I read it and still don't understand. Could you please explain it?

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

https://elixir.bootlin.com/linux/v6.12-rc1/source/drivers/gpu/drm/xe

 

new intel linux code - check the comment

 

image.png.8c3f5c0f6d4a6fe5abc1b41b5b802692.png

 

you guys can try the new driver if updating kernel. to get logs use debug flags

 

mesa source code

https://gitlab.freedesktop.org/mesa/mesa

 

image.thumb.png.aab1c6ff6003007e4cb367e667c420f5.png

Capturadeecr2024-10-04s19_19_51.png.ea41a13a5b2d85d44c3c15ddf9b8ca52.png

 

Capturadeecr2024-10-04s19_19_04.png.17e824b0c0991739a8ca46fb282e1384.png

 

image.png.4e1a0f8f7aa1a5b2ab3b5742939d8dd7.png

 

so using mesa for gt2:

 

GFX12_GT_FEATURES(2)

GFX12_FEATURES(2,1,8)

.num_subslices = 6

.gt = 2

.num_slices = 1

.l3_banks = 8

.max_eus_per_subslice = 16

 

Edited by jalavoui
  • Like 2
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

this are tgl caps for gt1/2

 

image.png.53855a59704c251b9d6f067994a15878.png

 

altough IGScheduler5 doesn't crash it is not working - if someone solve this then the acelerator will work

 

this var as changes in icl/tgl graphics kext

image.png.a705cd4c31e742979354453b4cae2553.png

Edited by jalavoui
  • Like 2
Link to comment
Share on other sites
benmacfreak
benmacfreak
Posted
Posted
1 hour ago, jalavoui said:

this are tgl caps for gt1/2

 

image.png.53855a59704c251b9d6f067994a15878.png

 

altough IGScheduler5 doesn't crash it is not working - if someone solve this then the acelerator will work

 

this var as changes in icl/tgl graphics kext

image.png.a705cd4c31e742979354453b4cae2553.png

idk how to solve that jala, but when and if someone does ill gladly try it out on my laptop :)

Link to comment
Share on other sites
arquicion
arquicion
Posted
Posted
On 9/9/2024 at 5:52 AM, Mastachief said:

Can you share you current config.plist?

 

To test i place nblue in EFI/OC/Kexts

 

and hookcase + sle_internal (AppleIntelTGLGraphicsFramebuffer.kext only) in L/E

 

i get  iGPU hang message in verbose boot.

 

If I put nblue + hookcase + sle_internal (AppleIntelTGLGraphicsFramebuffer.kext only) in L/E (and disable nblue in EFI/OC/Kexts)

 

i get the same result, iGPU hang.

 

funny thing is, if i put back the previous nblue in EFI/OC/Kexts i can boot to the GUI again. I am attaching the current nblue that works for me and my current config.plist

 

NootedBlue.kext.zip 36.6 kB · 25 downloads

 

Config.plist 37.47 kB · 21 downloads

 

Keep in mind that the attached config.plist (based on nblue) is different from the one on Github (that one is based on WhateverGreen) so dont mix and match the files.

Hello! Do you use the NootedBlued with the AppleIntelTGLGraphicsFramebuffer kexts in L/E? I'm testing this on an ASUS X515EA (i7-1165G7). I've installed Ventura, and It's works fine just with the NootedBlue.kext but after some minutes it crashes and the I got the Error Report with the kernel panic backtracked. I will try the boot args that you have in the config.plist. Many thanks. Any more ideas will be welcomes.

  • Like 1
Link to comment
Share on other sites
Mastachief
Mastachief
Posted
Posted

No, you cannot. They need devs to work and get it working, not testing. You can use the Mesa library info for inspiration to help you port it over yourself.

Check or Monitor Kernel Logs: With HookCase configured, reboot your system with verbose logging enabled (-v flag) to capture real-time kernel messages. HookCase will now log every time one of the hooked functions is called. You can use Console.app or dmesg to examine these logs. Look for patterns like:

Whether tglframebuffer is starting correctly and attaching to the GPU.

If AGPM is detecting the framebuffer and adjusting power profiles accordingly.

If it's crashing, it could be a profile issue or a IOService::start and IOService::probe problem, and you haven't even reached the accelerator yet, or core image, and from a kernel engineering standpoint, I'd suggest prioritizing the patching of AppleGraphicsDevicePolicy and IOAcceleratorFamily2 to accommodate the Tiger Lake architecture, as these kexts control GPU management, acceleration features, and hardware-accelerated rendering pipelines. Jala is working on the pipelines via DDIO etc. Still only 9A40 and 9A40.

Check the GTK, I'm still reviewing as there is so much content. But you probably have to patch on your own as the only profiles that will work are the 9A49 AND 9A40 iGPU


Link to comment
Share on other sites
benmacfreak
benmacfreak
Posted
Posted
3 minutes ago, Mastachief said:

No, you cannot. They need devs to work and get it working, not testing. You can use the Mesa library info for inspiration to help you port it over yourself.

Check or Monitor Kernel Logs: With HookCase configured, reboot your system with verbose logging enabled (-v flag) to capture real-time kernel messages. HookCase will now log every time one of the hooked functions is called. You can use Console.app or dmesg to examine these logs. Look for patterns like:

Whether tglframebuffer is starting correctly and attaching to the GPU.

If AGPM is detecting the framebuffer and adjusting power profiles accordingly.

If it's crashing, it could be a profile issue.

i am just a user chief im not a dev by extent of the word, so i cant do much but test as i've stated before. So i will just wait and test accordingly.

Link to comment
Share on other sites
Mastachief
Mastachief
Posted
Posted

Also see below for a possible patches needed list, or kexts/binaries/profiles that may/need to be patched. Jala has patched in a way for some bypass of calls that are done via hookcase, but major patching still remain.

1. tglframebuffer.kext


2. AppleGraphicsDevicePolicy.kext


3. IOAcceleratorFamily2.kext


4. AGPM (AppleGraphicsPowerManagement.kext)


5. AppleGraphicsControl.kext


6. IOFramebuffer.kext


7. CoreDisplay.framework


8. AppleIntelGraphics.kext


9. AppleGraphicsPowerControl.kext, verify via Mesa framework for power profiles.


10. AppleIntelFramebuffer.kext (if needed, based on smbios)


11. IOGraphicsAccelerator.kext


12. Framebuffer-patch injection via Config.plist (in OpenCore or Clover) if your igpu is not 9A49 or 9A40.


13. Metal.framework


14. OpenCL.framework


15. AppleIntelGraphicsMCE.kext


16. CoreImage.framework


17. gMux (for dual GPU setups, for the radeon gpu guy that was here)


18. PCI Device ID spoofing (for Tiger Lake recognition in macOS)


19. ACPI patches (DSDT edits) (for Tiger Lake GPU initialization)


20. AppleBacklight.kext (for brightness control)


21. AGPM profiles patching


22. Kernel Cache rebuilding


23. NVRAM boot arguments (for Tiger Lake-specific adjustments)


24. System Integrity Protection (SIP) adjustments (for custom kext injection)


25. AppleMCCSControl.kext


26. Graphics-related SMBIOS settings (iMac-like profiles for GPU compatibility, not the macbook pro or air profiles)

  • Like 1
Link to comment
Share on other sites
benmacfreak
benmacfreak
Posted
Posted
1 hour ago, Visual Ehrmanntraut said:

What exactly is happening right now?

idk visual, everything jalavoui has said in these 20 pages has made ZERO sense to me. as i said im just a user patiently waiting for the kext to give me working acceleration. i dont know anything of how to help dev this stuff, nor the time or etc. to devote to learning it, so im leaving it to the people doing it. sorry all i can do is test that's it.

Link to comment
Share on other sites
Mastachief
Mastachief
Posted
Posted
What exactly is happening right now?
Jala was providing info based on Mesa for inspiration in fixing igscheduler. It's still devs only right now that should be commenting, I just posted to clarify some doubts about what's remaining for what's needed for people who kept assuming they need to test who might be non-devs.
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

right let me share some new logs

 

if i ignore wrong config of slices,etc and display pipes i can reach this. patching this allow the display to show working cursor with a  black screeen. this is very bad practice  but allow to get some gpu hang logs

 

image.png.57333243bd46119c4e351ad98f5af87e.png

 

windowserver display panic (temp patch in DYLDPatches.cpp depends on os x version)

image.png.f96ce2cf333348212aba41b82e7b4be9.png

 

WindowServer-2024-10-07-032842.ipsMTLCompilerService-2024-10-07-234202.ipsKernel_2024-10-08-005107_Mac.gpuRestart

 

can you guys check if you have this igpu property ?

image.png.0f86f888cce7ca167bcff455601562fa.png

 

 

Edited by jalavoui
Link to comment
Share on other sites
Mastachief
Mastachief
Posted
Posted
On 10/10/2024 at 6:21 AM, jalavoui said:

windowserver display panic (temp patch in DYLDPatches.cpp depends on os x version

 

can you guys check if you have this igpu property ?

image.png.0f86f888cce7ca167bcff455601562fa.png

 

 

 

 

A panic in WindowServer points to issues in how the framebuffer interacts with macOS's core display services. The temporary patch in DYLDPatches.cpp might be bypassing some version-specific checks, but it still results in the system becoming unstable (segmentation fault or access violation based on what youve shown).

 

core display patch needed then?

  • Display Pipeline Errors:

The logs show multiple references to CoreDisplay::DisplayPipe, particularly in the function stack: 

CoreDisplay::DisplayPipe::RunFullDisplayPipe
CoreDisplay::DisplayPipe::RunGPUDisplayPipe
CoreDisplay::DisplayPipe::Commit
CoreDisplay::Display::Present

These indicate that the display pipeline is not being fully initialized or committed, leading to incomplete GPU rendering on the display. This is likely where the cursor works but the screen remains black—cursor rendering is handled separately, while the main framebuffer fails to initialize. its the same reason why with nootedblue the cursor moves so fast now, versus its choppy behaviour with whatevergreen.

 

The log mentions VM_REGION errors related to memory regions that are either unmapped or unallocated. This might suggest an issue in GPU power management or resource allocation via AGPM (AppleGraphicsPowerManagement.kext).

 

These failures could be linked to improper configuration of display pipes or slices, causing GPU memory to be mapped incorrectly or not at all.

 

Key Call Stacks:

  • DisplayPipe Functions:

    • The critical crash location occurs in:
      • CoreDisplay::DisplayPipe::RunFullDisplayPipe
      • CoreDisplay::DisplayPipe::Commit
      • CoreDisplay::Display::Commit
      • These functions are responsible for managing the GPU display pipes, which route pixel data from the framebuffer to the display. Given that the iGPU is partially working (cursor shows, but a black screen persists), it suggests that the display pipes are misconfigured or not properly handling display data.

  • Present/Rendering Functions:

    • Additional frames suggest the system fails during the present/update cycle:
      • CoreDisplay::Display::Present
      • WS::Displays::CDDisplay::present_update
      • These functions relate to frame presentation, where completed frames are sent to the display. The presence of these functions in the crash stack indicates that the system is attempting to commit frames to the display, but something in the process (likely framebuffer or pipe misconfiguration) causes a failure.

The crash log reports KERN_INVALID_ADDRESS, which means the system tried to access a memory region that wasn't properly allocated or mapped. This points to incomplete memory mapping for the framebuffer or improper slice configuration, leading to invalid memory accesses.

 

The log mentions consecutive crashes and throttle timeout. This indicates that the WindowServer has been crashing repeatedly, likely due to the same unhandled GPU issues, which may result in the system preventing further crashes by throttling the WindowServer process.

 

The framebuffer profiles are usually hardcoded into the framebuffer kexts themselves, with configuration tables that define how the framebuffer interacts with different Intel iGPU models. For both ICLFramebuffer and TGLFramebuffer, the configuration data is embedded within the binary code of the kext.

 

todo

  • patch AppleGraphicsPowerManagement.kext to include the correct power management profiles for Tiger Lake 9A49.
  • Ensure that the AGPM profiles are correctly set up to prevent GPU hangs when switching power states.

 

 

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

maybe (AppleMobileFileIntegrity) AMFI failing in ioaceleratorfamily2 ?

 

i just installed kdk and try with signed kexts in /S/L/E - not sure if it helped

 

image.png.86872b486e5f68ff9363be8dfddcc507.png

 

but then the port config is wrong as forcing the display tobe on frame 1 bypass link config, etc and ofc the pipes won't work for aceleration.

 

problem is frame/pipe 0 config in connectors is always lcd and code calls like this use wrong address 0x6f000

image.png.4d9612124bba7eb6a69320927d833484.png

image.png.17b2cec3a760dcad9b4a295e358465c0.png

 

and here is the linux comment

image.png.a0d222145d656c7fc6f36c78e5d04fd2.png

 

 

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

so then tglframebuffer is the only way out? since tigerlake EDP pipe will be under transcoders, but icelake edp is direct to registers?

 

Also i built the nootedblue.kext and edited the info.plist, however even after changing xxxxx to apple for the specific framebuffer i wanted to test, it failed to boot, gave a kp and even making edits to kerngen11.cpp and .hpp still creates booting issues even though it compiles, im trying to do tgl vs icl binary comparisons based on the current Sonoma and the DTK files. so much is different.

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

i updated kexts to included also the signed version without link to hookcase so they can be moved to /S/L/E

 

nblue is now by default loading AppleIntelTGLGraphics.kext + bundles from /S/L/E (might work in /L/E)

 

the default AppleIntelICLLPGraphicsFramebuffer is in /L/E and is linked to hookcase

 

patches in AppleIntelICLLPGraphicsFramebuffer now skip pipe errors. there is actually several ways to achiev this (idk yet which will work better because its bot only registers that change, there's also some if-else cases that need patching)

 

atm the only crash i get is

 

MTLCompilerService-2024-10-13-0010552.ips

 

so in my ventura testing i installed  Kernel_Debug_Kit_13.3_build_22E252. other os versions wll need kdk so sys cache rebuilds.

Delete AppleIntelICLGraphics.kext if you get issues building sys cache

 

to use the non signed com.xxxxxx.driver.AppleIntelTGLGraphics you need to edit the info.plist of Gen7TGL and change (apple to xxxxx)

image.png.663e055cdd9ea00eaee1f22112c53056.png

then it will load in /L/E if changing the path in

image.png.8dcf1b82c922b460a6b4f2a659c3a6ae.png

xxxxx kexts lose the signed bit so they need tobe hacked with hookcase in order to work in /L/E

 

the AppleIntelTGLGraphicsFramebuffer.kext seems to work only with DG1 cards. i hope someone with the hardware checks it. i do think that with some registers changes for memory, plane/scaler it can work for icl/adl cards

 

btw breaking os x seal also broke my usb booting. i fixed by disable secure boot in opencore misc settings

i used https://github.com/jacklukem/BigSurmountsrw to mount rw - maybe other tools exist ?

don't try this on a os x version you use a lot - create a test version on some usb disk

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

When nblue kext is compiled inside of the info.plist it lists Gen7TGL_LE instead of Gen7TGL, I'm guessing it's just to indicate it's the unsigned version and that's it's intended for Library/Extensions ?

27c54baf7c7e42c9110dcc390f85183f.jpg

I use https://github.com/fxgst/writeable_root
 
big bummer on the DG1 compatibility though, no one so far has come forward with that card model.
 
Tigerlake was released September 2020
DG1 was released around Oct - Nov 2020
 
I also just noticed that DG1 was PCI based and not Ring Bus based.






Edited by Mastachief
  • Like 1
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted (edited)

found the pipe issue problem. in icl the hwUpdateRegCache() update for edp is port 0. i.e. the first conector

 

on tgl the code changed to use pipe_A instead of icl pipe_EDP address

 

but patching this on icl cause other issues with remaining edp panel code

 

anyway i'ts progress

Edited by jalavoui
Link to comment
Share on other sites
ASUS Vivobook
ASUS Vivobook
Posted
Posted (edited)
On 5/14/2024 at 6:37 PM, Mastachief said:

Okay here is the result of using the following config using the attached whenvergreen. im using my EDID in the config below, so modify to yours if needs be. its now being listed under index 0 instead of 2 in hackintool. Now it connects to display0 under framebuffer@0. You can also use AAPL,ig-platform-id 00008A52 and device-id 8A530000 as well to achieve the result if you want, you can also see the previous log.

 

Boot args: -v keepsyms=1 debug=0x100 -wegdbg igfxfw=2 -liludbg

 

Sonoma 14.4.1

  

<key>AAPL,GfxYTile</key>
				<data>AQAAAA==</data>
				<key>AAPL,ig-platform-id</key>
				<data>AABSig==</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>device-id</key>
				<data>U4oAAA==</data>
				<key>device_type</key>
				<string>VGA compatible controller</string>
				<key>disable-agdc</key>
				<data>AQAAAA==</data>
				<key>dpcd-max-link-rate</key>
				<data>CgAAAA==</data>
				<key>enable-cdclk-frequency-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-dvmt-calc-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-patch-enable</key>
				<data>AQAAAA==</data>
				<key>framebuffer-unifiedmem</key>
				<data>AAAAgA==</data>
				<key>model</key>
				<string>Intel Iris Xe Graphics</string>

this is the same as:

 

image.thumb.png.bad5454ac645369933101dde9db8a107.png

 

Which translates to:

 

image.thumb.png.176cd65b33e1bf4a06faba1019fab406.png

 

if I run the following command in terminal /System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a

 

I get the following result: 

Big@MacBook-Pro ~ % /System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a 
AGDCDiagnose Version: 8.1.9 (AGDC node count: 2)
### Start: GPUWrangler #######################################################
Stats: GPUCAdded:0 GpuAdded:1 Eject:0/f0/fd0/c0 Remove:0/t0 Un:0

gpu 0xe913 flags 0xb2000010 (IG,published,quiet,pubSched,pubArmed) vid.did=8086.8a53 b:d:f=0:2:0 
gpu 0xe913        pci 0x100000321 IOService:/AppleACPIPlatformExpert/PC00@0/AppleACPIPCI/IGPU@2
gpu 0xe913       agdc 0x1000004d2     /AppleIntelFramebufferController/IntelFBClientControl
gpu 0xe913       gpuc 0x000000000 
gpu 0xe913 agdpclient 0x000000000 
gpu 0xe913      accel 0x000000000 
gpu 0xe913     fb0:-1 0x1000004b3     /AppleIntelFramebuffer@0
gpu 0xe913     fb1:-1 0x1000004b4     /AppleIntelFramebuffer@1
gpu 0xe913     fb2:-1 0x1000004b5     /AppleIntelFramebuffer@2

### End: GPUWrangler (took 0.004 sec) ########################################

### Start: EFIDisplayInfo ####################################################
Not present
Dumping EFI data for GPU Path IOService:/AppleACPIPlatformExpert/PC00@0/AppleACPIPCI/IGPU@2
### End: EFIDisplayInfo (took 0.003 sec) #####################################

### Start: Mux ###############################################################
### End: Mux (took 0.000 sec) ################################################

### Start: Ports #############################################################
### Start: AGDC[1] 0x100000483 ###############################################
IOService:/IOResources/AppleGPUWrangler
Vendor: Apple [0000106b]: AppleGPUWrangler [8 10000] (0)
### End: AGDC[1] 0x100000483 (took 0.001 sec) ################################

### Start: AGDC[2] 0x1000004d2 ###############################################
IOService:/AppleACPIPlatformExpert/PC00@0/AppleACPIPCI/IGPU@2/AppleIntelFramebufferController/IntelFBClientControl
Vendor: AppleIntelFramebufferController [0000106b]: IntegratedGPU [1 10000] (0)
FBs: 3, Ports: 0x7e mst:0x7c ddc:0 aux:0x7c, Streams: dp:0 dvi:0 mst:2 max:3
Framebuffers:
* 0: Address:  1.0 Stream: Enabled  Group: 0   Online   Assoc'd                    
  1: Address:  0.0 Stream: Not Associated Group: 0                                       
  2: Address:  0.0 Stream: Not Associated Group: 0                                       
Port Capabilities:
* 1: None
  2: AUX, MST
  3: AUX, MST
  4: AUX, MST
  5: AUX, MST
  6: AUX, MST
Connections:
* 1: 
  2: 
  3: 
  4: 
  5: 
  6: 
## EDID Dump Port 1 - Start ## 
// EDID Dump: device, 128 bytes, OK
uint8_t EDID_LGD_30e4_71e[] = {
  /* 000: */  0x00, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x00, 
  /* 008: */  0x30, 0xe4, 0x1e, 0x07, 0x00, 0x00, 0x00, 0x00, 
  /* 010: */  0x00, 0x1f, 0x01, 0x04, 0x95, 0x22, 0x13, 0x78, 
  /* 018: */  0x03, 0xb3, 0x85, 0x99, 0x5e, 0x5b, 0x8c, 0x26, 
  /* 020: */  0x1b, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, 
  /* 028: */  0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 
  /* 030: */  0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x2e, 0x36, 
  /* 038: */  0x80, 0xa0, 0x70, 0x38, 0x1f, 0x40, 0x30, 0x20, 
  /* 040: */  0x35, 0x00, 0x58, 0xc2, 0x10, 0x00, 0x00, 0x1a, 
  /* 048: */  0x1f, 0x24, 0x80, 0xa0, 0x70, 0x38, 0x1f, 0x40, 
  /* 050: */  0x30, 0x20, 0x35, 0x00, 0x58, 0xc2, 0x10, 0x00, 
  /* 058: */  0x00, 0x1a, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
  /* 060: */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
  /* 068: */  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 
  /* 070: */  0x00, 0x0c, 0x3a, 0xff, 0x0a, 0x3c, 0x7d, 0x12, 
  /* 078: */  0x14, 0x24, 0x7d, 0x00, 0x00, 0x00, 0x00, 0x01
};
## EDID Dump Port 1 - End ## 
### End: AGDC[2] 0x1000004d2 (took 0.458 sec) ################################

### End: Ports (took 0.458 sec) ##############################################

### Start: Metrics ###########################################################
Display Metric Tool Version: 1.2 
Display Metric Plugin Version: 1.2 AGDC Version: 8.1.9
Dumping Metric Logs: currentlog(1) logsize(32768) numberlogs(819)
Total lines: 2 
2024-05-14 14:17:11.875674-0500:               kAGDCPluginMetricsPowerOff(411e) GPU:0xe913 Port: 0 Will
### End: Metrics (took 0.001 sec) ############################################

### Start: displaypolicyd ####################################################
running 169 sec (started Tue May 14 14:17:09 2024, now Tue May 14 14:19:58 2024)
boardID: Mac-5F9802EFE386AA28
featureMask: 0
platformFlags: 0
extraSupportFlags: 0
wranglerFlags: 0x44
gpu[0]: index=0 state=0x5 (Published) events=() dispPolicyState=0x6 (WaitingForAGDP) dispPolicyLaunchIndex=-1
gpu 0xe913 flags 0xb2000010 (IG,published,quiet,pubSched,pubArmed)
gpu 0xe913        pci 0x100000321 IOService:/AppleACPIPlatformExpert/PC00@0/AppleACPIPCI/IGPU@2
gpu 0xe913       agdc 0x1000004d2     /AppleIntelFramebufferController/IntelFBClientControl
gpu 0xe913       gpuc 0x000000000 
gpu 0xe913 agdpclient 0x000000000 
gpu 0xe913      accel 0x000000000 
gpu 0xe913     fb0:-1 0x1000004b3     /AppleIntelFramebuffer@0
gpu 0xe913     fb1:-1 0x1000004b4     /AppleIntelFramebuffer@1
gpu 0xe913     fb2:-1 0x1000004b5     /AppleIntelFramebuffer@2
Version: 8.1.9, Max: 512, counter: 13, calendar sync: 0x6186ed934d0a5/0xb1cbaf
GTRACEDATASTREAM traceData = {
    { 0x67547261, 0x63654461, 0x74614475, 0x6d700000, 0x102, 512, 13, 8, 1, 9, 0, 56, 1715714229850277, 11652015 },
    {
        { 11603316365, 0x0, 392, 38, 0, 0, 0x0, 0x0, 0x0 },
        { 13569842836, 0x0, 744, 88, 56, 0, 0x0, 0x4, 0x0 },
        { 13716189171, 0x0, 522, 72, 73, 0, 0x1, 0xe913, 0x0 },
        { 13716323080, 0x0, 70, 71, 73, 0, 0x20001, 0xe913, 0x0 },
        { 18032770978, 0x0, 522, 72, 73, 0, 0x1, 0xe913, 0x0 },
        { 18032923007, 0x0, 70, 71, 73, 0, 0x50002, 0xe913, 0x0 },
        { 18033103227, 0x0, 81, 77, 73, 0, 0x60000, 0xe913, 0x0 },
        { 48420370691, 0x0, 663, 84, 84, 0, 0x1, 0x1, 0x0 },
        { 48438912140, 0x0, 663, 84, 84, 0, 0x1, 0x1, 0x0 },
        { 49286990388, 0x0, 663, 84, 84, 0, 0x11, 0x1, 0x0 },
        { 49352426347, 0x0, 663, 84, 84, 0, 0x1, 0x1, 0x0 },
        { 57266712649, 0x0, 663, 84, 84, 0, 0x11, 0x1, 0x0 },
        { 62281474230, 0x0, 663, 84, 84, 0, 0x1, 0x1, 0x0 },
    }
};
### End: displaypolicyd (took 0.002 sec) #####################################

### Start: Devices ###########################################################
### Start: AGDC[1] 0x100000483 ###############################################
IOService:/IOResources/AppleGPUWrangler
Vendor: Apple [0000106b]: AppleGPUWrangler [8 10000] (0)
### End: AGDC[1] 0x100000483 (took 0.000 sec) ################################

### Start: AGDC[2] 0x1000004d2 ###############################################
IOService:/AppleACPIPlatformExpert/PC00@0/AppleACPIPCI/IGPU@2/AppleIntelFramebufferController/IntelFBClientControl
Vendor: AppleIntelFramebufferController [0000106b]: IntegratedGPU [1 10000] (0)
### End: AGDC[2] 0x1000004d2 (took 0.000 sec) ################################

### End: Devices (took 0.001 sec) ############################################

### Start: mpxdiagnose #######################################################
### End: mpxdiagnose (took 0.011 sec) ########################################

AGDCDiagnose completed in 0.460048 seconds

Other notable errors

 

2024-05-14 11:59:48.511372-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][GTPM_SLICESWITCH] : Invalid fRingTables, check if AGPM driver is loaded\

 

2024-05-14 12:00:04.732063-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][AUX       ] readAUX for address 0x600 failed with error 0xe00002d6\
2024-05-14 12:00:04.732065-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][POWER     ] Failed to set DP power state in 10s\
2024-05-14 12:00:04.751558-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG  ][DISPLAY   ] FB0: Online info for DDI = 0, PortType = 0\
2024-05-14 12:00:04.751592-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG  ][DISPLAY   ] FB0: fIsHDMI = 0, fEnableAudio = 0, newOnline = 1, fOnline = 1, fMaxPixelClock = 720000000\
2024-05-14 12:00:04.751599-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG  ][DISPLAY   ] FB0: newOnline: 1, fOnline: 1\
2024-05-14 12:00:04.751604-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG  ][DISPLAY   ] FB0: edid != fEDID\
2024-05-14 12:00:04.751609-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG  ][VRR       ] FB0: Indicate VRR Support in TimingRange\
2024-05-14 12:00:04.751623-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][DISPLAY   ] FB0: Invalid port type\
2024-05-14 12:00:04.752078-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][AGDC      ] AGDC Callback is not yet registered!!\

 

2024-05-14 12:00:09.591266-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][DISPLAY   ] Not able to get the current timing info\

 

2024-05-14 12:00:10.155672-0500  localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][ERROR][DISPLAY   ] Display Pipe Underrun occurred on pipe(s) A\

 

 

 

 

 

 

 

 

boot.log 1.7 MB · 5 downloads

 

WhateverGreen.kext.zip 293.57 kB · 32 downloads

 

I have tryed also these PciRoot(0x0)/Pci(0x2,0x0) confs but my pc reboots/gets stuck during the installation..

Edited by ASUS Vivobook
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...