[Acer PT14-51 Laptop] HowTo

[jkbuha]

8 hours ago, Stezza88 said:

 

Have you got a raptor lake A7A0 card too? @jkbuha

Yes, my production XPS 9730 (Raprtor Lake) does have that card. But the test machine I'm compiling this kext on is the XPS 9520 Alder lake, which has the 46A6 card.

 

The reason why I'm using the test machine not the (A7A0) production machine is that repeated resets have corrupted the keychain logins on the 46A6 machine and I dont want to corrupt a production machine atm.

 

With your latest kext, the machine never boots GUI (or even a black screen) because presumably it's looking for the A7A0 ID. I'll play around with the source code to see if I can change the IDs to match 46A6...

[Stezza88]

I did this, boot on black screen with square mouse xD (commenting hwConfigureCustomAUX call)

 

x.log

Edited 5 hours ago by Stezza88

[Stezza88]

<00 02 00 00>        DVI (Single Link)

FB0: set[0] is single-link

Maybe i must change to this the connector type in r3 patch..

Edited 4 hours ago by Stezza88

[Stezza88]

I changed r3 to this

static const uint8_t r3[]= {
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00, 0x18, 0x00, 0x00, 0x00,
			0x02, 0x00, 0x00, 0x00, 0x09, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x04, 0x00, 0x00, 0xc1, 0x02, 0x00, 0x00,
			0x03, 0x00, 0x00, 0x00, 0x0a, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x04, 0x00, 0x00, 0xc1, 0x02, 0x00, 0x00,
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
			0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

and got kp .. in 0xffffff7f96a490c7 com.xxxxx.driver.AppleIntelTGLGraphicsFramebuffer : __ZN24AppleIntelBaseController35hwCRTCToIODetailedTimingInformationEP21AppleIntelFramebufferP29IODetailedTimingInformationV2 + 0x499

Kernel-2024-11-18-222332.panic

 

Now I add

{"__ZN24AppleIntelBaseController35hwCRTCToIODetailedTimingInformationEP21AppleIntelFramebufferP29IODetailedTimingInformationV2", releaseDoorbell}

trying to resolve..

Edited 3 hours ago by Stezza88

[Stezza88]

..resolved, boot on black screen with square mouse xD

 

Log starts at 22:29:08.988461+0100

x.log

Edited 3 hours ago by Stezza88

[jalavoui]

4 hours ago, Stezza88 said:

I did this, boot on black screen with square mouse xD (commenting hwConfigureCustomAUX call)

 

x.log 2.53 MB · 0 downloads

 

this setup is you best option. the logs only show wrong pixelclock value (we had 2 patches to try fix this - agdc function and 1 patch with bytes)

the 1st connector is working 

the issue is when driver reach this log line

 

kernel[0]: (AppleIntelTGLGraphicsFramebuffer) [IGFB][DEBUG][DISPLAY   ][AppleIntelFB.cpp         : 4579 ][setGammaTable       ] (channelCount=3, dataCount=1024, dataWidth=10, data=0xffffff99f7217800) fCRTCIndex=0 syncToVBL=1
 

it just stops there. on a tgl working display this line repeats and ends with

 

kernel[0]: (AppleIntelTGLGraphicsFramebuffer) [IGFB][DEBUG][DISPLAY   ][AppleIntelFB.cpp         : 4579 ][setGammaTable       ] (channelCount=3, dataCount=1024, dataWidth=10, data=0xffffffa9cf282000) fCRTCIndex=0 syncToVBL=0

 

so question is why is this not working on raptor lake

 

try patch this part of code (camellia call). change 0x74, 0x5e to 0xeb, 0x5e so it jumps the call

 

 

you can try other things but the start point is a full working log with no hangs or log lines missing

try add missing addresses for adl firmware. they are in your linux logs

disable hwConfigureCustomAU call

Edited 5 minutes ago by jalavoui