FWIW, I started a new Mojave VM, and then allowed it to update itself whilst I played Q3A on the Win10 VM on the same box. Occasionally I poked at the update process when needed but otherwise it just worked. This certainly isn't an assessment, it's not backed by any other data, it's simply what I found out of curiosity. This is using Parallels 16.5.1, so it may be a more recent version than yours...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Latebloom - An experimental workaround for the 11.3+ race condition
- Thread starter Syncretic
- Start date
- Sort by reaction score
- Status
Seems that one way to stabilize the system is to reformat all your drives. I cannot test anything myself for quite a long time, but I wonder if any of you that has some intermittent problems would try to do a repair on all your drives before you do that.
I have seen in the past that although Disk Utility reports nothing something might be fixed anyway. If you try it be sure to select the drive itself, not only the partitions. Disk Utility starts with the drives hidden, so you have to select to show them. Also, the absolute newest version you are able to use. Go trough all your drives and partitions regardless of if they are apfs or something else. Have backup before you do.
The probability of this being a solution is low, but it would be nice to know.
I have seen in the past that although Disk Utility reports nothing something might be fixed anyway. If you try it be sure to select the drive itself, not only the partitions. Disk Utility starts with the drives hidden, so you have to select to show them. Also, the absolute newest version you are able to use. Go trough all your drives and partitions regardless of if they are apfs or something else. Have backup before you do.
The probability of this being a solution is low, but it would be nice to know.
Perhaps I've just been lucky so far, but I'm mystified that your booting experience should be so negative as of late. In my experience, the likelihood that BS 11.3+ will install correctly on a cMP 5,1 without latebloom is close to nil (although I succeeded once with 11.4 [I never got that one to boot to the Desktop and had to start from scratch weeks later, this time with latebloom]), but it is close to 60 or 70% if latebloom is used. In my case, since all I have is spinners, I use a low delay value for latebloom (my parameters: 15/1/1). For now, I'm keeping the same values after installation, and I haven't had any issues. Oddly enough, I noticed that I was able to successfully and consistently boot to the 11.4 Desktop WITHOUT latebloom! I haven't tried that with 11.5.1 yet, but I wouldn't be surprised if that should work. Admittedly, I haven't booted many times after three successful installs of 11.4+, but I haven't had any hangs for either 11.4, 11.5 or 11.5.1.
Yes, always leave a dedicated Mojave drive in one of the drive bays with a clean install of Mojave that can be booted from in case things go sour.
Added another SSD in optical bay and installed the latest Monterey Beta. Latebloom was flawless. I didn't change any values.
Now if I could get my bluetooth working in Monterey that would be lovely.
Now if I could get my bluetooth working in Monterey that would be lovely.
I'm now successfully using OpenCore Legacy Patcher on a variety of Mac models without issue. I do have approx. 20 close to identical 4,1 ->5,1 MacPros to roll out, and if I can get Latebloom working reliably it would make sense to do so now, rather than trying to patch and update these machines later. They work great with 11.2.3, but obviously it would be great to be able to have a uniform OS revision across all machines.
Is there a 'Latebloom for Dummies' post anywhere? Looking through this thread I see the basic concept is to either manually move the kext into place, or use the OpenCore Legacy Patcher to install it, and then to configure it for a specific delay until you find which delay works well for your configurations. However, I can't find a single post that really spells out the steps clearly.
Is there a 'Latebloom for Dummies' post anywhere? Looking through this thread I see the basic concept is to either manually move the kext into place, or use the OpenCore Legacy Patcher to install it, and then to configure it for a specific delay until you find which delay works well for your configurations. However, I can't find a single post that really spells out the steps clearly.
Please find my Latebloom test report below. I followed CDF's reformating all the drives. I used a bootable 11.5.1 installer to reformat my OS drives as apfs and spinners as HFS.
NB I have my 3 x 24Tb RAID drives (video and TV storage and backups) switched off until after I have booted into Big Sur. I switch back on after booting to minimize any data loss and will continue to do this until a non-experimental Latebloom or a future solution fixes the race condition.
I settled on these values (85/1/1) after testing Martin's OC 0.7.1 package (and Latebloom added) with macOS11.5.1 cMP 5.1 system with the specs given in the report. These values work for me
I had tried numerous higher Latebloom values from 100 to 250 and ranges from 1 to 50. Nothing worked consistently.
After about 20 cold and 15 warm boots I've settled on (85/1/1).
NB I have my 3 x 24Tb RAID drives (video and TV storage and backups) switched off until after I have booted into Big Sur. I switch back on after booting to minimize any data loss and will continue to do this until a non-experimental Latebloom or a future solution fixes the race condition.
I settled on these values (85/1/1) after testing Martin's OC 0.7.1 package (and Latebloom added) with macOS11.5.1 cMP 5.1 system with the specs given in the report. These values work for me
I had tried numerous higher Latebloom values from 100 to 250 and ranges from 1 to 50. Nothing worked consistently.
After about 20 cold and 15 warm boots I've settled on (85/1/1).
Code:
Coldboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-071-2021-07-05
51 0 0 0xd000 0xd000 AAA.LoadEarly.latebloom (0.19) D0667827-216F-33FF-9C91-1ED4972E4A28 <14 5 3 2 1>
2021-07-29 14:26:22.328044-1000 0x74 Default 0x0 0 0 kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0
Real model decoded from serial number: Mac Pro 2010 (MP5,1)
2 x Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
YMxxxxxQEUF
Radeon RX 580
running at 11.5.1 20G80 Kernel 20.6.0
boot-args -lilubetaall -wegbeta agdpmod=pikera shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0 latebloom=85 lb_range=1 lb_debug=1
Hardware:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.4 GHz
Number of Processors: 2
Total Number of Cores: 8
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
System Firmware Version: 9144.0.7.1.0
SMC Version (system): 1.39f11
SMC Version (processor tray): 1.39f11
System Software Overview:
System Version: macOS 11.5.1 (20G80)
Kernel Version: Darwin 20.6.0
Network:
Type: Ethernet
Hardware: Ethernet
Service Order: 0
Type: Ethernet
Hardware: Ethernet
Service Order: 1
Type: Ethernet
Hardware: Ethernet
Service Order: 2
Type: AirPort
Hardware: AirPort
Service Order: 3
Type: Ethernet
Hardware: Ethernet
Service Order: 4
Wi-Fi:
Storage:
File System: Journaled HFS+
BSD Name: disk2s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk2s3
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk2s4
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk2s5
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk3s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk3s3
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk4s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk5s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk7s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk7s2
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk5s3s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk11
Medium Type: Rotational
Protocol: USB
Internal: No
File System: Journaled HFS+
BSD Name: disk13
Medium Type: Rotational
Protocol: USB
Internal: No
Physical Interconnect: SATA
BSD Name: disk0
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
BSD Name: disk0s2
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk2
File System: MS-DOS FAT32
BSD Name: disk2s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk2s2
Content: Apple_HFS
File System: Journaled HFS+
BSD Name: disk2s3
Content: Apple_HFS
File System: Journaled HFS+
BSD Name: disk2s4
Content: Apple_HFS
File System: Journaled HFS+
BSD Name: disk2s5
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk3
File System: MS-DOS FAT32
BSD Name: disk3s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk3s2
Content: Apple_HFS
File System: Journaled HFS+
BSD Name: disk3s3
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk1
File System: MS-DOS FAT32
BSD Name: disk1s1
Content: EFI
BSD Name: disk1s2
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk6
File System: MS-DOS FAT32
BSD Name: disk6s1
Content: EFI
BSD Name: disk6s2
Content: Apple_APFS
PCI:
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-2
Name: ATY,AMD,RadeonFramebuffer
Type: Display Controller
Bus: PCI
Slot: Slot-1
Type: Audio Device
Bus: PCI
Slot: Slot-1
Name: RocketRAID 644L SATA Controller
Type: RAID Controller
Bus: PCI
Slot: Slot-3
Type: AHCI Controller
Bus: PCI
Slot: Slot-4
USB:
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x1705
Speed: Up to 480 Mb/s
Location ID: 0xfa200000 / 1
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB2.0 Hub:
Product ID: 0x0606
Speed: Up to 480 Mb/s
Location ID: 0xfd300000 / 1
Andrea Comm USB-SA Headset:
Product ID: 0x0016
Speed: Up to 12 Mb/s
Location ID: 0xfd340000 / 3
Product ID: 0x1006
Speed: Up to 480 Mb/s
Location ID: 0xfd310000 / 2
Product ID: 0x024f
Speed: Up to 1.5 Mb/s
Location ID: 0xfd312000 / 4
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Product ID: 0x4500
Location ID: 0x5a100000
Bluetooth USB Host Controller:
Product ID: 0x8215
Location ID: 0x5a110000
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB 3.1 Bus:
Host Controller Driver: AppleASMediaUSBXHCI
Product ID: 0xa4a7
Speed: Up to 480 Mb/s
Location ID: 0x00300000 / 1
Product ID: 0xa4a7
Speed: Up to 5 Gb/s
Location ID: 0x00100000 / 2
Product ID: 0xa4a7
Speed: Up to 10 Gb/s
Location ID: 0x00140000 / 5
USB Interface: 0
Product ID: 0xa4a7
Speed: Up to 10 Gb/s
Location ID: 0x00130000 / 6
USB Interface: 0
Product ID: 0xa4a7
Speed: Up to 10 Gb/s
Location ID: 0x00120000 / 4
USB Interface: 0
Product ID: 0xa4a7
Speed: Up to 10 Gb/s
Location ID: 0x00110000 / 3
USB Interface: 0
Bluetooth:
Bluetooth Low Energy Supported: No
Handoff Supported: No
Instant Hot Spot Supported: No
Manufacturer: Broadcom
Composite Class Of Device: 0x380104
Connected: Yes
Manufacturer: Apple (0x3, 0x31C)
Class of Device: 0x05 0x25 0x2594
EDR Supported: No
eSCO Supported: No
SSP Supported: No
Connected: No
Manufacturer: Cambridge Silicon Radio (0x6, 0x263A)
Class of Device: 0x04 0x06 0x240418
EDR Supported: Yes
eSCO Supported: Yes
SSP Supported: Yes
Memory:
Upgradeable Memory: Yes
Size: 8 GB
Type: DDR3
Speed: 1066 MHz
Size: 8 GB
Type: DDR3
Speed: 1066 MHz
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Size: 8 GB
Type: DDR3
Speed: 1066 MHz
Size: 8 GB
Type: DDR3
Speed: 1066 MHz
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Last edited:
The easiest way is to use OCLP 0.2.4 TUI (not supported in the GUI yet). You can adjust the Latebloom settings to what you want in the patcher settings and then install OCLP like normal.
Post #256 is also a good overview.
Not exactly, there's a couple posts here and there for general explanation but I can write one here regarding OCLP. Ofc I'm the co-author of OpenCore Legacy Patcher so there will be some self promotion ;p
Getting Started with Latebloom
With OpenCore Legacy Patcher v0.2.4, the TUI Application (Text Based interface) gained Latebloom configuration support. Setup is quite simple for those already using OpenCore Legacy Patcher.- GUI (Graphical interface) and CLI (Command line) do also support Latebloom however precise configuration is not implemented. The GUI and CLI will check if latebloom arguments are present in NVRAM so users only need to use the TUI once and can continue using the GUI/CLI afterwards
Configuring Latebloom
Configuring Latebloom with the TUI is quite simple. Open the application and you'll be presented with the main menu. You'll want to head toPatcher Settings and you should see Latebloom settings:Once you select that entry, you'll be presented with all the possible configuration settings:
Latebloom Configuration Settings
The settings are pretty basic and straight forward:Delay
- This property, in milliseconds (ms), sets the delay per configuration loop during boot up.
Range
- This property, in milliseconds (ms), sets the range that latebloom's delay can deviate between per configuration loop.
Debug
- This property sets the debug level of Latebloom, at the time of writing only 0 (no debug) and 1 (debug) are supported.
Recommended Defaults
By default, OpenCore Legacy patcher will assume all pre-Sandy Bridge Macs should use a delay of 100ms, range of 1ms and debug enabled (1). However for certain models that commonly have issues, we increase the delay to 250ms.- These models are MacPro4,1, MacPro5,1, iMac7,1 and iMac8,1
Additionally many users have also contributed their testing on the second post of this thread to better aid users what values are more common with certain hardware and hardware configurations.
Finishing up
Once you have adjusted your latebloom settings to your liking, you can now return to the main menu and build OpenCore. You should see this line when it's building:
Code:
- Adding latebloom.kext 0.19
- Setting latebloom delay of 100ms, range 1ms, debug TrueOnce this is done, head to
Install OpenCore to USB/internal drive and install OpenCore to your desired disk. Reboot, test and if issues persist, continue adjusting and post back here with your finalized results.
I was going to beat myself up for not realizing that was there, then I noticed that revision was only released 3 hours ago, so I let myself off the hook! Thank you!.
(Syncretic: You might consider adding a link to this post as sticky in the first post of this thread. I think it will help a lot of users.)
Last edited:
this post several pages back in this thread posted by a fellow forum member spells out clearly every step. strange you did not find it if you reviewed the thread.
Post in thread 'Latebloom - An experimental workaround for the 11.3+ race condition'
https://forums.macrumors.com/thread...the-11-3-race-condition.2303986/post-30107324
EDIT: Thanks @dataid, you did a great job with this brief but complete FAQ/guide!
Last edited:
Post in thread 'macOS 12 Monterey on Unsupported Macs Thread'
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30134224
Look at page 11 of the thread for the Guide To Installing Latebloom Post # 256. If you feel there I something that should be added or changed please let me know.
Even after a night of sleep I could no resists to answer:
The author of this tool calls it a workaround and not a solution, the results are very mixed, rarely you have seen a report where all problems were gone after applying the workaround and still you are considering obviously without having any clue about its functionality and use and configuration to drop your customers and their systems into a deep hole with potential data corruption and even firmware loss? This is insane!
That's just what drinking too many pan galactic gargle blasters will get you! See if they don't!
But really, there is always a danger on the internet that you don't know the situation and post something wildly off-base, and that's what you've done here.
These are a fleet of MacPros that were donate to our public non-profit K-8 school years ago and have gone through a long series of upgrades at my hands. The aren't going out to customers. You may have been mislead by a thread I started when I was considering selling them off rather than keeping them. They will remain under my direct control and for certain reasons it's important to keep as many of our Macs running as current a MacOS as possible. State-mandated testing software often supports the current and last major revision, or last 2 major revisions, of an OS. This is a HUGE problem now with the extremely frequent major-revisions in the MacOS and iOS ecosystem compared to Windows, because the state mandated testing software still supports Win7 at this time, but will very soon drop support for Mojave and iOS 10 and 11 support went away ages ago. When testing time rolls around the more systems we have that can do it the better, so 20 or so MacPros running BigSur will be useful to us for years longer than 20 MacPros running Mojave. And yes, I think it's reprehensible of the software developers to drop support for older versions of MacOS so quickly, especially when we are talking about mandated testing software.
I've been using the DosDude patchers for years with excellent success, and now I'm in the process of learning the basics of OpenCore so I can use that going forward. If I can't get Latebloom to boot the machines reliably I'll use 11.2.3, but if I can get them to boot reliably this is the time (summer, no students here) to play with it. In the end, if something goes south during the school-year I can have these machines wiped, reinstalled and back on the MDM in short order.
And, a big and heartfelt thank you to the helpful persons working on OpenCore, Latebloom, and OpenCore Legacy Patcher, and those willing to answer questions regarding installation. It's not just individual hobbyists you are helping. In our case you are saving a school many thousands of dollars, or more accurately, since we don't have that money to spend, you are keeping a computer in the hands of students who would otherwise might not have one.
Last edited:
I would recommend against using 11.2.3 if you can’t get Latebloom to work as these are school machines (essentially public) and will not be receiving security updates. If you can’t get Latebloom to work I would keep them all on Catalina which will receive security patches until fall 2022.
Regards.
Long, long answer, unfortunately no facts or arguments about the real topic. Now I know what you would like to achieve, but this does not change the current state or the facts. You still spent obviously no time in studying the thread I linked in or in reading the first post of this thread.
Regardless where you plan to use these machines you will face most likely in this particular situation the trouble I have already described. Honestly I doubt you will be able to restore or even worse rebuild the firmware in your MacPro fleet.
But to not blame other people when you get answers you do not like. This is exactly way politicians react if they face a scientist. They also like to answer questions never been asked.
I did actually initially plan on going with Catalina, but had no luck getting Catalina installed on these using either DosDude patchers or OpenCore (using Legacy Patcher), and decided "what the heck I'll try OCLP and 11.2.3" and things went very smoothly. I'm not sure exactly why I had no luck with Catalina patchers from DosDude (they work fine for me on other varieties of Mac) and was actually under the impression that OpenCore Legacy Patcher didn't even support Catalina. I'm not worried about the software updates; I disable updates and then manually force all machines to update through either ARD or our MDM using 'softwareupdate -i -a --restart' (This is in flux now and definitely doesn't work on M1 machines however. I'm unsure if it works on Big Sur running on intel Boxes; yet another thing I have to figure out.) At any rate, they will only be getting updated on my schedule and under my supervision.
Hopefully I'll have some useful feedback to add sometime next week as I test things a bit further; I'm going to try getting Latebloom up and running on a MacPro 4,1 -> 5,1 which has a BYO Fusion Drive setup, as that's the most common configuration I have on hand. I expect there aren't a lot of people using Latebloom under that scenario.
I have been successfully using DosDude's Catalina installer without patches. I use the boot-args="-no_compat_check" option. I do have an updated BLE card and a flashed RX-580. I do patch the system for Continuity (turn ff SIP, enable the flag and patch the white list in the driver, enable SIP.) It has worked like this completely since Catalina beta and has been my main system.
I moved all the NVRAM options out of config.plist and just set them so I can boot Mojave, Catalina, and Windows 10 without OC. Catalina works well with OC. Big Sur seems fine now using latebloom, but sometimes takes reboots.
To update Catalina, I boot OC with the VMMC flags set and then check my patches.
If you do not have modified BLE or GPU cars, OC is the way to go and works pretty well.
Always keep Mojave around.
I wanted to share my new report now that i'm on Monterey Beta 4.
Its all good except for no WIFI/BT but Ethernet ports working great.
(As in BS 11.5.1, I'm using stock LB settings)
Its all good except for no WIFI/BT but Ethernet ports working great.
(As in BS 11.5.1, I'm using stock LB settings)
Code:
Coldboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-071-2021-07-02
58 0 0 0xd000 0xd000 AAA.LoadEarly.latebloom (0.19) D0667827-216F-33FF-9C91-1ED4972E4A28 <16 6 3 2 1>
2021-08-01 12:30:50.074026-0400 0x72 Default 0x0 0 0 kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0
Real model decoded from serial number: Mac Pro 2012 (MP5,1)
2 x Intel(R) Xeon(R) CPU X5690 @ 3.47GHz
CMxxxxxF4MG
NVIDIA GeForce GTX 680
running at 12.0 21A5294g Kernel 21.0.0
boot-args keepsyms=1 debug=0x100 -lilubetaall latebloom=200, lb_range=20, lb_debug=1
Hardware:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.46 GHz
Number of Processors: 2
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Hyper-Threading Technology: Enabled
Memory: 48 GB
System Firmware Version: 9999.999.999.999.999
OS Loader Version: 537~14
SMC Version (system): 9.9999
SMC Version (processor tray): 1.39f11
System Software Overview:
System Version: macOS 12.0 (21A5294g)
Kernel Version: Darwin 21.0.0
Network:
Type: Ethernet
Hardware: Ethernet
Service Order: 0
Type: Ethernet
Hardware: Ethernet
Service Order: 1
Type: AirPort
Hardware: AirPort
Service Order: 2
Type: Ethernet
Hardware: Ethernet
Service Order: 3
Wi-Fi:
Storage:
File System: NTFS
BSD Name: disk0s3
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk2s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk2s2
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk4s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk8s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk4s2s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk6s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk7s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
Physical Interconnect: SATA
Physical Interconnect: SATA
BSD Name: disk3
File System: MS-DOS FAT32
BSD Name: disk3s1
Content: EFI
BSD Name: disk3s2
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk7
File System: Journaled HFS+
BSD Name: disk7s1
Content: Apple_HFS
BSD Name: disk7s2
Content: Microsoft LDM Metadata
BSD Name: disk7s3
Content: Microsoft Reserved
Physical Interconnect: SATA
BSD Name: disk6
File System: MS-DOS FAT32
BSD Name: disk6s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk6s2
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk5
BSD Name: disk5s1
Content: Apple_APFS
PCI:
Name: NVDA,Display-D
Type: Display Controller
Bus: PCI
Slot: Slot-1
Name: pci10de,e0a
Type: NVDA,Parent
Bus: PCI
Slot: Slot-1
Type: NVM Express Controller
Bus: PCI
Slot: Slot-3
Type: NVM Express Controller
Bus: PCI
Slot: Slot-4
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-2@10,0,0
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-2@9,0,0
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-2@11,0,0
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-2@8,0,0
NVMExpress:
Generic SSD Controller:
Samsung SSD 970 PRO 1TB:
Capacity: 1.02 TB (1,024,209,543,168 bytes)
TRIM Support: Yes
Model: Samsung SSD 970 PRO 1TB
Revision: 1B2QEXP7
Link Width: x1
Link Speed: 5.0 GT/s
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table)
Removable Media: No
S.M.A.R.T. status: Verified
Volumes:
NO NAME:
Capacity: 104.9 MB (104,857,600 bytes)
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
disk0s2:
Capacity: 16.8 MB (16,777,216 bytes)
BSD Name: disk0s2
Content: Microsoft Reserved
WIN11:
Capacity: 999.56 GB (999,557,169,152 bytes)
Free: 739.02 GB (739,018,539,008 bytes)
Writable: No
File System: NTFS
BSD Name: disk0s3
Mount Point: /Volumes/WIN11
Content: Microsoft Basic Data
Generic SSD Controller:
CT2000P2SSD8:
Capacity: 2 TB (2,000,398,934,016 bytes)
TRIM Support: Yes
Model: CT2000P2SSD8
Revision: P2CR033
Link Width: x4
Link Speed: 5.0 GT/s
Detachable Drive: No
BSD Name: disk1
Partition Map Type: GPT (GUID Partition Table)
Removable Media: No
S.M.A.R.T. status: Verified
Volumes:
EFI:
Capacity: 209.7 MB (209,715,200 bytes)
File System: MS-DOS FAT32
BSD Name: disk1s1
Content: EFI
disk1s2:
Capacity: 2 TB (2,000,189,177,856 bytes)
BSD Name: disk1s2
Content: Apple_APFS
USB:
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x1006
Speed: Up to 480 Mb/s
Location ID: 0xfd300000 / 1
Apple Optical USB Mouse:
Product ID: 0x0304
Speed: Up to 1.5 Mb/s
Location ID: 0xfd330000 / 4
Product ID: 0x0220
Speed: Up to 1.5 Mb/s
Location ID: 0xfd320000 / 3
Product ID: 0xa100
Speed: Up to 480 Mb/s
Location ID: 0xfd100000 / 5
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
Product ID: 0x55aa
Speed: Up to 5 Gb/s
Location ID: 0x00800000 / 1
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB3.0 Hub :
Product ID: 0x8110
Speed: Up to 5 Gb/s
Location ID: 0x02800000 / 1
USB3.0 Hub :
Product ID: 0x8110
Speed: Up to 5 Gb/s
Location ID: 0x02830000 / 5
USB2.0 Hub :
Product ID: 0x2811
Speed: Up to 480 Mb/s
Location ID: 0x02400000 / 2
Product ID: 0x6204
Speed: Up to 12 Mb/s
Location ID: 0x02440000 / 4
USB2.0 Hub :
Product ID: 0x2811
Speed: Up to 480 Mb/s
Location ID: 0x02430000 / 3
Product ID: 0x190f
Speed: Up to 480 Mb/s
Location ID: 0x02433000 / 6
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
Bluetooth:
Memory:
Upgradeable Memory: Yes
Size: 16 GB
Type: DDR3
Speed: 1333 MHz
Size: 16 GB
Type: DDR3
Speed: 1333 MHz
Size: 16 GB
Type: DDR3
Speed: 1333 MHz
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Last edited:
Continuing the testing of my recent setup:
Turning to 1: As I've mentioned before, my experience with the race condition has greatly improved with my recent setup. Both cold and warm boots have been virtually flawless except during the installation of macOS 11.5 and the update to 11.5.1 (a total of 3 hangs). To see what role Latebloom (60/-/-) plays in this improvement, I simply disabled it. The result was that I was unable to boot! After 4 consecutive hangs, I reenabled it. (In keeping with 4, I used an emergency OpenCore CD with a known good configuration that includes Latebloom). Every boot thereafter has been successful. So Latebloom definitely plays a major role.
- Latebloom ✔
- macOS 11.5
- Reformatting all physical disks with the 11.5 installer
- Having only one macOS installation in the system
Matt card
Turning to 1: As I've mentioned before, my experience with the race condition has greatly improved with my recent setup. Both cold and warm boots have been virtually flawless except during the installation of macOS 11.5 and the update to 11.5.1 (a total of 3 hangs). To see what role Latebloom (60/-/-) plays in this improvement, I simply disabled it. The result was that I was unable to boot! After 4 consecutive hangs, I reenabled it. (In keeping with 4, I used an emergency OpenCore CD with a known good configuration that includes Latebloom). Every boot thereafter has been successful. So Latebloom definitely plays a major role.
- Status