3.0.0 have some problem

myselfghost commented 3 years ago

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

PLTorrent commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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

myselfghost commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

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

profzei commented 3 years ago

@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 commented 3 years ago

Updated EFI release 3.1.0 and notes!

PLTorrent commented 3 years ago

@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 commented 3 years ago

there is no discrete GPU in your Laptop?

My Matebook X Pro i5 has an Nvidia MX150 inside

PLTorrent commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 / Matebook-X-Pro-2018

3.0.0 have some problem #186