Jump to content
3741 posts in this topic

Recommended Posts

11 hours ago, Cyberdevs said:

I just did a clean install of macOS Tahoe on my Z270 rig without WEG and only using device properties for my RX 580, the installation went smoothly except for the purple lines when the GPU being initialized during boot's second stage which was expected.

I attached two config.plist files for RX 580/590 and TX 6800/6800XT GPUs if any one is interested.

Just copy the DeviceProperties to your config and give it a try,

 

Let me know how it works.

config-rx580.plist 2.9 kB · 29 downloads 6800XT - config.plist 1.65 kB · 15 downloads

I have been using this in my device properties for a while with my RX 6800 XT without agdpmod=pikera in the boot-args

 

image.png.496405105920024ab8ce7641de305827.png

Your,s has more information. will it. improve. performance using your file?

  • Like 3
3 minutes ago, BALDY_MAN said:

I have been using this in my device properties for a while with my RX 6800 XT without agdpmod=pikera in the boot-args

 

image.png.496405105920024ab8ce7641de305827.png

Your,s has more information. will it. improve. performance using your file?

When you use Device Properties you don't need the bootarg, I must have forgotten to remove it.

You can test and see if it improves the performance but I don't think it changes much.

  • Like 2

I fork and modified weg, boot Installer and Recovery Mode no longer need to be disabled WhateverGreen.

 

https://github.com/laobamac/WhateverGreen

 

You need to add a new boot arg. How and what to add README. It will not affect normal startup, so add this parameter all the time.

 

IMG_20250914_141426.thumb.jpg.cbacda4f2a31dbb868d76484a5e86ba0.jpg

 

IMG_20250914_141450.thumb.jpg.c3fad691b49f1faa2e298dd28559eb32.jpg

 

----EDITED-9.14-19:28Image_1757849300080.thumb.jpg.47b002931c6ae5cc4150b95672bf0f21.jpg---

It works well too on OTA!

Update macOS no longer need to disable WEG.

 

Edited by laobamac_yyds
  • Like 17
  • Thanks 2
16 hours ago, Cyberdevs said:

I just did a clean install of macOS Tahoe on my Z270 rig without WEG and only using device properties for my RX 580, the installation went smoothly except for the purple lines when the GPU being initialized during boot's second stage which was expected.

I attached two config.plist files for RX 580/590 and TX 6800/6800XT GPUs if any one is interested.

Just copy the DeviceProperties to your config and give it a try,

 

Let me know how it works.

config-rx580.plist 2.9 kB · 45 downloads 6800XT - config.plist 1.65 kB · 25 downloads

 

Thanks @Cyberdevs 

 

Long time ago, @Slice upload a kext patching to solve violet strips for Clover. I don't know if it's available for Opencore and macOS Tahoe. Let me know. Please.
 

Spoiler

image.png.4746d96c98c89e3ac86ec5caa141a55e.png

 

Edited by Matgen84
  • Like 7

Minor observation, but it indicates an improvement in Tahoe... closing IORegistryExplorer (versions 2 and 3) would generate an error for me when running in Tahoe Betas.  With Tahoe RC1, I no longer see the error.  Each improvement in Tahoe makes this final Intel version of macOS a fitting send-off for Intel.

 

I can't help but think that if Intel had kept pace with TSMC and didn't keep delaying technology releases, we'd have had a few more years.

  • Like 2
  • Thanks 1
9 minutes ago, Matgen84 said:

 

Thanks @Cyberdevs 

 

Long time ago, @Slice upload a kext patching to solve violet strips for Clover. I don't know if it's available for Opencore and macOS Tahoe. Let me know. Please.
 

  Hide contents

image.png.4746d96c98c89e3ac86ec5caa141a55e.png

 

Thanks for sharing that I will test it and see if it works on OpenCore as well.

  • Like 1
7 hours ago, laobamac_yyds said:

I fork and modified weg, boot Installer and Recovery Mode no longer need to be disabled WhateverGreen.

 

https://github.com/laobamac/WhateverGreen

 

You need to add a new boot arg. How and what to add README.

 

 

@laobamac_yyds, many thanks for this new exciting achievement. I was studying the README and started to translate everything. But somehow I got lost. The boot argument we need to add is wegdetectmode=norec? I mean you also mention a few other options. Maybe you can shortly comment on this? 👍

1 minute ago, KGP-iMacPro said:

 

 

@laobamac_yyds非常感谢你带来的这项激动人心的新成就。我正在研究 README 文件,并开始翻译所有内容。但不知怎么的,我迷路了。我们需要添加的启动参数是wegdetectmode=norec?我的意思是,你还提到了其他几个选项。也许你可以简单评论一下?  👍

WhateverGreen Boot Arguments:

 

wegdetectmode=ignore - Ignore all checks, always load WhateverGreen

wegdetectmode=force - Skip loading if system info not found (safe mode)

wegdetectmode=norec - Automatically skip loading in recovery mode

 

Combinations:

wegdetectmode=ignore,norec - Ignore recovery detection, always load

wegdetectmode=force,norec - Skip if no info or in recovery mode

 

Detection Logic:

• Normal system (boot.efi) - Always load

• Recovery mode (bootbase.efi) - Depends on norec/ignore settings

• Unable to detect - Depends on force setting

 

Priority: ignore > norec > force

 

 

---------------

 

In most cases, just add wegdetectmode=norec, this will be in macOS Tahoe boot recovery mode/installer and OTA correctly on the. The other parameters are for debugging purposes only.

  • Like 10
  • Thanks 1
1 hour ago, laobamac_yyds said:

In most cases, just add wegdetectmode=norec, this will be in macOS Tahoe boot recovery mode/installer and OTA correctly on the. The other parameters are for debugging purposes only.

Thank you @laobamac_yyds for developing this weg solution. So I can add this boot arg when loading the weg version in your branch to boot Tahoe normally and get OTA updates/run full installer or boot Mac recovery. If I read your post well, I can keep this boot arg all the time, right?

Edited by jlrycm
28 minutes ago, jlrycm said:

谢谢@laobamac_yyds 感谢您开发这个 weg 解决方案。这样我就可以在加载您分支中的 weg 版本时添加这个启动参数,以便正常启动 Tahoe 并获取 OTA 更新/运行完整安装程序或启动 Mac Recovery。如果我仔细阅读了您的帖子,我可以一直保留这个启动参数,对吗?

Yes, it can be kept indefinitely. This parameter will not have any impact on the normal startup of the system

  • Like 4
5 hours ago, Matgen84 said:

 

Gracias@Cyberdevs 

 

Hace mucho tiempo,@Rebanada Sube un parche de kext para solucionar las franjas violetas en Clover. No sé si está disponible para Opencore y macOS Tahoe. Avísame, por favor.
 

  Revelar contenidos ocultos

image.png.4746d96c98c89e3ac86ec5caa141a55e.png

 

One question... do you use your monitor via HDMI?
If so, can you set it to 60 Hz using your config.plist for the RX 580 GPUs?

16 hours ago, laobamac_yyds said:

I fork and modified weg, boot Installer and Recovery Mode no longer need to be disabled WhateverGreen.

 

https://github.com/laobamac/WhateverGreen

 

You need to add a new boot arg. How and what to add README. It will not affect normal startup, so add this parameter all the time.

 

IMG_20250914_141426.thumb.jpg.cbacda4f2a31dbb868d76484a5e86ba0.jpg

 

IMG_20250914_141450.thumb.jpg.c3fad691b49f1faa2e298dd28559eb32.jpg

 

----EDITED-9.14-19:28Image_1757849300080.thumb.jpg.47b002931c6ae5cc4150b95672bf0f21.jpg---

It works well too on OTA!

Update macOS no longer need to disable WEG.

 

It would be nice if you would please read your private messages and maybe reply 🙂

@AlfredoM Here's a little tip to help you with public forum etiquette:  Private Messages are private.  The recipient of a PM has the right to respond (or not respond) in their own time.  Pressuring them with a public post is inconsiderate.  You can do better.

  • Like 4
3 minutes ago, deeveedee said:

@AlfredoM Here's a little tip to help you with public forum etiquette:  Private Messages are private.  The recipient of a PM has the right to respond (or not respond) in their own time.  Pressuring them with a public post is inconsiderate.  You can do better.

Hey, @deeveedee, what do you mean by "putting pressure on me?"
That's not what I meant. I just wanted to point out that I sent him a private message; maybe he didn't notice.
Now, no one is more Catholic than the Pope himself 🙂

Edited by AlfredoM
On 9/13/2025 at 7:40 PM, Cyberdevs said:

I just did a clean install of macOS Tahoe on my Z270 rig without WEG and only using device properties for my RX 580, the installation went smoothly except for the purple lines when the GPU being initialized during boot's second stage which was expected.

I attached two config.plist files for RX 580/590 and TX 6800/6800XT GPUs if any one is interested.

Just copy the DeviceProperties to your config and give it a try,

 

Let me know how it works.

config-rx580.plist 2.9 kB · 53 downloads 6800XT - config.plist 1.65 kB · 29 downloads

Hi I would like to add the rx580. plist to my Config. I'm not sure how to do this or the best way to do it. Any chance of some instructions?

39 minutes ago, johnnyl said:

Hi I would like to add the rx580. plist to my Config. I'm not sure how to do this or the best way to do it. Any chance of some instructions?

Hi,

You can either open both configs in TextEdit and copy/paste the following section under device properties:

    <dict>
    <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
    <dict>    <key>hda-gfx</key>
    <string>onboard-1</string>    <key>device-id</key>
    <data>32cAAA==</data>    <key>ATY,EnableHardwareDRM</key>
    <data>AQAAAA==</data>    <key>ATY,EnableMSAA</key>
    <data>AQAAAA==</data>    <key>@3,connector-type</key>
    <data>AAQAAA==</data>    <key>PP_DisablePowerContainment</key>
    <data>AQAAAA==</data>    <key>ATY,Copyright</key>
    <string>Copyright AMD Inc. All Rights Reserved. 2005-2016</string>    <key>ATY,EnableMetalPerformance</key>
    <data>AQAAAA==</data>    <key>ATY,EnableHDR</key>
    <data>AQAAAA==</data>    <key>model</key>
    <string>RX 580</string>    <key>vendor-id</key>
    <data>AhA=</data>    <key>CAIL,CAIL_EnableVCEHWAcceleration</key>
    <data>AQAAAA==</data>    <key>ATY,MetalMaxCommandBuffers</key>
    <data>/////w==</data>    <key>ATY,EFIVersion</key>
    <string>113-4E353BU-214</string>    <key>PP_ActivityTarget</key>
    <data>/////w==</data>    <key>ATY,Card#</key>
    <string>113-4E353BU-O4E</string>    <key>@0,connector-type</key>
    <data>AAgAAA==</data>    <key>@2,connector-type</key>
    <data>AAQDAw==</data>    <key>CAIL,CAIL_EnableUVDHWAcceleration</key>
    <data>AQAAAA==</data>    <key>AAPL,slot-name</key>
    <string>Slot-1</string>    <key>device_type</key>
    <string>ATY,OrinocoParent</string>    <key>ATY,MemClock</key>
    <data>/////w==</data>    <key>ATY,RefreshRate</key>
    <data>AACwAA==</data>    <key>ATY,EnableAsyncCompute</key>
    <data>AQAAAA==</data>    <key>ATY,EnablePolarisGeometry</key>
    <data>AQAAAA==</data>    <key>ATY,MemoryBandwidth</key>
    <data>/////w==</data>    <key>shiki-id</key>
    <data>39cAAA==</data>    <key>PP_EnableHighPerformanceMode</key>
    <data>AQAAAA==</data>    <key>PP_EnableBoostClocks</key>
    <data>AQAAAA==</data>    <key>ATY,EnableComputeShaders</key>
    <data>AQAAAA==</data>    <key>CAIL,CAIL_EnableComputeAcceleration</key>
    <data>AQAAAA==</data>    <key>CFG,CFG_FB_LIMIT</key>
    <data>CAAAAA==</data>    <key>@1,connector-type</key>
    <data>AAgAAA==</data>    <key>AAPL,boot-display</key>
    <data>AQ==</data>
    </dict>

or you can open both your original config and the one I posted above with OpenCore Configurator and under the device properties right click on PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) and copy the value and paste it in your config.plist.

  • Like 6
2 hours ago, Cyberdevs said:

Hi,

You can either open both configs in TextEdit and copy/paste the following section under device properties:

    <dict>
    <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
    <dict>    <key>hda-gfx</key>
    <string>onboard-1</string>    <key>device-id</key>
    <data>32cAAA==</data>    <key>ATY,EnableHardwareDRM</key>
    <data>AQAAAA==</data>    <key>ATY,EnableMSAA</key>
    <data>AQAAAA==</data>    <key>@3,connector-type</key>
    <data>AAQAAA==</data>    <key>PP_DisablePowerContainment</key>
    <data>AQAAAA==</data>    <key>ATY,Copyright</key>
    <string>Copyright AMD Inc. All Rights Reserved. 2005-2016</string>    <key>ATY,EnableMetalPerformance</key>
    <data>AQAAAA==</data>    <key>ATY,EnableHDR</key>
    <data>AQAAAA==</data>    <key>model</key>
    <string>RX 580</string>    <key>vendor-id</key>
    <data>AhA=</data>    <key>CAIL,CAIL_EnableVCEHWAcceleration</key>
    <data>AQAAAA==</data>    <key>ATY,MetalMaxCommandBuffers</key>
    <data>/////w==</data>    <key>ATY,EFIVersion</key>
    <string>113-4E353BU-214</string>    <key>PP_ActivityTarget</key>
    <data>/////w==</data>    <key>ATY,Card#</key>
    <string>113-4E353BU-O4E</string>    <key>@0,connector-type</key>
    <data>AAgAAA==</data>    <key>@2,connector-type</key>
    <data>AAQDAw==</data>    <key>CAIL,CAIL_EnableUVDHWAcceleration</key>
    <data>AQAAAA==</data>    <key>AAPL,slot-name</key>
    <string>Slot-1</string>    <key>device_type</key>
    <string>ATY,OrinocoParent</string>    <key>ATY,MemClock</key>
    <data>/////w==</data>    <key>ATY,RefreshRate</key>
    <data>AACwAA==</data>    <key>ATY,EnableAsyncCompute</key>
    <data>AQAAAA==</data>    <key>ATY,EnablePolarisGeometry</key>
    <data>AQAAAA==</data>    <key>ATY,MemoryBandwidth</key>
    <data>/////w==</data>    <key>shiki-id</key>
    <data>39cAAA==</data>    <key>PP_EnableHighPerformanceMode</key>
    <data>AQAAAA==</data>    <key>PP_EnableBoostClocks</key>
    <data>AQAAAA==</data>    <key>ATY,EnableComputeShaders</key>
    <data>AQAAAA==</data>    <key>CAIL,CAIL_EnableComputeAcceleration</key>
    <data>AQAAAA==</data>    <key>CFG,CFG_FB_LIMIT</key>
    <data>CAAAAA==</data>    <key>@1,connector-type</key>
    <data>AAgAAA==</data>    <key>AAPL,boot-display</key>
    <data>AQ==</data>
    </dict>

or you can open both your original config and the one I posted above with OpenCore Configurator and under the device properties right click on PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) and copy the value and paste it in your config.plist.

Does this addition to the config mean you can remove WEG, when I added it to my config and set WEG to false my hack booted to a black screen

have I missed something 

my config only has the  audio in device properties 

11 minutes ago, gsxb said:

Does this addition to the config mean you can remove WEG, when I added it to my config and set WEG to false my hack booted to a black screen

have I missed something 

my config only has the  audio in device properties 

Yes you can remove weg and the boor args.

just make sure the device path is correct. You can also use it with weg but having both device properties and weg enabled serves no purpose.

  • Like 1

macOS 26 Tahoe Beta 9 USB Tests

1. -wegdetectmode=force,norec System stopped on both computers, NEW and OLD:

 

2. -wegdetectmode=ignore,force Restarts when the screen goes black and the graphics card is activated on both computers.

 

3. -wegdetectmode=norec The USB beta 9 installer appears perfectly.

 

Therefore, when the beta is released today, I will switch from Sequoia to the official Tahoe.

Edited by kaoskinkae
  • Like 3
41 minutes ago, Cyberdevs said:

Yes you can remove weg and the boor args.

just make sure the device path is correct. You can also use it with weg but having both device properties and weg enabled serves no purpose.

Am I correct in thinking that the device path for my Hack will be available in Hackintool 

  • Like 1
14 hours ago, HmO said:

As far as I understand this kext is only for Tahoe?

Yes. However, WEG+norec doesn't cause any problems for Ventura and Sequoia either. I use the same EFI folder for all three systems.

  • Like 2
  • Thanks 1
4 hours ago, Cyberdevs said:

Hi,

You can either open both configs in TextEdit and copy/paste the following section under device properties:

    <dict>
    <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
    <dict>    <key>hda-gfx</key>
    <string>onboard-1</string>    <key>device-id</key>
    <data>32cAAA==</data>    <key>ATY,EnableHardwareDRM</key>
    <data>AQAAAA==</data>    <key>ATY,EnableMSAA</key>
    <data>AQAAAA==</data>    <key>@3,connector-type</key>
    <data>AAQAAA==</data>    <key>PP_DisablePowerContainment</key>
    <data>AQAAAA==</data>    <key>ATY,Copyright</key>
    <string>Copyright AMD Inc. All Rights Reserved. 2005-2016</string>    <key>ATY,EnableMetalPerformance</key>
    <data>AQAAAA==</data>    <key>ATY,EnableHDR</key>
    <data>AQAAAA==</data>    <key>model</key>
    <string>RX 580</string>    <key>vendor-id</key>
    <data>AhA=</data>    <key>CAIL,CAIL_EnableVCEHWAcceleration</key>
    <data>AQAAAA==</data>    <key>ATY,MetalMaxCommandBuffers</key>
    <data>/////w==</data>    <key>ATY,EFIVersion</key>
    <string>113-4E353BU-214</string>    <key>PP_ActivityTarget</key>
    <data>/////w==</data>    <key>ATY,Card#</key>
    <string>113-4E353BU-O4E</string>    <key>@0,connector-type</key>
    <data>AAgAAA==</data>    <key>@2,connector-type</key>
    <data>AAQDAw==</data>    <key>CAIL,CAIL_EnableUVDHWAcceleration</key>
    <data>AQAAAA==</data>    <key>AAPL,slot-name</key>
    <string>Slot-1</string>    <key>device_type</key>
    <string>ATY,OrinocoParent</string>    <key>ATY,MemClock</key>
    <data>/////w==</data>    <key>ATY,RefreshRate</key>
    <data>AACwAA==</data>    <key>ATY,EnableAsyncCompute</key>
    <data>AQAAAA==</data>    <key>ATY,EnablePolarisGeometry</key>
    <data>AQAAAA==</data>    <key>ATY,MemoryBandwidth</key>
    <data>/////w==</data>    <key>shiki-id</key>
    <data>39cAAA==</data>    <key>PP_EnableHighPerformanceMode</key>
    <data>AQAAAA==</data>    <key>PP_EnableBoostClocks</key>
    <data>AQAAAA==</data>    <key>ATY,EnableComputeShaders</key>
    <data>AQAAAA==</data>    <key>CAIL,CAIL_EnableComputeAcceleration</key>
    <data>AQAAAA==</data>    <key>CFG,CFG_FB_LIMIT</key>
    <data>CAAAAA==</data>    <key>@1,connector-type</key>
    <data>AAgAAA==</data>    <key>AAPL,boot-display</key>
    <data>AQ==</data>
    </dict>

or you can open both your original config and the one I posted above with OpenCore Configurator and under the device properties right click on PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) and copy the value and paste it in your config.plist.

Can this setting be used with the RX560?
I'm using the default settings shown in the system information and can boot both in recovery mode and normal mode, but I'm having a slight issue with the purple bar.

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