Igashu

Hi daspazz et al, sorry I've been AWOL for awhile, and I'm glad you managed to figure out some of your issues! The default NIC that came with my E6520 was actually an Intel ABGN card of some sort - from everything I read there was basically no way to make it work, so I grabbed an Atheros for like $5 from Ebay and haven't looked back since. One thing I will say is that I'm not sure that the edits in the most recent (r3) Extras were an improvement. It may just be me, but I found that my graphics were not functioning properly with the new DSDT and kexts after going r2->r3, so I rolled back. @iMick, if you have any time to help look at this again, would be nice to iron out some of these problems. In the meantime, reposting r2 in case it helps anybody else. Extra-Igashu-E6520-r2.tar.gz

One thing you can try, to eliminate the possibility of it being an actual USB device issue, is to create an ~8gb partition on your ssd, use myHack to set THAT up as an installer, and boot to that partition from Chameleon. I have done that before too, and it does work... other than that I'm at a bit of a loss as to why it won't boot for you.

Maybe a silly question, but you are actually booting from the USB drive, right? Not just choosing the USB drive at your normal Chameleon boot? You should be booting directly to the USB drive like, from BIOS.

I see an ath_dev_attach failure up there too; you may want to remove the DeviceMergeNub.kext if you're not using the Atheros wifi card. Is this failure just trying to boot to the myHack installer, or after installing and trying to boot from your drive?

Regarding your questions: You can name it anything you want (preferably something OTHER than Extra -- when I create a myHack stick, I tend to create a folder on the root of the volume called "My Extras" and then inside that keep a directory with an appropriate folder for each of my machines (e.g. "Extra - Sabertooth P67", "Extra - E6520", etc...), which leads to point number two... Placing the folder on the stick is just something you can do manually by copying it. After you've booted to the stick, and toward the end of the OSX install via myHack, it will prompt you to choose whether you want to use its default Extra folder (which is designed to load very little, and only load common things that will boot on most machines) or specify your own. If you choose to specify your own, it'll let you browse the filesystem and pick the one you set up, which is why it doesn't matter where you put it or what you call it, as long as it's there. It will copy it over to your hard drive (or in your case, your 512gb OCZ Vertex 4 - nice!) so that it can boot the system with this DSDT and kexts. Yep!

So, my recommendation would be to use something like Carbon Copy Cloner to make a backup image of your existing 10.7.5 drive in case things go horribly awry, and then follow my instructions in post #10 above for creating and using a myHack USB installer. There's no need to 'upgrade' OSX - for the most part you can literally just do a full, fresh install right on top of your existing one, and all of your user files and data etc will just continue to work as they did before. If for some reason you did want to do a reformat/reinstall from scratch, you can always use Migration Assistant after the fact to re-import your user accounts and data from your backup drive. EDIT: To specifically answer your question, any USB port will work, although I *have* noticed that if I have multiple USB devices plugged in at boot time on the E6520, sometimes it will only see one of them. When I'm trying to boot from the myHack USB drive, I unplug my USB external. No special boot switches should need to be used to get into the installer. I agree that between all the threads, there is a lot of confusion on how to get to a working state. I created this thread to try to make a single, straightforward source of information for E6520 (and honestly, probably E6510 too) owners. There's also an awful lot of misinformation and conjecture out there (not just on this forum but on other popular shall-remain-unnamed ones) concerning the various flavors of voodoo people believe has suddenly made their hackintosh work. More often than not, people have run many tools and installers essentially "throwing things at the wall until something sticks" and don't really even know what path they've taken to get there or what additional files may be in their System/Libraries/Extensions that are making things work properly. (Without intending to offend you, your own claim of "can't honestly remember how I got there" is a perfect illustration of that fact.) This is all a lengthy lead-up to me saying that I've tested this E6520 extra on a fresh install of 10.8.2 with zero modifications. If you have the same hardware and follow the process, it should and will work for you too.

It is probably not the Bluetooth controller, most likely fails on something a bit further up and just doesn't hang until then. What system/specs/hardware do you have? Are you booting from a myHack USB? Try booting with nv_disable=1 and see if that helps.

Sure. There is a full guide over at their website (http://myhack.sojugarden.com/guide/) but the basic steps go a little something like this: Download myHack from the above site, and run it At the menu, choose "Create OS X Installer" Select "Create OS X 10.8 Install DIsk" Choose your USB flash drive from the menu that appears ("Select target volume to run myhack on") myHack will either scan your system automatically, or you can point it to your downloaded 10.8.x image from the App Store. myHack will do its thing - this takes awhile - but you'll end up with a bootable install USB. Create a folder on the USB drive and copy over the contents of my Extras zip (extracted, not as a zip file!) When you boot from the USB drive, it'll lead you through the install process much like the normal OS X installer, but will give you some options near the end to install a default Extra or select your own - select the folder you put my files into and it will install them automatically. ??? Profit! If you're unfamiliar with myHack, one of the things it does is places a myHack.kext into your /System/Library/Extensions folder that contains all of the kexts from /Extra/Extensions. The "myFix" operation from the myHack program will regenerate this kext, so if you add or remove things from /Extra/Extensions, be sure to run a myFix again before rebooting to ensure they take effect. The nice thing about this approach is it leaves your SLE clean - all changes are encapsulated in the Extra folder, so it's easy to share and repeat. If you run into problems, make sure to boot with -f -v (no caches, verbose) so you can actually see what's going on - a pretty splash screen doesn't do much good in troubleshooting.

The AR5B95H is slightly different from my AR9280 (I believe it is a.k.a. AR9285) but this may be the same problem. The kext that I had been using only had support for Atheros21 (which does not work with 802.11n) and I needed instead to inject Atheros40 support. You can test this by setting your router to b or g-only mode and seeing if it works. (As far as the Bluetooth PAN goes, try just deleting the connection and re-adding it; it should come up as Wi-fi, it won't say Airport.)

Be careful using unifail/multifail. It will tend to modify/install kexts directly in your /System/Library/Extensions and can lead to some puzzling problems when you upgrade. If you have the time, I would do a fresh install using myHack and put my Extra folder on the USB installer, so that when myHack asks you if you want to use a generic Extra or your own, you can select that one. With mine, audio should work (using VoodooHDA/HDAdisabler), and if you happen to get one of those Atheros 9280 half-height cards (e.g. http://www.ebay.com/sch/i.html?_trksid=p5197.m570.l1313&_nkw=ar9280&_sacat=0&_from=R40) that will work with my dsdt/kexts too. (You can also look at Apple-branded Broadcom cards as those are generally recognized right out of the box.) Also, try to install Chameleon instead of chimera (chameleon, stolen and rebranded); avoiding tonycrap's stuff wherever possible is a good idea.

MacFace, I'm confused now. You say that you have NVidia Optimus technology - I am assuming that means you have the NVidia 4200M as well? In our BIOS, disabling Optimus disables the Intel HD3000 and only presents the NVidia chip. It's not recognized out of the box by Mountain Lion, which is why you're seeing "3 MB" Regarding your other issues, you need to remove the tscsync.kext - your second error screen isn't super informative, but I'd be willing to bet it is actually a graphics issue, requiring patching (or overriding) your nvidia kexts. Your wifi will likely never work unless you replace the card with another one. I recommend the Atheros 9280. I'm interested in what errors you get with my Extra pack - it sounds like you have a similar configuration.

MacFace, this may not be your issue as it seems to be at a much lower level with the controller/device error, but one thing I found was necessary for the 10.8.2 update was the removal of OemSMBIOS.kext -- look inside your FakeSMC plugins, or possibly even your System/Library/Extensions for an OemSMBIOS.kext (and delete it, then myFix.) I understand your E6520 may have different hardware from mine - not sure if you have NVidia graphics or just the Intel HD3000, but if you're unable to even boot, give my Extra archive a try from the other thread and do a full myFix.

Posting a new Extra for the E6520. Changed from the previous pack is an NVS4200M.kext that I created - it's a legacy kext that overrides the appropriate strings in the NVidia kexts in S/L/E, preventing the need to make any edits there whatsoever. Additionally, there is a DeviceMergeNub.kext along with some DSDT changes that enable proper operation of the Atheros AR9280. Previously, I was only able to connect to 802.11b/g networks, and failed to get a DHCP lease on any N network. As it turns out, I was loading a kext with Atheros21 support when I needed Atheros40 support. In addition to proper connectivity, AirDrop is now active and available as well. This was tested and verified working on a fresh 10.8.2 install with no modifications to S/L/E other than the myHack.kext that a myFix will add. TODO: Still using NullCPUPowerManagement, would love to get speedstep/sleep working Still get an AGPM error, need to edit for proper power mgmt Still using VoodooHDA+HDADisabler - need to work on getting the onboard IDT 92HDXX audio working the right way

Up and running now. Still a lot of polishing and tweaking work to go!

I find that VoodooBattery works "sometimes" Occasionally it boots and is just a battery with an X inside, and other times it has a properly working battery meter. Not sure what the rhyme or reason is. Something to try, but rather than using a sleepenabler kext, I'd like to get the actual power management working. Sleep is nice, but speedstep is useful on a more regular basis. EDIT: I've also updated this E6520 ML topic @ https://osxlatitude.com/index.php?/topic/1689-e6520-mountain-lion/

Hi Loralon, Sorry for not updating sooner, but I've gotten things booting properly now. I'm attaching my Extra folder - it's largely based on your work, but I've replaced the PS2Controller/Nub kexts from my working Lion install which seem to work better, a FakeSMC that's been injected with the hardware monitoring additions from multifail, an IO80211Family.kext that includes support for the AR9280 Atheros card, and a VoodooHDA/AppleHDADisabler that will hopefully avoid the dreaded VoodooHDA kernel panics. I've tested, and this works straight out of the box (after being MyFix'd) with no modifications whatsoever to S/L/E That said, it's using NullCPUPowerManagement, which is less than ideal. Would like to work on getting a properly patched AppleIntelCPUPowerManagement in there so that speedstepping works (and maybe even the pipe dream of sleep, someday) Would be cool to have support for audio in the DSDT, too, so we didn't need to rely on VoodooHDA, but probably not a priority. Let me know how this works for you, and hopefully we can use this as a basis for an ongoing, improving EDP for the e6520 w/NVS4200M. Once we get it to a relatively stable state, we can encapsulate most of it into a nice tidy Preboot.dmg, too. Extra-Igashu-E6520-NVS4200M.zip

Hi Loralon, Thanks for the post. I have not yet been able to get ML to boot with your files (even though I understand they're not yet completely done.) I have a fresh install (from myHack) and added your Extra folder (wouldn't boot) and then also added your S/L/E kexts (still wouldn't boot) - there is no Extensions folder inside your Extra (and not sure what the KextStore folder is used for) - can you offer more detailed instructions on exactly what steps you took? Thanks!

Attached is the DSDT I am currently using for Lion 10.7.3 (with working shutdown) - if you can merge whatever it's doing right into yours, that would be awesome. Please also share your DSDT/Extras/modified kexts that you have working in ML if possible. If the modified kexts you have have been patched in S/L/E and the only thing you've modified is Info.plist entries, would be cool to move all that to legacy kexts in E/E for ease of portability - I could help with that, too. DSDT.aml.zip

Hi Loralon, my e6520 does properly shut down and reboot now. The DSDT I am currently using isn't one I patched myself - I had one that I was making patches to here and there, but eventually found one on another forum thread somewhere that enabled proper shutdown and reboot, as well as volume control with the hardware buttons, so I start using that instead. I don't know enough about DSDTs yet to merge these changes back into a proper one for my hardware, but I imagine that must be possible. Did your 4200M patches work under Mountain Lion or just for Lion? I'm hoping that between all of us with this model, we can come up with a good DSDT+Extras to fully support as much as we can.

Negative on that. Seems to be properly injected by Chameleon (the image in the first post is no longer the case; it's recognized as a nVidia Quadro NVS 4200M, with 1024mb of vram, etc, etc - but QE/CI appears to be non-functional. It's super, super choppy to the point of being mostly unusable. I was reading about NVCAP and fired up GPU-Z and then also nvflash, trying to dump the vgabios, but apparently doing so isn't supported on mobile chipsets. (No supported EEPROM error message, bunch of other forum posts I found expressing the same issue.) I also tried messing with AGPM, modifying values in the kext and finally just deleting the kext altogether, but didn't seem to solve the problem either. Running out of ideas!

Since this thread is rapidly spinning off-topic, let me redirect the conversation for E6520 Mountain Lion to https://osxlatitude.com/index.php?/topic/1689-e6520-mountain-lion/ Unless somebody has an idea for how to disable the built-in display (so that the video card can drive two external displays) or take advantage of the secondary Intel GPU, I think this discussion is probably closed. I did finally end up ordering one of these: http://www.monoprice.com/products/product.asp?c_id=101&cp_id=10114&cs_id=1011403&p_id=6038 Along with the latest DisplayLink drivers, this effectively provides an extra display in the display options to be dragged around and set up. It's slow, since the data is all going via USB -- not great for watching video, playing games, etc, at least not at 1920x1200 -- but sufficient for basic desktop computing (having an extra screen with terminal windows, web browsers, or an IDE)

Thanks, Syonagar. I'm not sure why I didn't have GraphicsEnabler=yes - that got the card recognized straight away, but interestingly enough I still experience extreme graphical choppiness in ML 10.8 that I did not see in Lion.

I was having the exact same problem with this Atheros card, and have nailed it down to an issue with 802.11n support. (If you're connecting to your home router, hold Alt and click the wireless icon to see your detailed connection info, almost guaranteed you're connected on an N network.) Change your router's settings to 802.11g only and watch it connect with no problems. Spent a very long time trying to figure out why in some buildings at work I got a connection fine, and in others I was out of luck. It wasn't until I was in a building that had both a G and an N access point equidistant from each other that I realized it, because half the time I was connecting to the G and getting on, and the other half I was connecting to the N and getting the 169.254 autoassigned IP. Now I know the cause, but still working on the solution. I might just buy a different card Too bad OS X won't let you specify a BSSID to connect to!

Wacky. Not sure why the attachment didn't go through the first time, edited post above. Sadly, no gesture support, and TBH I find it weirdly sensitive, so much so that my thumbs are constantly accidentally moving the cursor while I type. But hey, it beats having to carry a mouse around everywhere you go.

bpedman, for your trackpad, you should be using the AppleACPIPS2Nub.kext and ApplePS2Controller.kext. I've attached them in a .zip below. As for your frustrations with keymappings, I strongly recommend installing DoubleCommand (http://doublecommand.sourceforge.net/) KB_Trackpad.zip