Hervé

It turned out to be an easy installation then, great! No idea about potential issues with Lion; I've never setup Mac OS X on an AMD system but give it a try, you'll know soon enough.

You'd be right there: you probably need NullCPU if you use SleepEnabler at the same time. But, whilst the D620 GMA will run fine without both, it may not sleep/wake properly without SleepEnabler. Anyway, if the default settings were to install NullCPU + SleepEnabler, then go with that and ignore my crap. My apologies for getting you confused (too many models and the old fart that I am is getting lost! "Fromage frais!" DelBoy might say...). Re: Chameleon Wizard, once you've downloaded it, just double click on your boot plist in /Extra and you'll understand...

Ok, that's what I thought: waiting for root device... That's not related to the LAN interface but to the chipset. We can try and fix that too, but try the 32bit audio kext in 32bit kernel mode first and see if you get audio. Now, you don't necessarily need to run the kernel in 64bit mode. The machine will boot in 32bit mode but that does in no way prevent the computer to run 64bit programs and applications. It's not like Windows where the 32bit version can only execute 32bit code and RAM is limited to 3.5Go. No such limitations with Mac OS X.

boot with -v option and tell us where it stops. Also, I just looked at some Ultra 20 documentation I found (http://www.atc.uniovi.es/inf_superior/4atc/PARALELAS/maquinas/arch-wp.pdf). It says AC'97 for audio. That limits you to 32bit kernel mode as there are no 64bit kexts for that audio type as far as I'm concerned, only 32bit kexts. I tried so-called AC'97 64bit kexts on my Precision 670 but they would not work... AppleAC97Audio.kext.zip AppleAC97Audio64b.kext.zip Oh and if you ever update to 10.6.8, use the following kernel afterwards (simply refer to it in your boot plist): Darwin_10.8.0.zip

Still unable to boot 64bit?

Try and use Chameleon Wizard to edit your boot plist, it's much much easier. In addition to repairing file permissions for that new kext you placed in /S/L/E, you also need to rebuild the kext cache. Using Terminal, try and type: sudo touch /System/Library/Extensions. In theory, that triggers cache regeneration. An alternative is to boot in safe mode using -x boot flag. Safe mode normally empties the cache which gets regenerated at next regular boot. There are also specific commands to handle cache; you'll get details by issuing the Terminal command: man kextcache. This is not the recommended way though... Since you've built your system with Nawcom's BootCD and not myHack, you can use a little tool called Kext Wizard to handle all this (kext installation and cache generation). MyHack includes its own tool called myFix (which should always be used with a myHack installation). I would also recommend that you 1st try and install new kexts in /Extra/Extensions rather than /S/L/E. This helps to keep /S/L/E vanilla and keep specific separate and in a place where you can experience with things. Only place new kexts in /S/L/E if you encounter trouble loading them from /E/E (assuming they're correct kexts of course). If you want to ignore kext caches, you can try to boot with -f flag or option UseKernelCache=No. This would slow the boot process a little, but all kexts will be looked at and your new nforce kext should load.

The D620 GMA950 does not need the NullCPUPowerManagement kext to run. But it means your boot plist has to bet set for P and C states. There's nothing infamous about the AppleIntelCPUPowerManagement, it's just the standard vanilla kext than handles CPU power and there's no problem with it on your model.

Reboot with flags: -f -v. You should be able to get to your desktop. The 2 error messages you got ("System extension cannot be used...") is the sort of things you get after you've installed a kext but have not (yet) repaired its permissions and rebuilt the cache. However, EDP does that automatically after a system build, so I wouldn't have expected those error messages to pop up. If when you get this sort of things after modifying kexts (add/delete/move kexts), go to Applications, run myHack and select myFix. Apply it to your HDD ("/") and do a full repair (not a quick one). Coming back to your KP, could you: have a look in folder /Extra/Extensions and check for presence of a kext called "NullCPUPowerManagement". I expect that kext to be absent. if it's not already on your system, download and copy a tool called Chameleon Wizard to your Applications folder, then double click on a file called "org.chameleon.Boot.plist" found in /Extra. Do a screendump (move pointer to target window, then press ALT-Left Shit-4 simultaneously, then press Space, then do a left click) of the boot plist tab and publish it here.

Of course, any new model is a candidate for integration!

Ok, if you need patching, follow the process detailed in R&D->Other research-> DSDT section. You can't miss it. PS: no EDP bug here, so moving post to support section.

In other words, it's work in progress.

Ok, thanks for raising this and providing the correct DSDT.

From 10.6.3, you ought to: 1) download and install Combo update 10.6.8 2) when prompted to reboot, don't! 3) download and install EDP. Launch EDP and do a system build for your particular D620 GMA950 LoRes model. You'll need to add the brightness fix too. That's it, you should then be able to reboot in a fresh SL 10.6.8 installation.

Did some tests with the Kozlek's FakeSMC kext + HWMonitor app as published in Web site article. I obtained similar results as with my D630 nVidia laptop, i.e. native SpeedStep + discrete graphics card GPU monitoring. This removes the need for PState kext & launcher, IntelCPUMonitor kext; even the VoodooTSCSync kext can be removed. I've been experimenting with MBP5,1 (SMC key 1.33f8) profile to start with as it's now a known good basis to verify behaviour. Then tested iMac8,1 (1.30f1), iMac9,1 (1.30f3) and iMac10,1 (1.53f13) profiles. All give good native SpeedStep and GPU throttling between 270Mhz and 810MHz. I saw no throttling at all for GPU RAM: it's always shown at 405MHz. After thorough testing, I found iMac10,1 settings (smc-mcp/1.53f13) appeared to give best clocking results overall. FakeSMC_1.53f13.kext.zip smbios_iMac10.1.plist.zip HWMonitor.zip - - - - - - - - - - Edit #1: 15 Aug 2013 . Updated post with SMC key & SMBIOS details, kext/app versions and copies of files. Now using FakeSMC v5.2.678 (compiled 32/64bit mode).

Good, now you can do a search on NVRAM module and Chameleon version conflicts...

BIOS can't be updated from OS X. You can: - use Windows package - use DOS bootable USB key - extract .hdr file from BIOS package and use recovery procedure Do a little search (on this forum or on the greater Web) and you'll find all you need.

If you have NVRAM.dylib in /Extra/modules, remove it and try again.

Well, normally you swap discs, press F5 to refresh media list on screen, the retail DVD should appear and if you press ENTER, it should load.

Are you using a Snow Leopard retail DVD and if so, which version is it? 10.6.0? 10.6.3? I can't recall ever seeing any reference to EVOreboot on any of my previous "standard" ModCD+retail SL 10.6.3 DVD utilisation. But maybe you're using a USB key with a restored image of SL and some tuning with kexts in /Extra.

Tabernacle! That is most excellent: native SpeedStep. It's probably the result of that more recent FakeSMC that you installed. Even greater if it's also able to monitor the GT610 GPU, which it appears to.

Excellent, another to the list! Well done! What do you mean re: Sleep works "manually"? Anything that doesn't work at all?

You should try and run some unix-level commands or programs in the background whilst monitoring your CPU multipler & frequency in HWMonitor. I've got a funny feeling you've got no SpeedStep at all and are therefore running permanently at lowest multipler & frequency. For instance, run Geekbench or open up Terminal and type: yes | yes | yes | yes >/dev/null &, then click on HWMonitor to monitor CPU. If SpeedStep is indeed running, you should see multiplier & frequency go up to maximum value (in your case x9.5 and 3.16GHz) with possible intermediate variations. If you have no SpeedStep, you're CPU will be stuck at x6 and 1.99GHz. Don't trust those CPU T° either... Even at x6 and 1.99GHz, I kind of doubt your E8500 would operate at only 28°. You probably require to do some Tjmax tuning here. If you're now using FakeSMC 5.0.3x (your initial kexts pack showed older version v4.2.0), have a look at the article we've posted on the web site re: performance turing with FakeSMC and SMBIOS editing. Find the Mac model that best matches your own gear and try to edit your SMC value. If you didn't have native SpeedStep, you may gain it this way. If not, you should use the emulated SpeedStep utility that we've included in EDP (PState).

If you use tools such as HWMonitor, you would be able to monitor Temperatures + CPU throttling. You may need a FakeSMC kext that's more recent that the version you're currently using or you can try to add plugin kexts too. If you don't have native SpeedStep and/or no SpeedStep facilitator (such as PState), your E8500 CPU is highly likely to be stuck at its lowest frequency/multipler, i.e. 2.0GHz.

No harm done at all. On the contrary, you may be able to contribute to fine tune certains things. And on double checking, I don't see a specific ML bootpack for the Optiplex 755 (although it's easy enough to make one up out of the previous 2), so thanks for showing us ML runs well on that model and without a (patched) DSDT table. In fact, you even seem to have a better installation than most I've seen on this model. I'm unfamiliar with the AHCI_3rdParty_SATA + AHCIinjector kexts you use, but I guess they work together, right? Did you try at all to copy/paste the ICHx AHCI contents of the injector to the "more" regular/known IOATAFamily kext plugin? I guess the BIOS does not offer native AHCI or RAID HDD mode. Did you try to boot without NullCPUPowerManagement and do you get native SpeedStep at all? Could you confirm your Optiplex 755 model and specs? SFF with Intel E8500, isn't it?

You don't necessarily need AHCI to install Snow Leopard... You say you get a KP; what does it show in the error message? I know of issues with nVidia graphics cards on AMD machines (at least for ML), so you may be in the presence of something similar.