No problem, by the way "normal" dsdt does no longer "exist" i changed the DSDTs to be universal across screens and made the boot.plist screen specific. AppleHDA and some other fixes are also DSDT dependent. Also i forgot to mention this, i included a USB3 DSDT fix in the L502x dsdt, this gives us native USB3 support but it's painfully slow.
I still need some volunteers to test a boot cd/stick...
I'll help out with testing the boot cd/stick if your still looking for people.
Huh i dont see how a caddy could affect the speed? Think i will go with that one.
Is connecting it to the XPS hard?
Thanks for your help!
I don't know if it can or not, essentially I guess it's just a data cable,so it shouldn't make a difference. I just remember looking at caddys and getting paranoid about data transfer speeds, they all claim something different.
But to answer your question, it is very simple to replace the DVD drive with the caddy, pretty much just a couple screws, pop out the DVD drive, swap the cover, and pop in the caddy. Piece of cake.
Now swapping the internal is a different story, it's fairly straight forward, there are several videos out there, just go slow and take your time.
I followed Pcwiz13's install for ML and got the "Still waiting for root device" message. What have I done wrong?
I dont have this problem with my install but apparently it is fairly common. Try booting with UseKernalCache=No if that solves the problem check out this link DoiX posted a couple pages back:http://www.insanelym...dpost&p=1834431
I got the "official" release of ML up and running yesterday and thought I would share my experience/technique for doing so. I'm not promising this will work for anyone else, its just how I went about getting it running.
My setup: I have 2 hard drives in my L502x a SSD that currently is my stable working Lion install, and the original hard drive in a caddy replacing the CD drive with 2 partitions on it, one windows, and one a "test" partition for osx.
I installed ML on the "test" partition of my second hard drive.
This is the procedure i used to get it up and running. Once I get it 100% I will copy it over to my SSD to become my primary OS.
I followed these instructions for downloading/creating a bootable install USB for Mountain Lion:
Creating USB Installer A. Preparing the USB 1. In your working OS X install open Disk Utility 2. Click on your USB drive in the left sidebar 3. Click the “Partition” tab 4. Under “Partition Layout” click “1 Partition” 5. Click Options -> select “Master Boot Record”; check the format is set to “Mac OS X Extended (Journeled)”; name it “USB” 6. Click Apply
B. Creating the OS X installer on the USB drive 1. Show hidden files in finder by opening Terminal (in utilities) and typing (copy / pasting) the following: defaults write com.apple.finder AppleShowAllFiles YES then killall Finder 2. Mount your Mountain Lion DMG. If using a copy downloaded from the app store: Navigate to Applications (which is where it will save your downloaded copy of ML by default) -> right click "Install OS X Mountain Lion" and click "Show Package Contents" -> Contents -> SharedSupport -> Double click "InstallESD.dmg" 3. Mount BaseSystem.dmg by typing the following in terminal: open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg 4. Go back to disk utility and click on “Mac OS X Base System”, click the “Restore” tab then drag and drop your USB to “destination” and click restore then erase. This will take a while. 5. You’ll now have 2 “Mac OS X Base System”s present in Finder, right click them and “get info” to determine which is your USB drive (hint: look at the size). 6. Navigate to the one which is your USB drive, open it and go to /System/Installation. Delete the “Packages” link then create a folder called “Packages”. 7. Open a new Finder window and navigate to “Mac OS X Install ESD”. Copy everything inside the packages folder to the packages folder you have just created. This will take a while. 8. Copy mach_kernel from “Mac OS X Install ESD” to the root of your USB drive.
C. Patching the installer for a PC 1. Remember the two kexts we downloaded above? Copy "FakeSMC" and "NullCPUPowerManagment" to /System/Library/Extensions on your USB stick. 1.A. Install MBR Patch- Copy "OSInstall.mpkg" to /System/Installation/Package/OSInstall.mpkg 1.A. Install MBR Patch- Copy "OSInstall" to /System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/OSInstall 2. Run the chameleon installation package and ensure to choose your USB drive as the destination. 3. Run Doix's Installer and ONLY install the keyboard trackpad kext's to the USB drive.
Installing OS This is where I just ran with it and it worked out.
1.Booted to USB drive, installed Mountain Lion to the partition I wanted. 2.Booted back into my working Lion install. 2A. Used KextWizard to install the "FakeSMC" and "NullCpuPowerManagement" kexts onto the mountain lion once again. 2B. Ran the chameleon installer on the mountain lion install. 3. Reboot onto the Mountain Install using -v (for some reason I have to use -v to boot, I understand this basically just makes it show the command lines, but for some reason it works, I saw the work around for this posted by DoiX earlier, I have yet to try it.) 4. Everything worked fine except sound, battery indicator, and speed stepping. I used the battery and audio kext from DoiX and everything works great.
Next to get sleep/speedstep enabled (I asssume its the same process as it was in Lion, I just have yet to mess with it for fear of crashing my new working install.)
So have I missed anything? On another note, I have ZERO artifacts/freezes in my video anymore, that alone makes ML worth the upgrade to me.
**UPDATE 1: after a short while my graphics artifacts began to come back exactly like they did in 10.7.4, The last kext i had installed was the battery kext. Once i removed it, the graphics problems have gone away. I don't see how there is any connection between the two, but for reason thats whats happening. I was using a kext in a package called "battery fix - Lion". I'll look into the issue later.
has anyone heard of a connection between battery kext and graphics issues?