Hervé

If you've installed EDP, it's available in the list of installation kexts. On the D630, it's one of the kexts I've had to use to get keyboard+mouse/trackpad to work.

They are just batteries, nothing else. They do not provide any additional functionalities or extensions like a docking station or a port replicator does.

Just so that there is no confusion, are you talking about battery slice as illustrated below? If that's the case, I see no reason why it would not. After all, Latitude D6xx run OS X ok when connected to a docking station and so do attached devices (screen, keyboard, mouse, USB devices, etc) + power block. I would not expect any need for dedicated kexts...

Mmm, sounds like we need to verify M4300 bootpack too. Out of interest, do you get the correct Graphics Card reported, or do you get the NV 135m of the D630?

That's the HiRes DSDT all right. Ok , so to me, that definitely points the built-in LCD corrupted graphics on wake to incorrect DSDT table. Thanks for your feedback. We'll put a new bootpack out for D620 GMA950 HiRes.

Hi guys, those of you on D620 GMA950 HiRes (1440x900), could you check whether you use the LoRes (1280x900) DSDT or HiRes DSDT? There's no easy way to check the version except decompiling the table to DSL file (via ChamWizard for example) and checking it out in a text editor (look for "Width" and/or "Height" parameters in Hex -> 0xA0 0x05 and 0x84 0x03 respectively for Hi Res, 0xB0 0x04 and 0x20 0x03 respectively for LoRes). I say this because there is only one D620 GMA950 bootpack wich contains both DSDT tables and, by default, the LoRes table is installed as /Extra/DSDT.aml. You have to go to model specific subdirectory of /Extra to find the HiRes DSDT. Maybe the root cause of the problem is simply the wrong DSDT. I could not reproduce the problem with my D620 GMA950, but it's a LoRes model...

ML or Lion for GMA models. No issue experienced with that OS X version either.

Well, I would have expected the same error with the kext I sent since it comes from 10.8.2. What I meant to ask was to compare kext & plugins from 10.8.1 and 10.8.2 (size + individual plugins versions). What happens if, before booting 10.8.2, you replace that kext by the version from 10.8.1?

Hi and welcome. The D630 is one of the easiest platform to turn into a Hackintosh. You'll find all you need on the Web site's pages, not just the forum. Start at the EDP pages where you will find documentation, procedure, bootpacks (you'll need to choose the right one), compatibility table, etc. Then you can read-up the D6xx pages of the forum. You'll find that Snow Leopard runs exceedingly well and exceedingly fast on a D630. Just remember that Intel wireless cards are incompatible with Mac OS X and that, to date, there's no solution to get PCMCIA port working well along all the other hardware. For the rest, it's 100% operational. Note that our recommended installer creation solution (i.e. myHack © by Conti) works only with retail versions of Mac OS X. Anything else will fail as only retail versions have all the files required for installation from scratch. Have a go and let us know how it went.

To all of you who got stuck at: ACPI: System State [s0 S3 S4 S5] [ PCI Configuration begin ] please download new D830 boot pack. The ACPIPlatform kext might have been missing from the boot pack, resulting in above state/issue. The boot packs certainly are Ok now. If one of you could try again, that'd be great. Thanks.

Guys, I'd avise you download the D830 bootpack again and retry; one kext might have been missing these last few weeks, but it sure is Ok now.

And if you want to compare... IOPlatformPluginFamily.kext.zip (from 10.8.2)

Ok, here's what I have: How does it look on your laptop with 10.8.1?

Was that after a straight update to 10.8.2? There is a ACPI_SMC_PlatformPlugin.kext as a plugin inside /S/L/E/IOPlatformPluginFamily.kext on my D630 under 10.8.2. I need to check if it's loaded or not, but if it is the case with 10.8.1 (something you can check), maybe you could try to port that onto 10.8.2. You never know... Of course, I'd take a full backup of /S/L/E + /Extra before the update.

'glad you found this site of assistance. The D630 nVidia is indeed a great C2D platform to run ML. My own one has an ultra crisp LCD with WSXGA+ resolution + SSD drive which makes for a superb oldish laptop to run Mac OS X (Ok, I'm a great fan of 13"-14" size laptops). I might replace my 11g wifi card by a 11n model to get improved internal network performance, especially with my Win-based server. Enjoy your latest Hackintosh!

Hi Dragon, thanks for your contribution and feedback post DSDT table creation by Dinesh. Definitely a new system for integration into EDP.

Do you have the Chameleon SATA module in /Extra/modules? Available here: http://forge.voodooprojects.org/p/chameleon/downloads/ BIOS HDD settings set to AHCI?

Ok, we found that a kext had gone missing from the bootpack. it's been corrected. Re-download and re-apply the bootpack (re-run myHack -> install /Extra) and all will be in order, although it looks like you got there with that other /Extra folder which had the required kext!

Because the bootpack is what it's called: a boot package. It's the basic stuff required to boot and get started (DSDT table + mandatory kexts and modules). It does not contain all the additional EDP stuff or whatever a user may add post-installation (eg: Chameleon themes) in /Extra.

1) http://argo.osxlatitude.com/edp/bootpack/ 2) https://osxlatitude.com/index.php?/topic/1868-bios-settings-d630/ 3) http://argo.osxlatitude.com/edp 4) http://argo.osxlatitude.com/edp/pre-installation/ 5) http://argo.osxlatitude.com/edp/installation/ 6) http://argo.osxlatitude.com/edp/post-installation/

Did you try boot option: PciRoot=1 ? All usual Broadcom-based wireless cards will work: DW1390, DW1395, DW1490 to name some '11g' cards. You used the M4300 bootpack, right? If that didn't work to boot the M4300, note that it is quite similar hardware to D630 or D830, so you may reach some success with one of those bootpacks. Use the nVidia versions.

That just applies to built-in LCD or ext. display in mirrored mode. The problem experienced above is only for ext. display in extended mode and that is only available post-boot.

Try this in /S/L/E, but I would expect it to be ignored... IO80211Family.kext.zip 'ever tried to use the BCM43xx kexts instead of patched IO80211 for that DW1395?

Out of interest, I've also done the same tests with my 20" widescreen 1680x1050 LCD. -> same sort of results: bottom of screen gets corrupted beyond 1280x800: 1) @1280x1024 2) @1680x1050 -> looks like any resolution starting from 1280x1024 and above gets corrupted.

Ok, good, that's exactly what I experienced the other day. It's totally consistent and the black parts on the external screen are due to the widescreen ratio that is being maintained across both displays. You should still be able to select 1440x900 on the built-in LCD and another resolution on the external display; it'll then adjust with bars accordingly. Now, coming back to the issue you reported in extended mode, I have good news and bad news. The good news is that I can 100% reproduce the problem with my D620 GMA low res; the bad news is that there is indeed a problem! I hooked my D620 (GMA950) to a 19" 4:3 1280x1024 external LCD and booted SL 10.6.8. Internal display was @1280x800 as usual and external screen got automatically set by default @1152x864 (75Hz). No problem, external display looking nice enough. I then started to play with higher resolutions. 1) @1280x768 (60Hz), no problem, but graphics and text are a bit distorted/squeezed horizontally due to resolution. Not nice at all (doesn't show on screencopy). 2) @1280x960 (60Hz), no problem. Graphics and text look very much like @1152x864, there is just a bit more space available on the screen. 3) @1280x1024 (60Hz/75Hz), I too get the graphics corruption at the bottom. The issue is bad enough to even temporarily affect screen contents during moves. Conclusion: stick to 1152x864 or 1280x960!