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.
Being deprecated is one thing, but when will those kexts be completely locked out?

This may not affect those with the 2015 MacBook Pros, since those MacBook Pros likely won't be getting a lot of macOS support going forward, aside from security updates. There is a chance for the 2015 MBP to get macOS 13, but I'd be shocked if it got macOS 14.

OTOH, it could affect some later machines since many still have upgradable storage, eg. 2017 MacBook Air, non-Touch Bar MacBook Pros... speaking of which, this is by far the worst SSD upgrade I've seen so far:


The guy stuck a 2280 sized WD SN550 in a 2017 nTB MacBook Pro. It doesn't fit of course, so he just taped it down to keep it from falling out. o_O

BTW, I'm thinking of getting a 2 TB NVMe M.2 SSD for use in an external enclosure. However, I will keep in mind the compatibility for use in Macs should I ever decide to use it in a Mac. There is a sale locally on the XPG Gammix S11 Pro but I think I'll avoid that one. I suspect its integrated heatsink will make it too big for some Macs. It has the Silicon Motion SM2262EN controller too which is OK but not great for power utilization without the kexts.
See sig. I have the 2TB ADATA XPG SX8200 Pro in my 2015 MBA. Works well. Power decent.
 
... speaking of which, this is by far the worst SSD upgrade I've seen so far:


The guy stuck a 2280 sized WD SN550 in a 2017 nTB MacBook Pro. It doesn't fit of course, so he just taped it down to keep it from falling out. o_O
Not only that, but the a1708 is PCIe 3.0x4, and the SN550 isn't nearly capable of maxing that out. So he's left performance on the table. I mean, if you're going to force a 2280 card into your machine, at least get some performance out of it.
 
Yes, but you need to activate the Aspm boot argument per the nvmefix instructions. Also you may have to activate the keepsyms=1 boot argument (please read nvmefix posts in this thread about how to get that working).

So a little more involved than ssdpmenabler, but not hard and nvmefix does a lot more. For instance on my ssd (intel 660p), using ssdpmenabler I got the idle down from .17A to .06. Using nvmefix with aspm enabled, I went down to lower than .01A idling.

Nvmefix attempts to correct apples lack of support for modern ssds and allows them to work as intended. Some will benefit dramatically from this.
Hi Terrazoids,

Could you confirm Intel 660p is working on Monterey latest edition for you as I keep getting boot errors after installing Nvmefix and Lilu?

Thanks

- i got the same machine Macbook mid 2015 15” and ssd as you
- did you have to do anything special when installing or possible to outline how you got it installed
 
Then, you don't really need it, do you?

Also, even with just the kext signing disabled, any rampant kext you may download unwittingly can damage your system.
Yes. Not much point to use it. But I have other Macbook with m510 and this is there this kext makes difference in power consumption.
It's the same with the A2000. What does that mean?
This means system does not know your ssd can handle lower power state such as L1. If you run Hackintool on a system with original ssd installed you will see L1 state available for it.
* ASPM operates in several modes:
* L0-Normal mode.
* L0s-Standby mode. L0s mode enables fast entry and exit from the idle state, and after entering the idle state, the device is placed at a lower power consumption.
* L1-low power standby mode. L1 further reduces power consumption compared to L0s. However, the time to enter or exit the idle state is longer than L0s.
 
Yet, he has a disclaimer that he's not responsible for any possible damage to the system.
I have seen such disclaimer many times before, from the people who creates something for themselfs in 1st place and later decide to share success (results) of his labour with others for free.
All these people has good intentions. Unlike big companies who writes software like Apple or Microsoft small developer can not afford to be sued for any damage cause by inproper software use or due to incompatibility. They charged you nothing for using it.
So they shift responsibility from themselfs to end users - US.
So it is completely your decision and responsibility to use. And it is fear. Cause non of us ever spend a penny for using it or his/her time developing it. From this point of view am on developers side fully.
 
Would someone be able to comment on my post or suggestions? As looks like I will need NVMFix to enable Aspm modes.

The error is after I’ve tried all the installation instructions and terminal commands in this thread or using Hakintool the Mac cannot boot into Monterey 15.2 after the apple logo then it will say error happened and will reboot and stuck in a loop until I disable the kext.
 
I have seen such disclaimer many times before, from the people who creates something for themselfs in 1st place and later decide to share success (results) of his labour with others for free.
All these people has good intentions. Unlike big companies who writes software like Apple or Microsoft small developer can not afford to be sued for any damage cause by inproper software use or due to incompatibility. They charged you nothing for using it.
So they shift responsibility from themselfs to end users - US.
So it is completely your decision and responsibility to use. And it is fear. Cause non of us ever spend a penny for using it or his/her time developing it. From this point of view am on developers side fully.
I too feel that the software is likely reliable but disputable. If there was an issue I’m sure we would have heard already from the NVMEFix developer as when he reverse engineered it and studied the app behaviour anything unusual would have been spotted.
 
Would someone be able to comment on my post or suggestions? As looks like I will need NVMFix to enable Aspm modes.

The error is after I’ve tried all the installation instructions and terminal commands in this thread or using Hakintool the Mac cannot boot into Monterey 15.2 after the apple logo then it will say error happened and will reboot and stuck in a loop until I disable the kext.
Lilu or NVMEFix may not be compatible with 15.2 yet. I have installed Monterey 15.1 yesterday. Had no problem with booting it with Opencore and kexts activated. Have you tries 15.1?
 
Lilu or NVMEFix may not be compatible with 15.2 yet. I have installed Monterey 15.1 yesterday. Had no problem with booting it with Opencore and kexts activated. Have you tries 15.1?
Lilu or NVMEFix may not be compatible with 15.2 yet. I have installed Monterey 15.1 yesterday. Had no problem with booting it with Opencore and kexts activated. Have you tries 15.1?
my timemachine wasn’t on when I did the update so can’t roll back I am afraid. I didn’t test under 15.1 as I only saw this thread recently.
 
my time machine was not on so no way to roll back. I did not test on 15.1 as only saw this thread after upgraded to 15.2

Is there a manual way to enable aspm?
 
my time machine was not on so no way to roll back. I did not test on 15.1 as only saw this thread after upgraded to 15.2

Is there a manual way to enable aspm?
You can roll back see here. Alternatively you can use Opencore bootloader to change ASPM.
 
I am not after latest an greatest. Did not install beta. 12.1 worked fine for me yesterday when tested. Are your kexts are up to date?
I used the latest ones available. Maybe there is something with my setup eg bootcamp or softwares. Anyway thank you for your assistance.
 
  • Like
Reactions: Eugene28
Have gone through the debug logs. The crash point appears to be Lilu causing kernel panic on 12.2 Monterey. If people can also test that would be great.
 
See sig. I have the 2TB ADATA XPG SX8200 Pro in my 2015 MBA. Works well. Power decent.
Thanks. I ended up just getting a 1 TB Kingston A2000 instead for now, and will reassess in a year.

The concern I had with the SX8200 was its max power usage, which is around 6 Watts. That might sometimes be problematic in an external enclosure. The A2000 was closer to 4.6 Watts.

Screen Shot 2021-12-24 at 11.09.49 AM.png
Screen Shot 2021-12-24 at 11.10.00 AM.png


The Crucial P2 was significantly lower power but after the cache is filled, the QLC variant (which I think may include all of the 2 TB models), it drops to 40 MB/s. Ouch. Not great for an external storage drive. Plus, strangely enough, it wasn't that cheap.

I ended up getting the 1 TB A2000 for CA$95, which is only US$74. Cheap for a DRAM model. I think if I do get another 2 TB drive though, I might just get a Samsung T7 instead. They're relatively inexpensive, and never have USB power issues.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.