ktbos

Realz and Jake, when I first switched over to using hibernatemode=3, I also cleared out any sleepimage file that might have been there. For a computer that had never slept to disk before, it shouldn't have mattered. And for a computer that does sleep to disk, it should clear it out every time it creates new image. But on the off chance that there's something wrong and you do have an existing sleepimage that cannot be correctly overwritten, it's worth trying this: sudo rm -f /private/var/vm/sleepimage

Realz, try this boot.plist instead of the generated one you are using: boot.plist.zip It shouldn't be much different, but that's an easy thing to check. You may need to make some changes if the referenced files don't match.

The big difference between our two files is how many sections of log file there is and how long each section is. I have 6 sections and you have 32. Wow. How many disks do you have mounted on your system? And how many different USB drives have you inserted into the computer at one time? Not sure if that is related to the number of sections, but just in case. And have you logged in to Apple through iTunes or through Mail or anything? I'm wondering why you get so many more of those preventing sleep from address book than I do. I have 186 and you have 5170. Again, I'm not sure if your log is just being more chatty than mine and they are all equally unimportant, but the quantity difference is significant. I haven't yet connected my test install to anything accounts. (Actually, I think I used the AppStore.) But what I was looking to see was information about battery status and the rest of the info about the settings for sleep and yours matches mine for the things I was looking for. (One other difference is that you have 4 entries in your powerstate section whereas my file has only 1. At the time I ran my pmset, I had one display connected so I connected a second display and I ended up with 4 entries like you. Not sure why 1 display has 1 AppleDisplay and 2 displays have 4 AppleDisplays, but at least it is consistent between our computers. Perhaps related to extra Display software required to drive more than one display.) I also noticed something in your file named "jp_co_roland_RDUSB012ADe". And while that might not be a problem it makes me think that you have really moved into the computer already. And frankly that makes it tough to figure out whether it might be something you added or installed that is causing trouble or if it is the core install that is at fault. If you have another disk you could use to do a new install (any old thing lying around that can be connected temporarily or even a USB drive, perhaps), that would be the best way to debug. And even if a clean install didn't work, at least we'd know it was an OS/install issue.

realz and Jake, here is the output from my pmset -g everything. pmset-everything-ktbos.txt If you could post yours, we can compare to hopefully figure out this hibernate thing once and for all.

Realz and Jake Lo, here is my Extensions directory along with my smbios.plist and my DSDT.aml. Give it a try and let me know if it is better for you than what you have. Extra-9020-ktbos.zip Realz, I've been working on the audio issue with Jake and it appears he figured out how to get VoodooHDA working well now. The VoodooHDA included here is one I compiled with his suggestion. (Also, since the HDEF section of the DSDT doesn't need to be the same for VoodooHDA to work, the included DSDT has that removed so you can try the one in the attachment. However, my DSDT also has additional content for an additional SATA card I've added so it's possible that will cause new problems for you - hopefully, that will just be ignored.) For hibernate, I wonder if part of the problem comes from the smbios setting of the computer you have. I've included my smbios so you can give that a try and see if it impacts your hibernate situation.

Realz, do you have sound and hibernate working? And if so, did you need to do anything more than what is described in this thread to get them working? Any kexts different on yours than in the guide, for example?

I've been at this for a few days and no luck yet. My patched AppleHDA loads (kextstat shows it) but the control panel shows no output (or input) devices are found. I've tried a number of different combinations of things but I think the crux of the problem is that when I look at /proc/asound/card0/codec#0, I see only HDMI digital output. When I look at /proc/asound/card1/codec#0, I see ALC280. I followed the guide info here for the dump from the ALC280 but when I boot the computer, lspci shows me that it has two cards, neither of which is an ALC280: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio Controller [8086:0c0c] (rev 06) 00:1b.0 Audio device [0403]: Intel Corporation Lynx Point HD Audio Controller [8086:8c20] (rev 04) From what I've been able to find, the second one is the ALC280 compatible device. And that is the one that shows up at 1B, which does match what is in the HDEF section of the DSDT. I've tried using both the 10EC0280 device and the 80868C20 device in the places where devices is asked for in this guide (decimal equivalents, of course) - in the layout28 file, the Info.plist of AppleHDAHardwareConfigDriver, and in the binary changes made with HexFiend to AppleHDA. But I don't seem to get any audio device recognized using either device. Also, I've removed the AppleHDADisabler.kext, the AppleKextExcludeList, and the VoodooHDA.kext from my Extra/Extensions directory before re-running myHack. So in the Extra/Extensions directory, the only kext I have related to audio now is the AppleHDA.kext I've created. In my console log, I see a bunch of these. After the last, AppleHDAHardwareConfigDriver appears to give up and it goes away from the kextstat list. 8/2/14 9:06:52.685 AM mds[64]: (Warning) Volume: vsd:0x7fbacc82c600 Open failed. failureCount:5 { DisabledRecycleCount = 5; } So I'm wondering whether the this guide is applicable for what I'm trying to do. And if so, what steps should I do differently based on the card0 vs. card1 and multiple audio device issue?

Realz, I had no problem with the bootpack from the Guide. Chameleon worked fine and booted fine for me. Now, granted, our systems are not the same because of the difference in the processor, but that shouldn't impact the ability to boot with Chameleon. Some suggestions off the top of my head: Make sure when you create the USB installer, you start with a USB drive that you completely wipe and repartition first. Just to make sure there is no MBR stuff hanging around. (Confirm in Disk Utility that it says GPT and not MBR at the bottom.) Download the Extra directory from the Guide. Substitute your SSDT, however, in the Extra folder after you download it. Follow the instructions in the guide for creating the installer. When you get to where it asks you to choose an Extra directory for the installer, you will choose the one you downloaded (as the guide tells you to) and since you've already put the new SSDT in there, it will go along for the ride. For your 9020, going into BIOS setup and Reload Defaults, then switch SATA from RAID to AHCI. Continue the install as described in the guide. Then when you get to the point where you are completing the installation and it asks you for your Extra directory, again, you point to the one on the installer so your new SSDT goes along for the ride there too. That should get you successfully booting up. If not, then there's apparently more different between your setup and mine than just the i5 vs. i7. Hope you get it working!

Does the 10.9.0 image work for you? Before the update? If so, very interesting that an update breaks it. And also worth keeping in mind that a new install of 10.9.4 might break it similarly. In other words, whatever might have changed from 10.9.0 to 10.9.2 probably didn't revert when going to 10.9.4 Apple doesn't undo stuff very often that I'm aware. I think the bigger deal is the i5. Yes, I think that probably is the issue. If you can boot windows or linux on your computer, you could run the DSDT editor and extract from there. Then you could do the patching. The patching isn't too bad. Perhaps someone else could suggest whether the SSDT would need to be changed too for a processor change?

Realz, I'm looking forward to results too! It'll be a few days. In the meantime, no, I didn't have any issues with DSMOS. My best suggestion is to start over and follow the guide exactly. So far, I've tested A04 and A07 BIOS versions and both worked the same for me. Be sure to do the Load Defaults button in the BIOS and then the only change is to make SATA AHCI instead of RAID. When creating the installer with myHack, use a 10.9.4 InstallESD image so you can skip over any updates. Use the Extra from the guide to create the installer and use that during post install for the Extra for your new install. Remove any add-on cards you may have installed and any USB devices you have plugged in that might make your computer different from Jake's or mine. The only change from the guide I can recommend so far is to do sudo pmset -a hibernatemode 3 after you complete the installation. Of course, if your computer is not exactly an Optiplex 9020 with an i7 4770, then the DSDT might not be working for you and you'd need to make your own. And if you can't reinstall because you would lose stuff, your best bet is to search this site or others for other people with similar DSMOS errors. (Though you could try restoring to a backup prior to the 10.9.2 update and then regain access to whatever you need and back that up externally so that you could then do a new install.)

Bronxteck, funny timing. A few hours before your post, I had found that hibernatemode fixes the wake problem. I had to get to work so I couldn't post when I figured it out and I wanted to test a long sleep cycle. It works! But actually, it was set to 0 and I needed to change to 3 to get it to work. It seems that Apple sets hibernate mode to zero by default on desktops and since the smbios in the guide's bootpack has it emulating an iMac, that does make sense. Hibernate mode is set to 3 by default on a laptop. Hibernatemode of 3 includes a system image stored to disk that it will supposedly use in case of a power loss to the memory - which theoretically doesn't happen on a desktop under normal circumstances. But apparently, the memory storage of the image is somehow incomplete on the 9020 (or at least on mine) and the disk image supplies what is missing. It's worth pointing out that I had disabled the wake-on-lan in the BIOS and also the wake on USB too. But at least one time while the setting was supposedly off, a keyboard bump started a wake so I'm not sure that those settings were ever really disabled. Also, it's worth noting that I'm unlikely to use sleep with any regularity. But having a menu pick that would put the computer in a state that it could never recover from was too dangerous. (Perhaps if I could have removed Sleep from the menu, that would have resolved the issue a different way - but this is better!) Realz, I have seen similar excessive green-ness in my recent testing with two monitors. (Since my last post above, I discovered that having two monitors connected at the time of sleep actually allowed the wake to get further with green strips on one display while the other one remained black. But the mouse and keyboard never became active so it never successfully woke - just as before with one monitor remaining black or blinking.) I wonder if the difference in success with waking from sleep has to do with the kind of memory installed and whether the memory has enough power during sleep to properly maintain the image. Next up is audio. I want to see if I can resolve the squeal Jake mentioned and that I have. And then put it all together with the 10.9.4 image and my new DSDT and smbios and see if I can get something that is relatively complete. I'll post back with results (hopefully successful). My current goal is to get 10.9.4 working well so that I can be ready for 10.10 - the ultimate goal is a fully functional Yosemite system. Better than an iMac because I can use my own displays and add cards and drives as needed but not the crazy overkill that a Mac Pro would be.

I created my own DSDT today from an extraction within Windows. I didn't add in any of the usual changes and comparing to the one from the guide, it was mostly similar, but still had some significant differences. The result: exactly the same failure to wake as with the DSDT from the guide. My thinking is that if the DSDT had any impact on the sleep/wake issue, I would have seen at least something different. The only thing that has provided any change at all is changing the monitor resolution and the only change that provides is a different kind of black screen failure. It is either all black with occasional white flashes (1920x1200), black with blinking grey on the top 20% (1600x1200), or black with most of the screen blinking grey (when I dragged the resolution scrollbar all the way down for some arbitrary but low resolution). They all seem like variations on a theme: something like the GPU info didn't seem to survive the sleep/wake cycle. The only differences between Jake's and my 9020 at this point are different brand of SSD, monitor, and memory modules, etc.. My setup should be the same, including BIOS version and settings. My latest install uses Mavericks 10.9.0 which I think it what Jake used. And I followed the instructions and used the Extra directory provided. I used myHack version 3.3.1. Assuming I've got the same versions of everything, then there should be nothing materially different between my 9020 and the 9020 that Jake used for the guide. And yet I'm still having problems with sleep/wake. So, Jake, any insight on what might be different? Can you double-check your 9020 to see if it does sleep/wake correctly and if so what versions of myHack, MacOS, etc., you used to build it? Maybe something is different? And at the same time, does anyone have any suggestions on what to check/change when it seems like the GPU is causing a sleep/wake failure? Sleep/Wake fixes are everywhere for all kinds of different issues, but I didn't see any that seem to be related to the HD4600 so if anyone has suggestions, I'd love to hear them. Or maybe the black screen doesn't actually indicate a GPU problem and I should look elsewhere?

jmvbmw, it could be an issue with partition of your installer. I have found that a USB stick that had originally been formatted as MBR needs to be wiped clean before doing the myHack. In Disk Utility, delete the partition and when it asks what format for the new partition, use MacOS Journaled. Don't bother setting up the installer until you see Disk Utility report GPT for your USB stick.

I did another install. This time with 10.9 (instead of 10.9.4). Same result! I used all of the files from the 9020 guide to build the installer USB drive and I finally found a reputable 10.9 InstallESD image to use. I shrunk the existing 10.9.4 volume on my SSD to make room for a second partition to install to. I did the install of 10.9 there and tested and got the same black screen on waking from sleep. I tried adding in the kernel flag you suggest in the guide and found no difference. The following is what my addition to the Boot.plist looks like: <key>Kernel Flags</key> <string>-gux_defer_usb2</string> Let me know if I am not adding that flag correctly. In desperation to figure out what might be different, I decided to try downgrading from my BIOS version of A07 to A04 that you had. Again, same result with waking from sleep: black screen. For BIOS settings, I do a factory default load and then switch SATA from RAID to AHCI. That's the only change from factory default. Let me know if you have anything different. (And of course, I could send details about any BIOS setting that you might be interested in.) That's what I had done with A07 and that's what I did with A04. Just for kicks, I tested sleep in Windows 8 - works fine. (Just to test if my system had faulty hardware or something!) My displayport monitor is 1920x1200. In case there's something different about waking a higher res monitor, I hooked up a passive displayport to DVI adapter to a 1600x1200 monitor. Waking was a little different. I got a mostly black screen but the top 20% had blinking grey. I don't think that's either better or worse - presumably just a different manifestation of the same problem. I don't have access to any other monitors of lower resolutions. Jake, what resolution monitor did you test your sleep/wake on? What else should I look at? And Jake, can you confirm that you do have sleep/wake working on your 9020 even as it stands now with MacOS 10.9.0 on it? (Before trying any upgrade?)

Just to confirm I have the best "Azul", I went through the other 14 possible numbers and all failed. The only one that works is the one I started with, number 10, which matches Jake's. So I'm pretty confident I've got the graphics working correctly and I assume QE/CI is okay because of the translucent menubar and working genie animation. I've been battling the Sleep/Wake issue and haven't gotten anywhere. The computer still sleeps just fine (it seems) and it still wakes to a black screen. I did some log checking and here is a block that shows prior to sleep through eventual hard reboot. The marker is just prior to selecting sleep on the Apple menu. 8:57:14 starts the sleep process. The sleep process ends at 8:57:20. I push the power button to start the Wake at 8:59:36. (The line with the stamp of 8:57:31 is, I assume, because the clock hadn't yet updated when it writes that entry to the log - not because it is being psychic about how the computer will be woken!) I let the wake try to work with a black screen, periodically flashing, until time stamp 9:02:16 when I gave up and held the power button down to do a hard reboot. Is there anything in this log that shows where something might be going wrong? 7/18/14 8:57:08.664 PM Console[155]: Marker - Jul 18, 2014, 8:57:08 PM 7/18/14 8:57:14.414 PM WindowServer[105]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fcd7a65a260(2001) 7/18/14 8:57:14.447 PM WindowServer[105]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7fcd7a65a260(2001) 7/18/14 8:57:15.148 PM WindowServer[105]: _CGXHWCaptureWindowList: No capable active display found. 7/18/14 8:57:17.000 PM kernel[0]: **** [IOBluetoothHCIController][SearchForTransportEventTimeOutHandler] -- Missing Bluetooth Controller Transport! 7/18/14 8:57:20.717 PM WindowServer[105]: _CGXHWCaptureWindowList: No capable active display found. 7/18/14 8:57:31.000 PM kernel[0]: Wake reason = PWRB 7/18/14 8:59:36.000 PM kernel[0]: Previous Sleep Cause: 5 7/18/14 8:59:36.149 PM configd[18]: setting hostname to "******.local" 7/18/14 8:59:36.151 PM configd[18]: network changed: v4(en0-:192.168.2.102) DNS- Proxy- 7/18/14 8:59:36.153 PM netbiosd[108]: network_reachability_changed : network is not reachable, netbiosd is shutting down 7/18/14 8:59:36.360 PM WindowServer[105]: CGXDisplayDidWakeNotification [53746685542]: posting kCGSDisplayDidWake 7/18/14 8:59:37.561 PM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: NULL shield_window (lock state: 1) 7/18/14 8:59:40.000 PM kernel[0]: AppleIntelE1000e(Info): e1000e NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx 7/18/14 8:59:40.446 PM configd[18]: network changed: v4(en0+:192.168.2.102) DNS+ Proxy+ SMB 7/18/14 8:59:40.454 PM configd[18]: setting hostname to "*****.*****.**.*****.****" 7/18/14 8:59:50.446 PM AirPlayUIAgent[265]: 2014-07-18 08:59:50.445920 PM [AirPlayUIAgent] Changed PIN pairing: no 7/18/14 8:59:50.447 PM AirPlayUIAgent[265]: 2014-07-18 08:59:50.446728 PM [AirPlayUIAgent] Changed PIN pairing: no 7/18/14 9:02:16.000 PM bootlog[0]: BOOT_TIME 1405731736 0 Other than the Mac OS version, my set up should be functionally identical to Jake's. So is 10.9.4 causing the problem? And if so, what should I do about it? If not, any suggestions on where to look? Jake, have you tried updating your setup to 10.9.4? If not, when you do a wake from sleep, what does your log look like - anything similar to mine?

Bronxteck, after doing the install, I switched back to the IntelAzulFB=10 and it works fine now. I haven't bothered checking other Azul numbers to see if any work the same, but as far as graphics go, it appears to be working about as well as it can. Jake, the install was a success. Thanks so much for that pointer to the new version of the mach_kernel. That was definitely the main issue I was having. I also have the audio problem you reported in your guide, Jake. I'm going to see if I can improve the situation and I'll report back if I succeed. But my main problem now is sleep is not working. The same as described in the guide where it comes back to a black screen. Interestingly, if you give it enough time, the video flashes once in a while. I did try adding "-gux_defer_usb2" as you recommend but that didn't have any effect. I'm wondering if there could be an issue with the new kernel or 10.9.4 with the USB kext? Or if something else with 10.9.4 is impacting the way the computer sleeps? I've checked my BIOS and I can choose which sleep states to enable - I have S4 and S5 both on.

Jake, yes, I confirmed it is 10.9.4 Thanks for the pointer to that post. I rebuilt the USB installer and substituted that kernel for the one that was in this guide's Extra download. (Everything else about the new USB installer is per the guide - it does not include the changes I discussed with Hervé above.) This time I did get further - one line further, to be exact. Now, shortly after the BootCacheControl line, I see the following, and no I am not making any of it up: panic(cpu 0 caller 0xffffff80002526cf): "a freed zone element has been modified: expected 0xdeadbeefdeadbeef but found 0xdeadbeef88098809, bits changed 0x56a436e6, at offset 48 of 64 in zone: malloc.64"@/SourceCache/xnu/xnu-2422.110 Debugger called: <panic> I'll keep poking at it, but if you have any suggestions, fire away! Thanks!! I booted again and this time used -f and it went right through to the graphical part of the installer. Major progress. Unfortunately the graphics are were completely messed up and I couldn't even tell the installer window was there until "to use English press the return key" came out of the speaker and I jumped out of my chair. I removed IntelAzulFB=10 from the boot plist and tried again. I'm looking at the installer screen now. I know I will need to figure out the right "Azul" later, but for now I can at least proceed with install. I'll report back again later.

Hervé, your note about the E/E not working is why I did the S/L/E, although I did not do the chmod/chown thing and I may not have done the -f. So I just booted in single user mode with the USB installer, and did the chmod and chown and booted with -f. Same problem. I also did the kextcache thing but found something peculiar there. it appears that every kext in S/L/E returned "WARNING - Invalid signature -2147416000 0xFFFFFFFF80010840 for kext ..." and concluded with a "Segmentation fault: 11". Whoa. Don't really know what any of that means or what it says about my current situation, if anything. I've been feeling like if I have gotten past the initial part of the boot up, I must be okay with my installer. But yeah, maybe now is a good time to see about doing the installer over. As for Mavericks version, I believe it is 10.9.4 - it's whatever would have come down from the App Store on Thursday.

Hervé, thanks for the fast reply. Yes, it is a young system - it's a "new" refurb I just got specifically for use as my new main Mac - it arrived yesterday. I downloaded those two kexts and put them in the USB installer's E/E directory and also in the S/L/E (both locations because of the comment in your linked post) and then ran myHack's myFix to make sure everything was okay. Unfortunately, no improvement - same result I got before the kext change. (If you think I should have put the kexts somewhere different or done something procedurally different, let me know.) I think the most interesting difference between your result and mine, however, is that your USB drive does keep working, even though it is super slow. Mine appears to be quite dead.

Jake, I've got an Optiplex 9020. It is an i7-4770 and therefore, should have the same HD4600 you have. I have followed your guide but I'm stuck booting up the USB installer on the 9020. It seems to load everything okay and then gets to "BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 No such file or directory" and hangs there while the USB stick's light stops blinking. I'm pretty confident that the BootCache thing has nothing to do with the problem. Am I right that the BootCache thing is a nice-to-have and that without it, the boot sequence continues and I just happen to see the activity fail shortly after that? Guessing it might be related to graphics, I removed the IntelAzulFB from the boot plist file and tried entering it at the chameleon boot prompt. I tried IntelAzulFB=1 through =15 and all gave the same result. I've also tried not using IntelAzulFB at all with the same result. Same with changing GraphicsEnabler=No and not using IntelAzulFB - same result. I'm using a DisplayPort connection on the computer and hooked in to a monitor that has a DisplayPort input. I have tried both DisplayPort connections on the back of the 9020 and same result on both. I tried adding the -gux_defer_usb2 switch at the chameleon boot prompt but that didn't have any effect. I also tried USBBusFix=Yes which also had no effect. Booting in safe mode (-x) does not change anything and neither does -f to ignore caches. Booting to single user mode (-s) will work in that it gets me to a prompt but that won't help get the installation running. In single user mode, I tried running lspci and got an "illegal instruction 4" error. So I booted from an Ubuntu Live CD and ran lspci there. It reports the video as 8086:0412. I created the installer yesterday using the version of myHack currently available for download. When I boot, I have "Chameleon svn2266 | myHack 3.3". And the Extra directory I'm using is downloaded from this post yesterday. The InstallESD is from a Mavericks installer I downloaded from the AppStore Thursday. At this point, I'm not sure what to do next. I don't know if I should pursue graphics issues or not. Maybe it is a DSDT issue. BIOS setting. Maybe something about the Extra directory contents or the boot plist is incompatible with this latest version of myHack. I'm hoping you have a suggestion on what to check next.

Jake, are you saying that with the AppleHDA from your guide, the controls sync when headphones are plugged in but do not sync when headphones are unplugged? That sounds right, given what I found: the modification I made was only in the platforms.xml and was only to the internal speaker path, not the headphone path. So my mod should only have improved the controls for the speakers. And thus, after my mod, controls should work for either internal speaker or for headphones. If I read that wrong and perhaps you are saying that my mod only works with headphones for you and that controls do not sync with internal speaker, that is definitely different than what I am experiencing. And if this is the case, I'd be interested to see your codec dump.

Oh sorry didn't mean to criticize! Yes there's lots of great info here. And amazing you managed to figure it all out even though you don't have the hardware. I just wanted to note where I had been confused so that when others read this post they don't think that the rev number 9 means they should use that as their platform. That killed a lot of time for me. I think the best way to choose platform is match video ram and capabilities. And most people reading this will probably want to start with 3. So I figured contributing this info was my way of giving back for all the great info you had here.

Next topic is sleep. Sleeping to RAM works great and it wakes perfectly. Sleeping to disk works but waking from disk does not. I get the Chameleon error: sleep read size 200 incorrect image signature And then it boots cleanly as though there was no sleep image. I've tried changing the hibernatemode to 1 using pmset. I've also tried changing it to 5 because I read that somewhere even though I think it was wrong. And I've tried changing it to 25 which is what the MacOS man page says. None of those worked. Same error as shown above. (In the long run, I do probably want "25" - if I want to use battery, then I'll leave the laptop on; if I am going somewhere and packing up the laptop, I want the power fully off right away. In other words, use safe sleep instead of a full shutdown.) I also tried "sudo defaults write /Library/Preferences/com.apple.virtualMemory DisableEncryptedSwap -boolean yes" which I avoided doing but tried just in case it worked. Nope, same error as above. I've got a very recent version of Chameleon so I don't think that's the issue. Any guesses? Are there any things I should check when this error comes up that I haven't already checked?

I have no idea why, but docking and undocking are working now. First, for docking, I close the lid first before docking and that seems to work better than docking and closing the lid as was suggested elsewhere;. It's a little silly since it will sleep for that second, but it handles the displays correctly. And now undocking works okay too - no change in my procedure, just kept trying? (It's possible that setting the displays to mirroring one time got past something?) Now that I know I have that much working, I think it's a good time to share my two files described in the previous post here in this thread. AppleIntelFramebufferCapri.kext.zip dsdt.aml.zip

Jeff, I've got the same hardware as you (also HD4000 only) and have been able to set up my system with most things working now. I've even improved on the AppleHDA so the controls stay in sync. (See the thread for my E6430 for audio and video details.) But one thing I can't get to work is the docking/undocking. When I dock, I get the additional display but closing the lid never takes away the internal one. Likewise with undocking, I lose the external display (duh!) but the internal one never comes back. Looking through the link you gave to Apple's site, there doesn't appear to be any magic there - just dock and close the lid and it will work is what it seems to say. But it doesn't for me. Any additional suggestions you can think of? Anything else you did that may have helped? Thanks!