Darvinko

For future updates, you can usually update without wiping. This will save any information (photo, documents, etc.) you have on your computer. I thought you upgraded from 10.8.5 installing over that version, instead of wiping and do a new install.

The update shouldn't change the serial number. Nor does it normally change the model, which appears to be the case, thus the change from 15" to 13". Based on the screen shots, it look as if both have been changed. Assuming it was an App Store update as indicated in your initial post.

At first glance, it appears OK. If you are worried, either wait a little longer for users to notice any possible problems or create a backup.

Your screen shots show different serial numbers - check the SMBIOS. I have updated my E6410 with no obvious issues.

Apple's OS X builds (up through the latest developer builds of 10.9.2) have a SSL flaw which keeps the certificates from being validated. Translation: use caution as this leaves you vulnerable. It is suggested that you avoid using your devices on unprotected networks with questionable security (no encryption). The flaw allows someone to intercept and view or modify traffic over non-protected or poorly protected networks (read WEP encryption). Patches are expected shortly (and have already been released for the same flaw in iOS devices (iphone, iPad, ipod & Apple TV)). Until Apple resolves this SSL validation issue, you should avoid questionable and public networks and update as necessary only by trusted networks. Additionally, you might want to change the setting on your "Ask to Join Other Networks" to "OFF"

Here is a link to the patch (iOS 7.0.6) for the appropriate devices. Apple has not yet released a patch for OS X devices. - http://support.apple.com/kb/HT6147  For older devices and Apple TV patches, see here: http://support.apple.com/kb/HT1222

UPDATE: Apple has acknowledged the issue and has promised that a patch will be available "very soon". I will add a link to the patch if necessary, although I believe it will come through normal update procedures, possible even a "forced" update (one that downloads in the background and installs upon a subsequent reboot).

UPDATE 2: It appears that the flaw MAY be limited to Mavericks builds 10.9.0 to the current developer 10.9.2 beta 7 build (I'm not certain about earlier pre-GM & GM developer builds as I no longer have them) and is due to a duplicated line of code. Hopefully it will only require removing that line, recompiling and testing.

UPDATE 3: Apple has pre-released 10.9.2 to some employees, with FaceTime audio, Call Waiting for FaceTime Audio & Video calls, the ability to block incoming iMessages from individual senders and a patch for the above mentioned SSL issue. Past practice indicates this is done just prior to a public release, so it is unknown whether a stand alone patch (such as was issued for iOS) will be issued, or if the patch will be incorporated into this build. 

As you may know, Apple has released 10.9.2, which, along with the SSL patch, has provided updates/upgrades to other features, including those listed above. There is currently no stand alone patch for the "gotofail" issue. Additional security updates have also been issued for Lion and Mountain Lion.

There are two choices for that model - 1280x800 or 1440x900 if that helps.

Thought you had it - they are in Console

What has worked for me on two recent hackintoshes is to add the NVRAM file to a created Modules file in Extra on the installer. Go through the install and I have working iMessages after set-up. I have not confirmed this to be the positive solution, but anyone starting a new hackintosh project or willing to do a reinstall of an existing one, please consider this and report back with your results so we can confirm if this is a work around or another dead end.

See if this works for your ethernet: http://www.osx86.net/files/file/482-bcm5722d-mini-for-ml-and-lion-and-sl/

Might be a Mavericks software issue - see here: https://discussions.apple.com/message/23547505#23547505 and the other link that is in this thread.

Have you checked your logs to see if they give an indication of whats going on?

There are some listed on eBay already rebranded.

Aside from the things Bronxteck has already mentioned, I'd like to add a few other items.

 

I participated in finding a way to install Mountain Lion on a Dell Latitude E6400/E6500 laptop. Fortunately, there were several other members with the same machine, a good bit of knowledge and time to commit to working on it. As much as our machines were closely spec'ed, there were factors that created issues as well as unexplained circumstances that allowed certain aspects to work for some, and not others. Among the factors that were noted were:

• different flash drives can produce different results (often related to read/write times)
• type of machine used to create the installer (virtual machines, hackintoshes, real Macs)
• source of OS (torrents often had a propensity to failure)
• failure to properly configure BIOS and human error. When there are fewer people (as is likely the case for your machine)
• changes to plists (as you experienced with audio) are not always noted, or forgotten.

 

Especially if you have configured your build in Lion and updated to ML for example, you might report it working, forgetting about changes you made. I have always viewed this site as a resource, a place where I can try what others have had work for them, learn a little about how these things work, figure out what doesn't, try a few things, and contribute to the community by offering what I have found to work or what hasn't worked. I enjoy the challenge of finding the solutions for my circumstance. I have always tried to help others find solutions, explain how to complete certain tasks, but I also feel strongly that these things are a mutual undertaking, a little effort leads to a lot of understanding, making the student capable of contributing to the community.

 

We all hope that, just as you shared your audio solution, you might volunteer to help correct any potential problems with EDP by volunteering to "test it periodically against EDP" to help the next member (new or old) who decides to use that machine.

If you're installing in a E6510, try using the Extra for the E6410 from Patel4Prez.

Erm, I would have not expected the Vostro200/Inspiron530s DSDT to work on that machine; there's nothing in common at all. If any Dell DSDT were to be used (and I would never recommend that), it would be the D430's which bears some similarities with this HP's hardware (GM945 chipset, GM1950 graphics, ICH7-M controller, etc.)

 

Try and list your lspci -nn specs to see if we can do anything. For Ethernet, the E1000 or E1000e kext might work...

 

Yeah, my bad - 12 hour day at work and an hour commute and my tired eyes read DELL 530 instead of HP 530.

Your UID is 4. Can we assume you added it correctly (you have "PCIRootUIT" shown above)? Also PCIRoot=4 is enough, the UID isn't necessary.

Try using the Extra that is posted and the bottom of the first post in Mountain Lion Anyone (replacing the one you have, then running a MyFix (FULL) on the drive afterward).

Try using the DSDT.aml that Hervé has used in the Vostro 200 bootpack (try the whole bootpack actually). It works well on my Inspiron 530 (see signature), including sleep. For ethernet try: Intel82556MM.kext found here: http://www.osx86.net/files/file/1631-intel82566mm-kext/

You should be able to boot either Mountain Lion or Mavericks if so desired. Mountain Lion is a little more of a chall"nge, Mavericks somewhat easier. Your model is the same as the E6400 with the exception of the screen size, so you can use one of the guides from the forum. "Mountain Lion Anyone" thread is thorough, and there are others. Lion will use the same bootpack (Extra). One thing to keep in mind is the Intel WiFi cards that usually ship with these are not supported by OSx and will need to be changed. This is a good thread to start with for Lion installation: https://osxlatitude.com/index.php?/topic/1100-dell-e64006500-research-thread/

You are probably going to have to find a DSDT for your system and place it in the Extra or extract and patch one. There is a documented procedure on the forums for having one prepared for you.

Not sure if I leave enough room on my desk for one of these!

That is often a consequence of adding the MBR patch to the installer USB. If you have added this patch, you will need to remove it. Conti has posted instructions on these forums recently on how to do so. If I have time, I will find and post the link.

 

https://osxlatitude.com/index.php?/topic/5890-after-language-selection-the-os-x-installation-couldnt-be-completed/  see post #4

I believe you need to update the trackpad kext - it is in the thread for this model: https://osxlatitude.com/index.php?/topic/5582-mavericks-on-e6410-intel/page-4  post #64.

Curiosity (and rechecking my memory) got me to pull out my Inspiron 530 (not an S model), with the G33M03 board to check and a refresher course over at Bios-Mods. At the time I decided to bypass the BIOS mod due to conflicting information in the 530 thread (what was working, not working, which board etc). I was able to "locate" my HDD by using the AppleIntelPIIXATA plugin on the IOATAFamily.kext, which allowed me to setup my computer. After, I installed DSDT from ??, which had everything working but sleep. It currently remains one of two holdouts with ML in my inventory. As per Hervé's suggestion, I tried LatinMcG's DSDT and found it to be an excellent choice, as it enabled wake from sleep and the need for the AppleIntelPIIXATA plugin. It can now return to hibernation, knowing all is well.

You can try adding a patched IOATAFamily.kext or an AppleIntelPIIXATA2.kext into your installer's Extra and see if that allows your hard drive to be seen for set up.