inedible

Ahh, okay, missed that step. Now my dmesg log says things like: GPM: GPU = VID G-state set to 1 from 0, ControlID = 17. SW occupancy updated. AGPM: updateGPUHwPstate(2, 0): fHwPstate = 1 fFB = 0xffffff8012520800 AGPM: updateGPUHwPstate(): state = 2. Calling fFB->setAggressiveness()... AGPM: GPU = VID G-state set to 2 from 1, ControlID = 17. SW occupancy updated. Which seems good. I can't say for sure if it's actually running any cooler, but those are reassuring log entries.

Back on page 21 or so, when I was playing with editing the DSDT, I found that it was the displayport's audio chip preventing sleep mode from working. It's the HDA device in the DSDT, and I recall it's missing some return value, preventing sleep from working. Could be related. I dunno. I really have no idea how any of this works, I make it up as I go along. rmk: I tried adding that, but it's giving me "[AGPM Controller] unknownPlatform" in the log now. I'm not sure if I put it in the right section. I added it right after this part: <key>MacBookPro6,2</key> <dict> <key>LogControl</key> <integer>1</integer> <key>Vendor10deDevice0a6c</key> (your code starts here)

Hmm, nuts. It looks like this must be the drive that came with it. Funny that it's not in dell's firmware section. I replaced it with a TS-U333 (DVD-ROM, not RW) that I had laying around, and it seems to have shut up now. Edit: Though, the eject icon by the clock now says "No Drives". That's fine though, the button works. PS: So, the last thing remaining is power management, speedstep, and sleep, which I guess are all the same problem. Where did you get the DSDT.aml that you include in the zip? What modifications have been made to it? As far as I can tell, it's not stock, and it's not this patch: http://olarila.com/Packs/Dell/Latitude%20E6410.txt I tried removing NullCPUPowerManagement, and the system still boots fine, leading me to believe I'm now using unpatched native power management, but speedstep and sleep still don't work. Also, the battery icon is an X half the time I boot up now.

Any chance you read the model number off the drive itself? There's one screw holding it in at the bottom, then if you push in the little plastic tab at the bottom right, you can simply slide the drive out. Mine is a model GU10N Hmm, could be firmware I suppose. If it wasn't seated correctly I doubt I'd be able to actually use the drive to burn and read discs. I'll have to figure out what model this is first though. Dell's site lists four possible drives for this model. Also sucks I'll have to install windows in order to apply the update

Hmm. Odd. It does it on a fresh install. Could be my dvd drive I suppose. It might have been from a different model of dell. Do you have an eject icon by your clock? If so, does it work? I also just noticed the "Disc burning" section in system information sits there blank with a spinning wheel in the corner. Interestingly, the drive works perfectly fine, and I've used it to burn several discs from Disk Utility.

Has anyone noticed an issue where your cd drive gets accessed once per minute or so? The light comes on and it tries to read a disc, even though there's not one in the tray. Also, there's an eject button by the clock, which if I click it, it freezes the whole clock area until I reboot. I think this eject button only shows up after VoodooHDA is installed.

I didn't mean to get your hopes up about the nub mouse... I just meant that it seems for the trackpad we don't have to go through the hassle of deleting all the PS2 kexts or copying that daemon. It seems to work on a fresh install just by installing the single kext. The little jump that the nub does no longer bothers me, since I disabled it with a piece of tape like so: http://imgur.com/a/GnUhN Not really a solution if you actually use the nub, but I never touch the thing.

Ok, that's good to know... I was about to order a 1520 actually, since I must have misread something somewhere. I guess I was confused by the fact one is a BCM4322 and the other is BCM94322? I dunno. Anyway, I found an Atheros AR9285 I had laying around, which I did manage to get working, but not without some setbacks. I ended up needing to reinstall from scratch in the end. After installing the card and patching /S/L/E/IO80211/Content/Plugins/AirportAtheros40.kext/Info.plist to add the PCI ID [168c:002b], I got errors like these: kxld[com.apple.driver.AirPort.Atheros40]: The super class vtable '__ZTV17IO80211Controller' for vtable '__ZTV22AirPort_AtherosNewma40' is out of date. Make sure your kext has been built against the correct headers. kxld[com.apple.driver.AirPort.Atheros40]: The __ZTV26AtherosNewma40P2PInterface was not patched because its parent, the __ZTV19IO80211P2PInterface, was not found. It turns out there's some copy of IONetworkingFamily.kext being loaded somewhere else that's an incompatible version. I removed the copies at /Extra/Extensions and at /S/L/E/myHack.app/Contents/Plugins/ and it loads successfully. In my new install that's the end of it, the card works perfectly, but in my old install, it started acting like the airportd problem, where it would immediately say Connection Timed Out, even though I was already using the old 10.8.3 version. It turns out there was something strange about the authentication, and if I went into Keychain Access and deleted all instances of my AP from both Login and System, then it would at least pop up asking me for a password. But then, when I entered the password it would instantly say Connection Failed, and the system log would say it failed because no password was entered. I'm not sure if any of that helps anyone, maybe provides insight into how 10.8.4's wifi authentication has changed. Either way I couldn't figure it out and needed to reinstall. I thought maybe I needed the 10.8.4 copy of airportd, so I applied the combo update again, then before rebooting applied the kexts in the first post (IOACPIsomething.kext), but for whatever reason the combo update broke Chameleon, and on reboot I was given "cannot find /mach_kernel" So anyway... After reinstall everything works now, and this Atheros card seems to be doing a great job. PS: Patel: About the trackpad - This install I tried just installing the VoodooPS2.kext on a fresh install, without deleting any other PS2 kexts, and without installing the VoodooPS2Daemon program. It seems to be working fine this way. I have no idea why last time it decided to not work unless the other PS2 kexts were deleted. You may want to add the VoodooPS2.kext in the post-install instructions, in the same section as VoodooHDA, and leave the current instructions under troubleshooting.

Darvinko, if I'm not mistaken that's the same card other people are using. There are kexts available for it. The options are pretty limited here, it needs to be a half-height card, since the antenna wires don't reach the full length slot. I don't think there are any actual airport cards that are half-height.

This isn't strictly hackintosh related, but here is how I disabled the nub mouse: http://imgur.com/a/GnUhN I never use the nipple, and since the kext we're using for the ALPS touchpad makes the cursor jump every time it's touched, I wanted to disable it. Apparently in windows you normally use special dell software for disabling it, and there's no option in the BIOS either, so the only way is to disable it is to physically remove the hardware. Rather than cut wires, I figured tape is a better choice as it's removable in the future. You could also use nailpolish on those pins, then chip or sand the nailpolish off when you want to re-enable it. Edit: I don't recommend anyone do this while the laptop is on. I only did it because I'm reckless and irresponsible. I take no responsibility for anything. PS: The three copper pins to the right are for the backlight, in case you ever feel like completely disabling the keyboard's backlight for whatever reason, you can cover those pins as well.

V7 seems to work fine on my E6410 (ALPS Device with ID E7=0x73 0x02 0x64, EC=0x88 0x07 0x9d) It does something weird with the trackpoint nub though... Any time you move the nub, half a second after you let go, the cursor will jump up and to the right about 20 pixels from where you left it. I have no other PS2 kexts anywhere on my system. It does the same with both v5 and v7. It's not just me either, Here's another report of the same thing happening with the same model laptop: https://osxlatitude.com/index.php?/topic/1695-e6410-mountain-lion-guide/?p=21282 Any idea why that happens? Also is it possible to use a different kext for the nub than the trackpad?

Patel4prez, yes I'm having that issue too. I don't use the nub though so it hasn't really bothered me too much. I was planning on trying to disable or unplug the nub. I noticed something else, the two-finger scroll "bounces back" a few pixels at the end of your scrolling, but only if you "flick" it, not if you gently release it.. So, if you scroll all the way to the top of a document, it will scroll back down two to five pixels if you let go too fast. Normally this isn't annoying at all, but it makes zooming in on google maps really annoying. Edit: Tested v7, still same problem.

Okay, so I've played around with DSDT editing a bit, and I can't figure anything out. I dumped a fresh DSDT table from my bios using a ubuntu livecd, then applied this patch file: http://olarila.com/Packs/Dell/Latitude%20E6410.txt It compiles with only one remark and a bunch of optimizations, but it still says sleep is being prevented, and plus, when I use the DSDT.aml that I compiled, I lose my battery status icon. I really don't know enough about these things to know why. Patel4prez, where did you get the DSDT.aml you include in the package? I'm semi-convinced we should be able to get sleep, speedstep, etc working via DSDT editing.

I have a bluetooth module in mine, and it works perfectly, even during the install process. No extra steps needed. System profiler says it's a broadcom module: Vendor ID: 0x413c Product ID: 0x8187 ACTUALLY, I shouldn't say "no extra steps needed" because having a bluetooth module means the setup process asks to pair a bt keyboard and mouse, and the only way to shut it up is to either do as it asks or plug in a USB kb and mouse. For some reason the installer doesn't recognize the PS2 kb/trackpad even though they do work during setup. I should have mentioned earlier, you may want to put in your guide "If you have a bt module, have a USB kb/mouse handy" Try booting in verbose mode, that'll tell us where it's failing. My guess is those kexts didn't get installed correctly, and you may need to install them by hand from the USB key.

Ok, so looking in dmesg it says "System sleep prevented by pci10de,be3" which is apparently the Nvidia HD Audio controller. I guess it has a separate audio port in the displayport output, which is preventing it from sleeping. According to this: http://olarila.com/forum/viewtopic.php?f=19&t=634 I should remove the _PRW section from the offending device's DSDT section, which seems to be HDEF. I really have no idea what I'm doing here, but I'm about to test. Will edit this post in minutes. Edit: Nope. Removed the _PRW section from the HDEF device, but it's still saying "sleep prevented by 10de 0be3" Edit2: Also the battery icon goes missing.