Hi everyone,
I've just installed a Samsung 970 Evo into my 2013 13" Macbook Pro, but experiencing a couple of issues:
On boot, I am greeted with a gong and a black screen, then a second gong with a black screen, shortly followed by the Apple logo and normal boot up.
Just installed a 2TB Sabrent in my Late 2013 15" MacBook Pro... Pretty happy with the results. Lightroom feels a little snappier but it's might just be psychological, glad to finally have a 2TB internal SSD... now if only it was possible to upgrade the RAM!
Hello, I am trying to put standby to 0 to fix my kernel panic problem, but I'm getting an error. I am using
"sudo pmset -g standby 0" as stated in the OP and the error message I am getting is
Error: unhandled argument standby
Usage: pmset <options>
See pmset(1) for details: 'man pmset'
Did you try you assigning the 970 Evo as the Startup disk in System Preferences?
Hi @macgeek01 I was a little too fast to claim success. I started eventually getting the random reboots and double-startups. I put back the original Apple SSD and installed OS X 10.14.4. Now I have MacBookPro11,1 151.0.0.0.0 which is latest rom. In fact I have more problems now than ever before!I have the Sabrent which is PCIe 3 x4 NVME which is very fast and get 2600MBps read and writes with my Late 2015 27” iMac which is also PCIe 3 x4.
The same Sabrent drive in my 15” Late 2013” MacBook Pro which is PCIe 2 x4 gets 1300MBps reads and 700MBps writes. The stock OEM (SSUAX) is PCIe 2 x2 AHCI gets 700MBps read and writes. An Apple OEM PCIe 3 x4 (SSUBX) gets 1250MBps reads and 1400MBps writes so it outperforms the Sabrent.
This sounds similar to some others experience with 3rd party NVME in PCIe 2 x4 Macs. You may be better of with a used Apple SSUBX from eBay for better speed and not worry about sleep issues and battery unless. Their prices on eBay seem to be lower than in the past.
Wonder how both of you manage to have no issues without modified firmware?
You bring up a good point about idle power.
System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
womp 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 1
gpuswitch 2
networkoversleep 0
disksleep 10
standbydelayhigh 86400
sleep 1 (sleep prevented by coreaudiod)
autopoweroffdelay 28800
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 10
highstandbythreshold 50
acwake 0
lidwake 1
sudo nvram enable-legacy-orom-behavior=1
I'm also curious about how @gilles_polysoft is testing the power draw.
Can anyone comment what happens if you put back in the original drive to get an EFI update when you have flashed modified ROM with the NVME DXE driver? Does it overwrite or not take the update? Thanks.
Does anyone have any experience with the intel 660p and how its power consumption differs from the rest of the drives? There's been some major deals online for this drive, wondering if i should change from my 760p
Hi,
The most reliable method I have found is :
- install iStatMenu (or HardwareMonitor)
- monitor the "SSD" (A) sensor. Then multiply by the tension (3.3V), you have your power consumption.
- plug the MacBook Pro on the AC adapter...
Plugging the MacBook on AC adapter is mandatory : strangely, while on battery the SSD 3,3V power sensor show no consumption 0A, even during writes.
I then get power consumption graphs where I can see clearly the idle, read and write consumption (during my 100GB files write and read test).
And I pick the power during idle, read, write.
Here are examples with the HP ex920 :
idle:
View attachment 831608
read :
View attachment 831607
write :
View attachment 831610
write at the end of garbage collection :
View attachment 831609
The whole archive of my consumptions test is available here :
http://www.polysoft.fr/dl/NVMe_consumtion_test.zip
[doublepost=1554983490][/doublepost]
If you put back an AHCI SSD (original Apple) to get an EFI update... you get an EFI update. And the EFI update overwrite the previous BootRom, so you loose the "full" uncompressed NVMe DXE driver..;
If you are not happy with this, please contact Apple, make bug reports to then (bugreport.apple.com), so that Apple be aware of the situation and may provide future Bootrom updates with the full uncompressed NVMe DXE driver for the 2013-2014 macs.
[doublepost=1554984080][/doublepost]
Please read my charts (post #1 of this thread).
The intel 660P as the Crucial P1 are not so bad af first sight (0.6W idle, 2.7W during read/writes)... EXCEPT that after a write, those QLC drives don't go to idle power immediately...
They need to "rewrite" the SLC cache back to "QLC" form, and this process can consume up to 3W during... 30 minutes in my tests ! This is terrible.
So those QLC SSDs barely go to idle power... they consume a lot of power after each write because they need to "clear" the SLC cache and rewrite data in QLC form.
TLC drives have the same behaviour, but a lot lighter : it only last seconds and they resume to idle very fast.
It will be interesting to see if they were able to work out any of the sleep/hibernation issues and how much power they consume.
Correct, a quick google search of OWC Aura Pro X hibernation will lead you to results of people experiencing the same thing as with other NVME drives. The new OWC models will likely have the same issues. The only drive you wont have problems with is the regular OWC Aura, I don't think this drives uses NVME and has read/write speeds only slightly faster than the OEM but its wicked expensive.My guess is only Apple can fix it by pushing a bootrom update with full support. Truth is Aura, Transcend and alike, selling third party nvme upgrade don't tell you upfront but their drives have the exact same problems on 2013-2014 macbooks. I don't think it can be fixed on the drive side.
Thank you sir, the information about QLC drives is a lot more clear!!Hi,
The most reliable method I have found is :
- install iStatMenu (or HardwareMonitor)
- monitor the "SSD" (A) sensor. Then multiply by the tension (3.3V), you have your power consumption.
- plug the MacBook Pro on the AC adapter...
Plugging the MacBook on AC adapter is mandatory : strangely, while on battery the SSD 3,3V power sensor show no consumption 0A, even during writes.
I then get power consumption graphs where I can see clearly the idle, read and write consumption (during my 100GB files write and read test).
And I pick the power during idle, read, write.
Here are examples with the HP ex920 :
idle:
View attachment 831608
read :
View attachment 831607
write :
View attachment 831610
write at the end of garbage collection :
View attachment 831609
The whole archive of my consumptions test is available here :
http://www.polysoft.fr/dl/NVMe_consumtion_test.zip
[doublepost=1554983490][/doublepost]
If you put back an AHCI SSD (original Apple) to get an EFI update... you get an EFI update. And the EFI update overwrite the previous BootRom, so you loose the "full" uncompressed NVMe DXE driver..;
If you are not happy with this, please contact Apple, make bug reports to then (bugreport.apple.com), so that Apple be aware of the situation and may provide future Bootrom updates with the full uncompressed NVMe DXE driver for the 2013-2014 macs.
[doublepost=1554984080][/doublepost]
Please read my charts (post #1 of this thread).
The intel 660P as the Crucial P1 are not so bad af first sight (0.6W idle, 2.7W during read/writes)... EXCEPT that after a write, those QLC drives don't go to idle power immediately...
They need to "rewrite" the SLC cache back to "QLC" form, and this process can consume up to 3W during... 30 minutes in my tests ! This is terrible.
So those QLC SSDs barely go to idle power... they consume a lot of power after each write because they need to "clear" the SLC cache and rewrite data in QLC form.
TLC drives have the same behaviour, but a lot lighter : it only last seconds and they resume to idle very fast.
OWC announced their Aura Pro X2 drives, which now offer up to 3200MB/s read and 2400MB/s write performance and uses 3D TLC.
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 960.2 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 960.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +960.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh SSD 502.8 GB disk1s1
2: APFS Volume Preboot 47.9 MB disk1s2
3: APFS Volume Recovery 522.7 MB disk1s3
4: APFS Volume VM 8.6 GB disk1s4
Device Identifier: disk0
Device Node: /dev/disk0
Whole: Yes
Part of Whole: disk0
Device / Media Name: BPXP
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: PCI-Express
SMART Status: Not Supported
Disk Size: 960.2 GB (960197124096 Bytes) (exactly 1875385008 512-Byte-Units)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: Not applicable (no file system)
Device Location: Internal
Removable Media: Fixed
Solid State: Yes
Hardware AES Support: No
Device Identifier: disk1
Device Node: /dev/disk1
Whole: Yes
Part of Whole: disk1
Device / Media Name: BPXP
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): EF57347C-0000-11AA-AA11-00306543ECAC
OS Can Be Installed: No
Media Type: Generic
Protocol: PCI-Express
SMART Status: Not Supported
Disk / Partition UUID: A05A14D1-3A23-4AAA-9BA2-A52FABD9FCB0
Disk Size: 960.0 GB (959987367936 Bytes) (exactly 1874975328 512-Byte-Units)
Device Block Size: 4096 Bytes
Read-Only Media: No
Read-Only Volume: Not applicable (no file system)
Device Location: Internal
Removable Media: Fixed
Solid State: Yes
Virtual: Yes
Hardware AES Support: No
Hi everyone,
I've just installed a Samsung 970 Evo into my 2013 13" Macbook Pro, but experiencing a couple of issues:
On boot, I am greeted with a gong and a black screen, then a second gong with a black screen, shortly followed by the Apple logo and normal boot up.
When I close the lid and open it up a while later, i only get a black screen and nothing else - I have to hold down the power button and am back to problem 1. Any ideas?
I have hibernate 0 and standby 0 for now.
Thanks in advance!
Did you try you assigning the 970 Evo as the Startup disk in System Preferences?
Yup - did that. Although it was already picked when I went into the preferences (I guess because the volumes was named the same?)
Ha ha, nice of them to obliterate any info about the chipsets they're using.
To me, it looks like they're jumping on the Phison E12 bandwagon, it's a controller that promises those same exact speeds but I'm not really sure about power management. A ton of these SSDs with Phison E12 controllers and Toshiba-built 3D NAND are coming out- the Sabrent Rocket, the Seagate Firecuda 510, the MyDigital BPX Pro, the Gigabyte Aorus, the Silicon Power 34A80, and the Inland Premium.