v3ct0r

@rwsgamer,

You may have to modify the org.Chameleon.Boot.plist...

To do this, open up Terminal and run:

sudo nano /Extra/org.Chameleon.Boot.plist

Use the arrow keys to navigate. Modify the resolution to match:

1440x900x32

And make sure the UseKernelCache is set to "No" if you still have to boot with -f

Press Ctrl+X, the letter Y and Enter.

Hey marlawre,

Did the HDD in the computer ever get wiped/zero-filled? If so, you may need to create a new partition map. You can do this with an Ubuntu/GParted/Other Linux Distro Live DVD/USB.

Also, can I suggest trying a Mavericks install? The install procedure is much simpler and there are less issues reported than Mountain Lion.

Thanks Jake Lo for the answer.  Since I still had the same problems with iMessage and AppStore, I did a full reinstallation from the start.  I followed deano019s advice for iMessage, I did generate a serial number with Chameleon Wizard, changed the PlatformUUID following instructions  and still no deal.  I generated again a new serial number wit CH Wizard, but still no go.  I could live without iMessage but AppStore appears to be a problem for getting new Apps or even any future version of OSX. As now, updates from AppStore are functionning . But I am unable to download new apps. Error  messages are the same as mentioned in post no. 259.  Am I a case apart or is this a known problem ? Is anyone with the same configuration having the same problem ? I would like to hear from you.

 

Thanks in advance

Nope, this problem has been happening to other people as well...

Try barkerman's solution here

In the BIOS setup, set your boot order so that your 2nd hard drive is at the top of the list followed by your other drives in whatever order you'd like. You should be able to select between Windows 7 on the first drive and OS X on the first drive via Chameleon on the 2nd drive.

For the iMessage fix(es), check the Troubleshooting section of the guide. 

Hey guys, sorry for the long absence! I've been extremely busy with life.

@vgalandin: In System Preferences -> Energy Saver -> look for the computer sleep slider and slide it to "Never"

@barkerman: Thanks for posting back! I'll include this as another solution in the guide.

Yup, that kext should not be needed on this system.

Deano's post (which I've linked to in the Troubleshooting section of the guide) should fix the problem.

Hello all and sorry for the absence. I've been extremely busy these past few months.

In addition to what Hervé mentioned, please do try the steps located in the troubleshooting section of the guide, which can be found here:

https://osxlatitude.com/index.php?/topic/3112-dell-latitude-e6410-mavericks-guide/?p=24235&do=findComment&comment=24235

If that still doesn't work, post back here and we'll figure it out .

Haven't noticed anything weird about the update on my end...

Can you bout with -v until the kernel panic shows up for you? Then just post a picture of where it hangs here and we'll try and sort it out.

I've noticed a good battery life boost between the older BIOSes and A14. Also, the fan is more controlled in the later updates.

Check the change logs if you really want to know.

To make a bootable DOS drive:

http://www.sevenforums.com/tutorials/46707-ms-dos-bootable-flash-drive-create.html

After that, throw the BIOS executable on the root of the drive:

http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=WMHW9

Lastly, when it boots, execute the executable by typing the following:

E6410A14.exe[PRESS ENTER KEY NOW]

Hi IONIX,

on you Dell Wireless 375 Bluetooth did you have it shipped with your system?  What model is this machine.  I have dell e6410 and don't have Bluetooth preinstalled.  So I like to get a sense on installing it myself.   Also, the Dell Wireless 5540 3G/HSDPA are you using it?

 

Thanks.

I had ordered a DW 375 Bluetooth for my system after I got it. I installed it when it came (a bit of a process is involved, so make sure you have time!) and it works with OS X just fine. Can't comment on the DW 5540 though; I took mine out because I didn't use it. 

Bronxteck,

Thanks much, that was a solid answer.  This definitely encourage me to triboot (chameleon, stolen and rebranded) as I was thinking I had to go to BIOS to do the switch every time.

 

So  if I had set BIOS to AHCI on let say a Dell Latitude e6410 with a blank HDD, does the following high level steps works?

with patel's note

"

Also, for those who have MBR Disks, you can install Mavericks to said disk by copying the following files from the MBR Support folder after you finish Creating the Installer:

1. Copy OSInstall.mpkg to [iNSTALLER ROOT]/System/Installation/Packages

2. Copy OSInstall to [iNSTALLER

"

1. create hackintosh partition. Linux, Windows.

1.1 install Chameleon

2. install OSX

3. install Linux, Windows,

 

So every time I cool boot I can choose OS to work with?

 

Thanks in advance.

I found this:

http://lifehacker.com/5698205/how-to-triple-boot-your-hackintosh-with-windows-and-linux

It's a bit dated, so it references Snow Leopard/Windows 7/an older version of Ubuntu, but it should work the same way with the current OSes.

Hello all, 

Just wanted to let you know about the new guide update. It has been updated to reflect the following:

• All fixes to date are included
• VoodooPS2Keyboard Kernel Panics on first boot are gone
• No more Post Installation steps required!
• Installer creation has been slightly simplified.

Hello all, 

Just wanted to let you know about the new guide update. It has been updated to reflect the following:

• All fixes to date are included


• VoodooPS2Keyboard Kernel Panics on first boot are gone


• No more Post Installation steps required!


• Installer creation has been slightly simplified.

Under System Preferences, click on Sound, and then the Input tab. Select the Microphone (digital) from the dropdown list.

Try and delete VoodooPS2Keyboard.kext from /Extra/Extensions and reboot

EDIT: Don't forget to run a myFix on the drive you deleted it from!

Thanks for the heads up, npolite!

Also, if you mean the stock wifi card that came with the E6410, then no, there is not a driver that I currently know of to get that working. Your only option would be to swap it out for a Broadcom 4322/Dell Wireless 1510.

Ok after going through the guide I found my problem. It was the option in the BIOS uncheck "Enable VT for Direct I/O". I must have missed that the first few times. Once I unchecked that I was able to get the installer going with no problem. Thanks Patel and Darvinko for your help.

Hey npolite,

You didn't miss that! I just put that up this morning! After ako posted his solution, I added it to the guide for the future.

Great. Thanks for letting me know about these issues!

Check for any output devices under the Sound section of System Preferences.

When you created your installer, did you use the myHack.app from within the Applications folder? This is an error I've seen when you open myHack after downloading it directly from the desktop.

Hey darvinko,

Do you mean that myHack should be run from the Applications folder of the boot drive instead of the installation drive? Or vice versa?

Hey guys just found the reason why it didn`t boot.

 

I had to disable VT for direct IO in bios.

 

But...

 

I knew, on my first Installation of OS X ever, I had to disable that to get it working properly. Then, I installed Virtualbox and XP as guest OS which needed that VT for direct IO function. So just for fun I enabled it, and kind of wondered why the system booted with that function enabled. Now, after the update to 10.9.2 it has to be disabled again.

 

Do you guys have an idea what allowed that function to be enabled, so I could do that again and use it for Virtualbox?

Did VT for direct IO need to be enabled for 10.9/10.9.1 (where os x is the host os/not in vmware)?

Boot to safe mode and try to remove voodooPS2Trackpad from /Extra/Extensions.

Make sure you back the kext up to somewhere like the desktop before deleting it.

Unfortunately, I have some bad news too.

The reason why things like sleep and the monitor switching used to work before is because the computer didn't have any recollection of a graphics card/there were no drivers. It won't wake up (I'm guessing here) because it can't restart/bring the graphics card back up.

This is (for the most part) because of the nonexistent LVDS connector in the Intel E6410 as well as some edits that need to be made to the DSDT. The DSDT can help with the sleep and maybe with the dual displays; I'm not very knowledgeable about DSDT edits, which is why I can't get certain things to work on other machines. 

Which brings us to the bad news . Since only CI will work on the Intels, it all comes down to a choice. You can either keep CI and have full resolution on one monitor at a time without sleep, or revert back to a system with working sleep without full resolution on the second monitor (no graphics driver/CI).

Maybe someone more experienced with such an issue can prove my assumptions wrong, however this has been the most abundant answer I have found in my research. 

Try the Enable Core Image steps in this guide:

http://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/

Nope, that's good for now! If you could test one more thing however, that would be great.

Open up System Preferences > Desktop & Screensaver > Screen Saver. Click on one of the slideshows. If you see the preview, post back here and let us know. Basically we're trying to see if core image is enabled at the least.