veritae

I'm shocked! But after looking them up on Wikipedia, I see that this same person has nullified all perpetual licenses by saying that a version change means the original software will no longer exist. Your treatment seems to be one of their methods to reduce the number of customers with perpetual licenses. I would put the copyright notice in place and build a concurrent open source based forum that would then be promoted to the live forum. Both would be php based and then it's just a matter of copying database contents from one to the other. This is one example of how dependence on proprietary software means you don't control your own destiny. I've gone back to school to work on my B.S. in computer science so funds are limited but I offer assistance to aid in such an endeavor.

Could you explain how you resolved the issues? I have the same error messages. Could you also link the DSDT's you are using? Yes, I understand they are works in progress. I did some reading and it looks like the _DOS section is what we need to look at for the proper output port. Veritae

Oh that is very interesting. It sounds like one DSDT or some missing code detects the E-port and changes the output port. So... if we could use the DSDT to determine if it is docked (I believe that some system enclosure values change if docked and tell the system which type of dock is in use) we could use some logic to set the output port to what you docked DSDT does and if not docked, then set the values for your undocked DSDT.. no? Does an event have to occur for the ACPI code in the DSDT to be called or is it constantly running? If only event driven, we need to catch the dock/undock events.

I made some more progress... By changing the version byte in the E6430HD4000 DSDT from 03 to 09 (see below) I was able to avoid the "ugly screen" and noted that the screen went totaly black. As though the output was shifted to another port. Sure enough, when I hooked it up to my HD TV, I had a glorious 1920x1080 screen. I was unable to get a screen shot because the keys seemed wonky. I'm going to start calling this one E6430HDp4000 since the screen is HD Plus (check the F2 System Setup info) The Graphics/Displays section from the system report. Intel HD Graphics 4000: Chipset Model: Intel HD Graphics 4000 Type: GPU Bus: Built-In VRAM (Total): 512 MB Vendor: Intel (0x8086) Device ID: 0x0166 Revision ID: 0x0009 Displays: SHARP HDMI: Resolution: 1920 x 1080 @ 60 Hz Pixel Depth: 32-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Television: Yes Now I'm going to check into what resolved the "internal/external" display problem mentioned elsewhere here. Method (_DSM, 4, NotSerialized) { Store (Package (0x08) { "AAPL,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,ig-platform-id", Buffer (0x04) { 0x09, 0x00, 0x66, 0x01 }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "model", Buffer (0x17) { "Intel HD Graphics 4000" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Update: I now have Quartz (translucent menu bar) running with the DSDT from the E6430HD4000.zip modified as above. HD Kext is loaded. Really just the massive list of VoodooSDHC errors now. To get the output to display on the LCD, I had to use a modified AppleIntelFrameBufferCapri kext from another site (not sure which 10.8.x version it is though). http://iFail.me/forum/viewtopic.php?f=77&t=23300 Sound is working working, including auto detection of headphones, Mic working. Shutdown does a restart and sleep looks to be broken. I'll work on researching USB issues also. I think the 2.0 3.0 issues are related to rate matching internal hubs. I've also seem to have lost the ability to autosave screen captures to the desktop. Maybe having quartz active did something? Veritae

I tried the install link but it uses the 1366x768 screen that doesn't need the Dual Link patch to the DSDT. If I use the device properties method, OR the DSDT, when entering graphics mode, the screen starts black and turns ugly white with dark edges and corners... I'm sure this is not good for the LCD. Can I take the E6430HD4000.zip DSDT and add the Dual Link patch? Could someone tell me where in the DSDT I need to place the code or even a approximate line number? One place in the E6430HD4000 DSDT already has the Dual Link Code, (I'll double check to make sure it is identical) I'm getting very close. Still starting with -v -s DSDT=null I changed resolution in org.chameleon.Boot.plist to 1600x900x32 and I have a very nice screen in Safe Mode. Onboard Keyboard & TouchPad also working in Safe Mode (Yay!) eBay Broadcom works fine but displays as Third-Party Wireless Card (who cares as long as it connects via WPA-2) Thanks all for the suggestions. Veritae

I have been struggling with a similar E6430 with slightly different specs. Display is my biggest problem. It is HD+ (1600x900) and therefore not regonized by the existing DSDT's. There are also different processors that can be in these units. Mine is an i5 3320. I've extracted the acpi tables via SystemRescue CD but dont have the expertise to create a working DSDT.aml file for my unit. For the OP try booting with the following flags: -v -f -x DSDT=Null I've been able to do this and get safe mode running, complete initial Mac setup and even do some updates. I did use a usb mouse in safe mode but was able to install using onboard touchpad and mouse by having myHack integrate the E6430 pack on the key. Can anyone recommend next steps for getting some additional DSDT's? Thanks for making it much easier! V.