Another drive-by; time seems to be in short supply these days. I may be making some headway with apfs.kext, so stay tuned for updates. Fingers crossed.
Re: on-/off-topic discussion
As far as I'm concerned, meaningful discussion of anything related to the boot-time race condition (including latebloom itself) is fair game in this thread. "Meaningful" meaning something potentially informative or productive, not just moaning. Note that based on what we (think we) know, a system that successfully boots to the login screen has survived the race condition (for this boot, anyway), and anything that happens after that
should be unrelated - therefore, discussion of bluetooth problems and sluggishness and app misbehavior is off-topic here, unless you can somehow directly associate it with the race condition or latebloom.
(Short version: on-topic discussion is welcomed and encouraged, off-topic is discouraged. I'm not around very much right now to steer the thread, so you folks are on the honor system for staying on-topic. ;-)
@Syncretic If possible, could you insert the version(s) of OC recommended for running latebloom in the first post? I'm on v6.7, unsure if that will work?
I am not an OpenCore expert, especially about which versions support what, so your question might be better directed to someone who is. However, all that's required here is that OpenCore can load a simple kext, and as far as I know, pretty much every version of OpenCore can do that, so just about any version should do the trick. I'm running 0.6.8, so I'd imagine your 0.6.7 should work just fine. (And as always, I am prepared to be completely wrong.)
I am willing to test this as I don't use OpenCore. Can a kind soul elaborate on this a bit:
How to install? Setting the paramters … and so on.
I have only ever booted Big Sur via OpenCore, so I don't know what might break by doing this, but: when I've experimented with replacing Big Sur system kexts, and when I've added kexts to Big Sur outside of OpenCore, I've followed
these instructions from
@khronokernel, which have worked perfectly. Again, that's still booting with OpenCore, so I don't know if something in those instructions would break a non-OpenCore boot, but it may be worth a try (or perhaps someone else can chime in here and clarify that).
Note that you'll need to set any boot-args manually, using
sudo nvram boot-args={your boot-args}, since OpenCore won't be setting them for you. With no relevant boot-args, latebloom will use a delay of 60ms, no variation, and no per-loop debug messages.
@Syncretic is it possible to format the kext zip file similar to Acidanthera format? Latebloom-0.19-RELEASE.zip and Latebloom-0.19-DEBUG.zip, ideally, you should have a Github repo to make available the releases and keep track of all changes.
I'm not sure how renaming the zip file helps anything, but since it doesn't really change my workflow, I'll start naming them as you describe. Note that at present, I have no plans to produce separate release and debug versions, so they'll all be named one way or the other (I'll have to think about which name is more appropriate). A github repository is a good idea, when I have some time - I'm in serious need of a bunch of 48-hour days right about now, just to get caught up. (I seem to be in "I'll sleep when I'm dead" mode...)
I am getting a 4,1 in about a week. I will probably be keeping it at 4,1 because of the slower RAM and CPUs that I have. Can always up the firmware later.
More data is always welcome. I don't expect the native 4,1 to behave any differently from a 4,1->5,1 or an actual 5,1, but being wrong is where all the interesting stuff comes from, and where the fun begins. I look forward to hearing your results.
EDIT:
@gradyg22 - is your system a 4,1->5,1 or a 5,1? I'd like to put your results in the correct place.
