Contribute
Register

<< Solved >> Do the Samsung 970 EVO Plus drives work ? New Firmware Available 2B2QEXM7

Status
Not open for further replies.
All Monterey Betas have worked fine for me with these drives.
Like a boot disk? I tried everything and I couldn't in Montery, it works perfectly as a second disk, but not for booting, very slow at startup, and very unstable, but it could be my hardware. I decided to change the boot disk and bought a WESTERN_DIGITAL SSD BLACK SN850 NVME M.2 500GB PCIE 4.0, works great with Montery.
 
Last edited:
Like a boot disk? I tried everything and I couldn't in Montery, it works perfectly as a second disk, but not for booting, very slow at startup, and very unstable, but it could be my hardware. I decided to change the boot disk and bought a WESTERN_DIGITAL SSD BLACK SN850 NVME M.2 500GB PCIE 4.0, works great with Montery.
I use both a WD SN750 and an EVO Plus and in both cases they work just fine.
 
I use both a WD SN750 and an EVO Plus and in both cases they work just fine.

May I ask with your SN750 if you have particular settings re: sleep or enabling/disabling TRIM, etc?

Also, do you use NVMEfix.kext or not?

Having panic issues with my SN750 that only are resolved with clean installs every so often and I'm out of ideas on what to try next. I see people using the SN750's very successfully so I'm hoping I just have something configured wrong. Thank you!
 
May I ask with your SN750 if you have particular settings re: sleep or enabling/disabling TRIM, etc?

Also, do you use NVMEfix.kext or not?

Having panic issues with my SN750 that only are resolved with clean installs every so often and I'm out of ideas on what to try next. I see people using the SN750's very successfully so I'm hoping I just have something configured wrong. Thank you!
I think I have trim enabled if it is not now it was in the past never saw issues. My system sleeps very well and quickly like 15 or 20 mins. I do not use the nvmefixup.kext. The only thing that has ever made my system panic is enabling XMP in the bios and if I OC my CPU. I have my memory bus clocked manually.
 
I think I have trim enabled if it is not now it was in the past never saw issues. My system sleeps very well and quickly like 15 or 20 mins. I do not use the nvmefixup.kext. The only thing that has ever made my system panic is enabling XMP in the bios and if I OC my CPU. I have my memory bus clocked manually.

Thank you! I really appreciate the reply. That’s now the second confirmation of people having great success with this drive but not using NVMeFixup - Maybe I was never supposed to be using it and I’m an idiot. I have removed it and I’m going to see how it goes. Thank you again
 
Thank you! I really appreciate the reply. That’s now the second confirmation of people having great success with this drive but not using NVMeFixup - Maybe I was never supposed to be using it and I’m an idiot. I have removed it and I’m going to see how it goes. Thank you again
I have never used NVMeFixup, with the SN750 in 500gb or 1tb. Also I Never used it with Samsung Evo Plus once the firmware came out...
 
I've noticed something very strange today, as I just experimented around with a fresh Monterey install on a T480s using the 970 Evo Plus 1TB. First of all, I've already mentioned this in another thread, but I still want to state it again:

With the Samsung SSDs, I found myself to *need* to load NvmExpressDxe.efi from the OpenCore Released Drivers in order to get the disk to show up at all in the installer. Don't need this with a WD-Blue NVMe for example. I also add NVMeFix.kext for good measure.

But then, I also experienced tremendous boot times, unbearable... But I saw that these BRCM...-stall timeout messages appeared again, so I decided to unload *all* WiFi&BT related kexts (Fixup, Injector, Store, Patch, ...). Now, it boots up in a matter of a few seconds. With those kexts loaded, system preferences was also almost unusable, since some sub-menus relied on the bluetooth or wifi settings, and they then crashed the whole menu.

No idea why that is yet, just want to share this since I don't think that the 970 Evo Plus 1TB with upgraded firmware (bootable upgrade ISO to be found online), plus the needed Driver and Kext has any issues, as it works for me now too.

// Edit 1:

Loading AirportBrcmFixup.kext and it's plugin AirPortBrcmNIC_Injector.kext is okay, just make sure you don't load AirPortBrcm4360_Injector.kext. So it seems that the troublemaker is once again bluetooth.
 
Last edited:
just make sure you don't load AirPortBrcm4360_Injector.kext. So it seems that the troublemaker is once again bluetooth.
Do you think this kext is at fault for the excessively long boot times in Monterey (For Samsung NVMe) many are experiencing.
 
@trs96

Either the AirPortBrcm4360_Injector.kext, or everything related to BrcmPatchRAM. For the former, it's extremely easy to miss to disable it, since a "OC Clean Snapshot" in OpenCore re-sets all values back to default, re-enabling the kext.
 
I now know what I did wrong regarding bluetooth:

On Monterey, don't use BrcmBluetoothInjector.kext but do use BlueToolFixup.kext instead. With this, WiFi and BT are fully working, and boot is still at around 16s till' login screen. Happy with that! :)
 
Status
Not open for further replies.
Back
Top