OC fails to recognize boot drive after installation

[elfzweik]

Describe the bug I have already installed Monterey using the Profzei's EFI. Everything is satisfactory except that I cannot get sleep function well. So I want to have a try of your EFI. With my own SMBIOS info added to the config.plist, I copied the whole folder to my EFI partition. When rebooting, the system hangs after select the first icon of the OpenCore picker screen. The system will come back to the OpenCore picker in a few seconds.

To Reproduce Reboot the machine

Expected behavior Boot to my Monterey installation.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Monterey 12.3
• OpenCore 0.7.9

Additional context Add any other context about the problem here. Matebook X Pro 2018 CPU: I7-8550U Memory: 16GB 2133 SSD: 1TB Samsung 980 Pro

Hi, Tyler, ​ ​I have tried your version of config but still failed. The response is the same. After selecting Macos on OC picker, 5 lines shows for several seconds and come back to the picker screen. ​ ​I tried not including the Thunderbolt related 6 ssdts as my current config.plist does. The failure is the same. I also tried to ​set or unset the CFG lock quirks. But no any change. ​ ​I googled the screen message and found only 1 post reporting exactly the same as mine. But the cause for his problem is the memory incompatibility. Obviously I am not the case. ​ Then I tried to find the differences between your EFI and Profzei's EFI. Wow, so many differences ​in the config.plist, dsdt, ssdts. They are totally different EFI. I think I need to devote myself understanding Dortania's OpenCore Install Guide. I attached my config.plist in case you have time and interests to check it. ​ ​Thanks a lot for your time and patience. ​ ​Jeff Wang ​ ​ …

hmm. so let me tell you what. it probably does release to some sort of opencore quirk or memory setting. so maybe in the config. in any case, send me the EFI that boots for you. I will edit it to make the fixes for things that I did on this repo hopefully without breaking it

[tlefko]

Describe the bug I have already installed Monterey using the Profzei's EFI. Everything is satisfactory except that I cannot get sleep function well. So I want to have a try of your EFI. With my own SMBIOS info added to the config.plist, I copied the whole folder to my EFI partition. When rebooting, the system hangs after select the first icon of the OpenCore picker screen. The system will come back to the OpenCore picker in a few seconds.

To Reproduce Reboot the machine

Expected behavior Boot to my Monterey installation.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Monterey 12.3
• OpenCore 0.7.9

Additional context Add any other context about the problem here. Matebook X Pro 2018 CPU: I7-8550U Memory: 16GB 2133 SSD: 1TB Samsung 980 Pro

Morning! Okay, so I see you’ve listed the issue. This is trying to boot the installed macos on your ssd correct? Please try using an earlier release (for now) and send me the result. it’s a strange error.. this isn’t bapppening when trying to boot installer only the OS on the profzei drive?

[elfzweik]

Good Afternoon!. Thanks so much for your quick response.

This is trying to boot the installed macos on your ssd correct?

Right.

Please try using an earlier release (for now) and send me the result.

I changed to EFI 1.01 release. As usual, I download the zip file, unzip, and modify the SMBIOS info in the config.plist. Without any other change, I copied the whole OC folder to my EFI partition to replace the existing OC folder. The OC picker screen shows up correctly. When I select the first icon, there is no output, just black screen, so I have nothing to capture for your info. After several seconds, it goes back to OC picker screen again.

this isn’t bapppening when trying to boot installer only the OS on the profzei drive?

Nope. I can boot to my macos with Profzei's EFI and it works well, except for the abnormal sleep. The bluetooth doesn't work after a deep sleep. And 5-language warning screen shows when pushing power button after hibernation.

[tlefko]

Good Afternoon!. Thanks so much for your quick response.

This is trying to boot the installed macos on your ssd correct?

Right.

Please try using an earlier release (for now) and send me the result.

I changed to EFI 1.01 release. As usual, I download the zip file, unzip, and modify the SMBIOS info in the config.plist. Without any other change, I copied the whole OC folder to my EFI partition to replace the existing OC folder. The OC picker screen shows up correctly. When I select the first icon, there is no output, just black screen, so I have nothing to capture for your info. After several seconds, it goes back to OC picker screen again.

this isn’t bapppening when trying to boot installer only the OS on the profzei drive?

Nope. I can boot to my macos with Profzei's EFI and it works well, except for the abnormal sleep. The bluetooth doesn't work after a deep sleep. And 5-language warning screen shows when pushing power button after hibernation.

okay. this is the error (i think, maybe lol). try this. don’t modify the config, i think the editor you’re using is corrupting it. try booting with vanilla installation and let me know. if it works i’ll edit the config for you. Sometimes using like OC configurator with version mismatches can cause this.

[tlefko]

@elfzweik it could be, but I think these two things are the first steps. First of all let’s try clearing the NVRAM, or persistent memory. If this fails, we can explore the BIOS.

[elfzweik]

I have tried clearing NVRAM, no joy. I don't know how to clear persistent memory. Do you mean the kext cache? Could you give more hints?

By the way, I wonder how you upgrade the BIOS to 1.37. My PC Manager says 1.28 is the newest version. My MBXP is American version, I think, the last available model Huawei laptop in US.

[tlefko]

PS: Based on the SSD in your machine, it is possible you may need NVMEFix.kext to be set to enabled. @elfzweik You can either download the latest version or the may be one in Kexts already, and in the config. if so, just enable it with the checkbox. Hopefully this is the bug, it would make somewhat sense given my EFI booted the installer. I saw your post on Profzei’s repository. It’s super interesting the issue you laid out and Id love to look at the APFSTrim timeout values. Lastly, Deep Sleep, Broken Bluetooth After Sleep, and the language thingy (no clue at all what that is) are fixed in this repository🕹

Please understand, this project is the one he accuses of being a direct clone. Super interesting considering one doesn’t even boot. This repository wouldn’t exist if he had looked through the original changes and documented them. Instead, he pulled all his releases instead of implementing changes and cried about it. It’s unfortunate, but I need to state this as seeing his message on his front page is beyond offensive, and the amount of comments understanding/agreeing with his plight. I continue to run this repository because i’m appalled at his actions towards the community. Within this repository, despite my personal opinion on him he is credited as well. I would like nothing more than to fix this issue, solely for the improvements to make themselves apparent between the two repositories.

With this in mind, I can’t actually help you (or won’t rather) with profzei’s EFI. but, I’m more than happy to work with you within my repo files. I didn’t assume anyone would change the SSD, and thus didn’t prepare. Hopefully, we can document this, and publish in future versions.

You can also contact me directly via as email well. thanks! @elfzweik

On Wed, Apr 13, 2022 at 02:21 elfzweik @.***> wrote:

I have tried clearing NVRAM, no joy. I don't know how to clear persistent memory. Do you mean the kext cache? Could you give more hints?

By the way, I wonder how you upgrade the BIOS to 1.37. My PC Manager says 1.28 is the newest version. My MBXP is American version, I think, the last available model Huawei laptop in US.

— Reply to this email directly, view it on GitHub https://github.com/tlefko/Matebook-X-Pro-2018-Monterey/issues/6#issuecomment-1097603785, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHES3FIHOSRIBOEHN6IJLLVEZRXPANCNFSM5TAQYFMA . You are receiving this because you modified the open/close state.Message ID: @.***>

[tlefko]

PS: Based on the SSD in your machine, it is possible you may need NVMEFix.kext to be set to enabled. @elfzweik You can either download the latest version or the may be one in Kexts already, and in the config. if so, just enable it with the checkbox. Hopefully this is the bug, it would make somewhat sense given my EFI booted the installer. Lastly, Deep Sleep, Broken Bluetooth After Sleep, and the language thingy (no clue at all what that is) are fixed in this repository🕹 …

Check BIOS version within the BIOS itself, but to be entirely honest that’s not the issue most likely. I do just want to see the picker options as well if that’s okay. Within the config, if the kext doesn’t work we may need to make some changes.

Part of the increased boot time on Profzei’s repo could be partially attributed to the potential bluetooth issues, (failing to inject = hang). However, not entirely sure if this is the case.

Note: If you are coming from Profzei's repo, you will have two internal speakers in macOS. As I'm sure you've realized, these are the subwoofers separated from main speakers. Within this repo, they are all condensed into one internal speaker device so volume can be controlled normally. Feedback on the battery vs. the original repo is still needed but seems better.

Try this configuration file -- to boot config.plist.zip Here is my personal config file to try as well. these have differences within XCPM and CFG lock just to rule that out too.

myconfig.plist.zip

[elfzweik]

PS: Based on the SSD in your machine, it is possible you may need NVMEFix.kext to be set to enabled. @elfzweik You can either download the latest version or the may be one in Kexts already, and in the config. if so, just enable it with the checkbox. Hopefully this is the bug, it would make somewhat sense given my EFI booted the installer. I saw your post on Profzei’s repository. It’s super interesting the issue you laid out and Id love to look at the APFSTrim timeout values. Lastly, Deep Sleep, Broken Bluetooth After Sleep, and the language thingy (no clue at all what that is) are fixed in this repository🕹 Please understand, this project is the one he accuses of being a direct clone. Super interesting considering one doesn’t even boot. This repository wouldn’t exist if he had looked through the original changes and documented them. Instead, he pulled all his releases instead of implementing changes and cried about it. It’s unfortunate, but I need to state this as seeing his message on his front page is beyond offensive, and the amount of comments understanding/agreeing with his plight. I continue to run this repository because i’m appalled at his actions towards the community. Within this repository, despite my personal opinion on him he is credited as well. I would like nothing more than to fix this issue, solely for the improvements to make themselves apparent between the two repositories. With this in mind, I can’t actually help you (or won’t rather) with profzei’s EFI. but, I’m more than happy to work with you within my repo files. I didn’t assume anyone would change the SSD, and thus didn’t prepare. Hopefully, we can document this, and publish in future versions. You can also contact me directly via as email well. thanks! @elfzweik … On Wed, Apr 13, 2022 at 02:21 elfzweik @.> wrote: I have tried clearing NVRAM, no joy. I don't know how to clear persistent memory. Do you mean the kext cache? Could you give more hints? By the way, I wonder how you upgrade the BIOS to 1.37. My PC Manager says 1.28 is the newest version. My MBXP is American version, I think, the last available model Huawei laptop in US. — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHES3FIHOSRIBOEHN6IJLLVEZRXPANCNFSM5TAQYFMA . You are receiving this because you modified the open/close state.Message ID: @.>

Sorry to know you and Profzei had disputes. But I think as you credited his repo, you are not one of the guys he mentioned. In my case, I published a series of articles on a website. And after several months I found my articles are on lots of websites and for most of them the author is just changed to other name. I claimed to the administration of the website, and provided the screen capture of the data when my articles were published, as well as my photo id, as per the website's request. But my claim was rejected because they said I did not prove that the author (username) is me. LOL, I do not know how to prove it and have to give up.

[elfzweik]

PS: Based on the SSD in your machine, it is possible you may need NVMEFix.kext to be set to enabled. @elfzweik You can either download the latest version or the may be one in Kexts already, and in the config. if so, just enable it with the checkbox. Hopefully this is the bug, it would make somewhat sense given my EFI booted the installer. Lastly, Deep Sleep, Broken Bluetooth After Sleep, and the language thingy (no clue at all what that is) are fixed in this repository🕹 …

Check BIOS version within the BIOS itself, but to be entirely honest that’s not the issue most likely. I do just want to see the picker options as well if that’s okay. Within the config, if the kext doesn’t work we may need to make some changes.

Part of the increased boot time on Profzei’s repo could be partially attributed to the potential bluetooth issues, (failing to inject = hang). However, not entirely sure if this is the case.

Note: If you are coming from Profzei's repo, you will have two internal speakers in macOS. As I'm sure you've realized, these are the subwoofers separated from main speakers. Within this repo, they are all condensed into one internal speaker device so volume can be controlled normally. Feedback on the battery vs. the original repo is still needed but seems better.

Try this configuration file -- to boot config.plist.zip Here is my personal config file to try as well. these have differences within XCPM and CFG lock just to rule that out too.

myconfig.plist.zip

Thanks a lot. I will try and report the result.

[elfzweik]

Hi, Tyler,

​

​I have tried your version of config but still failed. The response is the same. After selecting Macos on OC picker, 5 lines shows for several seconds and come back to the picker screen.

​

​I tried not including the Thunderbolt related 6 ssdts as my current config.plist does. The failure is the same. I also tried to ​set or unset the CFG lock quirks. But no any change.

​

​I googled the screen message and found only 1 post reporting exactly the same as mine. But the cause for his problem is the memory incompatibility. Obviously I am not the case.

​

Then I tried to find the differences between your EFI and Profzei's EFI. Wow, so many differences ​in the config.plist, dsdt, ssdts. They are totally different EFI. I think I need to devote myself understanding Dortania's OpenCore Install Guide. I attached my config.plist in case you have time and interests to check it.

​

​Thanks a lot for your time and patience.

​

​Jeff Wang

​

​

On Apr 13 2022, at 5:07 PM, Tyler Lefko @.***> wrote:

PS: Based on the SSD in your machine, it is possible you may need NVMEFix.kext to be set to enabled. @elfzweik (https://github.com/elfzweik) You can either download the latest version or the may be one in Kexts already, and in the config. if so, just enable it with the checkbox. Hopefully this is the bug, it would make somewhat sense given my EFI booted the installer.

… (http://#)

Check BIOS version within the BIOS itself, but to be entirely honest that’s not the issue most likely. I do just want to see the picker options as well if that’s okay. Within the config, if the kext doesn’t work we may need to make some changes.

—

Reply to this email directly, view it on GitHub (https://github.com/tlefko/Matebook-X-Pro-2018-Monterey/issues/6#issuecomment-1098488342), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AFYZAWXZ22SE62XXXHXV4FTVE4ZR5ANCNFSM5TAQYFMA).

You are receiving this because you were mentioned.

[tlefko]

Hi, Tyler, ​ ​I have tried your version of config but still failed. The response is the same. After selecting Macos on OC picker, 5 lines shows for several seconds and come back to the picker screen. ​ ​I tried not including the Thunderbolt related 6 ssdts as my current config.plist does. The failure is the same. I also tried to ​set or unset the CFG lock quirks. But no any change. ​ ​I googled the screen message and found only 1 post reporting exactly the same as mine. But the cause for his problem is the memory incompatibility. Obviously I am not the case. ​ Then I tried to find the differences between your EFI and Profzei's EFI. Wow, so many differences ​in the config.plist, dsdt, ssdts. They are totally different EFI. I think I need to devote myself understanding Dortania's OpenCore Install Guide. I attached my config.plist in case you have time and interests to check it. ​ ​Thanks a lot for your time and patience. ​ ​Jeff Wang ​ ​ …

No worries, I totally get this. I’m honeslty really confused too, it probably does relate to some sort of opencore quirk that i’m not seeing. In any case, I do have an idea. Send me your existing EFI. let me see if I can work around it to make it a) compatible with the updates in this repo and b) still work

i know it’s profzei efis, but it’s fine. and trust me, originally that guy put MY NAME on the front page of his repo. as stealing it, not just general people. I found a different person with the same issue, so hoping to find a solution. the issue is 99% one of the quirks imo

@elfzweik just send me whatever current EFI you’re using. I can make changes to the config and files/DSDT without breaking it (hopefully)

The 5 lines are just the opencore lines before it’s even trying to boot macos, so it’s kernel panicking instantly. maybe related to virtual memory map settings, apple memory, etc. these are all quirks

[elfzweik]

Thank you so much. My EFI is here https://drive.google.com/file/d/1j2fLClx-jALOcP_4CVJ-OYYgC6CccFjX/view?usp=sharing

[vebbis321]

Thank you for your work! I have the exact same error. I tried to boot with the EFI you listed (tlefko) and the EFi in your release. The computer works perfect, but when I turn it off and starts it again I receive the same error as the image on top in this post.

[tlefko]

Thank you for your work! I have the exact same error. I tried to boot with the EFI you listed (tlefko) and the EFi in your release. The computer works perfect, but when I turn it off and starts it again I receive the same error as the image on top in this post.

Hey! so do you mind going into more detail exactly what’s happening? Is this a clean installation or one that used profzei EFI. I am trying to figure out what causes this as 3 people have bad this coming from profzei. I cannot replicate the issue 😂

[tlefko]

@elfzweik @vebbis321 Also please set ScanPolicy to zero in the config.plist you have and try booting. may work. Press space after to unhide any auxillery inputs

[elfzweik]

@tlefko I made the try, using the config you use. No improvement booting MacOS, but there is a change in the OC picker screen. In the before there shows only MacOS and Recover. This time my Windows bootloader shows there. Unfortunately, no joy. I cannot boot windows by selecting windows from OC picker. Blue screen. It is understandable, I noticed you used create mode for updateSMBIOSMode. The problem is windows still goes blue screen even when I select bootloader of windows from BIOS. After several times reboot and repair, I finally succeeded in entering windows desktop and change back the EFI. Interesting.

[tlefko]

wow I've never encountered this before thank you for noting that. Send me your bluetooth panel in your system information app

On Sat, Apr 16, 2022, 23:46 elfzweik @.***> wrote:

@tlefko https://github.com/tlefko I made the try, using the config you use. No improvement booting MacOS, but there is a change in the OC picker screen. In the before there shows only MacOS and Recover. This time my Windows bootloader shows there. Unfortunately, no joy. I cannot boot windows by selecting windows from OC picker. Blue screen. It is understandable, I noticed you used create mode for updateSMBIOSMode. The problem is windows still goes blue screen even when I select bootloader of windows from BIOS. After several times reboot and repair, I finally succeeded in entering windows desktop and change back the EFI. Interesting.

— Reply to this email directly, view it on GitHub https://github.com/tlefko/Matebook-X-Pro-2018-Monterey/issues/6#issuecomment-1100797012, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHES3F2YQOKYSZZ5LPCENLVFOCS7ANCNFSM5TAQYFMA . You are receiving this because you were mentioned.Message ID: @.***>

[elfzweik]

Here you are.

[tlefko]

Describe the bug I have already installed Monterey using the Profzei's EFI. Everything is satisfactory except that I cannot get sleep function well. So I want to have a try of your EFI. With my own SMBIOS info added to the config.plist, I copied the whole folder to my EFI partition. When rebooting, the system hangs after select the first icon of the OpenCore picker screen. The system will come back to the OpenCore picker in a few seconds.

To Reproduce Reboot the machine

Expected behavior Boot to my Monterey installation.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Monterey 12.3
• OpenCore 0.7.9

Additional context Add any other context about the problem here. Matebook X Pro 2018 CPU: I7-8550U Memory: 16GB 2133 SSD: 1TB Samsung 980 Pro

Hi, Tyler, ​ ​I have tried your version of config but still failed. The response is the same. After selecting Macos on OC picker, 5 lines shows for several seconds and come back to the picker screen. ​ ​I tried not including the Thunderbolt related 6 ssdts as my current config.plist does. The failure is the same. I also tried to ​set or unset the CFG lock quirks. But no any change. ​ ​I googled the screen message and found only 1 post reporting exactly the same as mine. But the cause for his problem is the memory incompatibility. Obviously I am not the case. ​ Then I tried to find the differences between your EFI and Profzei's EFI. Wow, so many differences ​in the config.plist, dsdt, ssdts. They are totally different EFI. I think I need to devote myself understanding Dortania's OpenCore Install Guide. I attached my config.plist in case you have time and interests to check it. ​ ​Thanks a lot for your time and patience. ​ ​Jeff Wang ​ ​ …

hmm. so let me tell you what. it probably does release to some sort of opencore quirk or memory setting. so maybe in the config. in any case, send me the EFI that boots for you. I will edit it to make the fixes for things that I did on this repo hopefully without breaking it

Hey, just a heads up this issue was fixed for the other guy by clean installing macOS with this EDI

[vebbis321]

@elfzweik @vebbis321 Also please set ScanPolicy to zero in the config.plist you have and try booting. may work. Press space after to unhide any auxillery inputs

It is 0, but I still get the image above. I used a clean install of your release the first time. Then I did the same thing only with the EFI you listed here as your personal one, but I still got the same error.

And I have of course generated my own SMBIOS.

[elfzweik]

I tried boot from usb to install the system. The install process is working. But at the restart, the same thing happens.

[tlefko]

@elfzweik please speak to @doggie13 whenever he has time, he manage to resolve this and get this up and running with me. The installer part he had a similar issue as well, but i'm still unsure as to how he fixed it / his whole process. When he has time, I believe he'll detail it all for you. Sorry for the wait, been super busy with exams for university.

[elfzweik]

@elfzweik please speak to @doggie13 whenever he has time, he manage to resolve this and get this up and running with me. The installer part he had a similar issue as well, but i'm still unsure as to how he fixed it / his whole process. When he has time, I believe he'll detail it all for you. Sorry for the wait, been super busy with exams for university.

@tlefko Thanks a lot for your help. I did not come for a period of time. Busy delivering a project. I will ask @doggie13 to see whether he can help. Thanks anyway!

[elfzweik]

@tlefko Surprising! When I download the latest release and install the MacOS with a clean format, the miracle happens. Now I enjoyed the correct function of sleep and hibernation, as well as the 4 speakers. It is such a wonderful experience. Thanks for your great work.

[elfzweik]

@tlefko And I got ACPI_BIOS_ERROR when booting windows via OC, as well as booting Ubuntu via OC. No problem directly boot windows. I changed the quirk UpdateSMBiosMode to Custom to avoid inject SMBios info, and set SyncRuntimePermissions quirk. After that Ubuntu is able to boot via OC. But Windows still fails. The rest that affects Windows booting leaves only SSDT. Have you met this problem? Do you have some idea what should I do?

[github-actions[bot]]

Stale issue message