Lost-Entrepreneur439 Posted yesterday at 06:41 AM Share Posted yesterday at 06:41 AM I'm trying to hackintosh a Latitude E6400, and it crashes really early into boot. I believe it's a kernel panic, but I could be wrong because it's way shorter than a normal kernel panic. The panic mentions VoodooInput, so I tried disabling everything related to VoodooPS2, and then got a single line panic log, which I've never seen before. Does anyone know how to fix this? Before someone questions the airportitlwm, I'm using a fork that has support for El Cap. I don't want to use a prebuilt EFI, and I'd rather keep OpenCore if possible. Yes I know El Capitan is ancient. config.plist is attached as a zip since site doesn't allow me to upload plist files. Panic log with VoodooPS2 enabled: Panic log with VoodooPS2 disabled: config.plist.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted yesterday at 12:53 PM Administrators Share Posted yesterday at 12:53 PM Try and use kexts from the era of El Capitan; you may refer to guides/threads posted for similar C2D models. As stated in a previous E6400 thread, OpenCore should be avoided on C2D systems because it does not support power management for old Intel CPUs up to 1st gen CORE models. I would recommend you stick to Clover which does; Clover is perfectly fine and best suited to this type of ancient Penryn laptops. You should also use the FakeSMC kext I had tuned for improved CPU power management and GPU throttling. https://osxlatitude.com/forums/topic/2673-performance-tuning-with-fakesmc https://osxlatitude.com/forums/topic/7807-nvidia-gpu-performance-tuning-with-agpm I was able to get my old D630 nVidia up to Catalina (see my old D630 guide) so no reason why your E6400 could not do the same. Big Sur and beyond will be challenging especially as Apple dropped AICPUPM from macOS Ventura though it can be injected (see my E6230 old guide) and you'll need OCLP patcher, of course, to obtain support for Tesla graphics (last natively supported in High Sierra). Link to comment Share on other sites More sharing options...
Lost-Entrepreneur439 Posted yesterday at 05:36 PM Author Share Posted yesterday at 05:36 PM As I said previously, I want to keep using modern kexts and OC. Power management doesn't matter since this laptop has a battery life of 5 minutes even on Linux, there's nothing like Dortania's guide for Clover, and pretty much every Hackintosh community no longer supports Clover (this site is the only one I'm aware of that still does). Plus, from everything I've seen, Clover is just an OpenCore fork now. Also, I don't think what you said is accurate. I have an N5040 (Arrandale) running on High Sierra with OC, and it has no problems with power management. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted 1 hour ago Administrators Share Posted 1 hour ago My mistake, OC does indeed support CPUPM for Sandy and Ivy Bridge platforms of course (post above corrected to that effect). It does not provide and P States and C States generation and, as such, cannot manage CPU power management for C2D and 1st gen. CORE platforms, only for LFM and HFM speeds. It's Ventura that dropped CPU PM for older CPUs up to Ivy Bridge by removing AICPUPM kexts. I think you're looking at this a wee bit wrongly; you want to use "modern" kexts and OpenCore on an ancient platform and with an ancient OS X version; it's contradictory and makes little sense to me. And no, absolutely not, Clover is not "just an OC fork". It's better suited to older platform such as yours. It's still subject to development and I still use its latest versions on my E7270 with Sequoia and Tahoe with everything working perfectly... Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now