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

Add constants for macOS 15/Sequoia support #10

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

AlfCraft07
Copy link

No description provided.

@vit9696
Copy link
Collaborator

vit9696 commented Aug 11, 2024

Was it tested? Could you provide debug logs with -liludbgall liludump=120?

@AlfCraft07
Copy link
Author

Was it tested? Could you provide debug logs with -liludbgall liludump=120?

Unfortunately I have no computers using NVMe, but I saw a couple of posts on Reddit from people being able to load the original version using -lilubetaall

@vit9696
Copy link
Collaborator

vit9696 commented Aug 11, 2024

Being able to load does not mean the kext works.

@EAZYBLACK
Copy link

Was it tested? Could you provide debug logs with -liludbgall liludump=120?

Tested it, Sequoia Beta 7, works fine
I have one nvme intenso and one nvme crucial p3, both work fine
Lilu_1.6.8_24.0.txt

@vit9696
Copy link
Collaborator

vit9696 commented Aug 29, 2024

To be honest, it does not seem to be working. In the logs we have the following lines (copied from various places in the log):

NVMeFix    disasm: @ (DBG) Failed to find ANS2MSIWorkaround
NVMeFix   feature: @ (DBG) ProcessSyncNVMeRequest failed
NVMeFix     nvmef: @ (DBG) Failed to configure APST with 0xe00002c7
NVMeFix        pm: @ registerPowerDriver failed with 0xe00002c2
NVMeFix        pm: @ Failed to initialise power management

They signalise that NVMeFix is not working as intended. While your SSDs work fine, I believe NVMeFix does nit change anything in their behaviour. I.e. they work as good and as bad as without NVMeFix.

@EAZYBLACK
Copy link

To be honest, it does not seem to be working. In the logs we have the following lines (copied from various places in the log):

NVMeFix    disasm: @ (DBG) Failed to find ANS2MSIWorkaround
NVMeFix   feature: @ (DBG) ProcessSyncNVMeRequest failed
NVMeFix     nvmef: @ (DBG) Failed to configure APST with 0xe00002c7
NVMeFix        pm: @ registerPowerDriver failed with 0xe00002c2
NVMeFix        pm: @ Failed to initialise power management

They signalise that NVMeFix is not working as intended. While your SSDs work fine, I believe NVMeFix does nit change anything in their behaviour. I.e. they work as good and as bad as without NVMeFix.

I tested on monterey and same stuff happen as u said above
So i dont think this is because sequoia
Lilu_1.6.8_21.6.txt

@vit9696
Copy link
Collaborator

vit9696 commented Sep 9, 2024

That only means that macOS 14 is broken as well.

@AlfCraft07
Copy link
Author

That log is from Monterey, not Sonoma

@sandr8
Copy link

sandr8 commented Oct 1, 2024

Any update on this?

@MatteoBax
Copy link

MatteoBax commented Nov 2, 2024

Was it tested? Could you provide debug logs with -liludbgall liludump=120?

My NVMe SSD isn't supported by this kext so I don't know if the logs are actually correct.
Lilu_1.6.9_24.0.txt

@EAZYBLACK
Copy link

Why not merge it , since same log shows in monterey and sequoia, ANS2MSIWorkaround is probably broken in big sur+

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

Successfully merging this pull request may close these issues.

6 participants