[pre-release] macOS Tahoe 26.5

[kgp]

10 minutes ago, deeveedee said:

@kgp Yes - he already indicated that he knows that.  Isn't the important part of the discussion that he received an answer that helped him?

 

If he reconfigures everything to get root patching working again, the boot time will likely increase significantly again.

Anyway, I just wanted to suggest a simple test: boot a clean install of Tahoe using his original EFI folder for comparison.

That’s all — over and out 🙂

  

Edited May 5 by kgp

[deeveedee]

@kgp If I were a betting person, I'd take that bet any day.  The 25 seconds boot-time difference was between MaLd0n's two proposed EFIs (both without root patches).  I doubt the difference would be reversed by the root patches.

[dogansan]

1 hour ago, deeveedee said:

@dogansan you could diff the two EFIs with "diff --brief -r EFI EFI-2"

 

• Files EFI/OC/Kexts/USBMap.kext/Contents/Info.plist and EFI-2/OC/Kexts/USBMap.kext/Contents/Info.plist differ

• Files EFI/OC/config.plist and EFI-2/OC/config.plist differ

Looks like the change was in config.plist: SetApfsTrimTimeout

 

EDIT: I'm confused by the SMBIOS change in USBMap.kext.  You might want to check that.  It should be MacPro7,1 to match the SMBIOS configured in your OC config.plist (unless you've decided to use SMBIOS iMacPro1,1 instead).

@deeveedee , yess , it was the I just made SetApfsTrimTimeout = 0 in my original EFI as it is in @MaLd0n's second EFI  and it now boots in 12 seconds and surely I kept functionality of my Intel BE200 wifi. It is fascinating while I don't know the funtion of this . Thank you

I checked from AI it says this disables the trim function during boot to speed up the boot, so it recommends to chnage it to -1 once a month. Funny

Edited May 5 by dogansan

[deeveedee]

@dogansan Thank you for asking your question. I always love learning something new from MaLd0n and our other hackintosh masters!

 

EDIT: @dogansan What SSD makes/models do you have in your hack?

Edited May 5 by deeveedee

[dogansan]

37 minutes ago, deeveedee said:

@dogansan Thank you for asking your question. I always love learning something new from MaLd0n and our other hackintosh masters!

 

EDIT: @dogansan What SSD makes/models do you have in your hack?

My Tahoe is running on Samsung 9100 Pro 1 tb,  I previously tried  CT2000T700 and T-Force but they were not stable in macos, frequently resetting. Then I moved to this new Samsung model which is quite stable and very fast.

[MaLd0n]

5 hours ago, dogansan said:

This improved a lot,  reduced from 50-52 seconds to 25 seconds. Still behind 15 secs of Sequioa , but very good. Thank you very much. Please advise which change(s) has improved the boot time so I can adapt to my original EFI, as this EFI does not contain my wi-fi and some other features

TRIM SSD is the problem. 

Im using 9100 too, have some slow boot. Is common. stay with -1 and live with that. Use last EFI folder and apply what u need. Is optmized for ur hardware.

[dogansan]

1 hour ago, MaLd0n said:

TRIM SSD is the problem. 

Im using 9100 too, have some slow boot. Is common. stay with -1 and live with that. Use last EFI folder and apply what u need. Is optmized for ur hardware.

By the way, I decided to stay with 0 . And I also understood why my Sequioa and Sonoma bootings are fast , because they are on CT2000 and T-Force SSD's , it seems they don't have issue with -1 TRIM while Samsung has.

[deeveedee]

@dogansan If you have room on one of your other SSDs where Sequoia is working well, you can create another APFS volume and install Tahoe there.  Use the Samsung for non-boot storage.

 

EDIT: This and this confirms your Samsung findings.

Edited May 5 by deeveedee

[MaLd0n]

47 minutes ago, dogansan said:

By the way, I decided to stay with 0 . And I also understood why my Sequioa and Sonoma bootings are fast , because they are on CT2000 and T-Force SSD's , it seems they don't have issue with -1 TRIM while Samsung has.

The speed justifies a few extra seconds.  

[deeveedee]

Wow!!! That's incredible!

 

[chris1111]

It's because @MaLd0n doesn't have air conditioning and he's getting his computer fans to cool him down. 

[ANTIKO]

17 hours ago, MaLd0n said:

Post ur EFI folder here

Here

https://drive.google.com/file/d/1tYWlgMNxrZWupniINI3KN6D4L1S_XG2B/view?usp=sharing

[Max.1974]

All good!!!

 

Edited May 6 by Max.1974

[MaLd0n]

24 minutes ago, ANTIKO said:

Here

https://drive.google.com/file/d/1tYWlgMNxrZWupniINI3KN6D4L1S_XG2B/view?usp=sharing

https://limewire.com/d/lfyQd#KBMpRLOoEO

-Delete old EFI folder and paste new then empty trash. Don't use merge files.
-Don't use Drag and Drop into EFI partition. Use Copy/Paste instead.
-Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen.

[ANTIKO]

1 hour ago, MaLd0n said:

https://limewire.com/d/lfyQd#KBMpRLOoEO

-Delete old EFI folder and paste new then empty trash. Don't use merge files.
-Don't use Drag and Drop into EFI partition. Use Copy/Paste instead.
-Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen.

Thank you, I'll come back in the evening and check.

[dogansan]

11 hours ago, deeveedee said:

@dogansan If you have room on one of your other SSDs where Sequoia is working well, you can create another APFS volume and install Tahoe there.  Use the Samsung for non-boot storage.

 

EDIT: This and this confirms your Samsung findings.

The problem with old generation Samsung , Team T-Force Z540 TM80FF and Crucial CT2000 SSD's is bigger than long boot because of -1 TRIM . They all are unstable , very frequently freezes and crashes , ranging in every few seconds to a few hours. It is mentioned somewhere that all Phison E26 controller equipped gen5 SSD's suffer from this on Mac's. Samsung 9100 Pro has introduced their own inhouse developed controller (Presto)  and very stable. I never experienced a crash over the last two years.  

 

Edited May 6 by dogansan

[ANTIKO]

12 hours ago, MaLd0n said:

https://limewire.com/d/lfyQd#KBMpRLOoEO

-Delete old EFI folder and paste new then empty trash. Don't use merge files.
-Don't use Drag and Drop into EFI partition. Use Copy/Paste instead.
-Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen.

The loading time has increased by about 10 seconds.

[deeveedee]

4 hours ago, dogansan said:

The problem with old generation Samsung , Team T-Force Z540 TM80FF and Crucial CT2000 SSD's is bigger than long boot because of -1 TRIM . They all are unstable , very frequently freezes and crashes , ranging in every few seconds to a few hours. It is mentioned somewhere that all Phison E26 controller equipped gen5 SSD's suffer from this on Mac's. Samsung 9100 Pro has introduced their own inhouse developed controller (Presto)  and very stable. I never experienced a crash over the last two years.

 

You are confirming the Open Core developer recommendations for SSDs to avoid.  This is valuable information for others who are creating new hacks or having problems with their existing hacks.  The SSD choice matters.   This and this are good reading.

[deeveedee]

@laobamac_yyds Have the remaining OCLP Devs invited you to join their team yet?  If not, they're making a mistake.

[laobamac_yyds]

29 minutes ago, deeveedee said:

@laobamac_yyds Have the remaining OCLP Devs invited you to join their team yet?  If not, they're making a mistake.

I wasn't invited, but please don't think it's a mistake.

 

We are all enthusiasts in this field, including you and me. Whether we join a team or not doesn't affect our dedication to our interests.🥰

[deeveedee]

@ANTIKO Attached are a new config.plist and new SSDT-AWAC that disable HPET.  If you want to test, replace the two files in your EFI with these.  Since I haven't seen your DSDT, the HPTE patch is a guess.  I don't expect these changes to make any performance changes to your hack, but am curious to know what you find.

 

EDIT: @ANTIKO You may want to ocvalidate your config.plist.  I didn't look beyond the changes needed to disable HPET.  I just ran ocvalidate 1.0.7 and see this:

NOTE: This version of ocvalidate is only compatible with OpenCore version 1.0.7!

OCS: No schema for HideVerbose at 3 index, context <Drivers>!
OCS: No schema for HideVerbose at 3 index, context <Drivers>!
OCS: No schema for HideVerbose at 3 index, context <Drivers>!
Serialisation returns 3 errors!

 

config.plist.zip SSDT-AWAC.aml.zip

Edited May 6 by deeveedee

[MaLd0n]

This OC is from https://github.com/daliansky/OpenCore_Patch_Build

This version don't inject nothing on Windows or Linux 

[deeveedee]

EDIT2: I'm leaving the post below, but the video stream just froze on remote TV.  Some video works and some is frozen.  I wonder if this has anything to do with DRM?  ... This is definitely a content-specific issue.  Some streaming content that I watch works perfectly.

 

=========================================================

 

Sorry for what is probably a remedial post, but I just experienced a pleasant surprise on my HackBookPro16,2 running Tahoe 26.5 (25F71) with Intel Wi-Fi (itlwm).  Screen mirroring to Apple TV works perfectly.  That may seem trivial to some, but I had never tried it.  No root patches - just Intel Wi-Fi with Open Wireless itlwm and Screen Mirroring works perfectly.

 

In this case, I'm streaming live TV in Firefox from my hack to Apple TV with excellent video / audio quality.

 

 

EDIT: A couple of observations (probably remedial to someone who has experience with Screen Mirroring):

• The picture on the remote TV is more vibrant than the picture on my laptop internal display
• Audio on the remote TV is controllable via the Volume slider in my hack's menu bar

 

Note that I am using VoodooHDA.kext 3.3.4 for Tahoe audio on my hack (to eliminate the need for root patches), but this has no impact on the audio cast via Screen Mirroring.

Edited May 6 by deeveedee

[Pc Bacabal]

8 hours ago, MaLd0n said:

This OC is from https://github.com/daliansky/OpenCore_Patch_Build

This version don't inject nothing on Windows or Linux 

How to use this OC?

[jlrycm]

2 hours ago, Pc Bacabal said:

How to use this OC?

Refer to this guide which provides some guidance on how to use this OpenCore fork

 

https://github.com/5T33Z0/OC-Little-Translated/blob/main/Content/O_OC_NO_ACPI/README.md