Jump to content

[pre-release] macOS Tahoe

fantomas

By fantomas,
in New Releases and Updates

 Share
3741 posts in this topic

Recommended Posts

macky1
macky1
Posted
Posted
2 hours ago, eSaF said:

.For me, this Tahoe is a strange entity.

I still can't make an installer USB configured with the RX580 as primary Graphics.

 

It has to be the Integrated CPU UDH 630 Graphics without the WEG.kext enabled. 

I will try again with the next released Beta.

I have configured a USB EFI Installer and used RX580 as the primary Graphics. 

Additionally I have initiated an Upgrade for Tahoe from the Desktop and  separately also via a FULL Install from the OC boot menu

by erasing the drive clean and installing a fresh copy of Tahoe. ie. setup as Headless mode in config.plist

 

Firstly in bios I set these parameters.

PEG set as primary.

Mirror Display ON

4g Graphics OFF

The minimal kext I use are Lilu, NVMeFix, REALTEKTL8111 (Ethernet for my System), RestrictEvents, USBPort, VirtualSMC, WatereverGreen.

The rest of the settings in EFI would be configured for your particular  motherboard/video card combo.

Oh bye the way this is for my Intel System ASUS PRIME Z370-P

Hope this helps.

  • Like 3
macky1
macky1
Posted
Posted (edited)
7 minutes ago, strangeron said:

Tried installing on RX590. Installation took a long time because I had to use HDD with a USB SATA cable. Just removed WEG and installation was successful.

Yeah unfortunately it is a WIP. Every system is different and what works for one system doesn’t work for another. And sometimes you get lucky and find the right combo that works.😀

Edited by macky1
  • Like 2
ANTIKO
ANTIKO
Posted
Posted
5 hours ago, Alpha22 said:

try config.plist, do not use WhateverGreen.kext

from the signature you use I5 13660KF from the config.plist it is marked as I9

 

config.plist.zip 6.95 kB · 2 downloads

Brother! You saved me! 😂, let's see what comes of this🤫, I saw the light!

IMG_5686.jpeg

  • Like 3
  • Haha 3
macky1
macky1
Posted
Posted
4 minutes ago, eSaF said:

Trust me Bro, I have tried every which way to clean install with the RX580 as primary.

It just won't happen, the only way is with the Integrated Graphics then change over to the RX580 after the installation is finished, also making the change in the BIOS.

 

Setting WEG disabled gives purple lines and a black screen on the initial boot-up.

With WEG enabled, the boot hangs at KC: blah, blah, blah.

Yeah sorry to hear that. Every system is different and sometimes you get lucky & find the right combo that works.

  • Like 1
MorenoAv
MorenoAv
Posted
Posted (edited)

And now I understand why I can't install Tahoe with you EFi @eSaF, it boots and then it gives me a black screen.

the last try results in the picture below ...

IMG_0924.jpg

Edited by MorenoAv
  • Like 1
  • Confused 1
  • Sad 2
miliuco
miliuco
Posted
Posted

 

@eSaF

 

The pic you posted in this comment is practically the same as what I have; everything is the same except for MaxKernel, where 24.20.00 and 24.99.99 have the same functionality.


Since I have an RX 6600 XT and MacPro 7.1 SMBIOS,I don't have the issue you're referring to with the USB installer. In my case, the same BIOS settings, hardware and EFI work for both the USB installer and Tahoe already installed.

  • Like 2
robi62
robi62
Posted
Posted

@Stefanalmare Hi you were the only one to offer any help and I really appreciate that ; others did not offer anything at all 😳

Anyway the solution was really easy no voodoohda fakepci etc,etc

I set up opencore simplify efi where it told me to use 99 for my audio which I have never seen that and all working .

So I just changed my efi with that I am good Time for bed now 😊😊

  • Like 1
macky1
macky1
Posted
Posted
17 minutes ago, ANTIKO said:

Thanks for your help! Another question - Tahoe encrypted my system, and somewhere here there was a way to solve this problem (it's inconvenient to search from a phone), please give me a link.

IMG_5689.jpeg

IMG_5690.jpeg

I tried to find the page but couldnt.

Look for fernando.c.neves

 

Anto65
Anto65
Posted
Posted (edited)
11 hours ago, MorenoAv said:

Good day to all,

Yesterday pissed at the lack of network and my inability to make it work I decide to reinstall Tahoe, at the reboot I'm confronted with the inability of the general EFI from Olaria to boot the installer. Ater that I have used all EFI's that are laying around to try and install Tahoe, with no success.

i made and EFI from scratch and it boots the system until it arrives at this part and the installion stops.

Could anyone see the above picture and point me in the right direction.

thanks

IMG_0922.jpg

EFI.zip 5.41 MB · 11 downloads

 

Hard without VirtualSMC.kext

 

Spoiler

 

  Screenshot2025-06-29alle03_13_20.png.180f42d8e1a57f025cebdfbc4fe39879.png

 

Try EFI.zip

 

 

Edited by Anto65
  • Like 3
Anto65
Anto65
Posted
Posted (edited)
48 minutes ago, ANTIKO said:

Thanks for your help! Another question - Tahoe encrypted my system, and somewhere here there was a way to solve this problem (it's inconvenient to search from a phone), please give me a link.

IMG_5689.jpeg

IMG_5690.jpeg

 

https://www.ichi.co.uk/blog/removing-file-vault-from-internet-recovery-console

 

I voluntarily activated FileVault to see if I could unlock it from Recovery... it works (As a precaution I had saved the access key, in case I failed 🙂 ) 

 

Image

https://limewire.com/d/f4k3o#82hDRa1wQ1

Edited by Anto65
  • Like 5
ANTIKO
ANTIKO
Posted
Posted
Just now, Anto65 said:

From your picture you posted

 

" If you have trouble entering your password, turn off your Mac by pressing and holding the power button.

 

Then press the button again to boot the computer into Recovery OS mode.

 

Shutdown

 

Restart "  🤷‍♂️
 

Yes, thank you very much! I figured it out😂

  • Haha 2
laobamac_yyds
laobamac_yyds
Posted
Posted (edited)

 I compiled a metallib and use Metal.framework(13.2.1-24),but timeout for WindowsServer🥶

It boot well in the whole process,but cause timeout and reboot at when about to enter the user interface of the system.....😖

Do you have any ideas? Attached is the list of metallib and patches I compiled.

https://drive.google.com/file/d/1D28Q5VuWs5CqL3UTdnCZmvoX3jX9cSNB/view?usp=share_link

and the patch_dict https://drive.google.com/file/d/1J0cgQ82vvYAUkEzwFR2fE1vp9n61Yw_M/view?usp=share_link

 

ps:trying to fix Kepler on Tahoe

image.thumb.jpeg.0f462cdec0d60047b5195bf45837e54f.jpeg 

Edited by laobamac_yyds
  • Like 2
ANTIKO
ANTIKO
Posted
Posted

To sum up, the USB ports are working, sleep is working, and there is sound via DP on the monitor. FileVault disabled it via recovery mode. As expected, WI-FI does not work)).  Thank you all so much for your help! You are the best!

Spoiler

image.thumb.png.4446d9f14f0019de28c6aa099a8a59e5.png

 

  • Like 3
surenmunoo
surenmunoo
Posted
Posted
1 hour ago, laobamac_yyds said:

 I compiled a metallib and use Metal.framework(13.2.1-24),but timeout for WindowsServer🥶

It boot well in the whole process,but cause timeout and reboot at when about to enter the user interface of the system.....😖

Do you have any ideas? Attached is the list of metallib and patches I compiled.

https://drive.google.com/file/d/1D28Q5VuWs5CqL3UTdnCZmvoX3jX9cSNB/view?usp=share_link

and the patch_dict https://drive.google.com/file/d/1J0cgQ82vvYAUkEzwFR2fE1vp9n61Yw_M/view?usp=share_link

 

ps:trying to fix Kepler on Tahoe

 

The below is what ChatGPT says if its any help.

 

This issue typically means:

  • WindowsServer fails to start (often due to broken GPU acceleration).

  • You're dropped into launchd’s restart loop because the graphical interface cannot initialize.

🧠 Key Observations from the Screenshot:

  • Messages like: 

     
    makefile
    CopyEdit
    (Warning): Lingering coalition: 166 (com.apple.WindowServer)

    strongly indicate WindowServer crash or stall, confirming your suspicion.

🎯 Causes Specific to Kepler on Sequoia:

  1. Kepler is officially unsupported in macOS Sequoia (macOS 15).

    • Apple removed support for non-Metal 3.x and older shaders.

    • Even with a patched metallib, you may also need binary patches to:

      • Skip Metal device checks.

      • Allow older GPU families.

      • Prevent system daemons from crashing on unsupported features.

  2. Your metallib may not be compatible with the full Metal API expectations in Sequoia.

    • If shaders or Metal functions are missing or incorrect, WindowServer may crash or hang during rendering setup.

  3. Missing GPUDevicePolicy patches — these are common when AppleGraphicsControl.kext prevents acceleration.

    • On older macOS versions we use agdpmod=pikera or similar boot-args.

    • You may need similar tricks (but patched for Sequoia).

✅ Suggestions:

1. Check GPU Acceleration Logs

Use -v debug=0x100 keepsyms=1 (you probably already are) and look earlier in the boot log:

  • Do you see messages like: 

     
    makefile
    CopyEdit
    IOAccelerator: Metal device not supported

    or 

     
    lua
    CopyEdit
    GFX firmware load failed

    or 

     
    makefile
    CopyEdit
    IOService: matching failed for AppleMGPUPowerControl

These will confirm failure to load GPU acceleration.

2. Try Headless Boot to Disable WindowServer

Try booting with: 

 
bash
CopyEdit
nv_disable=1 -v debug=0x100 keepsyms=1

This disables Kepler acceleration to test if system boots without starting WindowServer.

If it boots: you have a working system minus graphics acceleration. That confirms it's purely GPU related.

3. Add/Check These Kernel Patches:

  • IOAcceleratorFamily2 patch to allow unsupported GPUs.

  • Patch AppleMGPUPowerControl or AGDC to skip model checks.

  • Consider applying OCLP-like patch sets manually if using a Hackintosh.

4. Try Lilu + WhateverGreen (latest betas):

Even if they're not designed for Kepler on macOS 15, they:

  • Inject missing framebuffer properties.

  • Bypass some AppleGPU policies.

  • Work better with patched metal libraries.

Also use boot-args: 

 
diff
CopyEdit
-wegbeta -lilubetaall gfxrst=1 agdpmod=pikera

5. Use a Patched/Stub WindowServer (for debugging)

In some cases, you can replace /System/Library/CoreServices/WindowServer with a stub (like sleep 60) just to confirm booting — not usable for real work but helps confirm it's the cause.

🔗 Resources:

If you can share:

  • Your metallib

  • Any OpenCore patches/kexts you're applying

  • IORegistry dump (from another machine)
    … I can help analyze what’s missing.

  • Like 1
Irish_Man
Irish_Man
Posted
Posted
2 hours ago, Anto65 said:

 

https://www.ichi.co.uk/blog/removing-file-vault-from-internet-recovery-console

 

I voluntarily activated FileVault to see if I could unlock it from Recovery... it works (As a precaution I had saved the access key, in case I failed 🙂 ) 

 

Image

https://limewire.com/d/f4k3o#82hDRa1wQ1

I tested it also. But I didn't use Recovery. I just booted to Sequoia and did it from there. 

I was curious if Recovery is a MUST. It looks it's not.

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