Jump to content

v3ct0r

Members
  • Posts

    383
  • Joined

  • Last visited

  • Days Won

    24

Everything posted by v3ct0r

  1. Quick note: I had to boot with GraphicsEnabler=Yes after a restart; if I didn't, I got a black screen. I will modify my earlier post to reflect this.... Thanks for reminding me :$
  2. Darvinko, you've done it again! IT WORKED! No more screen tear, stuttering, etc.! Attached are the edited kexts as per your request. Also, after the restart, I had to boot with GraphicsEnabler=Yes at boot, otherwise I got a black screen; not sure if it will happen to you since Darvinko didn't mention it, but if it does, you know know how to get past it Edited Nvidia Kexts.zip I'm also very sorry to hear about your mother; my best condolences go out to you...
  3. When booting 'normally' I can get the audio/mic to work using VoodooHDA, but specifically with the version I have posted below, I can get more out of it. I am not sure which version it is (I forgot; I used it in Lion though) but it gives you some level of volume control (the sound completely turns off after about 6 'squares' in the volume control popup to the left of the maximum volume 'square') and a working microphone, whereas the one that came with the ML4300 pack remained at the same volume, whether turned all the way down or up. VoodooHDA.kext.zip Place in System/Library/Extensions (Note: you may have to replace the one currently there if you used Darvinko's install method) and repair permissions using anything you'd like (Disk Utility, MyHack, etc.)
  4. I can confirm that the NVDAResman.kext is the culprit of us having to use the -x boot flag and the [iOBluetoothHCIController][start] -- completed error.
  5. Will do; I am not with my laptop right now but I will try this as soon as I am.
  6. Hello again! I come bringing good news! I managed to boot WITHOUT SAFE MODE and fix the [iOBluetoothHCIController][start] -- completed error! All I did was delete the NVD*.kexts/move them to a different location (ex. the desktop in a folder called NVDIA Kexts Backup, etc.). Then I rebooted in verbose mode to see what (if any) errors showed up and it took me to the login screen and I was able to login! Now that those kexts are gone, however, there are sure to be new problems, one of which I found where if you don't touch the computer for a few minutes, and it goes/tries to go to the screensaver, the entire screen goes white and there is a grey rectangle where your cursor should be. One step down a few to go (I hope)!
  7. I have tried booting up with the wireless switch off and it has no effect on where the boot hangs... @tengokuu I can confirm that the voodoobattery.kext in extra\extensions and repairing disk permissions works. Also, to repair permissions, install other kexts, etc., multifail from tonycrapx86 makes things a lot easier
  8. Hey guys, First I'd like to give Darvinko a huge thank you; I've been trying to get ML to work since DP3 and couldn't. His method worked the first try! Now, getting the rest of the system to work: I have installed multifail 4.6.1 from tonycrapx86.com/downloads (have to register) I replaced the AppleACPIPlatform.kext from 10.6.7 and Netkas's IOPCIFamily.kext (basically the same ones Darvinko was talking about) I cleaned up the org.chameleon.boot.plist by removing everything except EthernetBuiltIn=yes, Kernel=mach_kernel, and (for my convenience) Timeout=n After all that, I rebooted, but this time normally, in verbose mode (-v only; no -x) It hangs at the following: [iOBluetoothHCIController][start] -- completed The line right before the one above is: DSMOS has arrived Once again, thank you Darvinko and everyone else who is involved in getting ML on the E6XXX P.S. I have an E6400 with a Core 2 Duo (2.8 GHz) and NVIDIA Quadro NVS 160M Graphics. I also have a 30GB SSD and 4GB of ram, if it helps. Previously, this machine ran Snow Leopard and Lion.
×
×
  • Create New...