Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Boot process] Ignoring kextcache invocation from early boot #1346

Closed
dreamwhite opened this issue Dec 2, 2020 · 20 comments
Closed

[Boot process] Ignoring kextcache invocation from early boot #1346

dreamwhite opened this issue Dec 2, 2020 · 20 comments

Comments

@dreamwhite
Copy link

dreamwhite commented Dec 2, 2020

Hi there,
I don't even know if this can be considered as an issue, but I've noticed that while booting macOS Big Sur 11.0.1 (20B29) on my Dell Inspiron 5370 with OpenCore 0.6.3 and latest kexts (EFI), the boot process hangs itself for circa 5 seconds on the string Ignoring kextcache invocation from early boot. I don't care too much about boot-times since 20 seconds is a reasonable time, but wanted to elaborate on that """bug""". Do you have any idea?
Thank you so much and have a nice day ^^

@telepati
Copy link

telepati commented Dec 3, 2020

I have that too. Mine taking 10 sec. But, I am not sure this is related to OC.
ASUS TUF Z390, 9900K, ASUS RX 560
OC 0.6.4, macOS Big Sur 11.1

@zhen-zen
Copy link

zhen-zen commented Dec 4, 2020

Have the same issue with a partition from beta 1 to 10. After that I did a clean install for the release and it disappears. Are yours upgraded from beta as well?

@dreamwhite
Copy link
Author

Have the same issue with a partition from beta 1 to 10. After that I did a clean install for the release and it disappears. Are yours upgraded from beta as well?

I've dirty upgraded from Catalina 10.15.7 (19H2) to Big Sur 11.0.1 (20B25)

@nikhil19rathore99
Copy link

I have that too. Mine taking 10 sec. But, I am not sure this is related to OC.
ASUS TUF Z390, 9900K, ASUS RX 560
OC 0.6.4, macOS Big Sur 11.1

I think u haven't enable trim thats why it takes 10 sec otherwise it takes 20+ sec

@telepati
Copy link

telepati commented Dec 5, 2020

I think u haven't enable trim thats why it takes 10 sec otherwise it takes 20+ sec

TRIM is auto-enable on NVME. You don't need an extra step for TRIM on Catalina and Big Sur. But this problem is not related to TRIM.

@dreamwhite
Copy link
Author

I think u haven't enable trim thats why it takes 10 sec otherwise it takes 20+ sec

I don't think that TRIM is the cause of that issue, since NVMe, as @telepati said have TRIM enabled OOB.
Below my System Report infos about NVMe drives attached on my laptop ._.

image

@telepati
Copy link

telepati commented Dec 6, 2020

Could this problem be due to different APFS driver values and required values?

Screen Shot 2020-12-06 at 19 36 49

@dreamwhite
Copy link
Author

Could this problem be due to different APFS driver values and required values?

Screen Shot 2020-12-06 at 19 36 49

I don't think so. If you look at the highlighted string it says:

Found APFS driver vXXXXXXX/20201123

2020-11-23 is the release date of the driver you're using.
If we have to apply that logic, then the string after required 11111111111111/ can be interpreted as "the minimum version of apfs.efi driver is the one release on 2018-06-21. That condition is true so allow the boot, else fail"

@seungjunProgramming
Copy link

Me too.
I'm not using nvme, so I think it's not 'cause nvme drives.
I'm having this problem with m.2 sata3 ssd

@dreamwhite
Copy link
Author

Update

After upgrading to OpenCore 0.6.4 (as well as the kexts) I'm still experiencing a break of a few seconds on the string `Ignoring kextcache invocation from early boot.

However, compared to OpenCore 0.6.3, the interruption takes a few seconds less

@seungjunProgramming
Copy link

Update

After upgrading to OpenCore 0.6.4 (as well as the kexts) I'm still experiencing a break of a few seconds on the string `Ignoring kextcache invocation from early boot.

However, compared to OpenCore 0.6.3, the interruption takes a few seconds less

Me too.
It takes less time than 0.6.3

@seungjunProgramming
Copy link

Update

After upgrading to OpenCore 0.6.4 (as well as the kexts) I'm still experiencing a break of a few seconds on the string `Ignoring kextcache invocation from early boot.

However, compared to OpenCore 0.6.3, the interruption takes a few seconds less

However, still taking about 5~10secs

@telepati
Copy link

telepati commented Dec 9, 2020

I'm not using nvme, so I think it's not 'cause nvme drives.

I am using NVME and I still have this issue. It takes about 10/15 sec.

@vit9696
Copy link
Contributor

vit9696 commented Dec 9, 2020

The issue looks like a bug on Apple side. Please report to Apple.

@vit9696 vit9696 closed this as completed Dec 9, 2020
@telepati
Copy link

telepati commented Feb 2, 2021

Setting "SetApfsTrimTimeout" to 999 disables this problem and shortens the boot time.

@dreamwhite
Copy link
Author

Setting "SetApfsTrimTimeout" to 999 disables this problem and shortens the boot time.

Sorry for the late reply: I tried this trick but nothing changed. The boot process still hangs for a few seconds before proceeding.
Again, I don't care much about this but just wanted to get why it hangs

@McDonnellTech
Copy link

Setting "SetApfsTrimTimeout" to 999 disables this problem and shortens the boot time.

This solution did the trick for me. No longer any hang at all at "Ignoring kextcache invocation from early boot"

@YaPaY
Copy link

YaPaY commented Jul 8, 2021

Setting "SetApfsTrimTimeout" to 999 disables this problem and shortens the boot time.

nothing changes by me

@dreamwhite
Copy link
Author

Setting "SetApfsTrimTimeout" to 999 disables this problem and shortens the boot time.

nothing changes by me

Neither do I. I simply swapped the NVMe from a Sabrent Rocket NVMe to a Western Digital Black SN750 and the boot-process is definitely faster, despite still hanging for a few seconds on Ignoring kextcache invocation from early boot

@1alessandro1
Copy link

I think all of this is TRIM related. Setting 999 on SetApfsTrimTimeout disables TRIM since it's a very short timeout, so the SSD can behave differently (hanging or not hanging) due to the supported/unsupported nature in IONVMeFamily....

Before making any future purchase, I recommend everybody to check this post

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

9 participants