I think 15ms is too low to make an effect. The most of us have success in the range of 100 to 200.
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
Most of you have SSDs and/or NVMe units. I don't. As I said before, I once booted BS 11.4 without latebloom, and I once was able to install BS 11.4 (a previous installation) without latebloom (but that one never booted, not even with latebloom). I've only been able to install BS 11.4+ successfully (meaning after no more than two hangs) using latebloom 15/1/1, which seems to be close to perfection for me (I've never claimed it would be good for others; at most, it will presumably be good for someone with hardware similar to mine). I've kept 15/1/1 also for booting BS 11.5.1 to the Desktop, and it seems to be working reasonably well. Chances are I might be able to reach the Big Sur desktop without latebloom, but I don't need to try that right now.
Does anyone think we are coming to the end of this latebloom experiment as it was intended?
I don't think we are going to get much further unless it's updated or something.
As I stated a few times before, I'm booting about 5 out of 6 times at least! at least!! and thats good enough for me.
(I'm on BS11.5.1 and Monterey Beta4.)
As far as i'm concerned it's a good enough success to never go back!!!
Thank you @Syncretic!
I don't think we are going to get much further unless it's updated or something.
As I stated a few times before, I'm booting about 5 out of 6 times at least! at least!! and thats good enough for me.
(I'm on BS11.5.1 and Monterey Beta4.)
As far as i'm concerned it's a good enough success to never go back!!!
Thank you @Syncretic!
Last edited:
Why would you actually post such a thing into an important and developing thread?
I just feel we have reached a successful point at which we really can't get much better until there's an update to Latebloom my friend.
You just feel - this is a really great way to end every engineering/scientific approach to get facts based data!
Just a quick drive-by update from me. I've been busy, but I finally eked out a few minutes to update Post #2 with the results that have been submitted during the past week or so, and Post #1 with links to the guides and script that have been written (many thanks to @dataid, @khronokernel, and @Macschrauber for their contributions!).
My current working theory (and focus) remains centered on apfs.kext. Of all the various types of systems that are affected by this bug (including Hackintosh), the single thing they all have in common is booting from APFS. Since its inception, every single dot-rev of APFS has introduced something new. Something big changed between 11.2.3 and 11.3.
I have chased numerous promising leads into dead-ends (e.g. they changed how S.M.A.R.T. is handled, they changed how IOStorageFamily handles AHCI Block Storage, they changed how the BSD VFS is handled, thread priorities are now policy-based - but manipulating each of those led nowhere), and I keep coming back to APFS. The way MacOS handles locks was completely rewritten system-wide in 11.3, so that's an obvious place to look, but I have yet to see any evidence of that being the direct source of the problem. Various elements of the APFS kext were restructured in 11.3, but thus far, manipulating those has produced no interesting results.
My analysis of the APFS kext continues. Since the problem surfaced in 11.3, I have focused on differences/things that changed from 11.2.3 to 11.3, since those are the most likely sources of the problem. The one thing that haunts me is that the bug may not be new - it's entirely possible that this race condition has existed for a long time (possibly years), but until 11.3, the race was always "won" by the correct piece(s) of code. If that's the case, a differential analysis won't reveal the bug, and the change in timing could be so subtle as to not be recognizable. Down that road lies a lot of wasted time. (I'm still hoping that's not the case.)
No and yes (sort of). Until we have a known cause, latebloom remains a workaround, and remains experimental. At best, it's a useful kludge. From that perspective, all users of latebloom (including via other packages, such as OCLP) should be forewarned as I tried to do in my original post. Judging from the reports, latebloom's reliability varies from system to system, and from OS version to OS version, so it's hard to make any blanket statements about it (beyond "your mileage may vary"). Continuing to gather data (user reports) is useful, even if it's only to allow new users to home in on potentially useful delay values; plus, clues to "the answer" might be buried in those reports. (Or not.)
On the other hand, I have yet to see any reports of latebloom causing problems (panics, corruption, or other weirdness), so it may be time to remove the "beta" designation and just call it a kludgy workaround. When I get some time (maybe by this weekend?), I'll try to clean up the code, maybe condense the boot-args into a single argument, and post an "official" non-beta version. It will definitely remain experimental, but I think it's stable enough to merit wider distribution. (I am open to debate on that issue, if anyone disagrees.)
My current working theory (and focus) remains centered on apfs.kext. Of all the various types of systems that are affected by this bug (including Hackintosh), the single thing they all have in common is booting from APFS. Since its inception, every single dot-rev of APFS has introduced something new. Something big changed between 11.2.3 and 11.3.
I have chased numerous promising leads into dead-ends (e.g. they changed how S.M.A.R.T. is handled, they changed how IOStorageFamily handles AHCI Block Storage, they changed how the BSD VFS is handled, thread priorities are now policy-based - but manipulating each of those led nowhere), and I keep coming back to APFS. The way MacOS handles locks was completely rewritten system-wide in 11.3, so that's an obvious place to look, but I have yet to see any evidence of that being the direct source of the problem. Various elements of the APFS kext were restructured in 11.3, but thus far, manipulating those has produced no interesting results.
My analysis of the APFS kext continues. Since the problem surfaced in 11.3, I have focused on differences/things that changed from 11.2.3 to 11.3, since those are the most likely sources of the problem. The one thing that haunts me is that the bug may not be new - it's entirely possible that this race condition has existed for a long time (possibly years), but until 11.3, the race was always "won" by the correct piece(s) of code. If that's the case, a differential analysis won't reveal the bug, and the change in timing could be so subtle as to not be recognizable. Down that road lies a lot of wasted time. (I'm still hoping that's not the case.)
No and yes (sort of). Until we have a known cause, latebloom remains a workaround, and remains experimental. At best, it's a useful kludge. From that perspective, all users of latebloom (including via other packages, such as OCLP) should be forewarned as I tried to do in my original post. Judging from the reports, latebloom's reliability varies from system to system, and from OS version to OS version, so it's hard to make any blanket statements about it (beyond "your mileage may vary"). Continuing to gather data (user reports) is useful, even if it's only to allow new users to home in on potentially useful delay values; plus, clues to "the answer" might be buried in those reports. (Or not.)
On the other hand, I have yet to see any reports of latebloom causing problems (panics, corruption, or other weirdness), so it may be time to remove the "beta" designation and just call it a kludgy workaround. When I get some time (maybe by this weekend?), I'll try to clean up the code, maybe condense the boot-args into a single argument, and post an "official" non-beta version. It will definitely remain experimental, but I think it's stable enough to merit wider distribution. (I am open to debate on that issue, if anyone disagrees.)
Adding to the Mac Pro 4,1->5,1 list. Updated from 11.2.3 to 11.5.1 after switching my setup to OCLP v2.4.0 and enabling Latebloom.
Had no boot issues so far using the default settings for Latebloom in OCLP (250/1/1), but I have not done an extensive amount of reboots.
Had no boot issues so far using the default settings for Latebloom in OCLP (250/1/1), but I have not done an extensive amount of reboots.
Code:
Warmboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-071-2021-07-02
56 0 0 0xd000 0xd000 AAA.LoadEarly.latebloom (0.19) D0667827-216F-33FF-9C91-1ED4972E4A28 <14 5 3 2 1>
2021-08-04 08:13:54.213771-0400 0x74 Default 0x0 0 0 kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0
Real model decoded from serial number: Mac Pro 2009 (MP4,1)
2 x Intel(R) Xeon(R) CPU X5680 @ 3.33GHz
H0xxxxxW20H
Radeon RX 580
running at 11.5.1 20G80 Kernel 20.6.0
boot-args -no_compat_check keepsyms=1 debug=0x100 -lilubetaall latebloom=250, lb_range=1, lb_debug=1 -v
Hardware:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.33 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: 32 GB
System Firmware Version: 9999.999.999.999.999
SMC Version (system): 9.9999
SMC Version (processor tray): 1.39f5
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: FireWire
Hardware: FireWire
Service Order: 2
Type: AirPort
Hardware: AirPort
Service Order: 3
Type: Ethernet
Hardware: Ethernet
Service Order: 4
Wi-Fi:
Card Type: AirPort Extreme (0x14E4, 0x111)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1680.8)
Storage:
File System: Journaled HFS+
BSD Name: disk0s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk1s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk2s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk5s1
Medium Type: SSD
Protocol: PCI
Internal: Yes
File System: APFS
BSD Name: disk5s5s1
Medium Type: SSD
Protocol: PCI
Internal: Yes
Physical Interconnect: SATA
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
Physical Interconnect: SATA
BSD Name: disk0
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk0s2
Content: Apple_HFS
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
Physical Interconnect: SATA
BSD Name: disk1
File System: MS-DOS FAT32
BSD Name: disk1s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk1s2
Content: Apple_HFS
Physical Interconnect: PCI
BSD Name: disk4
File System: MS-DOS FAT32
BSD Name: disk4s1
Content: EFI
BSD Name: disk4s2
Content: Apple_APFS
PCI:
Name: ATY,AMD,RadeonFramebuffer
Type: Display Controller
Bus: PCI
Slot: Slot-1
Type: Audio Device
Bus: PCI
Slot: Slot-1
Type: AHCI Controller
Bus: PCI
Slot: Slot-3
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-4
USB:
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Product ID: 0x4500
Location ID: 0x5a100000
Bluetooth USB Host Controller:
Product ID: 0x828d
Location ID: 0x5a130000
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Product ID: 0x0601
Speed: Up to 12 Mb/s
Location ID: 0x1d100000 / 1
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB Receiver:
Product ID: 0xc52b
Speed: Up to 12 Mb/s
Location ID: 0x00200000 / 1
Bluetooth:
Bluetooth Low Energy Supported: Yes
Handoff Supported: Yes
Instant Hot Spot Supported: Yes
Manufacturer: Broadcom
Composite Class Of Device: 0x380104
Connected: Yes
Manufacturer: Broadcom (0x5, 0x2211)
Class of Device: 0x05 0x10 0x0540
EDR Supported: No
eSCO Supported: No
SSP Supported: Yes
Connected: Yes
Manufacturer: Nordic Semiconductor (0x7, 0x5A)
Class of Device: Low Energy
Connected: No
Manufacturer: Nordic Semiconductor (0x7, 0x5A)
Class of Device: 0x00 0x00 0x0000
Connected: No
Class of Device: 0x00 0x00 0x0000
Connected: No
Manufacturer: Broadcom (0x9, 0x420E)
Class of Device: 0x02 0x03 0x7A020C
EDR Supported: Yes
eSCO Supported: Yes
SSP Supported: Yes
Memory:
Upgradeable Memory: Yes
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHzI have been following this thread since it started and rather than stressing my 5,1 Pro, I have just testing how Latebloom has been working in normal running. I'd say I am having better results in the 150/20 range rather than 200/20 reported for most dual processor machines, not that interesting but a stat. Cold boots are now more 50/50 rather than 1 in 4/5 attempts and warm boots maybe 1 in 4 fail, if that.
Thank you @Syncretic for your continued fight against this mess for all the great Mac Pro's still loved out there.
Thank you @Syncretic for your continued fight against this mess for all the great Mac Pro's still loved out there.
Code:
Warmboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-072-2021-08-02
49 0 0 0xd000 0xd000 AAA.LoadEarly.latebloom (0.19) D0667827-216F-33FF-9C91-1ED4972E4A28 <14 5 3 2 1>
2021-08-04 16:37:00.937130+0100 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 X5680 @ 3.33GHz
CKxxxxxBEUH
Radeon RX 560
running at 11.5.1 20G80 Kernel 20.6.0
boot-args latebloom=150 lb_range=20 lb_debug=1 -v
Hardware:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.33 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: 64 GB
System Firmware Version: 9999.0.0.0.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: FireWire
Hardware: FireWire
Service Order: 2
Type: AirPort
Hardware: AirPort
Service Order: 3
Type: Ethernet
Hardware: Ethernet
Service Order: 4
Wi-Fi:
Card Type: AirPort Extreme (0x14E4, 0x111)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1680.8)
Storage:
File System: Journaled HFS+
BSD Name: disk0s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk3s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk4s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk6s1
Medium Type: SSD
Protocol: PCI
Internal: Yes
File System: APFS
BSD Name: disk6s5s1
Medium Type: SSD
Protocol: PCI
Internal: Yes
Physical Interconnect: SATA
Physical Interconnect: SATA
Physical Interconnect: SATA
BSD Name: disk0
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk0s2
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk2
File System: MS-DOS FAT32
BSD Name: disk2s1
Content: EFI
BSD Name: disk2s2
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk1
File System: MS-DOS FAT32
BSD Name: disk1s1
Content: EFI
BSD Name: disk1s2
Content: Apple_APFS
Physical Interconnect: PCI
BSD Name: disk5
File System: MS-DOS FAT32
BSD Name: disk5s1
Content: EFI
BSD Name: disk5s2
Content: Apple_APFS
PCI:
Name: ATY,AMD,RadeonFramebuffer
Type: Display Controller
Bus: PCI
Slot: Slot-1
Type: Audio Device
Bus: PCI
Slot: Slot-1
Type: AHCI Controller
Bus: PCI
Slot: Slot-4
USB:
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x9126
Speed: Up to 480 Mb/s
Location ID: 0xfd300000 / 1
Product ID: 0x7849
Speed: Up to 12 Mb/s
Location ID: 0xfd330000 / 5
Product ID: 0x9226
Speed: Up to 12 Mb/s
Location ID: 0xfd360000 / 4
Product ID: 0x8508
Speed: Up to 480 Mb/s
Location ID: 0xfd350000 / 3
Product ID: 0x1105
Speed: Up to 12 Mb/s
Location ID: 0xfd340000 / 2
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
Product ID: 0x4500
Location ID: 0x5a100000
Bluetooth USB Host Controller:
Product ID: 0x828d
Location ID: 0x5a130000
Bluetooth:
Bluetooth Low Energy Supported: Yes
Handoff Supported: Yes
Instant Hot Spot Supported: Yes
Manufacturer: Broadcom
Composite Class Of Device: 0x380104
Connected: Yes
Manufacturer: Apple (0x3, 0x31C)
Class of Device: 0x05 0x10 0x2540
EDR Supported: No
eSCO Supported: No
SSP Supported: No
Connected: Yes
Manufacturer: Apple (0x3, 0x31C)
Class of Device: 0x05 0x20 0x2580
EDR Supported: No
eSCO Supported: No
SSP Supported: No
Connected: Yes
Manufacturer: Apple (0x3, 0x31C)
Class of Device: 0x05 0x25 0x2594
EDR Supported: No
eSCO Supported: No
SSP Supported: No
Connected: No
Class of Device: 0x00 0x00 0x0000
Connected: No
Manufacturer: Cambridge Silicon Radio (0x6, 0x21C8)
Class of Device: 0x04 0x01 0x240404
EDR Supported: Yes
eSCO Supported: Yes
SSP Supported: Yes
Connected: No
Class of Device: 0x00 0x00 0x0000
Connected: No
Manufacturer: Unknown (0x8, 0x00)
Class of Device: 0x05 0x02 0x0508
EDR Supported: Yes
eSCO Supported: Yes
SSP Supported: Yes
Memory:
Upgradeable Memory: Yes
Size: 16 GB
Type: DDR3
Speed: 1066 MHz
Size: 16 GB
Type: DDR3
Speed: 1066 MHz
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: Empty
Size: 16 GB
Type: DDR3
Speed: 1066 MHz
Size: 16 GB
Type: DDR3
Speed: 1066 MHz
Size: Empty
Type: Empty
Speed: Empty
Size: Empty
Type: Empty
Speed: EmptyThere was some misbehavin' with restarts after successful initial boot from USB 11.5.1 installer with 200/25 settings, and I toned it down to 175/25.
However... take a look, @Macschrauber:
Why
Is there something I am doing wrong?
However... take a look, @Macschrauber:
Code:
Coldboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-070-2021-06-07
50 0 0 0xd000 0xd000 AAA.LoadEarly.latebloom (0.19) D0667827-216F-33FF-9C91-1ED4972E4A28 <14 5 3 2 1>
2021-08-04 18:05:38.276236+0200 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 X5690 @ 3.47GHz
CKxxxxxDH2P
AMD Radeon HD 7970
running at 11.5.1 20G80 Kernel 20.6.0
no boot-args setWhy
no boot-args set? Well, obviously not true, since my config.plist says <string>keepsyms=1 debug=0x100 -lilubetaall latebloom=175 lb_range=25 lb_debug=1</string> (and the system actually boots).Is there something I am doing wrong?
the code is:
Code:
try
set bootargs to do shell script "nvram boot-args"
on error
set bootargs to "no boot-args set"
end trywhat happens if you type
Code:
nvram boot-argsinto the terminal?
Code:
wojtek@Wojteks-Mac-Pro.homebound /Users/wojtek nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not foundFunny, I must have f**ked something up in OC.
Regarding your system booting, the default (60/-/-) might actually be suitable in your case then.
I thought the same, however changing the latebloom value to above 200 renders the system unbootable.
So the script is doing what it is supposed to do.
If boot-args are not set then latebloom was run in default setting (60 ms, no range).
10 cold starts, 10 warm starts, so far 95% success rate with apparently default settings of 60 ms and no range (I assume the single time it didn't boot was a coincidence with myself setting the LB to 200, without the actual change of value causing the boot to fail). So my settings are defaults (60,0,0)
Code:
Coldboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-070-2021-06-07
50 0 0 0xd000 0xd000 AAA.LoadEarly.latebloom (0.19) D0667827-216F-33FF-9C91-1ED4972E4A28 <14 5 3 2 1>
2021-08-05 12:29:20.322381+0200 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 X5690 @ 3.47GHz
CKxxxxxDH2P
AMD Radeon HD 7970
running at 11.5.1 20G80 Kernel 20.6.0
no boot-args set
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: 64 GB
System Firmware Version: 9999.999.999.999.999
SMC Version (system): 9.9999
SMC Version (processor tray): 1.39f11
System Software Overview:
System Version: macOS 11.5.1 (20G80)
Kernel Version: Darwin 20.6.0
Network:
Type: AirPort
Hardware: AirPort
Service Order: 0
Type: Ethernet
Hardware: Ethernet
Service Order: 1
Type: Ethernet
Hardware: Ethernet
Service Order: 2
Type: FireWire
Hardware: FireWire
Service Order: 3
Type: Ethernet
Hardware: Ethernet
Service Order: 4
Type: VPN (com.adguard.mac.adguard)
Service Order: 5
Type: PPP (L2TP)
Service Order: 6
Wi-Fi:
Card Type: AirPort Extreme (0x14E4, 0x112)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1680.8)
Storage:
File System: APFS
BSD Name: disk1s2
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk1s1s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
Physical Interconnect: SATA
Physical Interconnect: SATA
BSD Name: disk2
BSD Name: disk2s1
Content: Microsoft Reserved
File System: NTFS
BSD Name: disk2s2
Content: Microsoft Basic Data
BSD Name: disk2s3
Content: Windows Recovery
PCI:
Type: NVM Express 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
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-3
NVMExpress:
Generic SSD Controller:
ADATA SX8200PNP:
Capacity: 2.05 TB (2048408248320 bytes)
TRIM Support: Yes
Model: ADATA SX8200PNP
Revision: 42B7T1KA
Link Width: x4
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:
EFI:
Capacity: 209.7 MB (209715200 bytes)
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
disk0s2:
Capacity: 2.05 TB (2048198492160 bytes)
BSD Name: disk0s2
Content: Apple_APFS
USB:
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB2.0 Hub :
Product ID: 0x2812
Speed: Up to 480 Mb/s
Location ID: 0xfa200000 / 1
Product ID: 0x1261
Speed: Up to 480 Mb/s
Location ID: 0xfa230000 / 3
Product ID: 0x6377
Speed: Up to 480 Mb/s
Location ID: 0xfa210000 / 2
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x1006
Speed: Up to 480 Mb/s
Location ID: 0xfd300000 / 1
Product ID: 0x0250
Speed: Up to 1.5 Mb/s
Location ID: 0xfd320000 / 2
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Product ID: 0x4500
Location ID: 0x5a100000
Bluetooth USB Host Controller:
Product ID: 0x8289
Location ID: 0x5a130000
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
Bluetooth:
Bluetooth Low Energy Supported: Yes
Handoff Supported: Yes
Instant Hot Spot Supported: Yes
Manufacturer: Broadcom
Composite Class Of Device: 0x380104
Connected: Yes
Manufacturer: Apple (0x3, 0x31C)
Class of Device: 0x05 0x20 0x2580
EDR Supported: No
eSCO Supported: No
SSP Supported: No
Memory:
Upgradeable Memory: Yes
Size: 16 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: Empty
Type: Empty
Speed: Empty
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
sub'd.... hanging out to see when it will be good to perform an update w/latebloom.
per the signature, I'm on a mid-2010 with 2012 bootrom and running NVMe drives for macOS and Windows.
still at 11.2.3 until I see some updates to the #1 post that enough testing/development has been completed.
per the signature, I'm on a mid-2010 with 2012 bootrom and running NVMe drives for macOS and Windows.
still at 11.2.3 until I see some updates to the #1 post that enough testing/development has been completed.
I found myself with a a little time to spare, so I did some tidying up on latebloom and added a condensed boot-arg arrangement. I'm posting it here to get some feedback before I replace the "official" version in Post #1, just to be sure I didn't break anything. Attached is version 0.20.
Overall, it should behave exactly like previous versions did, meaning there's no compelling reason to "upgrade" unless you really need the abbreviated boot-arg mechanism.
The default delay remains 60ms, and the old
Examples:
(I haven't yet looked to see if that breaks @Macschrauber's script.)
If you're so inclined, please give it a whirl and report back here. Once a few others have reported success (or at least no reports of Macs bursting into flames), I'll replace the version in Post #1, and maybe remove the "beta" designation as well.
Overall, it should behave exactly like previous versions did, meaning there's no compelling reason to "upgrade" unless you really need the abbreviated boot-arg mechanism.
The default delay remains 60ms, and the old
latebloom=, lb_range=, and lb_debug= boot-args still work, so this version can work as a drop-in replacement for the previous version. However, there's also an abbreviated version of the boot-args, lbloom=, where the syntax is lbloom=delay,range,debug. As with the previous versions, the boot-args parser isn't very smart, so the values for delay/range/debug must all be decimal, maximum 4 digits. Any argument that's missing is presumed to be 0. Any parse error (such as a non-numeric typo) will cause all subsequent arguments to be set to 0.Examples:
lbloom=90,20,1: delay of 90, range of 20 (70..110), debug on.lbloom=110,,1: delay of 110, range 0, debug on (this is identical tolbloom=110,0,1, but one character shorter, in case you need to squeeze every byte out of your boot-args).lbloom=77: delay of 77, range 0, debug off. Again, this is identical tolbloom=77,0,0orlbloom=77,,, but saves a few characters of boot-args.
lbloom=,20,1: this does NOT produce the default of 60; the missing first argument is taken as 0, and latebloom will not do anything at all. (The same thing would happen with an emptylbloom=)lbloom=60,-10,1: the '-' is considered non-numeric, so the range will be set to 0; in addition, this will make the flay rod go skew on the treadle (i.e. confuse the simplistic parser), which will then set debug to 0 as well.latebloom=100 lb_range=20 lb_debug=1 lbloom=90,10: This scenario was present in earlier versions, but undocumented - if any of the latebloom boot-args appears more than once, the last one "wins." In this case, the delay will be 90, the range will be 10, and debug will be 0. The exceptions to the "last one wins" rule are (effectively)latebloom=0orlbloom=0; as soon as the parser sees an effective delay of 0, parsing stops and the kext does nothing, so a subsequentlatebloom=100would be ignored.
_____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0 :: 120,50,1.(I haven't yet looked to see if that breaks @Macschrauber's script.)
If you're so inclined, please give it a whirl and report back here. Once a few others have reported success (or at least no reports of Macs bursting into flames), I'll replace the version in Post #1, and maybe remove the "beta" designation as well.
Script should work
Code:
set boot_log to (do shell script "log show --predicate 'sender == \"latebloom\" AND composedMessage CONTAINS \"Hook placed successfully\"' --last boot --debug")
if boot_log does not contain ("successfully") then
...OCLP 0.24, Latebloom 0.20
Code:
Warmboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-071-2021-07-02
55 0 0 0xe000 0xe000 AAA.LoadEarly.latebloom (0.20) 3F857F21-9A08-3147-8922-1DAB5273CA90 <14 5 3 2 1>
2021-08-05 17:19:21.065719-0700 0x74 Default 0x0 0 0 kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0 :: 70,10,1
Real model decoded from serial number: Mac Pro 2010 (MP5,1)
1 x Intel(R) Xeon(R) CPU W3670 @ 3.20GHz
CKxxxxxCEUG
NVIDIA GeForce GT 640
running at 11.5 20G71 Kernel 20.6.0
boot-args keepsyms=1 debug=0x100 -lilubetaall latebloom=70, lb_range=10, lb_debug=1 -v -no_compat_check
Hardware:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3,2 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 48 GB
System Firmware Version: 9999.999.999.999.999
SMC Version (system): 9.9999
SMC Version (processor tray): 1.39f11
System Software Overview:
System Version: macOS 11.5 (20G71)
Kernel Version: Darwin 20.6.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:
Card Type: AirPort Extreme (0x14E4, 0x8E)
Firmware Version: Broadcom BCM43xx 1.0 (5.106.98.102.31)
Storage:
File System: Journaled HFS+
BSD Name: disk2s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk1s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk3s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: MS-DOS FAT32
BSD Name: disk3s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk5s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk6s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk8s2
Protocol: USB
Internal: No
File System: APFS
BSD Name: disk1s5s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk9s2
Protocol: USB
Internal: No
File System: Journaled HFS+
BSD Name: disk10s2
Protocol: FireWire
Internal: No
Physical Interconnect: SATA
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_Boot
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: disk3
File System: Journaled HFS+
BSD Name: disk3s1
Content: Apple_HFS
File System: MS-DOS FAT32
BSD Name: disk3s2
Content: DOS_FAT_32
Physical Interconnect: SATA
BSD Name: disk5
File System: MS-DOS FAT32
BSD Name: disk5s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk5s2
Content: Apple_HFS
File System: Journaled HFS+
BSD Name: disk5s3
Content: Apple_Boot
PCI:
Type: NVM Express Controller
Bus: PCI
Slot: Slot-2
Name: NVDA,Display-D
Type: Display Controller
Bus: PCI
Slot: Slot-1
Name: pci10de,e1b
Type: NVDA,Parent
Bus: PCI
Slot: Slot-1
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-4
NVMExpress:
Generic SSD Controller:
Samsung SSD 970 EVO Plus 500GB:
Capacity: 500,11 GB (500.107.862.016 bytes)
TRIM Support: Yes
Model: Samsung SSD 970 EVO Plus 500GB
Revision: 2B2QEXM7
Link Width: x4
Link Speed: 5.0 GT/s
Detachable Drive: No
BSD Name: disk4
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: disk4s1
Content: EFI
disk4s2:
Capacity: 499,9 GB (499.898.105.856 bytes)
BSD Name: disk4s2
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
Product ID: 0x1000
Speed: Up to 480 Mb/s
Location ID: 0xfd500000 / 1
USB Interface: 0
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x1006
Speed: Up to 480 Mb/s
Location ID: 0xfa200000 / 1
Product ID: 0x0001
Speed: Up to 12 Mb/s
Location ID: 0xfa230000 / 2
Product ID: 0x0265
Speed: Up to 12 Mb/s
Location ID: 0xfa210000 / 4
Product ID: 0x0221
Speed: Up to 1.5 Mb/s
Location ID: 0xfa220000 / 3
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB3.0 Hub:
Product ID: 0x0616
Speed: Up to 5 Gb/s
Location ID: 0x00500000 / 1
Product ID: 0x25a2
Speed: Up to 5 Gb/s
Location ID: 0x00520000 / 4
USB Interface: 0
USB2.0 Hub:
Product ID: 0x0610
Speed: Up to 480 Mb/s
Location ID: 0x00100000 / 2
Bluetooth:
Bluetooth Low Energy Supported: Yes
Handoff Supported: No
Instant Hot Spot Supported: No
Manufacturer: Cambridge Silicon Radio
Composite Class Of Device: 0x380104
Connected: No
Class of Device: 0x05 0x25 0x2594
Memory:
Upgradeable Memory: Yes
Size: 16 GB
Type: DDR3
Speed: 1066 MHz
Size: 16 GB
Type: DDR3
Speed: 1066 MHz
Size: 8 GB
Type: DDR3
Speed: 1066 MHz
Size: 8 GB
Type: DDR3
Speed: 1066 MHzOCLP 0.24, Latebloom 0.20
Still working great!
Still working great!
Code:
Warmboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-071-2021-07-02
56 0 0 0xe000 0xe000 AAA.LoadEarly.latebloom (0.20) 3F857F21-9A08-3147-8922-1DAB5273CA90 <14 5 3 2 1>
2021-08-05 20:57:51.071952-0400 0x74 Default 0x0 0 0 kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0 :: 200,20,1
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 11.5.1 20G80 Kernel 20.6.0
boot-args keepsyms=1 debug=0x100 -lilubetaall lbloom=200,20,1 -no_compat_check
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
SMC Version (system): 9.9999
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: AirPort
Hardware: AirPort
Service Order: 2
Type: Ethernet
Hardware: Ethernet
Service Order: 3
Wi-Fi:
Card Type: AirPort Extreme (0x14E4, 0x8E)
Firmware Version: Broadcom BCM43xx 1.0 (5.106.98.102.31)
Storage:
File System: APFS
BSD Name: disk1s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk1s2
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk5s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk9s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: Journaled HFS+
BSD Name: disk3s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk4s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk6s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: NTFS
BSD Name: disk7s3
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk9s2s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
Physical Interconnect: SATA
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: 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: disk3
File System: Journaled HFS+
BSD Name: disk3s1
Content: Apple_HFS
BSD Name: disk3s2
Content: Microsoft LDM Metadata
BSD Name: disk3s3
Content: Microsoft Reserved
Physical Interconnect: SATA
BSD Name: disk4
File System: MS-DOS FAT32
BSD Name: disk4s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk4s2
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk2
BSD Name: disk2s1
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@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
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-2@10,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: disk7
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: disk7s1
Content: EFI
disk7s2:
Capacity: 16.8 MB (16,777,216 bytes)
BSD Name: disk7s2
Content: Microsoft Reserved
WIN11:
Capacity: 999.56 GB (999,557,169,152 bytes)
Free: 739.02 GB (739,019,014,144 bytes)
Writable: No
File System: NTFS
BSD Name: disk7s3
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: disk8
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: disk8s1
Content: EFI
disk8s2:
Capacity: 2 TB (2,000,189,177,856 bytes)
BSD Name: disk8s2
Content: Apple_APFS
USB:
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 / 2
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 Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Product ID: 0x2018
Speed: Up to 12 Mb/s
Location ID: 0x1a200000 / 1
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
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 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB3.0 Hub :
Product ID: 0x8110
Speed: Up to 5 Gb/s
Location ID: 0x00800000 / 1
USB3.0 Hub :
Product ID: 0x8110
Speed: Up to 5 Gb/s
Location ID: 0x00830000 / 3
USB2.0 Hub :
Product ID: 0x2811
Speed: Up to 480 Mb/s
Location ID: 0x00400000 / 2
Product ID: 0x6204
Speed: Up to 12 Mb/s
Location ID: 0x00440000 / 5
USB2.0 Hub :
Product ID: 0x2811
Speed: Up to 480 Mb/s
Location ID: 0x00430000 / 4
Product ID: 0x190f
Speed: Up to 480 Mb/s
Location ID: 0x00433000 / 6
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
Bluetooth:
Bluetooth Low Energy Supported: No
Handoff Supported: No
Instant Hot Spot Supported: No
Manufacturer: Broadcom
Composite Class Of Device: 0x380104
Connected: No
Manufacturer: Broadcom (0x5, 0x240C)
Class of Device: 0x05 0x20 0x0580
EDR Supported: Yes
eSCO Supported: No
SSP Supported: Yes
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:
OCLP 0.24, Latebloom 0.20. 200-20-1: It is working fine.
Always "Thank you" @Syncretic !
Always "Thank you" @Syncretic !
Code:
Warmboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-071-2021-07-02
57 0 0 0xe000 0xe000 AAA.LoadEarly.latebloom (0.20) 3F857F21-9A08-3147-8922-1DAB5273CA90 <14 5 3 2 1>
2021-08-06 17:37:56.036446+0200 0x74 Default 0x0 0 0 kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully. Count = 0 :: 200,20,1
Real model decoded from serial number: Mac Pro 2009 (MP4,1)
2 x Intel(R) Xeon(R) CPU X5680 @ 3.33GHz
CKxxxxxM8Q0
Radeon RX 580
running at 11.5.1 20G80 Kernel 20.6.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,33 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: 32 GB
System Firmware Version: 9999.999.999.999.999
SMC Version (system): 9.9999
SMC Version (processor tray): 1.39f5
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: FireWire
Hardware: FireWire
Service Order: 2
Type: AirPort
Hardware: AirPort
Service Order: 3
Type: Ethernet
Hardware: Ethernet
Service Order: 4
Wi-Fi:
Card Type: AirPort Extreme (0x14E4, 0x111)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1680.8)
Storage:
File System: APFS
BSD Name: disk2s1
Medium Type: SSD
Protocol: PCI
Internal: Yes
File System: APFS
BSD Name: disk2s2
Medium Type: SSD
Protocol: PCI
Internal: Yes
File System: APFS
BSD Name: disk3s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk3s4
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk6s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk6s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk7s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk9s1
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk3s5s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: NTFS
BSD Name: disk4s2
Medium Type: SSD
Protocol: SATA
Internal: Yes
Physical Interconnect: SATA
Physical Interconnect: PCI
BSD Name: disk0
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
BSD Name: disk0s2
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk5
File System: MS-DOS FAT32
BSD Name: disk5s1
Content: EFI
BSD Name: disk5s2
Content: Apple_APFS
BSD Name: disk5s3
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk4
File System: MS-DOS FAT32
BSD Name: disk4s1
Content: EFI
File System: NTFS
BSD Name: disk4s2
Content: Microsoft Basic Data
Physical Interconnect: SATA
BSD Name: disk8
File System: MS-DOS FAT32
BSD Name: disk8s1
Content: EFI
BSD Name: disk8s2
Content: Apple_APFS
File System: MS-DOS FAT32
BSD Name: disk8s3
Content: EFI
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
Type: AHCI Controller
Bus: PCI
Slot: Slot-4
Type: NVM Express Controller
Bus: PCI
Slot: Slot-3
NVMExpress:
Generic SSD Controller:
Samsung SSD 970 EVO 1TB:
Capacity: 1 TB (1.000.204.886.016 bytes)
TRIM Support: Yes
Model: Samsung SSD 970 EVO 1TB
Revision: 1B2QEXE7
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: 1 TB (999.995.129.856 bytes)
BSD Name: disk1s2
Content: Apple_APFS
USB:
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x005a
Speed: Up to 480 Mb/s
Location ID: 0xfd300000 / 1
Product ID: 0x005a
Speed: Up to 480 Mb/s
Location ID: 0xfd340000 / 4
Product ID: 0x0064
Speed: Up to 12 Mb/s
Location ID: 0xfd330000 / 3
Product ID: 0x026c
Speed: Up to 12 Mb/s
Location ID: 0xfd320000 / 2
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
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 3.0 Bus:
Host Controller Driver: AppleUSBXHCIFL1100
Bluetooth:
Bluetooth Low Energy Supported: No
Handoff Supported: Yes
Instant Hot Spot Supported: Yes
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
Class of Device: 0x00 0x00 0x0000
Connected: No
Manufacturer: Cambridge Silicon Radio (0x5, 0x22F9)
Class of Device: 0x04 0x05 0x240414
EDR Supported: Yes
eSCO Supported: Yes
SSP Supported: Yes
Connected: No
Class of Device: 0x02 0x03 0x5A020C
Connected: No
Manufacturer: Broadcom (0x5, 0x240C)
Class of Device: 0x05 0x10 0x2540
EDR Supported: Yes
eSCO Supported: No
SSP Supported: Yes
Memory:
Upgradeable Memory: Yes
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
Size: 4 GB
Type: DDR3
Speed: 1333 MHz
I have installed Latebloom 0.19 and successfully updated and used BS 11.5.1. I have one destabilizing factor. That's restarting Mac. I have no problems with cold start on Mac. However, a restart of the Mac always fails.
Do you have any tips on how to successfully start Mac with the restart process?
Mac Pro 2009(5.1), macOS Big Sur 11.5.1, OpenCore 0.7.1, Latebloom 0.19, latebloom(150/20/1)
Do you have any tips on how to successfully start Mac with the restart process?
Mac Pro 2009(5.1), macOS Big Sur 11.5.1, OpenCore 0.7.1, Latebloom 0.19, latebloom(150/20/1)
Last edited:
This thread is about finding exactly this data. There have been reports on the different behaviour with cold and warm reboots before and the main reason to post here was to collect (stable) results.
So I am afraid you will have to do another round checking out different values for your particular system and setup.
This may be a problem only in my environment. I use a USB disk to boot my Mac and adjust the Latebloom.
When I do a reboot command on a Mac booted with a USB disk and then boot the Mac again with the USB disk, I sometimes can't find OpenCore, which should be in the EFI volume. I'm specifying the disk number correctly. In that EFI volume/folder, there is an "APPLE" folder instead of an OC folder. Could this be the reason why Mac fails to start on reboot?
When I do a reboot command on a Mac booted with a USB disk and then boot the Mac again with the USB disk, I sometimes can't find OpenCore, which should be in the EFI volume. I'm specifying the disk number correctly. In that EFI volume/folder, there is an "APPLE" folder instead of an OC folder. Could this be the reason why Mac fails to start on reboot?
- Status