Sidebar Sidebar
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

Status
Not open for further replies.
tsialex

tsialex

Contributor
Jun 13, 2016
13,455
13,601
Syncretic said:
Thank you for your submissions!

Should that perhaps be X5680? I'm not aware of an X5980 CPU...


Should that perhaps be 2x W3690? I'm not aware of a 3960 CPU, other than the i7-3960X, which I'm pretty sure won't fit in an LGA1366 socket...
Click to expand...
W3xxx processors have only one functional QPI link, can't be used on a dual CPU tray. W3xxx are always single CPU processors.
 
S

sfalatko

macrumors 6502a
Sep 24, 2016
642
365
Syncretic said:
A Request:

Now that we're starting to see some results, I'd like to start compiling them in an orderly fashion, so that we can begin looking for patterns. As such, I'd ask the following:

Once you've done your testing and settled onlatebloom=/lb_range=/lb_debug= values that work for you, please post those values along with a detailed description of the system as it was tested. (If you're still experimenting, please wait until you're satisfied before posting all this). For system details, I'd like to see the following, in whatever format you choose (I'll be collecting them and reformatting them into a table in Post #2 as time permits, so use whatever format is easiest for you):
  • Actual model (e.g. MacPro 3,1; MacPro 4>5,1; etc.). While there should be no difference whatsoever between a 5,1 and a 4,1 that's flashed to 5,1, please specify if it's flashed (e.g. 4>5,1 or 4.5,1 or similar).
    SPECIAL DISPENSATION: While this is not a Hackintosh forum, nor is this a Hackintosh thread, I'll welcome any Hackintosh results here, since those could conceivably shed more light on the issues at hand. If you post Hackintosh results, please provide as much detail as possible about your system (motherboard, overclocking, any special hardware, etc.). Please note that this invitation applies only to Hackintosh results; if the thread devolves into Hackintosh-specific discussions or gets noisy, I will ask the moderators to take action.
  • BootROM version
  • CPU and count (e.g. 1x X5680, 2x X5675, etc.)
  • Memory count, size, and speed (e.g. 4x2GB 1066, 8x8GB 1333, etc.)
  • WiFi (e.g. none, factory, BCM94322MC, BCM94360CD, etc.)
  • Bluetooth (e.g. none, factory, USB (model info), combo (w/upgraded WiFi), etc.)
  • Disks (internal, including optical drives) - physical, location, logical/formats (no need for size of each partition), e.g.
    • Seagate ST3000DM008 3TB, Bay 2, EFI/APFS Mojave
    • SanDisk SDSSDA 240GB SSD, ODD 1, EFI/HFS+ Sierra/NTFS Windows
    • Samsung 970 EVO 1TB NVMe, HighPoint 7101A, EFI/APFS Big Sur
    • (etc.)
      (Please include the name or version of the OS that formatted the partition (if known) - the APFS format has changed over time, and older APFS-capable MacOS versions can't read some newer APFS volumes.
      There's no need for any personal details, serial numbers, partition sizes, disk names, notation of bootable vs. data drives, etc.)
  • NVMe devices (cards/location/blades), e.g.
    • kryoM.2 evo, slot 4, 1x WD Blue SN550 1TB
    • Sonnet M.2 FUS-SSD-4X4-E3, slot 3, 4x Toshiba XG6-P 2TB
    • (etc.)
  • PCIe devices/location:
    • AMD RX570 4GB, slot 1
    • Sonnet Allegro USB3-4PM-E, slot 4
    • SIIG NN-E38012-S3, slot 2
    • (etc.)
  • USB devices (including external storage):
    • Apple wired keyboard
    • Logitech wireless mouse (Unifying interface)
    • 128GB USB3 flash drive
    • External USB2 Blu-Ray burner
    • (etc.)
If you're lacking some details, or can't access the hardware to get them, just include whatever details you can. The more information we have, the more likely we'll be able to find useful patterns (assuming any exist).

So, as an example modeled loosely on my own system, I might post:


latebloom=90, lb_range=20, lb_debug=0
MacPro 4,1 -> 5,1
BootROM 144.0.0.0.0
CPU: 2x X5675
RAM: 8x8GB 1066
No WiFi
Factory Bluetooth
Disks:
  • Inland 860270 256GB NVMe, MicroConnectors PCIE-M20803HS slot 3, EFI/APFS Mojave
  • SanDisk SDSSA-240G SSD, ODD 2, EFI/APFS Big Sur
  • HP S700 120GB SSD, ODD1, EFI/APFS Big Sur
  • Inland Professional 256GBM 256GB SSD, Bay 2, EFI/APFS Catalina
  • Inland Professional 256GBM 256GB SSD, Bay 1, EFI/APFS Mojave
  • HGST 0F22408 4TB HDD, Bay 4, EFI/APFS Mojave
  • Seagate ST3000DM008 3TB HDD, Bay 3, EFI/APFS Mojave
NVMe:
  • (see first item under Disks)
PCIe:
  • AMD RX570 4GB, slot 1
  • (NVMe, slot 3)
  • Sonnet Allegro PCIE-USB31-X3, slot 4
USB:
  • Apple wired keyboard
    • Logitech wired trackball (on built-in Apple keyboard hub)
  • KVM switch
    • Wired keyboard
    • Logitech M570 wireless trackball (Unifying interface)
  • USB3 hub
    • 128GB USB3 flash drive, Windows exFAT
    • 64GB USB3 flash drive, High Sierra HFS+
    • 32GB USB3 flash drive, Catalina HFS+
  • 32GB USB3 flash drive, Windows FAT32
  • Sabrent USB3/SATA3 adapter
    • Inland Professional 256GBM 256GB SSD, EFI/APFS High Sierra

I may or may not include username attribution in the public table; if you'd rather remain anonymous, just PM me your results, let me know you'd like anonymity, and I'll include your results without attribution.

Thanks in advance. If you're unable or unwilling to get that level of detail, please post whatever you can, and I'll include your results as best I'm able.
Click to expand...
@Syncretic - should you also collect OC Version?
 
  • Like
Reactions: Syncretic
khronokernel

khronokernel

macrumors 6502
Sep 30, 2020
278
1,425
Alberta, Canada
sfalatko said:
@Syncretic - should you also collect OC Version?
Click to expand...
OpenCore version would have little effect as it's run under UEFI space and should have little impact version to version with kernel space. A more useful data point would be what kexts are being injected with OpenCore in addition to latebloom, as this can help correlate kexts that are conflicting with latebloom or hampering the boot process
 
  • Like
Reactions: startergo, Ausdauersportler and cdf
S

sfalatko

macrumors 6502a
Sep 24, 2016
642
365
@Syncretic - another thing I noticed. I booted three times in a row from a cold boot with 100, 20 and had hangs. I thought something was wrong as I didn't see the hook message. I realized I had set debug=0 (had been running with it on). I changed that to debug on and had two straight cold boot successes. I will test some more but thought I would mention that.
 
tsialex

tsialex

Contributor
Jun 13, 2016
13,455
13,601
khronokernel said:
OpenCore version would have little effect as it's run under UEFI space and should have little impact version to version with kernel space. A more useful data point would be what kexts are being injected with OpenCore in addition to latebloom, as this can help correlate kexts that are conflicting with latebloom or hampering the boot process
Click to expand...
Just to add, another thing that is useless is to report the spoofed EFI release. The real one matters, not the spoofed one.
 
  • Like
Reactions: HuRR
Syncretic

Syncretic

macrumors 6502
Original poster
Apr 22, 2019
311
1,533
sfalatko said:
@Syncretic - another thing I noticed. I booted three times in a row from a cold boot with 100, 20 and had hangs. I thought something was wrong as I didn't see the hook message. I realized I had set debug=0 (had been running with it on). I changed that to debug on and had two straight cold boot successes. I will test some more but thought I would mention that.
Click to expand...
(Per your suggestion, I added "OC version" to the template; @khronokernel makes a good point about its likely irrelevance, but at this point, every data point is welcome.)

If lb_debug=1 works better than lb_debug=0, you might consider trying a slightly higher latebloom= value (add maybe 5-10ms). The only difference is the amount of time consumed by a call to printf() (plus related screen-handling overhead).
 
  • Like
Reactions: HuRR
Ausdauersportler

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
During update to Monterey Beta 3 I got these messages:

Code: 
_____[ !!! *** latebloom *** !!! ]: Hook byte pattern not found, HOOK NOT PLACED. ...---...

Code: 
2021-07-14 23:54:44.565164+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Starting.
2021-07-14 23:54:44.571580+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: boot-args = latebloom=100 lb_range=20 lb_debug =1 keepsyms=1 debug=0x100 -lilubetaall -v
2021-07-14 23:54:44.575444+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: based on boot-args, using delay of 100 ms.
2021-07-14 23:54:44.579452+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: delays will be random, between 80 and 120 ms.
2021-07-14 23:54:44.583751+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Start - First time through, trying to place hook...
2021-07-14 23:54:44.588456+0200 0x72       Default     0x0                  0      0    kernel: (latebloom)
_____[ !!! *** latebloom *** !!! ]: Hook byte pattern not found, HOOK NOT PLACED. ...---...
2021-07-14 23:54:51.924195+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Start - First time through, trying to place hook...
2021-07-14 23:54:52.020288+0200 0x72       Default     0x0                  0      0    kernel: (latebloom)
_____[ !!! *** latebloom *** !!! ]: Hook byte pattern not found, HOOK NOT PLACED. ...---...
2021-07-14 23:55:00.324751+0200 0x2f0      Default     0x0                  0      0    kernel: (latebloom) <compose failure [UUID]>
2021-07-14 23:55:00.324769+0200 0x2f0      Default     0x0                  0      0    kernel: (latebloom) <compose failure [UUID]>
2021-07-14 23:55:00.324777+0200 0x2f0      Default     0x0                  0      0    kernel: (latebloom) <compose failure [UUID]>
2021-07-14 23:55:00.333817+0200 0x74       Default     0x0                  0      0    kernel: (latebloom) <compose failure [UUID]>
2021-07-14 23:55:00.334962+0200 0x74       Default     0x0                  0      0    kernel: (latebloom) <compose failure [UUID]>
2021-07-14 23:55:00.334967+0200 0x74       Default     0x0                  0      0    kernel: (latebloom) <compose failure [UUID]>
2021-07-14 23:55:15.241104+0200 0x8c1      Default     0x0                  0      0    kernel: (latebloom) <private>
2021-07-14 23:55:15.241746+0200 0x8bf      Default     0x0                  0      0    kernel: (latebloom) <private>
2021-07-14 23:55:15.248134+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::init start
2021-07-14 23:55:15.248444+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::init super init result 1
2021-07-14 23:55:15.248475+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::Start Started
2021-07-14 23:55:15.248618+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::SetProperties start
2021-07-14 23:55:15.248781+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::Start Status of RegisterService == 0
2021-07-14 23:55:15.251255+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::NewUserClient Creating New User Client
2021-07-14 23:55:15.251321+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialClient::init initializing Serial Client
2021-07-14 23:55:15.251434+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialClient::init initialized Serial Client
2021-07-14 23:55:15.251447+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialDriver::NewUserClient Created New User Client with status 0
2021-07-14 23:55:15.251457+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialClient::Start Starting to create Serial Client
2021-07-14 23:55:15.251467+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialClient::Start done creating client with status 0
2021-07-14 23:55:15.251862+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialClient::ExternalMethod name <private>
2021-07-14 23:55:15.251873+0200 0x8dd      Default     0x0                  0      0    kernel: (latebloom) [IOUserUSBHostHIDDevice.cpp:504][0x100000448] Open interface: 0x10000035b
2021-07-14 23:55:15.251887+0200 0x8e1      Default     0x0                  0      0    kernel: (latebloom) IOUserBluetoothSerialClient::createTerminal got called to create new ports

Last boot into Monterey Beta 2 gave this:

Code: 
2021-07-12 22:14:40.603530+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Starting.
2021-07-12 22:14:40.610110+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: boot-args = latebloom=100 lb_range=20 lb_debug =1 keepsyms=1 debug=0x100 -lilubetaall -v
2021-07-12 22:14:40.613973+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: based on boot-args, using delay of 100 ms.
2021-07-12 22:14:40.617989+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: delays will be random, between 80 and 120 ms.
2021-07-12 22:14:40.622288+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Start - First time through, trying to place hook...
2021-07-12 22:14:40.625873+0200 0x72       Default     0x0                  0      0    kernel: (latebloom) _____[ !!! *** latebloom *** !!! ]: Hook placed successfully.  Count = 0
 
Last edited:
Syncretic

Syncretic

macrumors 6502
Original poster
Apr 22, 2019
311
1,533
I have updated Post #1 with latebloom version 0.19, which adds support for Monterey Beta 3. If you're not running Monterey Beta 3, there is no need to update/upgrade the kext; there is no new functionality added in this version.

My thanks to @Ausdauersportler for noticing the problem and providing some quick testing.
 
  • Like
Reactions: Ausdauersportler
StarPlayrX

StarPlayrX

macrumors member
Jul 13, 2021
40
31
My best results and system:

latebloom=120 lb_range=40 lb_debug=1 kext-dev-mode=1 -v

Last three warm reboots successful on Monterey Beta 2 (21A5248p)! started with 100, 20, tried other numbers with little success especially if I 250, 500, 1000 with no randomization, and tried a variation of 100/20 with 120/40 and am every pleased with the results. This seem to give a great variation / stagger start on the PCIe delays. Randomization seems to work best on Monterey. Will test 11.5 GM when it's out.

  • MacPro 3,1 Early 2008
  • Not using OCLP, using BigMac2 direct install instead. Have late bloom kext loading in /Library/Apple/System/Library/Extensions and updated KCs and kcditto using BigMac2
  • BootROM version MP31.006C.B05
  • CPU 2 x Intel(R) Xeon(R) X5482 @ 3.20GHz, Original
  • Note: Machine has Bad Serial #, got blown out, replaced it w/ original, but since then no messages or hand off. Do not know if that affects anything boot wise, but wanted to make a note of it.
  • BigMac2 running Monterey Beta 2, 12.0 Beta (21A5248p)
  • Memory count 56GB, 8 x 6GB, 2 x 4GB, 800Mhz DDR2 FB-DIMM
  • WiFi (802.11ac/BT4LE Combo card iMac style, Broadcom Wi-Fi (0x14E4, 0x111), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1703.6)), upgrade
  • Bluetooth 4LE, upgrade v150 c9317, BRCM20702 Hub
  • Disks (4TB SSD, 1TB Each, +250GB PCIe Slot 3, +250GB PCIe Slot 4)
    • StarTech RAID 0 Enclosed Drive Bay 1, two 500GB Samsung 850 EVO SSDs, Striped 1TB
    • StarTech RAID 0 Enclosed Drive Bay 2, two 500GB Samsung 850 EVO SSDs, Striped 1TB
    • StarTech RAID 0 Enclosed Drive Bay 3, two 500GB Samsung 870 EVO SSDs, Striped 1TB
    • StarTech RAID 0 Enclosed Drive Bay 4, two 500GB Samsung 860 EVO SSDs, Striped 1TB
    • OWC Accelsior S PCIe card, Sandisk Ultra 250Gb SDD, Slot 3, 4x, 2.5 GT/s
    • OWC Accelsior S PCIe card, Samsung Apple SSD, Slot4, 4x, 2.5 GT/s
  • PCIe devices/location:
    • AMD Radeon RX 580, Sapphire, slot 1
    • Red USB 3.0 card, 4 Ports, 0x1b73, 0x1100 slot 2 (I forget the brand but it's pretty common)
    • OWC Accelsior S PCIe card, slot 3
    • OWC Accelsior S PCIe card, slot 4
  • USB devices (including external storage):
    • USB2.0 Hub (Switch) UGREEN Brand - 2.0 Hub is Required for Monterey Beta 2
      • Apple Magic Keyboard with Numeric Pad
      • Apple Magic Trackpad 2
 
Last edited:
  • Like
Reactions: Pri-est and Syncretic
Macschrauber

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
Syncretic said:
I'm confused, and I'm guessing I'm not the only one...
Click to expand...
The W3690 is the "Single Processor" variant of the X5690, you cannot have two of them in a dual cpu board.

those terminal commands output amount and type of processors

Code: 
sysctl -n hw.packages
sysctl -n machdep.cpu.brand_string
 
  • Like
Reactions: StarPlayrX
S

sfalatko

macrumors 6502a
Sep 24, 2016
642
365
@Syncretic - So another interesting item - from a run with 100/20 150/20 [Edit - the verbose output doesn't lie and I had moved to 150 after several failures at 100] and a hang I had at least one “loop” out of order in the verbose output. There is PCI LOOP # 63 then 65, 66, 67, and 68 and then 64 which was where it hung. I ended up with the no boot symbol.

I’m not sure it matters but another data point. Other times when it panics it seems to nave been right after the two Intel Ethernet lines. This boot attempt makes it past that but then fails (it appears) when the PCI LOOP is out of order.


Out of Order PCI LOOP.png
 
Last edited:
  • Like
Reactions: Syncretic
J

joevt

macrumors 604
Jun 21, 2012
6,968
4,262
Maybe the loop counter is incremented on entry but the message is output near exit?
Maybe there should be reentrancy counter added - increment it at entry and decrement it at exit - if it's greater than 1 then it means more than one is happening at the same time.
 
kkinto

kkinto

macrumors regular
Apr 29, 2011
228
63
Hi Guys, firstly, thanks for this!

Installed 11.4 (installer) from 11.2.3 to NVME 1TB to test. Install went perfectly, no hitches with soft boot. Was pleasantly surprised because Mac is full up with PCI cards! Chose migration to xfer from sata SSD 11.2.3 (CD Bay) and went to bed. Woke up to prohibit sign (obviously did a reboot during migration?). Hard shutdown, waited, booted into OC picker, selected the recently installed 11.4 on NVMe and booted successfully, with Mac announcing migration successfully completed when booted and entered setup. Haven't restarted again yet but will monitor.

Checker script: "latebloom is loaded"
Used 200/20 & debug=1, -v

Quick question - white apple logo on grey during start w/progress? is that normal? Starts out black, verbose on. Never seen a white apple logo on grey bkgnd before!

----------------------
mid 2010 Mac Pro 5,1
BootROM v: 9144.0.7.1.0. (Martin 0.71 Config with factory Wifi/Bluetooth factory patch)
2 x 3.33 GHz X5680
4 x 16GB 1066
WiFi factory
Bluetooth factory
1 x factory DVD R
1 x WD WDS 1 TB SSD in CD 2 Bay. (OS Big Sur 11.2.3) APFS
Int Bay 1 - Samsung 840 EVO 512 SSD SATA (formatter Mojave) APFS
Int Bay 2 - Seagate TGB formatter unknown (HFS+)
Int Bay 3 - Seagate TGB formatter unknown (HFS+)
Int Bay 4 - WD Blue 4TB formatter OS Mojave (HFS+)
PCI 1 - Radeon RX580 Sapphire / Dell 27U18 / DisplayPort
PCI 2 - IOCrest (SI-PEX40129) Dual NVMe Controller with 2 x Samsung 970 EVO NVMe 1TB 1 of them formatted by Mojave and other (current 11.4) formatted by BS 11.2.3 APFS (one is OS newly installed, other APFS data only)
PCI 3 - Sonnet Allegro Pro USB3.1 Type C (USB3C-4PM-E) -- 4 port 1 x USB3 Hub (2 x Seagate 3TB), 4TB External WD, spare formatters unknown / old (all HFS+)
PCI 4 - Sonnet Allegro Pro USB3 Type A -- 4 port 1 x USB 3 Hub (2 x 2TB Seagate in each of 2 bays), formatters unknown (Yosemite era), connector to dell monitor USB3 port (all HFS+)
Apple wired keyboard aluminium - via extender -> Mac Pro built in
USB3 Portable 2TB Seagate via Dell monitor -> Mac Pro built in
Logitech wireless mouse M325 (Unifying interface)

Booting 11.4 install with external Apple Wired (plastic) because one on USB extender does not work for OC booting

Hope that helps
 
Syncretic

Syncretic

macrumors 6502
Original poster
Apr 22, 2019
311
1,533
sfalatko said:
@Syncretic - So another interesting item - from a run with 100/20 and a hang I had at least one “loop” out of order in the verbose output. There is PCI LOOP # 63 then 65, 66, 67, and 68 and then 64 which was where it hung. I ended up with the no boot symbol.

I’m not sure it matters but another data point. Other times when it panics it seems to nave been right after the two Intel Ethernet lines. This boot attempt makes it past that but then fails (it appears) when the PCI LOOP is out of order.


View attachment 1806482
Click to expand...

That is arguably the most interesting thing I've seen yet (WRT this problem). That's going to get a lot of my attention for the next few days, I think...

...unless it turns out to be common. Has anyone else observed out-of-order PCI LOOP #s? The counter in question is incremented and then immediately printed, so the only way this should be able to happen is if (1) multiple threads are performing PCI bus scans simultaneously (possible because the workloop can launch separate scans for separate buses) and (2) the thread for loop #64 just happened to get interrupted between the increment and the output from printf. That's entirely possible, of course, but it feels odd, and I'm wondering if this might be part of the bigger problem (an untimely interrupt during a secondary bus probe).
 
  • Like
Reactions: cdf, vsc and PeterHolbrook
C

cdf

macrumors 68020
Jul 27, 2012
2,256
2,583
latebloom=100, lb_debug=1
MacPro 4,1 -> 5,1
BootROM: 144.0.0.0.0
CPU: 2 x X5680
RAM: 6 x 4 GB 1333 MHz DDR3
WiFi/BT: BCM94360CD
OC version: 0.7.1 (custom config)

Disks:
  • Kingston HyperX Predator 240 GB PCIe AHCI SSD, slot 3, EFI/APFS (formatted in Mojave)
  • Samsung 860 EVO 500 GB SSD, bay 2, EFI/APFS (macOS 11.4 installed in container formatted in Mojave)/NTFS (Windows 10)/EXT4 (Ubuntu 20.04)
  • Samsung 860 EVO 500 GB SSD, bay 1, EFI/APFS (formatted in Mojave)
  • Apple SuperDrive (Hitachi GH41N) optical drive, ODD 1
PCIe:
  • Radeon RX 580 8 GB, slot 1
  • AHCI SSD (see above), slot 3
  • GC-TITAN RIDGE (rev 1), slot 4
USB:
 
Last edited:
  • Like
Reactions: Syncretic
C

cdf

macrumors 68020
Jul 27, 2012
2,256
2,583
sfalatko said:
from a run with 100/20 and a hang I had at least one “loop” out of order in the verbose output.
Click to expand...
Interesting. But are you sure this is not from a run with 150? All the messages indicate a delay of 150 ms.
 
C

cdf

macrumors 68020
Jul 27, 2012
2,256
2,583
kkinto said:
Quick question - white apple logo on grey during start w/progress? is that normal? Starts out black, verbose on.
Click to expand...
This has been a minor issue since Big Sur. It occurs when booting in verbose mode and also during installations and updates.
 
  • Like
Reactions: kkinto
S

sfalatko

macrumors 6502a
Sep 24, 2016
642
365
cdf said:
Interesting. But are you sure this is not from a run with 150? All the messages indicate a delay of 150 ms.
Click to expand...
Well then - it was from a run of 150/20. I had moved to 150 after several failures at 100 and I thought this was from one of the 100 runs but the verbose output doesn't lie....I have edited the post.

Thanks @cdf
 
haralds

haralds

macrumors 68030
Jan 3, 2014
2,993
1,253
Silicon Valley, CA
Tried to upgrade from 11.2.3 to 11.4 and it ended up with a "forbidden" sign and a URL apple, com/support/startup during the second phase.

Using OC 0.69, Latebloom 0.19
latebloom=120 lb_range=40 lb_debug=1 kext-dev-mode=1

Any ideas?
 
Last edited:
khronokernel

khronokernel

macrumors 6502
Sep 30, 2020
278
1,425
Alberta, Canada
haralds said:
Tried to upgrade from 11.3.1 to 11.4 and it ended up with a "forbidden" sign and a URL apple, com/support/startup during the second phase.

Using OC 0.69, Latebloom 0.19
latebloom=120 lb_range=40 lb_debug=1 kext-dev-mode=1

Any ideas?
Click to expand...
Without verbose information, it's difficult to understand whether or not this was the race condition. Enable verbose (-v in boot-args) and see if you can replicate.

Also unrelated but why the usage of kext-dev-mode? It's been dead for ages (unless I'm missing something):

Kernel Extensions

Describes a security feature that protects against unauthorized access to system locations and processes.
developer.apple.com
 
  • Like
Reactions: Ausdauersportler
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom