Jump to content
3338 posts in this topic

Recommended Posts

24 minutes ago, miliuco said:

But I'm already telling you that for me it's too difficult.

This fix is from PikerAlpha

https://pikeralpha.wordpress.com/2016/07/13/simple-skylake-usb-fix-no-kexts-required/

Connector types in the ACPI specification(pages 524 and 525)

https://uefi.org/sites/default/files/resources/ACPI_6.0.pdf

Now i'm using USBInjectAll.kext + XHCI-unsupported.kext + SSDT-UIAC (This version of USBInjectAll.kext from topic bellow is updated to TigerLake, AlderLake, etc)

or

USBPorts.kext(by Hackintool) + XHCI-unsupported.kext

https://www.olarila.com/topic/14220-hackintosh-usb-port-mapping-guide-2021-2022-mojave-catalina-bigsur-monterey/

  • Like 4
21 minutes ago, deeveedee said:

That's awesome.  What gave you the idea to try it?

I have already build that clover long time a go, then some user in my forum have trying spare usb key and Voila

  • Like 1
15 hours ago, greythorne said:

Would you be able to share the details how you installed on a Skylake machine? What quirks to turn on or off, what kexts to include etc.

 

I am on Monterey 12.4 on my trusty Skylake Intel NUC.

 

Pre-install:

  1. Update OpenCore and related kexts: Lilu, WEG, VirtualSMC.
  2. Change SMBIOS to iMac18,1

No other changes required for config.plist. (Leave AvoidRuntimeDefrag=Yes for functioning NVRAM)
 

Download macOS 13 full installer here. Proceed to install/update macOS 13 via method of choice: Install.app (preferred) or bootable media.

 

Post-install:

  1. Spoof iGPU to KBL for full graphics acceleration: inject fake device-id <16590000> under Device Properties --> iGPU device location: PciRoot(0x0)/Pci(0x2,0x0)
  2. Choose appropriate KBL framebuffer profile: AAPL,ig-platform-id <00001259> under Device Properties --> iGPU device location: PciRoot(0x0)/Pci(0x2,0x0)

IMPORTANT: iGPU spoofing/adding KBL properties to be done post install for successful install of macOS 13. (installer otherwise hangs during last phase of installation).


Currently one issue reported: Due to SKL iGPU not having support for VP9 hw decode (YouTube), playback initiated through Safari will lead to iGPU instability thereby causing system freezes due to presence of VP9 decode-capability variable in KBL kext. If this is a deal breaker, you may:

  • opt to use codeless kext attached below however please note that this approach is still a WIP and as such leads to additional issues with booting into macOS 13 recovery/install media and HDMI/DP audio (not recommended)
  • use other browsers like Chrome, Firefox for YT playback in the meantime while waiting for a proper fix to this only issue.

 

UPDATE: Use WEG build attached below for fix to installer/recovery boot + VP9 fix for YouTube on Safari. Thanks @dhinakg and @PMheart

 

Cheers.

 

 

 

WhateverGreen-1.6.0-RELEASE.zip

Edited by aben
Updated post to add info about WEG build
  • Like 5
  • Thanks 1

@dhinakg made some progress on the spoofing progress, so now we can drop the use of injector. By using this method, installer/recovery will boot as well.

 

@aben I saw your injector, but looks like it was outdated; now we only remove the vp9 property `IOGVAXDecode`, which was confirmed to work as you posted on the PR. No?

  • Like 3
6 hours ago, D3v1L said:

Anyone on rx6600xt in Monterey or Ventura, with injected aty,henbury framebuffer instead of natively load aty,radeonframebuffer with lower geekbench score? ...mean...55000vs91000 Not 50000vs52000 ... 

 

Woah 1000th lol cool

Monterey nitro+ ati.henbury. iMacPro1.1

!!! Yesterday I asked someone who has a 6600 XT to check if all DP are working - today I figured it out - it turns out that only 1 display port + hdmi works withiMacPro1.1, and all ports work with smbios MacPro7.1

Spoiler

image.thumb.png.ba6ebdc483c7d570cf651c7f2f24ee26.png

 

Edited by viorel
Just now, ichelash said:

It’s official ventura has won the battle 😂😂 skylake intel HD 530 has refused to work @Cyberdevs

That beats me! post the EFI that you are using and I will double check the settings. At this point i need to cross examine the settings.

6 minutes ago, Cyberdevs said:

That beats me! post the EFI that you are using and I will double check the settings. At this point i need to cross examine the settings.

Here it is. Installation process went smoothly, the issue arise when in post installation I add the device properties

EFI.zip

6 minutes ago, ichelash said:

the issue arise when in post installation I add the device properties

Yes the issue is that you are not using the correct version of WhateverGreen.

I told you several times already you need a very specific build of WEG because they have rolled back the SKL-->KBL spoofing because of the "Booting into Recovery Mode" issue but in your EFI folder you are using the version of the WEG which already has that setting removed.

 

image.png

 

Replace the WhateverGreen.kext with this one and it should work.

WhateverGreen.kext.zip

  • Like 4
  • Thanks 1
  • Sad 1
20 minutes ago, miliuco said:

@viorel

Which DP and HDMI, near or far from the motherboard? Even with WhateverGreen?

DP1 which is closer to the motherboard, HDMI always works. yes Even with WhateverGreen, and D3v1L rightly noticed that something is wrong with henbury

 

20 minutes ago, miliuco said:

@viorel

Which DP and HDMI, near or far from the motherboard? Even with WhateverGreen?

Spoiler

image.thumb.png.68a3766b74b0b10006bd315d561e4777.png

 

 

Edited by viorel
  • Like 1
10 minutes ago, Cyberdevs said:

Yes the issue is that you are not using the correct version of WhateverGreen.

I told you several times already you need a very specific build of WEG because they have rolled back the SKL-->KBL spoofing because of the "Booting into Recovery Mode" issue but in your EFI folder you are using the version of the WEG which already has that setting removed.

 

image.png

 

Replace the WhateverGreen.kext with this one and it should work.

WhateverGreen.kext.zip 216.68 kB · 0 downloads

On it

  • Like 1

I am afraid that the redistribution of GitHub Actions Artifacts is never a good idea, given the fact that they are downloadable with the possession of a GitHub account.

 

Secondly, there is no such support for SKL spoofing as KBL on WhateverGreen master branch; While I did make a test, it caused problems with firmware disabling and thus was *reverted*. I apologize for the inconvenience which I brought.

 

In case of any curiosity, we are currently testing the spoofing on a separate branch of WEG; thanks @5T33Z0 for pointing it out. Now you should be able to boot in any case without the injector/codeless kext being used.

Edited by PMheart
  • Like 7

@PMheart

do you have the latest compiled version of that branch, I can't compile it and I'm too tired to troubleshoot it right now.

But if you think posting it here might cause mayhem you can send it to me via PM if that's possible.

Thanks in advance.

5 minutes ago, Cyberdevs said:

@PMheart

do you have the latest compiled version of that branch, I can't compile it and I'm too tired to troubleshoot it right now.

But if you think posting it here might cause mayhem you can send it to me via PM if that's possible.

Thanks in advance.

As I said in the previous post - It’s available on our GitHub Actions: https://github.com/acidanthera/WhateverGreen/actions?query=skl-as-kbl-13

 

This is why I was against the idea of redistribution.

  • Like 2
  • Thanks 1
2 hours ago, viorel said:

Monterey nitro+ ati.henbury. iMacPro1.1

!!! Yesterday I asked someone who has a 6600 XT to check if all DP are working - today I figured it out - it turns out that only 1 display port + hdmi works withiMacPro1.1, and all ports work with smbios MacPro7.1

  Reveal hidden contents

image.thumb.png.ba6ebdc483c7d570cf651c7f2f24ee26.png

 

 

In monterey, with SMBios iMacPro1,1  my RX6600 all ports work, (3-DP+HDMI ) and with hot plug, I just tried it.  

 

Plug and play in Monterey 😄

 

https://browser.geekbench.com/v5/compute/5003841

  • Like 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...