Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About jebediah2

  • Rank
    InsanelyMac Protégé
  1. jebediah2

    [GUIDE] Dell Latitude E6410

    I thought I'd post some new explorations and discoveries in the "how to get that fixed" chapter for E6410. My specs are core i5 with NVidia graphics and 3gb RAM, and I'm running 10.6.8 without trouble except sleep, restart, and a somewhat higher temperature than I wish I had. So I donnow how my solutions will go for someone with different specs (especially thoses with integrated Intel graphics). This deals with do-it-yourself DSDT, but don't be scared away, it's easy. First off, olarila.com maintains a trusted database of DSDT patches for specific hardware. They happen to have one for both E6410 and E6510. I thought it wouldn't hurt to apply the current patch over ktbos' DSDT which was made a while ago. Furthermore the ones posted in this topic seemed not to have been so stable in this end. I'm using all the fixes I'm posting now and everything is stable. If you know nothing of DSDT, you're just like me, so just follow the steps: 1. If you're happy with your current DSDT stability, open your DSDT.aml (from your /Extra folder) with DSDT Editor. In my case I worked it out from ktbos' modifed DSDT.aml file. 2. If you're not happy with it, you'll have to extract the unmodified DSDT from your motherboard. To do this you will need to use DSDT Editor and boot without a custom DSDT (or the Editor will mistake it for your original DSDT). If that is a problem, run DSDT Editor Windows or Linux version. 3. Download DSDT Editor from here 4. Select File>Extract DSDT. If you're working from an existing DSDT.aml file, simply select File>Open instead. 5. Go to the patch page of olarila , register and download the E6410.txt patch 6. In DSDT Editor, select Patch>Open and browse the file. Press Apply button and Close. 7. Select IASL>Compile and press Fix Errors. If Errors don't get fixed instantly, something was already wrong with the extracted/opened DSDT. Repeat steps as stated. 8. Select IASL>Save AML as... and save the new file as DSDT.aml in some safe place. 9. Optionally select File>Save DSL as... if you want to edit your DSDT in your favorite text editor in the future. If you don't save your DSDT as DSL at that point, you will still be able to create it by converting your AML file with the help of an app called iaslMe . 9. Place the compiled AML file in your /Extra folder with the name DSDT.aml. Make sure you have a backup of the one you may so replace. Make sure you com.apple.boot.plist file mentions <key>DSDT</key><string>/Extra/DSDT.aml</string> in order to use the new file at boot. 10. You should now boot with a better custom DSDT that helps your OSX install to better speak to your hardware. Second, the dreadful [PCI Configuration Begin] is not so dreadful as it seems. Basically the booting process goes on but doesn't show up on the screen. Keep looking at the blinking icon on the top-left of your keyboard: if it keeps thinking, you're on the right track - but if it stops for a long while, it means you got a panic, the worst part being you can't diagnose it since no error has appeared! Anyway I found a DSDT way to permanently fix it in some forums: EDIT: I found out this fix doesn't work for Lion. However, it works fine for Snow Leopard 10.6.8. EDIT2: Recently I found out that once update to 10.6.8, the freshly installed AppleACPIPlatform kext prevents this fix from working (if not OSX altogether). Therefore, make sure you use the 10.6.7 version of AppleACPIPlatform (and possibly IOPCIFamily) for this to work. 1. Open your personally modified .AML file in DSDT Editor 2. From the left panel, scroll a few lines and select the "Device (PCI0)" section 3. Add "Name (_UID, Zero)" right under "Name (_ADR, Zero)" (FYI Zero is interchangeable with 0x00) 4. Look just a few lines below, if you see another occurrence of "Name (_UID, Zero)" close to a "Method" sub-section (I had one just above "Method _PRT..."), delete the occurrence (I think I had it from a wrong patch I had done earlier so don't worry if it's not there). 5. Now select IASL>Compile from the menu. Press fix errors if any shows up and they should resolve instantly. Then select IASL>Save AML as... and save the new file as DSDT.aml in your /Extra for next booting. 6. The [PCI Configuration Begin] no longer shows up at boot. Third, fix shutdown (so you don't have to press the power button to actually turn the computer off after OSX has exited): Open your custom DSDT in DSDT Editor, find the "Device (PS2M)" section, and replace: Method (_PTS, 1, NotSerialized) { APTS (Arg0) EV5 (Arg0, Zero) } with OperationRegion (PMRS, SystemIO, 0x0430, One) Field (PMRS, ByteAcc, NoLock, Preserve) { , 4, SLPE, 1 } Method (_PTS, 1, NotSerialized) { If (LEqual (Arg0, 0x05)) { Store (Zero, SLPE) Sleep (0x10) } Else { APTS (Arg0) EV5 (Arg0, Zero) } } 2. Select IASL>Compile, then press Fix Errors 3. IASL>Save AML as... Fourth, fix VGA. Note that this most probably applies to those with NVidia Graphics only: 1. Find the "Device DP2" section. There should be a "Method (UCMP…)" sub-section, scroll a few lines below and there should be a "Method (_DSM…)" sub-section. 2. Replace: Method (_DSM, 4, Serialized) { Name (_T_0, Zero) If (LEqual (UCMP (Arg0, Buffer (0x10) { /* 0000 */ 0x75, 0x0B, 0xA5, 0xD4, 0xC7, 0x65, 0xF7, 0x46, /* 0008 */ 0xBF, 0xB7, 0x41, 0x51, 0x4C, 0xEA, 0x02, 0x44 }), One)) { If (LNotEqual (Arg1, 0x0102)) { Return (0x80000002) } Store (Arg2, _T_0) If (LEqual (_T_0, Zero)) { VDP1 (0x06, Zero) Return (Buffer (0x04) { 0x21, 0x00, 0x08, 0x00 }) } Else { If (LEqual (_T_0, 0x05)) { CreateDWordField (Arg3, Zero, DSTS) If (And (DSTS, 0x01000000)) { And (DSTS, 0x0FFF, GATD) And (ShiftRight (DSTS, 0x0C), 0x0FFF, GACD) } Return (Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }) } Else { If (LEqual (_T_0, 0x13)) { Return (Buffer (0x04) { 0x00, 0x06, 0x00, 0x00 }) } } } Return (0x80000002) } Return (0x80000001) } with Method (_DSM, 4, NotSerialized) { Store (Package (0x2A) { "AAPL,aux-power-connected", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL00,blackscreen-preferences", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL01,blackscreen-preferences", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,built-in", Buffer (One) { 0x01 }, "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,device_type", Buffer (0x08) { "display" }, "@0,display-cfg", Buffer (0x04) { 0x03, 0x01, 0x00, 0x00 }, "@1,display-cfg", Buffer (0x04) { 0xFF, 0xFF, 0x00, 0x01 }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "NVCAP", Buffer (0x18) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, /* 0008 */ 0x0E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "NVPM", Buffer (0x1C) { /* 0000 */ 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0018 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x20 }, "device_type", Buffer (0x0D) { "NVDA,GeForce" }, "model", Buffer (0x19) { "nVidia GeForce NVS 3100M" }, "built-in", Buffer (One) { 0x01 }, "rom-revision", Buffer (0x27) { "nVidia GeForce NVS 3100M OpenGL Engine" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } 3. Select IASL>Compile, then press Fix Errors 4. IASL>Save AML as... I'm attaching my DSDT in case you don't wanna run the trouble to do it all yourself. However I don't recommend it since we may not have have the exact same specs/motherboard. That is why you should always patch your own DSDT by yourself. Now I'm mostly looking for CPU temperature solutions. Since I switched to a 500Go 7200RPM hard-drive, my idle temperature is around 60°, but easily goes to 70°-75° under normal load and above 85° under heavier, but still regular load. Unfortunately olarila's DSDT patch doesn't fix much regarding this. Also sleep works without SleepEnabler but only half of the time (I think it won't wake up when I've waited to long after putting it to sleep - I get the "incorrect image signature" message). And finally I've been reading that some got restart to work on this machine. I'd be grateful if they could give more info on that one. Hope this is useful! DSDT.aml.zip
  2. jebediah2

    [GUIDE] Dell Latitude E6410

    Hi Jsmmao, There definitely is a solution for wifi access on the E6410 running OSX without the need for a dongle. The one I can testify for is replacing your internal wifi card with the Dell DW1397 (aka Broadcom BCM94312HMG) which is compatible for OSX (I tried with 10.6.6). The DW1397 is just as fast, operates on the same range, and sells cheap on eBay (though the first I received from China was actually defective and made me doubt the method). So after replacing the original card I followed the instructions posted by ETdoFresh on this thread and that was all there was to it! I'll transcript the method here for convenience: - Open Terminal - sudo su - /Applications/TextEdit.app/Contents/MacOS/TextEdit /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AppleAirPortBrcm4311.kext/Contents/Info.plist - Add <string>pci14e4,4315</string> under <key>IONameMatch</key><array> - Save and Close TextEdit NOTE: if you can't save at this point due to permission issue, I fixed that by giving Read&Write permissions to myself for the Info.plist file AND the folder it's contained in. - Reboot computer in 32-bit mode (very important in my case, and was the one thing I was missing). How? In my case, during the Chameleon boot screen, press the down arrow and then type in arch=i386 - If you see the wireless icon, or empty baseball field icon on top on your toolbar, you are almost there! - Open Terminal again - sudo su - /Applications/TextEdit.app/Contents/MacOS/TextEdit /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist - Change <string>en0</string> to <string>en1</string> AND Change <integer>0</integer> to <integer>1</integer> - Save and Close. Reboot (I rebooted once more into 32-bit mode, and then normal 64-bit mode). Hope this will help everyone trying to get wireless!
  3. jebediah2

    [GUIDE] Dell Latitude E6410

    Thank you for this guide. It is a godsend especially as osx86 first-timers couldn't dream of anything better than a dedicated boot cd and tutorial for their laptop. I am one of them but despite familiarity with basic command line and booting operations I couldn't get past step 5, which means I do not even get to the OSX Install screen. I did set SATA Operation to AHCI. In fact I would like to dig a bit more on the error reported by ucandoit earlier in this thread, because his screenshot (here) is actually the exact same I have. What happens is I hit the Install DVD in the bootloader and some verbose goes on for like 10 seconds before it stops and gives a kernel panic based on the following line for a missing kext: Can't load kext com.apple.iokit.IOACPIFamily - link state missing. Therefore it can't load com.apple.driver.AppleACPIPlatform for dependency reasons, and continues with errors of missing com.free.driver.UUID, and com.psystar.driver.OpenHaltRestart. One other potential hint I spotted was right after I hit the Install DVD button in the bootloader, some verbose about loading drivers starts in the Chameleon background first, and indicates one line of failure although not putting a halt to the process: FileLoadDrivers failed on a ramdisk Then it goes on and eventually switches to a black DOS environment in which the aforementioned screenshot appears. This is happenning with a more recent version of a single layered Install DVD. My specs are as follows: E6410 with A06 BIOS Discrete NVidia NVS 3100M i5-520M 3GB RAM PLDS DVD+-RW DU-8A3S ATA Intel 82577LM Gigabit Intel Centrino Advanced-N 6200 AGN No Bluetooth Ricoh 1394 OHCI Compliant I have tried both with the HDD wiped out and with Windows 7 installed. I hope this is not a matter of new Latitude hardware. Have tried with other OSX images to no avail. I have read reports of people having similar issues of OSX Install not getting to install screen in different contexts. Some managed to solve their problem by either removing all OS from the HDD or trying with an earlier version of Snow Leopard (one had success with 10.6.3 instead of 10.6.5 I think). I have a hard time figuring this out with my weak knowledge of OSX environment and OS installation processes in general. Thanks, your help is much appreciated.