Jump to content

[pre-release] macOS Tahoe

fantomas

By fantomas,
in New Releases and Updates

 Share
3741 posts in this topic

Recommended Posts

arsradu
arsradu
Posted
Posted
On 6/25/2025 at 4:30 PM, Sergey_Galan said:

There should be beautiful purple stripes, a black screen, and after a couple of seconds an apple with loading progress))) I think you need to configure the port on which your monitor is, you can see this in ioreg.

 

Hello,

 

Does anyone know what causes these purple lines upon boot on the RX580 (and probably others, too), when booting without WEG? I know it's cosmetic, I know probably nobody cares about it. But I'm just wondering. What's the cause of the issue?

  • Like 1
Sergey_Galan
Sergey_Galan
Posted
Posted
12 minutes ago, arsradu said:

 

Hello,

 

Does anyone know what causes these purple lines upon boot on the RX580 (and probably others, too), when booting without WEG? I know it's cosmetic, I know probably nobody cares about it. But I'm just wondering. What's the cause of the issue?

Hi.

I read somewhere a long time ago that purple stripes are a test of AMD card video memory, but this is not certain))). WEG treated this problem, so the stripes were not visible when using this kext.

  • Like 2
arsradu
arsradu
Posted
Posted (edited)
45 minutes ago, LockDown said:

connector-type probably. It is where weg fixes it by specifying the correct one

Then it should be possible to patch it with device properties, right...? Or is WEG doing something else here, as well?

This issue does not occur with Windows, for example. And if I remember correctly, Linux either. So I don't think it's hardware... and it seems to be MacOS specific.

I must admit I haven't tested other connectors. I'm currently on DP. But I can try HDMI just to see if it makes a difference. 

Anyway, thank you for your feedback. :)

Edited by arsradu
  • Like 2
arsradu
arsradu
Posted
Posted
28 minutes ago, Sergey_Galan said:

Hi.

I read somewhere a long time ago that purple stripes are a test of AMD card video memory, but this is not certain))). WEG treated this problem, so the stripes were not visible when using this kext.

Ok, but...why would it perform that test only on MacOS? I don't have this issue on Windows or Linux (as far as I remember). Windows for sure not, since I have it in dual-boot with MacOS. So I already confirmed that. Anyway, I was only curious.

 

arsradu
arsradu
Posted
Posted
52 minutes ago, eSaF said:

Bro your mind is delightfully active since winning the fight to install Tahoe on your machine.

I like that, I like that a lot. The fact you're asking about the process and curious about certain aspect of this macOS version proves your initial determination.

 

My personal feelings are I am kinda sad Apple has shut us out of all future versions as we won't be privy to these kind of conversations.

Asking questions from members more knowledgeable than oneself. Will the Hack Forums be a thing of the past??!! Kinda makes me wonder. :cry:

Most likely... I mean, unless someone finds a way to run it on current ARM chips from other manufacturers...yeah, I'm not sure what will happen. Definitely a very nice piece of history we all lived together. I feel quite lucky to have met you guys and brainstorm alongside you. :)) Fun, fun times, for sure. But yeah, we'll see what the future holds.

  • Like 3
deeveedee
deeveedee
Posted
Posted (edited)
14 hours ago, LockDown said:

revpatch=sbvmm should not be written in nvram. It must be in boot-args

 

Hunted me since i switched to iMac20,1 for Tahoe (I never used that command)

 

All good now 👍

Could that be a RestrictEvents bug or a problem with the way you implemented your NVRAM property?  With NVRAM property revpatch=sbvmm, I received Tahoe Beta 2 update on my hack with SMBIOS macMini8,1 

 

Also, OCLP 3.0.0 still uses the NVRAM property:

Screenshot2025-07-01at9_15_33AM.png.ab7490ce0a98a9d01f88951c0479aa58.png

 

EDIT: Be sure to include the corresponding NVRAM > Delete in OC config.plist.

Spoiler

Screenshot2025-07-01at10_52_32AM.png.fb3491f87dabc42723200ca52fa5cdff.png

 

Edited by deeveedee
  • Like 2
deeveedee
deeveedee
Posted
Posted

@Ludox If you're trying to manually install AppleHDA.kext, it's not going to be as easy as you think.  See here for a better understanding.  Best to use OCLP if you are going to install AppleHDA.

  • Like 3
Slice
Slice
Posted
Posted
7 hours ago, arsradu said:

 

Hello,

 

Does anyone know what causes these purple lines upon boot on the RX580 (and probably others, too), when booting without WEG? I know it's cosmetic, I know probably nobody cares about it. But I'm just wondering. What's the cause of the issue?

I know. This is AMDRadeonX4000.kext the procedure like checkVideoMemory. The procedure writes 0xA5A5A5A5 in some addresses in VideoMemory And this looks like purple stripes.

Than it immediately reads back and compares with original value. If OK the graphics is good.

No sense to disable this check as WhateverGreen does.

  • Like 3
  • Thanks 1
arsradu
arsradu
Posted
Posted
54 minutes ago, Slice said:

I know. This is AMDRadeonX4000.kext the procedure like checkVideoMemory. The procedure writes 0xA5A5A5A5 in some addresses in VideoMemory And this looks like purple stripes.

Than it immediately reads back and compares with original value. If OK the graphics is good.

No sense to disable this check as WhateverGreen does.

Thank you very much! All clear. :)

  • Like 1
Max.1974
Max.1974
Posted
Posted
8 hours ago, Sergey_Galan said:

Hi.

I read somewhere a long time ago that purple stripes are a test of AMD card video memory, but this is not certain))). WEG treated this problem, so the stripes were not visible when using this kext.

 

You're on the right track — purple (or magenta) stripes or artifacts on the screen can be related to GPU or VRAM (video memory) issues, and there's a bit of history connecting these types of artifacts with AMD graphics cards, especially when they're under stress, overclocked, or starting to fail. (ChatGPT) The links is forbidden some web tons here ;) 

https://controllertest.org // https://graphicscardhub.com/ 

  • Like 1
Max.1974
Max.1974
Posted
Posted (edited)
9 hours ago, naiclub said:

Hello friend, I tried to do as you suggested to turn off Hot Plug and reduce the number of SSDT to 2-3 pieces. The result is still the same.

Hello friend, I tried to do as you suggested by unplugging the DVD-ROM first, but the result is stuck at the same point.

 

P.S. (UIAC.aml, RHUB, XHCI, SSDT) I don't know how to do these things and I don't have the knowledge. Most of the time, someone else does it for me.

 

Hi @naiclub using Hackintool, with your usb ports mapping (need use USBMap available in GitHub from CorpNewT page) you can extract your UIAC. 

 

You need export in USB Menu and click on last button like print: 

 

image.thumb.png.c378d87a181185f17f4d3b83a9a212ff.png

Will extract in your Desktop 

 

SSDT-UIAC.aml

SSDT-USBX.aml

USBports.kext (you can use but for Tahoe I recommend still use USBMap.kext) 

 

 

Them if you want implement you Hardware I recommend you use @LAbyOne tool to extract all your ACPI devices: 

 

ACPIDump app 

 

 

ACPIDump.zip

 

image.thumb.png.8534c99189ca5e2d7a1d1ae963b49fd6.png

 

https://github.com/LAbyOne/ACPIDump 

 

 

After Run "All ACPI Table" you will see many ACPI tables on your Desktop. Hackintool does this too. But I used this program.

 

You need search for some SSDT like "xh_rps" and you can use it or better fine tuning, you can see my video tutorial how to formalize and edit this SSDT:

 

See that mine is SSDT-17-xh_rps14 

 

image.thumb.png.bcc65ca1298521f8755a5bca7642e98a.png

 

My video tutorial to edit some parts of SSDT (its easy):

 

Spoiler

 

 

After that you can use for boot, don't forget inject in info.plist inside of your Usb kext the  updates for macOs Tahoe ;) 

 

You can send me PM if you need my friend! Good Lucky :thumbsup_anim:

 

Edited by Max.1974
  • Like 5
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...