Jump to content

AppleTyMCEDriver Kext Injection Stopped Working


GokieKS
 Share

4 posts in this topic

Recommended Posts

I have a Hackintosh with the following components:

 

MB: Gigabyte GA-Z87N-WIFI (Rev. 2.0)

CPU: Intel Core i7 4770K
GPU: nVidia EVGA GTX750 Ti SSC 1GB GDDR5
RAM: 2 x 8GB Crucial 1.35V DDR3 1600MHz
HDD: Samsung 830 256GB SSD + Western Digital Green 3TB
 
I rebuilt it using the current components a couple weeks ago (previously was using an i3 3225).  I installed 10.9.3 using Clover, set it as a MacPro5,1 in SMBIOS, installed nVidia drivers (because I was getting the "Fermi Freeze" issue though my card is Kepler), and everything was working fine (though I was still experimenting with P- and C-States because it seemed like the CPU was only ever running at minimum (800MHz) or maximum (either 3.5GHz or 3.9GHz Turbo, can't remember).  Last week, I updated to 10.9.4, and didn't experience any issues.
 
This morning, however, I woke up to discover that the system had rebooted and was on the login screen.  I was a little confused since I knew there wasn't a power issue (my other computer remained on with no issues), but didn't think too much of it.  However, after I restarted it again, I started getting kernel panics on boot.  I thought it might've been due to the changes in Clover config that I made, so I switched back to the previous version in single-user mode, but that didn't fix the problem.  I tried using the USB installer with Clover, which I knew for sure had a working config.plist, but that didn't work either.  I ended up taking a picture of it in verbose mode to get the proper KP message, and discovered that it shows AppleTyMCEDriver as the cause:
 
 
Kernel panics due to AppleTyMCEDriver is usually from using a MacPro5,1 SMBIOS without ECC RAM, which then requires a kext injection, which I have in my Clover config.plist (and was working fine up until now).
 
I tried a bunch of things to no avail, and eventually had to boot in Safe Mode and rename AppleTyMCEDriver.kext in S/L/E, after which I was able to boot as normal again.  So now I'm stumped - why would this suddenly stop working?  Did the kext injection for it change in 10.9.4?  And if it did, why did it only start manifesting today, quite a while after I upgraded to 10.9.4?  The AppleTyMCEDriver.kext version is the same as far as I can tell (1.0.2d2, file modification date of 2014/4/28).  Anyone have any ideas?
Link to comment
Share on other sites

Hello!

 

I don´t know, why you ar forcing your system to get the personality of an MacPro 5,1, which has never been produced with the architecture of your hardware, resulting in not fully working C- and P-States and resulting in gfx-freezes. To get rid of them, you have installed the NVidia Webdrivers, which have, as it seems before the update have been working. The update could not work, because of your in the Apple architecture not existing device. So the update has been probably done on the one part with the dedected hardware and on the second part with your to be an MacPro 5,1 forced device personality. May be, that even Clover can not work properly.

 

The most common opinion is, to use a SMBios, matching the board and cpu architecture as near as possible. You should bee just fine with the personality of an iMac 14,2 with NVidia Kepler gfx.

 

And by the way, installing NVidiaWebdrivers are not worth the trouble at a system update. I am pretty sure, the performance gain with the Webdrivers, if there is even one, is not feelable.

 

If you are a gfx performance junkie, you should try to find a faster compatible gfx card or inject an occed vbios with bootloader. If the shown up system information is disturbing you, correct the corresponding framework entries to your needs.

 

Have fun.

Link to comment
Share on other sites

I used a MacPro5,1 SMBIOS because it would let me update nVidia webdrivers without having to mess around with modifying the installer.  At any rate, the SMBIOS is working fine, as are the nVidia web drivers, even after 10.9.4 update, and that's not the issue here.  The question is with AppleTyMCEDriver, and why the kext injection to bypass the ECC check is no longer working - changing my SMBIOS definition is not a useful suggestion considering the effort to deal with associating my Apple ID with a "new" machine, especially since removing AppleTyMCEDriver.kext is a perfectly fine work-around.

Link to comment
Share on other sites

Hello!

 

But every thing else is not working just fine as the apple stock Nvidia drivers, C- and P-States. If you want at every the version changing system update having big troubles with your not fully working hardware, install furtheron the webdrivers and stay with your hardware on in a noway matching SMBios of MP 5,1.

 

But look around here, you are not the only one, who has problems with systemupdate with a not matching personalitiy and the under it installed webdrivers.

 

If you want to have a faked MacPro 5,1, yo1 should get a socket 1366  mainboard, a used 6 Core Xeon CPU from ebay (working on ASUS mainboards), and sell the not more used parts of your existing hardware. The performance of your system would increase notificable, as by you wished and needed with working  NvidiaWebdriver.

 

Have fun.

 

PS: But please be so nice, to  not suggest the way, you have gone, to make the webdrivers working on your in any case not matching hardware, to a newbie. :yes:

Link to comment
Share on other sites

 Share

×
×
  • Create New...