infamousgeek2

Correction, io fatal errors are now gone.

Didn't know that was a bad thing, but anyway I am not using Niresh's distro anymore. I am trying to make a working vanilla USB installer with 10.10.2 downloaded from the app store.

Yes. This is what I've been using for kernel arguments in org.chameleon.Boot.plist: -gux_defer_usb2 npci=0x2000 kext-dev-mode=1 dart=0

Yes I booted with -v -f arguments.

Thanks. I am already using the nullcpu kext. I just tried removing the LPC plugin and I got the same result.

Ok NullCPUPowerManagement was not renamed to .bak. But I just realized that I had forgotten to download the 10.10.2 kernel from your guide. So once this corrected, the proper kext updates done, I do not get a KP anymore but here's where it hangs:

As a last resort, to make sure my issue is not related to my Maverick install, today I downloaded the latest OSX from the App Store and tried to follow the guide previously mentioned in hope of creating a brand new vanilla installation of OSX Yosemite on a different partition. The USB Installer won't boot, gets stuck at some Kernel Panic. Are you aware if the bootpacks from your guide are working with OSX 10.10.2 Jake?

I have voodooPS2Controller installed in S/L/E only. That is the only PS2 kext installed at the moment. Heres the kextstat result: 36 3 0xffffff7f80ca5000 0xb000 0xb000 org.rehabman.voodoo.driver.PS2Controller (1.8.9) <10 7 5 4 3 1> 57 0 0xffffff7f80f35000 0x5000 0x5000 org.rehabman.voodoo.driver.PS2Keyboard (1.8.9) <37 36 7 6 5 4 3 1> 58 0 0xffffff7f80f3b000 0xe000 0xe000 org.rehabman.voodoo.driver.PS2Trackpad (1.8.9) <37 36 7 6 5 4 3 1> 59 0 0xffffff7f80bcd000 0x4000 0x4000 org.rehabman.voodoo.driver.PS2Mouse (1.8.9) <37 36 5 4 3> Now, I'm not sure where PS2Keyboard, PS2Trackpad and PS2Mouse are coming from since I do not have those kext installed (I did at the very beginning but I had to remove them cause it was causing the computer to freeze at boot). As for the symptoms, I found this video on Youtube displaying the exact same problem: https://www.youtube.com/watch?v=HQDqzvhVC0E

Now that's the thing, when I go to System Prefences->Trackpad, it says No Trackpad Found. But my trackpad is working (except for the drag and drop).

Jake, you were right once again, thank you! I did follow that step to the T when I first did the upgrade, but in my many attempts to make things work I must have tried an older version of FBCapri. I just reinstalled the one you mentioned and everything booted up perfectly, no more flickering, no more high CPU usage. The only thing remaining is my PS2 mouse and trackpad's button that won't allow any drag n drop. I'm thinking maybe it's another kext conflicting with voodooPS2Controler.kext... I removed ApplePS2Controler.kext, do you think I should put it back?

So I followed your original advice, Jake, and I used the DSDT.aml you mentioned, created both the SSDT.asl and SSDT.dsl using the ssdtPRGen script provided, and removed the GraphicsEnabler=Yes and IntelCapriFB=3 in org.chameleon.boot.plist. I also added this to it: <key>DSDT</key> <string>/Extra/DSDT.aml</string> <key>DropSSDT</key> <string>Yes</string> I booted with -f -v argments and the strangest thing happened, just before making it to the logon page the computer went to sleep on its own (and it now does that everytime I boot). I pressed the power button to wake it and made my way to the desktop. My graphic adapter still shows as it should in About This Mac, but the flickering is a bit worse than before. A new problem arises now, my 4 CPU threads are at 100% in menu meter, and according to Activity Monitor the process responsible would be ReportCrash. One thing that seem to be improved is that the PS2 mouse is responding almost normally now.

Yes I thought about it, but I'm trying to avoid having to reinstall and reconfigure all my apps...

Ok, I manually rebuilt the cache and it still does the same thing. Then I tried with -v argument only and to my surprise it booted fine. Weird, I always thought the -v argument did not have any other effect than displaying textually what was going on...! Now, I may have spoken too fast when I said that I got QE/CE working... What I actually got is a proper display property in About This Mac (Intel HD Graphics 4000 1024MB). I am not convinced that QE/CE is actually working because I still have the logon screen graphic flicker glitches (witch I thought IOGraphicsFamily.kext was going to fix) and those glitches are also apparent in some apps like Google Chrome. I also found out I have another problem to fix with the PS2 driver. I'm using a PS2 mouse and I can't drag anything with it, it's like when I hold the mouse button down it mimics multiple clicks. I have the same problem with the trackpad buttons. If I use a USB mouse, it works ok. I'm currently using VoodooPS2Controller.kext (I had to remove ApplePS2Controller or i would not have either a working mouse or keyboard). Any suggestion on which proper kext to use?

Ok I will try this. Is this the exact same as doing a repair permissions & rebuild cache in Kext Wizard?

Thank you for your quick answers. Yes, same result. Ok, I tried booting with -f -v and to my great surprise QE/CE worked for the first time! The weirdest thing is that I did try booting with those parameters before without success. But I tried so many different configs that I probably forgot to try the -f -v recently... Anyway, after seeing that it worked I tried booting without any parameters and it froze as usual, around 1/3 of the progress bar. Then I tried just with -f, same result. So the only way I can get it to boot with full QE/CE support is with -f -v. Any suggestion to fix this?

Hello everyone. I've been using Mavericks on my E6530 for a while now and recently decided to try upgrading to Yosemite 10.10.1. After many hours of fine tuning I finally managed to have it to fully boot to desktop. The only thing left to fix is HD4000 QE/CE as it currently doesn't work (shows as generic with only 4MB of memory). Getting the HD4000 to work was a pain when I originally installed Mavericks, I just don't remember how exactly I finally got it to work back then. Important facts about my original Maverick installation: - it did not use any DSDT or SSDT files. - It was using Chameleon for a bootloader - In org.chameleon.Boot.plist, I had GraphicsEnabler set to yes and IntelCapriFB set to 3 About my Yosemite upgrade: - I used Niresh's Yosemite distro that was burned to a DVD (USB installer kept giving errors) - I used the Extra folder from bootback found here: https://osxlatitude.com/index.php?/topic/7478-dell-latitude-yosemite-install-guide/ - I also installed the kexts from Extra/Extensions/SLE - I installed the IOGraphicsFamily.kext version suggested in the guide previously mentioned - I had to remove the IOBluetoothFamily.kext as it was making it crash during boot (don't use Bluetooth anyway) - Installed Chameleon-2.3svn-r2437 - I had to remove the GraphicsEnabler and IntelCapriFB mentions from org.chameleon.Boot.plist (hence no more QE/CE) or it would freeze halfway during boot Here is what my org.chameleon.Boot.plist looks like now: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EthernetBuiltIn</key> <string>Yes</string> <key>Graphics Mode</key> <string>1366x768x32</string> <key>Instant Menu</key> <string>Yes</string> <key>Kernel</key> <string>/System/Library/Kernels/kernel</string> <key>Kernel Flags</key> <string>-gux_defer_usb2 npci=0x2000 kext-dev-mode=1 dart=0</string> <key>SMBIOS</key> <string>/Extra/smbios.plist</string> <key>SystemType</key> <string>2</string> <key>UseKernelCache</key> <string>Yes</string> </dict> </plist> Hopefully there is a way to make HD4000 work in Yosemite without the use of DSDT/SSDT since it was the case with Mavericks. Any help at this point would be greatly appreciated. Thanks PS, my E6530 doesn't have the Optimus option