huskerphile

How about a more specific question. Since Clover allows you to inject kexts at startup, if I set clover to inject those kext files, would that work? Or would I need to delete certain OEM kext files from S/L/E to avoid conflicts? Also, has the DSDT file in the guide been modified?

Have you ever tried to use the Clover bootloader on the E6410? I used your myHack guide to get Mavericks up and running, but I switched over to Clover for a new desktop and would like to try and keep consistent.

So I just updated to 10.9.2 via the app store. System was working fine before the update. It boots normally through the gray apple splash screen, then the system hangs with a blank screen when the OS should come up. With -v, the system still hangs with a blank black screen. Anyone know a fix?

I'm not sure if this represents progress on the sleep issue, but it's a new avenue for investigation. I noticed today that if you press Fn+F1 that the system will go to sleep like it should (unlike trying to select "sleep" from within OS X, which only darkens the display but everything keeps running). Unfortunately, pressing the power key to re-awaken the system must cause a kernel panic because the system won't come back to life and requires a hard restart.

Here is a download link for the kext that worked for me: https://www.dropbox.com/s/9dmndlcy5swch2x/IntelE1000e.kext Just copy to E/E and run myFix on your OS X drive.

I just got the Edimax EW-7811Un card that was mentioned in the ML thread. I just got it installed and it's working great.

In order to get Ethernet working, I had to download an updated 64-bit IntelE100 kext, copy it to E/E and then run myFix. In order to log in to the App Store, I had to download Chameleon Wizard and use the smbios editor to generate a serial number for my machine and then reboot. I am still working on the iMessage fix listed above.

I applied the same fix and got further into the boot process without KP. Instead, my boot hangs at the following point: 10/28/13 9:56:56.000 PM kernel[0]: NTFS volume name Windows, version 3.1. 10/28/13 9:56:56.603 PM mds[59]: (Warning) Volume: vsd:0x7fea73814000 Open failed. failureCount:0 (null) I have a feeling this is due to the non-standard setup I'm using (OS X installed on a partition of an existing Win 7 drive). The system still boots find with -f. Since I'm dual booting anyways, entering -f at startup to start the Mac OS isn't really a big deal, but I wonder what that means for future functionality issues.

So here's my question...It looks like everything except iMessage & SD reader is working with the "-f" bootflag. Battery monitor, scrolling trackpad, sleep, Ethernet and keyboard. Other than annoyance, what's the downside of always booting with the "-f" bootflag? EDIT--turns out sleep isn't working (surprise, surprise...) The computer monitor darkens, and awakens to a prompt for my password, but no actual sleep happens...the battery drains, the LCD stays on, etc.

I already tried that and it didn't work.

OK. I looked through my console and I'm pasting concerning looking entries below: 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AppleHDAController - library kext com.apple.iokit.IOGraphicsFamily not found. 10/28/13 2:40:05.000 PM kernel[0]: Can't load kext com.apple.driver.AppleHDAController - failed to resolve library dependencies. 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AppleHDAController failed to load (0xdc00800e). 10/28/13 2:40:05.000 PM kernel[0]: Failed to load kext com.apple.driver.AppleHDAController (error 0xdc00800e). 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AppleSMCPDRC - library kext com.apple.driver.IOPlatformPluginFamily not found. 10/28/13 2:40:05.000 PM kernel[0]: Can't load kext com.apple.driver.AppleSMCPDRC - failed to resolve library dependencies. 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AppleSMCPDRC failed to load (0xdc00800e). 10/28/13 2:40:05.000 PM kernel[0]: Failed to load kext com.apple.driver.AppleSMCPDRC (error 0xdc00800e). 10/28/13 2:40:05.000 PM kernel[0]: Couldn't alloc class "AppleSMCPDRC" 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller::start entered... 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller: initial commandByte = 45 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller: new commandByte = 44 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller::start leaving. 10/28/13 2:40:05.000 PM kernel[0]: Couldn't alloc class "AppleHDAController" 10/28/13 2:40:05.000 PM kernel[0]: Controller: Intel PCH (vendor ID: 8086, device ID: 3b56) 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC - library kext com.apple.iokit.IOGraphicsFamily not found. 10/28/13 2:40:05.000 PM kernel[0]: Can't load kext com.apple.driver.AudioAUUC - failed to resolve library dependencies. 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC failed to load (0xdc00800e). 10/28/13 2:40:05.000 PM kernel[0]: Failed to load kext com.apple.driver.AudioAUUC (error 0xdc00800e). 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC might not load - kextd is currently unavailable. 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC might not load - kextd is currently unavailable. 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC might not load - kextd is currently unavailable. 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC might not load - kextd is currently unavailable. 10/28/13 2:40:05.000 PM kernel[0]: Couldn't alloc class "AudioAUUCDriver" 10/28/13 2:40:05.000 PM kernel[0]: FireWire runtime power conservation disabled. (3) 10/28/13 2:40:05.000 PM kernel[0]: OSMetaClass: Kext org.voodoo.driver.PS2Keyboard class ApplePS2Keyboard is a duplicate;kext org.rehabman.voodoo.driver.PS2Keyboard already has a class by that name. 10/28/13 2:40:05.000 PM kernel[0]: Kext org.voodoo.driver.PS2Keyboard start failed (result 0xdc00400a). 10/28/13 2:40:05.000 PM kernel[0]: Kext org.voodoo.driver.PS2Keyboard failed to load (0xdc008017). 10/28/13 2:40:05.000 PM kernel[0]: Failed to load kext org.voodoo.driver.PS2Keyboard (error 0xdc008017). 10/28/13 2:40:05.000 PM kernel[0]: Kext com.apple.driver.AudioAUUC might not load - kextd is currently unavailable. 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Up: { 003b, 0037, 007e, 107e, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Down: { 003b, 0037, 007d, 107d, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Left: { 003b, 0037, 007b, 107b, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Right: { 003b, 0037, 007c, 107c, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard::probe entered... 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard::probe leaving. 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Up: { 003b, 0037, 007e, 107e, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Down: { 003b, 0037, 007d, 107d, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Left: { 003b, 0037, 007b, 107b, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard: Swipe Right: { 003b, 0037, 007c, 107c, 1037, 103b, } 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard::probe entered... 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard::probe leaving. 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard::start entered... 10/28/13 2:40:05.000 PM kernel[0]: ps2bl: KKCL, KKCM, KKQC methods not found in DSDT 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller: oldCommandByte = 44 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller: setCommandByte for keyboard interrupt install 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller: oldCommandByte = 44 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Controller: newCommandByte = 45 10/28/13 2:40:05.000 PM kernel[0]: ApplePS2Keyboard::start leaving. 10/28/13 2:40:05.000 PM kernel[0]: OSMetaClass: Kext org.voodoo.driver.PS2Mouse class ApplePS2Mouse is a duplicate;kext org.rehabman.voodoo.driver.PS2Mouse already has a class by that name. 10/28/13 2:40:05.000 PM kernel[0]: Kext org.voodoo.driver.PS2Mouse start failed (result 0xdc00400a). 10/28/13 2:40:05.000 PM kernel[0]: Kext org.voodoo.driver.PS2Mouse failed to load (0xdc008017). 10/28/13 2:40:05.000 PM kernel[0]: Failed to load kext org.voodoo.driver.PS2Mouse (error 0xdc008017).

I'm a total noob at this. I can navigate to the console app, but I'm not sure what I'm looking for.

After another hour or so of futzing, I was able to get the AppStore, FaceTime, iMessage and iCloud working by downloading Chameleon Wizard and editing SMbios.plist to generate a real serial number for my system. My only remaining issue is the need to boot with the "-f" bootflag, and I'm not sure how to get that resolved. I also edited the org.chameleon.boot using Chameleon Wizard and unchecked the "graphics enabler" and set the resolution to 1440x900x32. That made an huge difference in the graphics performance.

Re: built-in Ethernet, I was able to find the 64-bit version IntelE1000e.kext through Google, I copied it to E/E and ran myFix and now Ethernet is working fine.

I looked through the E/E folder as well as S/L/E and didn't see any conflicts. Here's a screen grab of my KP:

I get the same exact KP if I boot without the "-f" flag.

Thanks for the assistance, this guide is amazing. I was able to finally make a working Flash drive with my wife's MacBook Pro and the install went like a dream. I was able to successfully install 10.9 on a blank MBR partition on my E6410. My end goal is to dual-boot OS X and Win 7 from different partitions of my SSD and use a shared exFAT32 partition for most of my storage. My question now is how to set up the bootloader. After the OS X install & post-install, I shut down the computer and removed the USB stick and immediately got a boot 0 error. I was able to succesfully boot again into OS X with the USB stick inserted and the "-f" bootflag. I tried using myHack to Install Chameleon to my partition and that still gave the boot 0 error. So I used a Windows recovery disk and then startup repair to re-write the Windows 7 bootloader and the system now defaults into Win 7 without any problem. I can also boot into OS X using the USB Stick and the "-f" bootflag (the system KPs if the -f flag is absent). I'd love to be able to have a simple bootloader where I can choose my Windows 7 partition or my OS X parition, but I'm not sure how to get there.

I'm currently running myHack on my flash drive. After deleting the kext files, I assume I would run myFix (and not use Kext Wizard from the Mountain Lion zip file to fix the permissions)...

After multiple attempts to reformat, clean, and reparition the USB drives in Disk Utility (with multiple Kernel Panics), I think it has something to do with how myHack write protects the USB drive. I remember getting a warning that I needed to "Authenticate" when copying the OSInstall files to the Flash drive at that step. My best guess now is that when myHack failed, the write protection got buggered. I tried to reformat the drive in Windows using diskpart and get an error message when I "clean" the drive, but it then succeeds. However, when I try to view files on the drive I get a permissions error.

Unfortunately, my wife's MacBook Pro is at work, so I'm trying to do this through virtualbox on my 6410.

myHack KPs when it gets to the last merging step of the "Install Extra" program. Also KPs immediately when I try and run myFix or Install Chameleon.

I went back into myHack and tried to install the extras and I got a KP when it was writing to the USB stick.

I think I fried another Flash drive, because I got another new one and ran myHack (without adding any extras or MBR patching) and it booted to the gray splash screen. Predictably, it froze with the "spinning wheel". Now I will add the Extras to the Flash drive and see how far I get. If that works, I will do the MBR patch. Do I need to run myFix after I overwrite the files from the MBR folder?

I tried this with my new Flash drive (and the myHack process works flawlessly now.) Unfortunately, I get the same boot error as suarte (same exact output). That was using the provided Extras and the MBR patch. I re-made the drive with myHack and stopped prior to adding the Extras and didn't apply the patched MBR files and I'm still unable to get into the bootloader, although the text is "unable to boot from USB device" or something similar. I'm going to try making a new USB stick with unifail just to see if its part of the myHack process that my computer doesn't like.

OK. I've got a new Flash drive and that appears much more stable. Has anyone tried to apply the workaround for the integrated Intel graphics card that worked in ML? I will try when I get to that stage but I wonder if it will require more fixing.