3.0.0 have some problem #186

myselfghost · 2021-09-23T02:57:48Z

Update from 2.4 to 3.0.0，When the computer starts, the computer will crash when you go to the login interface

samwzlim · 2021-09-23T04:02:49Z

Update from 2.4 to 3.0.0，When the computer starts, the computer will crash when you go to the login interface

Can you provide a screenshot of the error you are facing? It's difficult to tell what you mean by 'crashing on login interface'.

samwzlim · 2021-09-23T04:04:54Z

Upon updating to the latest EFI release, I'm getting this error when trying to boot (during Huawei logo screen). Not sure what went wrong, all I did was replace my previous EFI with the latest one.

linshixiong · 2021-09-23T05:14:43Z

I have the same problem, computer freeze and restart after logging in

samwzlim · 2021-09-23T05:19:08Z

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick for me; the machine now boots without any errors. However, is it safe to leave SecureBootModel at Disabled? I had a look through the guide to enable BIOS Secure Boot with OpenCore, and it doesn't seem like a recommended thing to do. However, I solely run macOS on my machine (no dualboot), so I dont have to be worried about enabling secure boot right?

samwzlim · 2021-09-23T05:55:19Z

Alright, I'm experiencing freezing issues as well; happens a few minutes after logging in. The system will stop responding and I'm forced to restart it. Compared to the previous EFI, this release is much more unstable. I'm currently on macOS Monterey Beta 6

ldan93 · 2021-09-23T07:32:13Z

I also had to disable SecureBoot, but I haven't noticed any kind of instability at the moment with release 3.0.0 ... (Big Sur 11.6)

Edit : I have updated my MLB, SystemSerialNumber and SystemUUID values, I don't know if this is related...

BigEmperor26 · 2021-09-23T10:47:00Z

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick for me; the machine now boots without any errors. However, is it safe to leave SecureBootModel at Disabled? I had a look through the guide to enable BIOS Secure Boot with OpenCore, and it doesn't seem like a recommended thing to do. However, I solely run macOS on my machine (no dualboot), so I dont have to be worried about enabling secure boot right?

Also setting to j132 works. Check the guide to enable SecureBoot with OpenCore in this repo, just follow steps from 1 to 4

profzei · 2021-09-23T13:54:31Z

It's quite weird that

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick

Did someone have tried to reset NVRAM at first reboot? Honestly, I don't know if it could do the trick since with these settings I never had any issue for

Monterey Beta 5 + update OTA to Monterey Beta 6
a clean install of Big Sur 11.6 (which is now my running system)

Moreover, in "official" OpenCore Configuration.pdf, the setting Default points to x86legacy which is the minimum required for running Big Sur (and then Monterey)... the fact that setting j132 is working and Default not seems to point out that macOS didn't recognize your system as Big Sur but as older...
For this reason, I suggested to try to reset your NVRAM.
If, instead, you are running macOS Catalina, then it is obvious that the setting Default is wrong, but all my EFI are meant for Big Sur+ (then I'll add the changes needed for Catalina...)

Did everyone update MLB, SystemSerialNumber and SystemUUID values? Honestly I don't remember whether these values are checked (or not) during AppleSecureBoot... "the default ones" are clearly not acceptable anymore!
Honestly, if those parameters could be relevant then the setting j132 should not be working...

this release is much more unstable

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

BigEmperor26 · 2021-09-23T14:40:12Z

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

Keep the hard work. Love what you are doing.

I didn't update MLB SystemSerialNumber SystemUUID, i kept the old ones with new SMBIOS so I didn't have to resign on iServices.

I don't have fully SecureBoot enabled, so I'm unable to confirm wether these values are checked during AppleSecureBoot

myselfghost · 2021-09-23T23:57:06Z

It's quite weird that

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick

Did someone have tried to reset NVRAM at first reboot? Honestly, I don't know if it could do the trick since with these settings I never had any issue for

Monterey Beta 5 + update OTA to Monterey Beta 6

a clean install of Big Sur 11.6 (which is now my running system)

Moreover, in "official" OpenCore Configuration.pdf, the setting Default points to x86legacy which is the minimum required for running Big Sur (and then Monterey)... the fact that setting j132 is working and Default not seems to point out that macOS didn't recognize your system as Big Sur but as older...
For this reason, I suggested to try to reset your NVRAM.
If, instead, you are running macOS Catalina, then it is obvious that the setting Default is wrong, but all my EFI are meant for Big Sur+ (then I'll add the changes needed for Catalina...)

Did everyone update MLB, SystemSerialNumber and SystemUUID values? Honestly I don't remember whether these values are checked (or not) during AppleSecureBoot... "the default ones" are clearly not acceptable anymore!
Honestly, if those parameters could be relevant then the setting j132 should not be working...

this release is much more unstable

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

I update MLB, SystemSerialNumber and SystemUUID values and restart. There is no option for reset NVRAM in opencore with 3.0.0. the computer will crash when go to the login interface

I updated the EFI in the bootable USB flash drive to version 3.0.0 and booted from the USB flash drive, the installation process would also crash.

myselfghost · 2021-09-24T00:32:06Z

have reset NVRAM ,also crash.

linshixiong · 2021-09-24T01:04:30Z

Still crash after resetting nvram

profzei · 2021-09-24T06:19:31Z

the computer will crash when go to the login interface

For Login interface do you mean the screen where you insert your password after all the boot process with loading bar under apple sign? ...or are you improperly referring to OpenCanopy boot picker where you choose to boot or not OpenCore?

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash?
Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100?
Could you report them, please?

myselfghost · 2021-09-24T07:57:00Z

the computer will crash when go to the login interface

For Login interface do you mean the screen where you insert your password after all the boot process with loading bar under apple sign? ...or are you improperly referring to OpenCanopy boot picker where you choose to boot or not OpenCore?

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash?
Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100?
Could you report them, please?

the screen where you insert your password.

debug log :
1: https://imgtu.com/i/4BbKfJ

2: https://imgtu.com/i/4BbRhQ

profzei · 2021-09-24T14:51:29Z

@myselfghost Thank you for your report!

the screen where you insert your password.

To my knowledge, it should not be related to enabling SecureBootModel key to Default value

In fact your two images taken from debug log point out to a fatal error (Kernel Panic) due to your nvme... It is a well known issue in hackintosh world. References are:

in my homepage: search for Notes: NVMe SSD support
official thread
Official fix is reported in my Notes: NVMe SSD support or in WhateverGreen Official Known Issues

Try if the official fix is working for you otherwise, please, report your issue in official thread asking if there could be a correlation between SecureBootModel flag and such an issue to acidanthera team .
Let me know whether it works!
Btw, what are your nvme specifics? ...and did you make an internal install?

Edit #1: Maybe there could be a relation between Apple snapshots (made on filesystem i.e. on your nvme) and your trim specifics: try also to disable trim as suggested in the same thread...

Edit #2: Could anyone who had trouble enabling SecureBootModel key as Default share its NVMe specifics (manufacturer + model), please?

samwzlim · 2021-09-24T23:44:55Z

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

No, don't apologize! I really appreciate your hard work even though this issue just a side project. Without your repo I would hardly manage to hackintosh my machine.

@profzei Regarding the NVMe specifics, my SSD is the WD Black SN750. I changed the stock SSD to this as my previous one was dead and this particular model was highly recommended by the hackintosh community. FYI, I am currently on macOS Monterey Beta 6.

In fact, I am now greeted with a new error while booting with SecureBootModel set to Default:

According to Apple's Support page, this happens when the macOS version/build is not something the machine can use? The solution provided was to use Disk Utility in Recovery to repair the startup disk and if that didn't work, reinstall macOS, but I didn't go through the hassle of doing either.

Setting SecureBootModel to Disabled bypasses this for me. However, similarly to the others, my machine freezes, although it happens after I'm logged in.

If you need any further report/help let me know!

profzei · 2021-09-25T13:01:29Z

If you need any further report/help let me know!

In my opinion, it should be useful if all people, who had issues with Release v. 3.0.0, could share their report about the following:

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash?
Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100?

samwzlim · 2021-09-25T14:10:28Z

If you need any further report/help let me know!

In my opinion, it should be useful if all people, who had issues with Release v. 3.0.0, could share their report about the following:

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash?

Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100?

Upon booting, it's stuck here for a while:

Then after that, it shows this screen which I mentioned earlier:

Kokkolabs · 2021-09-26T11:54:26Z

Just updating to 3.0.0 and all go well, zero issues.
Boot is really faster, thank you :)

samwzlim · 2021-09-26T12:06:04Z

Just updating to 3.0.0 and all go well, zero issues.
Boot is really faster, thank you :)

What macOS version are you on? Did you directly upgrade from previous EFI without making any changes? If not, what changes did you make?

Kokkolabs · 2021-09-26T12:11:44Z

Monterey beta 5 and i change only serialnumber.
Edit1: i have beta 5
Edit2: updated today latest beta, all ok.
Edit3: Still beta 5. I start update and go out, it wont update some reason.

profzei · 2021-09-26T14:22:46Z

Boot is really faster, thank you :)

@Kokkolabs Thank you!

@samwzlim

Your first image is "readable": system is loading/injecting Bluetooth driver... it "hangs" since, as you know, support for Monterey Beta6+ is "not optimal"...
Your second image is "not readable": it seems there could be something related to WiFi but I'm not sure...
Please, try a second shot...

Monterey beta 5

"All the patches" I wrote were tested on Monterey Beta 4 - 5 - 6 without any particular issues... now I replaced Monterey with Big Sur 11.6 and, by my side, all is working fine!

samwzlim · 2021-09-26T14:58:41Z

@profzei I totally forgot to disable IntelBluetoothInjector.kext in config.plist as I'm still on Monterey! I gave it another shot but the machine still does not boot with SecureBootModel set to default. It now shows a different error log:

Regarding the 2nd image, there is nothing I can do about the clarity of the image, as it is blurry irl as well. However, it seems to me that logs on the 2nd image are the same as that of the 1st image.

profzei · 2021-09-26T15:37:53Z

@samwzlim

I gave it another shot but the machine still does not boot with SecureBootModel set to default. It now shows a different error log:

Honestly, I do not see any relevant issue reported in your system boot log: as you could see also my system boot log (Big Sur 11.6) reports some "fails" for nvme but they are not relevant since boot phase is fine...

2021-09-26 16:38:13.524930+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> AppleNVMe Assert failed: ( fClients->getCount ( ) == 0 )
2021-09-26 16:38:13.524934+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> ErrorExit
2021-09-26 16:38:13.524938+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> file: /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeBlockStorageDevice.cpp
2021-09-26 16:38:13.524943+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> line: 2406
2021-09-26 16:38:13.524944+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> 
2021-09-26 16:38:13.526059+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> AppleNVMe Assert failed: result
2021-09-26 16:38:13.526061+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> ErrorExit
2021-09-26 16:38:13.526064+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> file: /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/AppleNVMeSMARTUserClient.cpp
2021-09-26 16:38:13.526067+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> line: 79
2021-09-26 16:38:13.526068+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> 
2021-09-26 16:38:13.527210+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> AppleNVMe Assert failed: result
2021-09-26 16:38:13.527213+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> DetachUserClient
2021-09-26 16:38:13.527218+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> file: /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeBlockStorageDevice.cpp
2021-09-26 16:38:13.527223+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> line: 2352
2021-09-26 16:38:13.527224+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert>

Regarding the 2nd image, there is nothing I can do about the clarity of the image, as it is blurry irl as well. However, it seems to me that logs on the 2nd image are the same as that of the 1st image.

I agree with you! ...but this also means I do not have any clues for your issue...

samwzlim · 2021-09-27T04:33:53Z

@profzei Would it be possible for you to share the exact EFI you used when you were still on Monterey beta 6? Hopefully I might be able to find some differences between mine and yours and fix the issue.

profzei · 2021-09-28T18:01:14Z

my SSD is the WD Black SN750

Maybe it could be useful monitor also this issue

Would it be possible for you to share the exact EFI you used when you were still on Monterey beta 6?

I need to check its presence in my backup (i.e all the EFI): it should be the same config.plist I included into my release 3.0.0 (there is no reason for including any changes to it since the same file is working fine , for me, both for Monterey beta 6 and Big Sur 11.6 which I installed later...), but I surely checked it asap

sev7en2507 · 2021-09-29T02:11:50Z

Good morning,
thanks for the thread, I tried multiple times the procedure (very well done... thanks!) but I am stuck on that:

I am using OpenCore 0.7.3 and I don't how to go ahead...

Thanks for your support.

profzei · 2021-09-29T12:12:52Z

@sev7en2507

I guess you installed successfully macOS since there is no macOS Installer icon in your OpenCanopy boot picker...
I really don't know why two windows partition are visible (Windows + EFI? or Windows + Data?)... but nevermind
Enter your Windows partition and add OpenCore entry to UEFI boot following this guide

stevezhengshiqi · 2021-09-29T12:50:05Z

SecureBootModel should be kept as Disabled for general use. Default does not apply to all users, and it will cause KPs on certain machines. Unless user test by themselves that Default is safe, I agree that Disabled should be used for general public. Disabled is safe for all macOS versions.

profzei · 2021-09-29T13:11:08Z

@stevezhengshiqi
Thank you very much for your advice since I consider very valuable your opinion!
I'll update failsafe condition setting SecureBootModel key as Disabled in my next update...

I'd like your opinion, if possible, about our situation i.e. all Huawei Matebook X Pro 2018 users:

the settings I shared in my last release are those recommended in OpenCore Configuration.pdf for enabling Apple SecureBootModel
if those settings are working fine for my Matebook X Pro, why other users (using the same identical machine) could report issues?
In your experience, which could be the possible KP causes that may arise from identical machines?

Edit:

When I say identical machines I mean that all our Matebook X Pro 2018 are the same except NVMe SSD... Is NVMe SSD a possible KP source just enabling Apple SecureBootModel in your opinion? If yes, there are bug reports I may consult?
The last factor of diversity (among our Matebook X Pro) could be BIOS version... Could it be a possible source for a KP just enabling Apple SecureBootModel?

All other hardware is soldered...

There is no mention in OpenCore Configuration.pdf about these two possible sources of KP related to Apple SecureBootModel... just to be honest, there is no mention in such document about possible issues enabling Apple SecureBootModel...

PLTorrent · 2021-10-18T20:44:29Z

@profzei
Just downloaded 3.1.0 again, made the changes you have mentioned in the install guide and also the the ones above as well as BIOS settings and I can report that still there is no change. When trying to run the install my LiteOn NVMe is still not visible in the installer. When trying to boot there is still the prohibitory circle.

When I go back to 2.4.0 the system boots ok.

I have bios 1.37 but this should not have any impact afaik.

Not sure how to diff those two version since they are so far apart.

Maybe you have in your archives some working configs for OC 0.7.1 - 0.7.4 that I could use to pinpoint where exactly it stopped working?

profzei · 2021-10-18T21:51:22Z

Maybe you have in your archives some working configs for OC 0.7.1 - 0.7.4 that I could use to pinpoint where exactly it stopped working?

I was too confident: I had a single crash (playing with Monterey during summer) with no backup... sigh!

When trying to run the install my LiteOn NVMe is still not visible in the installer.

I guess you are trying to re-install Big Sur 11.6 over its existing APFS volumes... aren't you?
If I'm right:

you didn't create new FAT32 partitions for a new/clean Big Sur install nor converted them into APFS
when did you create your current APFS volumes? i.e. with which macOS version?
maybe it could be an APFS driver issue and in this case (if you are using latest OC/Driver/HfsPlus.efi driver) you should modify config.plist for skipping APFS integrity/validity check (which has been added by OpenCore Team probably during this summer...):

<key>UEFI</key>
	<dict>
		<key>APFS</key>
		<dict>
			<key>EnableJumpstart</key>
			<true/>
			<key>GlobalConnect</key>
			<false/>
			<key>HideVerbose</key>
			<true/>
			<key>JumpstartHotPlug</key>
			<true/>
			<key>MinDate</key>
			<integer>-1</integer>
			<key>MinVersion</key>
			<integer>-1</integer>
		</dict>

Please, let me know if this fixes your current issue... honestly I'm going out of ideas...

PLTorrent · 2021-10-19T00:09:10Z

@profzei (@elliotnash)

Did some diffing between 2.4.0 and 3.1.0. This is the culprit:

config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x0) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x4) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1d,0x0) - pci-aspm-default

After removig those 3.1.0 boots BigSur 11.6 on my machine without prohibitive circle.

Not sure what those are and why they were added, off to sleep, debugged this for 12+ hours ;P

Will do some more checking tomorrow. ;]

elliotnash · 2021-10-19T01:19:08Z

Thanks @PLTorrent, just tried removing those and 3.1.0 is also working great for me on 11.6 :)

myselfghost · 2021-10-19T02:54:15Z

@profzei

I also passed the test and verification

BigSur 11.6 ,EFI 3.1.0. the computer will not crash .

but need to delete :

config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x0) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x4) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1d,0x0) - pci-aspm-default

thanks @profzei @PLTorrent

samwzlim · 2021-10-19T05:59:36Z

Can confirm removing:

config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x0) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x4) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1d,0x0) - pci-aspm-default

allows my machine to boot up with no issues. Huge thanks to all of you!

Edit: In order to update to macOS 12.0.1, I had to set SecureBootModel to Default, otherwise the update wouldn't show in system preferences.

PLTorrent · 2021-10-19T13:25:50Z

I guess you are trying to re-install Big Sur 11.6 over its existing APFS volumes... aren't you?

@profzei

I can now confirm that removing those:

config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x0) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1c,0x4) - pci-aspm-default
config.plist -> DeviceProperties -> Add -> PciRoot(0x0)/Pci(0x1d,0x0) - pci-aspm-default

also resolves this issue, and now my internal drive is visible in the install mode. ;]

profzei · 2021-10-19T13:29:53Z

@PLTorrent @myselfghost @samwzlim @elliotnash

Please see my reply for thanking the great support received by @PLTorrent here

@PLTorrent @myselfghost @samwzlim @elliotnash

Please could you try to report your specific SSD model?
and also your BIOS version?
and also your processor architecture i.e. i5 or i7?

Edit: if you would like to cooperate, I'll wait for your replies and then I'll update current 3.1.0 release with fixes

rohirrim27 · 2021-10-19T14:48:42Z

Dropping in my response here, thank you @profzei for investigating!

Please could you try to report your specific SSD model?
Mac OS - external Sandisk extreme SSD, Windows - internal Toshiba

and also your BIOS version?
1.37

profzei · 2021-10-19T14:52:38Z

@rohirrim27 Sorry, do you have an i5 or i7 processor? I'm asking since an i7 is paired with a discrete gpu i.e. an nVIDIA MX150

samwzlim · 2021-10-19T16:28:42Z

@profzei
Please could you try to report your specific SSD model?
WD Black SN750 500 GB

and also your BIOS version?
1.36

and also your processor architecture i.e. i5 or i7?
i5 with integrated graphics

PLTorrent · 2021-10-19T18:11:25Z

@profzei

Intel Core i5-8250U @ 1.60 GHz
Micron memory 8192MB @ 2133 GHz
LiteOn CA3-8D256 NVMe SSD (256GB)
BIOS reported model: MACH-WX9
BIOS version: 1.37
No dGPU on board, only iGPU.

Just checked that even leaving pci-aspm-default for the non-existent on my system dGPU prevents my system from booting. So all those entries must be removed.

I also now can set Misc -> Security -> SecureBootModel to Default in 3.1.0 and system boots without issue.

myselfghost · 2021-10-20T00:03:29Z

@profzei

Intel Core i5-8250U @ 1.60 GHz
Micron memory 8192MB @ 2133 GHz
WD Black SN730 256 GB
BIOS version: 1.37
No dGPU on board, only iGPU.

elliotnash · 2021-10-20T00:06:16Z

I've also got an i5, no dGPU
bios 1.37
Sabrent rocket q 1tb ssd

profzei · 2021-10-20T08:30:01Z

@elliotnash @myselfghost @PLTorrent @samwzlim @rohirrim27

Thank you very much for your report!

What can we deduce?

all your models are based on i5 architecture: there is no discrete GPU card so trying to activate ASPM on a fake device (in your case) is definitely not a good idea and will definitely cause issues... I think we can agree on that point.
your BIOS version is 1.37 (only one has 1.36) while mine is 1.28: ASPM is definitely related to BIOS version since we are trying to force correct power management on macOS on PCI buses (which then influenced power management for the device attached to those buses i.e. for example NVMe SSD)
all of you have good NVMe SSDs which should support very well ASPM
critical point is what @PLTorrent reported:

LiteOn CA3-8D256 NVMe SSD (256GB)

Its NVMe SSD is the same model which is on my laptop, but, in my case, I can enable ASPM on PCIe bus where my NVMe SSD is attached without any issues: this could be interpreted as a regression on 1.37 BIOS release respect to 1.28

However, I'll remove code related to forcing ASPM support and I add a note on updated 3.1.0 release

@PLTorrent

I also now can set Misc -> Security -> SecureBootModel to Default in 3.1.0 and system boots without issue.

This is another good news!

profzei · 2021-10-20T09:24:29Z

Updated EFI release 3.1.0 and notes!

PLTorrent · 2021-10-20T15:39:45Z

@profzei

Status report:
I have spent some more time focused on downgrading BIOS. Had to go back to Windows 11 for that but I managed to do so and finally my MBXP is back on 1.28 BIOS. ;] I am currently reinstalling BigSur 11.6. Still had to disable ASPM for the installer to see my drive. I think the whole issue might be connected to what you have deduced here:

"all your models are based on i5 architecture: there is no discrete GPU card so trying to activate ASPM on a fake device (in your case) is definitely not a good idea and will definitely cause issues... I think we can agree on that point."

I really think that this is the clue of the problem. Could you please describe how to remove all things peritnent to dGPU from the OC config please? I will do so, and then test re-enabling the ASPM.

I am even willing to go back to the newest bios afterwards, which will mean reinstalling the Win11 but that's not a big problem. ;]

AshleyMiller9696 · 2021-10-20T16:34:37Z

there is no discrete GPU in your Laptop?

My Matebook X Pro i5 has an Nvidia MX150 inside

PLTorrent · 2021-10-20T17:08:08Z

@profzei

Status Update:
Just tested BigSur 11.6 with pci-aspm-default on BIOS 1.28 and no joy... so it is not the BIOS. It is the dGPU (or lack of thereof) Therefore I have done the following modifications (I am using OpenCore Configurator):

Disable SSDT-DDGPU.aml in ACPI -> Add
Delete PciRoot(0x0)/Pci(0x1c,0x0) and PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0) in DeviceProperties -> Add
Add pci-aspm-default with data value 02000000 for PciRoot(0x0)/Pci(0x1c,0x4) and PciRoot(0x0)/Pci(0x1d,0x0) in DeviceProperties -> Add

Now device boots without any issues with ASPM enabled ;]

One thing that got me wondering is why you did not add pci-aspm-default with data value 02000000 for PciRoot(0x0)/Pci(0x1d,0x2) in DeviceProperties -> Add i.e. enable ASPM for the WiFi Card?

P.S. In case someone needs it I can provide BIOS downgrade steps... ;]

profzei · 2021-10-20T19:06:09Z

@PLTorrent

Now device boots without any issues with ASPM enabled ;]

Very good!

One thing that got me wondering is why you did not add pci-aspm-default with data value 02000000 for PciRoot(0x0)/Pci(0x1d,0x2) in DeviceProperties -> Add i.e. enable ASPM for the WiFi Card?

Two reasons:

AirportItlwm had dropped down support for ASPM on release 2.X+
I tried to enable it even before "dropping down", but my system froze... so no joy... ;)

P.S. In case someone needs it I can provide BIOS downgrade steps... ;]

Steps have been published on r/MatebookXPro more than a couple of times... but maybe they could be added in Wiki section...

@AshleyMiller9696

My Matebook X Pro i5 has an Nvidia MX150 inside

Honestly I don't know how many variants were manufactured...
Have you tried EFI release 3.0.0 or 3.1.0?
If yes:

did you have issues?
which BIOS version are you on?

PLTorrent · 2021-10-20T20:16:28Z

@profzei

Steps have been published on r/MatebookXPro more than a couple of times... but maybe they could be added in Wiki section...

Procedure I have discovered is quite simple (seems to be simpler than what at least I was able to find):

Steps depend on which version of BIOS we are interested in and must be performed in Windows 10/11:

1.29 - Simply download BIOS from here -> https://github.com/profzei/Matebook-X-Pro-2018/blob/master/Wiki/Bios/MateBook_X_Pro_BIOS_1.29.zip and just flash it. This version of BIOS uses Insyde flasher and version check is not implemented in this version. Using this version I was able to flash 1.29 over 1.37 on my machine. ;]

>1.29 - Downgrade to 1.29 and then use the later version you wish to flash. ;]

1.28 and earlier - Those BIOSes used Windows UEFI upgrade mechanism. Therefore we will need to download the BIOS (e.g. 1.28) from the Wiki of this repo -> https://github.com/profzei/Matebook-X-Pro-2018/blob/master/Wiki/Bios/MateBook_X_Pro_BIOS_1.28.zip as well as 1.29 mentioned earlier. Now we follow those steps:

unpack the 1.28 bios file using 7zip until we get the BIOS_Capsule.FD file.
run the 1.29 bios upgrade, wait for the prompt asking if we really want to install this BIOS, when the prompt appears do not click any button (leave it open)
search local computer for file H2OFFT-Wx64.exe. We should find it in some temp folder in the user homedir. Go to this directory. Inside should be unpacked files for the flashing tool and isflash.bin file
copy BIOS_Capsule.FD file to the directory found in the previous step and change its name to `isflash.bin' effectively overwriting the original file
go back to the open prompt and now press ok to flash
system will restart after a while and afterwards if everything is ok the flasher will show that it is flashing BIOS version 1.28 (in our case).

As usual when flashing BIOS have at least 30% battery and keep the AC attached.

myselfghost · 2021-10-21T00:56:27Z

I also passed the test and verification

Disable SSDT-DDGPU.aml in ACPI -> Add
Delete PciRoot(0x0)/Pci(0x1c,0x0) and PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0) in DeviceProperties -> Add
Add pci-aspm-default with data value 02000000 for PciRoot(0x0)/Pci(0x1c,0x4) and PciRoot(0x0)/Pci(0x1d,0x0) in DeviceProperties -> Add

profzei · 2021-10-21T16:31:59Z

@myselfghost
At this point I'll update note for EFI release v. 3.1.0 as soon as possible. Thank you!

@samwzlim
On Monday 25 October, final release for Monterey 12.0.1 will be published by Apple...
During last days I saw some/many troubles reported by users in acidanthera/bugtracker regarding Bluetooth managing...

What's your experience with Beta 10 or RC about Bluetooth?
Everything else was working very fine without any issues with previous betas... any regressions?

To anyone running Monterey Beta 10 or RC release:

BlueToolFixup.kext.zip

Please, try latest BlueToolFixup.kext: it is under testing since it should/could fix/mitigate atm Bluetooth issues:

Apple added a USB vendor id check in Monterey Beta 10+ releases and considers non-Brcm and non-CSR dongles as unsupported devices
this new BluetoolFixup.kext should disable the bluetoothd's vendor id check introduced in Monterey Beta 10+

Please, report here your feedback!

samwzlim · 2021-10-22T04:26:09Z

@profzei

What's your experience with Beta 10 or RC about Bluetooth?

Skipped Beta 10 but am currently on RC, bluetooth cannot be turned on although I was able to on Beta 6 and lower.

Everything else was working very fine without any issues with previous betas... any regressions?

So far everything seems to be working fine except for bluetooth.

To anyone running Monterey Beta 10 or RC release:

BlueToolFixup.kext.zip

Please, try latest BlueToolFixup.kext: it is under testing since it should/could fix/mitigate atm Bluetooth issues:

Apple added a USB vendor id check in Monterey Beta 10+ releases and considers non-Brcm and non-CSR dongles as unsupported devices

this new BluetoolFixup.kext should disable the bluetoothd's vendor id check introduced in Monterey Beta 10+

Please, report here your feedback!

After replacing the previous BluetoolFixup.kext with the one attached, bluetooth is usable once again!

profzei · 2021-10-22T12:59:11Z

After replacing the previous BluetoolFixup.kext with the one attached, bluetooth is usable once again!

Great news!
When you say it "is usable once again", does this mean you can toggle off AND then on Bluetooth without any issues?

samwzlim · 2021-10-22T13:11:45Z

After replacing the previous BluetoolFixup.kext with the one attached, bluetooth is usable once again!

Great news! When you say it "is usable once again", does this mean you can toggle off AND then on Bluetooth without any issues?

Forgot to mention, but nope, once I turn off Bluetooth, it cannot be turned on again until a restart, similar to previous Monterey beta versions.

profzei · 2021-10-22T13:29:36Z

Forgot to mention, but nope, once I turn off Bluetooth, it cannot be turned on again until a restart, similar to previous Monterey beta versions.

Ah, ok! Then we need to wait for a fix from OpenCore Team and/or OpenIntelWireless one-single-man-Team!

profzei mentioned this issue Oct 18, 2021

Prohibitory circle after upgrade #192

Closed

PLTorrent mentioned this issue Oct 19, 2021

3.1.0 Crash after 1-2 mins of startup #194

Closed

profzei mentioned this issue Oct 28, 2021

Bluetooth issue after Monterey upgrade with MacBookPro15,2 SMBIOS #201

Closed

3.0.0 have some problem #186

3.0.0 have some problem #186

Comments

myselfghost commented Sep 23, 2021

samwzlim commented Sep 23, 2021

samwzlim commented Sep 23, 2021

linshixiong commented Sep 23, 2021 • edited

samwzlim commented Sep 23, 2021 • edited

samwzlim commented Sep 23, 2021

ldan93 commented Sep 23, 2021 • edited

BigEmperor26 commented Sep 23, 2021

profzei commented Sep 23, 2021

BigEmperor26 commented Sep 23, 2021 • edited

myselfghost commented Sep 23, 2021

myselfghost commented Sep 24, 2021

linshixiong commented Sep 24, 2021

profzei commented Sep 24, 2021

myselfghost commented Sep 24, 2021 • edited

profzei commented Sep 24, 2021 • edited

samwzlim commented Sep 24, 2021 • edited

profzei commented Sep 25, 2021

samwzlim commented Sep 25, 2021

Kokkolabs commented Sep 26, 2021

samwzlim commented Sep 26, 2021

Kokkolabs commented Sep 26, 2021 • edited

profzei commented Sep 26, 2021 • edited

samwzlim commented Sep 26, 2021

profzei commented Sep 26, 2021

samwzlim commented Sep 27, 2021

profzei commented Sep 28, 2021

sev7en2507 commented Sep 29, 2021

profzei commented Sep 29, 2021

stevezhengshiqi commented Sep 29, 2021

profzei commented Sep 29, 2021 • edited

PLTorrent commented Oct 18, 2021

profzei commented Oct 18, 2021 • edited

PLTorrent commented Oct 19, 2021 • edited

elliotnash commented Oct 19, 2021 • edited

myselfghost commented Oct 19, 2021 • edited

samwzlim commented Oct 19, 2021 • edited

PLTorrent commented Oct 19, 2021

profzei commented Oct 19, 2021 • edited

rohirrim27 commented Oct 19, 2021

profzei commented Oct 19, 2021

samwzlim commented Oct 19, 2021

PLTorrent commented Oct 19, 2021 • edited

myselfghost commented Oct 20, 2021

elliotnash commented Oct 20, 2021

profzei commented Oct 20, 2021

profzei commented Oct 20, 2021

PLTorrent commented Oct 20, 2021

AshleyMiller9696 commented Oct 20, 2021

PLTorrent commented Oct 20, 2021 • edited

profzei commented Oct 20, 2021

PLTorrent commented Oct 20, 2021

myselfghost commented Oct 21, 2021

profzei commented Oct 21, 2021 • edited

samwzlim commented Oct 22, 2021 • edited

profzei commented Oct 22, 2021

samwzlim commented Oct 22, 2021

profzei commented Oct 22, 2021

linshixiong commented Sep 23, 2021 •

edited

samwzlim commented Sep 23, 2021 •

edited

ldan93 commented Sep 23, 2021 •

edited

BigEmperor26 commented Sep 23, 2021 •

edited

myselfghost commented Sep 24, 2021 •

edited

profzei commented Sep 24, 2021 •

edited

samwzlim commented Sep 24, 2021 •

edited

Kokkolabs commented Sep 26, 2021 •

edited

profzei commented Sep 26, 2021 •

edited

profzei commented Sep 29, 2021 •

edited

profzei commented Oct 18, 2021 •

edited

PLTorrent commented Oct 19, 2021 •

edited

elliotnash commented Oct 19, 2021 •

edited

myselfghost commented Oct 19, 2021 •

edited

samwzlim commented Oct 19, 2021 •

edited

profzei commented Oct 19, 2021 •

edited

PLTorrent commented Oct 19, 2021 •

edited

PLTorrent commented Oct 20, 2021 •

edited

profzei commented Oct 21, 2021 •

edited

samwzlim commented Oct 22, 2021 •

edited