Jump to content
76 posts in this topic

Recommended Posts

31 minutes ago, ichelash said:

can you try and disable all wifi kexts..like shown below...and also make sure your kexts are up to date

 

Screenshot2025-11-06at13_12_06.png.82998d8bd0099de08ac792e8b622b6e6.png

 

Yes I my kexts are all up to date. Tried disabling them as you advised but no change. I am still able to boot in safe mode, but not normally. Here's the attached log:

xTcxj2Z.jpeg

4 hours ago, dorts said:

All kexts and OC has been updated,

If the UsbMap.kext was designed for Sequoia, it will not work on Tahoe.

WEG.kext version 1.7.0 causes problems on Tahoe. Similarly, Wi-Fi/BT kexts can cause problems during installation.

  • Like 3
49 minutes ago, eSaF said:

Hi clean the NvRAM and try this config.plist.

I have entered Min/MaxKernel Data for SkywalkFamily.kext and associates in your config.plist.

 

I don't know if that was the issue but it's worth a try.

Good luck.

 

PS- Remove the -amfipassbeta boot-arg it is no longer needed

 

Cheers.

config.plist.zip 7.04 kB · 5 downloads

 

Thanks for the updated file. Sadly I still encounter the same issue and it gets stuck at the same place. Any other ideas? :(

16 minutes ago, strangeron said:

If the UsbMap.kext was designed for Sequoia, it will not work on Tahoe.

WEG.kext version 1.7.0 causes problems on Tahoe. Similarly, Wi-Fi/BT kexts can cause problems during installation.

 

Usbmap.kext was updated for Tahoe in safe mode as I've read previously. If WEG.kext was an issue why would safe mode work? I did try disabling it however it would not boot either and was stuck at the same place during boot.

2 hours ago, Matgen84 said:

Hi @dorts Please complete your signature with your hardware like mine or @ichelash for example. 

Updated!

26 minutes ago, dorts said:

If WEG.kext was an issue why would safe mode work? I did try disabling it however it would not boot either and was stuck at the same place during boot.

Why wouldn't it turn on? If the problem is with the RX570, it will already be disabled in safe mode.

On 11/5/2025 at 12:44 AM, Matgen84 said:

 

@laobamac_yyds the csr-active-config value is already add to delete.

 

On my post, I'm talking about GateKeeper. I disable it with sudo spctl --global-disable and confirm in System settings (I also try --master-disable). But after each update, GateKeeper is enable by default. So apps are moving to relocated items/security/...

 

I made a lot of search and test without success. To prevent big headache, I need a solution. 🥲

Same. I also faced this issue. I searched many info for gatekeeper. But no luck. To resolve this issue, we need to gather same info. What is your mac model? I use imacpro1,1 and csr 03080000 and amfi kext.

19 hours ago, dorts said:

 

Yes I my kexts are all up to date. Tried disabling them as you advised but no change. I am still able to boot in safe mode, but not normally. Here's the attached log:

xTcxj2Z.jpeg

May be switch off VT-d?

A strange problem, I decided to perform a clean install of 25B78, but I am faced with a situation that I do not understand. The same EFI sees the disks in the already updated system, but not in the installer. I'm kind of stumped🥴

Spoiler

image.thumb.jpeg.ce71d8ab628f4902846b906748614267.jpeg

 

WhatsApp Image 2025-11-07 at 10.20.51.jpeg

  • Sad 1
28 minutes ago, ANTIKO said:

A strange problem, I decided to perform a clean install of 25B78, but I am faced with a situation that I do not understand. The same EFI sees the disks in the already updated system, but not in the installer. I'm kind of stumped🥴

  Hide contents

image.thumb.jpeg.ce71d8ab628f4902846b906748614267.jpeg

 

 

 

 

This is possibly due to a missing Lilu.kext and NVMeFix.kext for your ADATA SX8200PNP media? Check that.

13 minutes ago, spakk said:

 

This is possibly due to a missing Lilu.kext and NVMeFix.kext for your ADATA SX8200PNP media? Check that.

Thanks for the answer! but what does Lilu.kext have to do with it? he is present. NVMeFix.I don't need kext, I write that the installer doesn't see anything, although the same EFI runs 25B78 perfectly, already installed.

Spoiler

image.thumb.png.9bba2a20952c0ccf31e9e264b4bfea1b.png

 

45 minutes ago, ANTIKO said:

Thanks for the answer! but what does Lilu.kext have to do with it? he is present. NVMeFix.I don't need kext, I write that the installer doesn't see anything, although the same EFI runs 25B78 perfectly, already installed.

  Reveal hidden contents

 

This is just a guess and should be tested. NVMeFix.kext requires Lilu.kext because Lilu provides fundamental kernel patching services that NVMeFix uses. Check the kexts again after installation to pinpoint the cause more accurately.

  • Like 2
1 hour ago, ANTIKO said:

Thanks for the answer! but what does Lilu.kext have to do with it? he is present. NVMeFix.I don't need kext, I write that the installer doesn't see anything, although the same EFI runs 25B78 perfectly, already installed.

  Reveal hidden contents

 

 

15 minutes ago, eSaF said:

Hi Bro, a few things to check.

Insure all kexts are the very latest versions, UEFI/APFS/EnableJumpstart is enabled.

 

There is a possibility an errant setting could have crept into what was working before that is now giving a problem.

Compare a working config.plist with your current one to see if an unintentional change was made.

 

Good luck.

Cheers.

 

Anything is possible, so make sure to check everything, including whether AHCI mode is enabled in the BIOS. I recently made some changes to the BIOS on a running system with macOS Tahoe 26.01 and macOS Sequoia 15.7.1 to use a tool under Windows, and completely forgot to revert them.

The installed macOS systems were not affected. When I tried to install macOS 26.1 the day before yesterday, I couldn't boot into the installer. Only after a colleague in a forum mentioned the possibility of missing kext drivers did I remember the BIOS changes I had made. Once I reverted them, booting and installing macOS 26.1 worked immediately.

So never rule anything out, even if everything has been working fine before.

  • Like 1
25 minutes ago, eSaF said:

Hi Bro, a few things to check.

Insure all kexts are the very latest versions, UEFI/APFS/EnableJumpstart is enabled.

 

There is a possibility an errant setting could have crept into what was working before that is now giving a problem.

Compare a working config.plist with your current one to see if an unintentional change was made.

 

Good luck.

Cheers.

 

6 minutes ago, spakk said:

 

 

Anything is possible, so make sure to check everything, including whether AHCI mode is enabled in the BIOS. I recently made some changes to the BIOS on a running system with macOS Tahoe 26.01 and macOS Sequoia 15.7.1 to use a tool under Windows, and completely forgot to revert them.

The installed macOS systems were not affected. When I tried to install macOS 26.1 the day before yesterday, I couldn't boot into the installer. Only after a colleague in a forum mentioned the possibility of missing kext drivers did I remember the BIOS changes I had made. Once I reverted them, booting and installing macOS 26.1 worked immediately.

So never rule anything out, even if everything has been working fine before.

Everything is included, Opencore version 107, thanks anyway!

I am currently updating to 26.2 (25C5031i)

Spoiler

image.thumb.png.6533a0e4d9b51f59a241c0001f449d38.png

 

Снимок экрана 2025-11-07 в 12.22.00.png

Edited by ANTIKO
  • Like 1

Hey guys. Successfully updated to 26.1, using WEG 1.7.1d7 (and agdpmod=pikera boot-arg). The only thing I had to do was to disable BCMC in order to successfully update (or use a boot USB drive with it disabled). But in terms of update flow, everything went smoothly. 

Edited by arsradu
  • Like 1
4 hours ago, laobamac_yyds said:

Hi,friends.

Can XHCPortLimit increase the maximum number of ports to 64 on macOS Tahoe?

There is the limit of 15 ports per one hub. So if you make several hubs then you will have many ports.

The limit is because of 4 bits mask for port number 0x0F so do not use the patch to increase it.

  • Like 3
8 minutes ago, Slice said:

There is the limit of 15 ports per one hub. So if you make several hubs then you will have many ports.

The limit is because of 4 bits mask for port number 0x0F so do not use the patch to increase it.

Thank you for your reply, I understand that. So, does the option to modify AppleUSBXHCI and IOUSBHostFamily to achieve more than 15 ports support Tahoe?

  • Like 2
On 11/8/2025 at 4:29 PM, laobamac_yyds said:

Thank you for your reply, I understand that. So, does the option to modify AppleUSBXHCI and IOUSBHostFamily to achieve more than 15 ports support Tahoe?

AFAIK the 5th bit is occupied for other setting which you may loose trying to change this bit.

  • Like 2
58 minutes ago, Alan Mac said:

Mi placa base (ASRock B660M Phantom Gaming 4), según mis investigaciones, utiliza un controlador USB ASMedia, por lo que los puertos USB 3.0 solo funcionan como 2.0 en la Tahoe 26.1. ¿Alguien sabe cómo ayudarme con esto?

If you have this in Hackintool, it generates the SSDT-UIAC.aml file.

CleanShot 2025-11-12 at 12.46.42@2x.png

  • Like 1
  • 3 weeks later...
×
×
  • Create New...