Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
@dannytang

thanks for posting your result. Concise yet detailed.

So you shucked a Sabrent Rocket Pro. What do you end up re-purposing the enclosure? I might be completely off track.

Yeah, I shucked a Sabrent Rocket Pro. The original intention was to pull the drive out of the MacBook Pro and use it as an external drive when I upgraded to the 16" MacBook Pro, but ultimately decided to keep this one a little longer to see how the new keyboard played out. No I'm patiently hanging onto the enclosure to use with the eventual M2 16" MacBook Pro.
 
  • Like
Reactions: porg
This might be the “there is a pink elephant in the room” question:

How can it be that we observe that the combination of NVMeFix and SSdPmEnabler leads to a higher reduction of idle current than if we use just 1 of these?

According to the spec’s of the SSD’s there are usually 5 power states. 2 of them are related to idle. I cannot come up with a plausibel explanation for the combined effect. Is iStat Menus or SMC mislead? Is there solid proof that usage of both kext tools results in real lower power usage?

P.s. We are talking about digital electronics, not analog electronics. There should be no intermediate states possible.
 
Last edited:
I have a mid 2013 Macbook Air (i7-1.7ghz/8gb) on high sierra 10.13.6.
1) Does the method describe in the post below "Upgrading Boot ROM Version without upgrading to Big Sur" work for macbook air 2013 running high sierra?
#8,050
- That is to say, can I flash the boot rom in the Big Sur installer while I am running high sierra?
- I am hoping that this will sort out hibernation issues when I install an NVMe SSD, e.g. Crucial P2 1tb
- Another reason for high sierra is that Apple's technical specifications states that it requires 2gb of memory vs 4gb for Big Sur
2.1) Can anyone confirm that SsdPmEnabler has been successfully installed on mid 2013 / 2014 Macbook air running High Sierra / Big Sur / Catalina?
2.2) From reading recent posts, can I conclude that SsdPmEnabler does not work in reducing idle power consumption if I decide to stay on High Sierra OS?
2.3) Does this mean that I should move to Mojave / Catalina / Big Sur if I want to harness SsdPmEnabler's power saving prowess?
3.1) How is the UI performance and overall smoothness of high sierra vs catalina / big sur for the 2013 macbook air (i7-1.7ghz/8gb)?
- This post below mentions that big sur is more laggy than catalina 10.15.7 (on the 2015 macbook air i7/8gb)
#9
 
Hi guys,

This will certainly feel like a noob or silly question but how do I get SsdpmEnabler?

I've looked at the GitHub page but cannot find the file nor any way to download it...

Never mind, I finally opened my eyes and found the file... I'm not used to GitHub 🤪
 
Hi guys,

This will certainly feel like a noob or silly question but how do I get SsdpmEnabler?

I've looked at the GitHub page but cannot find the file nor any way to download it...

Never mind, I finally opened my eyes and found the file... I'm not used to GitHub 🤪
here you go.
 
is there a guide to installing a new ssd with big sur? i see a lot of posts about bootrom and nvmefix and im not sure what it all means, sorry

I have a macbook air 2015, and am looking to upgrade the ssd to a 500gb kingston a2000. my bootrom version is 425.0.0.0.0, is that a good thing?
i know i have to backup my data through something that isnt time machine, but then how am i supposed to access the data after installing ssd?
Don't feel bad if it takes a little more than what you wrote for help. I've been following this thread since there were maybe 3000 posts. It may take a while for someone to reply, only bc many have already asked your questions (I have too), and given there are like 8000 posts here, your answers probably lurk... and are answered more than once.

But... who has time to read 8000 posts! There are angels here who come in and out of this thread, who were probably in our shoes, and might randomly go back a few pages, see your commonly asked question (I say that with all due respect because I've done the same thing, and never felt I got it straight what to do, as some posts lead me to think it's plug and play, others do not, and that vagueness makes me stop!

Consequently, I have sat on my Sintech adapter, and new SSD, and been horrified I'll hurt my machine!

I have read in horror posts about kernel panics, been overwhelmed by screen shots of graphs and tests which I cannot comprehend, read about Boot Rom.

Boot Rom is way beyond my intelligence. I still don't know if I need to flash (mine is 199.0.0.0.0).

There is a physical device you can use, there are software solutions or patches with Terminal, and even a remote access or an in-the-machine down solution a sprightly volunteer here made, uploaded, and donated his/her time to avail... which, incidentally, I downloaded but couldn't figure out what to do with it after I had the thing.

So, I haven't touched my machine, or my Boot Rom either.

This thread's Wiki has a lower first number, e.g., so yours needs to be something like >124..., but I don't understand these numbers at all, and my machine (a mid-2015 15" 11,4) is still under AppleCare so am paranoid if I have a problem I might void my warranty. Lots of unknowns, and I know in good conscience if I was lucky enough to have the time to read all 8000+ posts, I'd find some--if not all--answers to my questions. (Nobody is paid to help, it's all a give and take thing, but this forum is above and beyond in terms of people and their generosity!)

So, hang in there, try reading backwards. That's what I do. I have always had replies to just about every stupid question conceivable—not just in this thread, but everywhere—so for you (and anyone else who is lost or confused), don't feel bad if it takes a while to figure it all out. You'l get the help you need, and odds are have success. I am just too reliant on my machine to risk losing it. That is my biggest hesitation.

Most here who have done this were going into unchartered waters, and took the plunge. I do not think this is a difficult thing to do, but everyone's experience may be different. Too many variables for each machine, person, etc.

I know I'm not answering your question, per se. This is just to make you (and me, maybe others) feel better :cool:
 
  • Like
Reactions: macpro_mid2014
What is the most updated version of the boot rom for an early 2015 13" MBP? Just upgraded to Big Sur 11.1 and boot rom is 425.0.0.0.0. Thanks!
 
You really should look into actual kernel panic logs inside Console.app before jumping to the conclusion that the installation of 3rd party SSDs is the culprit.

For area to apply Kapton tape, look at post #1 as a starting point. And exercise common sense from high school science class. Personally I don't think it hurts if you apply a bit more than you need.


The kernel panic is in the NVMe driver which isn't good news.

If you show AppleSSD is fine, then the machine (2014 13-inch) should be safe to assume okay. Next step will be borrowing a SSD listed in this table and see if it works or at the same time other models from 2013 to 2015 could report success (or failure) stories with these sticks:
  • Corsair MP510
  • Samsung 970 EVO Plus
  • Silicon Power A80
Looks like it'll take some time. To manage your expectation, there isn't much I could do in the kext at the moment.
Hi kvic,

Today I tested your SsdPmEnabler kext on my Mac with original Apple SSD and Big Sur 11.0.1. Installed SsdPmEnabler without any problem or KP. It seams to work perfectly on 2014 MBPr 13" with Apple SSD. Means problem was with Corsair and Samsung SSDs.
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
Frog:~ VAS$ log show --style syslog --last boot | grep \(SsdPmEnabler
2021-01-08 14:02:50.265408+0300 localhost kernel[0]: (SsdPmEnabler) Copyright (c) 2020-2021 kvic (https://github.com/kvic-z/SsdPmEnabler)
2021-01-08 14:02:50.265453+0300 localhost kernel[0]: (SsdPmEnabler) Enabled PCIe PM on SSD
Now my question is:
1. With Corsair and Samsung was the problem with NVME driver to reboot with installed SsdPmEnabler kext, but as I understand Apple SSD doesn't use NVME driver?
2. Been confirmed that Sabrent Rocket 1TB is ok to install SsdPmEnabler kext and my Corsair is completely the same memory, DRAM and Phison E12 controller, the only different can be the SSD firmware, Sabrent Rocket using ECFM12.3 and my MP510 has ECFM22.6.

Corsair Force MP510 1TB SSD kernel panic:
panic(cpu 0 caller 0xffffff801ef83d06): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x8 VID=0xffff DID=0xffff
. FW Revision=ECFM22.6\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.60.1/Common/IONVMeController.cpp:5472
Backtrace (CPU 0), Frame : Return Address
0xffffffa092513960 : 0xffffff801c8b9aed
0xffffffa0925139b0 : 0xffffff801c9fc6e3
0xffffffa0925139f0 : 0xffffff801c9ecd1a
0xffffffa092513a40 : 0xffffff801c85ea2f
0xffffffa092513a60 : 0xffffff801c8b938d
0xffffffa092513b80 : 0xffffff801c8b9678
0xffffffa092513bf0 : 0xffffff801d0be3ca
0xffffffa092513c60 : 0xffffff801ef83d06
0xffffffa092513c80 : 0xffffff801ef68427
0xffffffa092513de0 : 0xffffff801d01c795
0xffffffa092513e50 : 0xffffff801d01c696
0xffffffa092513e80 : 0xffffff801c8fe6b5
0xffffffa092513ef0 : 0xffffff801c8ff5c4
0xffffffa092513fa0 : 0xffffff801c85e13e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[008D1169-B6FD-39ED-9033-C67AC409031C]@0xffffff801ef61000->0xffffff801ef8afff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[E4DF1D8B-0DA9-33A8-A7B6-17DCA1678FC0]@0xffffff801dc59000->0xffffff801dc62fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9BA70327-883F-3E4F-960A-14203BB191FD]@0xffffff801de00000->0xffffff801de14fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D0F1BFB8-C28E-3E70-891B-73B783189394]@0xffffff801f22c000->0xffffff801f253fff
dependency: com.apple.iokit.IOReportFamily(47)[3A404946-7B6B-371A-A7B5-96E25F6F449D]@0xffffff801f262000->0xffffff801f264fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[AA8F8B9D-BA6E-3EBB-8195-4792042ADF71]@0xffffff801f34c000->0xffffff801f35dfff
Process name corresponding to current thread: kernel_task
Mac OS version:
20C69

Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x000000001c600000
KernelCache base: 0xffffff801c800000
Kernel slide: 0x000000001c610000
Kernel text base: 0xffffff801c810000
__HIB text base: 0xffffff801c700000
System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 74780513651
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000001169442cf7

Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000

Wake : 0x0000000000000000 0x000000027517988b 0x0000000000000000

last started kext at 20981471233: >!AUpstreamUserClient 3.6.8 (addr 0xffffff7fbcd78000, size 12288)

loaded kexts:

com.ZLab.SsdPmEnabler 0.1.1

>!AUpstreamUserClient 3.6.8

>AudioAUUC 1.70

@filesystems.autofs 3.0

@fileutil 20.036.15

>!APlatformEnabler 2.7.0d0

>AGPM 119

>X86PlatformShim 1.0.0

>!AHDAHardwareConfigDriver 283.15

>!AHDA 283.15

>!AGraphicsDevicePolicy 6.2.2

@AGDCPluginDisplayMetrics 6.2.2

>pmtelemetry 1

>LuaHardwareAccess 1.0.16

|IOUserEthernet 1.0.1

>usb.!UUserHCI 1


|IO!BSerialManager 8.0.2f9

@Dont_Steal_Mac_OS_X 7.0.0

>!AHV 1

>!ADiskImages2 1

>eficheck 1


>!ASMCLMU 212

>AGDCBacklightControl 6.2.2

>!AThunderboltIP 4.0.3

>!ABacklight 180.3

>!ALPC 3.1

>!A!ISlowAdaptiveClocking 4.0.0

>!A!IHD5000Graphics 16.0.1

>!ACameraInterface 7.6.0

>ACPI_SMC_PlatformPlugin 1.0.0

>!A!IFramebufferAzul 16.0.1

>!AMCCSControl 1.14

>!AFIVRDriver 4.1.0

|IO!BUSBDFU 8.0.2f9

|SCSITaskUserClient 436.40.6

>!UTCKeyEventDriver 256

>!UCardReader 511.60.2

>!UTCButtons 256

>!UTCKeyboard 256

>!AFileSystemDriver 3.0.1

@filesystems.tmpfs 1

@filesystems.hfs.kext 556.60.1

@BootCache 40

@!AFSCompression.!AFSCompressionTypeZlib 1.0.0

@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1

@filesystems.apfs 1677.60.23

>AirPort.BrcmNIC 1400.1.1

@private.KextAudit 1.0

>!ARTC 2.0

>!ASmartBatteryManager 161.0.0

>!AACPIButtons 6.1

>!AHPET 1.8

>!ASMBIOS 2.1

>!AACPIEC 6.1

>!AAPIC 1.7

@!ASystemPolicy 2.0.0

@nke.applicationfirewall 310

|IOKitRegistryCompatibility 1

|EndpointSecurity 1

@kext.triggers 1.0

>DspFuncLib 283.15

@kext.OSvKernDSPLib 529

>!AGraphicsControl 6.2.2

|IOSerial!F 11

|IOAVB!F 900.12

@!AGPUWrangler 6.2.2

>!ABacklightExpert 1.1.0


>!AHDA!C 283.15


|IOHDA!F 283.15


|IOAudio!F 300.6.1
 
Don't feel bad if it takes a little more than what you wrote for help. I've been following this thread since there were maybe 3000 posts. It may take a while for someone to reply, only bc many have already asked your questions (I have too), and given there are like 8000 posts here, your answers probably lurk... and are answered more than once.

But... who has time to read 8000 posts! There are angels here who come in and out of this thread, who were probably in our shoes, and might randomly go back a few pages, see your commonly asked question (I say that with all due respect because I've done the same thing, and never felt I got it straight what to do, as some posts lead me to think it's plug and play, others do not, and that vagueness makes me stop!

Consequently, I have sat on my Sintech adapter, and new SSD, and been horrified I'll hurt my machine!

I have read in horror posts about kernel panics, been overwhelmed by screen shots of graphs and tests which I cannot comprehend, read about Boot Rom.

Boot Rom is way beyond my intelligence. I still don't know if I need to flash (mine is 199.0.0.0.0).

There is a physical device you can use, there are software solutions or patches with Terminal, and even a remote access or an in-the-machine down solution a sprightly volunteer here made, uploaded, and donated his/her time to avail... which, incidentally, I downloaded but couldn't figure out what to do with it after I had the thing.

So, I haven't touched my machine, or my Boot Rom either.

This thread's Wiki has a lower first number, e.g., so yours needs to be something like >124..., but I don't understand these numbers at all, and my machine (a mid-2015 15" 11,4) is still under AppleCare so am paranoid if I have a problem I might void my warranty. Lots of unknowns, and I know in good conscience if I was lucky enough to have the time to read all 8000+ posts, I'd find some--if not all--answers to my questions. (Nobody is paid to help, it's all a give and take thing, but this forum is above and beyond in terms of people and their generosity!)

So, hang in there, try reading backwards. That's what I do. I have always had replies to just about every stupid question conceivable—not just in this thread, but everywhere—so for you (and anyone else who is lost or confused), don't feel bad if it takes a while to figure it all out. You'l get the help you need, and odds are have success. I am just too reliant on my machine to risk losing it. That is my biggest hesitation.

Most here who have done this were going into unchartered waters, and took the plunge. I do not think this is a difficult thing to do, but everyone's experience may be different. Too many variables for each machine, person, etc.

I know I'm not answering your question, per se. This is just to make you (and me, maybe others) feel better :cool:
wow thanks man! ill try reading up a bit then. hopefully soon ill build up the courage to actually open up my machine too
 
Now my question is:
1. With Corsair and Samsung was the problem with NVME driver to reboot with installed SsdPmEnabler kext, but as I understand Apple SSD doesn't use NVME driver?
2. Been confirmed that Sabrent Rocket 1TB is ok to install SsdPmEnabler kext and my Corsair is completely the same memory, DRAM and Phison E12 controller, the only different can be the SSD firmware, Sabrent Rocket using ECFM12.3 and my MP510 has ECFM22.6.
Hi BoPi

So basically the test confirmed your MBP (MacBookPro11,1) is okay. Its internal likely very similar to 2015 13-inch (MacBookPro12,1) as I would expect. Also perhaps you have to accept the reality that some NVMe SSDs simply won't work.

The AppleSSD shipped in these older machines are SATA drives with SATA express link that in turn is tunnelled over PCIe links. Like all SATA drives they use AHCI driver. ssdpmEnabler is redundant there as I believe Apple's AHCI driver already performs the same function.

I have little idea on details of Phison E12/E12s variants. I avoided such discussions and hoped not to drag myself into it. We simply won't be able to know what's the difference inside those variants and where manufacturers cut corners and save a dime.

With that said, there are indeed quite a few success stories on Sabrent Rocket but very few mentioned the details. In two data points where firmware versions are mentioned, it's ECFM12.3 which people seem confident that they're truly Phison E12.

A quick google shows Corsair MP510 has two variants with firmware ECFM13.1 and ECFM22.6. People claimed the latter is in fact Phison E12S. And for christ's sake, turns out Silicon Power A80 comes with ECFM22.6 firmware too.

2.2) From reading recent posts, can I conclude that SsdPmEnabler does not work in reducing idle power consumption if I decide to stay on High Sierra OS?

See @manu3569's post #8143 in the previous page. ssdpmEnabler works in High Sierra where WD SN550's idle power drops from 0.31A to 0.18A. That's 42%!

I would love to hear success stories from MBA. Pls let me know if you run into any ssdpmEnabler issues.
 
Hi BoPi

So basically the test confirmed your MBP (MacBookPro11,1) is okay. Its internal likely very similar to 2015 13-inch (MacBookPro12,1) as I would expect. Also perhaps you have to accept the reality that some NVMe SSDs simply won't work.

The AppleSSD shipped in these older machines are SATA drives with SATA express link that in turn is tunnelled over PCIe links. Like all SATA drives they use AHCI driver. ssdpmEnabler is redundant there as I believe Apple's AHCI driver already performs the same function.

I have little idea on details of Phison E12/E12s variants. I avoided such discussions and hoped not to drag myself into it. We simply won't be able to know what's the difference inside those variants and where manufacturers cut corners and save a dime.

With that said, there are indeed quite a few success stories on Sabrent Rocket but very few mentioned the details. In two data points where firmware versions are mentioned, it's ECFM12.3 which people seem confident that they're truly Phison E12.

A quick google shows Corsair MP510 has two variants with firmware ECFM13.1 and ECFM22.6. People claimed the latter is in fact Phison E12S. And for christ's sake, turns out Silicon Power A80 comes with ECFM22.6 firmware too.



See @manu3569's post #8143 in the previous page. ssdpmEnabler works in High Sierra where WD SN550's idle power drops from 0.31A to 0.18A. That's 42%!

I would love to hear success stories from MBA. Pls let me know if you run into any ssdpmEnabler issues.
Hi kvic:
My Corsair Force MP510 1TB SSD is still old version with Phison E12 controller and 1GB DRAM:
v0.3a
OS: 10.0 build 19042
Drive: 1(USB)
Bridge: JMS
Model : Force MP510
Fw : ECFM22.6
Size : 915715 MB
LBA Size: 512
Read_System_Info_5008 error: -1
Firmware lock supported [02 03] [P004] [0100]
F/W : ECFM22.6 00
P/N : 511-200611205
Bank00: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank01: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank02: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank03: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank04: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank05: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank06: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank07: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank08: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank09: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank10: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank11: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank12: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank13: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank14: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank15: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
Bank19: 0xfe,0xfe,0xfe,0xfe,0xfe,0xfe,0xfe,0xfe -
Bank22: 0xfb,0xfb,0xfb,0xfb,0xfb,0xfb,0xfb,0xfb -
Bank27: 0xfe,0xfe,0xfe,0xfe,0xfe,0xfe,0xfe,0xfe -
Bank30: 0xfb,0xfb,0xfb,0xfb,0xfb,0xfb,0xfb,0xfb -
Controller : PS5012-E12 [PS5012AA]
CPU Clk : 666
Flash CE : 16
Flash Channel : 8
Interleave : 2
Flash CE Mask : [++++++++ ++++++++ -------- --------]
FlashR Clk,MT : 666
FlashW Clk,MT : 666
Block per CE : 944
Page per Block: 5184
Bit Per Cell : 3(TLC)
DRAM Size,MB : 1024
DRAM Clock,MHz: 1600
DRAM Type : DDR4
PMIC Type : PS6102/PS6106
PE Cycle Limit: 2000
ONFI : MICRON MT29F512G08EBHBF3W [5EDA]
Page size : 18592 (16384+2208)
Page/Block: 5184
Block/LUN : 944
LUN/Chip : 1
Bit/Cell : 3 (TLC)
Endurance : 2000
PlanAdrBit: 2 (4 plane)


Defects Early Read Prog Erase
Bank00: 13 0 0 0
Bank01: 14 0 0 0
Bank02: 34 0 0 0
Bank03: 13 0 0 0
Bank04: 19 0 0 0
Bank05: 15 0 0 0
Bank06: 16 0 0 0
Bank07: 13 0 0 0
Bank08: 17 0 0 0
Bank09: 11 0 0 0
Bank10: 15 0 0 0
Bank11: 15 0 0 0
Bank12: 16 0 0 0
Bank13: 14 0 0 0
Bank14: 10 0 0 0
Bank15: 14 0 0 0
Total : 249 0 0 0

Defects Early Read Prog Erase
Ce00Pl0: 5 0 0 0
Ce00Pl1: 3 0 0 0
Ce00Pl2: 2 0 0 0
Ce00Pl3: 3 0 0 0
Ce01Pl0: 4 0 0 0
Ce01Pl1: 2 0 0 0
Ce01Pl2: 4 0 0 0
Ce01Pl3: 4 0 0 0
Ce02Pl0: 6 0 0 0
Ce02Pl1: 5 0 0 0
Ce02Pl2: 4 0 0 0
Ce02Pl3: 19 0 0 0
Ce03Pl0: 4 0 0 0
Ce03Pl1: 3 0 0 0
Ce03Pl2: 3 0 0 0
Ce03Pl3: 3 0 0 0
Ce04Pl0: 8 0 0 0
Ce04Pl1: 5 0 0 0
Ce04Pl2: 2 0 0 0
Ce04Pl3: 4 0 0 0
Ce05Pl0: 7 0 0 0
Ce05Pl1: 3 0 0 0
Ce05Pl2: 2 0 0 0
Ce05Pl3: 3 0 0 0
Ce06Pl0: 5 0 0 0
Ce06Pl1: 3 0 0 0
Ce06Pl2: 3 0 0 0
Ce06Pl3: 5 0 0 0
Ce07Pl0: 5 0 0 0
Ce07Pl1: 4 0 0 0
Ce07Pl2: 2 0 0 0
Ce07Pl3: 2 0 0 0
Ce08Pl0: 4 0 0 0
Ce08Pl1: 4 0 0 0
Ce08Pl2: 5 0 0 0
Ce08Pl3: 4 0 0 0
Ce09Pl0: 4 0 0 0
Ce09Pl1: 3 0 0 0
Ce09Pl2: 2 0 0 0
Ce09Pl3: 2 0 0 0
Ce10Pl0: 4 0 0 0
Ce10Pl1: 3 0 0 0
Ce10Pl2: 5 0 0 0
Ce10Pl3: 3 0 0 0
Ce11Pl0: 5 0 0 0
Ce11Pl1: 3 0 0 0
Ce11Pl2: 2 0 0 0
Ce11Pl3: 5 0 0 0
Ce12Pl0: 5 0 0 0
Ce12Pl1: 3 0 0 0
Ce12Pl2: 4 0 0 0
Ce12Pl3: 4 0 0 0
Ce13Pl0: 5 0 0 0
Ce13Pl1: 4 0 0 0
Ce13Pl2: 3 0 0 0
Ce13Pl3: 2 0 0 0
Ce14Pl0: 4 0 0 0
Ce14Pl1: 2 0 0 0
Ce14Pl2: 2 0 0 0
Ce14Pl3: 2 0 0 0
Ce15Pl0: 4 0 0 0
Ce15Pl1: 4 0 0 0
Ce15Pl2: 3 0 0 0
Ce15Pl3: 3 0 0 0
Total : 249 0 0 0
 
@BoPl

Perhaps you could do trial & error with different combinations if possible. E.g. place Corsair MP510 in MacBookPro12,1; get a Sabrent Rocket in MacBookPro11,1 etc etc.

Sorry, nothing much I could help really.
 
  • Like
Reactions: BoPl
So, shall we assume that SsdPmEnabler is not compatible with E12S controller and ECFM22.6 firmware?
 
So, shall we assume that SsdPmEnabler is not compatible with E12S controller and ECFM22.6 firmware?
My Corsair Force MP510 ssd is still with old Phison E12 (not E12S) controller. Corsair released new ECFM22.7 firmware, will try to update my ssd with new firmware and test SsdPmEnabler again.
Anywhere I've ordered already new Crusial P2 1TB SSD for my MBP and will use MP510 as external ssd.
 
See @manu3569's post #8143 in the previous page. ssdpmEnabler works in High Sierra where WD SN550's idle power drops from 0.31A to 0.18A. That's 42%!

I would love to hear success stories from MBA. Pls let me know if you run into any ssdpmEnabler issues.
I will likely be ordering the sintech adaptor, the P2 or SN550 SSD & screwdrivers soon.

1) In the meantime, I have attached 3 screenshots (pre-SSD upgrade):
- '1' shows the power consumption of OEM Apple SSD with High Sierra bootrom 122.0.0.0.0, the lowest number I have seen is 0.2A and not what is seen in the screenshot of 0.3A
- '2' shows the bootroom on my macbook air 2013 updating to 429.0.0.0.0 (this has been done following instructions in post #8,050)
- '3' shows the power consumption of OEM Apple SSD with High Sierra bootrom 429.0.0.0.0, the lowest number I have seen is the 0.2A shown

note: I am using the free 14 day version of iStat version 6.51 if that matters.

2) Should I be concerned about the P2 1tb having lower endurance of 300 TBW and lower power consumption be less stable in terms of "system stability & zippiness" and "data loss" compared to the WD SN550 (600 TBW for the 1tb version)? Since my macbook air battery is at 80% of original capacity, I am inclined to get the P2 to hopefully get back some use time off the charger.
2.1) Any other SSD suggestions specific to laptops especially the Macbook Air are appreciated
 

Attachments

  • 2_HighSierra_BootRom_updated_4290000.png
    2_HighSierra_BootRom_updated_4290000.png
    67.1 KB · Views: 139
  • 3_MBA62_OEM256SSD_8gb_HighSierra_4290000.png
    3_MBA62_OEM256SSD_8gb_HighSierra_4290000.png
    237.4 KB · Views: 124
  • 1_MBA62_OEM256SSD_8gb_HighSierra_1220000.png
    1_MBA62_OEM256SSD_8gb_HighSierra_1220000.png
    289.5 KB · Views: 110
Last edited:
Hi kvic:
My Corsair Force MP510 1TB SSD is still old version with Phison E12 controller and 1GB DRAM:
How do you check for the version of your SSD etc with details like below?

v0.3a
OS: 10.0 build 19042
Drive: 1(USB)
Bridge: JMS
Model : Force MP510
Fw : ECFM22.6
Size : 915715 MB
LBA Size: 512
Read_System_Info_5008 error: -1
Firmware lock supported [02 03] [P004] [0100]
F/W : ECFM22.6 00
P/N : 511-200611205
Bank00: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
 
I can confirm that ssdpmEnabler doesn't work on Big Sur clean install, laptop restarts after booting up, showing a window that there was some kind of a problem.
I have MacBook pro 13, Mid 2014 (MacbookPro11,1) with Sabrent Rocket 512Gb.

Although I managed to install Lilu and NvmeFix afterwards, it's too early to say anything about power consumption, but the lowest idle value I've seen is 0.10A according to iStat charts.
 
@megaco thanks for posting. Can you check and tell us your Sabrent Rocket’s firmware version?

You can look it up in About My Mac -> System Report -> NVMe
 
@kvic

I saw you updated your user reports table

2013/14 15" MBP (MacBookPro11,2)​
ADATA SX8200 Pro (? GB)​
41%​
0.10​

Not sure if this was the entry added for my report. The drive is a 2TB and my machine is an 11,3, if you wanted to update/add.
 
  • Like
Reactions: kvic
How do you check for the version of your SSD etc with details like below?

v0.3a
OS: 10.0 build 19042
Drive: 1(USB)
Bridge: JMS
Model : Force MP510
Fw : ECFM22.6
Size : 915715 MB
LBA Size: 512
Read_System_Info_5008 error: -1
Firmware lock supported [02 03] [P004] [0100]
F/W : ECFM22.6 00
P/N : 511-200611205
Bank00: 0x2c,0xc4,0x18,0x32,0xa2,0x0,0x0,0x0 - Micron 96L(B27A) TLC 512Gb/CE 512Gb/die
jerris86,

You can look it up in About My Mac -> System Report -> NVMexpress
Screen Shot 2021-01-01 at 8.39.55 AM.png
 
I can confirm that ssdpmEnabler doesn't work on Big Sur clean install, laptop restarts after booting up, showing a window that there was some kind of a problem.
I have MacBook pro 13, Mid 2014 (MacbookPro11,1) with Sabrent Rocket 512Gb.

Although I managed to install Lilu and NvmeFix afterwards, it's too early to say anything about power consumption, but the lowest idle value I've seen is 0.10A according to iStat charts.
@megaco Can you check and tell us your Sabrent Rocket’s firmware version pleaseScreen Shot 2021-01-01 at 8.39.55 AM.png?
 
  • Like
Reactions: kvic
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.