Jump to content

[Pre Release] macOS Tahoe 26.1

Anto65

By Anto65,
in New Releases and Updates

 Share
246 posts in this topic

Recommended Posts

arsradu
arsradu
Posted
Posted (edited)
29 minutes ago, KGP-iMacPro said:

 

I am using boot flag agdpmod=pikera since SMBIOS iMacPro1,1 and now also with MacPro7,1.. 😉

Well...what we've learned today:

  1. AppleBCMWLANCompanion kext causes issues with the OC boot picker and installing updates. Basically updates were not applied. And boot picker first showed "EFI" instead of automatically selecting MacOS Installer, and even if you manually chose MacOS Installer, the installation never completed. It was just rebooting, and trying to go to the main boot drive, as if the update was applied. But of course, since it wasn't applied, you still have the MacOS Installer option in boot picker, aaaand...if you were however choosing to boot into the system (or let it automatically boot into the system)...you would notice that no update has been actually installed.
  2. WEG + MacPro SMBIOS (using MacPro7,1 but I remember having the same issue with iMacPro1,1 as well, if I'm not mistaken, and also MacPro5,1) creates a "boot to no signal" issue..., UNLEEEESSSS...you're using boot-arg: agdpmod=pikera.

 

So yeah, looks like adding boot-arg: agdpmod=pikera solves this issues while using MacPro7,1 SMBIOS. :D Thank you!

 

Since I've now already completed the update to RC, will keep testing this setup (including WEG 1.7.1d7) with the next update, to see if everything goes smoothly, both during installation and afterwards. Boot is definitely working now, with this boot-arg in place. And I'm guessing (haven't tested yet) Recovery should, too.

 

Once again, thank you!

Edited by arsradu
  • Like 1
kgp
kgp
Posted
Posted
11 minutes ago, arsradu said:

Well...what we've learned today:

  1. AppleBCMWLANCompanion kext causes issues with the OC boot picker and installing updates. Basically updates were not applied. And boot picker first showed "EFI" instead of automatically selecting MacOS Installer, and even if you manually chose MacOS Installer, the installation never completed. It was just rebooting, and trying to go to the main boot drive, as if the update was applied. But of course, since it wasn't applied, you still have the MacOS Installer option in boot picker, aaaand...if you were however choosing to boot into the system (or let it automatically boot into the system)...you would notice that no update has been actually installed.
  2. WEG + MacPro SMBIOS (using MacPro7,1 but I remember having the same issue with iMacPro1,1 as well, if I'm not mistaken, and also MacPro5,1) creates a "boot to no signal" issue..., UNLEEEESSSS...you're using boot-arg: agdpmod=pikera.

 

So yeah, looks like adding boot-arg: agdpmod=pikera solves this issues while using MacPro7,1 SMBIOS. :D Thank you!

 

Since I've now already completed the update to RC, will keep testing this setup (including WEG 1.7.1d7) with the next update, to see if everything goes smoothly, both during installation and afterwards. Boot is definitely working now, with this boot-arg in place. And I'm guessing (haven't tested yet) Recovery should, too.

 

Once again, thank you!

 

Guess it is sufficient to disable AppleBCMWLANCompanion kext for the OTA update?

arsradu
arsradu
Posted
Posted (edited)
33 minutes ago, KGP-iMacPro said:

 

Guess it is sufficient to disable AppleBCMWLANCompanion kext for the OTA update?

I mean...probably.... I remember trying that, and having the same issue, but maybe I was missing something else...? So, technically yes, I think it should be enough. Unfortunately I'm having poor performance with this kext, so while it works as a last resort, for browsing and stuff, it's not that great for downloads. I mean, it's ok, but yeah, so far it's still in testing phase, so issues are prone to occur. But...having to disable that in order to update, combined with the poor performance, made me disable it for good. At least for now. :) It's a great initiative in a world without OCLP, and it works even with SIP enabled, which is awesome. But yeah, too many issues right now. And Tahoe seems to be really unstable on its own. When you're adding even more variables to the equation, it cannot go well.

Sometimes my system is hanging during boot, for absolutely no reason. Reboot and it works fine. Sometimes it hangs before displaying boot picker. It's still very, very slow in showing the boot picker and I still have no idea what's causing this. So...there are already plenty of issues. I'm trying to reduce their number, not add to it even more. :)))

 

Anyway, thank you so much for the idea. :)

Edited by arsradu
kgp
kgp
Posted
Posted (edited)
1 hour ago, arsradu said:

I mean...probably.... I remember trying that, and having the same issue, but maybe I was missing something else...? So, technically yes, I think it should be enough. Unfortunately I'm having poor performance with this kext, so while it works as a last resort, for browsing and stuff, it's not that great for downloads. I mean, it's ok, but yeah, so far it's still in testing phase, so issues are prone to occur. But...having to disable that in order to update, combined with the poor performance, made me disable it for good. At least for now. :) It's a great initiative in a world without OCLP, and it works even with SIP enabled, which is awesome. But yeah, too many issues right now. And Tahoe seems to be really unstable on its own. When you're adding even more variables to the equation, it cannot go well.

Sometimes my system is hanging during boot, for absolutely no reason. Reboot and it works fine. Sometimes it hangs before displaying boot picker. It's still very, very slow in showing the boot picker and I still have no idea what's causing this. So...there are already plenty of issues. I'm trying to reduce their number, not add to it even more. :)))

 

Anyway, thank you so much for the idea. :)


That‘s weird. I do not have any issues with the OC boot picker or the performance of the kext. Just a few random KP from time to time. If you want, pass by the respective thread whenever you feel like and we have a deeper look at your issues. 👍🏼

Edited by KGP-iMacPro
  • Like 1
jlrycm
jlrycm
Posted
Posted (edited)
4 hours ago, arsradu said:

I should probably mention I'm using the AppleBCMWLANCompanion kext, not sure if that makes a difference or not. I'll probably remove it anyway, since I'm getting incredibly slow speeds (couple hundred KB/s downloaded). I can get better speeds with my Android phone connected via data cable, and USB Tethering enabled.

Anyway, I'm just curious if you guys encountered the same issue or if you have any ideas what's causing this.

@arsradu you must disable in the config file the AppleBCMWLANCompanion kext to prevent the installation second phase (after restarting for the first time) to fail and re-enable it after the installation is completed. This issue was reported various times in the AppleBCMWLANCompanion kext thread created by @Austere.J who acknowledged it and said will try to fix it on a future kext release.

Edited by jlrycm
  • Like 3
arsradu
arsradu
Posted
Posted
19 minutes ago, jlrycm said:

@arsradu you must disable in the config file the AppleBCMWLANCompanion kext to prevent the installation second phase (after restarting for the first time) to fail and re-enable it after the installation is completed. This issue was reported various times in the AppleBCMWLANCompanion kext thread created by @Austere.J who acknowledged it and said will try to fix it on a future kext release.

Ah, ok. Good to know it's already on the list of things to fix. :) Do you also have poor performance with this kext?

jlrycm
jlrycm
Posted
Posted (edited)
17 minutes ago, arsradu said:

Ah, ok. Good to know it's already on the list of things to fix. :) Do you also have poor performance with this kext?

I don’t have poor performance using wifi. It’s working well. In the other hand, my Apple Magic Mouse 2 USB-C edition was struggling with the Bluetooth chip after switching to the Broadcom card and I had to relocate the desktop case closer to the mouse to see an improvement and no mouse lagging, this compared to the good mouse performance I was getting from an Intel AX210 chip which has BT 5.2.

 

Having said the above, I prefer to use Ethernet because it’s always more stable. 

Edited by jlrycm
  • Like 1
laobamac_yyds
laobamac_yyds
Posted
Posted
12 minutes ago, eSaF said:

I can confirm 100% this revised 1.7 WEG kext works as described.

As I explained previously to clean install or update Tahoe, I have to use a 7,1 Pro SmBIOS and then complete the setup with my 20,20 iMac SmBIOS.

 

@laobamac_yyds thank you for your continued hard work to make this possible.

Cheers. :thumbsup_anim:

 

Cheers:thumbsup_anim:

  • Like 1
kgp
kgp
Posted
Posted
11 minutes ago, jlrycm said:

I don’t have poor performance using wifi. It’s working well. In the other hand, my Apple Magic Mouse 2 USB-C edition was struggling with the Bluetooth chip after switching to the Broadcom card and I had to relocate the desktop case closer to the mouse to see an improvement and no mouse lagging, this compared to the good mouse performance I was getting from an Intel AX210 chip which has BT 5.2.

 

Having said the above, I prefer to use Ethernet because it’s always more stable. 


Weird, I have no issues with my Magic Mouse and Magic Keyboard with the BCM943602CDP and respective PCIe adapter with 4 antennas..

  • Like 3
jlrycm
jlrycm
Posted
Posted (edited)
19 minutes ago, KGP-iMacPro said:


Weird, I have no issues with my Magic Mouse and Magic Keyboard with the BCM943602CDP and respective PCIe adapter with 4 antennas..

My Broadcom card is a BCM943602CS which is installed on a 3-antenna PCIe adapter. Most likely there was interference affecting the Bluetooth signal and I read that Bluetooth 5.x handles that better. Anyway, it’s better now after moving the pc to the opposite side.

Edited by jlrycm
  • Like 2
arsradu
arsradu
Posted
Posted

Ok... If you guys don't have performance issues with this kext, then it must be just me and my setup... It's true that the positioning of my PC, and the other things around it might interfere with the reception. Unfortunately I can't switch places right now. Coincidentally, I had to switch places after Tahoe was released, and I haven't tested it on Sequoia anymore. Which reminds me I could actually test it on Sequoia, as well, since I have it installed. And I could try both OCLP patching and BCMC. And see which one works better, if there is any difference. If not...then it's clearly just the new environment. Unfortunately, there's nothing I can do right now. But I should be able to test again in a few weeks when I move back to my initial setup, and everything will be back to the original placements.

 

So, for now, I won't consider it a bug, since you guys mentioned it's ok for you. So there's no point setting up the developer on a ghost chase. :)) But will see how it goes. :) 

 

I'm also using the BCM943602CDP. BT seems ok... Haven't tested Magic Mouse and keyboard though. But for other peripherals, it works well. Only issue is the WiFi.

 

Speaking of Magic Mouse and Apple Wireless Keyboard, do you guys get issues with these two disconnecting and reconnecting? I do have other Apple devices nearby, and I'm thinking it could affect this. But I've tried this with real Apple hardware (a Mac Mini 2020) so it's definitely not a "hack" issue. It's weird, cause it just disconnects and reconnects while typing something or moving the mouse around. It does look like a reception issue. But they're close to each other. It's not like they're 10m apart. So it's not the distance. But it could be other devices.... I don't know.

 

Have you encountered something like this with your Apple accessories like BT mouse and keyboard?

kgp
kgp
Posted
Posted
33 minutes ago, arsradu said:

Ok... If you guys don't have performance issues with this kext, then it must be just me and my setup... It's true that the positioning of my PC, and the other things around it might interfere with the reception. Unfortunately I can't switch places right now. Coincidentally, I had to switch places after Tahoe was released, and I haven't tested it on Sequoia anymore. Which reminds me I could actually test it on Sequoia, as well, since I have it installed. And I could try both OCLP patching and BCMC. And see which one works better, if there is any difference. If not...then it's clearly just the new environment. Unfortunately, there's nothing I can do right now. But I should be able to test again in a few weeks when I move back to my initial setup, and everything will be back to the original placements.

 

So, for now, I won't consider it a bug, since you guys mentioned it's ok for you. So there's no point setting up the developer on a ghost chase. :)) But will see how it goes. :) 

 

I'm also using the BCM943602CDP. BT seems ok... Haven't tested Magic Mouse and keyboard though. But for other peripherals, it works well. Only issue is the WiFi.

 

Speaking of Magic Mouse and Apple Wireless Keyboard, do you guys get issues with these two disconnecting and reconnecting? I do have other Apple devices nearby, and I'm thinking it could affect this. But I've tried this with real Apple hardware (a Mac Mini 2020) so it's definitely not a "hack" issue. It's weird, cause it just disconnects and reconnects while typing something or moving the mouse around. It does look like a reception issue. But they're close to each other. It's not like they're 10m apart. So it's not the distance. But it could be other devices.... I don't know.

 

Have you encountered something like this with your Apple accessories like BT mouse and keyboard?


no issues.. as suggested above, pass by the BCMC thread when you feel set and ready and we try to fix your issues. 👍🏼 Let’s not overload this thread here with BCMC topics! There is a dedicated thread for such issues! 

  • Like 1
arsradu
arsradu
Posted
Posted
4 minutes ago, KGP-iMacPro said:


no issues.. as suggested above, pass by the BCMC thread when you feel set and ready and we try to fix your issues. 👍🏼 Let’s not overload this thread here with BCMC topics! There is a dedicated thread for such issues! 

True. And will do. :) 

jlrycm
jlrycm
Posted
Posted
8 hours ago, laobamac_yyds said:

The previous relevant explanation is as follows. If you don't know what this WEG is, you can take a look first.

https://www.insanelymac.com/forum/topic/361713-pre-release-macos-tahoe-261/page/8/#findComment-2842996

 

Well, nearly 20 graphics cards have been tested, and 4 of them have the problem of restarting after the second stage of OTA. The troubleshooting found that they seem to have mistakenly did not overwrite the connector data.

I changed to a simpler and faster method to judge whether the file exists directly through VFS, which can achieve faster startup speed and stability.

 

Tested graphics card:RX460，RX570，RX590，RX5600XT，RX5600OEM，RX6600，RX6900XT（All are official versions or XFX, ROG）

 

Please use 1.7.1d7, this is the final version! I won't modify it again until I encounter a new problem. At the same time, I have open sourced it and submitted it to PR. Welcome to check it out.

WhateverGreen-1.7.1d7.zip 604.87 kB · 29 downloads

 

Source code:https://github.com/laobamac/WhateverGreenPR

PR:https://github.com/acidanthera/WhateverGreen/pull/126

Using a MacPro 7,1 SMBIOS and defining the pikera boot arg, the kext did not work for me. It triggers  a kernel panic immediately after the OpenCore boot menu.

laobamac_yyds
laobamac_yyds
Posted
Posted
8 minutes ago, jlrycm said:

Using a MacPro 7,1 SMBIOS and defining the pikera boot arg, the kext did not work for me. It triggers  a kernel panic immediately after the OpenCore boot menu.

did you use 1.7.1d7？There are indeed reports of kp in d6, but I believe d7 has already been fixed.

laobamac_yyds
laobamac_yyds
Posted
Posted (edited)
8 minutes ago, jlrycm said:

Yes, I used 1.7.1d7.

ok It seems like a new problem that has never been encountered before. Please provide me with your hardware information. Thank you for your testing.

8 minutes ago, jlrycm said:

@laobamac_yyds Yes, I used 1.7.1d7.

  Hide contents

image.thumb.png.ef0805f2bd7b410d866de8e8496c60bf.png

 

Wait, it seems like you're using NootRX?

 

NootRX and WhateverGreen cannot coexist.

 

If you need to use NootRX driver for discrete graphics, you won't be able to load WEG, otherwise the system will crash directly

Edited by laobamac_yyds
jlrycm
jlrycm
Posted
Posted (edited)
12 minutes ago, laobamac_yyds said:

ok It seems like a new problem that has never been encountered before. Please provide me with your hardware information. Thank you for your testing.

@laobamac_yyds As requested, MSI Z590-A Pro, i9-10900K, 64 GB RAM and below is the dGPU information and panic log. I disabled NootRX before I booted using WEG.Kernel-2025-11-01-123400.panic

 

Spoiler

Screenshot2025-11-01at1_06_35PM.thumb.png.3f8498e009660ff3fda3dc940e73e2b1.png

 

Edited by jlrycm
laobamac_yyds
laobamac_yyds
Posted
Posted
3 minutes ago, jlrycm said:

I tried again, here is the panic log Kernel-2025-11-01-132807.panic

It seems that there are still other things in the log that caused the crash, look at the selected content in my picture.What is this?1000125424.thumb.jpg.22d3b7f7ea73dae12f0cfbe65aaad88d.jpg

jlrycm
jlrycm
Posted
Posted
3 minutes ago, laobamac_yyds said:

It seems that there are still other things in the log that caused the crash, look at the selected content in my picture.What is this?1000125424.thumb.jpg.22d3b7f7ea73dae12f0cfbe65aaad88d.jpg

I disabled the ibridged.kext and now macOS loaded without issues. Clearly the ibridged.kext and the WEG kext cannot co-exist. I enabled this ibridged.kext to test if it works and forgot it was still enabled.

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