MacOS – Consequences of disabling kext signing

macosssdtrim

What are the consequences of disabling Kest Signing on OS X Yosemite? I have disabled it to keep TRIM enabled on my aftermarket SSD. What are the security issues I could run up against? If I install applications only from trusted resources can I run in any kind of trouble?

I couldn't find online extensive answers to these questions. Sorry if it's a duplicate.

Best Answer

TRIM Support has been enabled for Third Party SSDs in OS X El Capitan. You can google it or watch this Youtube video

Related Solutions

Windows – Enabling AHCI for SSD under Win7 BootCamp on Macbook Pro 2011

You can't. Apple has implemented a Compatibility Support Module (CSM) into the Mac firmware that emulates the PC BIOS specification. Since the Mac firmware is not 100% UEFI compliant, that CSM is the only way Windows can boot on a Mac.

Unfortunately, the ACPI tables in that CSM are just the bare minimum necessary to allow Windows to boot and nothing more. You lose several features when using it:

No graphics switching (always uses the discrete card).
No AHCI support (SATA devices are in IDE compatibility mode)
- No support for TRIM
- No support for Native Command Queuing (NCQ).
No support for advanced power management features (only basic S1, S3, and S4 states are supported).

Basically Windows sees your SSD as just a really fast IDE hard drive. This will not affect the SSD in terms of lifespan. It may, however, make the SSD a little slower over time than it would otherwise be when running Windows.

NOTE: Some people have reported that they have been able to install Windows 7 in UEFI mode on a Mac, which would enable all those missing features. However, it cannot be done on your model. I've tried. With sufficient hacking you can get it up and running, but it's plagued with audio and video issues.

MacOS – Panic on boot, need to use single user mode (was: need to rebuild kext cache)

I encountered the same problem after updating to 10.10.1.

When I was booting through single user mode I noticed that fsck was reporting that the root file system didn't have journaling enabled.

After booting into OS X Recovery and enabling journaling on the volume in Disk Utility the kernel panics stopped.

I suspect that your problem will be solved by this as well as my panic seems to have the same callstack:

0xffffff875d5f3b40 : 0xffffff801573a811 mach_kernel : _panic + 0xd1
0xffffff875d5f3bc0 : 0xffffff801581e80a mach_kernel : _kernel_trap + 0x84a
0xffffff875d5f3d80 : 0xffffff801583a443 mach_kernel : _return_from_trap + 0xe3
0xffffff875d5f3da0 : 0xffffff801550e11b 
0xffffff875d5f3ed0 : 0xffffff8015b7d684 mach_kernel : _NodesAreContiguous + 0x1794
0xffffff875d5f3f80 : 0x0

Best Answer

Related Solutions

Windows – Enabling AHCI for SSD under Win7 BootCamp on Macbook Pro 2011

MacOS – Panic on boot, need to use single user mode (was: need to rebuild kext cache)

Related Question