trafsta

I'll show you a screenshot sometime

myhack won't even run on my D420 10.6.8 laptop unless I run 3.1.x or older which doesn't support 10.9. Might have something to do with it not being a Core 2 Duo (it's just a Core Duo) - no 64bit support. I had used my sisters real Macbook Pro with 10.6.8 (intel Core i7 64bit) to make my 10.9 USB installer a month or so ago. Won't be seeing her for a few more weeks and I have no other access to real Macbooks.

lol. whoops, I tried the 'AppleIntelCPUPowerMangement fix' or 'patch' or whatever its called in the new myhack 3.3.1 and it blew up my 10.8.5 partition... -f -v -x doesn't even work... oh well... I had a bit of time (my 1 month old kid finally fell asleep for a while) so I tried redoing my 10.9 installer USB and I've tried a few different ways but I always get "The OS X installation couldn't be completed" when I boot from it and it forces me to shutdown or reboot... never seen that before using myhack 3.2 beta 8. I think I'm going to take a break from this for a while and regroup at a later time... Especially since I only have a 10.6.8 D420 left now and it can't even run the latest myhack on it (incompatible with 10.6.8) to make another USB installer (and too lazy to reinstall 10.8.5 for the millionth time). steno, I'm leaving it up to you to figure it out and give detailed instructions on how to get 10.9 installed lol Anyways, thanks for all your help everyone. I'll definitely keep monitoring this thread to see how it progresses.

Hmm I'll let steno take this one, I'm swamped for the next week or so, don't think I'll have time to reinstall 10.9 to get a screenshot of the error again (the partition is currently wiped). I WAS using Myhack 3.2 BETA 8 (which was the latest version available the last time I tried to load 10.9 a few weeks ago - I now see 3.3.1 is out). OSX 10.9 is my target... don't really care about 10.8.x if I can get 10.9 working.

Oh I see. I haven't checked in the SLE folder on 10.8.5 for null. Will check tonight. I assumed it was not null, but I'm sure you are right You seem to know this stuff a lot better than I do.

The one on the osxlatitude Bootpack page for 10.8 and E6220's ( http://www.osxlatitude.com/packs/Dell/Dell_Latitude_e6220-ml.zip ). And yes immediately after installing 10.8.5 fresh I installed the supplemental update. No issues at all. Sleep works... not sure about power management (not really sure how to check that even lol) but I assume it works... I've been holding out on getting 10.9 working so I haven't used this E6220 too much under 10.8.5.

I installed 10.8.5 fresh, no upgrade from 10.8.2, perhaps that's the difference

Strange cause I have no issues with 10.8.5 ML

4GB ram here (2x2GB). It must be the processor though... I'm guessing most ppl have an i5, not an i7 processor. I have sent my dsdt stuff to Jake Lo and he did send me a custom Extras bundle but unfortunately it did not solve the problem. Not sure what else can be done, but I'm sure that there will be plenty of other people that run into this same problem in due time (since Mavericks is now out) and that someone much smarter than you or I will figure it out Just need to wait and see

Glad I'm not the only one with this issue anymore I'm sure we'll figure it out eventually. Must be related to our processor.

I'm sure that will work as I did that a week or so ago and it was fine with null. Just hoping to get it working without using null.

That worked! I installed with -f -v -x AND after the install booted up for the first time with -f -v -x and it worked! I used EE's provided to me by Jake Lo. w00t! Testing now to see if there is anything broken. (Still running through wizard right now). EDIT: Haha, well, booting in safe mode works... in regular mode I still get the usual AppleIntelCPUPowerMangement Kernel Panic Hmmm

Tried your Extra's (manually deleted my SLE AppleIntelCPUPowerMangement.kext before installing yours via MyHack) but unfortunately I still get a kernel panic on it Any chance this is related to a BIOS setting that I might have misconfigured? Wondering if I should maybe give one of you pros access to my 10.9 Mac via TeamViewer or something so that you can take a look over of it

Hmm, AppleIntelCPUPowerMangement KP Will have to look into this more next week, heading out of town for the weekend.

I'm going to re-install 10.9 with Extra's that tarfoh provided to me yesterday (I had provided him my DSDT and SSDT files yesterday). If that somehow fails I might try your Extra's chleea daspazz: I had done that, yes (installed latest Chameleon). Issue I've always had is with AppleIntelCPUPowerManagement.kext. Hopefully this clean install that I'm doing now will result in a fully functional system like I already have under 10.8.5.

Here are my DSDT and SSDT info files (and System Device Info too just in case...). Will PM tarfoh as well. Thanks! trafsta-DSDTandSSDTandSystemDeviceInfo.zip

Cool thanks. One more question related to your signature; What does 'rebranding' your DW1510 do? Does it simply make it NOT show up as a third-party wireless device? Edit: nevermind, just saw https://osxlatitude.com/index.php?/topic/2652-e6430-mavericks-109-dp1-successfully-installed/&do=findComment&comment=20309 and https://osxlatitude.com/index.php?/topic/2504-installing-ml-on-dell-e6530/?hl=%2Bdw1510+%2Brebrand&do=findComment&comment=18850 and subsequently http://www.osxlatitude.com/rebranding-broadcom-802-11abgn-cards-as-airport-extreme/

DELL HALF-MINI WIRELESS N CARD DW1510 BROADCOM BCM94322HM8L DW 1510 MINICARD http://thmb.inkfrog.com/thumbn/fenvi/13414_5.jpg=550 http://thmb.inkfrog.com/thumbn/fenvi/13414_6.jpg=550

Ok will do. Does it matter that I still have an Intel wifi card (which obviously does not work) in the E6220? Should I wait until the supported Wifi card arrives in the mail?

Tested out the instructions above at work on a E6400, works well (Ubuntu Live USB). Question though: I do not yet have the non-intel wifi card in the E6220. Should I wait until I receive it (few more weeks till it arrives - bought from eBay) or does it not matter for what you are going to do for me? Also, I later found this forum post: https://osxlatitude.com/index.php?/topic/1945-dsdtssdt-patching/ Should I be using these instructions instead? They seem different than the post above (more complex)

Sure, I can do that - right after I figure out how I'll hunt around the forums for instructions (I recall seeing them around somewhere once a while back) Edit: Found instructions @ https://osxlatitude.com/index.php?/topic/1224-e6520/page-2&do=findComment&comment=11239 . If I have some time I'll try them tonight.

Dell Latitude E6220 for 10.9 (Link: http://www.osxlatitude.com/packs/Dell/Dell_Latitude_e6220-mav.zip) http://www.osxlatitude.com/edp/compatibility/

Booted into 10.8 partition, used terminal to rm -R /Volumes/MacHD10.9/System/Library/Extensions/AppleCPUPowerManagement.kext and then copied Maverick Extra's (from osxlatitude website) to /Volumes/MacHD10.9/System/Library/Extensions (followed http://www.osxlatitude.com/remove-kext-from-single-user-mode/) then ran MyFix from latest MyHack on /Volumes/MacHD10.9, rebooted, selected 10.9 partition and voila, it worked! I think I'll leave this 256GB SSD with both 10.8 and 10.9 partitions for now as well, can perhaps load 10.10/11.0 when it comes out overtop of the 10.8 partition... nice having both available in case one gets blown up. Just need to wait for my new Wireless NIC to arrive from eBay, then can start using this E6220 Thanks for all your help everyone!

Thanks Jake Lo. Unfortunately I still receive the same error with that boot pack in Mavericks (AppleIntelCPUPowerMangement KP). Anyone have any other ideas? Has anyone here gotten Mavericks to work on an Exx20 series laptop? I guess with Mavericks announcement from Apple today (I think it's happening right now?) there might be more people trying Mavericks on their hackintosh soon enough...

Just wanted to give an update - your instructions on the other thread worked out VERY well for me. ModUSB was great. The D420 is running 10.6.8 quite well. The only issue with this Core Duo system is of course it heats up quite a bit, but I don't think there is any way around that (intel speedstep issue I'd imagine). Again, thanks for your help!