Jump to content
213 posts in this topic

Recommended Posts

2 hours ago, deeveedee said:

@miliuco Note that the original EFI in Post #1 has no DeviceProperties.  I will be amazed if it works.

You are right, forgotten that. Then, @Alan Sojan must add a framebuffer to his first config.plist. Maybe AAPL,ig-platform-id=00003B19 is a good starting point. 

1 hour ago, miliuco said:

You are right, forgotten that. Then, @Alan Sojan must add a framebuffer to his first config.plist. Maybe AAPL,ig-platform-id=00003B19 is a good starting point. 

Hi, how would I do this? Is it like this?

Screenshot 2023-04-15 at 18.12.34.png

@Alan Sojan

 

Yes, it's so. Trying after this (if it fails) others framebuffers, replacing only the value. E.g. those posted by @Slice and others: 00001619 / 02001619 / 00001E19 / 00002619 / 00002719 / 00001B19.

You must add the property framebuffer-patch-enable with value of 01000000 as Data, this key says to WhateverGreen to patch the framebuffer.

I don't use configurators, only plist files editor, to avoid errors when OpenCore Configurator doesn't match the OpenCore version. But the result must be like this:

 

Spoiler

occ.thumb.png.d1b52def2abf70022c2719a4310c373b.png

 

 

Edited by miliuco
  • Like 1
19 hours ago, miliuco said:

@Alan Sojan

 

Yes, it's so. Trying after this (if it fails) others framebuffers, replacing only the value. E.g. those posted by @Slice and others: 00001619 / 02001619 / 00001E19 / 00002619 / 00002719 / 00001B19.

You must add the property framebuffer-patch-enable with value of 01000000 as Data, this key says to WhateverGreen to patch the framebuffer.

I don't use configurators, only plist files editor, to avoid errors when OpenCore Configurator doesn't match the OpenCore version. But the result must be like this:

 

  Reveal hidden contents

occ.thumb.png.d1b52def2abf70022c2719a4310c373b.png

 

 

Hi, I tried all of the framebuffers with the framebuffer-patch-enable but it results in ":Whatever green igfx: @TCCE: failed to route the function istypeconlysystem" 

Maybe I need to try this as I have no option to select DVMT in BIOS.

Screenshot_20230416_162710_Edge.jpg

Edited by Alan Sojan

@Alan Sojan Please continue to post your current config.plist each time you report a problem and / or ask for help.  I could have sworn that frame buffer-stolenmem and framebuffer-fbmem were in one of the config.plist posted in this thread, so it's going to be hard to keep track of the changes unless you post your config.plist each time.

  • Like 1
13 minutes ago, deeveedee said:

@Alan Sojan Please continue to post your current config.plist each time you report a problem and / or ask for help.  I could have sworn that frame buffer-stolenmem and framebuffer-fbmem were in one of the config.plist posted in this thread, so it's going to be hard to keep track of the changes unless you post your config.plist each time.

Config.plistThis is the config.plist. It makes my monitor screen turn off before the apple logo comes on

@Alan Sojan

 

6 hours ago, Alan Sojan said:

Hi, I tried all of the framebuffers with the framebuffer-patch-enable but it results in ":Whatever green igfx: @TCCE: failed to route the function istypeconlysystem" 

Maybe I need to try this as I have no option to select DVMT in BIOS?

Yes, try adding also framebuffer-stolenmem and framebuffer-fbmem. These values are fixed, 00003001 and 00009000. 

AAPL,ig-platform-id is the property to try different values.

  • Like 1

@Alan Sojan Please try the attached config.plist.  It sets the connector types to HDMI (consistent with @Rocky12's post) and does a few other things.  I'm assuming that you are testing this with Monterey (not Ventura), you do not have a discrete graphics card (you are using the Intel iGPU) and your BIOS is configured to use the iGPU.  Please report your test results with this config.plist.  Thank you.

 

EDIT: Please attach your current config.plist to the post with your test results.

 

EDIT2: If config.plist doesn't work, please try the attached config2.plist (you'll need to rename it to config.plist to use it in your OpenCore EFI).  config2.plist includes boot-arg -disablegfxfirmware which we might need until graphics are working. I'm not sure about this boot-arg with Skylake, but I needed it when I was first trying to find a working solution for my CoffeeLake hack

 

 

Config.plist.zip

 

Config2.plist.zip

Edited by deeveedee
  • Like 2
14 hours ago, deeveedee said:

@Alan Sojan Please try the attached config.plist.  It sets the connector types to HDMI (consistent with @Rocky12's post) and does a few other things.  I'm assuming that you are testing this with Monterey (not Ventura), you do not have a discrete graphics card (you are using the Intel iGPU) and your BIOS is configured to use the iGPU.  Please report your test results with this config.plist.  Thank you.

 

EDIT: Please attach your current config.plist to the post with your test results.

 

EDIT2: If config.plist doesn't work, please try the attached config2.plist (you'll need to rename it to config.plist to use it in your OpenCore EFI).  config2.plist includes boot-arg -disablegfxfirmware which we might need until graphics are working. I'm not sure about this boot-arg with Skylake, but I needed it when I was first trying to find a working solution for my CoffeeLake hack

 

 

Config.plist.zip 4.17 kB · 5 downloads

 

Config2.plist.zip 4.18 kB · 1 download

Hey, I tried both config.plist files and they both result in my monitor turning off. Here is my config2.plist

Config.plist

@Alan Sojan You're being patient - the most important thing about framebuffer patching.  And I've violated my own "rule" which is "provide guidance, but don't do it for you."  I hope you're starting to learn enough about the trial-and-error framebuffer patching process to start making some of your own guesses and experiments.  Try the attached config.plist which specifies framebuffer 19120000 and changes con1 port type to HDMI.

 

Here are some things that I'm considering if the attached doesn't work:

  • We may be having an issue with your HDMI->VGA adapter.  Do you have a monitor with HDMI input and an HDMI-HDMI cable?
  • Note in my post here that I needed to experiment with BusIds.  BusIDs in framebuffer patching are still black magic to me.  I'll be honest when I tell you that I got lucky by guessing BusIds that worked.
  • If you don't have an HDMI monitor and HDMI-HDMI cable, we may need to experiment with other port types (instead of HDMI).

Looking forward to your test results with the attached config.plist.

Config.plist.zip

Edited by deeveedee
  • Like 2

@Rocky12  Good stuff.  Note that the com.apple.driver.AppleGraphicsDevicePolicy patch discussed in that last post is the same as the disable-agdc DeviceProperty that I included.

  • Like 2

I found a post in "the forum that shall not be mentioned" that claimed that a working Skylake solution includes the following:

  • Change connector pipes to 0x12

Can anyone confirm that these changes make sense for Skylake?

Edited by deeveedee
  • Like 1

@deeveedee First, I want to say I really appreciate your effort; you must be a really good person. Well, I do have an Intel HD 530 on my Dell Optiplex 7050. macOS Ventura install with full GPU acceleration AAPL,ig-platform-id 00001259 without any patches

Screenshot 2023-04-18 at 03.24.38.png

Screenshot 2023-04-18 at 03.25.39.png

boot - args -v alcid=11 watchdog=0 igfxonln=1 igfxagdc=0 agdpmod=vit9696

  • Like 1
  • Thanks 1

@Rocky12  That's awesome!  What video ports do you use on your PC and are you using any video adapters (e.g., HDMI -> VGA)?

 

EDIT: @Rocky12 I'm impressed that you were able to find a working solution without WhateverGreen.kext.  I tried to patch my CoffeeLake graphics without WhateverGreen and failed (see here).  Thanks for posting this!  I see that your spoofing another device-id for Ventura - that makes sense.

 

EDIT2: Reading this more carefully implies that agdpmod=vit9696 is for AMD graphics.  @Rocky12  do you have this boot-arg left in your config.plist for an AMD graphics card, or did you require this for working iGPU HD530?

 

Edited by deeveedee
  • Like 2

@deeveedeeYes of course I have monitor big enough 39 inches, and it is connected through HDMI cable all the magic happen because of WhateverGreen.kext

and lastly to be honest I really didn't care about it what it does on intel GPUs agdpmod=vit9696 

Yes we have to use kabylake Device ID Because Apple drop support for skylake

Edited by Rocky12
  • Like 1
  • Thanks 1

@Alan Sojan I've never used boot-arg agdpmod=vit9696, but it's worth a try.  The attached config.plist includes boot-arg agdpmod=vit9696.  If your graphics wasn't working with the previous config.plist, please try the attached and report your results.

config.plist.zip

 

EDIT: Note that this documentation indicates that agdpmod=vit9696 boot-arg is for AMD and NVidia graphics, but doesn't mention it as a solution for Intel iGPU.  If agdpmod=vit9696 fixes this Skylake issue, then I believe that the Dortania docs will need to be revised.

Edited by deeveedee
  • Like 2

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...