Jump to content
3741 posts in this topic

Recommended Posts

2 hours 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

Spoiler


image.thumb.jpeg.0f462cdec0d60047b5195bf45837e54f.jpeg 

 

 

It's funny, I've seen these errors during shutdown/sleep where Bluetoothd and WindowServer are failing to terminate cleanly.

In my case the fix was USB mapping and Device Properties input for GPU.

1 hour ago, ANTIKO said:

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!

  Reveal hidden contents

image.thumb.png.4446d9f14f0019de28c6aa099a8a59e5.png

 

If you want sound via external speakers we are using VoodooHDA which works surprisingly well.

Thanks to @Chris1111

https://github.com/chris1111/VoodooHDA-Tahoe

Edited by macky1
  • Like 1
  • Thanks 2
On 6/28/2025 at 12:11 PM, fernando.c.neves said:

Latest one... 2.4.2

 

https://dortania.github.io/builds/?product=RealtekRTL8111&viewall=true

 

Works OOB for me in OC kexts folder.

I tested the latest version on my system but for some reason the internet is very slow to load. Went back to my old trusted kext version and it is fine again, Go figure.

Well After A Lot Of Stuffing Around And Trial And Error, I Join The Elite And

Have One Clover EFI Folder Booting Sequoia AND Tahoe

Now To Fix Up Sound And Intel Wifi, Then I'll Be A Happy LITTLE Chappie

Any Pointers On Fixing Sound And Wifi Welcome

 

Edit1: Well Tahoe Boots Every Now And Again, Weird

Edited by STLVNUB
  • Like 3
5 minutes ago, STLVNUB said:

Well After A Lot Of Stuffing Around And Trial And Error, I Join The Elite And

Have One Clover EFI Folder Booting Sequoia AND Tahoe

Now To Fix Up Sound And Intel Wifi, Then I'll Be A Happy LITTLE Chappie

Any Pointers On Fixing Sound And Wifi Welcome

https://github.com/chris1111/VoodooHDA-Tahoe

  • Like 1
1 hour ago, STLVNUB said:

Well After A Lot Of Stuffing Around And Trial And Error, I Join The Elite And

Have One Clover EFI Folder Booting Sequoia AND Tahoe

Now To Fix Up Sound And Intel Wifi, Then I'll Be A Happy LITTLE Chappie

Any Pointers On Fixing Sound And Wifi Welcome

Edit1: Well That Was Short Lived, Booted Once Then Nothing, Weird

Edit2: Well It Boots Again, Needs To Be Shut Down Too Boot

 

1 hour ago, surenmunoo said:

Thanks, Will Come In Handy IF I Can Boot Again

Edited by STLVNUB
11 minutes ago, STLVNUB said:

Well After A Lot Of Stuffing Around And Trial And Error, I Join The Elite And

Have One Clover EFI Folder Booting Sequoia AND Tahoe

Now To Fix Up Sound And Intel Wifi, Then I'll Be A Happy LITTLE Chappie

Any Pointers On Fixing Sound And Wifi Welcome

For most sound cards, it is recommended to choose OCLP Mod and AppleALC to use the AppleHDA driver for better performance. Why choose VoodooHDA when SIP is lost in response?😅

3 hours ago, surenmunoo said:

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.

😭Well, GPT didn't provide any useful advice

  • Like 1
  • Haha 1
7 minutes ago, laobamac_yyds said:

For most sound cards, it is recommended to choose OCLP Mod and AppleALC to use the AppleHDA driver for better performance. Why choose VoodooHDA when SIP is lost in response?😅

😭Well, GPT didn't provide any useful advice

Speaking for me I am using VoodooHDA as a stop gap until OCLP is released with AppleALC and hopefully Wifi patched.  Your forked version is excellent but I have been using OCLP for a long time and my config.plist is set up for it. Just my 2 1/2 cents worth.

  • Like 1
  • Confused 2
2 hours ago, eSaF said:

Sorry Pal but your post makes absolutely no sense.

The only difference between OCLP and this Forked version are:

1. OLCP-Mod is in the Chinese language so may make navigating the app difficult (but if you're a regular user of OCLP, you instinctively know where to click in the Mod version).

2. The other difference is it brings back the Audio lost in the release of Beta 2.

 

You are quite entitled to use the Mod version or not to use it.

What you are not entitled to do is to rubbish the effort of a Developer with negative remarks about their contribution that was gratefully received and used by countless members.

I wish I had a fraction of this young person's knowledge of development and software reverse engineering.

Read this Developers Bio and maybe you'll just about understand.

 

This is also my 2 cents.

Cheers.

How can I put it delicately I prefer to support OCLP. Each to their own I suppose. And I sincerely apologize if I affended anybody which was not my intention. The developer is excellent and I thank him for his contributions.

Edited by macky1
  • Like 2

After struggling for about 4 weeks at last my ASUS PRIME Z690-P D4 Hackintosh can boot Tahoe beta 2 with RX570 now !

No such issues of Finder, Firefox, LucyRTL8125Ethernet or Audio output.

The only problem waiting for fix is unable to wake-up from S3 sleep.

[Edit]

It seems FL1100 USB 3.0 adapter may interfere its power management of MB.

After removal of it and modified my config-new.plist it can wake-up from S3 sleep now !

Screenshot 2025-06-29 at 15.04.09.png

Screenshot 2025-06-29 at 15.04.29.png

Screenshot 2025-06-29 at 15.04.47.png

Screenshot 2025-06-29 at 15.35.57.png

Screenshot 2025-06-29 at 15.42.25.png

config.plist

config-new.plist

Screenshot 2025-07-01 at 09.27.48.png

 

Edited by jsl
  • Like 7

Good morning to all,

Tried your EFI @Anto65 that I'll appreciate, and it don't work, stops at "kextlog: Loading Pageable Kc from file /system7library/kernelcollections/basesystemkernelextension.kc.

tried to the EFI from @jsl, and it stops in the same line.

grrrrrrrr

  • Like 1
  • Confused 1
  • Sad 1

@eSaF Following your suggestion changed from RX 570 to iGPU graphics in the bIos and disabled WhateverGreen, and it stops " In Memory Stackshot Succeed ** Bytes traced 65903 (uncompressed 164432)

 

  • Like 1
  • Sad 1
6 hours ago, ANTIKO said:

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!

  Reveal hidden contents

image.thumb.png.4446d9f14f0019de28c6aa099a8a59e5.png

 

 

👏 👏 👏

I only have active ALC, IntelMausi, Lilu, restrictedevents, usb map, and whatever green disabled in config.plis.

I think I can't boot if I disable one more

 

@Anto65 tried booting with your EFI and although I made the changes in the bios, it stops in the same place KC's

Edited by MorenoAv
  • Like 1
  • Sad 1

I use RX 570 Installed directly without any problems. Just disable WhateverGreen it can then be started and installed macOS Tahoe. If the startup process is in the PCI or AppleKeyStore stop at, try adding-amd_no_dgpu_accel add to startup parameters.

 

 

 

WhateverGreen will only cause a startup failure during installation, when you start "Macintosh HD" (your installation target name, after the installation process is complete), you need to enable it for your RX570 to work properly.

 

 

 

Ps: you said that your EFI stopped and crashed at EB, which was not caused by GPU at all cause, you should check something else, like the OC version, kext Version...

Edited by laobamac_yyds
  • Like 5
Guest
This topic is now closed to further replies.
×
×
  • Create New...