Hervé

EDP 5.0 worked perfectly 2days ago when I updated my D620 and did a system rebuild from EDPWeb. I guess you might have had a problem during update. Try and download a fresh copy and do a (full) re-installation. Then use /Extra/edpweb.command to redo your system build.

The manual module deletion fixed it then.

Without knowing the wireless card model, it's going to be difficult to answer...

Run /Extra/EDPWeb.command https://osxlatitude.com/index.php?/topic/2107-the-future-is-here-edp5/

pci=off ? That's a new one to me... What does that do?

You have the NVRam module + Cham boot file mismatch issue... Either remove FileNVRAM.dylib from /Extra/modules or replace/update your Chameleon boot file at HDD root by version 2170 or above. Best would be to redo a system build through EDPWeb. PS: don't use Chameleon boot file rev2181 on a D620, it will cause the system to KP...

Which card? On wake, does the wifi icon in the Finder bar stay empty (=deactivated), light gray (meaning non-connected) or does it go to black (meaning connected)? If light gray, it simply has not hooked back to your network. You say "previously I'm sure it did it straight"... What did you change or recently do then?

Just no onions in the oven tray.

Your BIOS is fine (latest version is A18, but that just brings signed firmware support). Which wireless card do you have? Does wireless not come back at all on wake, even after a minute or so?

Mmm, I just quickly checked the specifications as provided on Dell's web site and I see 2 systems with non-trivial differences. For instance: - GM45 chipset on one vs. PM45 on the other (I admit the diffs will be minor between the 2) - NVidia graphics only on one vs. Intel GMA X4500 only on the other To me, that sufficient to say the DSDT table of one model is not suitable to the other.

Well, DSDT is a BIOS table, so it's kind of specific to a model or a family of models. I could be wrong of course, but maybe the DSDT of a Latitude E64xx does not suit a Precision M44xx, unless they really share the same characteristics (chipset, controllers, graphics, screen, etc.). You could try without the DSDT (boot with option DSDT=No) or extract your own one.

As far as Video kexts are concerned, non-applicable ones (such as nVidia) should be without impact; I'd expect them not to be loaded since the OS would not find a matching PCI device id...

Did you use files or tables that could be specific to the E6400 (like DSDT)? If not, try rebuilding your kext cache with a myFix (full).

Re: 2.0GHz CPU reported at 1.81GHz, that could be a side effect of IDA. Check your BIOS settings and if it's enabled, disable it. Which CPU do you currently have, T7250 or T7300? You can upgrade your CPU to any C2D T7xxx, T8xxx or T9xxx at FSB 800MHz. The Extreme C2D CPUs should be supported too: X9000 or X78xx. I found these laptops work really really well with 4Mb cache CPUs (for instance, I found a D830 with a T7250 occasionally choppy under ML 10.8.2, whereas my D630 with a T7500 is a lot smoother). Unless you're a RAM-hungry application user, I doubt that 8Mb RAM would make any difference. But DDR2-800 does make a difference on DDR-667. I'd stick to 4GB.

Why do you add Mariusz's kexts? What's the purpose? You should only have to follow the documented procedure, i.e. : - myHack with dedicated bootpack to install 10.7.2 - install combo update 10.7.5 (no reboot on completion) - install and run EDP (EDPWeb) for D630 Intel HiRes (after which you can reboot to 10.7.5) That's it. The only possible missing item would be the wireless kext if you have a card that does not work OOB.

Assuming the Ethernet issue is indeed solved, please discuss other issues in appropriate posts.

I read about this Deviato thingie; I'd stay away from that old thing, the X3100 patching sounds a better method to me. With a T7200, you would really have to find a good explanation for using a legacy kernel!!! Just use plain Mach kernel. Again, I strongly recommend that you get SL 10.6.8 running before you start tuning things. Graphics set aside, everything else should be more or less straight forward under 10.6.8. But anyway, it's your call...

No, I would not think so, but I'm far from understanding how you installed Lion on your machine. Had you followed our myHack-EDP process, I'd know what to answer, but it appears you possibly followed obsolete ways... I have no problem running my D630 GMAX3100 on docking station with external VGA screen @ 1440x900 (no higher res I'm afraid), whether as main screen or as extended display. No problem running it in extended mode attached to my TV @ 1920x1280 either.... Haven't tried it as main/single screen, but that's an idea!

I would actually recommend that you run 10.6.8, because you'll get far more/far better support. For instance, most of the kexts we could recommend would have been tested with 10.6.3 and beyond. 10.6.0 is too old now and hardly anyone will be running that version. Upgrading really should not be an issue at all. If you want, you could even do it in steps: 1) download and install 10.6.3 Combo update - I'd expect this to be completely straight forward 2) download and install 10.6.7 Combo update - usually a straight forward update from 10.6.3 3) download and install 10.6.8 - can require kext tuning, especially ACPI/PCI/USB kexts... Why would you want to use legacy kernels??? What kind of CPU do you have?

You could also extract the DSDT table from your D630 with SATA mode set 1) to AHCI and 2) to IDE. Then compare the differences in the table to investigate potential DSDT edits...

No need to wait. Have faith!

Congrats for getting there! You should be safe to update if you're already running EDP-tuned 10.7.4, yes. It certainly worked for me months ago, with nothing to do on completion: https://osxlatitude.com/index.php?/topic/1819-1075-update/

If DSDT patching does not appear feasible, I was thinking that maybe a Chameleon module could work (where the device id would be changed from 27c4 to 27c5) -> that would in theory patch the kernel and be similar to those patches you see on Linux. Something to suggest to Chameleon developpers possibly... Wouldn't that operate before the OS begins to load? Isn't the Cham Sata module doing something similar?

AMD-based systems are a challenge, to say the least. Try another kernel maybe, like Modbin... You've probably done it, but I'd search the Net for info on systems of similar setup (chipset, CPU) and check all the BIOS settings.

'afraid not, the tables are 99.999% identical. Only line 5540 bears a tiny difference (unrelated to SATA controller) : Method (ZEJ0, 1, NotSerialized) -> in BIOS table Method (_EJ0, 1, NotSerialized) -> in Linux table